The number that matters is the fire-pump suction pressure at the required fire flow, with the source at its lowest credible level and every connected process pump in its actual transition state. A command that stops the process pumps immediately does not prove that flow stops immediately. Rotating inertia, valve travel, check-valve closure, header volume, and control-scan timing continue to affect pressure after the command changes state. This is hydraulics, not logic.
Common fixes that do not prove acceptability
An interlock that trips every process pump when the fire pump starts addresses simultaneous steady-state operation, but it does not establish a reliable fire-water supply. The fire pump may begin drawing before the other pumps coast down, or a failed starter, welded contact, unavailable controller, or valve fault may leave a process path active.
Adding a backflow preventer also does not settle the design. Where a direct water-authority connection exists and the authority permits it, backflow protection may be required at the connection. It introduces pressure loss that belongs in the hydraulic calculation, and it cannot correct inadequate source capacity or an unsuitable shared header.
A large stored volume is not the same as usable fire reserve. Available flow depends on water level, suction geometry, restrictions, entrained solids or air, and the pressure remaining while the fire pump draws. Silence in a basic local code is not approval; the authority having jurisdiction must accept the arrangement against the adopted fire and building requirements.
Hydraulic cause and manifold identity
The description of a common collector that sends treated water to the river creates a decisive ambiguity. Trace the piping on the P&ID and in the field. A header upstream of the process-pump inlets is a shared suction manifold; a header downstream of their outlets is a shared discharge manifold. The two arrangements require different calculations and failure analysis.
On a shared suction manifold, the fire pump and running process pumps compete for source flow. Header friction rises with flow, source level can fall, and local velocity at the intake can increase. The result can be inadequate suction pressure, unstable flow, air ingestion, or loss of pump performance.
On a shared discharge header, check valves and pressure relationships govern reverse flow and cross-circulation. Stopping the process pumps can change the network resistance abruptly, while the fire pump may drive water toward the river unless positive hydraulic separation directs its output into the fire system. A control interlock is not a substitute for the required piping path.
Quantities and approval limits
| Quantity | Why it controls the decision | Where to read or determine it |
|---|---|---|
| Required fire flow and pressure | Defines the operating point the source and fire pump must sustain | Approved fire-protection hydraulic calculation and pump curve |
| Minimum credible source level | Sets static suction head and usable reserve | Reservoir operating records, level instruments, and intake elevation survey |
| Fire-pump suction pressure | Shows whether the pump receives adequate pressure at demand | Calibrated suction-pressure instrument during the flow test |
| Process-pump coast-down time | Defines the overlap after the stop command | Timestamped speed, flow, current, or discharge-pressure trend |
| Valve and check-valve response | Controls reverse flow and transient pressure during transfer | Position feedback, field observation, and pressure trend |
| Source availability | Fire service needs a dependable supply, including loss of normal process operation | Operating history and documented availability assessment for 24/7/365 service |
| Future connected demand | Additional withdrawals can reduce residual pressure | Approved expansion basis and water-supply calculation |
| Motor current | Confirms that the resulting hydraulic operating point does not overload a driver | Starter or drive trend compared with the motor nameplate |
Use the current adopted editions of NFPA 1, , and the IFC as documents to verify with the authority having jurisdiction. The adopted edition, local amendments, water-source classification, and connection topology determine which provisions apply; no general interlock rule resolves those project-specific facts.
Engineering decision path
First establish whether the effluent inventory is legally and physically accepted as a fire-water source. Then test whether the source can supply the required operating point under the worst credible source level and connected-demand condition. Include the transient interval rather than calculating only the final state with every process pump stopped.
Next identify every single failure that can leave the process system connected: loss of control power, failed output, starter failure, manual mode, bypassed interlock, stuck isolation valve, or leaking check valve. If one such failure removes the required fire flow or pressure, the control concept lacks hydraulic independence.
The preferred decision is a dedicated fire-water suction path and controlled reserve accepted by the authority having jurisdiction. If a shared source or manifold remains under consideration, document why a single process fault cannot impair the fire-water path. Treat the arrangement as unapproved until the hydraulic calculation, piping details, control narrative, water-quality implications, and acceptance test are reviewed.
Design and interlock procedure
- Mark the source, every pump suction and discharge, check valves, isolation valves, bypasses, drains, and the river discharge on an as-built P&ID.
- Confirm whether the proposed connection is on a suction header or discharge header by tracing flow direction in the field.
- Obtain the required fire flow and pressure, fire-pump curve, minimum source level, pipe sizes, elevations, valve losses, and process-pump curves.
- Calculate the fire-pump operating point for normal conditions, the lowest credible source level, maximum connected demand, and the transition while process pumps coast down.
- Build the interlock as a secondary protective function: fire-pump start request commands process-pump stops, alarms any failure to stop, and records pump feedback rather than relying only on output-bit state.
- Define manual modes and loss-of-communications behavior. A local process-pump mode must not silently defeat the fire-water response.
- Submit the hydraulic basis, control narrative, failure analysis, and proposed test to the authority having jurisdiction. Where a water-authority connection exists, obtain that authority's connection and backflow requirements before finalizing losses.
Functional verification and recurring pitfalls
Run an accepted flow test with calibrated instruments. Trend fire-pump start request, process-pump run feedback, motor current, header pressures, fire-pump suction and discharge pressure, source level, valve position, and delivered fire flow on one time base. The test passes only when the required flow and pressure remain available throughout the transfer, not merely after pressures stabilize.
Repeat the relevant test state at the lowest practicable source level or use a reviewed calculation to account for the untested head difference. Verify alarms for a process pump that fails to stop, missing valve feedback, and low suction pressure. Inspect for reverse flow, intake vortexing, air entry, pressure oscillation, and unintended discharge toward the river.
Recurring errors include accepting a stop command without run feedback, omitting pump coast-down from the sequence, treating check valves as perfect isolation, calculating with normal rather than minimum source level, and adding a backflow device without including its pressure loss. Frequent process-pump trips and restarts also impose electrical and thermal duty; compare the expected sequence frequency and current profile with the starter, drive, and motor documentation.
FAQ
Why does stopping the process pumps not protect fire-pump suction?
The stop command changes control state before shaft speed and flow reach zero. Measure the interval from fire-pump request through process-pump rundown and pressure stabilization, then include that overlap in the hydraulic calculation.
Why does a large effluent volume not guarantee adequate fire flow?
Usable supply depends on minimum water level, intake geometry, pipe losses, water condition, and residual suction pressure at the required flow. Confirm those quantities by calculation and an accepted flow test.
Why does a backflow preventer not make a shared manifold acceptable?
It controls flow direction at a permitted connection but adds pressure loss and does not create reserve capacity or hydraulic independence. Include its documented loss in the operating-point calculation.
No interlock alone demonstrates source reliability or hydraulic performance. Review the adopted edition together with NFPA 1, the IFC, local amendments, and the authority having jurisdiction's decision.
Stop the design or test if the manifold identity is unresolved, required suction pressure cannot be maintained, reverse flow occurs, or a single process fault defeats fire flow. Escalate the P&ID, hydraulic calculation, transient trends, and failure results to the authority having jurisdiction, the responsible fire-protection engineer, and the fire-pump manufacturer's official support channel.