Pump management terminology

Abnormal State

During configuration, a state can be designated as abnormal. Underlying status or multistate records can be configured to inhibit Events and Alarms that occur when there are un-commanded state changes to abnormal states.

Block

A pump can indicate that it is blocked if the Line Blockage application detects that flow through has been blocked, or if it has a low capacity, in at least one direction in part of the Flow Network.

Commanded Change

Commanded changes are ones that are executed by you.

Flow Network

A network made to model the flow through a set of objects such as valves, pumps, tanks, meters, which are all connected by pipes.

Line Blockage

An application that queries the Flow Network in order to find and identify flow blockages, or potential blockages, so that pumps can be updated to show they are blocked, or open valves can be marked critical so they will not be closed, for example.

Logic Mode

The logic mode of the pump. This affects how the object is perceived by the Line Blockage/Flow Network application. An optional timeout can be configured in Advanced Database Editor (ADE) for this. If the optional timeout is configured, when the logic mode is changed to a state that is other than In Service, after the configured timeout period has elapsed, the device will revert back to In Service. There are four possible states:

• In Service: Default state. This indicates that the pump should be used as normal throughout any flow networks of which it is a member.

• Out of Logic: The Controller does not want line blockages calculated for this pump. The Line Blockage/Flow Network will ignore this pump for all operations. However, commands may still be sent to it.

• Out of Service Running: The Controller does not want line blockages calculated for the pump.The pump will always appear to the Flow Network application as being in the RUN state, and no commands may be sent to it.

• Out of Service Stopped: The Controller does not want line blockages calculated for the pump. The pump will always appear to the Flow Network application as being in the STOP state, and no commands may be sent to it.

monitorLMSObjects

A monitor process that watches the underlying points of all Pumps (and Valves) and updates their state on any change. These updates take place on both commanded and un-commanded changes.

Normal State

The default designation for Pump States. Pumps can be configured to inhibit events and alarms associated with un-commanded state changes to normal states.

Pump

The pump object.

The pump object is used as an interface into a multistate or status point. This allows the Administrator to create message sets that provide pump-specific information about the information received from the multistate or status point.

The pump object is multi-functional, used by the Flow Network and Line Blockage applications. For more information about pump setup, refer to the AVEVA Pipeline Operations for Liquids Administrator documentation.

Uncommanded Change

Uncommanded changes are ones that are not executed by you (i.e, the change is made at the field).