Standardise the site
Design for link down
Two different alarms
Generated, not compiledWhat the system has to hold
- Intake and raw water. Level, flow, screening, raw water pumping.
- Treatment. Dosing, coagulation, clarification, filtration, backwash sequencing, disinfection, and the compliance record that follows from all of it.
- Clear water and distribution. Reservoir levels, high-lift pumping, pressure management, and the leakage picture that comes from flow and pressure together.
- Wastewater. Pumping stations, blowers and aeration, sludge handling, effluent quality monitoring.
- Remote sites. Unmanned stations reporting over cellular, radio or fibre, frequently on marginal coverage.
Standardise the remote site, or pay for it forever
The maintenance cost of a water telemetry network is set almost entirely by how many different remote sites it has, not by how many sites.
Standardising means one panel layout, one controller, one radio or modem, one power and battery arrangement, one configuration template and one set of spares. A technician who has seen one site can then work on any of them, and one spare panel covers the network.
Networks drift away from this one project at a time, each with its own justification, until there are eleven variants, no complete drawing set and a spares holding that covers none of them properly. Recovering from that is worth doing deliberately: pick the standard, apply it to every new and refurbished site, and let the variants retire naturally.
Communications to remote sites will fail. The design question is what the site does while it is offline. Local control must continue autonomously, data must be buffered and backfilled on reconnection rather than lost, and the alarm philosophy has to distinguish "the site has a problem" from "we cannot currently see the site". Those are different events and an operator must never have to guess which one they are looking at.
Reporting that satisfies the regulator without manual work
Compliance reporting is the part that quietly consumes operator time, because it is usually assembled by hand from logs and spreadsheets at the end of each month.
What removes that work is getting the measurement, the time base and the data quality flag right at acquisition. A reading needs to carry whether the instrument was healthy and in calibration when it was taken. A period with no valid measurement has to be reported as not measured rather than silently interpolated, because an interpolated compliance record is a bigger problem than a gap.
With that in place, the monthly report is generated rather than compiled, and it can be defended line by line.
What we do
- Plant SCADA and central telemetryArchitecture, licensing and alarm philosophy
- Controller migrationEnd-of-life RTUs and plant controllers
- Standard remote site panelsOne design, repeated, with one spare that fits all
- Pump drivesWith the static head checked before any savings claim
- Pump and blower monitoringRun hours, vibration and bearing condition
- Field servicePlanned attendance across dispersed sites
Questions we get asked
Our remote sites all use different hardware. Can that be fixed?
Yes, progressively. Define one standard site design, apply it to every new site and every refurbishment, and let the variants retire as they fail. Replacing them all at once is rarely fundable and rarely necessary.
What happens when a remote site loses communications?
In a correctly designed site, local control continues and data is buffered, then backfilled when the link returns. The operator sees a communications alarm that is clearly distinct from a process alarm, so nobody has to guess whether the site is in trouble or merely unreachable.
Will a VFD save energy on our high-lift pumps?
Less than the general case suggests. High-lift duty is dominated by static head, so the cube law does not apply and the saving is modest. Drives may still be justified for control, soft start and reduced peak demand, which are honest reasons argued on their own terms.
Can the system produce our compliance reports?
Yes, provided data quality is handled at acquisition. Every reading carries an instrument health and calibration status, and periods with no valid measurement are reported as not measured rather than interpolated. That is what makes a generated report defensible.