Sewer Level Monitoring System for Reliable Networks

A sewer level monitoring system is most valuable before a wet well reaches alarm level, a pump station fails to respond, or a surcharge becomes a public incident. For utilities, councils and industrial operators, the objective is not simply to record depth. It is to create real-time operational visibility that supports faster decisions across distributed sewer assets.
Level data, collected reliably and delivered without manual intervention, gives operators a clear view of how wet wells, manholes, interceptors and remote collection points are behaving. Combined with rainfall, pump status, flow, pressure or trade waste information, it becomes an operational tool for preventing overflows, prioritising crews and improving long-term network planning.
What a sewer level monitoring system needs to deliver
A utility-grade system must perform in difficult conditions. Sewer sites are humid, corrosive, often remote and frequently subject to variable communications coverage. Equipment selection must account for the measurement point, mounting arrangement, expected range, maintenance access, power availability and the consequences of a missed alarm.
The strongest deployments combine non-contact level measurement, low-power telemetry, local alarm logic and secure cloud-based visualisation. This approach reduces exposure to contaminated media and limits maintenance associated with sensors that are continuously submerged. Radar level sensors are particularly effective where operators need stable readings in wet wells with foam, turbulence, condensation and changing process conditions.
The system should also distinguish between a normal daily pumping cycle and an emerging issue. A single high-level threshold is necessary, but it is not enough. Rate-of-rise alarms, prolonged high-level alarms, pump-down time, repeated starts and loss-of-communication events provide earlier warning of failures that may otherwise remain hidden until an overflow occurs.
Why level data changes sewer operations
Many sewer networks are still managed through periodic inspections, SCADA points at major stations and reactive response to customer reports. That model leaves a large number of smaller pump stations, sewer manholes and regional assets without continuous visibility. These locations can become the weak points in the network during wet weather, equipment faults or power disruption.
A connected level monitoring system changes the operating model. Instead of sending a crew to confirm whether a wet well is rising, operators can review the current level, recent trend and alarm history from a central map. They can determine whether the issue is localised, identify which sites need immediate attendance and avoid unnecessary call-outs to sites that have returned to normal operation.
The value is especially clear during major rainfall events. Infiltration and inflow can rapidly increase loading across gravity mains and pump stations. Level trends reveal where the network is responding outside its normal profile, allowing operations teams to deploy pumps, investigate likely restrictions or prepare contingency measures before sewer surcharge affects properties, waterways or roads.
For industrial and trade waste operators, continuous level measurement can also support process control and compliance. Monitoring tanks, pits and collection systems helps identify abnormal loading, blocked discharge paths and potential containment risks. The right configuration depends on the process, but the principle is consistent: decisions improve when level data is current, contextual and available to the people responsible for the asset.
Selecting the right measurement technology
There is no single sensor type that suits every sewer application. The correct choice depends on the media, measurement range, access constraints and maintenance strategy.
Non-contact radar is well suited to wet wells, manholes and chambers where operators want to avoid sensor contact with wastewater. It can provide accurate, repeatable level data from above the liquid surface and is generally less affected by the fouling risks associated with immersed instruments. Correct mounting remains critical. The sensor needs a clear measurement path, with consideration given to ladders, pipe inlets, pumps, guide rails and internal structures that may create false reflections.
Hydrostatic pressure sensors can be appropriate where a submerged measurement method is practical and the site conditions are controlled. They provide a direct level measurement but require careful attention to diaphragm fouling, cable installation, atmospheric compensation and long-term service requirements. In aggressive or high-solids environments, maintenance access and replacement intervals must be factored into whole-of-life cost.
Ultrasonic sensors remain useful in selected applications, particularly where the surface is relatively calm and vapour, foam or condensation are limited. However, their performance can be more sensitive to environmental conditions than radar. A low upfront equipment cost can be offset if the measurement becomes unreliable at the moment the site is under peak hydraulic stress.
The sensor is only one part of the design. A reliable installation also requires suitable enclosure protection, mounting hardware, battery or solar power design, antenna positioning and communications testing. Field conditions should drive the specification, rather than selecting a device solely from a data sheet.
Alarm strategy should focus on consequences
Alarm fatigue is a genuine operational risk. If a platform produces frequent low-value notifications, critical events can be missed or acknowledged without investigation. Sewer alarm settings need to reflect how each site operates and what action the operations team can realistically take.
At a minimum, high and high-high level alarms should be configured against known operating limits. More mature systems add configurable delays to avoid nuisance alarms from short pump cycles, rate-of-rise conditions to detect abnormal inflow or pump failure, and pump-down performance rules to identify declining station capacity.
Communication and power alarms matter as much as process alarms. A site that stops transmitting during a storm may be more urgent than a site reporting a stable, moderate level. Local data logging and store-and-forward capability protect the operational record when mobile coverage is interrupted, while a properly designed platform makes communication loss visible rather than silently leaving an asset unmonitored.
Alarm escalation should align with duty rosters and incident procedures. The purpose is not to send more messages. It is to ensure that the right person receives an actionable alert, with enough context to assess urgency before leaving the depot.
From isolated readings to network intelligence
A level trend becomes more powerful when it is viewed alongside other data sources. Pump run status can confirm whether a rising wet well is caused by pump failure, reduced pump capacity or incoming flow beyond design conditions. Rainfall data may identify catchment-driven infiltration and inflow. Flow monitoring downstream can help distinguish a local station problem from a wider network restriction.
This is where cloud-based monitoring platforms provide operational value beyond telemetry. A geo-mapped view of distributed sites allows teams to see which assets are in alarm, compare level behaviour across a catchment and review historical events without extracting data from separate systems. The platform should support secure access for operational staff, engineers and authorised contractors while avoiding the need for additional customer IT infrastructure.
Integration is equally important. Many utilities need level data available within SCADA, existing dashboards or asset management workflows. Systems using common interfaces, including Modbus and 4-20 mA inputs where required, allow new monitoring points to sit within established operational environments. The best outcome is not another isolated portal. It is a practical data layer that improves the tools already used by the network team.
TracWater’s plug & play monitoring approach combines field instrumentation, wireless communications and cloud delivery to make this level of visibility practical across remote and distributed sewer assets.
Deployment priorities for councils and utilities
A staged rollout is often the most effective way to build a business case and refine the monitoring standard. Start with sites that have a history of overflow, difficult access, high customer impact, recurrent pump faults or no existing telemetry. These assets usually provide the fastest operational return because they reduce uncertainty for crews and create an immediate dataset for engineering review.
Before installation, document the wet well geometry, normal operating levels, pump control setpoints, overflow elevation, available power and communications options. Establish what a normal level cycle looks like. Without that baseline, it is harder to set meaningful alarms or identify gradual performance decline.
After commissioning, review the first several weeks of data with operations staff. Alarm thresholds may need adjustment as real pump cycles, rainfall response and communications behaviour become clear. This tuning period is not a fault in the system. It is the process of translating raw measurements into reliable operating rules for a specific asset.
Over time, the data supports more than incident response. It can identify stations with declining pump-down performance, catchments affected by wet-weather inflow, locations suited to preventive cleaning and assets that warrant capital upgrade. The result is a better basis for maintenance prioritisation and master planning, built from measured network behaviour rather than assumptions.
A well-designed sewer level monitoring system gives operators the confidence to act earlier, send crews with purpose and keep a closer watch on the assets that matter most when conditions deteriorate.





Comments