The short answer
Alarm Indication on the HMI
Alarm indication is the set of visual and audible cues that tell the operator an alarm exists, its priority, and its acknowledgment state. ISA-101 practice reserves a small set of colors for alarms and uses them nowhere else, pairs each with a shape or a symbol so priority is not conveyed by color alone, blinks only unacknowledged alarms, and shows alarms both at the point on the display where the problem is and in a banner and summary that are visible from every screen. The indication is driven by the alarm state from the controller and ends only when the alarm is acknowledged and the condition clears.
Key points
- Alarm colors are reserved. Nothing else on the HMI uses them.
- Priority is shown by color and by shape or symbol, so a colorblind operator sees the same thing.
- Blink means unacknowledged. Steady means acknowledged and still active. Gone means cleared.
- The alarm is indicated where the problem is on the display, in the banner, and in the summary.
- One click from the indication to the device and to the alarm summary filtered to it.
What the indication must do
The operator has to notice that an alarm exists, know how urgent it is, find where it is, and know whether they have already seen it. Those four jobs are done by different cues, and an indication that does one of them at the expense of the others fails. A display in which everything abnormal is bright red gets the first job done and none of the others; a display in which an alarm is a small gray line in a list gets the fourth done and not the first.
ISA-101 sets out the presentation rules and ISA-18.2 sets out the alarm states and the transitions the operator drives. Together they produce a consistent indication scheme that a utility can adopt as-is.
Color and shape
| Priority | Color | Shape or symbol | Sound |
|---|---|---|---|
| Critical (where used) | Red | Filled square or a distinct symbol, priority number 1 | Distinct continuous tone until acknowledged |
| High | Red | Filled square, priority number 1 or 2 | Distinct tone |
| Medium | Yellow or amber | Filled triangle, priority number 2 or 3 | A different tone, or a chime |
| Low | Blue or magenta | Filled circle, priority number 3 or 4 | None, or a soft chime |
| Diagnostic, not an alarm | Gray or the muted display palette | Small symbol | None |
The exact colors are chosen by the site and recorded in the HMI style guide; what matters is that the same color always means the same priority, that the colors appear nowhere else on the displays, and that a shape and a number accompany each so that the priority is readable without the color. Red for a running pump, yellow for a piping line, and green for anything at all are how alarm colors lose their meaning.
States and blink
ISA-18.2 defines the alarm states the indication has to show. The operator needs to distinguish a new alarm from one they have already acknowledged, and an alarm that has cleared but was never acknowledged from one that is gone.
| State | Condition | Acknowledged | Indication |
|---|---|---|---|
| Normal | Clear | Not applicable | No indication |
| Unacknowledged alarm | Active | No | Priority color and symbol, blinking; audible |
| Acknowledged alarm | Active | Yes | Priority color and symbol, steady; audible silenced |
| Return to normal, unacknowledged | Clear | No | Symbol in outline or with a distinct marker, highlighted in the summary, until acknowledged |
| Shelved | Any | Any | Removed from the active list; shown in the shelved list with a timer |
| Suppressed by design | Any | Any | Not annunciated; shown in the suppressed list with the reason |
| Out of service | Any | Any | Not annunciated; shown on the device with a clear out-of-service marker |
Blinking is reserved for the unacknowledged state. A blinking indication that continues after acknowledgment, or a steady one for a new alarm, breaks the meaning. Blink rate is moderate, around one cycle per second, and nothing else on the display blinks.
Where the alarm appears
- On the process display
- At the device or the value that is in alarm: the symbol beside the number, the device outline, or a marker at the point on the display. The operator sees where the problem is without reading text.
- In the alarm banner
- A strip visible on every display, showing the most recent or the highest priority unacknowledged alarms, with priority color, symbol, time, tag, and message. Clicking an entry navigates to the display that contains the device.
- In the alarm summary
- The full list, sorted by priority then time, filterable by area and priority, with acknowledge controls. The banner leads to the summary; the summary leads to the device.
- On the navigation
- An indicator on the menu or the navigation buttons for each area, showing the highest priority active alarm in that area, so an operator on the water plant display knows the collection system has a high alarm.
- Audibly
- A tone per priority, silenced by acknowledgment or by a silence button that does not acknowledge, re-sounding for each new alarm.
Acknowledgment and navigation
Acknowledgment says an operator has seen the alarm. It is done from the summary, from the banner, or from the device faceplate, and it is logged with the user and the time. Acknowledging clears the blink and silences the tone; it does not remove the alarm, which stays indicated until the condition clears. Acknowledge-all is a function to be cautious with: in a flood it is how the one alarm that mattered is acknowledged unread, and many sites restrict it or require a confirmation. From any indication, one click reaches the device faceplate and one click reaches the summary filtered to the device or area, so that acting on an alarm never requires knowing where to look.
Testing the indication
- Drive an alarm of each priority and confirm the color, the symbol, the blink, the tone, the banner entry, the summary entry, and the display marker.
- Acknowledge each and confirm the blink stops, the tone stops, and the indication remains until the condition clears.
- Clear a condition without acknowledging and confirm the return-to-normal state is shown until acknowledged.
- View the displays in grayscale, or with a colorblindness simulator, and confirm priority is still readable.
- Stand at the back of the control room with the display at normal brightness and confirm a high alarm is visible.
- Confirm nothing but alarms uses the alarm colors, and nothing but unacknowledged alarms blinks.
Frequently asked questions
- Why not use green for normal and red for alarm?
- Because then red and green are everywhere, and an alarm is one red thing among many. Normal is shown in the muted display palette so that the alarm colors stand out. Green, in particular, is avoided as a status color on high-performance displays because it competes with the alarm palette and because red-green is the most common form of colorblindness.
- Should the alarm banner be on every screen?
- Yes. An operator on any display must see that a new alarm exists and its priority. The banner is small, a few lines, and it is the same on every display. The summary is the full list on its own display.
- What about alarms on remote client screens and phones?
- The same states and the same priority scheme, with whatever the device can render. A phone notification carries the priority in words and the message; the acknowledgment from the phone is logged like any other, if the site permits it.
- How do I show a device that is out of service?
- With a clear marker on the device symbol and on its faceplate, a distinct entry in the out-of-service list, and its alarms suppressed by that state. The marker must be obvious enough that an operator does not expect the device to respond, and the list must be reviewed so devices do not stay out of service by neglect.
Related topics
- ISA-101: Human Machine InterfacesWhat the ISA-101 standard for human machine interfaces covers, its lifecycle from philosophy to maintenance, the display hierarchy, and what adopting it changes on a project.
- ISA-18.2 Alarm ManagementThe lifecycle standard for alarm systems, the rate targets that define a workable system, and why alarm rationalization is the step nobody wants to fund.
- Alarm PriorityHow to assign alarm priorities that operators trust: a consequence-and-time matrix, three or four levels, the target distribution from ISA-18.2 and EEMUA 191, and the mistakes that make every alarm high.
- High Performance HMI DesignGrey backgrounds, reserved color, and displays designed to make abnormal conditions obvious rather than to look impressive in a demo.
- Alarm FloodsWhat an alarm flood is, why it happens at exactly the wrong moment, the ISA-18.2 rate targets, and the design measures that keep a power failure or a communication loss from burying the one alarm that matters.
- HMI FaceplatesThe pop-up that controls one device: what a pump, valve, or loop faceplate must show, the mode and command layout, interlock and permissive display, security by role, and building faceplates from a standard object so every device behaves the same.
Direct contact
Have a controls question?
Reach Eric Sullivan directly about anything on this site, a controls or automation topic, or one of his personal projects.