The alarm summary is the operator's to-do list for abnormal conditions. It is the live, sortable list of active alarms that tells the operator what is wrong right now, how urgent it is, and what has and has not been dealt with. This guide explains what an alarm summary shows and how operators work it.
Alarm Summary in one line: An alarm summary is a SCADA display that lists all active and unacknowledged alarms in the operator's area, each with its timestamp, tag, description, priority, and state (active, acknowledged, returned-to-normal). Usually sortable by time or priority, the alarm summary is the operator's primary tool for seeing what is abnormal, deciding what to address first, and acknowledging alarms as they are handled.
Each row in an alarm summary is one alarm and carries the essentials: the time it occurred, the tag and a plain-language description (for example, Separator V-101 High Level), the priority, and the current state. Priority - often high, medium, low - tells the operator what to handle first, and color coding reinforces it. State shows the alarm's lifecycle: newly active and unacknowledged alarms stand out, acknowledged ones fade back, and alarms that have returned to normal drop off or move to a history view.
Operators sort the summary to work it. Sorting by priority surfaces the most serious conditions; sorting by time shows the sequence in which things went wrong, which is invaluable during a cascade. A good alarm summary lets the operator acknowledge one alarm or a whole page, silence the audible annunciation, and jump straight from an alarm row to the relevant mimic diagram or faceplate.
The alarm summary only works if the alarm system is well managed. Under standards like ISA-18.2 and EEMUA 191, the goal is a short, meaningful list - roughly one alarm every ten minutes under normal operation - so that every alarm in the summary genuinely demands an operator response. When alarms are poorly configured, the summary fills with nuisance and standing alarms, and operators start ignoring it, which defeats its purpose.
During an upset the summary can flood: dozens or hundreds of alarms appear in seconds, and the operator can no longer read it. This is why alarm rationalization, prioritization, and techniques such as shelving and first-out logic exist - to keep the alarm summary usable when it matters most. In oil and gas, a clean alarm summary across a field of wells and facilities is what lets one operator cover a wide area without missing the alarm that counts.
The alarm summary shows currently active and unacknowledged alarms - the operator's live work list. The event log is a chronological, permanent record of everything that happened: alarms coming and going, acknowledgements, operator actions, and system events. The summary is for acting now; the log is for reviewing later.
Industry guidance (ISA-18.2, EEMUA 191) targets an average of about one alarm every ten minutes per operator under normal operation, with no more than around ten standing alarms. Rates far above that mean the summary is overloaded and operators may miss important alarms.
Merobix generates alarms from the tags it reads and presents an active alarm summary in the browser with timestamp, priority, and acknowledgement state, so an operator covering multiple sites can see and act on abnormal conditions from one list.
Merobix reads your field devices into a cloud SCADA - the real thing behind these terms, live in days from any browser.