Water · Industrial Effluent Representative scenario

Trade-effluent compliance — and a bill you can actually check

For a factory on the municipal sewer, the discharge is both a compliance risk and a line on the invoice — and both were running blind.

At a glance

The deployment in one view.

Setting

A food & beverage factory discharging process effluent to the municipal sewer under a trade-effluent permit

Problem

pH and COD shock loads risking a permit breach and disconnection — and an effluent bill calculated on COD load the site couldn't independently verify

What we monitored

Connection-point pH, COD, conductivity, temperature and flow, plus pre-treatment (balancing, neutralisation, DAF)

Alerts

Shock-load and out-of-limit alerts so a slug can be diverted or corrected before it leaves site

Compliance & billing

A continuous permit record, plus the site's own metered volume and COD load as an independent check on the charge

The shift

From quarterly municipal samples and an estimated bill to live control and a verifiable charge

The challenge

A factory that sends its process effluent to the municipal sewer lives under two pressures at once, and this site felt both. The first is compliance: discharge to sewer is governed by the local authority's bylaw and a trade-effluent permit, with limits on pH, COD, temperature, fats/oils/grease and more — and a single acid or caustic dump, a hot CIP cycle or a grease slug can breach the permit in minutes, risking penalties or even disconnection from the sewer. The second is cost: a trade-effluent bill is typically calculated on discharge volume and COD load, and if you don't measure those yourself, you're accepting someone else's figure on the most expensive line of the invoice.

The core gap: the municipality samples occasionally and bills on load — but the site had no continuous view of either. It couldn't see a breach forming between samples, and it couldn't independently check a charge built on a COD load it never measured.

Our approach

Instrument the connection point. Continuous pH, COD, conductivity, temperature and flow at the point the effluent enters the municipal sewer — integrating the analysers the site already ran where possible (see trade-effluent monitoring).
Alert inside the limit. Thresholds set within the permit limits, so a drift toward the edge raises a WhatsApp or email alert in time to divert to a balancing tank or correct dosing — before the slug leaves site.
Make the pre-treatment visible. Before/after sensing across balancing, neutralisation and the DAF showed whether pre-treatment was actually performing, turning "we think it's fine" into a measured answer.
Meter for billing, not just compliance. Continuous flow and COD give the site its own time-stamped record of volume and load — an independent basis to reconcile against the municipal charge and, where pre-treatment is cutting load, to substantiate a lower one.
Keep the record through outages. Edge buffering means load shedding never leaves a gap in the discharge record, on the addaNet platform — important both for compliance evidence and for catching a shock load that happens during an outage.

What changed

From discharging blind to discharging on data.

Breaches headed off

A pH excursion or COD spike becomes an alert and a diversion while it can still be contained — instead of a permit breach the municipality finds at its next sample.

A bill that can be checked

The site's own metered volume and COD load give it an independent basis to reconcile the trade-effluent charge, rather than accepting an estimate it can't test.

Pre-treatment proven

Before/after data shows the balancing and DAF doing their job — and flags a failing unit before it causes either a breach or a load the site pays for downstream.

Why it fits South Africa

For industrial dischargers under a bylaw, a bill and an unreliable grid.

Discharging to a municipal sewer in South Africa means living under a local bylaw and a trade-effluent permit that differ by municipality and change over time — and being billed on a COD-load formula you may never have measured. Continuous connection-point monitoring is a force-multiplier for a lean utilities team: it watches the discharge around the clock, alarms the shock loads that breach permits and choke sewers, and gives the site its own defensible record for both the regulator and the invoice. Edge buffering means load shedding — which often coincides with the process upsets that cause a breach — never leaves a hole in that record.

See trade-effluent monitoring and the guide on trade effluent & municipal bylaws.

This case study illustrates addanode's approach through a representative scenario; client details and figures are omitted by policy. Trade-effluent bylaws, charging formulae and permit limits differ by municipality and change over time — confirm obligations against your own permit, the applicable local bylaw and your advisers.

Discharging to the sewer — and not sure about the limits or the bill?

Send us your trade-effluent permit conditions and a recent effluent invoice. We'll scope connection-point monitoring to match your limits, set the alerts that keep you compliant, and give you the data to verify what you're charged.

Talk to our Water Team Trade-effluent monitoring →

Trade-effluent compliance — and a bill you can actually check

The deployment in one view.

The challenge

Our approach

From discharging blind to discharging on data.

Breaches headed off

A bill that can be checked

Pre-treatment proven

For industrial dischargers under a bylaw, a bill and an unreliable grid.

Discharging to the sewer — and not sure about the limits or the bill?

Related reading

Trade-effluent monitoring

Trade effluent & municipal bylaws

Effluent & DWS compliance