Skip to content
Hakan KaracaENGINEERING JOURNAL
AI & Intelligent AutomationEki 8, 20263 min read

Anomaly Detection vs. Alarm Logic: Define the Job Before Adding AI

Traditional alarms are good at detecting defined conditions. AI is useful when the interesting condition is a change in pattern.

An anomaly score is not an alarm rationalisation strategy, and an alarm is not automatically a root-cause diagnosis.

Traditional alarms are usually tied to known conditions: a limit was exceeded, a permissive was lost, a device went offline, or a sequence did not progress within the expected time. They should have a defined meaning and response. Anomaly detection instead asks whether current observations differ from a learned or statistical representation of expected behaviour. It can reveal patterns that were not explicitly encoded, but its output is often less specific: something looks unusual, not necessarily what happened or what the operator should do.

Match the method to the failure knowledge

If a pressure must stay below a validated limit, implement and verify the appropriate deterministic alarm or protective function. A learned anomaly model should not replace a known limit simply because it sounds more advanced. If an engineer wants to detect a combination of vibration, current and temperature trends that tends to precede bearing degradation, anomaly detection may be a useful supplementary signal. If the process changes mode often, the model must understand which mode it is observing or it may alert whenever production does something different.

What does the score mean?

Document the input features, time window, baseline period, training exclusions and expected operating envelope. Decide whether the score is a ranking for investigation, a notification for maintenance or a trigger in a higher-consequence workflow. A score of 0.92 has no universal interpretation unless the calibration and target definition support one. Displaying two decimal places does not create certainty; it only gives uncertainty better typography.

Build a layered response

  1. Known hazards and limits: retain deterministic alarm and protective logic.
  2. Novel patterns: use anomaly detection to prioritise investigation, initially in a shadow or advisory mode.
  3. Diagnosis: combine model output with engineering context, trends, work orders and operator observations.
  4. Action: define an accountable person, response time, escalation path and feedback mechanism.
  5. Review: analyse both useful detections and false alarms, then update the model through controlled change.

Evaluate alerts in operational terms

Precision and recall are useful, but industrial teams also need alert rate per shift, average lead time, time spent investigating, performance by recipe or speed, and the percentage of alerts that lead to a justified action. Label quality matters: a maintenance work order is not always proof of a failure, and no work order does not prove that an anomaly was harmless.

Protect operators from alert fatigue

Do not create a second alarm flood next to the first one. Suppress repeat notifications when the underlying condition remains unchanged, group correlated signals where appropriate, show the evidence behind a detection and provide a clear “insufficient data” state. Feedback should be captured in a way that does not let a convenient click silently redefine the ground truth.

AI should extend an engineered alarm strategy, not disguise the absence of one. The best result might be fewer false alarms, more useful maintenance leads or simply a better understanding of which process states are normal. That is measurable engineering value.

References and further reading

  1. NIST AI Risk Management Framework