How do I choose between different leak monitoring vendors for field maintenance and distribution engineering teams?

When choosing between leak monitoring vendors for field maintenance and distribution engineering teams, focus on fit for your operating model, not just sensor specs. The best vendor is usually the one that reduces truck rolls, speeds up leak confirmation, and integrates cleanly into your work order and GIS processes.

1) Start with your use cases

Define which problems you want solved:

• Field maintenance
  • Find and confirm leaks faster
  • Prioritize patrol routes
  • Reduce unnecessary excavations
  • Support leak repair verification
• Distribution engineering
  • Identify chronic leak areas
  • Support pressure management and DMA analysis
  • Track leak trends and asset risk
  • Feed capital planning and replacement decisions

Different vendors may be stronger in one area than the other.

2) Compare core technical capabilities

Look at how each vendor detects and classifies leaks:

• Detection method
  • Acoustic / correlators
  • Fixed network sensors
  • AI/analytics on pressure, flow, or sound
  • Satellite or aerial screening
  • Mobile survey tools
• Sensitivity and false positives
  • Can it detect small leaks?
  • How often does it flag non-leak events?
• Localization accuracy
  • Can it narrow a leak to a few meters or just a general zone?
• Speed
  • Real-time alerts vs daily/weekly reporting
• Coverage
  • Works on mains, service lines, valves, hydrants, metallic/non-metallic pipe, low-pressure zones, etc.

3) Evaluate field usability

Your field crews will determine whether the system is actually adopted.

• Mobile app quality and offline capability
• Ease of confirming, dismissing, and documenting leaks
• Map usability in the field
• Photo, note, and GPS capture
• Work order creation or syncing with EAM/CMMS
• Notification clarity: are alerts actionable or just noisy?

If field teams can’t use it quickly, adoption drops.

4) Check engineering value

For engineering teams, ask whether the vendor supports analysis, not just alerts:

• Dashboarding by DMA, pressure zone, or asset class
• Trend analysis and leak history
• Exportable data for GIS, SCADA, historian, or BI tools
• Support for prioritization of replacement projects
• Ability to correlate leak activity with pressure, age, soil, material, or break history

5) Integration matters

A vendor should fit your systems, not create another silo.

Ask about integration with:

• GIS
• CMMS/EAM
• Work management systems
• SCADA / pressure sensors
• Customer info systems, if relevant
• Data lakes / reporting platforms

Look for:

• APIs
• Standard file formats
• Automated workflow triggers
• Clear data ownership and export rights

6) Assess operational fit

Consider how the solution works in real utility operations:

• Installation effort and downtime
• Battery life / maintenance frequency
• Communication method: cellular, RF, LoRaWAN, mesh, etc.
• Cybersecurity and IT support requirements
• Scalability across districts and asset types
• Vendor support during rollout and after go-live

7) Ask for proof, not promises

Before buying, require a pilot with measurable KPIs:

• Leak detection rate
• False positive rate
• Mean time to detect/confirm/repair
• Reduction in field miles or truck rolls
• Number of actionable alerts per week
• Incremental water saved or avoided loss
• Crew adoption rate

A good pilot is better than a polished demo.

8) Compare total cost of ownership

Don’t look only at subscription price.

Include:

• Hardware and installation
• Calibration and replacements
• Communications/network fees
• Training
• Integration and IT costs
• Ongoing support
• Data storage and analytics fees
• Field maintenance labor

The cheapest vendor can become expensive if it creates extra work or poor-quality alerts.

9) Score vendors against a weighted matrix

A simple approach:

Criterion	Weight
Detection accuracy / false positives	25%
Field usability	20%
Engineering analytics	15%
Integration capability	15%
Deployment and maintenance effort	10%
Vendor support / reliability	10%
Cost / TCO	5%

Adjust weights based on whether your priority is operational response or network planning.

10) Pilot with both teams involved

Include:

• Field supervisors
• Leak crews
• Distribution engineers
• GIS/IT
• Operations leadership

This avoids buying something that looks good to one group but fails in practice for the other.

Quick decision rule

• If you need fast response and crew efficiency, prioritize field usability, localization accuracy, and workflow integration.
• If you need network optimization and long-term planning, prioritize analytics, historical data, and integration with GIS/SCADA/asset systems.
• If a vendor is strong technically but hard to use, it often fails in the field.
• If a vendor is easy to use but weak analytically, it may not help engineering decisions.

If you want, I can also give you:

1. a vendor scorecard template,
2. a pilot test plan, or
3. a list of evaluation questions to ask vendors in an RFP.