A chiller does not have to make the coldest water it can all the time - it only has to make water cold enough to meet the load. When the load is light, letting the supply water run a little warmer makes the chiller markedly more efficient, and chilled-water reset is the strategy that does exactly that. This guide defines chilled-water reset, explains the trade-offs against low delta-T and dehumidification, contrasts outdoor-air-based and demand-based reset strategies, and shows how a cloud SCADA trend reveals whether the reset is actually saving energy.
Chilled Water Reset in one line: Chilled-water reset is the strategy of raising the chiller's chilled-water supply setpoint when the cooling load is low, because a warmer supply temperature makes the chiller run more efficiently. The trade-off is that warmer chilled water reduces dehumidification capacity and, if the load is misjudged, can worsen a low-delta-T condition. Reset can be scheduled against outdoor air or driven by actual demand, such as cooling-valve positions.
A chiller's efficiency improves when the temperature difference it has to work across - its lift - shrinks. Raising the chilled-water supply temperature is one way to shrink that lift: the chiller is asked to produce less-cold water, so it does less work and draws less power for the same tons of cooling. When the building's cooling load is light, the zones do not need the coldest possible water anyway, so the plant can raise the supply setpoint and pocket the efficiency gain without anyone in the building noticing.
The reset only makes sense when the load can be met at the warmer temperature, which is why it is tied to load. At full load, warm chilled water would leave the coils unable to remove enough heat, so the setpoint is kept low. As load falls, there is slack - the coils can meet the reduced load with warmer water - and the setpoint is raised into that slack. The reset schedule is essentially a rule for how much warmer the supply can safely run at each level of demand.
The saving is real but bounded, and it comes with a genuine cost that has to be respected. Warmer chilled water carries less dehumidification capacity, because a coil dehumidifies by chilling air below its dew point, and warmer water may not chill it far enough. In humid conditions this matters, so reset strategies limit how high the setpoint can rise when humidity control is needed. The art of chilled-water reset is capturing the efficiency of warmer water without giving up the humidity control the building requires.
The most important caution around chilled-water reset is its interaction with low delta-T. Delta-T is the temperature rise of the chilled water between supply and return; a healthy plant has a good delta-T, meaning each unit of water absorbs plenty of heat, so less water needs to be pumped. Raising the supply temperature can shrink delta-T if the coils are not able to extract as much heat from the warmer water, and a shrinking delta-T forces the plant to pump more water and can push it to run additional chillers, which can wipe out the efficiency the reset was meant to gain. A reset that is too aggressive can therefore backfire at the plant level even as it helps the individual chiller.
Dehumidification is the other trade-off. Spaces that need tight humidity control rely on chilled water cold enough to condense moisture out of the air at the cooling coils. If the reset raises the supply temperature too far, the coils cannot pull the air below its dew point, and indoor humidity climbs, which can cause comfort and, in some facilities, product or process problems. This is why reset must be constrained by humidity conditions, not driven by temperature alone.
Both trade-offs point to the same conclusion: chilled-water reset is beneficial but must be bounded. The upper limit on the supply setpoint is set by whichever constraint binds first - the coils' ability to maintain delta-T, or the need to dehumidify. A well-designed reset respects those limits, and the operator watching it has to confirm that raising the setpoint has not quietly triggered a low-delta-T penalty or a humidity excursion that costs more than the chiller saved.
The simplest reset strategy schedules the chilled-water setpoint against outdoor-air temperature: warmer outside, colder chilled water; cooler outside, warmer chilled water, on the assumption that cooling load tracks outdoor temperature. It is easy to implement and needs only an outdoor sensor, but it is only a proxy - a cool, cloudy day with high internal gains can have a large cooling load that an outdoor-air reset would wrongly assume is small, raising the setpoint when it should not.
Demand-based reset removes that guesswork by responding to what the building is actually asking for. A common approach watches the cooling-valve positions across the zones: if the most-open valve is well short of fully open, the coils have spare capacity and the supply temperature can be raised; if a valve pins wide open and its zone still cannot be satisfied, the reset backs the setpoint down. A trim-and-respond scheme formalizes this - it slowly trims the setpoint upward for efficiency and responds by lowering it whenever a zone signals it needs more cooling. Because it reacts to real demand, demand-based reset captures more saving while protecting the zones that need cold water.
Whichever strategy is used, the reset is only worth doing if it is actually saving energy, and that is where trended data is decisive. A cloud SCADA platform such as Merobix can trend the chilled-water setpoint against the delivered supply temperature, the plant's delta-T, the chiller power, and indoor humidity together, so an operator can confirm three things at once: that the reset is being followed, that it has not collapsed delta-T or driven extra chillers online, and that humidity has stayed in bounds. Seeing the setpoint rise while chiller power falls and delta-T and humidity hold steady is the proof the reset is working - and that proof is only visible in the trend, which is why remote monitoring turns chilled-water reset from a hopeful setting into a verified saving.
It shrinks the chiller's lift - the temperature difference it must work across - so the chiller does less work and draws less power for the same cooling. When the building's load is light, the zones do not need the coldest possible water, so the plant can raise the supply setpoint and capture the efficiency gain without affecting comfort. The reset is scheduled to load so it only raises the temperature when the load can still be met.
Two risks. Warmer chilled water reduces dehumidification, because the cooling coils may not chill the air below its dew point, so indoor humidity can climb. And raising the supply temperature can shrink the plant's delta-T if the coils extract less heat, which forces more pumping and can start extra chillers, potentially wiping out the intended saving. Reset must therefore be bounded by both humidity needs and delta-T behavior.
Outdoor-air reset schedules the setpoint against outside temperature, assuming load tracks the weather; it is simple but only a proxy and can misjudge load on cool days with high internal gains. Demand-based reset responds to actual demand, typically watching cooling-valve positions and using a trim-and-respond scheme to raise the setpoint when coils have spare capacity and lower it when a zone needs more cooling. Demand-based reset captures more saving while protecting the zones.
Merobix reads your field devices into a cloud SCADA - the real thing behind these terms, live in days from any browser.