UK HQ Your time

Alarm Rationalisation

Alarm Management & Escalation — in depth

Most alarm systems drown operators in noise. Rationalisation reviews every configured alarm against agreed criteria — is it valid, actionable, correctly set? — deleting or re-tuning nuisance, duplicate, chattering and standing alarms, so the alarms that remain are few, meaningful and trusted in an upset.

Rationalisation

What matters in practice

Alarm Review

Every alarm tested against criteria.

Nuisance Removal

Chattering and fleeting alarms tuned out.

Duplicate Elimination

Redundant alarms removed.

Setpoint Tuning

Limits and deadbands corrected.

Rationalisation

IssueFixNote
NuisanceDeadband/delayTune
DuplicateRemoveConsolidate
StandingRe-setActionable
ChatteringHysteresisFilter

Related Topics

Continue across this series

Talk to our engineers

Reynolds & Bauhm designs and delivers alarm management & escalation solutions backed by process engineering and performance guarantees.

Alarm Rationalisation: Engineering Detail

Fundamentals, design drivers and practical guidance

Alarm rationalisation — reviewing every alarm against documented criteria to remove nuisance, duplicate and standing alarms so operators trust the system.

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.

Design & Specification Considerations

What our engineers assess on every scope of this type

  • Priority distribution targets (e.g. ~80% low / 15% medium / 5% high)
  • State-based and mode-based alarm suppression logic
  • Master alarm database with unique operator action per alarm
  • EEMUA 191 KPI monitoring: rate, standing, stale, flood
  • Management-of-change control so the database stays rationalised
  • Alarm philosophy document and rationalisation against it
ParameterTypical basisWhy it matters
Priority split~80 / 15 / 5 (L/M/H)A healthy distribution avoids priority inflation
Standing alarmsNear zeroStanding alarms desensitise operators
Operator actionOne clear, unique actionAn alarm with no action is removed
StandardISA-18.2 / EEMUA 191Defines lifecycle, metrics and good practice
Steady-state rate<1 alarm / 10 min / operatorKeeps the operator able to respond, not react
Post-upset flood<10 alarms / 10 minLimits the burst after a major trip

Frequently Asked Questions

Common questions on alarm management

What is alarm rationalisation?

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.

How is Alarm Rationalisation kept healthy over time?

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.

What is the difference between an alarm and an alert?

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.

What makes Alarm Rationalisation compliant with ISA-18.2?

Compliance comes from the alarm management lifecycle: a written philosophy, rationalisation of every alarm against it, priority by consequence and response time, and ongoing KPI monitoring. Alarm Rationalisation is documented in the master alarm database with a defined operator action, setpoint, deadband and priority.

Industries We Serve

Our expertise spans multiple industries with sector-specific water treatment solutions.

Related Pages

Explore closely-related topics, equipment and guides