Pipe Segment record Batch Tracking Compiler (BTC) attributes

PIPE

The record name.

Yes.

GROUP

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

No. If not specified, group will be inherited from pipeline record.

SECT

Name of the section table record to which the pipeline_segment belongs.

No. This is mainly used to aggregate segment linepacks into a single value for use in Pipeline Monitoring (PLM).

UPSOBJ

The node record or pipe_segment that connects in the upstream direction. Two values are present:

1. PIPENODE or PIPESEG. Indicates whether the upstream record is from the Node table or the Pipe_segment table.

2. Name of the node or pipe_segment record.

Yes.

For more information, see Create pipeline connections.

DWNSOBJ

The node record or pipe_segment that connects in the downstream direction. Two values are present:

3. PIPENODE or PIPESEG. Indicates whether the downstream record is from the Node table or the Pipe_segment table.

4. Name of the node or pipe_segment record.

Yes.

For more information, see Create pipeline connections.

PIPEMP

Two values are present:

5. Upstream linepost. A linepost is a distance indicator in miles or kilometers.

6. Downstream linepost.

Yes. These should match the lineposts for the first and last profile linepost.

Note: The system does not perform a check to confirm the match.

PIPEFL

Name of a status point representing a valve that, if Closed, indicates the pipe_segment to be shut in.

No.

PIPERV

Name of a status point, which, if Open, will indicate that the pipe_segment flow is reversed. Any state other than Closed will default to Open.

No.

BATCHXFER

VFC

Name of the record that is providing batching information to the meterPath attribute for this segment. If this is configured, the meterPath can be populated by any one of the following record types:

• BATCHXFER (batchxfer)

• VFC (virtualflowcomputer)

The pipe_segment must be a stub. For more information, see Create pipeline connections.

The pipe_segment must be a terminal. That is, in either the upstream or downstream direction, there can be no more pipe_segments.

No.

PIPEOD

Outer diameter, using the Thickness Units specified in the unit profile of the pipe segment.

Yes.

PIPEWT

Wall thickness, using the Thickness Units specified in the unit profile of the pipe segment.

Yes.

PIPELN

Length in miles or kilometers.

Yes.

PIPECAP

Capacity, in barrels or cubic meters, at standard temperature and pressure conditions.

Yes.

UNITPROF

The name of the unitprofile record that this pipe segment uses.

Note: The unit profile for each pipe segment needs to be configured to be the same for all pipe segments in the pipeline.

Yes.

PIPETMP

Two names of analog points that poll temperatures:

7. Temperature analog at the upstream end of the pipe, or NOTELEMETRY if none are present.

8. Temperature analog at the downstream end of the pipe, or NOTELEMETRY if none are present.

   The option to auto-inhibit a temperature analog point is available. For more information, see Pressure and temperature analog auto-inhibit configuration.

No. Temperatures are interpolated wherever analog points are absent. If none exist for the pipeline, default temperatures are used. See BASETEMP or BASETEMPMNTH configuration for the pipeline record above.

PIPEPRS

Two names of analog points that poll pressures:

1. Pressure analog at the upstream end of the pipe, or NOTELEMETRY if none are present.

2. Pressure analog at the downstream end of the pipe, or NOTELEMETRY if none are present.

The option to auto-inhibit a pressure analog point is available. For more information, see Pressure and temperature analog auto-inhibit configuration.

No. Pressures are calculated wherever analog points are absent. If none exist for the pipeline, default pressures are used.

For more information, see Configure the Base Pressure/Temperature Values tab of the Pipeline record for the pipeline record above.

SEVERITY

Severity of alarms issued against the node record:

• LOW

• MEDIUM

• HIGH

No. Defaults to lowest severity possible.

PIPESEQ

Sequence number. Used for reporting purposes only.

No.

FILCON

Linepack filter constant. This is used to smooth the calculated linepack between cycles via the following equation:

where:

= filtered linepack value.

= calculated linepack value.

= previous linepack value.

= linepack filter constant.

No. Defaults to 0.85

FLOWRATESOURCEPATH

This sets a source to use for the instantaneous flow rate instead of the default flow rate calculations employed by the Batch Tracking application.

No.

PROFPNT

Profile point. Defines properties at lineposts along the length of the pipe_segment. One line defines one profile point. Up to 40 of these may be present for one pipe_segment. A profile point has the following values:

• Linepost

• Elevation

• Maximum Operating Pressure (MOP)

• Upstream Moving Reference (not used and is always set to False)

• Downstream Moving Reference (not used and is always set to False)

Yes. Minimum two profile points required.

BELV

This sets a low pressure limit for the calculated gauged pressure in the profile. If any pressure drops below the limit, the system generates an alarm. There are two values.

9. The limit itself.

10. Enable/disable of the alarming. True is enabled.

No.

BMOP

This is the pressure threshold for the Maximum Operating Pressure (MOP). If any profile point pressure comes within this threshold of MOP, an alarm is issued. There are two values.

11. The threshold itself.

12. Enable/disable of the alarming. True is enabled.

No

DBAND

This is the limit which the difference between the polled pressure at the downstream end of the pipe_segment and the calculated gauged pressure from the profile for the same location cannot exceed. If exceeded, an alarm is issued. There are two values.

13. The limit itself.

14. Enable/disable of the alarming. True is enabled.

No.

PRIDISPLAY

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

No.

SLIPFACTOR

The slip factor of the pipe segment. The value must be between 0.0 and 1.0. The specified value will only be used by an anomaly passing through this segment if the anomaly has the Use Segment Slip Factor option enabled.

No. If not specified it will be set to 1 by default.

ANOMTYPEUNEXPECTED

A space separated list of anomaly type names. Anomalies of these types will raise alarms as they approach or enter this pipe segment. A maximum of ten anomaly types can be specified. If more than ten types are specified, then the remainder will be ignored.

No. If nothing is specified, all anomalies approaching or entering this segment will do so without raising alarms.

ANOMTYPEUNEXPECTEDAPPINH

True or False. Inhibits alarms when an anomaly with a type specified by ANOMTYPEUNEXPECTED approaches this segment.

No. Default is False.

ANOMTYPEUNEXPECTEDENTINH

True or False. Inhibits alarms when an anomaly with a type specified by ANOMTYPEUNEXPECTED enters this segment.

No. Default is False.