PAWD webinar:

Cape Coast Water

Hydraulic Supply
modelling Project
& EPANET
Siert Meijer, Joriën Mendez, Gideon Lomoko
24 & 25 June 2021
Schedule of webinar series Hydraulic modelling & EPANET
Five modules (sessions) in two batches:
- 20 & 21 May: Basic hydraulics
- 27 & 28 May: EPANET 1 (introduction to EPANET: workspace, project setup)
- 17 & 18 June: EPANET 2 (data input and model calibration)
- 24 & 25 June: EPANET 3 (analysis of hydraulic modelling results)
- 1 & 2 July: EPANET 4 (network design and improvement / optimization)

Please have EPANET available during all EPANET webinar sessions 1-4!

2
Previous session (20 & 21 May)
- Basic hydraulics - Block 1: Introduction to hydraulics / Pressure pipe flow /
Conservation of mass / Reynolds number / Fluid pressure
- Basic hydraulics - Block 2: Total energy equation / Bernoulli energy equation /
Conservation of energy / Energy losses
- Basic hydraulics - Block 3: Hydraulic head / Pump systems

3
Previous session (27 & 28 May)
- EPANET 1 - Block 1: Introduction to Epanet and hydraulic models / EPANET
components / Physical components
- EPANET 1 - Block 2: Non-physical components / EPANET workspace / Steps in
hydraulic modelling (with EPANET) / Project setup / Drawing a
network / Editing properties
- EPANET 1 - Block 3: Exercise / Run a hydraulic analysis / Viewing results

4
EPANET module 2 (17 & 18 June)
- EPANET 2 - Block 1: Run analysis / Graphs / Demand input / Demand patterns /
Non Revenue Water / Selection and Group Edit tools
- EPANET 2 - Block 2: Pipe length / Auto-Length function / Background maps
- EPANET 2 - Block 3: Import data from CAD or GIS / Input files / Model calibration

5
Schedule for today’s session
14:00 – 14:20: Introduction and Q&A previous session
14:20 – 14:50: EPANET 3 block 1 + Q&A (chat function)
14:50 – 15:30: EPANET 3 block 2 + Q&A (chat function)
15:30 – 16:00: EPANET 3 block 3 + Q&A (chat function)

6
EPANET module 3
- Q&A: Water demand input / Simple controls / Throttle valves
- Block 1: Network analysis / Guidelines and regulations / Scenarios to model /
Query and Map Finder tools / Maximum day model
- Block 2: Status report / Warnings and errors / Approach for hydraulic analysis /
Negative pressures
- Block 3: Warnings related to pumps / Other common warnings and errors /
Conclusions from hydraulic analysis / Attention point: pressures along
longer pipes

7
Q&A previous session

- In NRW, should we make a difference between commercial and physical NRW?

- Can we throttle valves?

8
Non Revenue Water
• “Non revenue” is missed income
• Non Revenue Water is the sum of:
- real losses (leakage) physical losses
- measurement errors (at water meters; apparent losses) commercial losses
- unauthorized consumption (e.g. theft, illegal connections) physical losses
- unbilled consumption (e.g. own use) physical losses

NRW has to be included in the model! NRW also flows through the network!

9
In NRW, should we make a difference
between commercial and physical NRW?
- You can measure what is produced (what is supplied from the sources)
- You can measure flow / consumption in the network (used for billing)
- The part that you do not measure / bill is total NRW, comprising both commercial
and physical NRW
- All NRW should be included in the model (this water also flows through the network)

10
Additional: How to determine water demand input?
- For existing networks / connections: measurements (used for billing)

- For new areas, you can use assumptions on water demand (based on knowledge
from similar buildings / areas). E.g. for household demand, multiply:
· no. of plots or houses
· persons per plot or house
· water demand per person

11
Can we throttle valves in EPANET?
- You can model a throttle valve as valve component (control valve) in EPANET

12
 Physical components (Valves) RECAP!

The different types of control valves included in EPANET are:

- Pressure Reducing Valve (PRV): limit the pressure at the downstream junction
- Pressure Sustaining Valve (PSV): maintain a set pressure at the upstream junction
- Pressure Breaker Valve (PBV): force a specified pressure loss to occur across the valves
- Flow Control Valve (FCV): limit the flow to a specified amount

- Throttle Control Valve (TCV): simulate a partially closed valve by adjusting the minor head
loss coefficient
- General Purpose Valve (GPV): are used to represent a link where the user supplies a
special flow-headloss relationship

Open/closed valves and check valves are modelled as pipe links with open/closed/CV status!
13
 Physical components (Valves) RECAP!

The different types of control valves included in EPANET are:

- Pressure Reducing Valve (PRV): limit the pressure at the downstream junction
- Pressure Sustaining Valve (PSV): maintain a set pressure at the upstream junction
- Pressure Breaker Valve (PBV): force a specified pressure loss to occur across the valves
- Flow Control Valve (FCV): limit the flow to a specified amount

- Throttle Control Valve (TCV): simulate a partially closed valve by adjusting the minor head
loss coefficient
- General Purpose Valve (GPV): are used to represent a link where the user supplies a
special flow-headloss relationship

Open/closed valves and check valves are modelled as pipe links with open/closed/CV status!
14
 Can we throttle valves in EPANET?

- You can model a throttle valve as valve component (control valve) in EPANET

- For control valves, you have to specify the type and the setting (mandatory)

- For a TCV, the setting is a value for the minor head loss coefficient

15
 RECAP!

Bends
Headloss in pipes (turbulent flow)
Two main categories:
- Friction losses (due to pipe roughness)

Contraction

- Other losses

We call the “other Expansion

losses” also “local
losses” or “minor
losses” Minor head loss coefficent

16
 Can we throttle valves in EPANET?

- For a TCV, the setting is a value for the minor head loss coefficient
- A relationship between the degree to which a valve is closed and the resulting head
loss coefficient is usually available from the valve manufacturer

- The setting parameter describes its operation point (at the considered moment in
time - user specified input)
- In EPANET, you can not specify a curve, but you simply assign the minor head loss
coefficient to the TCV

17
 2.832
∆𝐻 = 2 ∙ = 0.82
2 ∙ 9.81

18
 Can we throttle valves in EPANET?

- For a TCV, the setting is a value for the minor head loss coefficient
- A relationship between the degree to which a valve is closed and the resulting head
loss coefficient is usually available from the valve manufacturer

- The setting parameter describes its operation point (at the considered moment in
time - user specified input)
- In EPANET, you can not specify a curve, but you simply assign the minor head loss
coefficient to the TCV

- You can vary a setting over time using (simple) controls

19
 Non-physical components (Controls) RECAP!

Controls are statements that determine how the network is operated over time. They
specify the status of selected links as a function of time, tank water levels and pressures
at selected points within the network.

Simple controls Rule based control

20
Simple controls
Simple controls change the status or setting of a link based on:
- the water level in a tank
- the pressure at a junction
- the time into simulation
- the time of day

You can use an unlimited number

of control rules

21
Example of simple control to change valve setting over time

22
You can model other types of control valves in a similar way...
- Specify the type
- Specify the setting
- Vary the setting of the control valve using (simple) controls

23
 Physical components (Valves)

The different types of control valves included in EPANET are:

- Pressure Reducing Valve (PRV): limit the pressure at the downstream junction
- Pressure Sustaining Valve (PSV): maintain a set pressure at the upstream junction
- Pressure Breaker Valve (PBV): force a specified pressure loss to occur across the valves
- Flow Control Valve (FCV): limit the flow to a specified amount

- Throttle Control Valve (TCV): simulate a partially closed valve by adjusting the minor head
loss coefficient
- General Purpose Valve (GPV): are used to represent a link where the user supplies a
special flow-headloss relationship

For each type of valve, you can find the definition of the setting in the EPANET manual
24
Help Topics

25
Any further questions on these topics?

Please ask your questions in the chat!

26
BLOCK 1
Network analysis
Guidelines / regulations
Scenarios to model
EPANET tools: Query and Map Finder
Maximum day model

27
 Steps in hydraulic modelling

1. Building the EPANET model of the existing network (using available data, and
assumptions where necessary) or network design
2. Analysis of the EPANET model (Does the model run? Errors? Warnings? Do the
results show what you expect? → Correct input data if necessary)
3. Calibration of the EPANET model (comparing EPANET results to field
measurements, and adjusting assumptions where necessary)
4. a) Network analysis / optimization / scenario studies (adjusting the network, e.g.
network layout and demands, and dimensioning the network to the required
capacity, e.g. changing pipe diameters and sizing pump, to meet guidelines)
b) Water quality calculations

28
Viewing run results
Results can be viewed in:
- the network map (over time)
- graphs
- tables

29
What do we analyse after running EPANET (succesfully)?
Water District guidelines/regulations:
- Maximum pressure in pipelines (related to the strength of pipes)
- Minimum pressure at customer connection
- Maximum unit head loss (head loss/km)
- Maximum velocity (related to head loss and thereby to the energy needed for pumping)

Additional: Minimum velocity (at least once a day), related to self-cleaning pipes

When you make a design, you have to meet the guidelines!

30
What do we analyse after running EPANET (succesfully)?
Water District guidelines/regulations:
- Maximum pressure in pipelines (related to the strength of pipes)
- Minimum pressure at customer connection
pressure = head - elevation

- Maximum unit head loss (head loss/km)

- Maximum velocity (related to head loss and thereby to the energy needed for pumping)

Additional: Minimum velocity (at least once a day), related to self-cleaning pipes

When you make a design, you have to meet the guidelines!

31
 RECAP!

Hydraulic head

Hydraulic head

Pressure head
Head
Elevation

reference level: e.g. MSL

head = pressure + elevation

pressure = head - elevation
32
What do we analyse after running EPANET (succesfully)?
Water District guidelines/regulations:
- Maximum pressure in pipelines (related to the strength of pipes)
- Minimum pressure at customer connection
pressure = head - elevation

- Maximum unit head loss (head loss/km) UNIT head loss (not just head loss)
- Maximum velocity (related to head loss and thereby to the energy needed for pumping)

Additional: Minimum velocity (at least once a day), related to self-cleaning pipes

When you make a design, you have to meet the guidelines!

33
 Examples of guidelines / regulations

Water district 1 guidelines/regulations:

- Maximum pressure 70 m
- Minimum pressure at customer connection 7 m
- Maximum unit head loss (head loss/km) 10 m/km
- Maximum velocity Not defined

Water district 2 guidelines/regulations:

- Maximum pressure 100 m
- Minimum pressure at customer locations 7 m
- Maximum unit head loss (head loss/km) 10 m/km
- Maximum velocity 2 m/s
34
So how can we analyse whether a design is good?

Check if you fulfill the guidelines/requirements!

Check your extremes!

35
What do we analyse after running EPANET (succesfully)?
Water District guidelines/regulations:
- Maximum pressure in pipelines (related to the strength of pipes)
- Minimum pressure at customer connection
- Maximum unit head loss (head loss/km)
- Maximum velocity (related to head loss and thereby to the energy needed for pumping

Additional: Minimum velocity to be reached at least once a day, related to self-cleaning pipes
(different type of guideline!)

36
 What scenarios do you need to model?
Check your extremes!

Maximum demand → maximum flow → maximum velocity → maximum head loss →

minimum pressure [maximum day, maximum hour]

Minimum demand → minimum flow → minimum velocity → minimum head loss →

maximum pressure [minimum / average day, minimum hour]

You will need to collect input data for both scenarios (maximum and average day)!

37
 Question: What time to look at in the
maximum day model?

Maximum demand → maximum flow → maximum velocity → maximum head loss →

minimum pressure [maximum day, maximum hour]

Check the minimum pressure

criterion at the maximum
flow hour (morning peak
hour)

38
 Question: What time to look at in the
average day model?

Minimum demand → minimum flow → minimum velocity → minimum head loss →

maximum pressure [minimum / average day, minimum hour]

Check the special

minimum velocity
criterion (that
should be reached
at least one time
Check the maximum each day) at
pressure criterion at a maximum flow
minimum flow hour (peak hour) of the
(night hours) minimum / average
day
39
Analysis / check on guidelines in more complex systems
- The moments in time to check included in the previous slides are general
indications, and mostly true for gravity systems and simple pumped systems

- In more complex systems, minimum and maximum criteria may occur at different
moments of the day!
· Higher or lower pressure/velocity/headloss when pump(s) is/are on/off?
· In combination with higher/lower demands?
· Check results over time, using logical legends and EPANET tools!

40
Scroll through time
and check results
with logical legends

41
Query tool: Select nodes or links using a query
A query can be used to find nodes or links with properties or results below/equal
to/above a specified value

When you scroll through time, the query will change

to the correct no. of items found automatically

42
Map finder tool: Search for nodes or links that give errors or
warnings

43
From average day model to maximum day model

What input data needs to be changed?

44
 RECAP!
Steps in hydraulic modelling

1. Building the EPANET model of the existing network (using available data, and
assumptions where necessary) or network design
2. Analysis of the EPANET model (Does the model run? Errors? Warnings? Do the
results show what you expect? → Correct input data if necessary)
3. Calibration of the EPANET model (comparing EPANET results to field
measurements, and adjusting assumptions where necessary)
4. a) Network analysis / optimization / scenario studies (adjusting the network, e.g.
network layout and demands, and dimensioning the network to the required
capacity, e.g. changing pipe diameters and sizing pump, to meet guidelines)
b) Water quality calculations

45
 RECAP!

Steps to modelling with EPANET

1. Set up a new project (set defaults, units and time options)

2. Draw a network representation of your distribution system (or import the network)
3. Edit the properties of the objects that make up the system

4. Run a hydraulic analysis

5. View the results of the analysis
6. Repeat step 3 to 5 up to the desired result

46
 The Network Model – Required input
Elevation? NO NO / YES*
Junctions Water demand (base demand)?
Demand pattern?
Bottom elevation?
Diameter? Tanks
Water levels (initial/min/max)?

Reservoirs Hydraulic head (water level)?

Diameter?
Length?
Roughness coefficient? Pipes
Status (open/closed/check valve)?
Pump curve?
Pumps
(Control settings)?
Diameter?
Control setting? Valves
Status (open/closed)?
47
* How to go from average day to maximum day base demand?

- We can do this by applying a maximum day factor:

maximum day base demand = (average day base demand) x (maximum day factor)

- We can do this by applying a maximum day pattern (with pattern average >1)

- Alternatively, if consumption measurements (customer data) are available for a

maximum day, we can use these as direct input for customer demand

48
 Demand patterns

Pattern: multipliers to apply to the base demand

Average day PHIL pattern Maximum day PHIL pattern

Pattern average >1: Higher maximum

day base demand included in pattern 49
 The Network Model – Required input
Elevation? NO NO / YES*
Junctions Water demand (base demand)?
Demand pattern? YES
Bottom elevation? NO
Diameter? NO Tanks
Water levels (initial/min/max)? NO (min/max)
POSSIBLY (initial)
Reservoirs Hydraulic head (water level)?
Diameter? NO POSSIBLY
Length? NO
Roughness coefficient? NO Pipes
Status (open/closed/check valve)? POSSIBLY
Pump curve? NO
Pumps
(Control settings)? POSSIBLY
Diameter? NO
Control setting? POSSIBLY Valves
Status (open/closed)? POSSIBLY
50
QUESTION & ANSWER – BLOCK 1

Please ask your questions in the chat!

51
BLOCK 2
Status report
Warnings and errors
Appraoch for hydraulic analysis (using tools, tables and network maps)
Negative pressures

52
Exercise – Edit pipe properties

Let’s change some of the properties...

53
Exercise – Edit pipe properties

X
Pipe 6 to Closed

X 80

Let’s change some of the properties...

54
Run Analysis

55
Status Report

56
Set the Status Report to Yes or Full in the Hydraulics Options to
get more detailed information

No / Yes / Full

57
 What can we read in the Status Report?

- Information about iteration steps (EPANET calculations)

- Hydraulic Status at each hydraulic time step (1 hour in our case) over the simulation
time (24 hours in our case):
∙ opening/closing of links
∙ emptying/filling of tanks
Did you close the Status Report, and
∙ control actions do you want to open it again? Go to:
∙ etc....

- Errors and warnings

Status
58
Warnings and errors

- Errors: EPANET cannot calculate, run is unsuccesful (no results)

Status Report can
- Warnings: EPANET does calculate, but: read the warnings! also be found in
Report → Status
All error and warning messages generated during an analysis are written to the Status
Report (which will open automatically in case of an error or warning)

59
 Let’s zoom in on these warnings...

What does it mean to have negative pressures? 60

 Hydraulic head
h

Hydraulic head

head = pressure + elevation

pressure = head - elevation

Pressure head
Head
Elevation

Reference level
(e.g. MSL)

Pressure is negative when the elevation value is larger than the head value
61
 Pressure is negative when the elevation
value is larger than the head value

Pipelines and Pipe Networks Negative Pressure

Pipelines that travel over a long distance usually follow the natural contour of the land. This
may cause a section of the pipe to be raised to an elevation above the hydraulic grade line
(HGL) as shown in the figure below. Near the pipeline summit (S) the pressure head may
take on a negative value
-It is important to maintain pressure at
all points in a pipeline above the vapor
pressure of water (vapor pressure water
= -10m at 20°C)
-Water below this pressure will be
vaporized locally to form vapor pockets
-Vapor pockets collapse downstream in
regions of higher pressure
-Collapses are violent and may cause Cavitation
damage to the network
62
 Possible reasons for negative pressures

1. Start node head + head losses + node elevation → node pressure

(problems with the way the network has been designed or operated)

2. By default, EPANET is demand driven (DDA). Negative pressure when portions of

the network can only receive water through links that have been closed off

EPANET continues calculating as if water would be water even below the vapor pressure
(while in fact, water will turn into vapor below a certain pressure value called the “vapor
pressure”). This means that pressures can become very negative in EPANET.

63
 Negative pressures in future
and existing networks models
If negative pressures occur in a network model representing the design of a future water
supply network:
- Negative pressures may indicate that your system is unable to meet the given demand
- Negative pressures may be caused by data input errors

If negative pressures occur in a model describing an existing network model “as-is”:

- The negative pressures might actually occur in the real network. This could be verified by
measurements. If the negative pressure is confirmed in the field, there is no need to alter
the "as-is" model because it reflects reality.
- Negative pressures may be caused by data input errors. Double-check all network elements
from the source to the place where the negative pressure occurs.
64
 Negative pressures

Possible effects of negative pressures:

- Negative pressures might damage the pipe network (due to cavitation)
- Negative pressures (suction) indicate a risk that contaminated groundwater
infiltrates the network

Possibilities to avoid negative pressures:

- Raise the head at reservoirs, tanks and pumps that supply the criticial nodes
- Reduce the head loss along the pipeline to the critical nodes (e.g. by increasing pipe
diameters)

65
 Negative pressures

Is it logical what we see? Why do negative pressures occur from 5-14 Hrs
and from 16-19 Hrs into simulation, but not before, after and inbetween?
66
 Why do negative pressures occur at
these moments in time?

Average day PHIL pattern

- Demand is highest at those times, according
to our demand pattern!

- Higher demand → larger flow (and velocity);

- Larger flow (and velocity) → larger headloss;

- Larger headloss → lower resulting pressure

67
 Where do the negative pressures occur?

We know from the status report that

negative pressures start at 5:00.

Where are the nodes in which negative pressures occur? And why? Can we explain it?
1. Search in overview of all node results (e.g. in a table of node pressures for time 5:00)
2. Visualize the nodes with negative pressure (e.g. in the network map using logical
legends)
3. Use the Query tool

68
1. Search in overview of all node results

We can create a table!

69
 Pressure is related to
head and elevation

Click Add to
use the filter!

Negative pressures occur We can even choose to only

(in junctions) at 5:00 Hrs include the nodes with negative
into simulation pressures (pressure below 0)
70
 head = pressure + elevation
pressure = head - elevation

Indeed, for those nodes we find that

the elevation is larger than the head
value and thus pressure is negative

We could now search for

those junctions using the
browser junction list or
using the Map Finder tool

71
 2. Visualize nodes with negative pressures

Click on map page in the browser and choose what you want to see in the network map
(node and link properties / run results and time period)

72
 Viewing the results in the network map RECAP!

This menu appears when you

click with the right mouse
button on the network map

73
 RECAP!

Adjust legends

The legend editor appears when you click with your right mouse button on the legend

74
 Some quick buttons...
Click on a color to change it

Type any value

75
 What would be a logical legend?

- At least, clearly mark negative pressures

(pressures < 0 m)

- You can directly include the minimum

pressure requirement and the maximum
pressure reuquirement

76
How can we check in which nodes
negative pressures occur?

Move through time / move to the time (Hrs into

simulation) at which the negative pressures occur

77
Negative pressures!
(red color)

78
Extra option:
Add values to nodes
and links in the map

The values that will be shown on the map are the V

node and link properties or run results that you

select on the Map page of the Browser!

79
Extra option: Add flow arrows
- Flow arrows show the direction in which your water is flowing
- it does not matter whether the sign is positive or negative!

80
It does not matter whether the sign is positive or negative,
flow arrows show the real flow DIRECTION!
- The flow sign in pipe 2 is positive, the flow sign in pipe 6 is negative
- However, in both pipes flow is from left to right, therefore arrows point from left to right

81
3. Use the Query tool to find
junctions with negative pressure
When you scroll through time, the
query will change to the correct
no. of items found automatically

The found items are

highlighted in red

82
Now we know where these negative pressure occur...

... but WHY do they occur? Can we explain it?

83
 RECAP!
Possible reasons for negative pressures

1 2 3
1. Start node head + head losses + node elevation → node pressure
(problems with the way the network has been designed or operated)

2. By default, Epanet is demand driven. Negative pressure when portions of the

network can only receive water through links that have been closed off, or if
demand is more than can be supplied by the system.

Create maps with logical legends for node elevations and head losses!

84
 What are the elevations in our network?
Show them on the map!
We can create a table to get a quick idea of which elevations occur in the network...

85
Select all
table
values by
clicking on
the ‘Node
ID’ cell in
order to
copy it!
Paste in Excel (and
search for minimum
and maximum values)

86
Logical legend for elevations

87
 You can follow a similar approach to determine
a logical legend for the unit headloss of links

Large unit headloss

88
 You can follow a similar approach to determine
a logical legend for the unit headloss of links

Conclusions:
- Elevation is not the (only) reason (also negative pressures at lower elevations)
- High unit headloss upstream of junction 5, but not in all pipes of juctions with
negative pressures, so high headloss is not the (only) reason
89
What does this second warning (pump exceeds maximum flow) mean?

90
QUESTION & ANSWER – BLOCK 2

Please ask your questions in the chat!

91
BLOCK 3
Warnings related to pumps
Other common warnings and errors
Conclusions from hydraulic analysis
Attention point: pressures along longer pipes

92
What does this second warning (pump exceeds maximum flow) mean?

93
 WARNINGs related to pumps

EPANET will issue a warning message when a pump is asked to operate outside of the
range of its pump curve:

Pump curve is extended for increasing

flow (leading to negative pressures)

Pump shuts off if the system requires

more head than the pump can produce

94
 Pumps – maximum head

Flow through a pump is unidirectional (flow only possible in one direction) → If system
conditions require more head than the pump can produce, EPANET shuts the pump off.

Negative flow value

95
 Pumps – maximum flow

When exceeding the maximum flow, EPANET does not shut the pump off, but extends
the pump curve → Negative pressures are produced at the downstream junctions.

This can lead to a

negative head value
96
Pump results (negative headloss value)

Normally, pump headLOSS is

negative: the pump ADDS
head (energy) to the system

97
 Pump results (positive headloss value)

If pump headloss is positive,

there really is a LOSS, due to
EPANET continuing the
pump curve with negative
head values
Increased
flow value

This means the pump cannot

handle the amount of flow...
98
Pump head loss is
positive: there really
is a LOSS

This means the pump

cannot handle the
flow (demand)

This was caused by

our increased
demand in junction 5!

99
Conclusions so far
- Negative pressures occur in our system at 5-14 and 16-19 Hrs into simulation
- Due to the higher demands at those times (higher multipliers in the demand pattern)
- Negative pressures NOT only due to elevation (als negative pressures at low elevations)
- At some locations related to large unit headloss upstream (large flow through small
diameter pipe), but not at all locations
- Pump cannot handle the flow, works outside of range (creating negative pressures)

- We used tables, the Query tool and logical legends in our hydraulic analysis!

100
Conclusion on WARNINGs
- They do not necessarily mean that your model is incorrect!
- They are the logical result of all your network input
∙ Analyse the network properties and run results to find explanations of warnings!
∙ If the warnings are unlogical / unexpected, check and (if necessary) correct input
data!
∙ If the warnings are logical / expected, no model correction needed
- Warnings may mean that your system is not designed to meet the demand that is
present in the network

101
Now, we can continue with the real analysis!
- Do we fulfill the guidelines? Do we meet all customer demand?
- To find out, we can do similar analysis (using tables, tools and logical legends) for:
∙ other times into simulation
∙ all other guidelines on pressures, (unit) headloss and velocities
∙ average day and maximum day
∙ etc...

- Or do we have to change network design and/or operation to fulfill the guidelines?

- And if so, how to? What can we adjust to meet the guidelines?

102
Always relate your model and outcomes to reality!
- What do you expect to happen when you run the model?
- Is that indeed what you see happening?
- Is it logical what we see?
- Can we explain warnings?
- What do the result mean for our customers / water supply?

- Is the network design OK or do we need to we improve it?

103
Most common warnings and errors
“Pumps cannot deliver flow or head” → the pump is asked to operate outside the range of its pump curve; if the pump
cannot deliver the head, EPANET will close the pump down, which might lead to portions of the network becoming
disconnected from a water source (WARNING!)
“Network is disconnected” → if there is no way to provide water to all nodes that have demands, e.g. due to closed
pipes; if caused by a closed link EPANET will calculate, but with will give (extremely large) negative pressures as result
(WARNING!); if no connecting links exist it cannot run (ERROR!)
“Negative pressures exist” → when negative pressures occur at junctions with demand; indication that there is a
problem with the way the network is designed or operated (or with your input data...) (WARNING!)
“System unbalanced” → when EPANET cannot converge to a hydraulic solution within its allowed maximum number of
trials; increasing the allowed number of trials or loosening accuracy might help (Hydraulic Options); if unbalanced:
inaccurate hydraulic results (WARNING!)
“Hydraulic equations unsolvable” → if the set of equations that model flow and energy balance in the network cannot
be solved, e.g. when there is no physical link connecting a node with demand to any source of water (or when unrealistic
numbers are used for certain network properties) (ERROR!)

104
 Attention point: Pressures along longer pipes

- We can only check pressure in nodes, but not along pipes!

- If you have long pipes in your network, you may want to consider to split them into
multiple pipes with shorter length with nodes inbetween
- Check the elavtion for these nodes in e.g. GIS / Google Maps / Google Earth

- Especially important for areas with large elevation differences!

· High elevation → attention point for minimum pressures
· Low elevation → attention point for maximum pressures

head = pressure + elevation

pressure = head - elevation

105
 Pressure is only
given for nodes,
not along pipes!

E.g. pipe PP1 has a length of 1968

m, elevation differences over this
pipelength are not considered!

We can solve this issue by

splitting longer pipes into
multiple shorter pipes!

106
How to split a pipe?
You CANNOT simply
add a new junction
(1) and locate it on
the pipe: the pipe
will still run from
the original start
node (SPR1) to the
original end node
(N1) and the new
junction (1) is
‘floating in the air’
(unconnected)!

107
How to split a pipe?
You CANNOT simply
add a new junction
(1) and locate it on
the pipe: the pipe
will still run from
the original start
node (SPR1) to the
original end node
(N1) and the new
junction (1) is
‘floating in the air’
(unconnected)!

108
Auto-Length can only be used when
you have a scaled background map!

109
QUESTION & ANSWER – BLOCK 3

Please ask your questions in the chat!

110
 EPANET module 3

- Q&A: Water demand input / Simple controls / Throttle valves

- Block 1: Network analysis / Guidelines and regulations / Scenarios to model /
Query and Map Finder tools / Maximum day model
- Block 2: Status report / Warnings and errors / Approach for hydraulic analysis /
Negative pressures
- Block 3: Warnings related to pumps / Other common warnings and errors /
Conclusions from hydraulic analysis / Attention point: pressures along
longer pipes

- Questions? Contact [email protected]

111
Schedule of webinar series Hydraulic modelling & EPANET
Five modules (sessions) in two batches:
- 20 & 21 May: Basic hydraulics
- 27 & 28 May: EPANET 1 (introduction to EPANET: workspace, project setup)
- 17 & 18 June: EPANET 2 (data input and model calibration)
- 24 & 25 June: EPANET 3 (analysis of hydraulic modelling results)
- 1 & 2 July: EPANET 4 (network design and improvement / optimization)

Please have EPANET available during all EPANET webinar sessions 1-4!

112
www.witteveenbos.com