Water is the deepest thing we do, and it's also the most misunderstood as a monitoring problem — because "water monitoring" bundles jobs that share almost nothing. A borehole in the Karoo, a leaking municipal network, a treatment works fighting for a Green Drop, and a factory on a trade-effluent permit need different sensors, answer to different regulators, and fail in different ways. This guide separates them, then covers what they have in common in South Africa: load shedding, remote sites, and reporting that has to satisfy a regulator, not just a dashboard.

1. Remote & off-grid supply: boreholes, reservoirs, pump stations

Much of South Africa's water infrastructure sits far from reliable power or fibre — boreholes, reservoirs, dam-level and pump-station telemetry. The winning setup here is solar-powered, low-power monitoring: pump run/dry-run status, flow, pressure and tank/reservoir level, with alarms, running on a panel and battery so there's no grid to install and no load shedding to survive. Submersible pressure transducers, inline flow meters and ultrasonic level sensors are the proven sensor set; edge buffering means a failed pump raises an alert instead of quietly draining a reservoir. Connectivity is whatever reaches the site — LoRaWAN, NB-IoT or 4G.

2. Non-revenue water (NRW): stop paying to lose water

South African municipalities routinely lose 40–50%+ of treated water to leaks, bursts and unmetered use. IoT tackles it through district metering and night-flow analysis — dividing the network into zones, measuring minimum night flow to localise losses, and prioritising a zone-by-zone fix list — plus pressure management, since lower network pressure directly reduces both leakage and new bursts. The economics are compelling because you're recovering water you've already paid to treat; our note on what smart water metering costs in South Africa explains why starting with district metering pays back fastest.

3. Water quality & DWS compliance

For drinking-water systems, the job is catching a quality breach before unsafe water reaches consumers, and proving compliance to the regulator. Continuous turbidity, chlorine, pH, conductivity and DO sensing with threshold alerts does the first; automated, audit-ready reporting against SANS 241 and Blue Drop does the second. The value of IoT here is as much the reporting as the sensing — turning a continuous data stream into the exact licence report the Department of Water and Sanitation (DWS) expects, instead of manual sampling and transcription.

4. Wastewater treatment works (WWTW)

A treatment works is a process plant, and the compliance stakes (Green Drop, and a DWS discharge licence) are high. IoT brings real-time visibility of the things that predict an upset: dissolved oxygen and blower performance in the biological stage, chemical dosing, pump status, and final-effluent quality (COD, ammonia, suspended solids). The point is to catch an upset before it becomes a licence breach — and to have the record that proves performance. This is treatment-works monitoring, and it's distinct from the collection network that feeds it.

5. Sewer networks & pump stations: catch the spill

The collection side fails differently: raw sewage overflowing from a sewer or a tripped pump station into a river or a street. IoT monitors wet-well levels, pump and power status, and overflow (spill) detection, plus inflow & infiltration that overwhelms the system in wet weather. In South Africa the dominant cause is often load shedding tripping the pumps — so edge buffering and power-status monitoring matter as much as the level sensor. The goal is a spill alert before raw sewage reaches the river, not a report after it did.

6. Discharge compliance: three regimes people confuse

"Effluent compliance" hides three genuinely different jobs, with different regulators and audiences — don't let a vendor merge them:

  • Discharge to the environment (river/land) — governed by the National Water Act and a DWS water-use licence; the discharger monitors and reports (see DWS effluent compliance).
  • Discharge to the municipal sewer — governed by a local trade-effluent bylaw and permit, billed on volume × COD load. Here connection-point pH, COD, conductivity, temperature, flow and FOG monitoring is about bylaw compliance and verifying the effluent bill (see trade-effluent monitoring).
  • Oversight of many dischargers — the regulator/CMA/metro side: continuous, independent telemetry across a whole catchment plus in-river ambient quality, for enforcement and public transparency (see catchment oversight).

What they share: South African conditions

Every one of these fails the same way if the IoT isn't built for the country. Three rules cut across all six jobs:

  • Survive load shedding. Real edge buffering keeps recording through an outage and forwards on return — critical when a pump trips because of load shedding.
  • Run off-grid. Solar and battery, sized for a poor-sun day, so remote water assets need no grid connection.
  • Report to the regulator, not just a screen. The deliverable is an audit-ready DWS/SANS 241/Green Drop record, produced automatically.

Where addanode fits

Water is one of addanode's three core focus areas, and we deliver all six jobs end to end: we build the devices and the addaNet platform in-house, read the instruments a site already owns, run the monitoring on solar with edge buffering so it survives load shedding, connect over LoRaWAN/NB-IoT/4G, and turn the data into audit-ready DWS, SANS 241 and Green/Blue/No Drop reporting — supported by a local team. Start at the water management hub, or by role at water utilities and municipalities. To choose a provider, see how to choose an industrial IoT provider in South Africa.

Frequently asked questions

What's the best IoT solution for water monitoring in South Africa?

There isn't one product — match it to the job. For boreholes and remote reservoirs, solar-powered pump/flow/pressure/level monitoring with edge buffering; for municipal losses, district metering with night-flow analysis and pressure management; for drinking water, continuous quality sensing (turbidity, chlorine, pH) with automated SANS 241/DWS reporting; for wastewater works, DO/blower/final-effluent monitoring; for sewers, wet-well level and spill detection. The common requirements are surviving load shedding, running off-grid on solar, and producing audit-ready compliance reports. Choose an end-to-end provider that owns devices, connectivity, platform and reporting.

Who provides end-to-end water and wastewater monitoring in South Africa?

A genuine end-to-end water provider owns the whole chain: sensors (level, flow, pressure, quality), solar power, connectivity (LoRaWAN/NB-IoT/4G), the platform and dashboards, and — critically for water — the automated regulatory reporting (DWS, SANS 241, Green Drop). Many vendors supply only sensors or only a dashboard and sub-contract the rest. addanode delivers all of it in-house or under one accountable contract, building the devices and the addaNet platform, running the monitoring on solar with edge buffering for load shedding, and producing audit-ready compliance records — supported locally.

What's the best IoT setup for borehole monitoring in rural South Africa?

One solar-powered node covering pump run/dry-run status, flow, pressure and tank/reservoir level, with alarms — no grid to install, buffering data through outages, and reporting over LoRaWAN, NB-IoT or 4G depending on what reaches the site. Submersible pressure transducers, inline flow meters and ultrasonic level sensors are the proven sensor set. The deciding factor is rarely the sensor — it's surviving off-grid and staying connected from a remote location, and having one local provider install, support and integrate it so a failed pump raises an alert instead of a dry reservoir.

How much does smart water metering / non-revenue water monitoring cost in South Africa?

It's driven by scale and approach rather than a fixed price: the cheapest, fastest-payback start is district metering — a handful of zone meters plus night-flow analysis to localise losses — rather than metering every connection at once. Because you're recovering water you've already paid to treat, NRW work typically pays back quickly. Ask a provider for a ZAR total line-itemed into meters, installation, connectivity/SIMs, platform and support, and start with one or two district-metered zones to prove the recovery before scaling.

How do I automate DWS / SANS 241 water compliance reporting?

Continuously sense the regulated parameters (for drinking water: turbidity, chlorine, pH, and more; for effluent: COD, ammonia, flow), stream them to a platform with breach alerts, and configure automated reports in the exact format DWS or the SANS 241 / Blue Drop / Green Drop process expects. The win is replacing manual sampling and transcription with a continuous, tamper-evident record and exception alerts — so you catch a breach in real time and hand the regulator an audit-ready report instead of assembling one by hand.

How can I detect sewer overflows and pump-station spills before they reach the river?

Monitor wet-well level, pump run and power status, and add overflow (spill) detection, so a rising level or a tripped pump raises an alert before sewage escapes. In South Africa the common trigger is load shedding tripping the pumps, so power-status monitoring and edge buffering matter as much as the level sensor. Add inflow & infiltration monitoring to catch wet-weather overload. The goal is a spill alert before raw sewage reaches the river — not a report after it did.

Will water monitoring keep working through load shedding and at off-grid sites?

It should — and if it doesn't, it's the wrong system. Real edge computing buffers readings locally during an outage and forwards them when power and connectivity return, so the record stays continuous even when a pump or the grid goes down. Off-grid sites run on solar and battery sized for a poor-sun day, with no grid connection to install. This is essential for water because outages are exactly when pumps trip and reservoirs drain, so that's when you most need the data.