Ask three engineers to size a fire water system for the same process unit and you will get three different numbers. Not because the hydraulics are disputed, but because they made different assumptions about what happens simultaneously.
The single-largest-demand trap
The intuitive approach is to find the largest single fire scenario on the plot, size the system for it, and move on. On a refinery or a petrochemical complex this is almost always wrong, and it is wrong in the expensive direction — sometimes oversized, more often dangerously undersized.
The governing case is not one fire. It is a fire plus everything the fire strategy requires to run at the same time:
- the suppression demand for the incident itself
- cooling water for exposed equipment within the radiation envelope
- hydrant and monitor streams for manual intervention
- any deluge that the detection logic will open automatically on adjacent units
- the hose reel allowance the local authority requires regardless
Add those and the number moves. On tank farms it can double.
What defines the envelope
The radiation calculation decides which neighbouring equipment needs cooling, and therefore how much of the plant is inside the demand. This is the step most often skipped: cooling extent is taken from a spacing table rather than from a calculated incident radiation level.
The consequence is predictable. If the table is more conservative than the calculation, the client pays for water and pumping capacity that no scenario requires. If it is less conservative — which happens whenever geometry is congested or the inventory is unusually hot — the system is sized for a fire that cannot occur while the real one is unprotected.
Duration is a design decision, not a lookup
Stored volume is demand multiplied by duration. Duration is where standards diverge most, and where the operator’s own emergency response capability legitimately changes the answer. A facility with a trained on-site brigade, a confirmed second source and a credible depressurisation route is not the same facility as one relying on a municipal response an hour away — even if the two have identical piping.
Stating that assumption explicitly, in the fire strategy, is what makes the stored volume defensible later. Leaving it implicit is what makes it indefensible when someone asks.
What this means in practice
Three questions settle most fire water arguments before they start:
- Which simultaneous operations are we required to assume, and who decided?
- What radiation level defines the cooling envelope, and was it calculated or assumed?
- What duration are we storing for, and what does that assume about response?
If those three are answered and written down, the hydraulic calculation is arithmetic. If they are not, the calculation is a guess with decimal places.
Mainstream Petrochemical Instruments FZE provides fire safety engineering for high-hazard industrial facilities. This article is general technical commentary and is not a design recommendation for any specific facility.