Pipenet

PIPENET VISION
TRAINING MANUAL
STANDARD MODULE
CHAPTER 1
THE BASICS AND INTRODUCTORY EXAMPLES
Revision 4.1, June 2017

PIPENET VISION TRAINING MANUAL STANDARD: CHAPTER 1
PAGE 1 OF 46 REVISION 4.1, JUN 2017
1. INTRODUCTION..............................................................................................................................................2
2. CONCEPTS .....................................................................................................................................................2
2.1 PRESSURE DROP MODEL ...............................................................................................................................2
2.2 TREATMENT OF ELEVATION DIFFERENCES .......................................................................................................5
2.3 USER-DEFINED FLUIDS ...................................................................................................................................6
2.4 CONTROL VALVES ..........................................................................................................................................7
2.5 PUMPS ..........................................................................................................................................................9
2.6 INTRODUCTION TO SPECIFICATIONS ............................................................................................................. 14
3. INTRODUCTORY EXAMPLES .................................................................................................................... 18
3.1 STEADY STATE SINGLE-PIPE PROBLEM ........................................................................................................ 19
3.2 SIMPLE THREE-PIPE PROBLEM .................................................................................................................... 33
1. Introduction
In this section, the concepts used in the PIPENET VISION Standard Module are briefly
described. The modelling concepts and the design concepts are covered under this category.
PIPENET VISION Standard Module uses contemporary equations for all the models; for
example, pipes, ducts, pumps, valves, and filters.
In the past, engineers performed fluid-flow analysis using manual calculations. However, real
time and effort are required for carrying out such analysis for large networks. Now, the
PIPENET VISION Standard Module helps the user, providing faster and reliable solutions.
It is important that the reader of this chapter is familiar with the contents of the user interface
(which are described in detail in Chapter 1 of the PIPENET VISION User Interface Training
Manual). It is highly recommended that the reader is at least familiar with the main aspects
discussed in that chapter.
2. Concepts
2.1 Pressure Drop Model
The pressure loss, , in a pipe is described as
where
is the pressure loss due to friction and fittings,

is the pressure loss due to elevation change,
is the pressure loss due to any orifice plate fitted.
Full details of the equations that are used to calculate these pressure losses are described
below.
2.1.1 Frictional Losses in Pipes – Darcy Equation

is determined using the Bernoulli Equation, which is a theoretical equation that gives the
pressure in pipes, ignoring frictional effects. The pressure drop due to friction effects can be
found by comparing the theoretical results from the Bernoulli Equation with results obtained in
experiments. Based on the work of the French engineer Henri Darcy (1803–58) the following
equation is obtained.
where
is the internal diameter of the pipe,

is the pipe length,
is the equivalent length of any pipe fittings,
is the Fanning friction factor,
is the fluid velocity,
is the fluid density.
The Fanning friction factor depends on the relative roughness of the pipe (i.e., pipe roughness
divided by pipe diameter) and the Reynolds Number, , which is defined as
where is the fluid viscosity. The standard values for can be obtained from a graphical
representation known as the Moody Diagram. The friction factor is represented in PIPENET
VISION by the following empirical formulae (in which is the surface roughness of the pipe).
Laminar flow :
Transitional flow :
The value of is obtained by interpolating between the laminar value for and the
turbulent value at .
Turbulent flow :
2.1.2 Pressure Loss due to Fittings
The pressure loss due to fittings is given by the following formula.
where is the K-factor of the fitting.
2.1.3 Pressure Loss due to Elevation Change
The pressure drop caused by the difference in elevation of the two ends of a pipe is given by
in which
is the acceleration due to gravity,

is the change in elevation.
2.1.4 Frictional Losses in Ducts

Ducts are very similar to pipes, apart from the obvious difference that ducts have a
rectangular cross-section. In PIPENET VISION, ducts can be used only when the fluid in the
network is a gas. Ducts are modelled using the same equations as pipes.
Suppose that the user wishes to use PIPENET VISION for modelling the flow of a general
liquid in a network consisting of rectangular ducts. In this case, the user would include pipes
(and not ducts) in the network. However, the radius of each pipe would be specified as the
hydraulic radius of the corresponding duct. The mean hydraulic diameter, , for the duct is
given by
where
is the duct height,

is the duct width.
2.2 Treatment of Elevation Differences
2.2.1 Pipe/duct elevations
With this approach, each pipe or duct is assigned a change in elevation, which is equal to the
height at the output node minus the height at the input node.
PIPENET VISION also assigns a reference node. The height of each node is calculated with
respect to the reference node. If a network contains one or more loops, the pipe/duct
elevations option can result in height inconsistencies. In a loop, the sum of the elevation
changes must be zero. However, if a pipe/duct elevation has been incorrectly entered, the
sum will not be zero, and an elevation error will be registered. Elevation errors can be difficult
to locate in networks that contain many complex loops.
However, there are tools in PIPENET VISION for locating elevation errors quickly.
2.2.2 Node Elevations
With the node-elevations approach, the elevation of each node is directly entered as an
attribute of the node. Note that elevation errors cannot occur with this method. Therefore, if a
mistake is made while inputting a node elevation, this error will not be detected in PIPENET
VISION.
2.3 User-defined Fluids
2.3.1 User defined Liquids
The density and viscosity must be supplied for a user-defined liquid. For the following three
cases, the density and viscosity can be defined as follows:
 Liquid direct specification: The values are supplied as constants.
 Liquid property correlation: The values vary with temperature, and can be obtained
using the following correlation formulae:
Density:
Viscosity:
where
is the temperature (K),
is the critical temperature (K),
, , and are constants for the liquid.
Besides the temperature, , the user must also supply values for , , , and .
 Liquid variable properties: From a given set of tabular data for the density and
viscosity against temperature, the density and viscosity at a particular temperature, ,
are obtained using linear interpolation.
2.3.2 User-defined Gases
The user may define the gas to be either a Van der Waal’s Gas (Class 3) or an Ideal Gas
(Class 4). In either case, the user must supply the molecular weight, critical properties (i.e.,
temperature, pressure and volume) and ratio of specific heat capacities (Gamma).
2.4 Control Valves
A valve may be characterised by one of three built-in models, which requires either (a) a K-
factor and a port area, (b) a flow coefficient, or (c) a control-valve type. Select the appropriate
choice from the valve-type combo-box and radiobuttons, and then enter the required data (if
any) in the valve-characteristics boxes below. Note that the value of the flow coefficient
corresponds to water at 20°C.
2.4.1 Modelling Equation
The modelling equation is either
Or
where
is the pressure drop across the valve,
is the (volumetric) flowrate through the valve,
is the fluid density,
is the density of water at 20°C,
is the valve setting (0 < s < 1),
is the K-factor for the valve,

is the cross-sectional area of the valve port,
is the valve flow coefficient for water at 20°C.
2.4.2 Control Valve Considerations
A control valve regulates flow or pressure in a network. The pressure drop across the control
valve is dependent on the valve settings and the physical characteristics of the valve.
The valve setting can either be specified directly by the user, or be determined by PIPENET
VISION such that a particular sensor reading is satisfied. Three sensor types are available:
 Pressure at a node - Pressure control,
 Flow rate through a particular pipe - Flow control,
 Pressure difference between two nodes - Differential pressure control.
PIPENET VISION calculates a control valve's setting such that the associated sensor reading
is attained. However, in some scenarios, this is not possible. For example, a control valve that
monitors the flow rate in an adjacent pipe may be unable to achieve the sensor reading, even
with a fully open setting. In such cases, the valve setting will correspond to fully open or
closed, depending on which setting produces the closest result for the sensor reading.
Some care is required with control valves that use a sensor to calculate the valve position. A
fully closed control valve behaves like a closed non-return valve, and can isolate parts of the
network, resulting in an unsolvable system. In particular, this situation can sometimes occur if
blocked pipes and control valves are both present in the same scenario.
Three built in control-valve characteristics are available: linear, equal percentage and quick
opening. Alternatively, the user can create a library control-valve type by specifying the valve-
characteristic curve of the K-factor or flow coefficient against the setting, . Cubic
interpolation is then used in PIPENET VISION to determine intermediate points on the
characteristic curve.
The linear control-valve option is the same model as is present in earlier versions of PIPENET
VISION, some of which did not include the equal-percentage or quick-opening options.
2.5 Pumps
The simple pump model in PIPENET VISION uses the pump-performance curve, which is
normally intended only for use in the positive quadrant (in other words, when the flow and the
head are positive).
In this section, we shall describe the data that is required for defining a pump.
2.5.1 Pumps - Coefficients Unknown
In the PIPENET VISION Standard Module, data for pumps and fans can be created in a
library. Also, PIPENET VISION performs a curve fit to create coefficients that define the
curve, and then uses these coefficients in the calculations. The input data must be in the
form of data pairs taken from the performance curves.
Typically, the units for the pump curves are not the same as the units in which pressure-drop
calculations are to be made. For example, it is usual to specify the pump curve in head of
fluid, rather than psi. For this reason, the pump/fan module accepts data in its own units.
The dialog box for inputting a pump curve is shown below.

PIPENET VISION takes into account the fact that the head generated by a pump is
independent of the density of the fluid, and so PIPENET VISION makes an appropriate
density correction in converting the head into a pressure. Similarly, the pressure generated
by a pump depends on the fluid, and when the pump curve is defined in terms of pressure, an
appropriate density correction is applied. This is the reason why, when the pump-
performance curve is defined in terms of pressure, the performance curve is interpreted to be
that of water.
Creating a New Pump
1. Select the New Button, and provide a name and description.

2. Select the desired flow-rate and pressure units from the drop-down menus.
3. Provide minimum and maximum values of the flow rate.
4. Provide at least three points for the curve (at least four for cubic or cubic spline).
5. Select the type of curve to be fitted (quadratic, cubic or cubic spline).
6. Click on the Apply Button to add the pump to the library.
7. The coefficients are then calculated and displayed, along with the pump curve.
Note that the definition of the pump curve will only be accepted if at least three/four points are
supplied, and that the slope of the calculated curve is negative everywhere between the
minimum and maximum values.
Type of
curve fitted
function
Editing an Existing Pump
1. Select the name of the pump from the drop-down list.

2. Make the required changes to the pump parameters.
3. Click on the Apply Button to commit the changes.
Deleting a Pump
1. Select the name of the pump from the drop-down list.

2. Click on the Delete Button.
2.5.2 Pumps Coefficients Known
This capability is hardly ever used. Unless there is a compelling reason to do so, it is better to
use the coefficients-unknown option.
If the coefficients that define the pump-performance curve can be obtained from the
manufacturer, select “Pump – Coeffs. known” from the Libraries Menu (which can be
represented as Libraries | Pumps – Coeffs. known).
Pump Input Data
1. The pump label.
2. The input and output nodes.
3. The pump efficiency.
4. The name of the pump in the library.
An example of the dialog box for a pump is as follows.
2.5.3 Useful Tips
If the user knows the performance coefficients for a pump, but does not want to use a pump
library, then the pump can be defined as a non-library pump by supplying the values of , ,
, , and .
In order for the calculator to function correctly, it is necessary to ensure that there is only one
flowrate corresponding to each pressure gain. The following restrictions, therefore, apply:
 For flow rates between , and , the slope of the performance curve must
be negative or zero.
 For flow rates between , and , there must be no flow rate that results in
no pressure change; that is, the performance curve must not cross the horizontal
axis.
For flow rates outside the range , and , PIPENET VISION extrapolates the
performance curve using the tangent to the curve at the minimum or maximum flow-rate
values, and issues an appropriate warning message.
PIPENET VISION will calculate the power required by a pump, based on a supplied
efficiency. This efficiency value need not be supplied, in which case, it will be assumed in the
power calculation that the pump is 100% efficient.
2.6 Introduction to Specifications
In order to be able to solve a network, boundary conditions must be provided in the form of
either (a) flow or pressure specifications on input and output nodes or (b) pressure
specifications on internal nodes (which are nodes that are neither input nor output nodes).
These specifications must obey certain rules.
2.6.1 Assumptions
1. Input and output nodes are points in a network where fluid either enters or leaves
the network.
2. Internal nodes are nodes that are neither input nodes nor output nodes.
3. Sub-networks may be created by the presence of breaks and blocks.
4. If a node is at one end of a break then it is considered to have an attached

pressure specification.
5. If a node is at one end of a block then it is considered to have an attached flow

specification.
2.6.2 Rules Governing Specifications
The specification rules can be summarised as follows. Suppose that
is the number of pressure specifications,
is the number of flowrate specifications,
is the number of input/output nodes.
In all cases, specifications must adhere to the following basic rules:

2.6.3 Design Case
In the design case, one or more pipe sizes are left unset. PIPENET VISION will then
determine the pipe sizes based on either the maximum allowable pipe velocity or pressure
drop per unit length. In the design case, two sets of specifications need to be provided. One
set is for pipe sizing and the other is for the final analysis calculation. There are three
reasons why two sets of specifications are needed.
 The conditions for pipe sizing may be different from the conditions for analysis. For
example, pipe sizing may be based on the summer operating conditions of the plant,
whereas the analysis may be based on the winter operating conditions.
 Pipe sizing may be based on a future expansion, whereas analysis may be based on
current operating conditions.
 Pipe sizes depend mainly on the flowrates that the system needs to handle. In the
design phase, all but one specification must be a flow-rate specification. In the
analysis phase, pressure and flow-rate specifications may be given in any reasonable
combination, as long as there is at least one pressure specification.
In the pipe-sizing case where the design phase is used, and must satisfy the
constraints given in the following table.
Phase
Design
Analysis
The following points apply.
Design Phase: Supply a pressure specification to one input/output node, and then
supply flow-rate specifications to the other input/output nodes.
Analysis Phase: Supply appropriate pressure and flowrate specifications so that the
total number of specifications is equal to the sum of the number of
input and output nodes.
The design option must be switched on if pipe sizes are to be determined by PIPENET
VISION, as shown below.
Design Option
Button
A typical specification in the design case is shown below.
2.6.4 Analysis Case
If pipe sizing is not required then analysis specifications are all that are needed.
2.6.5 Design and Analysis Cases
Two sets of specification must be given; namely, one set for the design phase and another
set for the analysis phase.
The design-phase specifications are used for pipe sizing. The analysis-phase specifications
are used for modelling the actual operating case.
There are two reasons why the design-phase specifications may not be the same as analysis
phase specifications.
 In the design phase, all specifications except one must be flow-rate specifications. In
the analysis phase, there can be any reasonable combination of specifications, as long
as at least one of them is a pressure specification.
 The sizing of the pipes may be based on one set of operating conditions, and the
analysis case may be based on another set. For example, pipe sizing may be carried
out with a future expansion in mind, whereas the analysis specifications may be based
on the current operation.
2.6.6 Simple Example
Consider the following network.

Nodes 1, 3 and 4 are input/output nodes, so .
For the Design phase:
For the Analysis phase:
If pressures are set at Nodes 1, 3 and 4 then , and so .
The specifications in this example are summarised in the following table.
Phase
Design
Analysis
3. Introductory Examples
In this chapter, we consider several examples to enable users to become familiar with the use
of the PIPENET VISION Standard Module. Some of the examples are very simple and others
are closer to real applications.
In order to keep the input simple, some sections are omitted (as mentioned in the text).
3.1 Steady State Single-pipe Problem
Consider the following simple network.
In this example, the aim is to calculate the pressure loss in a single pipe with an inner
diameter of 1.61 in, a length of 10 ft, an elevation change of 2 ft, a pipe roughness of 0.0018
in, and three 90-degree bends. The inlet pressure is 20 psi G and the outlet pressure is 10
psi G. The fluid is water at 20 °C.
Note that, if the output node of a pipe is higher than the input node, the elevation of the pipe is
positive; however, if the output node is lower than the input node, the elevation is negative. In
PIPENET VISION terminology, elevation is the difference in height between the input and
output nodes of a pipe.
3.1.1 Initialisation Data
Firstly, click on either the Init Menu or the Options Menu, depending on which menu style is in
use. The Init Menu is shown when the PIPENET VISION Menu Style is in use, and the
Options Menu is shown when the Windows Menu Style is in use. The menu style can be
selected from the Window Menu. Note that, if the PIPENET VISION Menu Style is in use, the
menu style can be changed to the Windows Menu Style by choosing “Use Windows menu
style” from the Windows Menu; on the other hand, if the Windows Menu Style is in use, the
menu style can be changed by choosing “Use PIPENET menu style”.
The arrangement of the menu bar under the two styles (namely, Windows Style and
PIPENET VISION Style) is shown below.
Windows Menu Style:

PIPENET VISION Menu Style:
Title
The title can contain up to four lines. To register the data, click on the Apply Button and, to
undo the changes, click on the Cancel Button. The purpose of the OK Button is to register the
data in the dialog box and then leave the menu (unlike the Apply Button, for which the dialog
box is not closed).
Note that, throughout the training manuals, notation like Options | Title is used to represent
the action of choosing “Title” form the Options Menu.
Module Options
If you can still access the Title Page, click on the Module Options Tab (which is located just
below the top of the window); otherwise, use Options | Module options.
Choose “Coulson and Richardson (Darcy)” in the section entitled “Pressure Model”, and
select “Use pipe/duct elevations” in the Elevations Section. Also, ensure that, in the Warnings
Control Section, the “Ignore - proceed with calculation” option is chosen. Finally, choose
“Crane” for the “Orifice plate Model”.
Units
From the Units Page, choose U.S. Units.
Fluid Type
The fluid is water, at 68 °F.

Heat Transfer
Skip this page for now.
Pipe Type
Skip this page for now.
Display
For “Labels”, select all of the options; for “Grid”, select “Orthogonal” for “Style” and “Lines” for
“Grid”. Make sure that “Display grid”, “Snap to grid” and “Arrows indicate flow direction” (for
“Results”) are enabled.
Calculation
As there are no pipe-types defined in the system, only

the Analysis phase option is available and is
automatically selected.
Tables and Defaults
Skip these sections for the time being.

3.1.2 The Network
Go to the Tools Palette, and select the Pipe Tool.
Pipe Tool
Select the Schematic Window, move the cursor to a grid point, and click the left-hand mouse
button. Move the cursor to another grid point and click again. You have now drawn a line,
with a node at each end. The line represents a single pipe, with the node numbers and the
pipe label shown below.
Select Tool
Attributes Data
Click on the Select Tool from the Tools Palette (otherwise you will remain in the mode for
creating pipes), and then click on the pipe (to select it). Now that the pipe has been selected,
its attributes can be entered through the Properties Window.
The Additional K-factor Box is used for inputting a K-factor (which the user prefers not to set
up in a library).
In order to enter fittings, select the Fittings Tab (which is located at the bottom of the
Properties Window). Now, select the required fitting from the available fittings, and press the
Add Button the appropriate number of times. In the current example, there are three 90-
degree bends; therefore, “90 deg bend (r/d = 1.5)” should be selected, and the Add Button
should be pressed three times.
The flow status can be normal, blocked or broken. A blocked pipe is one that might either (a)
have an isolation valve closed or (b) contain a blocked filter. A broken pipe is one that might
have ruptured.
The pipe type is the pipe schedule that is used for the pipe, but is not relevant for this
particular problem.
The attribute data can be also entered through the Data Window, which can be accessed
from the View Menu (i.e., View | Data window). If the attributes are changed in the Data
Window, these changes will be reflected in the schematic. The Browse Menu can be used to
access the attributes for any node or component in the network.
3.1.3 Input Specifications
Specifications are operating conditions that are provided by the user to enable PIPENET
VISION to perform calculations.
The number of specifications is equal to the number of input/output nodes.
Make sure that the arrow cursor (i.e., the Select Tool from the Tools Palette) is active. Point
the cursor at Node 2 and click. The Properties Window will now contain a table for entering
the specification. Set the “Input/Output node” to “Output”, then select “YES” for “Analysis
Spec.”, and set the pressure to 10 psi G, as is shown below.
Next, point the cursor at Node 1 and click. The Properties Window for Node 1 will now
appear. Set the “Input/Output node” to “Input”, and then select “YES” for “Analysis Spec.”,
and set the pressure to 20 psi G.
Design specifications are the specifications that are used for the purpose of pipe sizing, if
required. However, pipe sizing is not required in this problem.
3.1.4 Saving the Data
Click on the File Menu and select “Save As…”. Specify a name for the “.SDF” file, and click
on “Save”. Make sure that the path name is as intended, and that the file type is” .SDF”.
3.1.5 Checking the Input Data
Now check the validity of (a) the network that has been generated and (b) the specifications
that have been input. This check can be performed by clicking on the Check Icon or by
accessing the Check Option through the Calculation Menu (via Calculation | Check).
Menu bar
check
Check Tool
If there are no errors, the following box is displayed.
3.1.6 Performing the Calculation
Once the validity of the system has been confirmed, the calculation can be performed. The
calculation can be run by clicking the Calculate Icon or by accessing the Calculate Option of
the Calculation Menu.
3.1.7 Looking at the Results
Display Display link

node results results
Menu of
node items
Menu of
link items
It is possible to look at the results in the Schematic Window itself, as well as through the Data
Window or the Properties Window. A more detailed result can be viewed through the output
browser (or word processor). The Display Options Tag, which is shown below, is used for
displaying the result in the Schematic Window.
In order to look at the results on the schematic itself, click on the results-related options.
Display node colouring legend button - If this option is selected, a node colour-
coded legend is displayed in the Schematic Window. From the drop-down box, the
parameter to be displayed on nodes can be selected; for example, elevation and
pressure.
Display pipe/duct colouring legend button - If this option is selected, a link

colour-coded legend is displayed in the Schematic Window. From the drop-down box,
the parameter to be displayed on pipes can be selected; for example, flow rate and
velocity. Arrows can be displayed to indicate the flow direction .
Results through the Schematic
Pressure
in psi G
Flow rate in
US gal/min
The above picture shows the results for the given network in the Schematic Window. The
result-related options are used to provide the results with distinct colours. In this case, the
legends are also provided for pressure (node result) and pipe volumetric flow (pipe result),
with their appropriate units. The topic of colouration is covered completely in the section on
colour schemes (which is discussed later).
Results Through the Data Window
Results
Button
The results can be viewed through the Results Tab of a Data Window, as shown above.
Since the Data Window contains the results in the Excel format, the details from the Data
Window can be directly copied into an Excel spreadsheet using the Copy and Paste
Commands.
Results through the Properties Window

The result can be viewed through the Properties Window, as shown below. To view the result
of any component (for example, a pipe or a node), click on the item that is to be examined,
and PIPENET Vision will display the appropriate data and results in the Properties Window.
Results
for Pipe 1
In order to look at the output file, either (a) click on the Browse Output Button (which is
located by the red Calculate Button) or (b) use Calculation | Browser. Then, in either case,
select the required option from the dialog box that appears.
3.2 Simple Three-pipe Problem
In this example, we look at a simple three-pipe problem, in which the fluid is water at 20 °C.
We consider the following points:
 Three pressure specifications.

 One pressure specification and two flow-rate specifications.
 Pump selection.
 Using a device to balance the flowrate.
 Inputting a vendor’s pump curve and performing the final calculation.
The network is shown below.
The objectives for this example are as follows.
 Perform calculations with several combinations of specifications.

 Perform calculations in order to find the duty point of the pump.
3.2.1 Initialisation Data
Standard Options
Use the Colebrook-White Equation for the pressure model.

Units
Select a user-defined system, and specify the following units.

Variable Unit
Length m
Diameter mm
Velocity m/s
Temperature Celsius
Density kg/m3
Viscosity cP
Power kW
Thermal
kW/(m.K)
conductivity
Heat capacity J/kg K
Pressure bar Gauge
Flow type Volumetric
Flow rate m3/hr
Fluid Data
The fluid is water at 20°C.
Pipe Data
Use a roughness of 0.0457 mm for all pipes, and enter the following data.
Pipe Input Output Diameter Pipe Elevation

Fittings
Label Node Node (mm) Length (m) (m)
1 1 2 25 25 0 2 x 90 deg bend
1 x 90 deg bend
2 2 3 25 12 0
2 x 45 deg elbow
1 x 90 deg bend
3 2 4 25 18 0
1 x ball valve
3.2.2 Case 1: Pressure Specifications
Set the following pressure specifications.
Node Pressure Flow rate

Number (Bar G) (m3/h)
1 2 Unset
3 1 Unset
4 1 Unset
To see the following box, click on Node 4, and then select the Properties Tab in the bottom
left-hand corner of the screen.
In the following diagram, the nodes and pipes are coloured according to the pressure and flow
rate respectively.
3.2.3 Case 2: Mixture of Flow and Pressure Specifications
With a flow specification, the user must indicate whether the node is an input node or an
output node. However, with a pressure specification this distinction is not necessary.
Node Pressure Flow Rate

Number (Bar G) (m3/hr)
1 2 Unset
3 Unset 3 (out)
4 Unset 2.4 (out)
The results are as follows.
3.2.4 Case 3: Pump Selection Case
In this scenario, we assume that the flow-rate and pressure requirements are given at both
output nodes. However, there are no specifications at the inlet. In fact, our aim is to find the
pressure and flow rate at the inlet. Furthermore, we regard the flow rate requirements as
exact, but the pressure requirements as minimal values.
Note that at most three specifications can be made at any one time. In the calculation, we
shall make an assumption as to which is the critical pressure, and then set that value as a
specification. After the calculation, we shall check whether the other pressure is more than
the required value. If it is, a further calculation will not be necessary; otherwise, we shall
change the node on which the pressure specification has been made, and perform another
calculation.
Let us assume the following requirements.

1 Unset Unset
3 > 4.5 3 (out)
4 >5.0 2.4 (out)
We are only allowed to supply three specifications, so (in the first instance) we shall use the
following combination. We expect this case to be the critical case.

1 Unset Unset
3 Unset 3 (out)
4 5.0 2.4 (out)
If this case turns out not to be the critical case then a pressure of 4.5 Bar G should be
specified at Node 3, and the pressure specification at Node 4 should be discarded.
As the pressure on Node 3 is 4.9856 Bar G, which is more than the required 4.5 Bar G, we
conclude that our choice of the critical node is correct. If our choice had not been correct, we
would have had to use specifications according to the table below.

1 Unset Unset
3 4.5 3 (out)
4 Unset 2.4 (out)
As our choice of the critical node is correct, we can determine that the excess pressure on
Node 3 is 4.9856 – 4.5 = 0.4856 Bar G. Therefore, in order to achieve the required pressure,
we can create and introduce a device-type user-defined fitting.
3.2.5 Case 4: Introduce a Device-type Fitting
A pressure of 0.4856 Bar G at a flow rate of 3 m3/h is required on Pipe 2.
The following page can be obtained via Libraries | Fittings (page shown after clicking Apply).
Fittings can be added via the Fittings Tab of the Properties Window. Note that this tab
appears at the bottom of the window.
The results are as follows.

The outlet nodes meet the required demands of the user exactly. Therefore, we conclude
that the duty point of the pump needs to be around 5.40 m 3/hr at 6.39 bar G.
3.2.6 Case 5: Select and Input a Suitable Pump into the Pump Library
We need to insert the pump into the network and perform a calculation. We shall assume that
the flow rates at the outlets are kept at their required values. We, therefore, intend to
calculate the delivery pressure that is achieved.
In general, the pump curve will be more than adequate to meet the requirement, and we
would expect the pressures achieved to be more than the required values.
Flow Rate Pressure

(m3/h) (Bar G)
4.00 6.9
5.00 6.7
6.00 6.4
7.00 6.0
The above points are now to be added to the pump/fan module. Note that the minimum and
maximum flowrates are supplied. To open the pump/fan module, go to the Libraries Menu and
select “Pumps – Coeffs. unknown” (i.e., Libraries | Pumps – Coeffs. unknown).
Insert the pump into the network.

Select the pump curve, as shown in the diagram below.
Remove the specification on Node 1.
Apply a specification of 0 Bar G at the inlet to the pump (Node 5).
The results are shown below.

.
3.2.7 Summary
It can be seen that the pressures at the outlet nodes are greater than what is required. This
completes the calculation.
This example illustrates the main steps in the complete design cycle, covering pipe sizing,
pump selection, flow balancing, and final calculation using the chosen pump.

Pipenet

Încărcat de

Informații document

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

Pipenet

Încărcat de

Drepturi de autor:

Formate disponibile

PIPENET VISION

THE BASICS AND INTRODUCTORY EXAMPLES

Revision 4.1, June 2017

2.1 Pressure Drop Model

The pressure loss, , in a pipe is described as

is the pressure loss due to friction and fittings,

2.1.1 Frictional Losses in Pipes – Darcy Equation

is the internal diameter of the pipe,

2.1.2 Pressure Loss due to Fittings

The pressure loss due to fittings is given by the following formula.

where is the K-factor of the fitting.

2.1.3 Pressure Loss due to Elevation Change

is the acceleration due to gravity,

2.1.4 Frictional Losses in Ducts

is the duct height,

2.2 Treatment of Elevation Differences

2.2.1 Pipe/duct elevations

2.2.2 Node Elevations

2.3 User-defined Fluids

2.3.1 User defined Liquids

 Liquid direct specification: The values are supplied as constants.

is the temperature (K),

is the critical temperature (K),

, , and are constants for the liquid.

2.3.2 User-defined Gases

2.4 Control Valves

2.4.1 Modelling Equation

The modelling equation is either

is the pressure drop across the valve,

is the (volumetric) flowrate through the valve,

is the fluid density,

is the density of water at 20°C,

is the valve setting (0 < s < 1),

is the K-factor for the valve,

is the cross-sectional area of the valve port,

is the valve flow coefficient for water at 20°C.

2.4.2 Control Valve Considerations

 Pressure at a node - Pressure control,

 Flow rate through a particular pipe - Flow control,

 Pressure difference between two nodes - Differential pressure control.

2.5.1 Pumps - Coefficients Unknown

The dialog box for inputting a pump curve is shown below.

Creating a New Pump

1. Select the New Button, and provide a name and description.

Editing an Existing Pump

1. Select the name of the pump from the drop-down list.

1. Select the name of the pump from the drop-down list.

2.5.2 Pumps Coefficients Known

Pump Input Data

1. The pump label.

2. The input and output nodes.

3. The pump efficiency.

4. The name of the pump in the library.

An example of the dialog box for a pump is as follows.

2.5.3 Useful Tips

2.6 Introduction to Specifications

3. Sub-networks may be created by the presence of breaks and blocks.

4. If a node is at one end of a break then it is considered to have an attached

5. If a node is at one end of a block then it is considered to have an attached flow

2.6.2 Rules Governing Specifications

The specification rules can be summarised as follows. Suppose that

is the number of pressure specifications,

is the number of flowrate specifications,

is the number of input/output nodes.