Pump Control Hydronics
On the load piping lesson we built up the picture of a variable-flow hydronic system from the load side: every coil throttled by a two-way valve, system flow rising and falling with the building's demand. On the VFDs lesson we walked through the box that lets a pump run at any speed you ask for. This page is the bridge between the two — how does the BMS decide what speed to ask for? The short answer is "by watching a pressure sensor in the loop and slowing the pump down until the building barely notices." The long answer is everything below.
Constant-Speed Pumps — The Simplest Case
Before we get to the variable-flow story, name the thing it replaces. A constant-speed pump is exactly what it sounds like: a motor wired across the line, running at 60 Hz any time it's energised. The "control" surface from the BMS is one binary point — start it or stop it. There's no speed reference, no setpoint, no curve to live on. The pump produces whatever flow the system happens to demand at its single fixed operating point, and that's the day.
This works fine as long as the system wants a constant flow. Old gravity-converted boiler loops with three-way valves at every load (constant system flow by design — that's the whole point of a three-way) sit at one operating point all day; a constant-speed pump is a sensible match. The problem shows up when constant-speed pumping meets the modern variable-flow building: every load on two-way valves, every valve throttling closed at part load, and the pump keeps pushing the same volume at the same head into a system that doesn't want it. Excess pressure dumps across the nearly-closed valves; the energy goes into noise and wear. And if every valve closes far enough at the same time and there's no bypass anywhere, you get a real failure mode — deadhead, where the pump spins against a closed loop with no flow path. We'll come back to it.
The protection against the constant-speed-pump deadhead is the differential pressure bypass valve at the far end of the loop — when system pressure climbs past a threshold (i.e. all the loads are closing in), the DPBV cracks open on its Δp setpoint and gives the pump somewhere to go. It's a mechanical fix for a control problem that variable-speed pumping solves a different way: don't push pressure the system isn't asking for in the first place. That's the rest of this page. (A variable-flow system carries the same deadhead risk but answers it with a minimum-flow bypass instead — sized to hold a flow floor rather than open on a pressure setpoint, since the VFD already caps loop Δp.)
Pump Curve and System Curve — The Operating Point
Two facts about a centrifugal pump — the kind on every hydronic system you'll touch — that are worth carrying around.
- A pump has a curve, not a flow rating. At zero flow (everything closed in front of it), the pump generates its maximum pressure — its shutoff head. As you let flow open up, head drops along a downward-curving line. At the right end of the curve — wide open, no system resistance — flow peaks and head falls toward zero. The pump can sit anywhere along that line; what it does depends on the system in front of it.
- A piped system has a curve too. Friction losses through pipe, fittings, valves, and coils rise with the square of flow. A loop with all valves wide open has a low, shallow system curve; throttle the valves and the curve gets steep — same flow takes more head to push through.
Where the two curves cross is where the pump actually runs — the operating point. It's not a number the engineer picks; it's where physics settles. Open the valves, the system curve flattens, the intersection moves right and down (more flow, less head). Close them, the system curve steepens, intersection moves left and up (less flow, more head). The pump rides its curve up and down as the building demands.
Drag both sliders below to see this in action. The thicker blue line is the pump curve at the chosen speed; the dim line is the same pump at full speed for reference. The green parabola is the system curve at the chosen valve position. The dot is where they meet — the operating point.
Two things to notice as you push the sliders around. First, with the pump at 60 Hz and the valves closing, the operating point walks up and left — flow drops, but head climbs hard. That's the constant-speed-pump problem; the pump doesn't care that the building stopped asking, it just pushes against the new resistance. Second, sliding the pump speed down at a constant valve position moves the operating point along the system curve — flow falls roughly with speed, head falls roughly with speed squared, and the cube-law shaped power readout drops faster than either. The pump is doing less work because the building asked for less, and the math is in our favour.
How a VFD Moves the Operating Point — Affinity Laws
The math behind that "the pump curve scales when speed changes" move is the affinity laws. Three short statements that hold across every centrifugal pump and fan you'll touch, and they're the reason VFDs are everywhere:
Affinity laws — pump speed scaling
- Flow scales with speed. Q₂ / Q₁ = N₂ / N₁
- Head scales with speed squared. H₂ / H₁ = (N₂ / N₁)²
- Power scales with speed cubed. P₂ / P₁ = (N₂ / N₁)³
That last one is the same cube law from the VFDs page, viewed from the pump side — drop the speed to 70% and the power needed for the duty drops to about 34%. The same equipment moving along its system curve.
There's a useful gotcha buried in the second law. Head is what overcomes elevation and friction in the loop, and on a closed loop the elevation contribution is zero (water gives back what it climbs). What's left is friction, which itself scales as Q² — same square. So as long as the system curve looks like H = R·Q², the operating point at lower speed walks neatly along it: lower speed, lower flow, much lower head, way lower power. The whole "VFD saves a fortune on the system pump" pitch is one neat triangle of arithmetic, no fudge factors.
Two caveats worth holding. Open-loop systems — cooling towers, irrigation, anything that moves water uphill from a sump — have a fixed static-head component the affinity laws don't reduce; the pump still has to climb the elevation no matter how slowly it goes, so the savings shape changes. And on a real drive, inverter and motor losses chip a few points off the cube-law theoretical at low speed. The shape is right; the absolute numbers shade conservative.
DP-Based Control — Sensor at the Far End of the Loop
So the BMS has a VFD with a speed-reference input. What does it modulate against? The answer that's overwhelmingly common today is a differential pressure sensor wired into the loop, with the BMS running a PID loop that holds DP measured equal to a DP setpoint. Building demands more flow, valves open, DP drops, pump speeds up. Building demands less, valves close, DP rises, pump slows down. The feedback is direct and physical — the pump answers to the building, not to a clock.
Where the sensor lives matters. Two common choices:
- At the pump (local DP). Cheap, no field wiring beyond the pump panel. Reads pump discharge pressure minus suction pressure — basically the head the pump is producing. Holds the pump output near a setpoint regardless of where in the building demand is coming from. The catch: it tells you nothing about what the far end of the loop is feeling. If the loop's friction climbs (dirty strainer, valves throttling), local DP looks fine while the worst-case load gets starved.
- At the hydraulically most-remote point (remote DP). A field-mounted sensor wired across the supply and return mains at the far end of the loop — usually beyond the last big load. Reads the pressure available to the worst-case load. The pump's job becomes "give the worst-case load at least this much DP," which is the variable the building actually cares about. Almost always the better choice on anything bigger than a small system.
Below: the layout. Pump on the left with a VFD; supply main feeding three two-way loads; return main coming back; remote DP sensor wired across supply and return at the far end. The pump's speed reference is whatever a PID loop running off that DP sensor produces.
On a real job the field-mounted sensor is usually a wet-tap differential transducer with two stainless capillaries running back to a transmitter on the BMS network — BACnet, Modbus, or 4–20 mA hard-wired back to the same controller running the pump PID. Calibrate it against a hand gauge during commissioning and check it again on the second-year tune-up; transducers drift, and a drifted DP sensor is exactly the kind of slow leak in performance nobody notices for a season.
DP Setpoint Reset — Squeezing the Last Bit
Fixed-DP control is already a big improvement over constant-speed pumping. But it leaves something on the table: the DP setpoint is sized for the worst-case load condition (peak demand, every valve open enough to need that pressure to pass design flow). The vast majority of operating hours look nothing like that — most of the time most of the valves are throttled back, and the pump is producing more pressure than any load actually needs. The remaining pressure just gets dropped across the throttled valves.
DP setpoint reset (also called valve-position reset, or most-open-valve reset) is the sequence that closes that gap. The BMS reads back the position of every modulating valve on the system and resets the DP setpoint downward until the most-open valve in the building has opened to about 95% — meaning that valve is doing essentially no throttling, and the pump is producing exactly enough pressure for the worst-case load right now. Every other valve is opened wider than it would be at the fixed setpoint, and the pump runs slower. Slower pump, less head, less head squared, way less power. Cube law one more time.
The widget below has five identical loads with two-way valves, fixed at the same demand for simplicity. Move the demand slider to vary how much heat (or cooling) the building is asking for. Toggle between fixed DP and reset DP to see the difference at part load. Watch the valves open up in reset mode, the pump's Hz drop, and the power readout collapse.
The reset can be smarter than this widget makes it look. Real installations have non-uniform demand — one zone is calling hard, the others are coasting — and the most-open-valve logic shines exactly there: the pump satisfies the one zone that's working and lets the rest sit nearly idle, instead of pressurising the whole loop to the worst-case zone's setpoint. There's an upper limit (the setpoint can't go below what it takes to push design flow through pipe friction alone — at some point you really do need to make pressure to move water through copper) and a lower limit (the BMS holds a small minimum setpoint so the loop never deadheads), but in the middle this is where most of the energy story lives.
Lead/Lag and Parallel Pumps — A Note
Most real systems have more than one pump — at minimum a primary plus a standby for N+1 redundancy, often a pair (or three) of variable-speed pumps in parallel staged up and down as demand climbs. The sequence patterns that govern which pump runs when, how staging transitions are bumpless, how runtime gets rotated for even wear, how an end-of-curve protection trips before a pump finds itself drowning the system — that's its own topic, and it's all sequencing rather than pump-control proper. Worth flagging that it exists; not the question this page is answering.
The short version: parallel variable-speed pumps run at the same speed reference (one DP loop, two motors), and a staging sequence brings the lag pump online when the lead is running near full speed for an extended period. Past that, the details get specific to the plant, the failure modes you're protecting against, and the BMS programmer's preferences — the equipment staging lesson picks up exactly there: how the sequence decides how many pumps to run, and rotates the lead so they wear evenly.
Tying It Together
Three pages, one picture. On load piping we set up the variable-flow system from the coil's point of view — every load throttled by a two-way valve, system flow varying with the building. On VFDs we walked through the drive that lets a pump motor follow a speed reference instead of running on/off at the line. On this page we filled in what the BMS does with that speed reference: hold a DP setpoint across the worst-case load, ideally one that walks down with the building, and ride the pump curve along the system curve as the day goes on. Variable-speed pumping is three concepts that have to land at once; isolated from each other, none of the three makes complete sense. Underneath all three, each load's connection valve has to hold its design flow as system pressure swings — that's what hydronic balancing covers, and it's why pressure-independent control valves (PICVs) are the natural pairing for aggressive DP-reset.
What comes next is the sequence layer above all of this. Part of it has landed: the equipment staging lesson covers how a plant decides how many identical pumps — or boilers, or chillers — to run, and rotates them for even wear. The rest is still ahead: what setpoints get reset against outside-air temperature, how a control loop transitions between modes, how a building goes from unoccupied night setback into morning warm-up without thrashing every piece of equipment in the plant.