Pipeline branches

 

To add a new branch, select a pipeline (or any already existing branch) in the project tree and click the  button of the Components toolbar (or use the corresponding Insert menu item) - the new branch will be added to the project tree after the selected element. It is important to remember that the order of branches in the project tree is not essential for calculating the pipeline. Therefore, branches can be added to the pipeline in any order; if they were inserted in the wrong order, they can be swapped at any time using the standard Cut/Paste commands of the Edit toolbar, the Edit menu, or the context menu (called by right-clicking on a branch in the project tree) - for more information, see here.  

In addition, a branch can be added by activating one of the pipeline nodes in the diagram - in this case, this node will be considered the default starting node of this branch.

After adding a branch, a list of its initial data will be displayed in the Object Properties Window:

 

 

Please note that when changing the specified branch diameters, the program will not only automatically adjust the values of the diameters of the components of this branch (up to the first element with a change in diameter if any), but will also change the values of the radii of the bends and elbows in this branch if they are equal to the standard value of 1.5*DN (for pipes with DN < 500mm) or 1*DN (for pipes with DN >= 500mm).

 

A special case is the assignment of flow rates for "three-phase" mixtures (of oil, water and natural gas). If three fluids are specified in the project tree, then the flow rates of each of the three phases (oil, water and gas) must be specified separately by clicking the corresponding button opposite the flow rate in the Object Properties Window for the branch:

 

 

 

The flow rates can be specified either explicitly (in kg/hour, m3/hour and other units) for each of the phases, or in the form of oil flow rate (it is mandatory) and water cut and gas factor coefficients (or any combinations of these values with each other):

 

 

 

If you are unsure of what type of calculation you will be performing for a pipeline, just in case, set the temperatures in all branches.

 

Please note that when calculating two-phase flows using the model taking into account boiling/condensation of the fluid along the pipeline (when the "Undefined" fluid phase state is specified), it is permissible not to specify the temperature in the source branch if the vapor quality value for this branch is specified greater than 0 but less than 1. In this case, the flow temperature will be automatically determined by calculating the phase equilibrium for the specified gas content and pressure at the starting point. If both the temperature and the gas content (greater than 0 but less than 1) are specified for the branch, then it is considered that the gas content value has a higher priority, so the flow temperature in this case will be recalculated when calculating the phase equilibrium for the specified pressure and gas content.

 

A special case is pipelines with an "Undefined" fluid phase state, consisting of one branch, in which the pressure at the end node is specified. For such pipelines, the specified values of the mass gas content and/or temperature in the branch are interpreted as the gas content/temperature of the flow at the end point of the pipeline, and an "inverse" heat and hydraulic calculation is performed for them in order to determine the required pressure, temperature and gas content of the flow at the inlet of the pipeline. Such a hydraulic analysis calculation task is, in particular, quite often used in the calculation of "transfer" pipelines feeding oil in a vapor-liquid state from furnaces/heaters to a distillation column.

 

 

 

Setting branch nodes parameters

 

The branch node data is specified in the Nodes tab of the Branch Properties Window; these include:

 

 

 

 

 

Please note that node parameters can also be set by directly selecting the required node of the pipeline - for more details, see Working with pipeline nodes.