In many older cities, one set of pipes carries both the sewage from homes and the rainwater from streets, and on a dry day that works fine. But when a heavy storm dumps far more rainwater into those pipes than the treatment plant can handle, the system has to let the excess go somewhere, and that release of untreated, diluted sewage to a river or harbour is a combined sewer overflow. This guide explains how combined systems work, why they overflow during wet weather, the regulatory and reporting obligations that attach to those discharges, and how level instrumentation, overflow detection, and real-time control gates monitor and minimize CSO events.
Combined Sewer Overflow in one line: A combined sewer overflow, or CSO, is the discharge of untreated wastewater mixed with stormwater from a combined sewer system into a receiving water body during wet weather, when rainfall overwhelms the capacity of the pipes and treatment plant. Combined systems carry sewage and stormwater in the same pipes, and rather than backing sewage into streets and basements, engineered overflow points relieve the excess flow to rivers or harbours. These discharges are regulated and must be monitored and reported, which is where SCADA instrumentation and real-time control play a central role.
A combined sewer system is one where a single network of pipes collects both sanitary sewage and stormwater runoff and carries them together toward the treatment plant. These systems were built in an earlier era of city-building and remain in place in many older urban cores. On a dry day the pipes carry only sanitary flow, a modest volume the plant treats easily. The trouble is rain. When a storm hits, the same pipes suddenly have to carry the sanitary flow plus a huge volume of runoff from streets and roofs, and that combined total can be many times what the pipes and the treatment plant were sized to handle.
Something has to give, and the system is deliberately designed so that what gives is a controlled overflow rather than sewage backing up into homes and streets. At points in the network sit overflow structures, often called regulators, where the combined flow is split. Up to a certain rate, flow is directed onward to the treatment plant; anything beyond that rate spills over a weir or through a gate into an overflow pipe that discharges to a nearby river, stream, or harbour. This is the combined sewer overflow: a designed release valve that protects the city and the plant by dumping the diluted excess to the environment during storms.
The discharge is untreated, though heavily diluted by rainwater, and it carries whatever the combined flow contained, which is why CSOs are an environmental and public-health concern rather than a benign stormwater release. The frequency and volume of overflows depend on the size and intensity of storms, the capacity of the pipes and plant, and how much extra wet-weather storage or treatment the utility has built. Reducing overflows, by adding storage, increasing plant capacity, or separating stormwater from sewage, is a long, expensive program for the cities that have combined systems.
Because a CSO is a discharge of untreated wastewater to a water body, it is a regulated event, and utilities that operate combined systems carry legal obligations around their overflows. Overflow points are permitted discharge locations, and the utility is generally required to monitor them, to record when and roughly how much overflow occurs, and to report that information to the environmental regulator and often to the public. The details of what must be measured and reported vary by jurisdiction and permit, so operators work to the specific requirements written into their own permits rather than to any single universal rule.
The direction of regulation has been steadily toward more measurement and more transparency. Regulators increasingly expect utilities not just to estimate overflows but to instrument their overflow points so that the timing and duration of discharges are recorded from actual data, and in many places to make near-real-time overflow status available to the public so that people can avoid contact with affected water after a storm. This shift raises the bar from occasional manual inspection to continuous, documented monitoring at every regulated outfall.
For the utility, this means an overflow event is not over when the water recedes; it generates a reporting duty. Being able to show exactly when each outfall overflowed, for how long, and that the system was operated to minimize the discharge is both a compliance requirement and a defence. That documentation burden is a major reason combined-system operators invest in instrumentation at their overflow structures, because reliable data is what turns a diffuse legal obligation into something they can actually satisfy and prove.
The foundation of CSO monitoring is level and overflow detection at the regulator structures. A level sensor in the chamber, watching the depth against the weir crest, shows when flow is approaching and then exceeding the overflow point, and a dedicated overflow sensor confirms when the outfall is actually discharging. Feeding those signals into an RTU with communications turns every outfall into a reporting station that records the start, duration, and end of each overflow automatically. On a cloud SCADA platform such as Merobix, an operator can see across all the monitored outfalls at once, know in real time which are overflowing, and build the timestamped record that regulators and the public require, without sending anyone to stand at a chamber in the rain.
Monitoring tells you when overflows happen; real-time control aims to make fewer of them happen. Many combined systems have unused storage capacity sitting idle in one part of the network while another part overflows, simply because flow is not distributed to use the whole system's volume. Real-time control uses movable gates and inflatable dams at key structures, driven by the same level and flow instrumentation, to actively steer wet-weather flow, holding it back in reaches that have room and releasing it to the plant as capacity allows. By squeezing more use out of existing storage and conveyance, real-time control can reduce the number and volume of overflow events without building expensive new tanks.
Both the monitoring and the control depend on the same field-operations backbone: sensors at the structures, controllable gates, communications, and a central system that ties them together. The value for operators is twofold. Day to day, the SCADA record turns a legally fraught, hard-to-document event into clean data that satisfies reporting obligations and warns the public. And during storms, real-time control lets the utility operate the whole combined system as one coordinated basin rather than a set of independent overflow points, actively minimizing discharges rather than passively watching them spill. That combination of documenting overflows and reducing them is precisely what modern CSO management asks of a control system.
A combined sewer overflow comes from a combined system, where sewage and stormwater share the same pipes, and it is an engineered wet-weather release of diluted flow that the system is designed to make when rain overwhelms capacity. A sanitary sewer overflow comes from a separate sanitary system that should never discharge untreated, and it is an unintended failure, usually from a blockage, pipe break, or pump failure. Both discharge untreated wastewater, but a CSO is a designed relief point while an SSO is a system failure.
A combined system carries both sanitary sewage and stormwater in the same pipes, so during a storm the pipes must handle sanitary flow plus a large volume of runoff, which can far exceed what the pipes and treatment plant were built to carry. To keep sewage from backing up into streets and buildings, the system is designed to spill the excess at engineered overflow points to a river or harbour. The overflow is a controlled release that protects the city at the cost of an untreated discharge.
Real-time control uses movable gates and dams, driven by level and flow sensors, to actively steer wet-weather flow through the combined system so that storage capacity sitting idle in one area is used to hold back flow that would otherwise overflow elsewhere. By operating the whole network as one coordinated system rather than a set of independent overflow points, it squeezes more use out of existing pipes and storage. This can cut the number and volume of overflow events without building costly new storage tanks.
Merobix reads your field devices into a cloud SCADA - the real thing behind these terms, live in days from any browser.