Combined Sewer Overflow Monitoring
In older cities, a single pipe carries both sewage and stormwater, and in a heavy storm that combined sewer can exceed capacity and discharge to a river through a relief point. A combined sewer overflow, or CSO, is a permitted but regulated event, and monitoring it is largely about proving when it happened and how much discharged. This page explains how a CSO point is instrumented, what an overflow event record contains, and why the reporting drives the design.
Combined Sewer Overflow Monitoring in one line: Combined sewer overflow monitoring detects and documents when a combined sewer discharges to a receiving water through a relief structure during a storm. It uses level sensors at the overflow weir to detect activation, records the start time, duration, and peak level of each event, and estimates the discharged volume. The record exists primarily to satisfy regulatory reporting and to prioritize which overflow points to reduce.
Detecting an Overflow Event
A CSO structure has a weir or a regulator that holds normal flow in the interceptor toward treatment and only spills to the receiving water when the level rises above the weir. Monitoring detects that spill by measuring the level in the overflow chamber: when it climbs above the weir crest, an overflow has begun. This is the same head-over-a-crest principle behind an open-channel flow meter, applied to a combined sewer overflow structure. Some sites add a simple activation sensor purely to timestamp the on and off transitions.
The instrument has to survive a filthy, intermittent environment, sitting dry between storms and then submerged in debris-laden combined sewage. Non-contact radar and rugged submersible sensors are both used, and a redundant or independent activation detector is common because the whole compliance value of the site rests on not missing an event. A CSO monitor that fails silently and reports no overflow during a storm is worse than useless, so its own health is monitored too.
What an Overflow Record Contains
Each overflow event is logged as a record, not just a moment. The essentials are the start time when the level first crossed the weir, the end time when it fell back, the resulting duration, and the peak level reached. From the level over the weir and the weir's geometry, the monitoring estimates the discharge rate through the event and integrates it into a discharged volume. That volume, however approximate, is what regulators and the public most want, because it quantifies what reached the river.
Continuous logging is what makes these records defensible. A CSO point that is only visited after a storm can say an overflow occurred but not exactly when, how long, or how much; a monitored point produces a timestamped trend that answers all three. Storing the level trend, not just the summary, also lets the utility revisit an event later if the weir rating is refined, recomputing the volume without having to have been there.
Why Reporting Drives the Design
CSO discharges are regulated because they put untreated sewage into a receiving water, and utilities operate under permits and long-term control plans that require them to report overflow events and, over time, reduce them. The monitoring exists first to meet that reporting obligation: which outfalls activated, when, for how long, and roughly how much. Because the reporting is the point, the design prioritizes reliable event capture and defensible volume estimates over process control, since a CSO structure is passive and has little to control.
The event history also directs investment. A utility with dozens of overflow points uses the monitored frequency, duration, and volume at each to rank which outfalls contribute most and to target storage, sewer separation, or treatment where it will reduce discharge the most. Notifying the public and downstream users of an active overflow, increasingly expected, likewise depends on the real-time detection. The monitoring turns a permit obligation into both a compliance record and a planning tool.
Frequently Asked Questions
How is a combined sewer overflow detected?
By measuring the level in the overflow chamber against the weir that separates it from the receiving water. When the level rises above the weir crest, the combined sewer is spilling and an overflow has begun. Non-contact radar or rugged submersible sensors are used, often with a redundant activation detector, because missing an event defeats the whole purpose of the monitoring.
What information does a CSO event record capture?
The start time when the level first crossed the weir, the end time when it receded, the duration, the peak level, and an estimated discharge volume computed from the level over the weir and the weir geometry. Storing the full level trend, not just the summary, lets the utility recompute the volume later if the weir rating is refined.
Why is CSO monitoring focused on reporting rather than control?
Because a combined sewer overflow structure is largely passive, spilling by hydraulics when capacity is exceeded, with little to actively control. The regulatory obligation is to report which outfalls overflowed, when, for how long, and how much, and to reduce them over time. So the monitoring prioritizes reliable event capture and defensible volume estimates, which also rank outfalls for investment.
Automation services
Need help turning this into a working system?
Merobix integrates SCADA, programs Allen-Bradley and Siemens PLCs, and designs and fabricates industrial control panels.
Meeting requests are reviewed before confirmation.