Peter Clarke
10 August 2026
Why Alarms Matter
In a process control room, alarms exist for one important reason: to tell the operator when intervention is needed to prevent an undesired event.
For example, reactor pressure may be rising beyond its normal operating range, potentially leading to a process trip or relief valve opening. Similarly, a waste tank may be approaching its safe operating level, creating a risk of overflow if action is not taken.
But an alarm is only useful if the operator can recognise it, understand its significance, and respond appropriately.
That means more alarms do not necessarily mean more safety.
If too many alarms are generated, operators can become overloaded with information. Important alarms may be missed among less significant events, or operators may simply begin to ignore alarms altogether. Alarm-related problems have contributed to a number of major industrial incidents, including the well-known Texaco refinery explosion at Milford Haven, UK, in 1994.
Effective alarm management therefore requires more than simply configuring alarm limits in the control system. It requires a systematic approach to deciding which conditions should generate alarms, how those alarms should be prioritised, and how the overall system should be monitored and maintained.
The Alarm Philosophy
This is where the Alarm Philosophy Document (APD) comes in.
An effective alarm system requires ongoing management. Even a well-designed system can gradually deteriorate as the plant changes, operating procedures evolve, and alarm settings are modified.
The Alarm Philosophy provides the framework for preventing this “alarm drift.”
It defines the principles and requirements governing the plant’s alarm system, including:
- What constitutes an alarm
- Criteria for determining when an alarm is required
- Alarm priorities
- Alarm settings and limits
- Operator response requirements
- Alarm shelving and suppression
- Alarm performance monitoring
- Key Performance Indicators (KPIs)
- Responsibilities for alarm management and maintenance
The commonly applied alarm management standards ISA 18.2 and IEC 62682 provide a framework for alarm management, but the Alarm Philosophy itself needs to reflect the specific plant and its operating environment.
And this is where a generic approach can create problems.
Don’t Just Buy a Generic APD
Writing an Alarm Philosophy Document from scratch is not a trivial exercise.
To address the requirements of ISA 18.2 and IEC 62682, an APD can easily run to dozens of pages and cover a large number of individual requirements.
So why not simply buy a generic APD?
Or, with today’s AI tools, why not ask AI to write one?
The problem is that an Alarm Philosophy needs to describe how alarms should actually work at your plant—not how they might work at some generic facility.
A document filled with options, assumptions and boilerplate text may look comprehensive. But if it does not reflect the plant’s actual processes, control systems, operating philosophy and risk profile, it is unlikely to be implemented effectively.
And an Alarm Philosophy that is not implemented is not providing much value.
The objective should therefore not be to produce the longest document or tick every compliance box.
The objective is to produce an Alarm Philosophy that operators, engineers and management can actually use.
The “Too Much Gas” Problem
Consider a plant handling flammable or toxic gases.
Such a facility may have a large number of fire and gas detectors. These alarms are clearly important: early detection of a gas release can give operators valuable time to take action, minimise exposure, and reduce the potential for fire or explosion.
It may therefore seem logical to assign these alarms the highest priority.
However, alarm management best practice generally recommends limiting the number of maximum-priority alarms to a small proportion of the overall alarm population—often around 5%.
This creates a practical problem.
If fire and gas alarms represent 30–40% of all configured alarms, simply applying a generic “5% critical alarm” rule may make the target impossible to achieve.
A generic Alarm Philosophy leaves the plant with a conflict between the KPI and the reality of the facility.
A plant-specific Alarm Philosophy should instead recognise the issue and define a workable approach.
Depending on the plant and its alarm architecture, possible solutions could include:
- Exclude fire and gas alarms from the process-alarm calculation when determining the percentage of critical process alarms.
- Measure the number of critical alarms generated rather than configured, which may provide a more meaningful indication of actual operator workload, although this requires analysis of historical alarm data.
- Introduce a dedicated “Loss Prevention” priority for fire and gas alarms rather than treating them in exactly the same way as process alarms.
- Use first-out grouping so that multiple detectors associated with the same event are treated as a single alarm when calculating alarm-priority statistics.
There is no single answer that is appropriate for every plant.
The important point is that the Alarm Philosophy needs to identify these issues and provide a practical solution for the facility in question.
From Compliance to Performance
This is one of the reasons alarm management should not be treated simply as a documentation exercise.
An APD should provide the foundation for an alarm management lifecycle in which alarm performance can be measured, reviewed and improved over time.
KPIs can help identify problems such as:
- Excessive alarm rates
- Alarm floods
- Excessive standing alarms
- Poor alarm prioritisation
- Repeated nuisance alarms
- Shelved or suppressed alarms
- Inappropriate alarm settings
The philosophy should define what good performance looks like, how it will be measured, and what happens when performance falls outside the agreed targets.
In other words, the APD should not sit on a shelf.
It should become part of the way the plant manages alarm performance.
We Can Help
Developing an effective Alarm Philosophy requires a balance between standards, engineering judgement and practical plant experience.
xSeriCon’s experienced alarm management specialists can support clients in developing or reviewing Alarm Philosophy Documents that are tailored to their specific facilities and operating requirements.
Our approach focuses on producing a document that is not only aligned with recognised alarm management practices, but is also practical, implementable and measurable.
If you are developing a new Alarm Philosophy, reviewing an existing APD, or struggling with alarm-management KPIs, talk to xSeriCon about how we can help.