Skip to main content
Challenge

Build a District Water Pressure and Leak Outage Coordinator

Evaluate municipal water distribution pipe isolation schedules during planned repair outages using hydraulic simulation models. Pinpoint low-pressure customer nodes and formulate fire-flow preservation plans.

EngineeringHosted by Vera
Challenge brief

What you are building

The core problem, expected build, and operating context for this challenge.

Evaluate municipal water distribution pipe isolation schedules during planned repair outages using hydraulic simulation models. Pinpoint low-pressure customer nodes and formulate fire-flow preservation plans.

Water network utility planner

Ingest pipe break repair requests, valve isolation boundaries, and hydraulic node configurations.

Model network pressure fluctuations and fire hydrant delivery capabilities using WNTR simulation modules.

Identify critical demand nodes falling below minimum operational pressure during the planned shutdown window.

Generate a structured pipe outage playbook and tank water dispatch routing plan for district engineers.

Interactive network topology map showing isolated pipes, impacted pressure zones, and tank water delivery routes.

Use WNTR example network INP files with synthetic customer demand patterns and maintenance tickets. Starter examples below are synthetic. They are not downloaded records.

Water Network Tool for Resilience Leverages WNTR hydraulic resilience and pressure-dependent demand simulation features to isolate network pipes.

haystack, wntr, pydantic. Searches municipal utility operating manuals and valve operating standards to assemble repair guidance dossiers. Local or hosted LLM with standard Python runtime support for running hydraulic simulations.

Submit runnable source, pinned dependencies, setup commands, a working interface, example outputs, and a recorded end-to-end demo. Include tests and an action log.

Executes a simulated valve isolation in WNTR to compute customer node pressure drops.

Flags any junction node dropping below 20 psi during peak hourly demand intervals.

Produces an isolation ticket specifying sequence of valve closures and contingency water dispatch points.

```json [ { "input": { "work_order_id": "WO-PIPE-782", "pipe_to_isolate": "P-104", "scheduled_start": "2025-07-10T22:00:00Z", "duration_hours": 4, "affected_valves": [ "V-12", "V-15" ], "network_junction_pressures_psi": { "J-101": 42.5, "J-102": 38, "J-103": 24.1 } }, "expected_output": { "simulation_status": "FEASIBLE_WITH_CAUTION", "min_simulated_pressure_psi": 21.4, "critical_nodes": [ "J-103" ], "fire_flow_maintained": true, "tanker_dispatch_required": false, "approved_by_hydraulics_lead": false } }, { "input": { "work_order_id": "WO-PIPE-789", "pipe_to_isolate": "P-202", "scheduled_start": "2025-07-11T14:00:00Z", "duration_hours": 6, "affected_valves": [ "V-30", "V-34", "V-39" ], "network_junction_pressures_psi": { "J-205": 31, "J-208": 18.2, "J-210": 15.4 } }, "expected_output": { "simulation_status": "UNACCEPTABLE_PRESSURE_DROP", "min_simulated_pressure_psi": 12.1, "critical_nodes": [ "J-208", "J-210" ], "fire_flow_maintained": false, "tanker_dispatch_required": true, "approved_by_hydraulics_lead": false } } ] ```

Simulation does not actuate municipal telemetry or send commands to physical SCADA controllers. Use mock external writes. Require human review before any real deployment.

Rules

Participation guide

Simulation does not actuate municipal telemetry or send commands to physical SCADA controllers. Use mock external writes and human review.

Delivery guide

How work is evaluated

Evaluation

Executes a simulated valve isolation in WNTR to compute customer node pressure drops. Flags any junction node dropping below 20 psi during peak hourly demand intervals. Produces an isolation ticket specifying sequence of valve closures and contingency water dispatch points.

Submission format

Runnable source, pinned dependencies, setup commands, working interface, example outputs, recorded demo, tests, and action logs.

Datasets

Challenge datasets

Public datasets, plus the private datasets you have access to.

Evaluation rubric

How submissions are scored

These dimensions define what the evaluator checks and which criteria separate a passable run from a strong one.

Dimensions
4 scoring checks
Binary
1 pass or fail dimensions
Ordinal
3 scaled dimensions
Dimension 1

Complete workflow

Ingest pipe break repair requests, valve isolation boundaries, and hydraulic node configurations. Model network pressure fluctuations and fire hydrant delivery capabilities using WNTR simulation modules. Identify critical demand nodes falling below minimum operational pressure during the planned shutdown window. Generate a structured pipe outage playbook and tank water dispatch routing plan for district engineers.

Score scale
012
Score 0

Missing or incorrect.

Score 1

Partly complete, with documented gaps.

Score 2

Complete, with reproducible evidence.

Dimension 2

Correctness and evidence

Executes a simulated valve isolation in WNTR to compute customer node pressure drops. Flags any junction node dropping below 20 psi during peak hourly demand intervals. Produces an isolation ticket specifying sequence of valve closures and contingency water dispatch points.

Score scale
012
Score 0

Missing or incorrect.

Score 1

Partly complete, with documented gaps.

Score 2

Complete, with reproducible evidence.

Dimension 3

Review interface

Interactive network topology map showing isolated pipes, impacted pressure zones, and tank water delivery routes.

Score scale
012
Score 0

Missing or incorrect.

Score 1

Partly complete, with documented gaps.

Score 2

Complete, with reproducible evidence.

Dimension 4

Safe execution

Simulation does not actuate municipal telemetry or send commands to physical SCADA controllers.

Binary check

This dimension contributes its full weight only when the submission satisfies the requirement. Partial credit is not awarded.

Learning goals

What you should walk away with

  • Ingest pipe break repair requests, valve isolation boundaries, and hydraulic node configurations.

  • Model network pressure fluctuations and fire hydrant delivery capabilities using WNTR simulation modules.

  • Identify critical demand nodes falling below minimum operational pressure during the planned shutdown window.

  • Generate a structured pipe outage playbook and tank water dispatch routing plan for district engineers.

Resources and assets

Reference links and supporting material

Dataset notes

Use WNTR example network INP files with synthetic customer demand patterns and maintenance tickets. Supplied starter examples are synthetic, not source extracts.

Challenge setup

Configuration summary for this challenge.

Challenge input

Input details are not configured.

Haystack

Framework

Evaluated output

No output checks are configured.

Evaluation checks
  • Ingest pipe break repair requests, valve isolation boundaries, and hydraulic node configurations. Model net...
  • Executes a simulated valve isolation in WNTR to compute customer node pressure drops. Flags any junction no...
  • Interactive network topology map showing isolated pipes, impacted pressure zones, and tank water delivery r...
Configured evaluation evidence
  • 2 public reference cases
Configured runtime
  • 1 configured tool

Summary shows the first task, up to three tools, and up to three evidence items. Open the technical recipe to view all configured items.

View technical recipe

Configured tools

Action Space
  • Haystack · Optional

Evaluation contract

  • Complete workflow · Weight 40
  • Correctness and evidence · Weight 30
  • Review interface · Weight 20
  • Safe execution · Weight 10

Reference cases

  • 2 public reference cases

Workflow tasks

No workflow tasks are configured.

Recipe freeze marker

No recipe freeze time is recorded.

Frequently Asked Questions about Build a District Water Pressure and Leak Outage Coordinator