What is an acceptable alarm rate per operator per hour?

ISA-18.2 recommends a target of no more than 6 alarms per operator per hour during normal operations, with a maximum manageable rate of approximately 10 alarms per 10-minute period during upset conditions. Alarm rates consistently above these thresholds indicate alarm management deficiencies that increase the risk of missed critical events.

How do you prioritize SCADA alarms?

SCADA alarms should be prioritized based on the consequence of inaction and the available response time. ISA-18.2 defines priority as a function of consequence severity (safety, environmental, financial) and urgency (how quickly the operator must respond). A well-designed priority scheme results in approximately 80% low, 15% medium, and 5% high priority alarms.

Can alarm rationalization be done remotely?

The implementation phase — updating alarm configurations in the Geo SCADA database — can be done remotely via secure VPN access. However, the rationalization review itself benefits from on-site participation by operators who understand the process and equipment. A hybrid approach with remote configuration and on-site review workshops is most effective.

SCADA Alarm Fatigue: How Unmanaged Alarm Floods Lead to Missed Critical Events

Quick Answer

SCADA alarm fatigue occurs when operators receive so many nuisance and low-priority alarms that they begin ignoring all alerts, including critical ones. ISA-18.2 recommends no more than 6 alarms per operator per hour. Alarm rationalization, proper Geo SCADA alarm configuration, and ongoing managed alarm tuning reduce alarm rates and restore operator trust in the alarm system.

What Alarm Fatigue Is and Why It's Dangerous

Alarm fatigue is not laziness. It's a well-documented human factors phenomenon where repeated exposure to frequent, low-consequence alerts desensitizes the operator to all alarms — including the rare but critical ones that require immediate action. Research across process industries consistently shows that when alarm rates exceed manageable thresholds, operator response times increase and critical alarms are missed.

In Geo SCADA environments, alarm fatigue manifests as operators routinely acknowledging alarm pages without reading them, disabling alarm notification services because their phone buzzes constantly, and configuring email rules to filter SCADA alerts to a subfolder they never check. The alarm system technically works — alarms are generated, logged, and displayed — but it has lost its purpose because humans have stopped responding to it.

The consequences are real. A high-priority alarm for a lift station pump failure arrives at the same time as 40 low-priority communication timeout alarms. The operator acknowledges the batch without distinguishing between them. The pump failure goes unaddressed for 6 hours, resulting in a sanitary sewer overflow and a TCEQ reportable event.

ISA-18.2 and IEC 62682 Alarm Management Standards

The ISA-18.2 standard (and its international counterpart IEC 62682) provides a comprehensive framework for alarm management in process industries. Key benchmarks relevant to SCADA operations include:

Average alarm rate: No more than 6 alarms per operator per hour during normal operations (ISA-18.2 target). Many Geo SCADA installations exceed 30 alarms per hour.
Peak alarm rate: No more than 10 alarms per operator in any 10-minute period. Alarm floods routinely generate hundreds in minutes.
Standing alarms: No more than 9 unacknowledged alarms at any time. Chronic "standing" alarms that are always active should be eliminated or suppressed.
Alarm priority distribution: Approximately 80% low, 15% medium, 5% high priority. Many systems have the inverse — 60% or more of alarms configured as high priority.

These benchmarks provide measurable targets for alarm rationalization programs. If your Geo SCADA system exceeds any of these thresholds, your operators are likely experiencing alarm fatigue.

Common Geo SCADA Alarm Configuration Mistakes

Default Templates Without Rationalization

When RTU or PLC device templates are imported into Geo SCADA, they often include hundreds of alarm points configured with default priorities and setpoints. These defaults are generic — they don't account for your specific process conditions, equipment capabilities, or operational procedures. Without rationalization, every point that crosses a default threshold generates an alarm, regardless of whether it actually requires operator action.

Chattering Alarms

A chattering alarm repeatedly activates and clears in rapid succession, typically because the measured value oscillates around the alarm setpoint. In Geo SCADA, this commonly occurs on analog points where the alarm deadband is not configured or is set too narrow. A single chattering alarm can generate dozens of alarm events per hour, each one demanding operator attention and database storage.

The fix is configuring appropriate alarm deadbands in the Geo SCADA point database. A deadband of 2-5% of the alarm setpoint eliminates most chattering without reducing alarm sensitivity for genuine process excursions.

Communication Alarms Treated as Process Alarms

Communication failures (RTU offline, channel timeout, poll failure) are infrastructure events, not process alarms. But in many Geo SCADA configurations, they are assigned the same priority as process alarms and appear in the same alarm summary. When a cellular carrier has a regional outage affecting 15 remote sites, the operator receives 45 communication alarms simultaneously — obscuring any genuine process alarms that may have occurred at the same time.

Communication alarms should be categorized separately, with their own priority scheme and display, allowing operators to quickly distinguish between infrastructure issues and process events.

Alarm Rationalization Process Overview

Alarm rationalization is the systematic review of every configured alarm to determine whether it is needed, whether its setpoint is appropriate, and whether its priority reflects the actual consequence of the alarmed condition. The process follows the ISA-18.2 lifecycle model:

Alarm philosophy document: Defines what constitutes an alarm in your operation, priority definitions, and target alarm rates.
Alarm identification: Inventory all configured alarms in the Geo SCADA database. Many systems have thousands of configured alarm points, many of which were never intentionally designed.
Rationalization review: For each alarm, determine: Is it needed? What is the consequence if the operator does not respond? What is the correct setpoint? What is the correct priority? What is the correct response time?
Implementation: Update Geo SCADA alarm configurations to reflect rationalization decisions. Suppress or remove alarms that don't meet the alarm philosophy criteria.
Monitoring: Track alarm rates over time and identify new alarm issues as they emerge.

How Managed Services Include Ongoing Alarm Tuning

Alarm rationalization is not a one-time project — it's an ongoing process. New equipment gets added, process conditions change, and operators identify new alarm requirements. Without ongoing attention, alarm performance degrades back toward pre-rationalization levels within 12-18 months.

Managed Geo SCADA services include continuous alarm performance monitoring as a standard deliverable. Monthly alarm reports track metrics against ISA-18.2 targets, identify new chattering alarms, flag standing alarms for review, and recommend configuration changes. This ongoing tuning keeps alarm rates within manageable thresholds and ensures that when an alarm activates, operators trust that it requires their attention.

If your SCADA alarm system has become background noise that operators routinely ignore, request an alarm audit from NFM Consulting to assess your current alarm rates against industry benchmarks and identify immediate improvement opportunities.