Designing SCADA Alarm Callouts That Actually Wake Someone Up
Remote notification is a delivery channel, not an alarm system. Picking which alarms page out, escalation timers that match humans, and proving delivery.
Articles
Field-oriented references for HMI/SCADA systems, industrial communication, alarms, tags, historians, and project delivery.
Remote notification is a delivery channel, not an alarm system. Picking which alarms page out, escalation timers that match humans, and proving delivery.
Designing rate-of-rise and rate-of-fall alarms: window length, noise filtering, units, and the quality gating that stops them screaming on comms recovery.
Building lead/lag/standby pump rotation so duty sharing, standby failover and role swaps stay predictable — and visible to the operator at 3am.
During a flood a newest-first summary pushes the critical alarm off screen, and a filter left on erases it. Picking a default sort that holds.
Wiring horn silence to the acknowledge tag corrupts the event log from day one. Splitting silence, acknowledge, reset and shelve under ISA-18.2.
Building an alarm priority matrix that ranks by consequence and operator response time, with the EEMUA 191 targets that keep high priority rare.
Standing alarms are acknowledged but still active. Reviewing them against the ISA-18.2 stale-alarm metric before they become summary wallpaper.
Practical alarm design mistakes that create nuisance alarms, floods, operator confusion, and poor incident response.