This article is part of a series examining the most common pitfalls operators encounter when modernizing legacy SCADA systems in oil and gas pipeline operations.
When a pipeline operator plans a SCADA modernization, alarm management rarely receives the attention it deserves relative to the operational value it delivers. Hardware selection, platform capabilities, and interface design tend to dominate the planning conversation. Yet of all the work involved in a modernization project, the rationalization of the alarm system may offer the single highest return on the time invested.
The reason is straightforward. Alarms are the primary channel through which a SCADA system communicates with the people running the pipeline. When that channel is well designed, operators receive clear, actionable, appropriately prioritized information at the moment they need it. When it carries forward years of accumulated configuration without review, operators work harder than necessary to separate the signal from the noise. A modernization project is the ideal moment to capture the full value of a well-rationalized alarm system.
What Alarm Rationalization Actually Means
Alarm rationalization is a structured, documented process for reviewing every alarm in a system against defined criteria. For each alarm, the process establishes whether it is genuinely needed, what condition it represents, what action the operator should take in response, who owns it, and what priority it should carry relative to every other alarm in the system.
The international standard that defines this work is ANSI/ISA-18.2, formally titled Management of Alarm Systems for the Process Industries. ISA-18.2 establishes a lifecycle framework for designing, implementing, and continuously improving industrial alarm systems, and it has been adopted across the United States and increasingly worldwide as the anchor framework for end-to-end alarm management. Rationalization sits at the center of that lifecycle. It encompasses several significant activities, including alarm justification, documentation, prioritization, and classification. Each alarm is assessed against the alarm philosophy, a foundational document that defines the organization’s criteria for what qualifies as an alarm in the first place. Alarms that do not meet those criteria are candidates for removal. Alarms that remain are assigned a clear purpose, a defined operator response, and a priority that reflects the actual operational consequence of the condition they signal.
For pipeline operators specifically, API 1167 provides recommended practice focused directly on SCADA alarm management in pipeline operations, and it aligns fully with ISA-18.2. Internationally, IEC 62682 harmonizes these principles across regions, and EEMUA 191 remains a widely referenced guide, particularly across the United Kingdom and Europe. The essential point is that a structured, documented process is applied, with defined criteria and clear ownership of each alarm in the system.
Why Legacy Alarm Systems Accumulate Complexity
Alarm systems in long-running pipeline operations tend to grow over time. When a new piece of equipment is commissioned, alarms are added. When an incident occurs, alarms are sometimes added in response. When a process is modified, new alarm conditions are configured. What is far less common is the removal of alarms that have outlived their original purpose.
Over years of operation, this pattern produces alarm systems that carry hundreds or thousands of configured alarms, many of which were set at original commissioning and never formally reviewed since. Thresholds may reflect the conditions of a different operational era. Some alarms may duplicate others. Some may activate routinely during normal operations, having been configured with limits that no longer match how the pipeline actually runs.
Experienced operators develop considerable skill at working within these systems, building familiarity with which alarms require immediate attention and which have historically been lower priority. This operational knowledge is valuable, and it keeps pipelines running safely every day. At the same time, it represents an opportunity. A well-rationalized alarm system allows that same operator expertise to be applied to a clearer, more actionable stream of information, rather than to the ongoing task of filtering it.
The Value of Getting This Right
The benefits of a rigorous alarm rationalization are well documented across the process industries, and they are measurable.
Industry guidance establishes clear performance benchmarks. EEMUA 191 suggests that the alarm rate presented to an operator should not exceed an average of one alarm per ten minutes during steady-state operation, with a peak rate that remains manageable during upset conditions. These benchmarks give operators a concrete target against which to measure alarm system performance before and after rationalization.
The operational improvement can be substantial. In one documented case from a large process facility that operated with more than 6,000 configured alarms and operators receiving over 200 alarms per hour during normal operation, a structured ISA-18.2 rationalization reduced the active alarm count to fewer than 500 and brought the alarm rate below 10 per hour under normal conditions. High-priority alarms were clearly distinguished, and response time to critical events improved measurably. While every operation is different, the direction of the result is consistent: a rationalized system presents fewer, clearer, more actionable alarms, and operators respond to genuine conditions more quickly.
For a pipeline operator, that translates directly into operational value. Clearer alarms support faster, more confident operator decisions. A well-prioritized system ensures that the most consequential conditions stand out immediately. And a documented, well-governed alarm system supports regulatory compliance and provides the auditability that modern pipeline operations increasingly require.
What the Industry Has Learned About Alarm Management
The importance of effective alarm management is grounded in hard-won industry experience. Two of the most thoroughly documented process safety investigations in the sector both identified alarm and instrumentation performance among their contributing factors.
The 2005 BP Texas City refinery incident, investigated by the US Chemical Safety Board, remains one of the most studied process safety events in the industry. Among the many factors the CSB examined, the investigation found that a high level alarm on a distillation tower did not activate as intended, and that a tower level indication the operator relied upon had been calibrated using decades-old data for a different process liquid. The Texas City investigation is a complex case with organizational and cultural root causes that extended well beyond alarms, and it should not be reduced to a single factor. But the role that alarm and instrumentation clarity played in the sequence of events has made it a foundational reference point for the entire discipline.
The 1999 Olympic Pipe Line incident in Bellingham, Washington, investigated by the National Transportation Safety Board, similarly underscored how critical it is that operators have access to clear, reliable operational information at the moment they need it. In that case, the SCADA system became non-responsive at a critical time during pipeline operations, leaving controllers without the operational awareness the system was meant to provide.
These investigations helped shape the modern consensus, embodied in ISA-18.2 and its companion standards, that alarm systems are most effective when every alarm is justified, prioritized, and actionable. That consensus is precisely what a rationalization process is designed to deliver.
Why Modernization Is the Ideal Moment
A SCADA modernization presents a distinct opportunity to apply this work at the most advantageous point in a system’s life. During a modernization, the alarm configuration is already being handled as part of the migration to the new platform, which means the team is engaging directly with every alarm as a matter of course. Applying rationalization criteria at this stage, rather than transferring the existing configuration and revisiting it later, captures the full value of a modern platform’s alarm capabilities from the first day of operation.
Modern SCADA platforms offer sophisticated alarm functionality: state-based alarming, dynamic prioritization, deadbands and delay settings to reduce chattering, and detailed performance monitoring against ISA-18.2 key performance indicators. These capabilities reach their full potential when the alarm system feeding them has been rationalized. A modern platform configured with a well-rationalized alarm set delivers clear, actionable information. The same platform configured with a legacy alarm set carries forward the characteristics of the previous system onto new technology.
The most effective approach treats alarm rationalization as a core deliverable of the modernization project, scoped and budgeted from the beginning. ISA-18.2 recognizes that for existing systems, it is practical and economical to begin the lifecycle with monitoring and assessment, benchmarking current alarm performance to establish a clear baseline before rationalization begins. That baseline both guides the work and provides a measurable demonstration of the improvement it delivers.
Building Alarm Management Into the Project
Operators who capture the full value of alarm rationalization during modernization tend to follow a consistent path. They begin with an alarm philosophy document, whether developing one for the first time or updating an existing one, so that every decision is measured against clear, agreed criteria. They benchmark the current alarm system’s performance to establish a baseline. They engage operators directly in the process, drawing on the knowledge of the people who work with the alarms every day to inform decisions about priority, response, and relevance. They configure the new platform to reflect the rationalized alarm set. And they establish monitoring and management-of-change practices so that the alarm system remains well-governed long after go-live.
Alarm rationalization is detailed, methodical work. It requires engineering time, operator input, and disciplined documentation. It is also among the highest-value activities in a SCADA modernization, because it directly shapes the quality of the information operators rely on to run the pipeline safely and efficiently every day.
A modern SCADA platform is a significant investment. Rationalizing the alarm system as part of the modernization ensures that investment delivers its full potential where it matters most: in the clarity, confidence, and effectiveness of the people operating the pipeline.