Understand data flow in valves

The following diagram summarizes data flow for a valve.

Valve objects are part of the lowest-level of data collection and interact directly with status or multistate points. Higher-level applications within AVEVA Pipeline Operations for Liquids then rely on valve objects rather than directly communicating with generic point types. The flow of data is shown in the following diagram:

The Omnicomm process collects data from field devices and stores this information within the default status and multistate tables. For more information, refer to Volume 1 of the RealTime Administrator documentation.

On RealTime servers that have AVEVA Pipeline Operations for Liquids functionality installed, the process monitorLMSObjects operates silently in the background and performs periodic operations to the valve table on points owned by the system. For example, the valve states are checked to ensure that they correspond with the values reported by their associated status and multistate states. All information related to valves is stored within the valve table, which is then later accessed by the higher-level AVEVA Pipeline Operations for Liquids applications.