Understand Flow Network alarms and events
- Last UpdatedApr 24, 2025
- 4 minute read
The following table details alarm examples. These alarms will only be created when a Flow Network is configured as Model Based Alarming. In Model Based Alarming, a blockage scenario results in a separate event being generated for each affected pump and a single alarm being generated for the affected Flow Network. This is different from Device Based Alarming where an alarm and an event are generated for each affected pump.
Note: When Model Based Alarming is selected, PubSub logs a shutdown alarm against the first device that is published if the alarm generated spans multiple Flow Networks and involves multiple devices.
For more information, refer to the RealTime Administrator documentation.
|
Alarm Text |
Description |
Default Severity |
|---|---|---|
|
Shutdown: Executed in station <station> due to line blockage. |
An alarm that is generated when one or more pumps is shut down without delay in a single station due to a line blockage. |
The default is set to Medium, but the severity can be configured. |
|
Shutdown: Executed in stations <upstream station>-><downstream station> due to line blockage. |
An alarm that is generated when one or more pumps is shut down without delay in multiple stations due to a line blockage. |
The default is set to Medium, but the severity can be configured. |
|
Shutdown: Delayed shutdown in station <station> in <delay> second(s) due to line blockage. |
An alarm that is generated when a delayed shutdown of one or more pumps is initiated in a single station due to a line blockage. |
The default is set to Medium, but the severity can be configured. |
|
Shutdown: Delayed shutdown in station <station> in <lower delay>–<upper delay> seconds due to line blockage. |
An alarm that is generated when a delayed shutdown of multiple pumps is initiated in a single station with varying delays due to a line blockage. |
The default is set to Medium, but the severity can be configured. |
|
Shutdown: Delayed shutdown in stations <upstream station>–><downstream station> in <delay> second(s) due to line blockage. |
An alarm that is generated when a delayed shutdown of multiple pumps is initiated in multiple stations due to a line blockage. |
The default is set to Medium, but the severity can be configured. |
|
Shutdown: Delayed shutdown in stations <upstream station>–><downstream station> in <lower delay>–<upper delay> seconds due to line blockage. |
An alarm that is generated when a delayed shutdown of multiple pumps is initiated in multiple stations with varying delays due to a line blockage. |
The default is set to Medium, but the severity can be configured. |
|
Line Blockage Cleared: Shutdown in station <station> canceled in Flow Network <flow network>. |
An alarm that is generated when an event results in the cancellation of one or more delayed shutdowns in a single station due to a line blockage within a Flow Network. |
The default is set to Low, but the severity can be configured. |
|
Line Blockage Cleared: Shutdown in stations <upstream station>–><downstream station> canceled in Flow Network <flow network>. |
An alarm that is generated when an event results in the cancellation of multiple delayed shutdowns in multiple stations within a Flow Network. |
The default is set to Low, but the severity can be configured. |
|
Line Blockage Cleared: Shutdown in stations <upstream station>–><downstream station> canceled in Flow Networks <flow networks>. |
An alarm that is generated when an event results in the cancellation of multiple shutdowns in multiple stations within multiple associated Flow Networks. |
The default is set to Low, but the severity can be configured. |
|
Shutdown: Executed in station <station> due to unexpected pump start (triggered by <devices in flow network(s)>). |
An alarm that is generated due to the shutdown of a pump without delay that unexpectedly started when blocked. |
The default is set to Medium, but the severity can be configured. |
|
Shutdown: Delayed shutdown in station <station> in <delay> second(s) due to unexpected pump start (triggered by <devices in flow network(s)>). |
An alarm that is generated due to the delayed shutdown of a pump that unexpectedly started when blocked. |
The default is set to Medium, but the severity can be configured. |
|
Device <table>.<name> is configured to be part of Flow Network <station> but has been removed. The system is unable to calculate the state of this device. Please reload your Flow Network configurations. |
An alarm that is generated when a record that is configured to be part of a Flow Network is removed. |
The default is set to Low, but the severity can be configured. |
|
Configuration error in Flow Network <station> has been resolved. Device <table>.<name> has been readded. |
A Return-to-Normal (RTN) alarm that is generated when a missing device has been recreated and is again linked to a Flow Network. |
The default is set to Low, but the severity can be configured. |
|
Configuration error in Flow Network <station> has been resolved. |
A Return-to-Normal alarm that is generated when the missing device error has resolved in a manner that did not involve the device being recreated, and the system could not identify the new device. |
The default is set to Low, but the severity can be configured. |
|
Flow Network plugin <plugin name> processing has exceeded <time interval> seconds. <plugin name> responses for all models will be delayed until this model completes processing. |
This alarm is generated when a Flow Network Plugin is taking longer than expected to complete. |
The default is set to Low, but the severity can be configured. |
|
New model uploaded. |
An event that is generated when loading a new model. |
The default is set to Low. |
|
Record deleted by [username] at [host name]. |
An event that is generated upon deletion of any associated device from the Flow Network. |
The default is set to Low. |