Overview
ISA-18.2, published internationally as IEC 62682, defines how to manage the full lifecycle of an alarm system: the guiding philosophy, the rationalisation of each alarm, and the design, operation, and ongoing performance monitoring that follow. Its aim is an alarm system operators can trust, where every alarm is meaningful, prioritised, and actionable, and the alarm flood that overwhelms operators during an upset is engineered out. Tenders for plants and critical facilities frequently reference ISA-18.2 because a poorly managed alarm system is a recognised safety risk. ControlBird supplies the technical building blocks an alarm system needs to operate to these principles.
Key requirements
- Rationalised alarms
- Every alarm has a defined condition, priority, and intended operator response, and the system is designed to avoid nuisance and chattering alarms that erode operator trust.
- Prioritisation
- Alarms are classified by urgency so operators address the most important conditions first, rather than treating every alarm the same.
- A defined state model
- Alarms follow a documented lifecycle, such as normal, active, acknowledged, and return-to-normal, with acknowledgement kept distinct from the underlying condition clearing.
- Controlled suppression and recording
- Suppression methods such as shelving are available but bounded and logged, and every alarm event is recorded so the alarm system can be monitored and audited over time.
How ControlBird aligns
- Rationalised, low-noise alarm conditions
- You define the condition and priority for each alarm, and on and off delays, deadband, and hysteresis suppress chattering and transient trips. This supports the rationalised, nuisance-free alarms the standard calls for instead of a stream of fleeting alerts.
- Priority levels you define
- Severities are configurable, each with its own rank, colour, icon, flash rate, and sound, so alarms are presented and sorted by urgency. Active, unacknowledged alarms are colour-coded, can flash, and can sound an alert until an operator handles them.
- A defined lifecycle with separate acknowledgement
- Alarms move through a clear state model spanning pending, active, latched, and cleared. Acknowledging records that an operator has seen an alarm without resolving the condition, and a latched alarm stays present until a manual reset, matching the acknowledgement and return-to-normal behaviour the standard describes.
- Controlled shelving and a complete alarm record
- Operators can shelve an alarm for a bounded time with a recorded reason and user, and it returns automatically when the period ends if still active. Every alarm event (activation, acknowledgement, shelving, clearing, and more) is written to the historian with its timestamp and operator and is searchable, giving the records the standard expects for monitoring and audit.
- What the standard expects beyond the tooling
- ISA-18.2 is a full lifecycle management standard that also covers the alarm philosophy document, the rationalisation process, management of change, and periodic performance audits. Those are organisational practices owned by the operator. ControlBird supplies the building blocks for the design, operation, and monitoring stages; the surrounding management process sits with your team. Email or text notification is delivered through the platform’s automation and email integration rather than from the alarm system directly.
Need this for a tender?
We can provide deployment-specific detail and supporting documentation for procurement and security reviews.