Water telemetry in Zambia — keep water moving through load shedding, and know where it goes.

Zambia's commercial water utilities run pump stations that lose power on a schedule, boreholes scattered across districts, and networks where a large share of what's pumped never gets billed. From Lusaka Water Supply and Sanitation Company's networks to Copperbelt schemes and private boreholes on the Lusaka Dolomite, addanode telemetry puts tank levels, flow, pressure, pump status and power state on one dashboard — verifies that every pump actually restarted after the outage, protects boreholes from dry-running, and produces the metered data that non-revenue water reduction and regulator reporting are built on. For groundwater specifically — levels, drawdown and abstraction on Lusaka's karst aquifer — see borehole monitoring in Lusaka; for monitoring driven by an approval condition, see ZEMA groundwater compliance.

What this solves in Zambia

The problems every Zambian water operator recognises.

Pumps that don't come back after load shedding

The hydropower crisis made extended load shedding a planning fact for Zambian utilities. The outage itself is survivable — the silent failure is the pump that trips on restart and stays down until the complaints arrive. Telemetry time-stamps every power event and verifies every restart, so "power is back but station 4 isn't pumping" is an alert within minutes, not a discovery next morning.

Water pumped but never billed

Zambian sector reporting has put non-revenue water above 40% for many utilities — production that costs electricity and earns nothing. Telemetry provides what every NRW programme starts with: continuous bulk-meter readings for input–billing reconciliation zone by zone, pressure data that shows where leaks and bursts concentrate, and night-flow patterns no meter reader ever sees.

Boreholes and stations a day's drive apart

District boreholes and rural schemes can be hours from the nearest technician. Without telemetry, a tripped pump is discovered when the tank runs dry. With it, the trip is a WhatsApp alert — and the drive out happens once, with the right spare on the truck, instead of twice.

Local operating constraints

Engineered for Zambian water infrastructure as it is.

  • Load shedding is the baseline, not the exception. Monitoring hardware rides through outages on battery, buffers readings locally, and uploads the complete record when power and connectivity return. The data survives exactly the hours when the interesting things happen — and separates "no water because no power" from "no water because the pump failed".
  • Coverage thins outside the line of rail. Lusaka and the Copperbelt towns have workable 4G; district boreholes often don't. Where mobile coverage is absent we deploy private LoRaWAN — sensors talk to your own gateway over kilometres, no operator involved — with satellite backhaul for the truly remote.
  • Solar pumping is spreading; telemetry should match it. Solar-charged, battery-buffered monitoring nodes run for months between visits, with remote diagnostics and over-the-air updates instead of site trips — the same energy independence as the pump they watch.
  • Utility budgets and procurement reality. Deployments start with one pressure zone, one borehole cluster or one problem station, priced as a written cost band after a free remote assessment. Existing bulk meters, level probes and pump starters are read rather than replaced — pulse, Modbus and 4–20 mA included.

Based on water-sector deployments across Southern Africa, this configuration is adapted for Zambian utilities — load shedding, long distances and coverage holes included.

Typical deployment

What a water telemetry rollout in Zambia looks like.

1 · Instrument

Level sensors in tanks and reservoirs, flow from existing bulk meters (pulse or Modbus), pressure transmitters at zone points, current and run-status on every pump — new sensors only where nothing exists.

2 · Connect

4G where coverage allows; private LoRaWAN gateways where it doesn't. Solar-powered nodes at off-grid sites; store-and-forward buffering everywhere, sized for load-shedding hours.

3 · Protect

Dry-run protection cuts a pump before drawdown destroys it; alerts fire on failed restarts after outages, abnormal pressure drops, overflowing tanks and pumps that should be running but aren't.

4 · Reconcile

The addaNet dashboard shows the whole scheme on one screen; bulk-meter and zone data export cleanly for input–billing reconciliation, NRW reporting and regulator returns.

Typical first deployment: one pressure zone or borehole cluster live in 2–6 weeks — hardware pre-configured in Johannesburg, installed by your own technicians or local partners under remote guidance, on the addaNet industrial IoT platform.

Zambian water assets and the sensors each needs

AssetSensorsConstraint that decides the design
Commercial utility zone (11 CUs)Bulk input, reservoir level, DMA night flowNWASCO benchmarking — NRW 57.0%, cost K12.61 vs price K7.9
ReservoirLevel + inlet/outlet flowOverflows and dry tanks during load shedding
Borehole (Lusaka karst)Abstraction meter, water level, pump currentSI 3 of 2026 groundwater monitoring; drawdown
Prepaid zone or kioskDelivered volume vs vends, tank levelDisputes settled by an independent count
Pump stationMains presence, pump current, suction levelEight hours a day without grid
Who this serves

Water operators we build for in Zambia.

Commercial water utilities — Lusaka and Copperbelt providers putting boreholes, pump stations, reservoirs and distribution zones under one dashboard, with the metered data NWASCO-style performance reporting expects · District and community schemes — rural water projects where a working pump verified remotely is the actual deliverable · Mines and mine townships — dewatering, potable supply and township reticulation tracked alongside mining condition monitoring · Agribusiness and irrigation — farm blocks pumping from boreholes and rivers, with abstraction records to stand on · Industrial water users — Lusaka and Ndola plants tracking abstraction, storage and consumption alongside production monitoring.

FAQ

Water telemetry in Zambia — common questions

Does the telemetry keep working during load shedding?

Yes — it is designed around it. Sensors and gateways run on battery and solar, buffer readings locally through the outage, and upload the complete record when power and connectivity return. The system also logs the outage itself: when power dropped, when it returned, and whether every pump actually restarted — the failure mode load shedding hides.

How does telemetry help reduce non-revenue water in Zambia?

NRW reduction starts with knowing where water goes. Continuous bulk-meter telemetry lets you reconcile what each zone received against what was billed, daily instead of quarterly; pressure monitoring finds the zones where leaks and bursts concentrate; and night-flow analysis exposes losses invisible to meter readers. The telemetry doesn't fix the pipes — it tells you which pipes to fix first, with numbers a board or a regulator can check.

Can you monitor a borehole with no mobile coverage?

Yes. A private LoRaWAN gateway — placed at the nearest point with power and backhaul, or connected by satellite where truly remote — receives sensor data over distances of kilometres with no mobile operator involved. The sensors themselves run for years on batteries or solar.

What is dry-run protection and why does it matter in Zambia?

Dry-run protection stops a pump automatically when water level or motor-current signatures show it is pumping air. Drought years draw boreholes down faster than they recover, and a pump that keeps running against falling water destroys itself — a replacement that costs far more than the monitoring. The same data shows each borehole's sustainable yield over time.

Can addanode read the meters and sensors we already have?

Usually, yes. Pulse-output bulk meters, Modbus instruments, 4–20 mA level and pressure transmitters and pump starters are all standard inputs — among 500+ supported protocols. New sensors are added only where a site has nothing to read, which keeps the cost of instrumenting an existing scheme down.

What does water telemetry cost for a Zambian utility?

It scales with sites and sensors, not with promises. A first deployment — one pressure zone or one borehole cluster — is quoted as a written cost band after a free remote assessment of your scheme layout and existing instrumentation. Starting with the worst zone and scaling on evidence is the pattern that works with utility budgets.

Put your whole scheme on one screen.

Send an engineer your scheme layout — boreholes, tanks, pump stations, meters — and get an honest proposal for what to monitor first and what it costs.