Alarming

Don't be Alarmed
In the beginning was a sound and the sound was annoying - but what does it mean and what do I do about it (apart from acknowledge/silence it).
  1. Does it indicate a genuine problem
  2. Does it require operator attention/intervention
  3. Can this be done safely & quickly enough
If so then....
  • How important (urgent) is it
  • When should it activate
  • Is it duplicated by another alarm
Remember:
  1. Identification
    • List your alarms (what you have and also what you need)
  2. Rationalization
    • Do they identify a problem, could/should an operator respond, are they duplicated ?
  3. Prioritization
    • How important (urgent) are they based on consequence & time.
  4. Optimization
    • What is the setting based on process dynamics
  5. Specification
    • Clearly, concisely and consistently define requirements
  6. Implementation
    • Configure and commission the alarms/system.
  7. Operation
    • Ensure Operators are trained how to respond
  8. Validation
    • Ensure alarms are tested and Operators rehearse
  9. Modification
    • Robust management of change
  10. Evaluation
    • Regular audits to ensure they are still active and appropriate
If Everybody is Somebody then Nobody is Anybody !

So to summarize:
  • ALARM = Problem + (Immediate) Action
  • ALERT = No (immediate) Problem + (Planned) Action
  • EVENT = No Problem + No Action
How hard can it be ?

No comments:

Post a Comment