65,000 alarms → the 6 that matter.
A duty-shift view of how SCADA, EDM, CIM and AMI signals are reduced to a short queue of actions, every row tied to a permit, an owner, a cascade and an SAP work-order template.
Anchored on the Scarborough wastewater catchment. Numbers are illustrative for the demonstrator; the funnel rules and permits are real.
From signal to action
The funnel on the left shows the rule-set that gets us from 65k raw signals to a 6-row queue. The queue on the right is what an operator picks up at the start of the shift.
How 65,412 signals become 6 decisions
to see the rule
What an operator should act on this shift
Dossier · what the operator sees
Permit context, the downstream cascade if the item isn't acted on, the evidence sources currently in agreement, and a one-click work-order against the SAP S/4HANA template.
Peasholm Gap CSO
5th EDM spill in 14 days · 42-min discharge at 04:18
EPR/UB3412KL — Peasholm Gap CSO
≤4 spills/yr against the bathing-water permit window (1 May – 30 Sep).
Spill → North Bay shore CIM ammonia excursion → bathing-water non-compliance attributed to catchment → ODI exposure.
Dispatch jet-vac crew to clear Royal Albert Drive screen and raise emergency storage-uplift scope.
Mocked integration — production wiring would push to SAP S/4HANA via the EAM REST adapter and write back the work-order ID against the asset.
1,804 signals filtered with a reason
Every suppression has an auditable rule
- Pump cavitation chatter1,204Below the duration threshold AND no downstream consequence in the dependency graph.
- Routine CSO screen rotation events412Pattern matches scheduled maintenance window logged in SAP.
- AMI low-flow tail in low-density DMAs188No customer contacts, no quality excursion — suppressed under the night-flow ruleset.