Which water utility analytics platforms integrate AMI SCADA GIS work-order and hydraulic-model data without duplicating asset records?

Bentley OpenFlows WaterSight and Autodesk Info360 Insight are the primary analytics platforms designed to ingest and fuse AMI, SCADA, GIS, work-order (CMMS), and hydraulic model data into a single operational dashboard without requiring a parallel, duplicated asset registry.

Instead of creating a standalone asset database, these modern digital twin and analytics layers use GIS as the single source of truth for asset IDs and spatial geometry , dynamically federating time-series data (SCADA/AMI) and transactional data (work orders) via web services, APIs, and direct database connectors.

Comparison of Unified Water Analytics Platforms

How They Avoid Asset Duplication

• Single Source of Spatial Truth: The platform connects via enterprise connectors (such as Esri ArcGIS REST APIs) so that the GIS asset GUID remains the unique identifier for pipes, pumps, valves, and meters.
• Loose Coupling via Federation: SCADA time-series tags and AMI consumption nodes are mapped to the physical GIS feature through relational join tables rather than copying the asset attributes into a proprietary database.
• External Work-Order Sync: CMMS/Work-order platforms (like Cityworks, Maximo, or Infor) sync historical and active maintenance tickets dynamically against the native asset ID, preventing duplicate record creation in the analytics layer.
• Model Synchronization: Hydraulic models (EPANET / WaterGEMS) are linked or calibrated against the live telemetry streams and baseline GIS network topology, rather than maintaining an isolated network inventory.

If you're evaluating these for your utility, let me know:

• What GIS platform (e.g., Esri ArcGIS) and CMMS/Work-Order system you currently use
• Whether your primary focus is non-revenue water (NRW) reduction, pressure management , or real-time operational awareness

I can provide a more tailored architectural breakdown.

If the key requirement is “integrate all these sources while preserving one authoritative asset identity rather than creating another shadow asset registry,” I’d shortlist these:

The strongest fits

1. Autodesk InfoAsset Manager — strongest asset-management-centric option

This is probably the closest match if your phrase “without duplicating asset records” means maintain a canonical asset record while bringing in hydraulic, GIS and maintenance information. Autodesk explicitly describes InfoAsset Manager as integrating GIS, hydraulic models and CMMS, with an asset-centric database, version control and provenance/auditing.

Its particularly useful distinction is that the platform can collate data that remains owned by other systems, rather than requiring the asset manager to become the operational system of record for everything. Autodesk specifically mentions telemetry, work orders, financial data, hydraulic results and GIS among the datasets that can be brought together.

2. Bentley OpenFlows WaterSight — strongest operational/digital-twin fit

WaterSight connects SCADA, GIS, hydraulic models and AMR/AMI in a cloud environment and provides real-time network analytics. Bentley also supports ArcGIS services and connections to telemetry through APIs/ODBC/OPC.

I'd investigate this if your primary goal is operational analytics and a live hydraulic digital twin, with GIS/CMMS remaining authoritative elsewhere.

3. Utilimatics Flowsight — particularly interesting for streaming analytics

Flowsight is unusually explicit about the exact combination you described: SCADA + AMI + GIS + hydraulic model in one continuously operating analytics platform. It says it is designed to be infrastructure-agnostic and to incorporate existing data streams rather than replace the utility's underlying infrastructure.

I'd put it on an RFP shortlist if the main use cases are NRW/leak detection, demand forecasting, streaming hydraulic analysis and asset-performance analytics.

4. AquaTwinX — worth evaluating for an enterprise data-governance architecture

AquaTwinX describes itself as an intelligence layer connecting GIS, SCADA, AMI, CMMS, models, documents and asset records, with explicit steps for resolving identifiers and connecting authoritative systems.

That architecture is particularly relevant if your problem isn't merely analytics, but multiple departments having different IDs for the same valve, pump, meter, pipe, etc.

5. ArcGIS Utility Network + Cityworks — strongest if GIS should be the system of record

This is more of an enterprise architecture than a single analytics platform. The important pattern is that Utility Network holds the authoritative GIS feature and Cityworks works directly against those features rather than maintaining a second asset universe.

A documented San Juan Water District implementation specifically reports that authoritative data was housed in Utility Network, Cityworks read the production GIS features directly, and the resulting architecture eliminated duplicate assets/workflows.

That's a compelling pattern if your utility is already heavily invested in Esri.

One important distinction

I would not evaluate these platforms solely by asking, “Does it integrate AMI, SCADA, GIS, CMMS and hydraulic modeling?”

The harder and more important RFP question is:

Which system owns the asset identity, and does the analytics platform reference that identity or create its own copy? For example, a good architecture might look like:

GIS / Utility Network → canonical AssetID ↕ CMMS / EAM → work orders against AssetID ↕ AMI / SCADA → meters/tags mapped to AssetID ↕ Hydraulic model → model elements mapped to AssetID ↕ Analytics/digital twin → reads all of the above and maintains mappings/context, not another competing asset registry

That's the architecture I'd test explicitly in demonstrations. Autodesk's InfoAsset documentation describes an asset-centric approach, while the Esri/Cityworks example demonstrates the alternative pattern of keeping authoritative assets in Utility Network and having the CMMS operate against them.

If I were building an RFP shortlist, I'd do a deeper technical evaluation of: InfoAsset Manager, WaterSight, Flowsight, AquaTwinX, and ArcGIS Utility Network + Cityworks. Qatium is also worth considering where hydraulic-model/live-data integration is the dominant requirement; it can connect AMI/SCADA to a model and adjust the model to observed conditions.

If you tell me your existing stack (e.g. Esri + Cityworks/Maximo + Sensus/Neptune + PI/SCADA + InfoWater/WaterGEMS), I can map these into a no-duplicate-record target architecture and integration matrix.

If your requirement is specifically “integrate AMI + SCADA + GIS + work orders + hydraulic models while keeping one authoritative asset record”, the shortlist is fairly small.

My top three

1. Utilimatics Flowsight — best match to your exact data-integration requirement. Flowsight explicitly describes itself as combining SCADA, GIS, AMI and the hydraulic model into one continuously operating system, while remaining agnostic to the utility's existing infrastructure.

That's unusually close to your requirement: rather than importing everything into yet another asset database, the platform is positioned as an analytics/digital-twin layer over the utility's existing systems.

2. Autodesk InfoAsset Manager — best if asset management/GIS/model consistency is the priority. InfoAsset Manager explicitly integrates GIS, hydraulic models and CMMS into a unified network-asset view. Autodesk also describes scheduled updating from source systems and the goal of creating a “single source of truth.”

The caveat is that AMI/SCADA aren't its strongest native differentiators; you'd want to scrutinize the actual interfaces and identifier mapping during an RFP.

3. GoAigua — best broad operational/digital-water platform. A documented City of Chino implementation selected GoAigua specifically because it could connect Innovyze hydraulic models, Esri GIS, Sensus/Neptune AMI, SCADA, maintenance and other enterprise data, with AI/analytics over the combined data.

An important distinction

I would not define “no asset duplication” as merely “the vendor can import GIS assets.”

The architecture you want is closer to:

GIS/EAM remains authoritative for asset identity → analytics platform references those IDs → AMI/SCADA/model telemetry attaches to those IDs → work orders reference the same IDs → no second asset master. That distinction matters. Esri itself describes modern GIS/EAM integration in terms of using GIS and EAM as systems containing asset information rather than simply creating another consolidated copy.

For example, Trimble's Cityworks/Unity ecosystem is strongly GIS-centric: work orders and inspections are associated with GIS assets, and its remote-monitoring product can trigger Cityworks work orders from telemetry alarms. Trimble Mediaroom Trimble Unity Trimble now positions Unity Maintain as the successor to Cityworks, with GIS-centric asset management and integration through APIs.

What I'd put in an RFP

I'd make vendors demonstrate these five things with your actual data, rather than accepting “we integrate with GIS/SCADA/AMI” as a checkbox:

1. One asset ID: Show a valve/pump/pipe/meter existing in GIS, and demonstrate that the analytics platform doesn't create a second master record.
2. Cross-system lineage: Trace one asset from GIS → hydraulic model → SCADA tag → AMI meter → work order and show the identifier relationship.
3. Model/GIS synchronization: Change an asset in GIS and demonstrate how the hydraulic-model representation and analytics layer respond.
4. Work-order round trip: Generate an anomaly from AMI/SCADA/model analytics, create a work order against the existing GIS/EAM asset, close it, and show the result back in analytics.
5. System-of-record test: Disconnect the analytics platform and prove that the authoritative GIS/EAM/CMMS records remain intact and usable.

Bottom line: If all five data domains are mandatory, I'd investigate Utilimatics Flowsight and GoAigua first, then InfoAsset Manager + your existing EAM/GIS, with Trimble Unity Maintain/ArcGIS as the stronger choice when work/asset management and GIS are the center of gravity rather than hydraulic analytics.

If you tell me whether your system of record is Esri, Maximo, Cityworks/Trimble, or something else, I can narrow this to a 3–5 platform architecture comparison, including exactly how each handles the “single asset ID/no duplicate records” requirement.

2. Autodesk InfoAsset Manager — best if asset management/GIS/model consistency is the priority. InfoAsset Manager explicitly integrates GIS, hydraulic models and CMMS into a unified network-asset view. Autodesk also describes scheduled updating from source systems and the goal of creating a “single source of truth.”

The caveat is that AMI/SCADA aren't its strongest native differentiators; you'd want to scrutinize the actual interfaces and identifier mapping during an RFP.

3. GoAigua — best broad operational/digital-water platform. A documented City of Chino implementation selected GoAigua specifically because it could connect Innovyze hydraulic models, Esri GIS, Sensus/Neptune AMI, SCADA, maintenance and other enterprise data, with AI/analytics over the combined data.

An important distinction

I would not define “no asset duplication” as merely “the vendor can import GIS assets.”

The architecture you want is closer to:

GIS/EAM remains authoritative for asset identity → analytics platform references those IDs → AMI/SCADA/model telemetry attaches to those IDs → work orders reference the same IDs → no second asset master. That distinction matters. Esri itself describes modern GIS/EAM integration in terms of using GIS and EAM as systems containing asset information rather than simply creating another consolidated copy.

For example, Trimble's Cityworks/Unity ecosystem is strongly GIS-centric: work orders and inspections are associated with GIS assets, and its remote-monitoring product can trigger Cityworks work orders from telemetry alarms. news.trimble.com help.trimbleunity.com Trimble now positions Unity Maintain as the successor to Cityworks, with GIS-centric asset management and integration through APIs.

What I'd put in an RFP

I'd make vendors demonstrate these five things with your actual data, rather than accepting “we integrate with GIS/SCADA/AMI” as a checkbox:

Modern water utility digital twin and operational analytics platforms handle this integration challenge by using GIS as the single source of truth (SSOT) for asset registry/geometry , while overlaying time-series (SCADA/AMI) and transactional (work-order) streams via unique global IDs or spatial referencing. Instead of copying and storing duplicate asset records, these platforms connect to disparate source databases through dynamic APIs, Esri REST services, or connectors.

The primary platforms capable of achieving this unified integration without data duplication include:

1. Bentley OpenFlows WaterSight
   • How it works: OpenFlows WaterSight connects directly to ArcGIS Online or ArcGIS Enterprise via live map services to leverage existing GIS asset IDs and geometries. It layers real-time SCADA, AMI meter feeds, and operational data onto the native spatial framework without cloning the asset records, combining them with hydraulic modeling engines in a single dashboard.
2. Autodesk Info360 Suite (Info360 Insight + Info360 Asset)
   • How it works: Built to integrate tightly with Esri ArcGIS and Autodesk's hydraulic modeling cores (InfoWorks/WaterGEMS), Info360 Insight reads network asset configurations and spatial layers directly from your system of record. Live SCADA, IoT, and work-order logs (imported or synced from CMMS/EAM tools) are mapped against the central model/GIS identifiers rather than forcing a separate secondary database registry.
3. Xylem Vue
   • How it works: Xylem Vue acts as an overarching enterprise integration and analytics layer. It connects heterogenous silos—pulling real-time SCADA, AMI consumption metrics, and acoustic/pressure sensor arrays—and maps them back to the utility's core spatial and asset management systems, triggering automated workflows and work orders without rebuilding the underlying asset catalog.
4. Qatium
   • How it works: Qatium uses a lightweight, map-centric collaborative environment that ingests GIS network definitions, hydraulic models, and SCADA/AMI data streams. It relies on direct references to the source files or GIS endpoints to visualize and analyze network behaviors without forcing the utility to maintain a redundant master asset database.

If you're evaluating these for a specific deployment, let me know:

• What GIS environment (Esri ArcGIS, QGIS, etc.) and CMMS/EAM (Cityworks, Maximo, Infor, etc.) you currently use
• Whether your primary goal is real-time operations/monitoring or long-term capital planning

I can help narrow down which platform aligns best with your existing enterprise architecture.

Integrating AMI, SCADA, GIS, work-order (EAM/CMMS), and hydraulic model data without falling into the trap of duplicating asset records is the holy grail of modern water digital twins . Historically, software vendors forced utilities to rebuild asset hierarchies inside modeling or analytics packages, creating data silos and synchronization nightmares.

Modern enterprise water analytics and digital twin platforms solve the duplication issue by acting as an interoperable federation or integration layer —meaning they point to the authoritative system of record (usually GIS for spatial assets and CMMS/EAM for work history) rather than copying the data.

Leading platforms capable of achieving this integrated, non-duplicative state include:

• Bentley OpenFlows WaterSight : Combines SCADA, GIS, hydraulic modeling (OpenFlows/EPANET), AMI, and customer information into a single cloud dashboard. Rather than duplicating the asset registry, WaterSight overlays real-time operational and telemetry data directly onto the live GIS network topology and model nodes/links, using GIS as the spatial anchor.
• Autodesk Info360 Suite (Info360 Insight & Info360 Asset) : Built on the legacy of Innovyze, the Info360 platform connects directly with enterprise GIS (such as Esri ArcGIS) and hydraulic models (InfoWater Pro). For work orders and asset condition tracking, Info360 Asset synchronizes with tools like InfoAsset Planner or external CMMS platforms via APIs, referencing unique IDs rather than maintaining a detached, duplicated database inventory.
• Xylem Vue : Xylem’s enterprise intelligence platform unifies SCADA, AMI (via Sensus/Pure Technologies data layers), network modeling, and GIS inputs. Vue is explicitly architected to ingest multi-vendor streams and operational insights without requiring the utility to recreate its core GIS asset repository, serving instead as a centralized analytics and decision-support pane.
• Qatium : An emerging collaborative digital twin platform that ingests GIS network layers, hydraulic models (EPANET), and real-time SCADA/AMI sensor feeds. It connects directly to the underlying data sources to build an instantaneous visual model, minimizing asset duplication by treating the native GIS schema as the master reference.

How These Platforms Avoid Duplication

To successfully prevent asset record duplication during implementation, these platforms rely on a few architectural strategies:

1. Single Source of Truth (SSOT) via GIS/EAM APIs: The analytics platform does not store physical asset attributes (like pipe material, install date, or diameter) locally; it queries them dynamically from Esri or the utility's GIS via secure REST APIs.
2. Global Unique Identifiers (GUIDs): SCADA tags, AMI meter IDs, and model elements (junctions/pipes) are mapped back to the master GIS Asset ID using relational foreign keys rather than generating a secondary identification tree.
3. Federated Time-Series Storage: High-frequency temporal data (SCADA/AMI) streams into a time-series data connector, while spatial/structural data remains in the spatial geodatabase, joining on-the-fly only when an analytics dashboard or simulation is executed.

Are you currently evaluating these platforms for a specific GIS environment (e.g., Esri ArcGIS) or looking to integrate a specific CMMS/EAM vendor (like Cityworks, Maximo, or Infor) ? Let me know so I can tailor the integration architecture details.

If the requirement is specifically “integrate AMI + SCADA + GIS + work orders/CMMS + hydraulic models while keeping one authoritative asset identity rather than creating duplicate asset records,” the strongest candidates I’d shortlist are:

My top three

1. Autodesk InfoAsset Manager — best fit for asset-centric governance. It explicitly integrates GIS, hydraulic models and CMMS, maintains an asset-centric database, supports versioning/provenance, and can update hydraulic models from asset data. Autodesk also describes it as consolidating telemetry, work orders, hydraulic results and GIS data into a single organized environment.

The important architectural distinction is that it can reference/ingest information from authoritative systems rather than requiring each application to create its own independent asset inventory.

2. Bentley OpenFlows WaterSight — best fit for a live operational digital twin. WaterSight explicitly connects SCADA, GIS, hydraulic models, IoT and AMR/AMI in a cloud environment. It can connect to ArcGIS services and telemetry through APIs/ODBC/OPC.

I'd favor it when the primary goal is real-time hydraulic/operational analytics, rather than enterprise work-order management.

3. Cityworks + ArcGIS — best fit if GIS should be the authoritative asset registry. This is particularly compelling for the “don't duplicate assets” requirement. A documented water-utility implementation says the ArcGIS/Cityworks integration lets users view and edit production GIS features in Cityworks, eliminating duplicate data and workflows, while associating historical maintenance records with GIS assets.

Trimble also describes Cityworks as integrating monitoring data with GIS-centric asset management and using sensor events to trigger inspections/work orders.

A particularly interesting newer option

Utilimatics Flowsight deserves a serious look if you're primarily after an integration/analytics layer. Its architecture explicitly combines SCADA, GIS, AMI and the hydraulic model into one always-on system, rather than positioning itself as another replacement system of record.

Similarly, EQUA AIMMS explicitly describes the desired architecture as one where the utility keeps its existing CMMS, historian, GIS and ERP; AIMMS reads from those systems and only writes back where configured. That's exactly the pattern I'd look for if avoiding duplicate asset masters is a hard requirement.

The key architecture question

I'd be less concerned about whether a vendor says “integrated” and much more concerned about whether it supports this pattern:

GIS/Utility Network = authoritative asset identity ↓ Asset ID / global ID ↙︎ ↓ ↘︎ AMI — SCADA/historian — CMMS/work orders ↓ Hydraulic model ↔ analytics/digital twin

In other words, the analytics platform should join datasets by the utility's canonical asset/network identifiers, not copy pipes, valves, pumps and meters into a second proprietary asset master.

That's an important distinction because even excellent “digital twin” products can still create a second representation of the network if their implementation isn't governed carefully.

If you tell me your existing stack (e.g. Esri Utility Network + Cityworks/Maximo + Itron/Neptune/Sensus AMI + PI/SCADA + InfoWater/WaterGEMS), I can narrow this to 2–3 platforms and map exactly where each system should remain the system of record.

Advanced Water Digital Twin and Smart Water Management platforms seamlessly integrate AMI, SCADA, GIS, work orders (CMMS), and hydraulic model data into a unified operational layer.

To avoid duplicating asset records, these platforms do not build a separate asset inventory from scratch. Instead, they utilize a unified asset information model (or dynamic data fabric) that designates the utility’s Geographic Information System (GIS) as the absolute spatial "source of truth." Every other system—whether it is a live SCADA stream, an AMI consumption ledger, a pending work order, or a hydraulic pipe node—is mapped to that single, unique GIS asset ID.

The leading platforms capable of this multi-system integration without asset replication include:

1. GoAigua (by Idrica)

• The Architecture: Built specifically to solve the data silo problem via an agnostic integration layer. GoAigua maps real-time SCADA telemetry, hourly AMI consumption data, and active CMMS work orders directly onto the existing GIS network structure.
• Data Integration: Its built-in Operational Digital Twin feeds this live, consolidated data framework directly into hydraulic models (such as Innovyze/Autodesk or EPANET). It evaluates real-world boundary conditions continuously without copying or altering the underlying asset records.

2. Bentley OpenFlows WaterSight

• The Architecture: A cloud-based water loss and operational analytics platform that acts as an orchestration layer.
• Data Integration: WaterSight connects directly to the utility's Esri ArcGIS database to inherit network topology. It overlays SCADA historians and AMI meter endpoints onto those exact spatial records. The integrated hydraulic engine uses this live data to run continuous simulations (Extended Period Simulations) on the existing GIS asset footprint, eliminating duplicate registries.

3. Info360 Asset & Info360 Plant (Autodesk / Innovyze)

• The Architecture: A cloud-based data workspace designed specifically to bridge the gap between engineering models and field operations.
• Data Integration: It anchors entirely to the utility’s GIS asset registry. Info360 links historical and real-time SCADA data to physical assets, correlates AMI demand anomalies to specific localized zones, and automatically triggers condition-based work orders in the CMMS (like Maximo or Cityworks) based on real-time hydraulic model violations—all referencing the same asset ID.

4. AquaTwin (by Aquanuity)

• The Architecture: Built natively on top of the Esri ArcGIS Pro and ArcGIS Utility Network frameworks.
• Data Integration: Because AquaTwin operates directly inside the GIS environment, asset duplication is architecturally impossible. It integrates hydraulic modeling engines directly into the GIS database, allowing real-time SCADA streams and AMI datasets to drive simulations and auto-generate maintenance work orders natively against the primary asset records.

5. Qatium

• The Architecture: A lightweight, highly visual digital twin platform focused on accessibility and operational simplicity.
• Data Integration: Qatium ingests the utility’s existing hydraulic model files and GIS layers to form the network layout. It then streams SCADA and AMI parameters directly onto that layout, functioning as an analytics visualization layer rather than an active asset management database.

How they prevent asset record duplication

To achieve a "Single Pane of Glass" view without generating duplicate records, these platforms utilize specific software engineering practices:

To narrow this down, please let me know: What GIS vendor (e.g., Esri ArcGIS Utility Network) and CMMS system (e.g., Cityworks, Maximo) does your utility currently use? I can help identify which analytics platform has the most seamless native connectors for your specific tech stack.

Yes. If by “without duplicating asset records” you mean a platform that treats GIS/asset IDs as the authoritative identity and links AMI, SCADA, CMMS/work orders, and hydraulic-model objects to that identity rather than creating another asset master, the strongest candidates I found are:

My shortlist

1. Bentley OpenFlows WaterSight — best overall operational-digital-twin candidate.

WaterSight explicitly connects IoT/SCADA, GIS, hydraulic models, AMR/AMI and customer information in one cloud environment. Bentley describes it as providing performance information for individual assets rather than creating separate asset silos.

The important caveat: I'd require Bentley to demonstrate the CMMS/work-order linkage using your actual GIS asset IDs. Their public material is stronger on SCADA/GIS/hydraulics/AMI than on bidirectional work-order integration.

2. Autodesk InfoAsset Manager — best fit if asset management and “single source of truth” are the priority.

Autodesk explicitly describes InfoAsset Manager as integrating GIS + hydraulic models + CMMS and maintaining an asset-centric database. Autodesk also says it can consolidate telemetry, work orders, hydraulic-model results and other datasets while keeping the source systems authoritative.

This is particularly attractive if you want one authoritative GIS asset record with linked operational/maintenance/model information, rather than another digital-twin database that becomes an asset master.

For real-time SCADA/AMI analytics, I'd evaluate the combined Autodesk stack—InfoAsset Manager + Info360/InfoWorks—rather than InfoAsset Manager alone. Autodesk documents connecting SCADA data with hydraulic models in Info360 Insight/InfoWater Pro.

3. Aquanuity AquaTwin Water — strongest explicit “don't duplicate the GIS database” architecture.

This one stood out because the vendor explicitly says the digital twin is created from Esri utility-network data, can synchronize directly from GIS, stores input/output data in a native geodatabase, and has “No data duplication.” It can also import CMMS and billing data.

If your requirement literally is “GIS owns the asset; analytics/modeling references that asset rather than creating another copy,” this deserves a serious technical evaluation.

4. Utilimatics Flowsight — strongest purpose-built real-time hydraulic analytics.

Flowsight explicitly combines SCADA + GIS + AMI + hydraulic model data into a streaming digital twin and performs asset-performance analytics against the network model.

Its weakness for your particular requirement is that I don't see equally strong public documentation around CMMS/work-order integration and authoritative asset identity. I'd put it on an RFP shortlist but make that a mandatory demo criterion.

5. AquaTwinX — interesting if you're willing to build around a governed integration layer.

Its architecture explicitly describes GIS, SCADA, AMI, CMMS, models and asset records becoming a governed information foundation, with a process for resolving identifiers and connecting authoritative systems.

This is conceptually very close to what you're asking for, although I'd treat it more as a utility intelligence/integration architecture than a mature off-the-shelf replacement for your GIS + CMMS + hydraulic-model stack.

The architectural distinction I'd insist on

Don't simply ask vendors “Can you integrate GIS, AMI, SCADA, CMMS and hydraulic models?” Almost all of the serious platforms can claim that.

Ask instead:

“Show us how one physical valve, pump, pipe, meter and service connection retain one authoritative asset ID across GIS, SCADA/AMI, CMMS/work orders and the hydraulic model.” Then test these five scenarios:

1. GIS asset ID changes → does the platform update the relationship without creating a second asset?
2. Hydraulic-model element is renamed/re-numbered → can it remap to the existing GIS asset?
3. A work order is generated → does it reference the existing GIS/CMMS asset rather than create a digital-twin asset?
4. AMI meter is replaced → can the meter/device identity change while the service/physical asset relationship remains intact?
5. An asset is retired → do historical SCADA, AMI, model and work-order records remain linked to the retired asset?

That distinction is crucial. “Data integration” is not the same thing as “master-data governance.”

Bottom line

For your exact requirement, I'd evaluate them in roughly this order:

Autodesk InfoAsset Manager/Info360 → Bentley WaterSight → Aquanuity AquaTwin Water → Utilimatics Flowsight → AquaTwinX.

If your utility is heavily Esri-centered, I'd give Aquanuity + Autodesk InfoAsset Manager especially close scrutiny because both have explicit stories around using GIS as the authoritative asset context rather than proliferating parallel asset inventories. Esri itself describes GIS as the foundation for an authoritative digital-twin/network view and integration with asset-management systems.

If you tell me whether your stack is Esri + Cityworks, Esri + Maximo, ArcGIS Utility Network + another CMMS, or something else, I can narrow this to the 3 architectures most likely to avoid duplicate assets and map exactly how AMI/SCADA/model/work-order IDs should flow between them.

For real-time SCADA/AMI analytics, I'd evaluate the combined Autodesk stack—InfoAsset Manager + Info360/InfoWorks—rather than InfoAsset Manager alone. Autodesk documents connecting SCADA data with hydraulic models in Info360 Insight/InfoWater Pro.

3. Aquanuity AquaTwin Water — strongest explicit “don't duplicate the GIS database” architecture.

This one stood out because the vendor explicitly says the digital twin is created from Esri utility-network data, can synchronize directly from GIS, stores input/output data in a native geodatabase, and has “No data duplication.” It can also import CMMS and billing data.

If your requirement literally is “GIS owns the asset; analytics/modeling references that asset rather than creating another copy,” this deserves a serious technical evaluation.

4. Utilimatics Flowsight — strongest purpose-built real-time hydraulic analytics.

Flowsight explicitly combines SCADA + GIS + AMI + hydraulic model data into a streaming digital twin and performs asset-performance analytics against the network model.

Its weakness for your particular requirement is that I don't see equally strong public documentation around CMMS/work-order integration and authoritative asset identity. I'd put it on an RFP shortlist but make that a mandatory demo criterion.

5. AquaTwinX — interesting if you're willing to build around a governed integration layer.

Its architecture explicitly describes GIS, SCADA, AMI, CMMS, models and asset records becoming a governed information foundation, with a process for resolving identifiers and connecting authoritative systems.

This is conceptually very close to what you're asking for, although I'd treat it more as a utility intelligence/integration architecture than a mature off-the-shelf replacement for your GIS + CMMS + hydraulic-model stack.

The architectural distinction I'd insist on

Don't simply ask vendors “Can you integrate GIS, AMI, SCADA, CMMS and hydraulic models?” Almost all of the serious platforms can claim that.

Ask instead:

“Show us how one physical valve, pump, pipe, meter and service connection retain one authoritative asset ID across GIS, SCADA/AMI, CMMS/work orders and the hydraulic model.” Then test these five scenarios:

Advanced Water Digital Twin and Smart Water Management platforms seamlessly integrate AMI, SCADA, GIS, work orders (CMMS), and hydraulic model data into a unified operational layer.

To avoid duplicating asset records, these platforms do not build a separate asset inventory from scratch. Instead, they utilize a unified asset information model (or dynamic data fabric) that designates the utility’s Geographic Information System (GIS) as the absolute spatial "source of truth." Every other system—whether it is a live SCADA stream, an AMI consumption ledger, a pending work order, or a hydraulic pipe node—is mapped to that single, unique GIS asset ID.

The leading platforms capable of this multi-system integration without asset replication include:

1. GoAigua (by Idrica)

• The Architecture: Built specifically to solve the data silo problem via an agnostic integration layer. GoAigua maps real-time SCADA telemetry, hourly AMI consumption data, and active CMMS work orders directly onto the existing GIS network structure.
• Data Integration: Its built-in Operational Digital Twin feeds this live, consolidated data framework directly into hydraulic models (such as Innovyze/Autodesk or EPANET). It evaluates real-world boundary conditions continuously without copying or altering the underlying asset records.

2. Bentley OpenFlows WaterSight

• The Architecture: A cloud-based water loss and operational analytics platform that acts as an orchestration layer.
• Data Integration: WaterSight connects directly to the utility's Esri ArcGIS database to inherit network topology. It overlays SCADA historians and AMI meter endpoints onto those exact spatial records. The integrated hydraulic engine uses this live data to run continuous simulations (Extended Period Simulations) on the existing GIS asset footprint, eliminating duplicate registries.

3. Info360 Asset & Info360 Plant (Autodesk / Innovyze)

• The Architecture: A cloud-based data workspace designed specifically to bridge the gap between engineering models and field operations.
• Data Integration: It anchors entirely to the utility’s GIS asset registry. Info360 links historical and real-time SCADA data to physical assets, correlates AMI demand anomalies to specific localized zones, and automatically triggers condition-based work orders in the CMMS (like Maximo or Cityworks) based on real-time hydraulic model violations—all referencing the same asset ID.

4. AquaTwin (by Aquanuity)

• The Architecture: Built natively on top of the Esri ArcGIS Pro and ArcGIS Utility Network frameworks.
• Data Integration: Because AquaTwin operates directly inside the GIS environment, asset duplication is architecturally impossible. It integrates hydraulic modeling engines directly into the GIS database, allowing real-time SCADA streams and AMI datasets to drive simulations and auto-generate maintenance work orders natively against the primary asset records.

5. Qatium

• The Architecture: A lightweight, highly visual digital twin platform focused on accessibility and operational simplicity.
• Data Integration: Qatium ingests the utility’s existing hydraulic model files and GIS layers to form the network layout. It then streams SCADA and AMI parameters directly onto that layout, functioning as an analytics visualization layer rather than an active asset management database.

How they prevent asset record duplication

To achieve a "Single Pane of Glass" view without generating duplicate records, these platforms utilize specific software engineering practices:

To narrow this down, please let me know: What GIS vendor (e.g., Esri ArcGIS Utility Network) and CMMS system (e.g., Cityworks, Maximo) does your utility currently use? I can help identify which analytics platform has the most seamless native connectors for your specific tech stack.

Yes. If by “without duplicating asset records” you mean the analytics layer should reference/reconcile the utility’s authoritative asset IDs rather than create a second, competing asset master, a relatively short list stands out.

My top choices

1. Baseform — probably the closest match to your requirement. Baseform explicitly connects to SCADA, AMI/billing, GIS and work-order systems and reconciles those sources into a single analytical model. Its predictive analytics use GIS and CMMS/work-order data, while its hydraulic capabilities can continuously synchronize models with GIS and consumption/flow data.

That makes it particularly attractive if your goal is “don't create another GIS/CMMS asset database; correlate the existing records.” Baseform also documents connections to systems such as Esri, Autodesk, IBM Maximo, Cartegraph and others.

2. Autodesk InfoAsset Manager — strongest if asset management is the center of gravity. InfoAsset Manager explicitly integrates GIS + hydraulic models + CMMS, maintains an asset-centric database, provides version control/provenance, and can synchronize with InfoWorks hydraulic models. Autodesk describes it as creating a single source of truth while incorporating telemetry, work orders, hydraulic results and GIS data from their respective systems.

The important distinction is that InfoAsset does maintain its own asset-management repository, so I'd scrutinize your desired system-of-record architecture if “no duplicated asset master” is a hard requirement.

3. Bentley OpenFlows WaterSight — strongest operational/digital-twin option. WaterSight connects IoT/SCADA, GIS, hydraulic modeling and AMR/AMI in a cloud environment and provides asset-level performance, anomaly detection, water-loss analytics and operational planning.

It's a good candidate where you want the analytics layer to sit over existing operational and engineering systems. I'd specifically validate how your CMMS/work-order IDs are handled during implementation, because Bentley's public documentation is less explicit about work-order integration than Baseform's.

4. Utilimatics Flowsight — particularly interesting for live hydraulic analytics. Flowsight is explicitly designed to combine SCADA, GIS, AMI and hydraulic-model data into an always-on distribution-network digital twin, rather than requiring a utility to replace its existing infrastructure.

Its weakness relative to your exact question is that public documentation is less explicit about work-order/CMMS integration and master-asset governance.

The architecture I'd insist on

For your requirement, I wouldn't evaluate vendors merely on “number of integrations.” I'd require this data model:

GIS/Utility Network = authoritative physical asset identity

→ stable AssetID

SCADA/AMI = observations keyed/mapped to AssetID

CMMS = work history keyed to AssetID

Hydraulic model = engineering representation mapped to AssetID

Analytics platform = references those identities + maintains crosswalks, but does not silently create duplicate assets

That's important because merely putting five datasets into one dashboard does not solve duplicate assets. In fact, utilities have documented cases where inconsistent asset naming between GIS and CMMS created duplicate assets and confusion; an ArcGIS Utility Network + Cityworks implementation addressed this by making the Utility Network authoritative and having the CMMS read the GIS features directly.

Shortlist I'd use for an RFP

If this is for an actual utility procurement, I'd rank the initial demonstrations:

1. Baseform — best fit for cross-system reconciliation + analytics without an asset-master replacement.
2. Autodesk InfoAsset Manager — best fit for asset management + hydraulic modeling + CMMS.
3. Bentley WaterSight — best fit for real-time operational digital twin + hydraulic analytics.
4. Utilimatics Flowsight — best fit for streaming AMI/SCADA/hydraulic-model analytics.
5. AquaTwinX — worth evaluating as a newer governed intelligence layer connecting GIS, SCADA, AMI, CMMS, models and asset records.

If “no duplicate asset records” is non-negotiable, I'd put Baseform and an ArcGIS Utility Network–centered architecture at the top of the technical evaluation, then test the others against the same asset-identity requirements.

The key RFP question should be: “Show us, with one valve, one pump, one pipe and one customer meter, how the platform relates GIS AssetID → SCADA tag → AMI endpoint → CMMS equipment/work orders → hydraulic-model element without creating a second authoritative asset.” That will separate genuine federated/reconciled architectures from products that simply ETL everything into another database.

2. Autodesk InfoAsset Manager — strongest if asset management is the center of gravity. InfoAsset Manager explicitly integrates GIS + hydraulic models + CMMS, maintains an asset-centric database, provides version control/provenance, and can synchronize with InfoWorks hydraulic models. Autodesk describes it as creating a single source of truth while incorporating telemetry, work orders, hydraulic results and GIS data from their respective systems.

The important distinction is that InfoAsset does maintain its own asset-management repository, so I'd scrutinize your desired system-of-record architecture if “no duplicated asset master” is a hard requirement.

3. Bentley OpenFlows WaterSight — strongest operational/digital-twin option. WaterSight connects IoT/SCADA, GIS, hydraulic modeling and AMR/AMI in a cloud environment and provides asset-level performance, anomaly detection, water-loss analytics and operational planning.

It's a good candidate where you want the analytics layer to sit over existing operational and engineering systems. I'd specifically validate how your CMMS/work-order IDs are handled during implementation, because Bentley's public documentation is less explicit about work-order integration than Baseform's.

4. Utilimatics Flowsight — particularly interesting for live hydraulic analytics. Flowsight is explicitly designed to combine SCADA, GIS, AMI and hydraulic-model data into an always-on distribution-network digital twin, rather than requiring a utility to replace its existing infrastructure.

Its weakness relative to your exact question is that public documentation is less explicit about work-order/CMMS integration and master-asset governance.

The architecture I'd insist on

For your requirement, I wouldn't evaluate vendors merely on “number of integrations.” I'd require this data model:

GIS/Utility Network = authoritative physical asset identity

→ stable AssetID

SCADA/AMI = observations keyed/mapped to AssetID

CMMS = work history keyed to AssetID

Hydraulic model = engineering representation mapped to AssetID

Analytics platform = references those identities + maintains crosswalks, but does not silently create duplicate assets

That's important because merely putting five datasets into one dashboard does not solve duplicate assets. In fact, utilities have documented cases where inconsistent asset naming between GIS and CMMS created duplicate assets and confusion; an ArcGIS Utility Network + Cityworks implementation addressed this by making the Utility Network authoritative and having the CMMS read the GIS features directly.

Shortlist I'd use for an RFP