How to Send SCADA Alarm Notifications with SeQent

SeQent uses a modular gateway architecture to connect to SCADA and automation platforms. Each gateway is purpose-built for a specific platform, providing native integration rather than generic middleware or custom scripting.

1. Gateway Architecture

Every SeQent gateway operates as an independent Windows service that connects to a SCADA platform, extracts alarm and event data, and forwards it to the FPAM server for processing. Gateways are lightweight and can run on the same server as FPAM or on a separate machine closer to the SCADA infrastructure.

This architecture means you can support multiple SCADA platforms simultaneously. A plant running Rockwell in one area and AVEVA in another can use both gateways feeding into a single FPAM server with unified alarm management.

2. Rockwell Automation Integration

Supported platforms: FactoryTalk View SE, PlantPAx, FactoryTalk Optix

The Gateway for FactoryTalk connects to Rockwell’s Alarm and Event engine. It receives alarm data including priority, description, area, and tag information. Configuration involves specifying the FactoryTalk server address and the alarm areas to monitor. SeQent has been a Rockwell Automation Technology Partner for over 15 years.

When to use: Any plant running Rockwell Automation HMI/SCADA where alarm notification to radios, mobile, or Andon displays is needed.

3. Velotic Proficy Integration

Supported platforms: iFIX, CIMPLICITY

SeQent provides the technology behind AlarmCast, the native alarm notification module within Velotic’s Proficy iFIX and CIMPLICITY platforms. The Gateway for iFIX and Gateway for CIMPLICITY monitor the native alarm queues and extract alarm data including priority, description, node information, and source details.

When to use: Any plant running Velotic Proficy SCADA. If you are already using AlarmCast, you are already running SeQent’s alarm engine.

4. AVEVA Integration

Supported platforms: System Platform, InTouch HMI, PI System

Native gateways for each AVEVA platform provide direct access to runtime alarm and event streams. Discrete messaging allows alarms to be routed to hierarchies of responsible parties with automatic escalation. SeQent offers native integration between AVEVA and Motorola Solutions.

When to use: Any plant running AVEVA automation where alarm notification, radio integration, or Andon display management is required.

5. OPC Integration (Universal)

Supported standards: OPC DA, OPC HDA, OPC UA

The OPC Gateway provides a universal connection path for any automation platform that supports OPC, including Siemens, Schneider Electric, ABB, Honeywell, and others. The gateway subscribes to OPC tags in read-only mode, evaluates data against configured exception conditions, and generates alarms when conditions are met.

Compatible OPC servers: Kepware, RSLinx, CODESYS, and any OPC-compliant server.

When to use: Any SCADA/DCS/PLC platform without a dedicated SeQent gateway. Also useful in multi-vendor plants where you need a single gateway to cover multiple systems via their OPC servers.

6. Integration Process

Regardless of the SCADA platform, the integration process follows the same pattern:

1. Install the appropriate gateway on the SeQent server or a machine with network access to the SCADA system.
2. Configure the gateway with the SCADA server address and connection credentials.
3. Verify the gateway connects and can browse available alarm sources or tags.
4. Map alarm fields to notification message templates.
5. Configure alarm routing, escalation, and notification endpoints.
6. Test end-to-end alarm delivery.

7. Multi-SCADA Environments

Plants running multiple SCADA platforms install one gateway per platform, all feeding into the same FPAM server. This provides a unified alarm management layer across all systems, with consistent routing, escalation, and notification regardless of the alarm source.