Understand pump Line Blockage alarms
- Last UpdatedApr 24, 2025
- 4 minute read
The following table lists events and alarms that are generated by Line Blockage related to pumps. If a pump has a status or multistate configured as its telemetry source, alarms and events will be generated against this point rather than the pump record.
Notes: To generate alarms based on Flow Network integrity updates, an alarm or event must be the result of an integrity update and integrity updates for the Flow Network must be enabled. For more information, refer to the AVEVA Pipeline Operations for Liquids Administrator Guide.
Alarms generated by the Line Blockage application will continue to be displayed in the Alarm Summary until acknowledged by you, the Controller. Each alarm is assigned a unique category consisting of an alphanumeric prefix and a timestamp to ensure that it does not get replaced by any subsequent alarms of the same type. The categorization, prefix, and timestamp ensure you are aware of all shutdown instances in the Flow Network.
|
Alarm Text |
Description |
Default Severity |
|---|---|---|
|
Shutdown: <shutdown sequence name> will be executed in <delay> second(s) (triggered by <pump name> in Flow Network <flow network>). |
An alarm and event that is generated when an unexpected line blockage is detected. A delayed shutdown has been queued by Line Blockage and will be executed after the displayed number of seconds. Note: The Flow Network indicated in the message is the network the pump is on. |
The default is set to Medium, but the severity can be configured. |
|
Shutdown: <shutdown sequence name> will be executed in <delay> second(s)in Flow Network <flow network>. |
An alarm and event that is generated when an unexpected line blockage is detected that is result of an integrity update and Flow Network integrity updates are enabled. A delayed shutdown has been queued by Line Blockage and will be executed after the displayed number of seconds. Note: The Flow Network indicated in the message is the network the pump is on. |
The default is set to Medium, but the severity can be configured. |
|
Shutdown: <shutdown sequence name> executed (triggered by <pump name> in Flow Network <flow network>). |
An alarm and event that is generated when an unexpected line blockage is detected. A delay of zero was configured, and the shutdown sequence was executed immediately. Note: The Flow Network indicated in the message is the network the pump is on. |
The default is set to Medium, but the severity can be configured. |
|
Shutdown:<shutdown sequence name> executed blockage started in Flow Network <flow network>. |
An alarm and event that is generated when an unexpected line blockage is detected that is result of an integrity update and Flow Network integrity updates are enabled. A delay of zero was configured, and the shutdown sequence was executed immediately. Note: The Flow Network indicated in the message is the network the pump is on. |
The default is set to Medium, but the severity can be configured. |
|
Higher priority shutdown occurred. Action sequence <shutdown sequence name> with remaining delay of <seconds> canceled (triggered by <pump name>). |
A Line Blockage element attempted to queue a shutdown sequence that was already queued. The new queued shutdown had a shorter delay than the remaining delay on the existing shutdown, so the existing shutdown was canceled and replaced. |
The default is set to Medium, but the severity can be configured. |
|
Line Blockage Cleared: Action sequence <shutdown sequence name> canceled (originally triggered by blockage in Flow Network <flow network>). |
A line blockage was resolved before the delay on shutdown sequence expired, so the shutdown sequence was canceled. |
The default is set to Medium, but the severity can be configured. |
|
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. |
Action Sequence encountered an error when it tried to stop a pump as requested by a Point of Interest (POI) or Flow Network. |
The default is set to High, but the severity can be configured. |
|
An error occurred while attempting to execute an Action Sequence <action sequence name> to stop pump <pump name>. See the Log for more details. |
Action Sequence encountered an error when it tried to stop a pump. |
The default is set to High, but the severity can be configured. |
|
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. |
Action Sequence encountered an error when triggered by a POI or Flow Network. |
The default is set to High, but the severity can be configured. |
|
An error occurred while attempting to execute an Action Sequence <action sequence name>. See the Log for more details. |
Action Sequence encountered an error. |
The default is set to High, but the severity can be configured. |
|
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. |
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. |
The default is set to High, but the severity can be configured. |
|
An error occurred while attempting to change state for <"pump" or "valve"> <pump or valve name>. See the Log for more details. |
Line Blockage encountered an error when it tried to change the state of either a pump or valve. |
The default is set to High, but the severity can be configured. |