What was going wrong
The authority had invested in a SCADA historian that collected data from 1,200 field sensors, but the data sat in a database and was only queried after a failure had already occurred.
Three pump bearing seizures in one quarter had caused 72 hours of unplanned water supply interruption to a city of 4 million people. The maintenance logs showed all three pumps had been serviced within the manufacturer recommended interval.
How we ran it
We built physics-based degradation models for each asset class: vibration spectral analysis for rotating machinery, thermal cycling fatigue for heat exchangers, and cavitation erosion curves for pump impellers. Each model was calibrated against the specific operating history of the individual asset, not against generic manufacturer curves.
The models were deployed on an edge computing layer at each site, with central aggregation for cross-asset pattern detection. A pump showing the same vibration signature that preceded three previous bearing failures at other sites would trigger a maintenance order automatically.
Where it landed
The platform is now live across all 47 sites, processing 847 sensor streams in real time. In the first 12 months of operation, it predicted 11 bearing failures, 4 heat exchanger tube leaks, and 2 transformer insulation degradation events before they caused outage.
Unplanned outage hours dropped 61 percent. Calendar-based maintenance tasks were reduced by 38 percent, with the freed crew capacity redirected to condition-driven work orders generated by the twin.