@Robert - Could a “device” be a hierarchy of alarm nodes and children? In that way you could effect a whole section of a plant, a line, an individual device, single alarm, etc.
[quote=“Robert”]The ability to suppress all alarms for a device.
This would allow users to take something out of service, fix it, test it, etc without driving operators nuts with alarms.
Ability to temporary suppress individual alarms. eg: faulty sensor.[/quote]
@Henry - I imagine that could work like how gmail does “tags” on your emails. Once you have your alarms grouped/tagged, what does that do? Anything besides who gets notified and how the alarm is displayed on the screen?
For fun, I want to think of ways that all these could be supported. The tricky part will be keeping it simple. I’m thinking right off the bat that there will need to be some sort of alarm hierarchy that is separate from the conditions that set it off (tag mapping or whatever). It also seems like there will need to be some sort of rules engine for all the elevating/re-sending, logging, etc.