The problem is our GIS data is siloed from our CMMS. What's the best EAM/GIS integration solution for a water utility?

For a water utility, the “best” EAM/GIS integration is usually not a data sync between two separate asset lists. The strongest architectures make GIS the authoritative asset/location model and connect work management directly to those assets. Water networks are spatial and connected (mains, valves, hydrants, meters, pump stations), so avoiding duplicate asset masters is a major design goal.

A practical shortlist:

TapWaterData Reliable## My recommendation by utility profile

If you are a typical water/wastewater utility on Esri

I would evaluate ArcGIS Utility Network + Cityworks first. This pattern is common because the GIS feature becomes the asset record, and work orders, inspections, and maintenance history attach directly to mapped assets instead of being copied into a separate CMMS database. San Juan Water District is one example of a utility using this architecture to eliminate duplicate workflows and improve field operations.

If you are a large enterprise utility

Evaluate Maximo + ArcGIS. It can work very well, but the key is defining ownership:

• GIS owns: location, connectivity, network topology, spatial attributes
• EAM owns: maintenance plans, labor, parts, costs, failure history
• Integration layer owns: synchronization rules and validation

The City of Henderson’s water/wastewater utility, for example, integrated ArcGIS and Maximo to manage hundreds of thousands of synchronized assets.

The architecture I would aim for

A good target state looks like:

ArcGIS Utility Network

• Asset ID
• Geometry/location
• Connectivity/topology
• Network tracing
• As-built information

⬇️ API/service integration

EAM/CMMS

• Preventive maintenance
• Work orders
• Inspections
• Labor/material costs
• Failure history
• Asset condition scoring

⬇️

ERP / finance / procurement / SCADA / AMI

Avoid these common mistakes

• Two asset masters: GIS has “Valve 123” and CMMS has “V-0456.” This creates reconciliation problems.
• Nightly batch syncing as the primary strategy: It can work, but crews may act on stale information.
• Integrating before cleaning asset IDs: Poor identifiers will just automate bad data faster.
• Treating GIS as only a map: For water systems, GIS often contains the network intelligence needed for isolation, outage planning, and field response.

A good RFP question set

Ask vendors:

1. “Which system is the system of record for asset location and identity?”
2. “Can a work order be created directly from a GIS feature without duplication?”
3. “How are asset IDs governed?”
4. “How does the system handle linear assets (mains, pipelines, sewer lines)?”
5. “Can field crews update GIS attributes during maintenance?”
6. “How are conflicts resolved when GIS and EAM disagree?”

If you share your current stack (e.g., ArcGIS + Maximo, ArcGIS + SAP, Cityworks, Infor, etc.), utility size, and whether you’re water-only or combined water/wastewater, I can narrow this to a recommended architecture and migration path.

Bridging the gap between GIS (where your assets live spatially) and your CMMS/EAM (where your work orders, costs, and maintenance histories live) is one of the biggest operational hurdles for water utilities.

The "best" solution depends heavily on your current software ecosystem, but the industry standard architecture relies on making Esri ArcGIS (specifically leveraging the ArcGIS Utility Network ) talk seamlessly with your Enterprise Asset Management (EAM) system.

Top-tier integration strategies and solutions break down as follows:

• The Esri-Native Approach (ArcGIS + ArcGIS Velocity/Solutions): If your GIS team is mature and already anchored in the Esri ecosystem, utilizing Esri ArcGIS capabilities alongside specialized water utility solutions allows GIS to act as the system of record for asset hierarchy, while triggering workflows directly in the field.
• Hexagon EAM (formerly Infor EAM): Widely regarded as a category leader for water and wastewater utilities. Hexagon features native, deep linear asset management and spatial integration rather than bolted-on connectors, making it powerful if you are looking for an EAM that speaks fluent geospatial data out of the box.
• Maximo with Esri Integration (IBM Maximo + Esri): The gold standard for large utilities with massive capital asset bases. The reliable IBM Maximo-Esri Spatial Integration connector allows bidirectional syncing—meaning updates to a valve, hydrant, or main in the GIS instantly update the asset record in Maximo, and vice versa.
• Middleware and Sync Tools (such as EpochSync Pro or custom REST APIs): If you are running legacy infrastructure or disparate systems that resist direct integration, utilizing specialized synchronization middleware prevents months of manual data reconciliation and duplicate entry.

What a Successful Integration Must Do

Regardless of the software vendor you lean toward, a true fix for "siloed data" requires:

1. A Single System of Record for Geometry vs. Attributes: Decide early if GIS owns the spatial location/identity and EAM owns the financial/maintenance history, enforcing a rigid master-data agreement.
2. Offline-Capable Field Mobility: Field crews fixing main breaks or exercising valves often drop below ground or into remote pump stations. The integration must support offline sync without creating data collisions.
3. Automated Workflows for AWWA/Regulatory Compliance: Tracking valve exercising, unidirectional flushing, and lead service line inventories requires automated triggers between the map and the work order queue.

To help narrow down the ideal path, tell me:

• What CMMS/EAM software are you currently using?
• Are you already utilizing Esri ArcGIS / Utility Network on the GIS side?
• Is your primary goal work order mapping, asset lifecycle tracking , or regulatory reporting?

If your core problem is GIS and CMMS/EAM being separate systems of record, I would not start by replacing either system. For a water utility, the best architecture is usually GIS-centric integration, with clear ownership of asset data and a governed synchronization layer.

My shortlist

1. My first choice: ArcGIS Utility Network + Cityworks

For a water utility, I'd seriously evaluate Esri ArcGIS Utility Network + Cityworks.

The important distinction is that Cityworks is designed around ArcGIS rather than treating GIS as an afterthought. In a documented water-utility implementation, San Jacinto Valley Water District put authoritative asset data in ArcGIS Utility Network while Cityworks consumed the GIS feature services. That eliminated duplicate asset records and allowed maintenance history/work orders to be associated directly with GIS assets.

That gives you a model like:

ArcGIS Utility Network → authoritative asset/location/connectivity model → valves, hydrants, mains, pumps, meters, manholes, etc.

Cityworks → work orders → preventive maintenance → inspections → labor/materials → service requests → maintenance history

Integration → common asset IDs → REST/feature services → near-real-time synchronization → GIS ↔ work management without maintaining two independent asset masters

That's considerably better than periodically copying GIS data into a CMMS database.

2. Maximo is the alternative I'd evaluate seriously

If you already have IBM Maximo, I would not migrate away from it merely to solve the GIS silo.

IBM's Maximo Spatial integrates with ArcGIS Enterprise, and the current documentation supports ArcGIS Enterprise versions through 11.5 for Maximo Spatial 9.1.x.

There are also large water-utility precedents. Henderson's water/wastewater utility has more than 348,000 synchronized assets between ArcGIS and Maximo, and Cobb County Water System implemented Maximo Spatial specifically to integrate ArcGIS and Maximo.

So if your existing CMMS is Maximo, my recommendation would change to:

ArcGIS Utility Network ↔ Maximo

with GIS remaining authoritative for where the asset is and how it connects, while Maximo remains authoritative for maintenance, work, costs, resources and asset lifecycle management.

3. Don't make "bi-directional synchronization of everything" the goal

This is probably the most important architectural point.

I would establish an asset-system-of-record matrix before selecting the integration technology:

The integration should then synchronize specific authoritative attributes, rather than creating two databases that continuously overwrite one another.

Esri itself describes the GIS/EAM relationship this way: GIS is particularly valuable for spatial relationships and network information, while EAM provides work and maintenance information.

What I'd build for a modern water utility

I'd target this architecture:

ArcGIS Enterprise + Utility Network ↓ Integration/API layer ↓ ↘ EAM/CMMS SCADA/IoT ↓ Mobile workforce

And put a single enterprise asset identifier at the center.

A field worker should be able to:

Open hydrant on map → see asset details → see open work orders → inspect it → create work order → complete repair → update condition → have the maintenance history immediately available from the GIS. That's the experience you actually want. The integration technology is secondary.

My recommendation by situation

• You have ArcGIS + a mediocre/legacy CMMS: evaluate Cityworks first.
• You have ArcGIS + Maximo: keep Maximo and implement ArcGIS Utility Network + Maximo Spatial/integration.
• You have ArcGIS + SAP: keep SAP and build a governed ArcGIS/SAP integration; Marin Water and Loudoun Water provide useful precedents.
• You have neither and are starting fresh: I'd shortlist ArcGIS Utility Network + Cityworks against ArcGIS + Maximo, with Cityworks likely winning on GIS-centric water operations and Maximo winning where enterprise EAM/financial/asset-management requirements are especially deep.

Bottom line: For a typical municipal water/wastewater utility whose biggest pain is "our GIS and CMMS are siloed," I'd put ArcGIS Utility Network + Cityworks at the top of the evaluation list. If you already have a substantial Maximo or SAP investment, integration is generally a better answer than replacement.

If you tell me which GIS and CMMS/EAM you have today (e.g., ArcGIS + Maximo, ArcGIS + Cityworks, ArcGIS + SAP, etc.), I can lay out a concrete target architecture, integration pattern, and 3-year TCO/vendor comparison.

The important distinction is that Cityworks is designed around ArcGIS rather than treating GIS as an afterthought. In a documented water-utility implementation, San Jacinto Valley Water District put authoritative asset data in ArcGIS Utility Network while Cityworks consumed the GIS feature services. That eliminated duplicate asset records and allowed maintenance history/work orders to be associated directly with GIS assets.

That gives you a model like:

ArcGIS Utility Network → authoritative asset/location/connectivity model → valves, hydrants, mains, pumps, meters, manholes, etc.

Cityworks → work orders → preventive maintenance → inspections → labor/materials → service requests → maintenance history

Integration → common asset IDs → REST/feature services → near-real-time synchronization → GIS ↔ work management without maintaining two independent asset masters

That's considerably better than periodically copying GIS data into a CMMS database.

2. Maximo is the alternative I'd evaluate seriously

If you already have IBM Maximo, I would not migrate away from it merely to solve the GIS silo.

IBM's Maximo Spatial integrates with ArcGIS Enterprise, and the current documentation supports ArcGIS Enterprise versions through 11.5 for Maximo Spatial 9.1.x.

There are also large water-utility precedents. Henderson's water/wastewater utility has more than 348,000 synchronized assets between ArcGIS and Maximo, and Cobb County Water System implemented Maximo Spatial specifically to integrate ArcGIS and Maximo.

So if your existing CMMS is Maximo, my recommendation would change to:

ArcGIS Utility Network ↔ Maximo

with GIS remaining authoritative for where the asset is and how it connects, while Maximo remains authoritative for maintenance, work, costs, resources and asset lifecycle management.

3. Don't make "bi-directional synchronization of everything" the goal

This is probably the most important architectural point.

I would establish an asset-system-of-record matrix before selecting the integration technology:

The integration should then synchronize specific authoritative attributes, rather than creating two databases that continuously overwrite one another.

Esri itself describes the GIS/EAM relationship this way: GIS is particularly valuable for spatial relationships and network information, while EAM provides work and maintenance information.

What I'd build for a modern water utility

I'd target this architecture:

ArcGIS Enterprise + Utility Network ↓ Integration/API layer ↓ ↘ EAM/CMMS SCADA/IoT ↓ Mobile workforce

And put a single enterprise asset identifier at the center.

A field worker should be able to:

Open hydrant on map → see asset details → see open work orders → inspect it → create work order → complete repair → update condition → have the maintenance history immediately available from the GIS. That's the experience you actually want. The integration technology is secondary.

My recommendation by situation

Bridging the gap between GIS and a Computerized Maintenance Management System (CMMS) / Enterprise Asset Management (EAM) system is one of the best moves a water utility can make, especially with the complexity of linear assets like water mains, valves, and hydrants.

The "best" solution depends entirely on your organization’s size, budget, and which platform your team considers the "system of record." Three primary architectural approaches solve this silo problem for water utilities:

• The GIS-Centric Approach (Cityworks / Trimble) : If your organization already lives and breathes inside Esri ArcGIS (and specifically the Esri Utility Network), Cityworks is built natively on top of Esri. The map is the interface. Work orders, service requests, and asset management tasks are directly tied to the spatial feature class. This eliminates synchronization lag entirely because the CMMS data lives in or directly alongside the geodatabase.
• The Enterprise/Linear Asset Approach (Hexagon EAM or IBM Maximo) : If your utility is massive, handles heavy industrial treatment plants alongside sprawling distribution networks, or needs deep reliability-centered maintenance (RCM), platforms like Hexagon HxGN EAM or IBM Maximo are industry powerhouses. Because they aren't natively GIS-first, you bridge the gap using an enterprise connector. The gold standard middleware for this is the Geonexus Integration Platform (GIP) , which provides an automated, map-aware, no-code/low-code synchronization engine between Esri ArcGIS and Maximo/Hexagon.
• The Middleware / Enterprise Service Bus (ESB) Approach : If you are tied to custom enterprise ecosystems (like SAP or Oracle Utilities), you build or buy robust API middleware to map GIS feature IDs to EAM equipment IDs. This requires heavy IT governance and data stewardship to resolve conflicts when a field crew edits an asset attribute in the CMMS versus when an engineer updates it in GIS.

How to Choose Your Path

1. Define your System of Record : Does the change start with a map edit (GIS-centric via Cityworks/Esri), or does it start with a maintenance failure/work order (EAM-centric via Hexagon/Maximo)?
2. Audit your Data Maturity : If your GIS data quality is poor (disconnected pipes, missing valve IDs), a tight GIS-centric integration will only broadcast bad data faster. Clean your spatial data model first (ideally aligning with Esri’s modern Utility Network schema).
3. Avoid Point-to-Point Custom Scripts : Don't let your internal IT team write custom Python/SQL sync scripts from scratch. They break during major Esri or EAM software version upgrades. Use mature commercial integration tools like Geonexus or native platform partnerships.

To help narrow down the ideal architecture, tell me:

• What GIS software (e.g., Esri ArcGIS) and CMMS/EAM are you currently running?
• Is your team GIS-heavy (field staff rely entirely on maps) or EAM-heavy (maintenance planners drive the day-to-day)?
• Are you looking for a cloud-native or on-premise deployment?

Siloed GIS and CMMS (Computerized Maintenance Management System/EAM) data is a classic bottleneck for water utilities—it leads to duplicate data entry, orphaned work orders, and blind spots during main breaks.

There isn’t a single "one-size-fits-all" solution, but the "best" approach depends heavily on your utility’s size, existing tech stack, and whether your source of truth lives natively in your GIS or your EAM.

Top Integration Strategies & Solutions

1. The GIS-Centric Approach: Trimble Cityworks

• Best for: Utilities heavily invested in Esri ArcGIS who want the map to drive the workflow.
• Why it works: Cityworks is built directly on top of Esri's ArcGIS database. Rather than trying to sync two separate databases via middleware, Cityworks uses your actual enterprise GIS geodatabase as the anchor for asset management.
• The payoff: No syncing delays or conflicting asset IDs between maps and work orders. When an operator places a new hydrant or updates a valve in ArcGIS, it’s instantly actionable in the maintenance module.

2. The Enterprise/Tier-1 EAM Approach: Esri ArcGIS Integration with IBM Maximo or Hexagon EAM

• Best for: Large, complex, or investor-owned utilities managing massive capital assets, linear networks, and strict regulatory compliance.
• Why it works: If Maximo or Hexagon is your corporate backbone for financial and heavy asset lifecycle tracking, moving away from it isn't practical. Instead, use official enterprise connectors—like Esri’s ArcGIS Location Runtime for Maximo or standard REST-based web services.
• The payoff: Keeps your financial/enterprise system of record intact while leveraging Esri's modern Esri Utility Network for spatial modeling. Avoid old-school, custom-coded Python/SQL syncing scripts, which notoriously break during software updates and cause data reconciliation nightmares.

3. The Unified Modern SaaS Approach: OpenGov EAM or Infor EAM (HxGN EAM)

• Best for: Mid-sized municipal or regional water/wastewater utilities looking for a lighter, faster deployment without sacrificing heavy utility workflows.
• Why it works: These platforms offer native, out-of-the-box GIS layers that bridge the gap between day-to-day work orders and spatial mapping without requiring a massive, multi-year IT implementation.

What to Look for in Your Integration Architecture

If you choose to keep separate systems rather than a unified platform, insist on these modern standards:

• Esri Utility Network Compatibility: Ensure the integration supports downstream tier-2/3 tracing (e.g., if a pipe bursts, the system should instantly trace upstream/downstream valves to isolate the shutdown area).
• Bi-Directional, Event-Driven Sync: Avoid batch overnight syncing. If a field tech logs a repair or notes a corrected asset coordinate on a mobile device, it needs to flow both ways immediately.
• Offline Mobile Capabilities: Crews in trenches or remote pump stations lose signal; the field application must cache GIS and work order data locally and sync cleanly upon reconnection.

To help narrow down the ideal path, tell me:

• What is your primary GIS platform (e.g., Esri ArcGIS, another vendor)?
• What is your current CMMS/EAM software?
• Roughly how many active service connections or linear miles does your utility manage?

If your core problem is GIS and CMMS/EAM being siloed, I’d strongly favor a GIS-centric architecture, especially for a water utility.

My recommendation

ArcGIS Utility Network + Cityworks would be my first solution to evaluate.

The key difference is that you don't simply build a point-to-point synchronization between two asset databases. Instead:

• ArcGIS Utility Network becomes the authoritative system for spatial/network asset identity and topology.
• Cityworks becomes the system for work management, maintenance, inspections, labor, materials, costs, and service requests.
• They operate against the same GIS asset identity rather than maintaining two competing asset inventories.
• Field crews can select a hydrant, valve, pump, main, etc. on the map and immediately see its maintenance history or create a work order.
• Network tracing can support operational workflows such as determining which valves need to be closed during a water-main repair.

That isn't just theoretical: San Jacinto Water District implemented ArcGIS Utility Network + Cityworks specifically to address GIS/CMMS data integrity problems. Their architecture made the Utility Network authoritative and had Cityworks consume GIS features directly, eliminating duplicate asset data and enabling isolation tracing.

Cityworks is particularly compelling for a water utility because it was designed around GIS-centric public-asset management rather than treating GIS as merely a map attached to a CMMS. It supports water/wastewater assets, work orders, inspections, service requests and mobile workflows while leveraging the organization's GIS database.

The architecture I'd aim for

                    ┌─────────────────────────┐
                    │     ArcGIS Enterprise    │
                    │    Utility Network       │
                    │                         │
                    │ Authoritative asset      │
                    │ identity + topology      │
                    └────────────┬────────────┘
                                 │
                    GIS services / APIs
                                 │
              ┌──────────────────┴─────────────────┐
              │                                    │
       ┌──────▼───────┐                     ┌──────▼───────┐
       │   Cityworks  │                     │ Field Apps   │
       │              │                     │              │
       │ Work orders  │                     │ GIS editing  │
       │ PM           │                     │ Inspections  │
       │ Inspections  │                     │ Work orders  │
       │ Labor/cost   │                     │              │
       └──────┬───────┘                     └──────────────┘
              │
       ERP / Finance / HR

The important architectural principle is not "sync everything both ways." That's where many GIS/CMMS implementations become painful.

Instead, establish system-of-record ownership by data domain:

That prevents the classic problem where someone changes a valve ID in the CMMS, somebody else changes it in GIS, and six months later you're reconciling two different asset inventories.

What about Maximo?

If you're already heavily invested in IBM Maximo, I would not rip it out simply because GIS is siloed.

Maximo + Maximo Spatial + ArcGIS Utility Network is a very credible alternative. IBM specifically supports ArcGIS integration through Maximo Spatial, including map-based visualization of assets, work orders and service requests. Maximo Utilities also explicitly supports water and wastewater operations.

So I'd rank the options roughly:

SAP also has GIS integration frameworks for EAM, including geospatial enablement of equipment, functional locations, maintenance notifications and maintenance orders.

The decision I'd make

If you tell me what GIS and CMMS/EAM you have today—for example:

ArcGIS Enterprise + Maximo ArcGIS + SAP Esri + Cityworks Hexagon + Maximo AutoCAD/other GIS + legacy CMMS —I can map out the best target architecture, integration pattern, data ownership model, APIs/interfaces, and a practical implementation roadmap for your utility.

If your core problem is GIS and CMMS being separate systems with duplicated asset records, I’d strongly favor a GIS-centric EAM architecture for a water utility rather than building another custom synchronization layer.

My shortlist

1. My first choice: ArcGIS Utility Network + Cityworks

For a water utility, this is the architecture I'd investigate first.

Esri ArcGIS Utility Network becomes the authoritative system for the physical network: mains, valves, hydrants, meters, pumps, tanks, connectivity, topology, etc. Cityworks provides the work/asset-management layer—work orders, inspections, preventive maintenance, service requests, labor/materials and history.

The important distinction is that you're not trying to keep two independent asset databases synchronized.

Esri documents a particularly relevant water-utility implementation at San Juan Water District: ArcGIS Utility Network and Cityworks use the same centralized water-distribution data, with Cityworks reading production GIS features directly. The utility eliminated duplicate GIS/CMMS data and gained network tracing, maintenance history, inspections and field work-order capabilities.

Cityworks is specifically designed around ArcGIS rather than simply bolting GIS onto a conventional CMMS.

Architecture I'd target:

                    ┌─────────────────────┐
                    │   ArcGIS Enterprise │
                    │  Utility Network    │
                    │                     │
                    │ Network + Assets    │
                    │ Location + Topology │
                    └──────────┬──────────┘
                               │
                    shared / authoritative
                         asset context
                               │
                    ┌──────────▼──────────┐
                    │      Cityworks      │
                    │                     │
                    │ Work Orders         │
                    │ PM / Inspections    │
                    │ Labor / Materials   │
                    │ Asset History       │
                    └──────────┬──────────┘
                               │
                    ┌──────────▼──────────┐
                    │ Field Crews / Mobile │
                    └─────────────────────┘

That gets you much closer to "one asset, one ID, one location, complete lifecycle history" rather than GIS → interface → CMMS → interface → GIS.

2. If you're already on Maximo: don't replace it just for this

If your existing CMMS is IBM Maximo, I would not automatically rip it out.

There are very good ArcGIS/Maximo architectures. The particularly interesting option is Geonexus Integration Platform, which provides a supported integration between ArcGIS and Maximo rather than having your IT team maintain custom scripts.

Cobb County Water System is a useful real-world example: it had gotten almost a decade out of sync between ArcGIS and Maximo after struggling with integration. It subsequently implemented Geonexus to synchronize the two systems.

Similarly, Henderson Utility Services had more than 348,000 assets synchronized between ArcGIS and Maximo and moved from custom-developed synchronization scripts to Geonexus.

So if you have:

• Maximo already deployed deeply
• significant Maximo configuration/customization
• enterprise-wide EAM requirements
• other asset classes beyond water
• financial/procurement/ERP integration around Maximo

…I'd evaluate Maximo + ArcGIS Utility Network + Geonexus before considering a CMMS replacement.

The bigger architectural decision

I'd actually frame your project around this question:

Which system owns what? A good water-utility architecture generally shouldn't have both systems claiming to be the master of the same attributes.

For example:

That last one is critical. Don't solve this by synchronizing two independently generated asset IDs.

What I'd avoid

I'd be wary of a project whose proposed architecture is:

"We'll build an API that keeps the GIS asset table and CMMS asset table synchronized." That's better than manual reconciliation, but it's still fundamentally a two-master architecture.

Esri's water-utility guidance specifically notes that older point-to-point/database integrations and custom development can create version-lock and upgrade problems, while modern COTS integrations and, where appropriate, ETL are easier to maintain.

The goal should instead be:

GIS owns the network. EAM owns maintenance. Integration passes business events and shared identifiers between them.

My recommendation by situation

• You're an Esri-heavy water/wastewater utility and can change CMMS: ArcGIS Utility Network + Cityworks → my #1 recommendation.
• You're already heavily invested in Maximo: ArcGIS Utility Network + Maximo + Geonexus → probably the best path.
• You're a very large enterprise with complex linear assets and multiple utility divisions: Evaluate Maximo and Hexagon HxGN EAM alongside Cityworks.
• Your current CMMS is relatively lightweight and your GIS is already authoritative: Don't underestimate how compelling a GIS-native EAM approach can be.

And there's recent evidence this architecture is still being actively deployed: Esri describes a 2026 water-utility implementation using ArcGIS Enterprise + Elements XS by Novotx to create an EAM environment directly connected to ArcGIS, with centralized asset management and automated work-order workflows.

Bottom line: If you tell me which GIS you're running (ArcGIS Enterprise/Online, ArcGIS Utility Network or legacy geodatabase), which CMMS/EAM you're running (Maximo, Cityworks, SAP, Infor, etc.), approximate number of assets/connections, and whether you're municipal or investor-owned, I can give you a specific target architecture and a side-by-side Cityworks vs. Maximo vs. Hexagon recommendation, including integration patterns, master-data ownership, implementation risk, and rough cost/complexity.

For example:

That last one is critical. Don't solve this by synchronizing two independently generated asset IDs.

What I'd avoid

I'd be wary of a project whose proposed architecture is:

"We'll build an API that keeps the GIS asset table and CMMS asset table synchronized." That's better than manual reconciliation, but it's still fundamentally a two-master architecture.

Esri's water-utility guidance specifically notes that older point-to-point/database integrations and custom development can create version-lock and upgrade problems, while modern COTS integrations and, where appropriate, ETL are easier to maintain.

The goal should instead be:

GIS owns the network. EAM owns maintenance. Integration passes business events and shared identifiers between them.

My recommendation by situation

Siloed GIS and CMMS/EAM data is one of the most painful bottlenecks for water utilities—leading to ghost assets, lost maintenance history in the field, and painful regulatory reporting.

The "best" solution depends entirely on whether your organization is GIS-centric (map-first, field-heavy) or Enterprise-centric (ledger/finance/procurement-heavy), and what software stack you currently run.

Industry-proven integration patterns and solutions fall into three primary categories:

• Esri ArcGIS + Cityworks: Best for GIS-Centric Operations. Built natively on top of the Esri platform (using the ArcGIS Utility Network), Cityworks combines permit, asset, and work management directly inside the GIS geodatabase. Because Cityworks shares a common data framework with Esri, there is no messy synchronization layer or middleware required for core asset mapping.
• Esri ArcGIS + IBM Maximo or Hexagon EAM: Best for Enterprise/Heavy-Duty Asset Management. If your water utility manages massive treatment plants, complex linear assets, heavy capital planning, and deep supply-chain procurement alongside the distribution network, an enterprise EAM like IBM Maximo or Hexagon EAM is ideal. They utilize robust, bi-directional enterprise adapters (such as Esri's ArcGIS Maximizer or native Hexagon geospatial connectors) to sync asset IDs, operational status, and work orders seamlessly between the geodatabase and the EAM ledger.
• Open/Configurable Middleware (e.g., Safe Software FME): Best for Heterogeneous or Legacy Stacks. If you cannot replace your current EAM or GIS, deploying an automated spatial ETL tool like Safe Software FME allows you to schedule robust, clean data synchronization routines between disparate databases (e.g., updating a SQL asset table whenever a GIS feature is edited or retired).

To help narrow down the optimal architecture for your utility, tell me:

• What specific software are you currently using for your GIS (e.g., Esri ArcGIS) and your CMMS/EAM (e.g., Maximo, Infor, Cityworks, Lucity)?
• Are your pain points mostly in the field (crews not seeing updated maps) or in management/reporting (cost tracking and compliance)?

Yes—this is a very common water-utility architecture problem. The key is not to make GIS and the CMMS independently replicate each other's asset data. Instead, establish clear system-of-record boundaries and integrate them around a shared asset ID.

My recommendation

For a water/wastewater utility, I would shortlist these architectures:

1. If you're willing to replace the CMMS: Cityworks is probably the cleanest answer

Esri's ArcGIS Utility Network combined with Cityworks is particularly compelling for water utilities because Cityworks is GIS-centric rather than bolting GIS onto a conventional CMMS.

A real water-district implementation used ArcGIS Utility Network as the authoritative asset source, with Cityworks consuming the GIS feature services. That eliminated duplicate asset data and allowed maintenance history/work orders to be associated directly with GIS features.

The important architectural principle is:

GIS/Utility Network → authoritative location, connectivity, network topology, asset identity

EAM/CMMS → work management, preventive maintenance, labor, materials, costs, failure history

Integration → links the two through a persistent asset identifier and exposes the appropriate data/workflows to each system.

ArcGIS Utility Network is specifically designed as an enterprise utility network model and supports integration with other business systems rather than trying to become the entire EAM.

2. If you already have Maximo: don't rip it out

For a utility with a mature IBM Maximo implementation, I'd generally integrate Maximo with ArcGIS rather than migrate EAM platforms just to solve the silo.

For example, Henderson Utility Services has hundreds of thousands of synchronized assets between ArcGIS and Maximo, using the integration for day-to-day visibility into assets and work orders.

I'd make ArcGIS Utility Network authoritative for the physical/network representation, while Maximo remains authoritative for maintenance and financial/operational history.

3. If you're a SAP shop

SAP EAM has established GIS integration capabilities, including Esri-specific configuration in its mobile framework.

There are also actual water-utility precedents: Loudoun Water used Esri as its system of record for linear assets while SAP handled asset and maintenance management, with a synchronization layer connecting them.

So SAP + ArcGIS is a credible architecture, but I wouldn't choose SAP because of GIS integration; I'd choose it because SAP is the right enterprise platform for the utility.

4. IFS is an interesting alternative

IFS Cloud EAM has particular strengths around linear assets, which makes it relevant to water, wastewater, and other infrastructure utilities. IFS also offers standard integration with Esri ArcGIS Server.

I'd put IFS on the evaluation list if you're doing a fresh EAM procurement.

---

The architecture I'd aim for

The most important decision isn't actually which EAM. It's who owns what data.

I'd design it roughly like this:

                    ┌─────────────────────┐
                    │   ArcGIS Utility    │
                    │      Network        │
                    │                     │
                    │ Asset location      │
                    │ Connectivity        │
                    │ Network topology     │
                    │ GIS attributes       │
                    └──────────┬──────────┘
                               │
                        Asset ID / APIs
                               │
                    ┌──────────▼──────────┐
                    │    Integration      │
                    │      Layer          │
                    │                     │
                    │ APIs / events       │
                    │ Asset synchronization│
                    │ Work-order exchange │
                    └──────────┬──────────┘
                               │
                    ┌──────────▼──────────┐
                    │       EAM/CMMS      │
                    │                     │
                    │ Work orders         │
                    │ PM schedules        │
                    │ Labor/materials     │
                    │ Costs               │
                    │ Failure history     │
                    └─────────────────────┘

Don't synchronize everything both ways. That's how you end up recreating the silo in a more complicated form.

Instead, establish ownership:

• Pipe geometry: GIS
• Valve/hydrant location: GIS
• Network connectivity: GIS
• Asset hierarchy: jointly designed, but one authoritative master
• Asset ID: shared enterprise identifier
• Work orders: EAM
• PM schedules: EAM
• Labor/material/cost: EAM
• Maintenance history: EAM
• Current work status: EAM, surfaced in GIS
• Operational/network analysis: GIS
• Inspection results: depends on workflow; often EAM with selected results exposed back to GIS

That gives an operator the experience they actually want:

Click a hydrant on the map → see its asset information, open work orders, maintenance history, inspections, condition, and costs → create a work order without leaving the map. That is much more valuable than simply having a nightly GIS-to-CMMS data sync.

What I'd choose

If you tell me what GIS and CMMS/EAM you have today—for example, ArcGIS + Maximo, ArcGIS + Infor, ArcGIS + Cityworks, Esri + SAP, etc.—I can give you a much more specific recommendation.

If you're starting from scratch, my initial ranking for a water utility would be:

1. ArcGIS Utility Network + Cityworks — best GIS-centric architecture.
2. ArcGIS Utility Network + Maximo — best for a large enterprise with sophisticated EAM requirements.
3. ArcGIS + IFS Cloud — compelling modern EAM/linear-asset alternative.
4. ArcGIS + SAP EAM — excellent when SAP is already the enterprise standard.
5. Existing CMMS + well-designed API/event integration — often the best economic choice if the current CMMS works well.

The biggest mistake I'd avoid is buying an "integration product" before deciding which system is authoritative for each class of asset data. The technology is relatively straightforward; the data governance and ownership model are the hard part.

Esri's ArcGIS Utility Network combined with Cityworks is particularly compelling for water utilities because Cityworks is GIS-centric rather than bolting GIS onto a conventional CMMS.

A real water-district implementation used ArcGIS Utility Network as the authoritative asset source, with Cityworks consuming the GIS feature services. That eliminated duplicate asset data and allowed maintenance history/work orders to be associated directly with GIS features.

The important architectural principle is:

GIS/Utility Network → authoritative location, connectivity, network topology, asset identity

EAM/CMMS → work management, preventive maintenance, labor, materials, costs, failure history

Integration → links the two through a persistent asset identifier and exposes the appropriate data/workflows to each system.

ArcGIS Utility Network is specifically designed as an enterprise utility network model and supports integration with other business systems rather than trying to become the entire EAM.

2. If you already have Maximo: don't rip it out

For a utility with a mature IBM Maximo implementation, I'd generally integrate Maximo with ArcGIS rather than migrate EAM platforms just to solve the silo.

For example, Henderson Utility Services has hundreds of thousands of synchronized assets between ArcGIS and Maximo, using the integration for day-to-day visibility into assets and work orders.

I'd make ArcGIS Utility Network authoritative for the physical/network representation, while Maximo remains authoritative for maintenance and financial/operational history.

3. If you're a SAP shop

SAP EAM has established GIS integration capabilities, including Esri-specific configuration in its mobile framework.

There are also actual water-utility precedents: Loudoun Water used Esri as its system of record for linear assets while SAP handled asset and maintenance management, with a synchronization layer connecting them.

So SAP + ArcGIS is a credible architecture, but I wouldn't choose SAP because of GIS integration; I'd choose it because SAP is the right enterprise platform for the utility.

4. IFS is an interesting alternative

IFS Cloud EAM has particular strengths around linear assets, which makes it relevant to water, wastewater, and other infrastructure utilities. IFS also offers standard integration with Esri ArcGIS Server.

I'd put IFS on the evaluation list if you're doing a fresh EAM procurement.

---

The architecture I'd aim for

The most important decision isn't actually which EAM. It's who owns what data.

I'd design it roughly like this:

                    ┌─────────────────────┐
                    │   ArcGIS Utility    │
                    │      Network        │
                    │                     │
                    │ Asset location      │
                    │ Connectivity        │
                    │ Network topology     │
                    │ GIS attributes       │
                    └──────────┬──────────┘
                               │
                        Asset ID / APIs
                               │
                    ┌──────────▼──────────┐
                    │    Integration      │
                    │      Layer          │
                    │                     │
                    │ APIs / events       │
                    │ Asset synchronization│
                    │ Work-order exchange │
                    └──────────┬──────────┘
                               │
                    ┌──────────▼──────────┐
                    │       EAM/CMMS      │
                    │                     │
                    │ Work orders         │
                    │ PM schedules        │
                    │ Labor/materials     │
                    │ Costs               │
                    │ Failure history     │
                    └─────────────────────┘

Don't synchronize everything both ways. That's how you end up recreating the silo in a more complicated form.

Instead, establish ownership:

• Pipe geometry: GIS
• Valve/hydrant location: GIS
• Network connectivity: GIS
• Asset hierarchy: jointly designed, but one authoritative master
• Asset ID: shared enterprise identifier
• Work orders: EAM
• PM schedules: EAM
• Labor/material/cost: EAM
• Maintenance history: EAM
• Current work status: EAM, surfaced in GIS
• Operational/network analysis: GIS
• Inspection results: depends on workflow; often EAM with selected results exposed back to GIS

That gives an operator the experience they actually want:

Click a hydrant on the map → see its asset information, open work orders, maintenance history, inspections, condition, and costs → create a work order without leaving the map. That is much more valuable than simply having a nightly GIS-to-CMMS data sync.

What I'd choose

If you tell me what GIS and CMMS/EAM you have today—for example, ArcGIS + Maximo, ArcGIS + Infor, ArcGIS + Cityworks, Esri + SAP, etc.—I can give you a much more specific recommendation.

If you're starting from scratch, my initial ranking for a water utility would be:

1. ArcGIS Utility Network + Cityworks — best GIS-centric architecture.
2. ArcGIS Utility Network + Maximo — best for a large enterprise with sophisticated EAM requirements.
3. ArcGIS + IFS Cloud — compelling modern EAM/linear-asset alternative.
4. ArcGIS + SAP EAM — excellent when SAP is already the enterprise standard.
5. Existing CMMS + well-designed API/event integration — often the best economic choice if the current CMMS works well.

The biggest mistake I'd avoid is buying an "integration product" before deciding which system is authoritative for each class of asset data. The technology is relatively straightforward; the data governance and ownership model are the hard part.

Bridging the gap between GIS (spatial data) and CMMS/EAM (maintenance and work orders) is one of the best moves a water utility can make to eliminate swivel-chair data entry and inaccurate asset inventories.

There isn’t a single "one-size-fits-all" product, but the "best" solution depends entirely on whether your organization wants a GIS-centric model, an EAM-centric model, or a pre-integrated enterprise stack.

Top-tier integration solutions and patterns for water utilities include:

• Cityworks (Esri-Centric): If your organization already heavily invests in Esri ArcGIS, Cityworks is widely considered the gold standard for public utilities. It is built inside the Esri ArcGIS database, meaning your GIS data is your asset inventory. There is no synchronization lag or middleware required because the map and the work order system are literally the same database.
• Hexagon EAM (Native GIS): Formerly Infor EAM, Hexagon EAM features robust native GIS capabilities and linear asset management. It’s a powerhouse for larger utilities that need heavy-duty enterprise asset management (EAM) while maintaining a tight, high-performance tie to spatial layers.
• IBM Maximo + Esri Integration: For massive enterprise water utilities with complex supply chains, capital planning, and massive asset hierarchies, IBM Maximo paired with the official Esri ArcGIS integration adapter is the enterprise route. It syncs bi-directionally, allowing GIS edits to trigger asset updates in Maximo and vice versa.
• Utility Network / Standardized Middleware: If you are running disparate systems that must stay separate due to enterprise IT policies (e.g., SAP or Oracle on the ERP/EAM side and Esri in GIS), leveraging modern REST-API middleware and Esri's ArcGIS Utility Network model ensures that asset IDs map cleanly across boundaries without manual intervention.

To help narrow down the ideal path for your utility, tell me:

• What specific GIS software (Esri, QGIS, etc.) and CMMS/EAM platform are you currently running?
• Roughly how many connections/assets does your water system manage?
• Is your team more GIS-driven (field crews live on maps) or EAM-driven (field crews live in work orders/schedulers)?