Demonstration Examples

Pipe2016: KYPipe Demonstrations and Example Data

Demo1 – Municipal Water Distribution System

A simple pipe system representing the main pipes of a small municipal distribution
system is shown in Figure 1-1. This system is used to demonstrate the use of Pipe2016:
KYPipe for regular and extended period simulations and Pipe2016: Surge for surge
analysis. A number of modeling features are demonstrated with the data files provided in
the Examples folder (“Examples” button in the File Open menu). In this manual the data
along with additional details are provided so the user can lay out and set up these
examples. A number of additional exercises are presented to illustrate Pipe2016 modeling
elements and features.

Figure 1-1 Pipe System – Demo1

1
 1-1 Demo1 –Description of System

The system is supplied by a pump which has the following head/flow/efficiency data:

The system has 2 overhead 35 foot diameter storage tanks with the following
characteristics:
Tank 1: Max. elevation = 755 ft., Min elevation = 735 ft. Initial level = 750 ft.
Tank 2: Max. elevation = 755 ft., Min elevation = 730 ft. Initial level = 749 ft.

The pipes are 6, 8, and 10-inch ductile iron as shown below and the Hazen Williams
Roughness coefficients are all 130. The pump suction and discharge lines are 12 inch
ductile iron.

Figure 1-2 Pipe System Diameters - Demo1

2
The node elevations and demands (in gpm) are shown in the figures below.

Figure 1-3 Pipe System Elevations and Demands - Demo1

3
 1-2 Demo1 – Developing the Pipe2016 Model

Step 1 – Background Map - Ideally you will have a scaled background map which can
be imported into Pipe2016 and used to lay out the pipes and automatically scale the pipe
lengths. If available this map should be imported to use as the background for the pipe
system. For this example the background map shown in Figures 1-1 to 1-3 is a .dwg file
which is a scaled vector drawing file. This map is called City.dwg and may be found by
clicking the Add Demo Map button in the Backgrounds menu shown below. The map is
imported as a background map as shown in Figure 1-4a and 1-4b.

KYnetic Background menu icon:

Classic tabs:

Figure 1-4a Adding the Background Map - Demo1

4
 Figure 1-4b Adding the Background Map - Demo1

Step 2 – System Layout - Using the mouse and the background map as a guide the pipe
system layout can be developed very quickly. Once the pipe layout is complete the two
tanks, supply reservoir and pump nodes can be created by selecting the locations and
using the Node Type dropdown list to designate the node type. At this point the pipe
system will appear as shown below in Figure 1-5

5
 Figure 1-5 Pipe System Layout – Demo1

Step 3 – Provide Pipe Data - The recommended means to provide pipe data is to first
develop the Pipe Type Table. This is accessed through the KYnetic Components menu
icon or the Classic tabs Setup/Defaults | Pipe Type. The following table is
appropriate for this example. The Estimated 10 Year Roughness is utilized with the
Pipe2016 aging feature and is optional.

Figure 1-6 Pipe Type Table – Demo1

6
 Figure 1-7 Pipe Type Table – Demo1

Figure 1-7 illustrates the Pipe Type data entry. When the pipe is selected in the map and
Pipe Type is clicked the menu shown above appears. A click on the second entry (di-150-
8) will result in all the data items except Length being entered into the pipe data box. The
length has been scaled using the background map so only the entry for Pipe Type is
needed to provide the required pipe data. Additional data for Fittings or other Pipe2016
features may be entered but this is optional. The Pipe Type is entered for each pipe to
complete the data requirements for pipes.

Step 4 – Provide Node Data - Data is then entered for each node in the system. The
data requirements vary depending on the Node Type. Node data entry is illustrated below
for the top center junction, the pump and Tank 2.

Junction Node: Classic – KYnetic

Tank (Fixed Diameter): Classic - KYnetic

7
 Pump (Table): Classic – KYnetic

Figures 1-8 Node Data – Demo1

1-3 Demo1 – Regular Simulations and Changes (Demo Model.P2K)

Step 1 – Check the Data and Run the Analysis - Once data entry is complete various
data checks should be performed. A graphical data check is very useful and is performed
by turning on labels such as Node Elevation and Pipe Diameter and Roughness as shown
in Figure 1-9.

Labels menu – Node Elevations: Classic - KYnetic

8
Figure 1-9 Graphically Checking Data – Demo1-1

Classic

9
 KYnetic
Figure 1-10 Error Check and Analysis Data – Demo1-1

Once the data is reviewed an Error Check should be performed as shown in Figure 1-10.
Then an Analysis can be carried out as shown also in Figure 1-10. The analysis will be
for the Baseline Conditions described by the input data. The results for pressures at
nodes are shown in Figure 1-11.

Figure 1-11 Node Pressures for Baseline Data – Demo1-1

10
 Figure 1-12 Pipe Flows (gpm) for Baseline Data – Demo1-1

Step 2 – Add Change Data and Run Additional Simulations - It is desired to set up
the following three scenarios:

Case 0 - The pump is running with normal (Baseline) demands

Case 1 - The pump is off and the tanks supply the system
Case 2 - The pump is off and a fire demand of 650 gpm is placed at Junction J-13

The first simulation (Case 0) is always the Baseline Data and is the analysis illustrated in
Section 3-1 Step 1. The additional cases may be run by modifying the Baseline data and
re-running the analysis. However, Pipe2016 has the capability to run multiple
simulations by specifying Changes to various Pipe and Node parameters, allowing the
Baseline Data to remain the unchanged. One advantage of this approach is that the results
for the various cases are easily compared in Tables and Graphs.

The Change Data screens used to set up these 2 additional simulations are shown in
Figure 1-12. These are accessed by clicking on the node in the map screen and selecting

the icon at the bottom of the Node Info window (KYnetic) or the ‘Chng’ (Change)

11
button at the top of the node information window (Classic). To set up an additional case
just select the node(s) and/or pipe(s) and enter the desired case number, parameter type
(click center column and select from list) and the new parameter value.

Case 1: Classic - KYnetic

Case 2: Classic - KYnetic

Figure 1-13 Change Data for Cases 1 and 2 – Demo1-1

12
Figure 1-14 Node Pressures for Case 1, Pump off – Demo1-1

13
 Figure 1-15a Node Pressures for Case 2, Pump Off, Demand 650 gpm – Demo1-1

Pressure contours are an effective alternate way to present results. Figure 1-15b shows
the setup screens and the resulting pressure contour plot for Case 2.

14
 Classic Contours menu

KYnetic Contours menu

Figure 1-15b Node Pressures Contours for Case 2 – Demo1-1

15
 1-4 Demo1-2 – Additional Node Types (Demo Other Nodes.p2k)

Figure 1-16 Additional Node Types – Demo1-2

A number of additional Node Types are illustrated in this example. These include:
a) Active Valve
b) Regulator
c) Loss Element
d) Sprinkler
For items a, b, and c insert a node at the indicated location. To Insert click on pipe at the

intended location and select Insert icon (bottom of Pipe Info window in KYnetic)
or “Insrt” button (top left of Pipe Information window in Classic). Then select the node
type from the drop-down list.

The Active Valve is a pump control valve located just downstream from the pump. It is a
10 inch Butterfly valve with a Cv = 1000 when fully opened. Note that an Active Valve

16
can be characterized by the wide open Flow Coefficient (Cv100%) or the wide open
Resistance (R100%). A check box in the Preferences menu (KYnetic) or System
Data | Preferences (Classic) is available to switch from one description to the other (as
shown in Figure 1-17). The data boxes for this Active Valve are shown in Figure 1-17.

Figure 1-17 Active Valve Data – Demo1-2: Classic - KYnetic

A Flow Control Valve is located in the pipe leading to Tank 2 to limit the flow to 300
gpm. The setup for this element is shown in Figure 1-18. In addition a Backflow
Preventor located in the pipe leading to J-2 on the lower left side in the pipe system. This
device has head loss vs. flow data and uses a curve based on this data to determine the
loss through the element. The data for these elements is shown in Figure 1-18

17
 Flow Control Regulator: Classic – KYnetic

Loss Element: Classic – KYnetic

Figure 1-18 Regulator and Loss Element Data – Demo1-2

Sprinkler Data: Classic - KYnetic

18
 Additional Pipe Data: Classic - KYnetic

Figure 1-19 Additional Pipe and Sprinkler Data – Demo1-2

For item d select the existing node and move the mouse to the location of the sprinkler
and RC. Then select the new node and change it to a sprinkler. A 900 foot long 4 inch
line leading to a 1 inch sprinkler (orifice) was added to model a fountain. At the fountain
a 4 foot long 2 inch pipe rises 4 feet to the sprinkler orifice. The data for the additional
pipe and sprinkler are shown in Figure 1-19. Data for the pipe connecting a sprinkler is
included with the sprinkler data. The Sprinkler Constant can be obtained using the
Sprinkler/Blowoff Constant Tool as shown below.
KYnetic Tools menu icon:

Figure 1-20 Sprinkler/Blowoff Constant Tool – Demo1-2

19
 Figure 1-21a Flowrates (gpm) – Demo1-2

Figure 1-21a and 1-21b show the pressures and flows obtained by the hydraulic analysis
which includes the additional elements. The Tabulated Report contains additional
sections summarizing results for various elements. The dropdown list illustrated below

may be accessed when (KYnetic) or Report tab (Classic) is selected. Figure 1-22
shows the report generated for Pumps and Regulators.

20
 Figure 1-21b Pressures (psi) Demo1-2

Figure 1-22 Pump and Regulator Reports - Demo1-2

21
 1-5 Demo1-3 – Fire Hydrants (Demo Hydrant Analysis.P2K)

Locations and reference names are shown below (Figure 1-23) for 9 fire hydrants. Fire
flow test data for the hydrants is shown in Figure 1-24. To Insert these hydrants, click on

pipe at the appropriate location and select Insert icon (bottom of Pipe Info window
in KYnetic) or “Insrt” button (top left of Pipe Information window in Classic). Then
select Hydrant from the drop-down list.

Figure 1-23 Fire Hydrant Locations Demo1-3

Figure 1-24 Fire Hydrant Test Data - Demo1-3

22
 Hydrant Data: Classic – KYnetic

Figure 1-25 Fire Hydrant (Test) Data and Flow Plot - Demo1-3

Once a hydrant is added the hydrant can be selected and the elevation and fire flow data
shown in Figure 1-26 can be entered as shown above (for reference and graphing only,
not used for calculation). The Graph button or the KYnetic menu shown above allows
you to generate Fire Flow Test Data plots such as the one shown in Figure 1-25. This plot
using a Q 1.85 factor for the X axis is used for predicting the available fire flow from the
test data (this follows AWWA and NFPA guidelines). Hydrants also allow you to use a
model to calculate available fire flows. The Pipe2016 setup screen for Fire Flow
calculations is shown below in Figure 1-26. Pipe2016 provides a variety of fire flow and
hydrant flushing calculations although the most common is the Available Fire Flow at a
Specified pressure (usually 20 psi) which is illustrated below.

23
 Figure 1-26 Fire Flow Calculations Set Up Screen - Demo1-3

Figure 1-27 Fire Hydrant Analysis and Report - Demo1-3

The Set Up screen shown in Figure 1-26 will analyze all the fire hydrants in your model
to calculate the fire flow available at each hydrant (one at a time) such that the pressure in

24
the system is above 20 psi at all locations. Normally the minimum pressure occurs at the
fire hydrant but it may occur at a different location. If this happens the Fire Flow Report
shown above will show 2 additional columns of calculations showing the reduced fire
flow and the node location where the minimum pressure occurs.

1-6 Demo1-4 – EPS (Demo EPS.P2K)

It is a simple matter to set up an Extended Period Simulation (EPS) using the Baseline
Data for the system. Care should be taken to initially clear any Change Pattern Data

before setting up the EPS (select (KYnetic) or Setups and Defaults/Change

Patterns (Classic) and click on the Clear button). To run an EPS go to the EPS Setup
Screen (KYnetic) or System Data/EPS (Classic) and enter data as shown in Figure
1-28. For a municipal water distribution system such as this example a 24-hour period
using a 1-hour computational period is a common selection although a shorter time
period may be needed if there are numerous events during the period (tanks filling or
emptying and pumps turning on and off).

KYnetic EPS menu icon:

Figure 1-28 EPS Setup Screen - Demo1-4

25
 Tank Data: Classic

Tank Data: KYnetic

Figure 1-29 Tank EPS Data - Demo1-4

For an EPS the maximum (Mx) and Minimum (Mn) levels are significant items. This
data shown in Figure 1-29 will cause the tanks to shutdown if either of these limits is
reached. For municipal water systems the demands will vary hour by hour because of the
variation in the diurnal curve as shown in Figure 1-30. This curve developed by AWWA
based on field measurements provides a rational basis for varying the demands over a 24-
hour period (Demand Pattern). Pipe2016 has the capability to set up, save and load
Demand Patterns. An example pattern based on the AWWA curve is available (click the
Load button in Demand Pattern menu and select AWWA.dmt). This Demand Pattern file
is loaded as shown in Figure 1-30 and used for this example.

26
 Figure 1-30 Diurnal Curve Data From AWWA - Demo1-4

KYnetic Demand Pattern table icon:

Figure 1-31 Demand Pattern EPS Data - Demo1-4

For Demo1-4 the pump is always on. For an EPS the pump status can be controlled either
by inputting Change Data which can be used to turn the pump on or off at designated
times or by a Control Switch which can be used to control the pump on/off status based
on pressures or tank levels. This EPS example illustrates the tank action based only on
demand variations.

27
Figure 1-32 Tank Levels - Demo1-4

Figure 1-33 Pressures - Demo1-4

28
 Figure 1-34 Pump Flow - Demo1-4

Figures 1-32 through 1-34 show results for this simulation. Figure 1-32 shows that the
tanks are completely filled within the first 2 hours and stay full for the rest of the
simulation. This causes the pump to run at a low flow and high head and produces a
substantial pressure increase when the tanks fill as shown in Figures 1-33 and 1-34.
Figure 1-35 shows the report on the pumping cost from the tabulated report. To obtain
this report you must enter a cost/kilowatt hour as shown in Figure 1-28.

Figure 1-35 Power Costs - Demo1-4

29
 1-6 Demo1-5 – EPS (Demo EPS Control Switch.P2K)

The results from Demo1-4 illustrate a situation which would be unacceptable for a
municipal water system. The tanks cannot remain full because of water quality concerns.
This example (Demo1-5) illustrates controlling the pump using the level of the water in
Tank 1 (T-1). For this illustration we add a pump control switch which will turn the pump
off when the water level exceeds 753 feet hydraulic grade (or 123 feet based on ground
elevation). This is 2 feet below the maximum level (125 feet). The pump will then come
on when the level drops below HGL = 737 feet (107 feet). The setup for this Control

Switch + (KYnetic) or Other Data/Control Switches (Classic)

is shown in Figure 1-36.

Figure 1-36 Control Switch Data - Demo1-5

The results for this EPS are shown in Figures 1-37 thru 1-39. As can be seen the pump
switches off at around 2 hours and turns back on at around 14 hours. This results in less
pressure fluctuations and a significantly reduced power cost (Figure 1-40)

Figure 1-37 Tank Levels - Demo1-5

30
 Figure 1-38 Pressures - Demo1-7

Figure 1-39 Pump Flow - Demo1-5

Figure 1-40 Power Costs - Demo1-5

31
 1-6 Demo1-6 - Water Quality Simulation (Demo Water Quality.P2K)

A water quality analysis is run using an EPS file. This is to determine the variance in the
water quality parameters over a time period (generally 24 hours). Only one screen of
additional data is required to set up the water quality analysis as shown below. Click on
the KYnetic Analysis menu as shown below or Other Data | Quality (Classic) to see the
Quality input menu.

32
 Figure 1-41 Water Quality Data

The Bulk and Wall Reaction Rates are set for all pipes using the global value shown
rather than averaging values for each pipe. A Simulation Time of 144 hours is chosen to
provide ample time for the solution to reach a repeatable condition. For this example a
Chemical analysis is chosen to determine the chlorine residuals. We could choose to
calculate the age of the water (select Age) or trace the origin of the water (select Trace).
One additional useful data input is the Initial Concentration of chlorine at each node.
This can be assigned an initial value of zero. However, a reasonable estimate of this
value will provide the solution more quickly and accurately. Since the chlorine is
supplied at 2 ppm, a value of 1 ppm is used for the initial concentration and this data is
assigned by using the Gbox (Group Mode) to select the entire system and the Edit Node
Set to assign a value of 1.0 to the Initial Concentration. When this is done the User Data
for each node should display this data as shown below:

Classic - KYnetic
Figure 1-42 User Data with Initial Concentration

33
The Water Quality Analysis is then run by selecting (KYnetic) or Analyze (Classic)
and Analyze | Water Quality.

Once the analysis is completed the results are reviewed. Figure 1-43 shows the results
for the minimum and maximum chlorine levels. This is obtained by selecting Chlorine in
the Results Selector – bottom right of program window and Node Results - Min and Max
under Labels.

A plot of the variations in the chlorine residuals at various nodes can be shown as
illustrated in Figure 1-44.

Figure 1-43 Min/Max Chlorine Residuals

34
Figure 1-44 Chlorine Residuals at Selected Nodes

35
 1-6 Demo1-7 - Optimized Calibration (Demo Calibration.P2K)

The section describes the original input approach for Optimized Calibration. A
Calibration Wizard is also available. Figure 1-45 shows a network schematic with the
test results of four fire flow tests displayed. This fire flow test data provides the basis for
performing a calibration of the distribution system. The calibration will determine the
optimum value for pipe roughnesses for various groups of pipes.

Figure 1-45 Fire Flow Test Results

The test data include the residual flow and pressure for each of the tests. For the
calibration these four hydrants were converted to junctions as required to set up the
calibration data. For this demonstration, it is assumed that the boundary conditions (tank
levels, demands, pump status, etc.) for each fire flow test were the same and that the
baseline demands and the tank levels are those used for the demo model.p2k file and
shown in Figure 1-46. Thus, it is not necessary to enter change data for the four separate
fire flow tests. The only additional data required is the Calibration Data shown in Figure
1-47.

36
Figure 1-46 Tank Levels and Baseline Demands for Calibration

KYnetic Calibration menu:

Figure 1-47 Fire Flow and Calibration Data

37
The roughness bounds were defined for four Calibration Groups selected using various
diameters as follows:

Group Diameter
0 12
1 6
2 8
3 10

Two calibration analyses were run.

For the first calibration a 5% tolerance was introduced for the fire flows. This means that
the fireflows can be +/- 5% of the measured residual flow and accounts for a small error
in this measurement. The calibration run produced a calibration where the optimal
pressure differed from the measured pressure by only 1.4% where the difference is
greater than 1.6% for the uncalibrated model. The results for the first case are shown in
Figure 1-48.

For the second case, a zero percent fireflow tolerance was used and, as expected, a larger
difference of 4.8% was obtained. These results are shown in Figure 1-49.

Figure 1-48 First Case Results (5% fire flow tolerance)

38
Figure 1-49 Second Case Results (0% fire flow tolerance)

39