From the Utility Management edition of November 10, 2026
Reclamation-funded AI & ML Guidebook for Potable Reuse sets staged, guardrailed validation for treatment-plant ML; newly promoted to U.S. utilities on 10 Nov
Carollo Engineers, Yokogawa, National Water Research Institute and Baylor University, for the U.S. Bureau of Reclamation · Drinking water, water reclamation and potable reuse treatment operations · United States (with a Japan-sponsored case study); applicable to conventional drinking water and wastewater plants
- Publisher
- National Water Research Institute (guidebook PDF)
- Original publication
- May 2026 (final guidebook; day not stated, publicationDate set to first of month); publicised by ASCE Civil Engineering Source on 10 Nov 2026
- Source retrieved
- 2026-11-11
What happened
The guidebook, from a Reclamation-funded project on data-driven fault detection and process control for potable reuse, gives utilities a staged path from desktop ML to full-scale use. It warns ML is 'extremely site-specific': models trained on one membrane or filter were inaccurate on others in the same plant, so tools proven at a demonstration facility need retraining at full scale. Safeguards: semi-autonomous trials (AI recommends, operators act) before automation, keep all prior alarms, trial on one parallel train, divert AI-controlled water to sewer for direct potable reuse, and program floors so AI cannot set treatment intensity below the old control system until months of validation. It flags data leakage (suspicious >99% accuracy) and calls for time-based splits. Case studies: a three-week full-scale dissolved-oxygen digital twin with 23% lower aeration energy per kg ammonia versus adjacent weeks; a modelled NDMA soft sensor where a two-standard-deviation safety factor halves UV energy savings from 26% to 13%.
Why it matters
Why now: ASCE promoted the guidebook to U.S. utilities on 10 Nov, quoting its author on phased implementation and data readiness. It is a rare U.S. federally funded, practitioner-written control framework for operational AI in treatment plants, directly usable in procurement and pilot design.
Evidence and measured results
Technical guidebook drawing on project work and cited studies. The 23% figure is a three-week, before/after comparison with adjacent weeks (no randomisation); the 26%/13% figures are modelled, not observed. ASCE's 'at least 10%' energy figure for a Southern California facility was not located in the extracted guidebook text and is attributed to ASCE only.
Limitations and uncertainty
Focus is potable reuse; transferability to conventional plants is asserted by authors. Engineering-firm authors with commercial interest; not peer-reviewed as a document. Older than the last run; included because it was newly promoted on 10 Nov.
Put this evidence to work
Lighthouse Advisory interpretation, grounded in this source. Enriched 2026-11-10; this does not change the original publication date. Each role follows the same checklist so takeaways compare across sources.
Sales
Role takeaway
- Customer problem
- Treatment plants cannot easily judge vendor ML optimisation claims or deploy them without risking water quality.
- Stakeholders
- Plant superintendent
- Water quality/compliance manager
- Process engineer
- State drinking-water regulator
- Data/IT lead
- Discovery questions
- Do you have parallel trains that could serve as a concurrent control?
- How are SCADA and lab data stored and versioned?
- What minimum treatment setpoints must never be breached?
- How would you validate a vendor's model on your site?
- Value hypothesis
- Applying the guidebook's staged validation could avoid unsafe deployments and produce site-specific evidence for or against an ML optimiser.
- Potential engagement
- Pilot-design and vendor-claim review using the guidebook's public-health plan, validation and parallel-train steps.
- Unsupported claims
- That a given plant will achieve 23% or 10% energy savings
- That modelled 26%/13% UV savings were observed
- That models transfer between plants or trains without retraining
Pre-sales engineering
Role takeaway
- Fit
- Drinking water, wastewater and reuse plants with SCADA historians and laboratory data, ideally with parallel trains.
- Architecture and integration
- Advisory ML layer reading historian/LIMS data; any control setpoints bounded by the existing control system.
- Prerequisites
- Clean, time-stamped process and lab data
- Parallel-train or comparable baseline
- MLOps for model and data versions
- Constraints
- Models are site-specific
- Regulatory approval for control changes in potable systems
- Cloud connectivity limits for OT data
- Security
- Keep ML read-only from OT during advisory phase; review any cloud data transfer and access paths.
- Proof of value
- Time-based validation results
- Concurrent parallel-train comparison
- Performance after retraining at full scale
Delivery
Role takeaway
- Work
- Create a public-health protection plan, data pipeline and staged trial from advisory to bounded control.
- Dependencies
- Regulator engagement
- Data quality work
- Operator availability
- Ownership
- Plant superintendent with process engineering.
- Skills and adoption
- Train operators to interpret recommendations and data staff in model maintenance.
- Governance checkpoints
- Public-health plan approval
- Advisory-to-control gate after months of validation
- Post-retraining review
- Acceptance criteria
- Measured savings vs concurrent control train
- Zero compliance excursions during trials
- Documented setpoint floors enforced
- Risks
- Model drift and sensor fouling
- Overstated desktop accuracy
- Staff capacity to maintain models
Implementation considerations
Lighthouse Advisory interpretation across the operating dimensions a public-sector buyer must settle before this evidence becomes a design. Each note answers the question under its heading for this specific source.
Architecture and integration
What must connect, and where does the AI sit in the workflow?
Requires robust data pipelines from SCADA/LIMS, model and data version management, and a control hierarchy where AI setpoints are bounded by the legacy control system.
Governance
Who approves, reviews and stays accountable for outcomes?
Public-health protection plan before any AI control; reward developers on full-scale performance, not desktop accuracy; benchmark against a parallel train.
Security and privacy
What data, permissions and controls need testing?
Cloud-hosted modelling (as in the digital-twin case) brings data transfer and OT-connectivity questions; the article notes utilities must consider cybersecurity, but the guidebook text inspected focuses on data and validation.
Accessibility and workforce
Who is affected, and what skills or accommodations follow?
Cites an ageing workforce and the need for staff training and model-maintenance skills.
Procurement
What should contracts, pricing and exit terms secure?
Pilot contracts can require time-based validation, parallel-train benchmarks and performance floors rather than desktop accuracy claims.
Operating model
Which teams own the service once it runs?
AI control authority expands only after months of full-scale validation; operators remain decision-makers during semi-autonomous trials.
Publication history
- 2026-11-10Utility Management · Issue 126 resources
Stable resource ID: reclamation-nwri-ai-ml-guidebook-potable-reuse-staged-validation-2026