From the Utility Management edition of October 31, 2026
EMASESA's Digital Reservoir 5.0 integrates 313,000 smart water meters and AI algorithms on one platform to detect leaks and anomalies
EMASESA (Empresa Metropolitana de Abastecimiento y Saneamiento de Aguas de Sevilla), with Xylem Vue · Public water supply and wastewater utility (about 1.4 million people, twelve municipalities) · Seville metropolitan area, Spain
- Publisher
- Water Online
- Original publication
- Water Online news item (source: Xylem Vue), 29 Oct 2026
- Source retrieved
- 2026-11-01
What happened
EMASESA's Digital Reservoir 5.0 project, which won IWA Project Innovation Award gold in the Smart Systems and the Digital Water Economy category in early October, brings together 200 network sectors and more than 313,000 smart meters (about 7.5 million readings a day), water quality data, real-time external data, numerical modeling and AI algorithms on a single Xylem Vue platform. The aim is to detect leaks, malfunctions and unusual consumption. EMASESA's head of digital transformation stresses a central data lake and connected rather than isolated solutions. The platform has three layers: a data engine, modules for supply, wastewater and water resources, and operational intelligence for decisions.
Why it matters
A large public utility's architecture for using AMI-scale meter data with AI, relevant to U.S. municipal water utilities that have deployed AMI but struggle to use the data. Metering and billing analytics was a recorded gap in both prior editions.
Evidence and measured results
Vendor-sourced trade press release quoting the utility and vendor. The IWA award is an external recognition, but no measured outcomes (leaks found, water saved, false alarm rates) are reported.
Limitations and uncertainty
Vendor-authored, non-U.S., no quantified results. EU data protection and utility ownership structures differ from U.S. municipal settings.
Put this evidence to work
Lighthouse Advisory interpretation, grounded in this source. Enriched 2026-10-31; this does not change the original publication date. Each role follows the same checklist so takeaways compare across sources.
Sales
Role takeaway
- Customer problem
- Utilities with AMI collect millions of daily readings but rarely turn them into leak and anomaly decisions.
- Stakeholders
- General manager
- Digital transformation lead
- Water loss manager
- Metering and billing manager
- IT and OT security
- Discovery questions
- What share of AMI interval data is analyzed today?
- How are customer-side leak alerts handled?
- Is there a central data repository combining meters and network sensors?
- Value hypothesis
- Integrating AMI with network and model data may enable earlier leak and anomaly detection, pending measured results.
- Potential engagement
- An AMI data-use assessment and one district metered area anomaly pilot design.
- Unsupported claims
- Water saved
- Leak detection rates
- False alarm rates
- Cost savings
Pre-sales engineering
Role takeaway
- Fit
- Fits utilities with AMI deployed and sectorized networks.
- Architecture and integration
- Data lake consolidating meters, sector flows, water quality and hydraulic models, with AI modules and an operational decision layer.
- Prerequisites
- AMI with interval data
- District metered areas or sectors
- Integration with billing and GIS
- Constraints
- High data volume
- Possible vendor lock-in
- No reported validation
- Security
- Protect consolidated consumption data; segment platform from OT control networks.
- Proof of value
- Compare AI alerts with confirmed leaks in one sector over three months
- Measure false alarm rate
- Measure time from anomaly to field action
Delivery
Role takeaway
- Work
- Data integration, alert triage process, customer notification process and performance reporting.
- Dependencies
- Metering team
- Billing system owner
- Operations
- Vendor
- Ownership
- Water loss or digital transformation lead.
- Skills and adoption
- Operators and customer service staff need training on interpreting and acting on alerts.
- Governance checkpoints
- Data protection review
- Data ownership and exit terms
- Alert performance review
- Acceptance criteria
- Proposed: confirmed-leak share of alerts above an agreed threshold
- Proposed: anomaly-to-action time within an agreed limit
- Proposed: data export available without vendor dependency
- Risks
- Alert fatigue
- Privacy objections
- Vendor lock-in
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?
A vendor-agnostic integration layer and data lake consolidate meters, sector flows, quality data and models before AI is applied, suggesting the data platform is the main build effort.
Governance
Who approves, reviews and stays accountable for outcomes?
Framed as a public-private partnership within the utility's 2030 Strategic Plan; data ownership and model transparency terms are not described.
Security and privacy
What data, permissions and controls need testing?
Consolidating meter-level consumption from 1.4 million people creates privacy and cybersecurity concentration risk; controls are not described beyond the vendor calling the platform secure.
Accessibility and workforce
Who is affected, and what skills or accommodations follow?
Customer service and field staff workloads will shift as anomaly alerts increase.
Procurement
What should contracts, pricing and exit terms secure?
Specify vendor-agnostic integration, data ownership and exit terms when buying meter analytics platforms.
Operating model
Which teams own the service once it runs?
Moves from isolated tools to a connected platform under a strategic plan with a dedicated digital transformation division.
Publication history
- 2026-10-31Utility Management · Issue 036 resources
Stable resource ID: emasesa-xylem-vue-smart-meter-ai-platform-2026