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

AVEVA Pipeline Operations for Liquids

Valve Management terminology

  • Last UpdatedApr 24, 2025
  • 2 minute read

Term

Description

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.

Alarm Inhibit

This field indicates whether or not alarms are inhibited for the valve.

Critical State

A valve within a flow network will be automatically designated as Critical by the Line Blockage application, depending on the Flow Network’s current topographical state. The conditions that designate a valve as Critical are configured on a valve-by-valve basis by an Administrator, but typically involve a state where the closure of the valve in question would result in the blockage of a pump.

Flow Network

A network that is created to model the flow through a set of valves, pumps, tanks, meters, etc., which are all connected by pipes.

Line Blockage

This application responds to valve closures, either Controller initiated or unexpected, to prevent accidental pumping into blocked line segments.

monitorLMSObjects

A monitoring process that watches the underlying points of all valves and updates their state on any change.

These updates occur when there is a commanded change by the Controller, or when there is a change from the field that is not the result of a Controller command.

Normal State

Any valve state which is not defined as an abnormal state.

The alarm and event information that is displayed in the Alarm and Event Summaries is configured by your Administrator. They have the ability to configure the alarm and event handling such that un-commanded changes occurring to normal states, and the un-commanded changes occurring to abnormal states, can be handled differently.

Valve

The valve object.

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

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