Cooling loop optimization.
Cooling is the largest controllable load on your site. When the loops beneath it hold their targets, the same plant cools more racks on less energy — no chiller replaced, no new hardware in the critical path, nothing changed until you approve it.
- PUE pointsEfficiency the control layer was giving away — recovered, then held
- kW · $/MW-yrEnergy back from loops hunting, saturated or left in manual
- CapacityCooling headroom you can fill with racks, without a capital project
- ExcursionsStable supply temperature through AI load steps, not just at steady state
A cooling plant rarely fails loudly. It degrades quietly.
Each of these is defensible on its own. Together they are a standing kilowatt charge, billed every hour, that never raises an alarm.
The loops we take responsibility for.
Scoped from your points list and historian on day one. Select a control point to see what we do there.
Why more tuning stops working — and what replaces it.
Past a certain deadtime, the problem is no longer the tuning. It is the model.
In a large chilled-water loop, or a CDU secondary, the sensor sits well downstream of the valve. The controller is acting on a measurement of the past. Conventional PID is built for deadtimes of a few seconds; a plant loop can run minutes.
Past that point, no set of PID constants both tracks load and stays stable. Tune it tight and it oscillates. Detune it and it stops controlling. Operators widen the margins, run cold — and the cost disappears into the baseline.
ControlSoft's MANTRA Internal Model Control acts on where the variable will be when the current move lands — not on error that has already happened. Same instruments, same valves, same BMS.
Model-based control predicts where the loop will be when the move lands — and settles on the first pass.
The same physics, already solved.
From plants where an unstable loop does not merely waste energy. Client names withheld; full case studies on request.
A loop nobody could tune, because tuning was never the problem
Transport deadtime meant the sensor reported a dose injected minutes earlier. PID overshot and oscillated, so operators permanently overdosed to stay compliant. Model-based control with flow feedforward replaced reaction with prediction.
Two minutes of deadtime had every pump and blower short-cycling
350 feet between the pumps and the flow meter meant a two-minute lag, so flow never stabilized and every downstream blower, UV system and pump cycled continuously. Model-based control settled the flow and the cascade unwound.
Holding a tight band while flow and inlet conditions swung underneath it
One controller could not absorb steam pressure, inlet temperature and flow changes at once, so the outlet cycled through its limit and fouled the exchangers. Coordinated control with feedforward on both disturbances pre-empted them instead of chasing them.
Start with one hall. Standardize across the fleet.
The assessment works from historian and BMS trend exports — no downtime, no controller changes, no site visit to begin.
Assess
Worked from your historian and BMS trends. You receive a ranked loop inventory, quantified instability, recoverable kW, and a costed fix plan.
Optimize
Tuning validated across the full operating range, not just today's load — plus model-based control where the physics puts a loop beyond PID's reach.
Hold, then replicate
Continuous loop-performance monitoring keeps the savings. The proven hall becomes the template, so a new site inherits a tuned plant instead of rediscovering one.
Show us your most difficult hall.
Two weeks tells you whether the kilowatts are there. You end up with a ranked list of the loops worth fixing and what each one is worth. If the numbers are not there, we will say so.
Generation closer to your critical path? Power generation control →