Configure the Main tab of the Pipeline record
- Last UpdatedApr 24, 2025
- 3 minute read
The table below compares fields that can be configured on the Advanced Database Editor (ADE) pipeline Row Edit form with the associated Batch Tracking Compiler (BTC) attributes.

This table details the pipeline Row Edit identification fields.
|
BTC Attributes |
pipeline Row Edit |
|---|---|
|
Pipeline |
Name |
|
Description |
Description |
This table details the Main tab and corresponding Batch Tracking Compiler (BTC) attributes.
|
BTC Attributes |
pipeline Row Edit, Main tab |
Description |
|---|---|---|
|
Group |
Group |
For more information, see Configure the Batch Estimated Time of Arrival (ETA) tab of the Node record. |
|
Dataset |
Dataset |
|
|
N/A |
Base Message |
BTC always uses the default setting. |
|
pointClass |
Point Class |
The Point Class field is used to allow the Administrator to configure alarm severity. For further information about the Point Class, refer to Volume 1 of the RealTime Administrator documentation. |
|
pointSubClass |
Point SubClass |
For further information about the Point SubClass, refer to Volume 1 of the RealTime Administrator documentation. |
|
N/A |
Active |
This must be set for the pipeline to be processed. Not set when BTC is run because the initial state on loading of a pipeline is Inactive. |
|
INACTLIM |
Inactive Alarm Limit (Min) |
For more information, see Pipeline Record (Batch Tracking Compiler [BTC]). |
|
ETADELETE |
When to delete ETAs past station |
This field defines when the ETAs which are past station can be deleted. 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. |
|
PRIDISPLAY |
Priority Display |
Specify the graphic you want to be associated with the Priority Display button on an easy eXtended Operator Station (ezXOS) control panel. |
|
LINEPACKMETHOD |
Linepack Calculation Method |
By default, the baseline linear calculation method is assigned. If you do not plan to override the default value, you can either remove this field completely or assign linear. If you want to override the default value with your extended linepack method, assign the name of the lpackalg enumeration that is mapped to the method. For example, if CustomMethod1 is mapped to CustomEnum1 in the lpackalg enumeration, assign CustomEnum1 for the Linepack Calculation Method. For more information, refer to "Creating Your Custom Batch Tracking Linepack Calculations" in the AVEVA Pipeline Operations for Liquids Developer Guide documentation. Note: This field can no longer be used together with LINEAR (now discontinued). When both fields are defined in a Batch Tracking (BT) file, Batch Tracking Compiler (BTC) execution will fail. |