A surge study is judged by its report, and reviewers send reports back for the same few reasons: they cannot see the model basis, the profile is missing, results are shown only at the pump, or the protection is described without the settings anyone needs to build it. Here is why the profile matters. The 12 km reference main, with the vessel that protects it on a flat profile (3.5 m³ of gas in a 20 m³ shell), was rerun on an undulating profile with two high points. The pressure history at the pump still looks healthy, never below +4.8 m. Along the line the pressure falls to −5.8 m at the 7.2 km high point, and 8.5 km of main is below the +3.0 m criterion. A report that showed the pump history, or the envelope as head rather than pressure, would have passed it. This article sets out what we put in a surge study, how we present it, and the checklist we use when reviewing someone else's.

1 · What the report has to do

A surge study supports decisions that are expensive to change later: the protection type and size, the pipe classes, the pump and valve specifications, the station layout and the operating rules [1][2]. Its report has three readers, and each needs something different.

We write the report so that each reader can find their part without reading the rest, and so that every number in the conclusions can be traced back to a run.

2 · The structure we use

Our surge reports follow the same order on every project. The order matters: the basis and the checks come before any result, so that a reader knows what the results are worth.

Surge study report: contents and what a reviewer looks for in each part
PartContentsWhat the reviewer looks for
SummarySystem, governing event, recommended protection with sizes, key limits met, open itemsOne page; numbers match the body; open items are named
System descriptionRoute, profile, pipe materials and classes, pumps, valves, reservoirs, operating modesA profile drawing with chainages and elevations; the weakest component classes
CriteriaMaximum and minimum limits and their sources: EN 805 terms, product standards, owner's limitsEach limit named and referenced, in EN 805 terms where they apply [5] (see the pipe's real limits)
Model basisSoftware and version, network, wave speeds, friction, pump data, valve data, cavity model, time step, run durationThe data register and assumptions register; the model checks
ScenariosThe matrix of events, operating points and protection statesOccasional and recurring events; protection out of service; the governing case justified
Results without protectionEnvelopes and histories for the governing eventsWhy protection is needed, and where
Protection designOptions compared, the selected scheme, its sizing runsA device schedule complete enough to procure and build
Results with protectionEnvelopes along the whole line, histories at critical points, extreme tablesPressure, not head; every high point; margins against each limit
SensitivityWave speed, pump data, device settings, model optionsWhether the decision survives the uncertainty
OperationInterlocks, start and stop sequences, restart after a trip, maintenance of the protectionRules an operator can follow
AppendicesModel files, input listings, run log, data sourcesEnough to rerun the study

3 · Model basis: the data and assumptions registers

The single most useful table in a surge report is the one that lists every input with its source and status. Reviewers trust a model whose weak points are written down, and distrust one where they have to dig for them. For the reference main at tender stage, ours reads like this:

Data and assumptions register, reference main (extract)
InputValue usedSourceStatusSensitivity tested
ProfileGround levels at 7 points, 0–12 mRoute surveyconfirmed–
PipeDN800 ductile iron, C25 barrel, PN16 fittingsDesign drawingsconfirmed–
Wave speed1,050 m/sKorteweg, K9 wall, cement liningcalculated±10 % (see wave speed)
Friction40.2 m at 0.70 m³/sSteady-state modelcalculatednew and aged pipe
Pump inertia44 kg·m² totalCorrelation (HAMMER calculator)assumed25 to 88 kg·m²
Pump characteristicNs 46, closest library curve 25Duty pointassumedcurve 94 as bracket
Check valveIdeal, closes at zero flowNone yetassumedreal closure once selected
Vessel gas lawPolytropic, n = 1.2Standard practicecalculatedn = 1.0 and 1.4
Cavity modelVapour cavity; gas cavity as checkModel optioncalculatedboth models on cavitating runs
Time stepSuggested step, length adjustment < 5 %Model checkconfirmedhalved step
Run duration150 sModel checkconfirmedextended to 225 s

Each “assumed” line is an open item in the summary and, where the decision depends on it, a hold point in a specification. The model checks themselves (time step, adjustment, halved step, run duration, Joukowsky test) are set out in Is your HAMMER run right?, and the pump data questions in Pump data for a pump trip.

4 · The scenario matrix

A report that runs one pump trip has not shown that the trip governs. We lay the scenarios out as a matrix of events against operating states and protection states [1][3]:

Scenario matrix for a pumped transmission main (reference main as the example)
EventTypeOperating statesProtection statesRuns
Power failure, all pumpsoccasionalmaximum flow, minimum flow, maximum reservoir leveldesigned, vessel isolated, low gas9
Single pump trip, others runningoccasionalmaximum flowdesigned1
Normal pump startrecurringfirst pump, last pumpdesigned2
Normal pump stoprecurringlast pump, one of severaldesigned2
Line valve closureoccasionalmaximum flowdesigned1
Restart after a tripoccasionalline partly drained, vessel refillingdesigned1
Sensitivity on the governing case–wave speed ±10 %, inertia range, curve bracket, gas law, halved stepdesigned8

That is 24 runs for a single main. Each is a scenario in the model with a clear name, and the report says which run governs each side of the envelope and why. The scenarios themselves are described in Surge Scenarios in Pumping Stations; what matters here is that the matrix appears in the report, with the run that governs each limit marked.

5 · Presenting the envelope: pressure along the profile

The envelope is the most important figure in the report and the one most often drawn badly. Three rules:

Here is the reference main of the surge series [6] laid on an undulating profile (high points of 10 m at 2.5 km and 12 m at 7.2 km), run three ways.

The same trip shown as head and as pressure
Reference main on an undulating profile, all pumps tripping. Method-of-characteristics model with a vapour cavity model, 100 m reaches, 150 s. Head view: HGL envelopes with the pipe profile and the steady HGL. Pressure view: pressure head envelopes with the limits. Lengths counted on the 100 m grid.
The second is the vessel that passes on a flat profile.
Same results, two ways of drawing them.
1 bar = 10.21 m.
Lowest pressure
–
Where
–
Lowest at the pump
–
Highest pressure
–
Line below +3.0 m
–
Verdict
–

With the flat-line vessel the head view looks reassuring: the minimum HGL never falls below +4.3 m above datum, everywhere above the pipe on the chart. The pressure view shows what the head view hides: the pressure is −5.2 m at the 2.5 km high point and −5.8 m at 7.2 km. Switch to the design vessel and the lowest pressure is +3.2 m at 2.5 km. The pump reads +12.0 m, nearly four times as much. The maximum is 89.9 m at the pump, well inside the 136 m project limit, because the larger gas volume also softens the upsurge.

6 · Presenting time histories: at the critical points

Time histories show how an event develops: when the minimum arrives, whether it is a single dip or a sustained low, how fast the protection responds. They belong at the points that govern, not only at the pump. We always include the pump or vessel node, every high point that comes within a few metres of the criterion, and the point of the overall minimum and maximum.

Pressure history at a chosen report point
Same runs as above. The grey trace is the pump node for comparison. 150 s runs, traces thinned for the page; readouts from the full runs.
Chainages of the report points in the model.
As in the profile chart.
Lowest here
–
Highest here
–
Lowest at the pump
–
Pump history alone says
–
This point says
–

At 7.2 km the flat-line vessel holds the pressure below +3.0 m for a long stretch of the first downsurge and reaches −5.8 m. The pump history for the same run never goes below +4.8 m. A report showing only the pump would conclude the opposite of the truth.

7 · The device schedule

The protection must be described completely enough to be specified, procured, installed and commissioned without going back to the model. For the design vessel on this profile:

Device schedule: hydropneumatic vessel at the pump station (example)
ItemValueBasis
Total shell volume30 m³Largest gas volume 23.5 m³, kept below 80 % of the shell
Gas volume at steady flow7.0 m³Smallest gas volume giving +3.0 m everywhere is 6.91 m³; rounded up
Gas pressure at steady flowabout 9.35 bar absolute (95.3 m)85.0 m at the vessel plus atmosphere
Water volume at steady flow23.0 m³Normal operating level for the level controls
ConnectionDN400 with differential orificeLoss coefficient 2.0 out of the vessel, 10.0 into it
Maximum pressure at the vessel89.9 m (8.8 bar)Design trip; vessel design pressure set above it, PN16
Level and gas controlsHigh, normal and low levels; compressor or gas chargingTo hold 7.0 m³ within a tolerance tested in the sensitivity runs
Air valves at 2.5 and 7.2 kmFor filling and drainingLowest pressures in the design trip +3.2 and +7.1 m: they do not open in the trip
Check valveFast-closing, non-slamReverse velocity at closure to be confirmed against the selected valve

Each figure in the schedule should point to the run that justifies it. A schedule that gives the vessel volume without the gas volume, pressure and connection loss cannot be built to the design; the vessel sizing article and the differential orifice article show how sensitive the result is to each.

8 · Operating rules and interlocks

The protection only works if it is in service and set correctly, so the report ends with rules that go into the operating manual and the control philosophy:

9 · The reviewer's checklist

This is the list we work through when reviewing a surge study. Tick what the report you are reviewing actually contains; the chart shows which parts are weak.

Surge study review: completeness by part
Each item carries a weight of 1, or 2 for items that on their own can invalidate a conclusion (marked ★). Bars show the weighted share of each part that is present. A report with any ★ item missing goes back, whatever its total.
Overall
–
★ items missing
–
Weakest part
–
Decision
–

The ticks start at what a typical first submission contains in our experience: a model description, a pump trip at the pump node and a vessel volume. That scores 17 %, with nine of the ten starred items missing. Nothing here is saved; reload the page to start again.

10 · Why studies are sent back

In our reviews the same problems come up again and again. Most concern presentation and evidence rather than hydraulics:

11 · Getting the report out of Bentley HAMMER

Field names differ slightly between versions; these follow the current documentation [4].

  1. Name scenarios and alternatives as they will appear in the report’s scenario matrix, so every figure can carry its scenario name.
  2. Define profiles along the whole main with the ground or pipe level, and plot the maximum and minimum pressure envelopes for each governing scenario.
  3. Set report points at the pump, the vessel and every high point before the run, and turn on Generate Animation Data, so histories exist where they are needed.
  4. Export the extremes with their locations from the transient results tables, and build the extremes table from them rather than reading graphs.
  5. Copy the calculation options into the model basis: time step, adjustment, run duration, friction method and vapour pressure.
  6. Keep the run log with warnings, including any wave-speed or length adjustment warning, and say in the report how each was dealt with.
  7. Archive the model with the report, with a list of scenarios and the run that supports each figure.

12 · Checklist for the author

Surge analysis practice series
  1. Is your HAMMER run right? Time step, adjustment and run duration
  2. Pump data for a pump trip: inertia, specific speed and four-quadrant curves
  3. Reading the surge envelope against the pipe's real limits
  4. The surge study report: what to deliver and what a reviewer checks
The protection devices themselves are covered in the surge protection design series.

References & standards

  1. Boulos, P.F., Karney, B.W., Wood, D.J. & Lingireddy, S. “Hydraulic transient guidelines for protecting water distribution systems.” Journal AWWA, 97(5), 2005: the scope of a transient study, data needs, scenarios and protection strategies.
  2. Thorley, A.R.D. Fluid Transients in Pipeline Systems, 2nd ed. Professional Engineering Publishing, 2004: the events to consider for pumped mains and the presentation of transient results.
  3. Wylie, E.B. & Streeter, V.L. Fluid Transients in Systems. Prentice Hall, 1993: transient events, boundary conditions and the method of characteristics behind the runs in this article.
  4. Bentley Systems. OpenFlows HAMMER documentation: scenarios and alternatives, profiles and transient envelopes, report points, animation data, results tables and calculation options.
  5. EN 805 Water supply. Requirements for systems and components outside buildings: the pressure terms and limits a surge report should state.
  6. Abokhatwa, M. Surge protection design series, abokhatwa.com, 2026: the reference main, the vessel sizing method and the verified MOC solver used for the runs in this article.
#SurgeAnalysis #WaterHammer #HydraulicTransients #SurgeStudy #TransientReport #DesignReview #EngineeringReview #BentleyHAMMER #OpenFlowsHAMMER #SurgeVessel #DeviceSchedule #AssumptionsRegister #ScenarioMatrix #PressureEnvelope #HydraulicGradeLine #PipelineProfile #HighPoint #AirValves #OperatingRules #Interlocks #PumpStation #TransmissionMain #PipelineDesign #WaterEngineering