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

AVEVA Pipeline Operations for Liquids

TABLE OF CONTENTS

Understand Batch Tracking configuration

Save PDF
Save selected topicSave selected topic and subtopicsSave all topics
Share
Share to emailCopy topic URL
  • Last UpdatedApr 24, 2025
  • 3 minute read

Because of the amount of data used to define and operate a pipeline and the complexity of the data relationships, many RealTime database (RTDB) tables, accessed in the Advanced Database Editor (ADE), are used in Batch Tracking. The primary table is the pipeline table. Other records can have a child relationship to the pipeline.

Note: When we refer to "pipeline," this term is used to indicate both the table record and the conceptual entity defined by the pipeline record and its child records.

For some tables, the records are defined by you as part of the pipeline configuration. For others, the records are created and deleted as part of operations.

It is possible for you to configure customized rounding precisions for Volume, Temperature, Density, and Pressure. These customized rounding precisions dictate how the input and output values are presented.

The precisions themselves are configured in the unitprofile table. For more information, see Work with Unit Profiles.

Refer to the table below for a list of tables that have a child relationship with the parent pipeline.

CTable

Purpose

Defined by Administrator

pipe_segment

Define physical attributes of the pipe in the pipeline system.

Yes

node

Represents points of note along the pipeline such as junctions and stations.

Yes

connectivity

Defines how the pipe_segments and nodes connect.

Yes

detect

Devices (represented by a status or multistate record) that are used to detect a batch interface that may exist on the pipeline. Records in this table link the device to the pipeline location.

Yes

adetect

Devices (represented by a status or multistate record) that are used to detect a pig or other type of anomaly that may exist on the pipeline. Records in this table link the device to the pipeline location.

Yes

section

Used to group together contiguous pipe_segments.

Yes

batch

Contiguous fluid of the same product and other attributes may represent a batch. A batch record identifies the batch and defines the product and other attributes.

No

fragment

Used to locate a portion of a batch in a single pipe_segment.

No

anomaly

Defines a point of interest that moves through the pipeline with the fluid. This may be a pig or may be an anomaly in the batch.

No

eta

Contains calculated estimated time of arrival information on batches and anomalies.

No

In addition, there are other tables that do not have a child relationship to the pipeline. These are configured and define attributes that are common to all pipelines.

The following table details the tables without a child relationship to the pipeline.

Table

Purpose

Defined by Administrator

anmtype

Defines the types of anomalies that can be used.

Yes

Consider the relationship of the tables to the physical pipeline as shown in the figure below.

Lines mapping out the pipeline are represented by pipe_segment table records.

Junctions in the diagram are represented by Node table records.

Connections between two pipe_segments, or a pipe_segment and a node, are handled by connectivity table records.

The tanks in the diagram represent terminals. Flow into and out of the pipeline at the terminals is handled in the Metering-Ticketing application. The pipe_segment records provide a reference to records in that application so that flow into and out of the pipeline can be determined.

The pumps are not directly represented; however, suction and discharge pressure measurements polled by analogs can be referenced by the pipe_segment records.

Valves, represented as status or multistate records, are referenced by the pipe_segment records.