Geo SCADA Alarm and Event Management — Configuration, Routing, and Best Practices

Quick Answer

Geo SCADA provides a comprehensive alarm and event management system. Alarms are configured on individual points with threshold limits, priorities, and categories. All alarm events are logged in the event journal with timestamps, and operators acknowledge alarms through the ViewX alarm summary or event journal display.

Geo SCADA Alarm Architecture Overview

The alarm system in Geo SCADA is tightly integrated with the point database. Every analog and digital point can have alarm conditions configured. When a point value crosses an alarm threshold, the server generates an alarm event, logs it to the event journal, updates the alarm summary, and optionally triggers notification routing. The entire alarm lifecycle — activation, acknowledgment, return to normal — is tracked and timestamped.

Alarm States

• Active, Unacknowledged — The alarm condition is present and no operator has acknowledged it. This is the most critical state requiring operator attention.
• Active, Acknowledged — The alarm condition is present but an operator has acknowledged it, indicating awareness of the situation.
• Returned to Normal, Unacknowledged — The alarm condition has cleared but the operator has not yet acknowledged it. The alarm remains flagged until acknowledged.
• Normal — The alarm is cleared and acknowledged. No operator action required.

Configuring Alarm Limits on Points

For analog points, alarm limits are configured in the Alarm tab:

• High High, High, Low, Low Low thresholds with individual setpoint values
• Deadband per threshold to prevent alarm chattering
• Time delay (on-delay) to filter transient conditions
• Priority assignment per threshold (Critical, High, Medium, Low, Diagnostic)

For digital points, configure which state (0 or 1) represents an alarm condition and assign the appropriate priority.

Alarm Priorities and Categories

Assign priorities consistently across the system to enable effective alarm management. Use ISA-18.2 priority guidelines:

• Critical — Immediate danger to personnel, equipment, or environment. Requires immediate operator response.
• High — Significant abnormal condition requiring prompt operator response (within minutes).
• Medium — Abnormal condition requiring operator awareness and response within a reasonable timeframe.
• Low — Informational or maintenance-related condition.

The Event Journal

The event journal is Geo SCADA's central audit trail. It records all alarm events, operator actions, system events, and communication status changes with timestamps and usernames. In ViewX, the event journal supports:

• Filtering by time range, priority, category, and source
• Exporting to CSV for analysis and reporting
• Searching for specific events by keyword
• Color-coded display by priority and state

Alarm Routing and Notification

Geo SCADA Expert includes built-in alarm routing that can send notifications when alarms trigger:

• Email — SMTP-based email notifications with configurable message templates and recipient lists
• SMS/Pager — Text message notifications via configured communication gateways
• Escalation — Configure escalation sequences so that if the primary operator does not acknowledge, the alarm routes to a supervisor or on-call engineer

Alarm Shelving and Suppression

Alarm shelving temporarily suspends alarm notifications for a point during maintenance or known abnormal conditions. Shelved alarms are logged but do not generate notifications. Always set a shelving duration to prevent alarms from being permanently suppressed. Track shelved alarms in the alarm summary to ensure they are unshelved after maintenance.

Alarm Summary Display in ViewX

The alarm summary provides a real-time view of all active alarms across the system. Operators use it to prioritize response, acknowledge alarms, and navigate to the associated mimic display or point properties for investigation. The summary supports sorting by priority, time, source, and state.

Best Practices: Alarm Rationalization

For oilfield and pipeline SCADA systems, alarm rationalization is critical to prevent alarm flooding:

• Set alarm limits based on process engineering requirements, not arbitrary values
• Use time delays to filter transient conditions (e.g., 5-second delay on pump status alarms to filter startup transients)
• Assign priorities based on consequence severity, not perceived importance
• Target a manageable alarm rate — ISA-18.2 recommends fewer than 6 alarms per operator per hour during normal operations
• Conduct regular alarm reviews to identify and address chronic nuisance alarms

ISA-18.2 Alignment Notes

Geo SCADA supports the key elements of ISA-18.2 alarm management including priority classification, alarm states, shelving/suppression, and event journaling. While Geo SCADA does not enforce ISA-18.2 compliance automatically, its alarm system provides the tools needed to implement a compliant alarm management program when combined with proper engineering practices and periodic alarm system audits.