From fixing failures to anticipating them

Maintenance strategy in manufacturing has evolved in three broad stages. Reactive maintenance fixes machines when they break. Preventive maintenance services them on a fixed schedule, whether they need it or not. Predictive maintenance tries to service them exactly when the data says failure is approaching. The economics are compelling: reactive work causes costly unplanned stoppages, while preventive work wastes parts and labour on healthy equipment.

What has made predictive maintenance practical at scale is a combination of cheap sensors, industrial connectivity and mature machine-learning tooling. A vibration sensor that once required a specialist and a laptop can now stream data continuously to an edge gateway. My own interest in embedded systems makes this the part I find most exciting: the intelligence is increasingly moving onto the device itself, closer to the motor, pump or compressor being monitored.

For manufacturers in Nigeria and across Africa, the motivation is often sharper than elsewhere. Spare parts may have long import lead times, foreign exchange is expensive, and specialist technicians are scarce. Knowing weeks in advance that a bearing is degrading can be the difference between a planned weekend repair and a month-long shutdown.

How the technology actually works

Signals and features

Most rotating equipment fails in physically understood ways. Bearing defects, misalignment, imbalance and looseness each leave characteristic signatures in vibration spectra. Traditional condition monitoring uses frequency-domain features (FFT peaks, envelope analysis, RMS, kurtosis) computed from accelerometer data. Machine learning builds on this: rather than replacing domain features, the best systems feed them into models alongside temperature, motor current, pressure and operating context such as load and speed.

Anomaly detection

Failures are rare, so labelled failure data is scarce. That makes unsupervised anomaly detection the workhorse. Methods range from statistical control charts to Isolation Forest to autoencoders that learn to reconstruct "normal" sensor patterns and flag high reconstruction error. The survey Deep Learning for Anomaly Detection (Chalapathy and Chawla) gives a good overview of the deep approaches and their trade-offs.

Remaining useful life

Where run-to-failure histories exist, teams train regression models to estimate remaining useful life (RUL). Sequence models such as LSTMs and temporal convolutional networks are common choices because degradation unfolds over time. In practice, RUL estimates are noisy and are best used as a ranking signal for maintenance planners rather than a precise countdown.

Computer vision for quality

The same AI wave has transformed visual inspection. Convolutional networks trained on images of good and defective parts can spot scratches, misprints or assembly errors at line speed. Combined with predictive maintenance, this lets factories connect machine health to product quality: a slowly drifting spindle often shows up first as a subtle rise in surface defects.

Edge versus cloud

High-frequency vibration data is large. Rather than streaming raw signals, many deployments compute features or run compact models on edge devices and send only summaries and alerts upstream. Model compression and quantisation make it possible to run useful anomaly detectors on modest microcontrollers.

Real-world examples

Predictive maintenance is now a standard offering from major industrial equipment makers, who monitor turbines, compressors and engines in the field and sell uptime as a service. Aviation is the most mature example: engine manufacturers have long analysed in-flight sensor data to schedule maintenance before problems occur. Public benchmark datasets, such as simulated turbofan degradation data released by NASA, became the standard training ground for RUL research for exactly this reason.

In discrete manufacturing, beverage bottlers, cement plants and food processors use vibration and thermal monitoring on conveyors, mills and packaging lines. These are sectors with a large footprint in West Africa, and they share a pattern: a handful of critical assets whose failure halts the entire line. Focusing AI on those bottleneck assets typically delivers far more value than blanketing every machine with sensors.

Risks and limitations

  • Alert fatigue. An anomaly detector that cries wolf a few times will be muted by the maintenance team. Precision matters more than recall in the early stages of adoption.
  • Changing operating conditions. A machine running a new product, at a new speed or after a repair looks "anomalous" to a model trained on old data. Models need context features and a process for re-baselining.
  • Label scarcity. Maintenance logs are often handwritten, incomplete or inconsistent. Without reliable records of what failed and when, supervised models cannot be validated.
  • Security of operational technology. Connecting legacy industrial controllers to networks exposes them to attack. Monitoring systems should be read-only where possible and segmented from control networks.
  • Skills displacement. Experienced technicians hold tacit knowledge that models lack. Systems designed to sideline them tend to fail; systems that amplify them tend to succeed.

For governance, the NIST AI Risk Management Framework offers a practical vocabulary for mapping, measuring and managing these risks, even though it is not specific to manufacturing.

Implementation guidance for teams

  1. Pick the right asset. Start with one critical, failure-prone machine where downtime has a clear cost. Avoid the temptation to instrument the whole plant.
  2. Digitise the maintenance log. A simple, structured work-order system is the most valuable dataset you will build. Every repair becomes a label.
  3. Combine physics and ML. Use known fault frequencies and engineering thresholds as features and sanity checks. Pure black-box models are harder to trust and debug.
  4. Design the workflow, not just the model. Decide who receives an alert, what they are expected to do, and how they record the outcome. An alert without an owner is noise.
  5. Plan for power and connectivity. In many African facilities, power fluctuations and patchy networks are normal. Edge buffering and robust hardware enclosures are part of the AI system.
  6. Measure value honestly. Track avoided downtime, false alarm rates and technician feedback. Organisations like UNIDO emphasise that digital industrial upgrades in developing economies succeed when tied to measurable productivity outcomes.

Conclusion

Predictive maintenance is one of the clearest, most measurable applications of industrial AI, but it rewards patience and humility. The algorithms are well understood; the hard parts are data discipline, alert design and earning the trust of the people who keep machines running. For emerging-market manufacturers dealing with long parts lead times and scarce expertise, getting those fundamentals right can be a genuine competitive edge.

Key takeaways

  • Predictive maintenance aims to service equipment exactly when data indicates degradation, avoiding both breakdowns and wasted preventive work.
  • Unsupervised anomaly detection on engineered vibration and process features is the practical starting point, since failure labels are rare.
  • Remaining useful life models are noisy and best used to prioritise, not to predict exact failure dates.
  • Edge computing reduces bandwidth needs and suits environments with unreliable connectivity.
  • Success depends on structured maintenance records, clear alert ownership and respect for technician expertise.

References & further reading

  1. Isolation Forest — IEEE ICDM 2008 (Liu, Ting and Zhou)
  2. Deep Learning for Anomaly Detection: A Survey — arXiv (Chalapathy and Chawla)
  3. An Empirical Evaluation of Generic Convolutional and Recurrent Networks for Sequence Modeling — arXiv (Bai, Kolter and Koltun)
  4. AI Risk Management Framework — NIST
  5. United Nations Industrial Development Organization — UNIDO

Cover image: original illustration created for this article. Cited works remain the property of their respective authors and publishers.