What goes wrong
| Class | What it looks like |
|---|---|
| No action defined | What it looks likeThe plan says “notify the engineer” but does not name the engineer or state what they must do. |
| Nobody there | What it looks likeThe alarm goes to a shared inbox that no one checks at night; the person on the call list has left. |
| Alarm fatigue | What it looks likeAlarms are raised so often without cause that people stop responding. |
| No time | What it looks likeThe trigger is set so close to the limit that the action cannot be completed. |
| Silent automation | What it looks likeAn automated pump fails to start and no one is notified. |
| Person-dependent | What it looks likeThe response works only while one person is employed. |
| No review | What it looks likeThe same failure recurs because nothing was changed after the last one. |
| Response by discovery | What it looks likeThe first response is a person seeing the problem in the field. |
Problems and services
| Problem | Service |
|---|---|
| An alarm that reached the wrong person, or too late | ServiceMonitoring system review |
| Alarms ignored, misdirected or unrecorded across the network | ServiceMonitoring system review |
| A response plan that has never been run | ServiceResponse exercises |
| A release, an exceedance or a missed alarm to explain | ServiceMonitoring system review |