Fire fighting network surge analysis exists for one reason: to find the pressure spike before it finds a weld seam. A deluge valve slams shut during a routine test on an offshore platform ring main. Three seconds later, a transient wave races back through six hundred meters of piping, and a flange nobody flagged as high-risk fails downstream.
Most O&G projects treat surge evaluation as a formality bolted onto network sizing calculations. In practice, it is a distinct engineering discipline with its own scenario set, its own standards, and its own failure modes that sizing calculations never touch. A firewater network is sized to deliver flow and pressure at the hydrant or monitor. It is rarely sized to survive the transient created when a fire pump trips, a deluge valve snaps closed, or an operator restarts a pump into a network still ringing from the last event.
That gap between steady-state design and transient reality is where surge analysis earns its place in the project scope, not as an afterthought at FEED close-out, but as a parallel workstream from the moment the network layout is fixed. This article covers what causes these surges, how the analysis is actually performed, what GCC, India, and Southeast Asian projects require for regulatory acceptance, where teams get the scope wrong, and how surge risk gets mitigated without redesigning the network from scratch.
What Causes Pressure Surges in Fire Fighting Networks
Pressure surges in fire fighting networks occur when a rapid change in flow velocity converts kinetic energy into a pressure wave that travels through the pipe wall faster than the fluid itself moves. Deluge valve closure, fire pump trip, and pump start-up against a full network are the three most common triggers. NFPA 24 recognizes each as a design-relevant transient event.
A closing deluge valve is the most underestimated trigger in the entire network. Closure times under two seconds are common on quick-opening deluge systems, and the resulting deceleration generates a pressure wave proportional to the fluid’s velocity change and the pipe’s wave speed. Steel firewater piping typically carries a wave speed between 1,000 and 1,400 meters per second, so a velocity drop from 3 m/s to zero can generate transient pressures several times the static operating pressure. Column separation adds a second failure mode: at elevated points in the network, the initial pressure drop can pull absolute pressure below vapor pressure, and the resulting vapor pocket collapses with a secondary hammer event that often exceeds the first. Left unassessed, this secondary event is what actually ruptures the pipe, not the initial closure.
A fire pump trip produces a different signature entirely. When a pump running against a closed or nearly closed system loses power, flow reversal through the pump can occur within a fraction of a second, and a check valve slamming shut against that reverse flow generates its own transient spike independent of the deluge valve behavior. Diesel-driven fire pumps complicate this further because engine coast-down is slower and less predictable than an electric motor trip, extending the transient window. Networks with jockey pumps cycling against the same header add a low-amplitude, high-frequency pressure ripple that a transient study must separate from the primary event to avoid false-positive mitigation recommendations. Treating pump trip and valve closure as a single generic water hammer scenario misses both failure signatures.
How Fire Fighting Network Surge Analysis Is Performed
Fire fighting network surge analysis models the entire ring main hydraulically under transient conditions, evaluating rapid valve closure with and without pump tripping, pump trip, pump start-up, pump trip followed by restart, and deluge valve closure as discrete scenarios. Each scenario produces a pressure-time history at critical nodes, checked against the pipe’s allowable transient pressure rating.
The methodology itself is not proprietary. DEP 31.38.01.25-Gen and DEP 31.38.01.26-Gen, the design and engineering practice documents most GCC and Southeast Asian operators reference for surge analysis scope, specify which scenarios must be modeled and how transient pressure limits are set relative to the pipe’s rated working pressure. A competent surge study begins with an accurate hydraulic model of the as-built or as-designed network, not a simplified representation, because pipe length, elevation change, and fitting count all affect where the pressure wave reflects. From there, each scenario in the table below is run independently, and the governing case, the one producing the highest transient pressure at the most vulnerable node, becomes the basis for any mitigation recommendation.
| Surge Scenario | Trigger | Typical Consequence if Unassessed |
| Rapid valve closure (no pump trip) | Deluge valve closing in under 2-3 seconds | Localized pressure spike at valve, joint failure risk |
| Rapid valve closure with pump trip | Combined valve closure and pump loss | Compounded transient, often the highest peak pressure case |
| Pump trip | Sudden loss of driver power | Flow reversal, check valve slam |
| Pump start-up | Pump start against a full, pressurized network | Water column impact at discharge header |
| Pump trip followed by restart | Automatic or manual restart into a still-transient network | Superimposed pressure waves, unpredictable peak location |
| Deluge valve closure | Valve closing after system activation or test | Column separation risk at elevated piping sections |
Engineering judgment governs which nodes get instrumented in the model and which simplifying assumptions are acceptable. That judgment is what separates a defensible surge study from a checkbox exercise run once and filed away. iFluids applies this same scenario-based methodology across our fire fighting network surge analysis service and our broader pipeline surge analysis standards work, adapting scenario weighting to firewater-specific triggers like deluge valve response time rather than the pigging and shutdown events that dominate product pipeline studies.
Recognized for excellence.
PROJECTS DELIVERED ACROSS THE GLOBE
Firewater Surge Analysis Requirements in GCC, India, and Southeast Asia
GCC operators generally require fire fighting network surge analysis as part of civil defence and process safety approval packages, referencing NFPA 24 for private fire service main design. Indian projects layer OISD-116 requirements for firewater network design on top of NFPA provisions. Southeast Asian projects typically follow whichever standard the operator’s corporate engineering practice specifies, most often NFPA or DEP-based documents.
Qatar Civil Defence approval packages for onshore and offshore facilities routinely ask for a documented transient analysis before final network acceptance, particularly where deluge systems protect process areas with a high consequence of fire escalation. ADNOC and KAHRAMAA-governed projects in the UAE follow a similar pattern, tying surge study submission to the same process safety review gate as HAZOP close-out. NFPA 24 governs private fire service main design broadly across these jurisdictions, and OISD-116 adds firewater network sizing and layout requirements specific to Indian onshore and offshore facilities. Neither standard prescribes a transient analysis methodology directly, leaving the surge scope to be defined by project specification, most often referencing DEP or an equivalent operator standard.
A network compliant with OISD-116 on a steady-state basis can still fail a transient check. Regulators reviewing GCC and Indian projects increasingly expect that gap to be closed before commissioning, not discovered during it. Southeast Asian operators, particularly in Malaysia and Indonesia, rarely maintain a single unifying standard for firewater surge and instead default to whatever the EPC contractor’s corporate practice document requires. This makes early clarification of the governing document, not just the governing code, essential before scope and fee are fixed.
Common Mistakes and Misconceptions in Firewater Surge Evaluation
The most persistent misconception treats fire fighting network surge analysis as optional if the network passes steady-state hydraulic sizing. A network can meet flow and pressure targets at every hydrant and still fail catastrophically under a fast valve closure or pump trip, because sizing and transient response are governed by entirely different physics.
Three mistakes show up repeatedly across the projects we review. The first is scoping surge analysis after piping isometrics are frozen, leaving no room to adjust valve closure time or add a surge vessel without a costly rework. The second is running only the deluge valve closure scenario because it is the most obvious trigger, and skipping pump trip and restart cases that frequently produce the governing pressure. The third is applying a generic wave speed value from a textbook rather than calculating it from the actual pipe material, wall thickness, and fluid properties in the as-built network.
| Project Condition | Is Surge Analysis Mandatory? |
| Deluge system protecting a high-consequence process area (GCC/India regulatory requirement) | Mandatory |
| Long firewater ring main with multiple elevation changes | Mandatory, column separation risk |
| Fire pump with automatic restart on low pressure | Mandatory |
| Small, single-elevation yard hydrant network, manual valve operation only | Discretionary, engineering judgment applies |
| Network unchanged from a prior facility with an existing accepted surge study | Discretionary, verify no scope or layout change first |
None of these mistakes are a modeling failure. They are scoping failures that happen before the modeling starts, and they are the reason two networks with identical steady-state hydraulics can produce completely different results in a fire fighting network surge analysis.
Best Practices for Mitigating Surge Risk in Fire Fighting Networks
Mitigating the risk identified in a fire fighting network surge analysis starts with slowing the trigger, not strengthening the pipe. Extending deluge valve closure time, staging pump trip sequencing, and specifying surge relief or air vessels at governing nodes typically cost less than upgrading pipe class or adding supports across an entire ring main.
Extending valve closure time from two seconds to eight or ten seconds, where the fire protection design allows it, is often the single cheapest mitigation available, because it directly reduces the rate of velocity change that drives the pressure wave. Where closure time cannot be extended without compromising deluge response, surge relief valves set just above operating pressure at the governing node absorb the transient without affecting steady-state performance. Staggered pump start sequencing, rather than simultaneous start of multiple fire pumps against a full network, spreads the transient load across a longer window and lowers peak superimposed pressure. Air or bladder-type surge vessels remain effective at elevated sections prone to column separation, though they require ongoing maintenance verification to stay charged and functional.
Pipe upgrade should be the last option considered, not the first. Every mitigation option carries a maintenance or operational cost, and the right combination depends on the governing scenario identified in the surge study, not a standard checklist applied uniformly across every project.
Frequently Asked Questions
Yes, for most GCC and Indian oil and gas projects with deluge protection or automatic fire pump restart, surge analysis is required as part of process safety and civil defence approval. NFPA 24 and project-specific documents such as DEP 31.38.01.25-Gen define the applicable scenarios. Networks without these features may still need a documented engineering judgment rationale if the analysis is skipped.
Water hammer occurs when the deluge valve’s closing or opening time is short relative to the time a pressure wave takes to travel the pipe length and reflect back. Fast closure decelerates the fluid column abruptly, converting velocity into pressure. Longer ring mains and higher flow velocities both increase the magnitude of the resulting transient spike.
Yes. At high points in the network, a closing valve or tripping pump can drop local pressure below the fluid’s vapor pressure, forming a vapor pocket. When the pocket collapses, it generates a secondary pressure spike that frequently exceeds the original transient. Elevated sections with limited air release provisions are the most vulnerable points in a typical ring main.
NFPA 24 governs private fire service main design across most GCC projects, while OISD-116 adds firewater network sizing and layout requirements for Indian onshore and offshore facilities. Neither standard prescribes a full transient analysis methodology directly. Project specifications, often referencing DEP or an equivalent operator practice document, typically define the surge scenario list and acceptance criteria.
Extending deluge valve closure time, staggering pump start sequencing, and installing surge relief valves or air vessels at governing nodes are the most common mitigation options a fire fighting network surge analysis typically recommends. Each targets the transient at its source rather than upgrading pipe class across the network. Selecting the right combination depends on which scenario governs in the surge study results.
For deluge-protected process areas and facilities under Qatar Civil Defence, ADNOC, or KAHRAMAA-governed approval, surge analysis is typically mandatory before final network acceptance. Smaller yard hydrant networks with manual valve operation only may qualify for a documented engineering judgment exemption instead. The determining factor is usually the presence of automatic actuation, not network size alone.
Preventing water hammer starts with controlling valve closure time and pump trip response rather than reinforcing pipework after the fact. Slower deluge valve actuation, staged pump sequencing, and surge relief devices at high-risk nodes address the transient at its source. A documented surge study identifies which specific combination is needed for a given network before commissioning.
Conclusion
Fire fighting network surge analysis is not a compliance formality bolted onto network sizing. It is a distinct engineering discipline that identifies the governing transient scenario, whether that is a closing deluge valve, a tripping pump, or a restart into an already-stressed network, before it becomes a failed joint or a collapsed section of elevated piping.
GCC and Indian projects increasingly tie surge study acceptance to the same process safety gate as HAZOP close-out, and Southeast Asian projects follow whichever governing document the corporate engineering practice specifies. The mistakes that undermine most studies happen at the scoping stage, not the modeling stage: isometrics frozen before the surge scope is set, incomplete scenario coverage, and generic assumptions substituted for as-built data.
If your project has a deluge-protected process area, an automatic pump restart function, or a ring main with significant elevation change, the transient behavior deserves the same engineering attention as the steady-state hydraulic design. Speak to our team about scoping a fire fighting network surge analysis for your project, or review our surge analysis case studies for examples of governing scenarios identified on comparable networks.
