Who this is for

Environmental and plant managers at South African factories, mines, abattoirs, food & beverage plants and treatment works that hold a Department of Water and Sanitation (DWS) water-use licence and have to report on the quality of what they discharge.

Why grab-samples aren't enough anymore

The traditional approach — a technician takes a sample, sends it to a lab, files the result monthly — has two problems. It's a snapshot, so a breach between samples is invisible (until the regulator's own sample catches it), and it's reactive, so by the time a bad result comes back, the non-compliant water is long gone downstream. Continuous monitoring closes both gaps: you see the discharge all the time, and you can act the moment it drifts.

The compliance shift: the question is no longer just "what was the reading?" but "can you prove what it was, continuously, and show you acted when it moved?" Continuous logging answers all three.

What to measure

Your water-use licence is the definitive list, but effluent monitoring at the discharge point typically covers:

  • pH — the most common and fastest-moving compliance parameter
  • COD (chemical oxygen demand) — organic load, critical for food, beverage and abattoir effluent
  • Conductivity / TDS — dissolved salts
  • Turbidity / suspended solids
  • Flow — volume discharged, often a licence condition in its own right
  • Temperature — and, depending on process, dissolved oxygen, ammonia or specific ions

How to put it in place

The sequence we follow on a DWS compliance project:

  • 1. Read the licence. Extract the exact parameters, limits and reporting frequency for your discharge point — don't monitor more or less than required.
  • 2. Instrument the discharge. Install online sensors for the licensed parameters at the final discharge point.
  • 3. Log continuously. Stream readings to a platform that time-stamps and stores them, with edge buffering so load shedding doesn't create gaps in your record.
  • 4. Alert on breach. Threshold alerts to WhatsApp or email, so an out-of-limit reading triggers action before it becomes an incident.
  • 5. Automate the report. Generate the periodic compliance report straight from the logged data, in the format DWS expects.

Why load-shedding resilience matters for compliance

A gap in your monitoring record is a problem, not a neutral absence — it's exactly when a regulator asks "what was happening here?" If your monitoring goes dark every time the grid does, your compliance record is full of holes. Edge buffering — logging locally and syncing when power returns — keeps the record continuous through outages, which is why we treat it as a compliance requirement, not a nice-to-have, on South African sites.

This is the backbone of our water management solution and a core reason water utilities and industrial dischargers work with us. It runs on the addaNet platform, so effluent compliance sits alongside flow, energy and the rest of your operation.

Frequently asked questions

What parameters does DWS require us to monitor?

It's defined by your specific water-use licence and discharge type, but effluent compliance commonly covers pH, COD, conductivity, turbidity, flow and temperature, sometimes with additional process-specific parameters. Always work from the parameters and limits stated in your own licence.

Can continuous monitoring replace lab grab-samples entirely?

It replaces the blind spots between samples and gives you real-time control, but most licences still require periodic accredited-lab verification. The practical model is continuous online monitoring for control and reporting, with lab samples for calibration and verification.

How does automated reporting actually work?

Because every reading is time-stamped and stored, the platform compiles the periodic compliance report directly from the data — values, exceedances and actions — in the format you submit, instead of someone rebuilding it from spreadsheets each month.

What happens if a parameter breaches a limit?

A threshold alert goes to the responsible person immediately via WhatsApp or email, so you can intervene — adjust dosing, divert flow, stop a process — before the excursion becomes a reportable incident, and the event and your response are logged.

Will the monitoring keep working during load shedding?

Yes, when it's designed for it. Edge devices buffer readings locally and sync when power and connectivity return, so your compliance record stays continuous through outages instead of showing gaps.