What you will learn
- How break reports are triaged and located
- How valve isolation plans are built and corrected on site
- What crew dispatch needs for a break repair
- How repair progress and restoration are tracked
- What the post-break record feeds: asset history and break analysis
What the project is
A main break begins with a report: a customer call, a pressure alarm, or a crew observation. The response system creates an incident, locates it on the network, and identifies the valves that isolate the broken section with the fewest customers affected. A crew is dispatched with the break location, pipe details, isolation plan, and traffic and safety notes. During repair, the crew updates progress, and when the main is repaired, disinfected, and flushed as required, service is restored and affected customers are notified.
The coordination problem is that several things happen at once: the crew repairs, the office handles customer calls, the outage system notifies customers, and traffic or road authorities may need informing. A response system that holds one incident record, updated by everyone involved, prevents the classic failure where the crew finishes, nobody tells the office, and customers wait hours for a restoration message that never comes.
Core features
The single incident record is the feature. When the crew, the office, and the notification system all read the same record, the response stops contradicting itself.
- Incident creation from customer reports, pressure alarms, and crew observations, with duplicate grouping.
- Network location and valve isolation planning, showing the isolated section and the customers affected.
- Crew dispatch with break details, pipe material and size, isolation plan, and safety notes.
- Repair progress updates from the field, including photos, with timestamps for each stage.
- Restoration workflow: repair, disinfection, flushing, and water quality checks where required, each signed off before service returns.
- Customer notification integration, so outage and restoration messages follow the incident record automatically.
- Post-incident records feeding asset history, break frequency analysis, and replacement planning.
How it is built
Build the incident record and the isolation plan first, with operators who have actually isolated a main. Messaging and reporting follow from a record everyone trusts.
- Response study: map how breaks are reported, isolated, repaired, and restored today, and where the handoffs fail.
- Incident and isolation build: incident records, network location, and valve isolation planning, validated on past breaks.
- Field and dispatch tools: crew dispatch and progress updates, tested with a real crew on a real repair.
- Notification integration: connect outage and restoration messages to the incident record.
- Analysis: break frequency by pipe material, age, and area, feeding the replacement program.
Tech considerations
GIS and offline field tools are the technical core. The incident record itself is straightforward workflow.
- GIS integration for network, valves, and customer locations, with isolation logic that operators can override on site.
- Offline-capable field updates, because break sites often have poor connectivity and crews cannot wait for signal.
- Incident state tracking with timestamps, so response times can be measured honestly per stage.
- Notification integration with the outage system, driven by incident state changes rather than manual messages.
- Asset history integration, so each break adds to the pipe's record and to break-frequency analysis.
Challenges to plan for
Break response fails on location errors, isolation mistakes, and restoration messages that arrive late or never. All three are record problems.
- Wrong location: a break reported at a cross street may be a hundred metres away, and the crew's first hour is spent finding it.
- Isolation errors: closing the wrong valve extends the outage to customers who should never have lost water.
- Restoration delays: repair complete but disinfection, flushing, or sampling still pending, with customers told water is back too early.
- Repeat breaks: a pipe that breaks twice in a year needs replacement planning, not a third repair, and only a good record reveals the pattern.
Who it is for, and honest limits
This fits any water utility with a distribution network, because every network breaks mains. It fits less well as a standalone purchase for a utility whose work order system already handles incidents and isolation well, where the gap may be notification integration rather than a new platform.
It does not prevent breaks or repair pipes faster by itself. It coordinates the response so crews, office, and customers work from the same facts. If break frequency is the problem, the fix is pipe replacement, and the incident record is what proves which pipes to replace first.
Frequently asked questions
How is the affected area determined?
From the valve isolation plan: the section of main between the closed valves, and the customers connected to it. Crews correct the area on site when the actual isolation differs from the plan.
How are duplicate reports handled?
Reports from the same area about the same break are grouped into one incident, with each reporter linked for updates. Dispatchers can split a group if it turns out to be two breaks.
What happens after the pipe is repaired?
The main is typically disinfected and flushed, and water quality checks are done where required, before service is restored and customers are notified. The incident record should show each step signed off, not just the repair.
How is response time measured?
By stage: report to dispatch, dispatch to arrival, arrival to isolation, isolation to repair, repair to restoration. Stage timings show where delays actually happen, which a single total time hides.
Can it predict which pipes will break?
It can support prediction by feeding break history into replacement analysis: material, age, soil, and break frequency together rank pipes for replacement. Prediction needs several years of good records, so start recording well before expecting forecasts.