Water treatment works with clarifiers and a telemetry cabinet on a pump-station wall

WWS · Water & Wastewater

Field note · Water & Wastewater

Water and wastewater: telemetry that crosses the fence line

Range Lab2026-11-036 min read

A treatment works has a fence, a gate and a control room. Most of its network lives somewhere else.

The pumps that push water into town, the lift stations that bring sewage back, the reservoirs on high ground: each has a cabinet of its own by the side of a road, and each cabinet has a link back to the works. The plant is the whole district.

The fence is in the wrong place

On most sites like this the works is the smallest part of the network. A distribution system of any size has intake pumping, booster stations, lift stations, reservoirs and valve chambers spread over many kilometres, each with an RTU or small PLC in a roadside cabinet. They report level, flow, pressure and pump status to SCADA at the works, and they take commands back: start a pump, open a valve, change a setpoint.

Every cabinet is a small network. A controller, a radio or cellular modem, often a local panel or service port, sometimes a switch nobody remembers fitting. The fence around the works reaches none of it. The padlock on the cabinet is the perimeter, and the link inside it is the way in.

Wide view of a treatment plant with open basins, pipe galleries and a control building
WWS · 01 / 09 · wide

Radio. Licensed or unlicensed, usually a point-to-multipoint network put in by the SCADA integrator and protected by a shared key, if anything. Built for reach and reliability, not for strangers. Anyone with the right radio, the right channel and the key can join, and the key sits in the integrator's commissioning file.

Cellular. One modem per site, each with a SIM and an address on the carrier's network that may or may not be private. Worse in one specific way: a modem given a public address so the integrator could reach it from the office can be reached by everyone else too, and it answers whoever connects.

Leased line or fibre. Where the budget stretched, and usually only to the biggest sites.

"Telemetry" only means measuring from a distance. Commanding from a distance came along for the ride.

Read and write, same wire

The protocols that carry telemetry were written when the only thing on the wire was the utility's own equipment. DNP3 is the most common in water, with Modbus and IEC 60870-5-104 close behind. All three carry reads and writes in the same session: SCADA polls an outstation for readings, then sends the command that starts the pump, and the outstation never asks who's sending.

Secure options exist, mostly switched off. DNP3 has had a secure authentication option for years, defined in IEEE 1815, but it needs support at both ends and an upgrade to outstations that haven't changed since commissioning. So it usually isn't on. Modbus has no such option at all.

Whoever can hear a reading on a telemetry network can usually send a command on it too.

One cable hears the district

Every remote site's traffic arrives in one place: the telemetry head end at the works, where the radio base station or cellular router hands it to the SCADA server. A passive capture there hears every outstation without visiting a single one.

What it shows. Which outstations are polled and how often, which addresses they answer from, which protocol and function codes are used, and so which sites are only read and which are written to. It also shows the devices that talk without being outstations: a service laptop, a modem's management page, an integrator's "temporary" remote session. And the traffic leaving telemetry for the office, for billing, dashboards or a vendor: the list of crossings any segmentation design will need.

Listening changes nothing. A mirror port on the head-end switch is the usual setup, and no packet reaches an RTU. For controllers that have run without a restart since commissioning, that matters: an active scan can stop one. Anything beyond listening waits for written authorisation and a named person from the operator beside us.

Sample · illustrative, not a client site

Site Link Protocol Written to Reachable from
Booster station 4 Cellular, public address Modbus TCP Yes Anywhere on the internet
Lift station 12 Radio, shared key DNP3 Yes Anywhere in the radio footprint
Reservoir A Radio, shared key DNP3 No, read only Anywhere in the radio footprint
Works intake Fibre DNP3 Yes Works network only
Close view of a telemetry cabinet with an RTU, a radio modem and an antenna lead
WWS · 01 / 09 · detail

Built for a team of three

A water operator's security team is often the same two or three people who program the RTUs and keep SCADA running. Whatever gets designed has to fit them, and none of this needs a round-the-clock watch.

1. A list. Every remote site with its controller, link, address, and whether it's ever written to. The capture produces most of it; the integrator's commissioning records fill the gaps.

2. A zone. Telemetry becomes its own zone, in ISA/IEC 62443-3-2 terms, with one conduit into SCADA and no other route toward the office. The head end is the natural boundary, because the traffic already passes through it.

3. Private modems. Cellular modems lose their public addresses, through a private APN from the carrier or a VPN ending at the head end, so each modem answers only to the works.

4. Brokered integrator access. Opened on request, time-boxed, logged and closed.

5. Listen again. Repeat the capture once or twice a year, or after any integrator visit, and check the list still matches the district.

None of it needs new RTUs. It wraps protection around equipment that can't change, and leaves a small team with a true drawing of their district and a short list of things to keep true.

New to the vocabulary? Learn OT covers it from zero, free.