← Back to the chapter · Next detail →
Technical detail · Time-Series Anomalies: Machine Learning
Training drift and deployment capacity
ML anomaly models are sensitive to training data. If the training period contains hidden faults, the model may learn faulty behavior as normal. If the site changes equipment, firmware, sampling rate, sensor placement, or operating modes, the model can drift. If the score is opaque, operators may ignore alerts even when the model is technically correct. A production ML detector therefore needs model governance, not just model training.
Deployment tier matters. Feature extraction and small-tree inference may fit at an edge gateway. Larger neural models, fleet comparison, retraining, and drift dashboards usually belong in cloud or offline workflows. A reliable design records where each step runs, what happens when connectivity is missing, and how alerts degrade when required features are absent.
Size the deployment path before choosing a model. A gateway with 256 MB RAM may fit a compact Isolation Forest over 12 features; verify the implementation and memory use. It may struggle with a neural model that needs large rolling tensors and GPU-style batching. If 500 motors send one 12-feature window every 10 seconds, the fleet produces 500 x 6 x 60 = 180,000 windows per hour. Pushing all raw windows to cloud may be acceptable on Ethernet, but edge scoring plus cloud review may be cheaper on cellular or congested plant networks.
Drift review should compare both feature distributions and score distributions. For example, if median motor load rises after a process change, a stable model may suddenly score normal production as abnormal. The right response is not simply to retrain overnight. First replay a recent normal window, check whether known incidents still score high, compare false-alert volume with operator capacity, and record the approved baseline version. That makes model change a controlled release instead of a hidden dashboard adjustment.