Understand Flow Network alarms and events
- Last UpdatedApr 24, 2025
- 4 minute read
The following table details alarm text 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 the shutdown alarm against the first device published if the alarm generated spans multiple Flow Networks and involves multiple devices.
For more information on Message Sets, see Understand Flow Network message sets.
|
Alarm/Event |
Alarm/Event Message Configuration |
Alarm Severity Configuration |
Type |
|---|---|---|---|
|
Shutdown executed in station(s) <station list> due to a line blockage in Flow Network <flow network>. |
FNET_PPL_LNBLCK_SHUTDOWN_EXECUTED An alarm that is generated when one or more pumps is shut down without delay in one or multiple stations within the same Flow Network. Note: The Flow Network is the parent of the station(s). Inhibit type: Shutdown |
Base Message: Shutdown (message set element 1) |
Alarm & Event |
|
Delayed shutdown in station(s) <station list> in <delay> second(s) due to a line blockage in Flow Network <flow network>. |
FNET_PPL_LNBLCK_SHUTDOWN_QUEUED An alarm that is generated when a delayed shutdown of one or more pumps is initiated in one or multiple stations in the same Flow Network due to a line blockage. Notes: The Flow Network is the parent of the station(s). If the pumps have different shutdown delays, then the <delay> parameter will look like <lowerDelay>-<upperDelay> Inhibit type: Shutdown |
Base Message: |
Alarm & Event |
|
Line Blockage Cleared: Shutdown in station(s) <station list> canceled in Flow Network(s) <flow network list>. |
FNET_PPL_LNBLCK_SHUTDOWN_CANCELED An alarm that is generated when an event results in the cancellation of one or more delayed shutdowns in one or multiple stations due to a line blockage within one or multiple Flow Networks. Inhibit type: Cancellation |
Base Message: |
Alarm & Event |
|
Shutdown executed in station(s) <station list> due to unexpected pump start (triggered by <flow network (pump list)>). |
FNET_PPL_LNBLCK_UNEXPECTED_SHUTDOWN_EXECUTED This alarm is generated due to the sudden shutdown of a pump that unexpectedly started when blocked. Inhibit type: Shutdown |
Base Message: |
Alarm & Event |
|
Delayed shutdown in station(s) <station list> in <delay> second(s) due to unexpected pump start (triggered by <flow network (pump list)>). |
FNET_PPL_LNBLCK_UNEXPECTED_SHUTDOWN_QUEUED This alarm is generated due to the sudden shutdown of a pump that unexpectedly started when blocked. Inhibit type: Shutdown |
Base Message: |
Alarm & Event |
|
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. |
FNET_CONFIG_ERROR_MISSING_DEVICE This alarm is generated when a record that is configured to be part of a Flow Network is removed. For example, the device record for a valve or a pump that exists in a drawing in AVEVA Process Simulation (APS) has been removed. To resolve this alarm, the removed device should be recreated, or the drawing should be updated to exclude the device and the Flow Network should be re-uploaded to the RealTime database. Inhibit type: Unihibitable |
FNET_CONFIG_ERROR_MISSING_DEVICE |
Alarm & Event |
|
Configuration error in Flow Network <station> has been resolved. Device <table>.<name> has been re-added. |
FNET_CONFIG_ERROR_DEVICE_RESOLVED This Return-to-Normal (RTN) alarm is generated when a missing device has been recreated and is again linked to a Flow Network. |
FNET_CONFIG_ERROR_DEVICE_RESOLVED |
Alarm & Event |
|
Configuration error in Flow Network <station> has been resolved. |
FNET_CONFIG_ERROR_RESOLVED This Return-to-Normal alarm 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. |
FNET_CONFIG_ERROR_RESOLVED |
Alarm & Event |
|
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. |
FNET_PLUGIN_TAKING_LONG_TIME_TO_PROCESS This alarm is generated when a Flow Network plugin is taking longer than expected to complete. |
FNET_PLUGIN_TAKING_LONG_TIME_TO_PROCESS |
Alarm & Event |
|
Record deleted by <username> at <host name>. |
FNW_RECORD_DELETE |
N/A |
Event |
|
Modified logic state from '<previous state>' to '{[current state}'. |
VALVE_CONTROL_STATE_MODIFIED |
N/A |
Event |
|
An error occurred while attempting to execute an Action Sequence <action sequence name> to stop pump <pump name> as requested by <"POI" or "flow network"> <POI or fnet name> See the Log for more details. |
FNET_PUMP_VALVE_ACTIONSEQ_STOP_ERROR_1 Action Sequence encountered an error when it tried to stop a pump as requested by a Point of Interest (POI) or Flow Network. |
FNET_PUMP_VALVE_UPDATE_SERVICE_ACTION_SEQUENCE_STOP_ERROR_1 |
Alarm & Event |
|
An error occurred while attempting to execute an Action Sequence <action sequence name> to stop pump <pump name>. See the Log for more details. |
FNET_PUMP_VALVE_ACTIONSEQ_STOP_ERROR_2 Action Sequence encountered an error when it tried to stop a pump. |
FNET_PUMP_VALVE_UPDATE_SERVICE_ACTION_SEQUENCE_STOP_ERROR_2 |
Alarm & Event |
|
An error occurred while attempting to execute an Action Sequence <action sequence name> as requested by <"POI" or "flow network"> <POI or fnet name>. See the Log for more details. |
FNET_PUMP_VALVE_ACTIONSEQ_STOP_ERROR_3 Action Sequence encountered an error when triggered by a POI or Flow Network. |
FNET_PUMP_VALVE_UPDATE_SERVICE_ACTION_SEQUENCE_STOP_ERROR_3 |
Alarm & Event |
|
An error occurred while attempting to execute an Action Sequence <action sequence name>. See the Log for more details. |
FNET_PUMP_VALVE_ACTIONSEQ_STOP_ERROR_4 Action Sequence encountered an error. |
FNET_PUMP_VALVE_UPDATE_SERVICE_ACTION_SEQUENCE_STOP_ERROR_4 |
Alarm & Event |
|
An error occurred while attempting to change state for <"pump" or "valve"> <pump or valve name> as requested by <"POI" or "flow network"> <POI or fnet name>. See the Log for more details. |
FNET_PUMP_VALVE_STATE_CHANGE_ERROR_1 Line Blockage encountered an error when it tried to change the state of either a pump or valve as requested by a POI or Flow Network. |
FNET_PUMP_VALVE_UPDATE_SERVICE_STATE_CHANGE_ERROR_1 |
Alarm & Event |
|
An error occurred while attempting to change state for <"pump" or "valve"> <pump or valve name>. See the Log for more details. |
FNET_PUMP_VALVE_STATE_CHANGE_ERROR_2 Line Blockage encountered an error when it tried to change the state of either a pump or valve. |
FNET_PUMP_VALVE_UPDATE_SERVICE_STATE_CHANGE_ERROR_2 |
Alarm & Event |