Operate the network from one live system picture.
A control-and-coordination platform for distribution operators, field crews, engineers, and customer-response teams managing a municipal water network.
Scale and interface figures on this page are illustrative.
From signal to street response.
Telemetry is useful only when it can be correlated with network topology, field history, customer consequence, and an executable isolation plan.
Fragmented context
SCADA alarms, GIS assets, AMI anomalies, work orders, and crew radio traffic were separate sources of truth.
Decision logic
A pressure drop only becomes actionable when operators can see zone boundaries, recent valve operations, customer impact, and planned work together.
Operational handoff
Field closeout needed to capture valve state, repair method, materials, photos, and restoration status—not just a generic “complete” flag.
The network is the primary interface.
Operations, field work, and capital planning all resolve back to the same assets and zones.
Network operations
Pressure zones, tanks, pumps, valves, hydrants, meters, telemetry and network events.
Incident command
Break triage, isolation plan, affected services, crew assignment, public notice and restoration.
Field work
Offline-capable inspections, valve exercising, leak repairs, flushing, photos and material usage.
Asset planning
Condition, break history, consequence of failure, road-program overlap and renewal scenarios.
Water loss
DMA/zone balance, AMI anomalies, estimated GPM loss and investigation cases.
A response plan is a state machine.
Detection, isolation, repair, restoration, and closeout each require explicit evidence.
Representative application states.
Representative application states from the product. Figures shown on screen are illustrative.
Distribution operations
Pressure Zone 04
Main break command
Maple Ave & 6th
Renewal portfolio
Risk-ranked pipe candidates
FY27 renewal portfolio
| Segment | Pipe | Mi | Risk | Brk | Cost |
|---|---|---|---|---|---|
| CI-4402 | 1928 cast iron · 6” With DOT resurfacing · Q2 | 1.9 | 91 | 6 | $1.24m |
| CI-1880 | Hospital feeder · 12” No overlap | 1.4 | 84 | 4 | $0.92m |
| CI-3317 | 1931 cast iron · 8” With sewer relining | 2.6 | 78 | 7 | $1.68m |
| DI-6021 | 1966 ductile · 8” With DOT resurfacing · Q2 | 0.9 | 71 | 3 | $0.61m |
| CI-2290 | 1934 cast iron · 6” With paving program | 3.1 | 66 | 6 | $2.02m |
| AC-0745 | 1958 asbestos cement · 10” No overlap | 2.9 | 61 | 5 | $1.84m |
Total 12.8 mi · $8.31m of $8.4m · 31 breaks avoided
Risk vs cost 46 candidates
Selected by material
Field work order
WB-2041 · repair & restoration
WB-2041 · Main break
Location
Maple Ave & 6th
Depth 4.5 ft · 8” CI · 1928
Steps
V-183 · closed on site
Turns to close
Photos
6 uploaded · GPS stamped
Sampling
Sample point SP-22 is scheduled after the flush.
Excavation Open · Pipe 8” CI · Repair Clamp · Restoration Pending
Zone balance
District metered area 04
District metered area 04
Inflow vs expected profile MGD
Water balance
Real losses 0.26 · apparent 0.09
Open cases
| Case | Signal |
|---|---|
| Night flow · Oak subzone | +41 gpm |
| Meter cluster 771 | Continuous flow |
| Leak survey LS-182 | Acoustic hit · high |
Failure states are part of the product model.
The cases below are intentionally modeled because real operating software is defined by what happens when data, people, or dependencies do not line up.
Telemetry goes stale
Mark the value with freshness/confidence and fall back to last-known state without pretending it is live.
Valve cannot be operated
Recalculate the isolation plan and customer-impact polygon before dispatch proceeds.
Restoration fails quality gate
Keep incident open and prevent customer-restored state until flush/sample workflow clears.
The data model behind the interface.
The interface follows the domain relationships and rules below.