Alarm-management standards — ISA-18.2 and EEMUA 191, the lifecycle frameworks that define good alarm philosophy, rationalisation and performance metrics.
Alarm Management & Escalation — in depth
Good alarm management follows recognised standards. ISA-18.2 and EEMUA 191 set out the alarm lifecycle — philosophy, identification, rationalisation, design, operation and audit — and the performance metrics (alarm rate, standing alarms, flood frequency) against which a system is judged, giving an objective basis for improvement.
What matters in practice
The alarm-management lifecycle standard.
Widely-used alarm-system guidance.
Philosophy to audit.
Alarm rate, floods, standing alarms.
| Metric | Target | Note |
|---|---|---|
| Alarms/operator | <~6/hour | Steady state |
| Standing alarms | Few | Managed |
| Flood frequency | Rare | <1% |
| Basis | ISA-18.2/EEMUA | Audit |
Continue across this series
A companion deep-dive in this series.
Read MoreA companion deep-dive in this series.
Read MoreA companion deep-dive in this series.
Read MoreThe overview page this topic expands on.
Read MoreThe wider hub for this subject area.
Read MoreReynolds & Bauhm designs and delivers alarm management & escalation solutions backed by process engineering and performance guarantees.
Fundamentals, design drivers and practical guidance
Alarm-management standards — ISA-18.2 and EEMUA 191, the lifecycle frameworks that define good alarm philosophy, rationalisation and performance metrics.
Reynolds & Bauhm rationalises alarm databases against a written philosophy, prioritises by consequence severity and operator response time, and tunes setpoints, deadbands and delays to suppress nuisance activations. We deliver the master alarm database, priority distribution, suppression logic and a monitoring regime so the system stays compliant through plant changes rather than degrading back into a flood.
Effective alarm management is governed by ANSI/ISA-18.2 and EEMUA 191, which define an alarm as an audible and/or visible means of indicating to the operator an equipment malfunction, process deviation or abnormal condition requiring a timely response. The discipline exists because poorly configured systems flood operators with nuisance and standing alarms, masking the genuinely safety-critical events during an upset — the failure mode implicated in several major process incidents.
A rationalised alarm system follows the alarm management lifecycle: philosophy, identification, rationalisation, detailed design, implementation, operation, maintenance, monitoring and management of change. Every alarm earns its place by being justified against the philosophy document, assigned a priority based on consequence and time-to-respond, and given a clear, unique operator action. Alarms that have no defined response are not alarms — they are removed or re-classed as alerts.
What our engineers assess on every scope of this type
| Parameter | Typical basis | Why it matters |
|---|---|---|
| Operator action | One clear, unique action | An alarm with no action is removed |
| Standard | ISA-18.2 / EEMUA 191 | Defines lifecycle, metrics and good practice |
| Steady-state rate | <1 alarm / 10 min / operator | Keeps the operator able to respond, not react |
| Post-upset flood | <10 alarms / 10 min | Limits the burst after a major trip |
| Priority split | ~80 / 15 / 5 (L/M/H) | A healthy distribution avoids priority inflation |
| Standing alarms | Near zero | Standing alarms desensitise operators |
Common questions on alarm management
Chattering and fleeting alarms are removed with deadbands, on/off time delays and hysteresis; duplicate and consequential alarms are suppressed with state-based logic; and standing/stale alarms are reviewed out. The aim is the EEMUA 191 target of fewer than one alarm per operator per ten minutes.
Rationalisation is the structured review where each candidate alarm is tested against the philosophy: does it indicate an abnormal condition, is there a unique operator action, and what is the consequence and time available to respond? Only alarms that pass are retained, each with a justified priority.
Through monitoring and management of change. Alarm rate, standing, stale and flood metrics are trended; any new or modified alarm passes through rationalisation before implementation, so the rationalised state does not erode as the plant evolves.
An alarm requires a timely operator response to a defined action; an alert is for information only. Conflating the two is a common cause of overload, so the rationalisation process re-classes action-less alarms as alerts or removes them.
Our expertise spans multiple industries with sector-specific water treatment solutions.
Explore closely-related topics, equipment and guides
Send your influent analysis and our engineers assess your process and recommend a tailored treatment solution — free, confidential and no obligation.
Select the regulatory standard for your country — it sets which parameters we need for a compliance-aware process assessment.
Required parameters for the chosen standard are flagged on the sample form. You can still submit a partial set and we will advise what else to test.
Your sample is stored against your company so we can track the project. Provide a company name or email as a minimum.