Route System alarms to a third-party application

The System Alarm Routing feature allows third-party applications to intercept System alarms. When the filter conditions are met, the system publishes the required alarm information to a PubSub topic and re-routes the alarm to a third-party application. AVEVA Enterprise SCADA does not create any re-routed alarms.

Third-party applications subscribed to the System alarm notification PubSub topic can override the alarm, ignore it, delay the creation of the alarm, or select a different method by which to manage the alarm.

For details on how to implement the third-party application, refer to "System Alarm Routing" in the AVEVA Enterprise SCADA RealTime Developer documentation.

Before You Begin

Create an almSevOverride record, and configure the Main tab of the Row Details dialog box as described in AlmSevOverride Row Details: Main tab.

PubSub Topic

If a key is not specified, AVEVA Enterprise SCADA publishes all System alarms on the following PubSub topic:

<system name>.realtime.systemalarm.notification

• Where: <system_name> is the name of the system that generates the original alarm.

You can also configure a unique PubSub topic on which to publish the System alarm:

<system name>.realtime.systemalarm.notification.<topic>

• Where: <topic> is configured by the Administrator.

For further information on the PubSub system, refer to the AVEVA Enterprise SCADA Common Developer documentation.

To route System alarms to a third-party application

For information on routing System alarms to a third-party application, refer to AlmSevOverride Row Details: Routing tab.