Create pipeline connections

The information generated when setting UPSOBJ and DWNSOBJ is not saved in the pipe_segment record but is instead used to automatically configure records in the Connectivity table.

Records in this table define the pipeline layout and are the reason why a pipeline must have its components initially configured as a whole using the Batch Tracking Compiler (BTC) rather than allowing components to be individually configured using the Advanced Database Editor (ADE).

A number of rules must be observed when making the connections for pipe_segments and nodes:

1. The pipeline must start and terminate at a node.

2. Pipe segments can connect to each other, but only one-to-one. (In other words, pipe segment connections will form a linear leg.)

3. Any number of pipe segments can connect to a node. (This allows the pipeline to branch.)

4. Whenever a pipe_segment makes a reference to another pipe_segment, the referenced pipe_segment record must refer back as part of its configuration.

   Example:

   PIPE: pipe1

   UPSOBJ: …

   DWNSOBJ: pipe2

   PIPE: pipe2

   UPSOBJ: pipe1

   DWNSOBJ: …

5. A pipe_segment must always have both an upstream connection and a downstream connection.

6. Forming a closed loop (in other words, a portion of line splits and then joins back downstream) is problematic but can be allowed. The following is not allowed:

   1. A pipe_segment or series of pipe_segments cannot be bounded by the same node.

   2. There cannot be two different series of one or more pipe_segments bounded by the same 2 nodes.

   3. These rules are applied when the BTC file load is run and a fatal error will occur and be reported if a violation is found.

Stub Pipe_segments

These are pipes of negligible size (set to a capacity of .001 barrels or cubic meters and a length of .01 miles or kilometers) that can be used to attach other objects (meters and valves) in specific locations.