Articles
RSSAlarm Management – Rules For SCADA And KPIs
October 23, 2009
•Article: Alarm Management – Rules For SCADA And KPIs
By Control Microsystems Inc.
Too often operators and engineers that are managing critical infrastructure are continually chasing alarms that are generated by their HMI or SCADA software leaving little time for monitoring the control system and being proactive about the process. Let's take a look at the most common cause for this situation and provide some solutions for improvement.
These are alarms that trigger when no abnormal condition exists or when no operator action is required.
Get rid of these alarms. If it is important that the condition is logged for audit trail purposes then log to the event journal.
If alarms are not cleared within 24 hours then they are considered stale alarms. These clutter the alarm list display and distract the operator from new alarms that may come in. Remember it is usual that high priority alarms appear first in the alarm list then medium priority, etc. If a new medium priority alarm comes in it may appear low in the list when in reality it needs attention immediately.
Assuming that long term alarms are valid they could be ‘parked' or disabled so that they are removed from the active alarm list. Of course you should have the ability to view these ‘parked' alarms on separate lists and potentially have them automatically re-enabled after preset time.
Click Here To Download:•Article: Alarm Management – Rules For SCADA And KPIs
