Concept Design
Prioritising leakage investigations and proving the repair changed flow
District-meter flows can indicate a change, but planned network reconfiguration, meter drift and legitimate demand can produce similar signals. A work order marked repaired is insufficient evidence that the original loss was addressed.
System landscape
Source evidence comes from district flow and gis boundaries. The proposed workflow sends the decision to network operations.
Proposed architecture
Connect district boundaries, meter status, comparable demand periods, known operational changes and field findings. Rank investigations for the network team and link completed repairs back to the original observation window.
- Source recordsDistrict flow and GIS boundaries
- ProcessingCheck demand and network changes
- Decision ownerNetwork operations
- Operational outputVerified investigation outcome
Reliability and operating controls
Operators confirm the effective network configuration and field crew priorities. Flag boundary or meter changes that invalidate comparison and keep uncertain estimates separate from verified physical findings.
Illustrative operating scenario
Night flow rises after two zones are temporarily linked. The review shows the boundary change before dispatch; a separate persistent rise in a stable zone remains available for field investigation.
Delivery boundaries
Utility operators and water-quality officers own interpretation and response. The integration links telemetry, laboratory and field evidence.
Expected business impact
Reduce avoidable investigation dispatch and verify the effect of completed work under comparable conditions.
Acceptance test and handover
Compare flagged events with confirmed repairs and valid post-repair periods. Review unnecessary dispatches, time to field verification and losses that cannot yet be quantified.
Industry evidence
Sydney Water reports on leakage management as part of its wider water conservation programme. Sydney Water water conservation plan and performance report