A field guide to finding useful AI applications without turning every sensor into a machine-learning project.
Industrial AI proposals often begin with a model family: a neural network, a vision transformer, a time-series model or a large language model. That is understandable—tools are exciting, and a demo that recognises a defect in three seconds can be persuasive. But the engineering question comes first: which decision is currently difficult, delayed, inconsistent or expensive, and what evidence would show that an AI system improves it?
Start with an operational decision
Consider a pump that fails more often than expected. A vague goal might be “predict pump failures with AI.” A testable goal is narrower: identify operating conditions associated with abnormal vibration early enough for maintenance to schedule an inspection, while keeping the nuisance-alert rate within an agreed limit. The second statement defines a decision, an action window and a trade-off. It also leaves room for the possibility that a simpler threshold or maintenance rule is enough.
Three useful families of problems
- Perception: computer vision for surface inspection, component presence or visual classification, provided illumination, pose, occlusion and acceptable defect rates are controlled.
- Prediction and anomaly detection: models that combine trends, operating modes and contextual signals to estimate risk or flag unusual behaviour.
- Knowledge assistance: retrieval-based systems that help engineers locate relevant manuals, alarm procedures and controlled documentation, with citations and permission-aware access.
These families require different evidence. Vision needs representative images and a defined labelling policy. Predictive maintenance needs event history and time-ordered evaluation. Documentation assistants need document lifecycle control, retrieval evaluation and a way to verify that an answer is supported by the cited source.
What data quality actually means
“We have a lot of data” is not enough. Check clock alignment, sampling intervals, missingness, sensor calibration, unit consistency, operating-mode changes, maintenance interventions and the way failure labels were created. Historical data often reflect the old process and its old operating policy. If operators intervened when a warning appeared, the absence of a subsequent failure does not automatically mean the warning was wrong.
Evaluate the workflow, not only the model
Track the baseline, the model’s performance and the downstream outcome. For a classifier, useful metrics may include precision, recall, false negatives, false positives and performance by operating regime. For a decision-support tool, also measure whether people use the output, how often they override it, how long they take to act and what happens when confidence is low. A model with an excellent offline score can still be operationally irrelevant if its alerts arrive after the maintenance window has closed.
Keep a non-AI baseline
Compare the proposal with a rule-based baseline, an existing alarm or a simple statistical model. This is not an argument against machine learning; it is the control group that tells you whether the additional complexity earns its keep. If the new model only outperforms an intentionally weak baseline, the slide deck may be more impressive than the result.
Deployment is a lifecycle
Plan data versioning, model versioning, monitoring, drift detection, rollback, access control, human oversight and ownership after the pilot team leaves. Define what the system does when the input stream becomes stale or the model service is unavailable. For control-critical functions, use the appropriate safety lifecycle and do not quietly place a probabilistic model inside an unreviewed interlock.
Industrial AI is most valuable when it improves a decision that already has a clear owner, an action and a measurable outcome. Start there. The model can come to the meeting after the problem has been introduced.