The question
What separates a treatment programme that holds from one that looks correct on paper?
Start with what has to be protected
"Treat the water" is not an objective. The objective is protecting a specific asset from a specific mechanism, and stating it that precisely is what makes the programme reviewable later.
Protecting condenser tubes from carbonate scale at high heat flux is a different problem from protecting a mild steel closed loop from oxygen corrosion, even though both are described as corrosion and scale control.
A clear objective also tells you what success looks like — and a programme without a definition of success cannot be assessed, only continued.
The order the work goes in
- Analyse. Make-up and system water, read against the actual metallurgy, temperatures and duty. Everything downstream rests on this.
- Establish the limits. Achievable cycles, the pH window the metallurgy allows, the maximum concentration each critical species can reach.
- Remove mechanically what you can. Filtration, separation and pretreatment are usually cheaper per unit of load removed than chemistry, and they reduce what the chemistry has to carry.
- Select the chemistry as a set. Inhibitor, dispersant and biocide chosen together, so an oxidiser does not degrade the inhibitor protecting the metal.
- Design the control. Which parameter drives which output, with what deadband, what feed limit and what interlock.
- Define verification. How you will confirm the programme is achieving the objective, and how often.
- Set the review cycle. When the programme will be reassessed against the system as it then is.
Control is part of the programme, not an accessory
A programme designed to hold a parameter within a range needs something capable of holding it there. Specifying chemistry that requires close control and then feeding it on a timer is specifying a programme that will not perform.
The control strategy has to be written down: which measurement drives which output, what the setpoint and deadband are, what happens on a lost signal, and what the operator is expected to do when an alarm appears. A system nobody can explain in two years will be run on defaults.
Verification is what makes it a programme
Without verification you have a dosing arrangement and a hope. Verification operates at two levels, and both are needed.
- Did the chemical arrive? Feed verification, residual testing or drum level against calculated consumption. A controller calling for a dose is not evidence that a dose was delivered.
- Is it achieving the objective? Corrosion coupons, deposit inspection, heat exchanger approach temperature, biological counts. These measure the outcome rather than the input.
The second level is the one that gets dropped, because it is slower and less convenient. It is also the only one that answers whether the programme is worth what it costs.
Programmes drift because systems change
A programme correct at commissioning slowly stops being correct. Production changes, a heat exchanger is replaced with a different alloy, the make-up supply changes, an operator adjusts a setpoint for a good reason that nobody records.
A review cycle exists to catch that. It compares the current system with the one the programme was designed for and asks whether the assumptions still hold. Where they do not, the programme changes — not because it failed, but because the system moved.
What to check
- 01Write down the objective as a specific asset protected from a specific mechanism.
- 02Obtain a current analysis of both make-up and system water.
- 03Establish the achievable limits before selecting any chemistry.
- 04Check what can be removed mechanically before deciding what to dose.
- 05Confirm the chemistry components are compatible with each other.
- 06Write the control philosophy down, including what happens on a fault.
- 07Define both levels of verification and who performs each.
- 08Set a review interval and a trigger for early review after any system change.
When to get technical support
A programme that has failed twice is diagnostic information, and the most useful step on a difficult system is establishing what has actually been happening before proposing anything new. Where mixed metallurgy, an unusual source chemistry or a demanding operating envelope is involved, the acceptable chemistry window may be much narrower than a standard programme assumes — and confirming that before implementation is considerably cheaper than discovering it afterwards.
Talk to an EngineerFrequently asked
On a defined interval, and additionally whenever the system changes — a new make-up source, a capacity change, replaced equipment or a change in operating pattern. The scheduled review catches drift; the triggered review catches the change that caused it.