Define Node records
- Last UpdatedApr 24, 2025
- 3 minute read
Node records represent junctions, stations, or terminals in the pipeline.
Their purpose is the following:
-
To create points where flow merges or splits.
-
To create Receipt (meter in) or Delivery (meter out) terminals.
-
To identify pipe points where batch or anomaly arrival needs to be predicted and alerted on.
The table below shows the Node Record Batch Tracking Compiler (BTC) attributes.
|
Attribute Name |
Description |
Required |
|---|---|---|
|
Node |
Record name. |
Yes. |
|
Group |
Group. For more information about groups, refer to Configure the Batch Estimated Time of Arrival (ETA) tab of the Node record. |
No. If not specified, group will be inherited from pipeline record. |
|
DISPNAME |
Display name. This is a more descriptive record name that can be used on displays such as the Pipeline Control. |
No |
|
EVTINH |
TRUE or FALSE. If true, events issued against the node record are inhibited. |
No. Default is FALSE. |
|
ALMINH |
TRUE or FALSE. If true, alarms issued against the node record are inhibited. |
No. Default is FALSE. |
|
MERGEPIPE |
When 2 or more batches merge at a node, a batch ID for the merged batch needs to be selected from one of them. The merged batch ID at this node will be the ID of the batch coming from the pipe_segment record named here. |
No. Merge batch ID is determined by other methods if this is not set. |
|
MERGEANM |
TRUE or FALSE. If TRUE, when two different batches (with the same product) are merged at this node a "merge start", a "merging", and eventually a "merge stop" anomaly will automatically be created. The "merge start" and "merge stop" anomalies will mark the beginning and the end of the merge (the "merge stop" is inserted when the merge actually finishes). When inserted, these two anomalies will flow with the product down the pipeline. The "merging" anomaly has a slip factor of 0 and does not move in the pipeline. It is positioned at the merging node, as a reminder to the Controller, and will be deleted when the merge stops. |
No. Default is FALSE. |
|
BDMERGEANM |
TRUE or FALSE. If TRUE, when two different batches (with a different product, also called a "bad merge") are merged at this node a "bad merge start", a "bad merging", and eventually a "bad merge stop" anomaly will automatically be created. The "bad merge start" and "bad merge stop" anomalies will mark the beginning and the end of the merge (the "bad merge stop" is inserted when the merge actually finishes). When inserted, these two anomalies will flow with the product down the pipeline. The "bad merging" anomaly has a slip factor of 0 and does not move in the pipeline. It is positioned at the merging node, as a reminder to the Controller, and will be deleted when the merge stops. |
No. Default is FALSE. |
|
SEVERITY |
Severity of alarms issued against the node record.
|
No. Default is set to the lowest severity possible. |
|
IDET |
Name of detect record at this node. Refer to Define Anomaly Detect records. |
No. |
|
ADET |
Name of detect record at this node. Refer to Define Anomaly Detect records. |
No. |
|
ETADIS |
TRUE or FALSE. If true, no estimated times of arrival at this node for batches and anomalies are generated. |
No. Default is FALSE. |
|
RTU |
Name of a remote associated with the node. This is used with alarms. |
No |
|
ALM |
This sets up warning and arrival alarming for batches at the node. Three values are present:
|
No. Default is ‘alarming disabled’. |
|
ANMALM |
This sets up warning and arrival alarming for anomalies at the node. Three values are present:
|
No. Default is ‘alarming disabled’. |
|
ANMEVT |
This field has been discontinued. The system will now always generate events. |
No. |