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

AVEVA Pipeline Operations for Liquids

Define Pipeline records

  • Last UpdatedApr 24, 2025
  • 6 minute read

The pipeline record is always the first record defined in Batch Tracking Compiler (BTC). Other records can appear in any order after this. The pipeline record contains the characteristics of the pipeline entity as a whole and the attributes that are global to the records that have a child relationship to the pipeline record.

The following table lists the items in the BTC pipeline record.

Note: For backward compatibility, the states are separated by spaces in the BTC file. In the actual database field, and in the Advanced Database Editor (ADE), the states are separated by commas.

Attribute Name

Description

Required

PIPELINE

Record name.

The line ‘PIPELINE:’ must be present at the start of the pipeline record but the actual name is not required since the pipeline name is set by the file name.

DESCRIPTION

Description.

No.

DATASET

Dataset. All child records will inherit this setting.

Yes.

GROUP

Group. For more information about groups, see Configure the Batch Estimated Time of Arrival (ETA) tab of the Node record.

No, but use is standard.

INACTLIM

Inactive alarm limit. If the pipeline is set to inactive, the application processing will wait for this period of time, in minutes, before issuing an alarm to remind the Controller that the pipeline is inactive. A value of zero disables this alarm.

No. If not specified, a default of 15 minutes is used.

BASETEMP or BASETEMPMNTH

The temperature to be used for volume corrections to GSV if no analog input for temperature exists. Use BASETEMP if a single temperature is to be used, BASETEMPMNTH if 12 are to be made available to the Controller for selection, one for every month.

No. If not specified, a default of 15⁰C is used for metric units, 60⁰F for imperial units.

BASEPRES

The pressure to be used for volume corrections to GSV if no analog input for pressure exists.

No. If not specified, a default of zero is used.

SEVERITY

The severity level to be used for alarms issued against the pipeline record.

No. If not specified, low severity is used.

INITPRD

The name of the product in the Prodtype table to be assigned to the default batch created for the pipeline when the pipeline is loaded using BTC.

No. If not specified, the first record found in the Prodtype table will be used.

INITBID

The ID to be assigned to the default batch created for the pipeline when the pipeline is loaded using BTC.

No. If not specified, a default ID will be created with the prefix: ‘DEFAULT’.

STATVLVOPEN

A string containing space-separated integers. This set of integers indicates which states of cursta in a valve status record represent open.

No. If not set, a string of "" will be entered. This will eventually default to "1" in use.

STATVLVCLOSE

A string containing space-separated integers. This set of integers indicates which states of cursta in a valve status record represent closed.

No. If not set, a string of "" will be entered. This will eventually default to "2" in use.

MULTVLVOPEN

A string containing space-separated integers. This set of integers indicates which states of inputCurRaw in a valve multistate record represent open.

No. If not set, a string of "" will be entered. This will eventually default to "1" in use.

MULTVLVCLOSE

A string containing space-separated integers. This set of integers indicates which states of inputCurRaw in a valve multistate record represent closed.

No. If not set, a string of "" will be entered. This will eventually default to "2" in use.

STATPMPON

A string containing space-separated integers. This set of integers indicates which states of cursta in a pump status record represent on.

No. If not set, a string of "" will be entered. This will eventually default to "1" in use.

STATPMPOFF

A string containing space-separated integers. This set of integers indicates which states of cursta in a pump status record represent off.

No. If not set, a string of "" will be entered. This will eventually default to "2" in use.

MULTPMPON

A string containing space-separated integers. This set of integers indicates which states of inputCurRaw in a pump multistate record represent on.

No. If not set, a string of "" will be entered. This will eventually default to "1" in use.

MULTPMPOFF

A string containing space-separated integers. This set of integers indicates which states of inputCurRaw in a pump multistate record represent off.

No. If not set, a string of "" will be entered. This will eventually default to "2" in use.

STATMIXON

A string containing space-separated integers. This set of integers indicates which states of cursta in a mixer status record represent on.

No. If not set, a string of "" will be entered. This will eventually default to "1" in use.

STATMIXOFF

A string containing space-separated integers. This set of integers indicates which states of cursta in a mixer status record represent off.

No. If not set, a string of "" will be entered. This will eventually default to "2" in use.

MULTMIXON

A string containing space-separated integers. This set of integers indicates which states of inputCurRaw in a mixer multistate record represent on.

No. If not set, a string of "" will be entered. This will eventually default to "1" in use.

MULTMIXOFF

A string containing space-separated integers. This set of integers indicates which states of inputCurRaw in a mixer multistate record represent off.

No. If not set, a string of "" will be entered. This will eventually default to "2" in use.

STATFLOREV

A string containing space-separated integers. This set of integers indicates which states of cursta in a flow status record represent reverse.

No. If not set, a string of "" will be entered. This will eventually default to "1" in use.

STATFLOFOR

A string containing space-separated integers. This set of integers indicates which states of cursta in a flow status record represent forward.

No. If not set, a string of "" will be entered. This will eventually default to "2" in use.

MULTFLOREV

A string containing space-separated integers. This set of integers indicates which states of inputCurRaw in a flow multistate record represent reverse.

No. If not set, a string of "" will be entered. This will eventually default to "1" in use.

MULTFLOFOR

A string containing space-separated integers. This set of integers indicates which states of inputCurRaw in a flow multistate record represent forward.

No. If not set, a string of "" will be entered. This will eventually default to "2" in use.

Base message

This is the standard RealTime database (RTDB) field flag.bmsg. It is not set by the BT file because the default is used on initial setup.

No. This will be set to the message table record with the name ‘Pipeline’.

ETADELETE

An integer. If greater than zero, it indicates that, when an ETA becomes "past station", it should be removed on that interval. For example:

If the integer is 0, the entry will not be deleted until the fragment goes away.

If the integer is 1, immediately delete the entry after it goes past the station.

If the integer is 2, delete the entry on the next cycle after the one on which it goes past the station. Leave it up for 1 cycle.

If the integer is 3, delete the entry on the second cycle after the one on which it goes past the station. Leave it up for 2 cycles.

This field is not required and will default to zero.

LINEAR

(discontinued)

By default, the system uses a linear calculation method for linepack.

This field has been discontinued and replaced with LINEPACKMETHOD. Remove this field from your Batch Tracking (BT) files.

LINEPACKMETHOD

By default, the system uses a linear calculation method for linepack. If you wish to use a custom linepack calculation method, use this field to specify the name of the method.

For more information on using a custom linepack calculation method, refer to "Creating Your Custom Batch Tracking Linepack Calculations" within the AVEVA Pipeline Operations for Liquids Developer Guide documentation.

This field is not required and will default to "LINEAR" unless you want to specify a custom linepack calculation method.

If you want to use the LINEPACKMETHOD field, you must remove the LINEAR field from the BT file. If both fields are defined within a BT file, Batch Tracking Compiler (BTC) execution will fail.

PRIDISPLAY

The easy eXtended Operator Station (ezXOS) display name that can be accessed from the Alarm Summary when this point generates an alarm.

This field is not required.

DISMAXPRESCHK

Can be set to one of the following options:

True

False

Set to True to disable the maximum pressure ceiling in the product group correction library when calculating correction factors for the pipe segment.

This field is not required and will default to False.