Please ensure Javascript is enabled for purposes of website accessibility
Powered by Zoomin Software. For more details please contactZoomin

AVEVA Enterprise SCADA

AlmSevOverride Row Details: Routing tab

  • Last UpdatedApr 24, 2025
  • 2 minute read

Use the Routing tab to configure the System Alarm Routing feature.

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.

When the system re-routes the alarm, it also generates an event. On the Operational Activities Summary window, the Inhibit field for this event displays the text Re-routed. The system generates the event regardless of whether or not the re-routed system alarm is handled by a third-party application.

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

Refer to the table below for field descriptions and instructions on how to configure the editable fields.

Item

Description

Publish System Alarm

Select to enable the System Alarm Routing feature.

Topic For Publishing System Alarm

If you leave this field blank, 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 the name of the unique PubSub topic.

    This will be a single word key name. The only valid characters are letters and numbers.