From the Utility Management edition of October 29, 2026
New Mexico Looks to Space for Help Combatting Water Waste (LeakTracer year-one results)
New Mexico Environment Department (with ASTERRA) · Drinking water distribution (small and rural public water systems) · New Mexico, United States
- Publisher
- Government Technology
- Original publication
- 19 Oct 2026
- Source retrieved
- 2026-10-30
What happened
NMED's statewide LeakTracer program uses ASTERRA L-band satellite radar plus AI to flag likely treated-water leaks, which are matched to utility GIS and verified by field inspectors. In year one, 28 utilities, 181 miles of pipe inspected and 216 leaks identified (45 main, 54 service, 117 customer-owned). Repairing all would recover an estimated 898,000 gallons/day (328 million gallons/year) and about $505,000/year in production costs, but NMED stresses these are projections, not measured savings; utilities pay for repairs and NMED is building a repair follow-up process.
Why it matters
A state-funded shared AI service for systems serving under 20,000 people, a model state agencies and small utilities can replicate; it also illustrates the gap between AI detections and verified outcomes.
Evidence and measured results
Reporting quoting NMED's communications deputy director and the state's Year One Summary; savings figures are estimates assuming all leaks are repaired. No independent verification of detection accuracy or completed repairs.
Limitations and uncertainty
Vendor-supported program; detection precision, false positives and repair completion rates not reported; savings are projections; trade press source.
Put this evidence to work
Lighthouse Advisory interpretation, grounded in this source. Enriched 2026-10-29; this does not change the original publication date. Each role follows the same checklist so takeaways compare across sources.
Sales
Role takeaway
- Customer problem
- Small and rural water systems cannot find hidden leaks or fund repairs, and states need evidence that loss-reduction programs work.
- Stakeholders
- State drinking water program manager
- Small utility operators
- Rural infrastructure finance staff
- Tribal utility leaders
- Discovery questions
- How do you track whether flagged leaks are repaired?
- What share of identified leaks are on customer-owned lines, and who notifies customers?
- What funding exists for the repair step?
- Value hypothesis
- Shared state-funded detection may reduce water loss for small systems if paired with repair funding and verification.
- Potential engagement
- Program outcome-tracking design and repair-verification analytics for a state agency.
- Unsupported claims
- 328 million gallons already saved
- $505,000 already saved
- Detection accuracy rates
Pre-sales engineering
Role takeaway
- Fit
- Good fit for distribution systems with usable GIS; weak where pipe maps are poor.
- Architecture and integration
- Vendor detection polygons overlaid on utility GIS, then linked to CMMS work orders and metering.
- Prerequisites
- Utility GIS pipe network
- Field verification capacity
- Work-order system
- Constraints
- Projected savings only
- Small-system data gaps
- Vendor-dependent analytics
- Security
- GIS infrastructure data shared with a vendor should be covered by data-use terms.
- Proof of value
- Link a sample of detections to completed repairs and measured flow change
Delivery
Role takeaway
- Work
- Onboarding, GIS preparation, verification scheduling, repair tracking and savings calculation.
- Dependencies
- State funding
- Vendor delivery
- Utility repair capital
- Ownership
- NMED program coordination; utilities own repairs.
- Skills and adoption
- Small-system operators need help interpreting flagged areas and logging repairs.
- Governance checkpoints
- Repair follow-up method approved before outcome reporting
- Customer-side leak notification process
- Acceptance criteria
- Proposed: repair status recorded for all flagged leaks
- Proposed: measured savings reported separately from projections
- Risks
- Unrepaired leaks
- Customer-side responsibility gaps
- Overstated outcomes
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?
Satellite detections must be joined with utility GIS pipe maps and field verification; outcome tracking requires a repair-documentation workflow that does not yet exist statewide.
Governance
Who approves, reviews and stays accountable for outcomes?
The state funds detection and verification but not repairs, so value depends on capital access; a statewide follow-up process is in development to document repairs and calculate savings.
Security and privacy
What data, permissions and controls need testing?
Utility GIS pipe network data is shared with a vendor; 117 of the leaks are on customer-owned lines, implying customer notification responsibilities.
Accessibility and workforce
Who is affected, and what skills or accommodations follow?
Small systems have thin staffing for excavation and repair logistics; the state's Rural Infrastructure Program may help with financing.
Procurement
What should contracts, pricing and exit terms secure?
State-procured shared service model avoids each small utility contracting separately; repair costs remain local.
Operating model
Which teams own the service once it runs?
Statewide shared service with local repair accountability; participation grew to more than 60 utilities by 1 July 2026 with 50-60 more expected.
Publication history
- 2026-10-29Utility Management · Issue 0110 resources
Stable resource ID: nm-leaktracer-satellite-ai-leak-detection-year-one