Smart OSD Tank Sensor Monitoring for Compliance

Published: Nov 4, 2026

Smart OSD Tank Sensor Monitoring for Compliance

An OSD system can appear serviceable from the surface while its available detention volume is being progressively lost. Sediment, debris, damaged outlet controls, failed pumps and altered site conditions can all change how the asset performs during rainfall. Smart OSD tank sensor monitoring gives asset owners a clearer view of what is happening between inspections, turning tank level data into an operational record rather than an assumption.

For property portfolios, industrial facilities and public infrastructure, that distinction matters. A tank that does not drain as designed can create flood exposure, breach development consent conditions and weaken an owner’s position when performance is questioned. Monitoring is not a substitute for inspection or maintenance. It is a practical layer of evidence that helps direct both activities where they are most needed.

Why OSD tank performance cannot be assessed by appearance alone

On-site detention systems are designed to temporarily store runoff and restrict discharge to an approved rate. Their purpose is simple: reduce the peak flow leaving a developed site so downstream drainage networks are not overloaded. The asset itself, however, often includes components that are difficult to observe during normal site operations.

Below-ground tanks may contain sediment build-up or standing water. Orifice plates can become blocked. Grates, trash screens and pit connections can collect rubbish. In pumped systems, controls and mechanical equipment add further failure points. A visual check of the access cover does not establish whether the tank is emptying to the required level, whether its outlet is functioning, or whether water levels are behaving as expected after rainfall.

This is where monitoring has value. A level sensor records the rise and fall of water within the tank. When paired with rainfall data, maintenance records and an understanding of the approved OSD design, those readings can show whether the asset is detaining runoff and drawing down in a manner consistent with its intended function.

What smart OSD tank sensor monitoring should measure

The term “smart” should mean more than a remote dashboard. For an OSD asset, the monitoring arrangement needs to produce data that is relevant to hydraulic performance and credible enough to support maintenance, compliance auditing or investigation.

A typical system uses a level sensor installed in a location that represents water depth within the tank or connected pit. Readings are transmitted at set intervals to a central platform, allowing authorised personnel to review current levels, historical trends and alert conditions. Depending on the site, this may be supported by rain gauges, flow monitoring, pump status signals or CCTV inspection information.

The most useful data points generally include the pre-rainfall water level, the rate at which the tank fills, peak depth, drawdown time and any residual level that remains after a reasonable drainage period. A single high-level alert is useful, but it is not the full story. The trend before and after an event often provides the stronger evidence.

For example, a tank that rises quickly and returns to its normal low level may be operating as intended, subject to confirmation against design assumptions. A tank that remains elevated long after rainfall has ceased warrants investigation. The cause could be a restricted outlet, sediment accumulation, a downstream surcharge condition, groundwater ingress or a sensor issue. Data identifies the pattern. Engineering assessment identifies the cause.

Sensor selection depends on the asset environment

Ultrasonic, pressure and radar-based level sensors each have different installation and maintenance considerations. The appropriate choice depends on tank geometry, access constraints, condensation, debris risk, expected level range, power availability and communications coverage.

A sensor that performs well in a clean, accessible chamber may produce unreliable readings in a confined environment with turbulent inflows, floating debris or frequent condensation. Installation position matters just as much as device selection. The sensor must be protected from damage while still measuring a representative water level. It also needs a defined reference level so readings can be related back to tank invert levels, overflow points and approved operating criteria.

Converting data into compliance and maintenance decisions

Remote data is only valuable when someone has defined what constitutes normal, abnormal and actionable performance. That requires a baseline. Before relying on alerts, asset owners should confirm the as-built configuration, available design documentation and the maintenance history of the OSD system.

The monitored level profile can then be assessed against practical operating thresholds. These may include an unusually high permanent water level, failure to draw down within an agreed timeframe, unexpected rapid filling, repeated high-level events or inconsistent readings that indicate a sensor fault. Thresholds should reflect the specific asset, not generic settings copied across a portfolio.

Where council conditions, development approvals or asset management obligations require periodic OSD inspection, sensor records can support a more informed maintenance program. They can help identify which tanks require priority cleaning, outlet inspection or detailed investigation. They can also provide date-stamped evidence that an issue was identified, assessed and addressed through a documented process.

That is particularly valuable for facilities managers responsible for dispersed assets. Instead of treating every tank as equally urgent, they can focus site visits on systems showing delayed drawdown, frequent alarms or unexplained changes in performance. This does not remove the need for scheduled inspections. It improves the quality and timing of those inspections.

The limitations asset owners need to understand

Smart OSD tank sensor monitoring is not a certificate of compliance. A level sensor does not confirm the diameter of an orifice, verify structural condition, measure sediment depth throughout the tank or demonstrate that the approved detention volume remains available. It records one aspect of asset behaviour.

Data can also be misleading without context. A high water level may reflect an intense rainfall event that exceeds the design event, downstream network surcharge, a temporarily obstructed outlet or a genuine asset defect. Likewise, a low recorded level does not necessarily prove full storage capacity if sediment has reduced the tank volume below the sensor’s reference point.

Communications dropouts, battery condition, calibration drift and physical damage must also be managed. A monitoring specification should include commissioning checks, data validation, planned calibration or verification, power management and clear responsibility for reviewing alarms. A system that generates alerts nobody owns can create more risk, not less.

For higher-risk sites, monitoring should sit within a broader asset assurance approach. This may include desktop review of approved plans, condition assessment, survey, CCTV, cleaning, flow-path checks, hydraulic assessment and compliance auditing. If performance is disputed, the available data should be considered alongside rainfall records, site observations and forensic investigation of the relevant infrastructure.

A practical implementation pathway

The right starting point is not selecting a device. It is defining the decision the data needs to support. For some owners, the priority is identifying tanks that do not drain. For others, it is demonstrating active management of critical infrastructure, reducing flood exposure at a site, or building evidence for a compliance program.

An effective implementation process usually starts by reviewing the asset register and ranking OSD systems by consequence of failure. High-consequence assets may include tanks beneath occupied buildings, systems serving large hardstand areas, sites with a history of water ingress, or assets subject to strict consent conditions. The next step is verifying the physical configuration and selecting monitoring points that can produce meaningful readings.

Following installation, the sensor should be commissioned against surveyed levels or known tank dimensions. Baseline monitoring through several rainfall events helps establish normal behaviour. Only then should final alarm thresholds and maintenance triggers be set. This staged approach reduces false alarms and gives decision-makers confidence in the information being reported.

For new developments, monitoring can be considered during drainage design and construction rather than retrofitted after handover. Early planning can allow for protected sensor locations, power or battery access, communications testing, safe maintenance access and a clear data handover to the future asset owner. It also makes it easier to align monitoring outputs with the approved OSD strategy and broader site drainage arrangements.

Monitoring works best when ownership is clear

The commercial value of monitoring is not the dashboard itself. It is reduced uncertainty around a critical asset. When monitored data is tied to a defined inspection regime, accountable review process and technically defensible response pathway, it can support better maintenance spend and stronger compliance records.

Stormwater Services Australia approaches OSD assets as lifecycle infrastructure, not isolated pits and tanks. The useful question is not simply whether a sensor can be installed. It is whether the resulting data will improve decisions about performance, maintenance, compliance and long-term risk.

For asset owners, the next step is to identify the OSD systems where an undetected drawdown failure would carry real operational, regulatory or financial consequences. Those are the assets where measured performance can turn routine maintenance into informed stewardship.

Related Articles

Seeking Residential or Strata Services?

Stormwater Services Australia is our national corporate, government, and industrial solutions provider. For local strata and residential services, including blocked drains, pit cleaning, and maintenance, please contact our dedicated local specialists.