Remote Telemetry Stormwater Management Systems

Published: Oct 29, 2026

Remote Telemetry Stormwater Management Systems

An OSD basin can look serviceable during a site inspection yet fail to detain water as designed when a critical storm arrives. A blocked outlet, inoperable pump, damaged control pit or altered downstream connection may remain invisible between inspections. Remote telemetry stormwater management gives asset owners a way to see how nominated assets are performing over time, rather than relying solely on assumptions, infrequent inspections or post-event evidence.

For government, industrial, commercial and multi-site property portfolios, the value is not simply receiving more alarms. It is producing reliable operational intelligence: what happened, when it happened, whether the asset performed within its intended operating range, and what work should be prioritised next.

Why remote telemetry stormwater management matters

Stormwater infrastructure is commonly treated as passive until it becomes a problem. This approach creates avoidable exposure where assets have a flood mitigation, water quality or approval compliance function. Detention systems, pump stations, treatment devices, wetlands and drainage networks can deteriorate gradually, while changes in catchment use and asset condition alter their actual performance.

Telemetry converts selected physical conditions into time-stamped data. Depending on the asset and risk profile, this may include water levels, rainfall, pump status, valve position, power supply, flow, turbidity, pH, electrical conductivity or equipment faults. The data can identify patterns that a single inspection cannot reveal, such as a basin that fails to draw down after rainfall, a pump that cycles excessively, or a treatment train that is bypassing more frequently than expected.

The commercial benefit is better control of uncertainty. For an asset manager, that means maintenance can be planned from evidence rather than calendar intervals alone. For a developer or facilities team, it supports a clearer record of how an OSD or WSUD asset has been operated and maintained. For insurance and legal matters, properly managed data may assist forensic investigation by establishing an objective timeline of asset conditions and events.

Start with the stormwater risk, not the device

Telemetry is not a generic add-on. A level sensor installed without a defined operating question may create data but not a useful decision. The system design should begin with the asset’s hydraulic purpose, approval conditions, known failure modes and the consequences of underperformance.

For an OSD system, the central questions may be whether the basin reaches expected operating levels, whether drawdown occurs within the required period, and whether the outlet structure is functioning as designed. A pump station may require monitoring of wet well levels, pump run status, duty and standby operation, power availability and high-level conditions. A water quality asset may warrant a different approach, combining level or flow triggers with scheduled inspections, sediment-depth assessment and, where appropriate, event-based water quality sampling.

This distinction matters because not every parameter can be measured continuously or interpreted in isolation. Turbidity readings, for example, can be affected by sensor fouling, low-flow conditions and installation location. Rainfall data from an on-site gauge may need validation against broader storm patterns. Remote data is valuable only when its limitations are understood and its quality is managed.

Align monitoring with design intent

The most defensible telemetry strategy connects observed conditions to the approved or engineered intent of the asset. That requires access to drainage drawings, OSD schedules, hydraulic calculations, maintenance records, asset condition information and, where relevant, DRAINS or MUSIC modelling outputs.

A model is not a live operating system, but it provides the baseline against which field behaviour can be assessed. If recorded water levels or drawdown periods differ materially from expected outcomes, the cause may be blockage, altered geometry, downstream surcharge, unauthorised connection, equipment failure or an assumption in the original model that no longer reflects site conditions. Telemetry does not answer every question automatically. It directs engineering attention to the questions that matter.

What a practical telemetry system includes

A dependable deployment has more moving parts than a sensor and a dashboard. It generally requires field instrumentation, a data logger or remote terminal unit, communications hardware, power management, data storage, alarm logic and a defined process for reviewing alerts. Each component should suit the site environment.

Below-ground pits, corrosive industrial areas, low-signal locations and flood-prone installations require careful equipment selection and installation. Sensor range, mounting method, ingress protection, access for calibration and battery life all affect whether the system remains useful after commissioning. Where mains power is unavailable, solar and battery arrangements must be sized for local conditions, reporting frequency and expected communications load.

Communications should also be treated as an engineering issue rather than an afterthought. Mobile coverage can vary significantly across large sites, basement areas and regional locations. Store-and-forward capability is valuable where short outages are likely, as it preserves event data for later transmission. For critical applications, the asset owner should understand what happens when communications or power are lost, how that condition is reported, and which data remains available locally.

Cybersecurity and data governance deserve the same discipline. Asset owners should establish who owns the information, who can alter alarm thresholds, who receives notifications, how long records are retained and how user access is controlled. A dashboard with unclear accountability can create a false sense of oversight.

Alarms should drive action, not alarm fatigue

The common failure of telemetry programs is excessive alerting. If staff receive repeated low-value notifications, genuinely significant conditions can be missed or routinely ignored. Alarm logic needs to reflect the operating characteristics of the asset and the response pathway available to the owner.

A high-level alarm at an OSD basin may be appropriate only after a defined persistence period, allowing for normal storm response. A drawdown alarm may be more useful when water remains above a nominated level for longer than expected after rainfall has ceased. Pump fault alarms should distinguish between a temporary communication loss, a power issue and an operational failure where possible.

Alert thresholds should be reviewed after real rainfall events. Initial settings are often conservative because baseline site behaviour is not yet known. Over time, the operating data can be used to refine thresholds, reduce nuisance alarms and identify the conditions that justify inspection, maintenance or engineering review.

Integrate telemetry with inspections and maintenance

Remote monitoring does not remove the need for physical inspection. It makes inspections more targeted and more productive. Sensors cannot confirm every issue that affects performance, including sediment accumulation, structural cracking, vegetation growth, corrosion, damaged grates, inaccessible outlets or changes made by third parties.

The strongest operating model combines telemetry, programmed maintenance and condition assessment. A maintenance team can use recorded trends to prioritise assets showing slow drawdown, unusual water levels or repeated equipment faults. Inspection findings can then explain the data and confirm rectification requirements. After repairs, telemetry provides a practical way to verify whether performance has improved.

This feedback loop is particularly valuable across portfolios where asset records are incomplete or inconsistent. Instead of applying the same maintenance frequency to every site, owners can use risk and performance evidence to direct budget towards assets with the greatest potential flood, compliance or operational consequence.

Establish a defensible implementation pathway

Before procuring hardware, complete an asset and risk review. Identify the drainage assets that are consequential, their design intent, known condition issues, access constraints and compliance obligations. This allows monitoring to be concentrated where it can change a decision.

The next stage is telemetry design and installation planning. It should define monitored parameters, sampling and reporting intervals, alarm conditions, communications method, power source, physical installation details and commissioning tests. Baseline inspection and survey information should be captured at this stage so future data can be interpreted in context.

Commissioning is not complete when values first appear on a screen. Level sensors should be checked against known physical levels, pump status signals should be verified during controlled operation, timestamps should be accurate, and alarm escalation should be tested with the people responsible for action. Documentation should record the installed configuration, calibration method and operational responsibilities.

Ongoing governance is then required. Data needs periodic review by personnel who understand both the asset and the risk being monitored. Where trends indicate underperformance, the response may range from routine cleaning to hydraulic investigation, compliance auditing, redesign or rectification works. The right response depends on the evidence, not on a dashboard colour code.

Use data to protect long-term asset performance

Remote telemetry is most effective when it supports a lifecycle decision, rather than serving as a standalone technology project. For some low-risk assets, periodic inspection remains the most economical option. For high-consequence OSD systems, pump infrastructure, industrial drainage assets or sites with recurring performance concerns, continuous or event-based monitoring can materially improve oversight and documentation.

The useful question is not whether every stormwater asset needs telemetry. It is whether the owner has sufficient evidence to demonstrate that critical assets are performing, being maintained and receiving attention before an avoidable failure becomes a flood, compliance breach or dispute.

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.