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

Bridging the gap between GIS (spatial truth) and your CMMS/EAM (operational truth) is one of the best moves a water utility can make to stop data duplication and streamline field work.

The "best" solution depends entirely on your existing tech stack, budget, and IT bandwidth. There is no single silver bullet, but the industry generally relies on three primary approaches:

1. The Native/Co-Managed Ecosystem (Esri + Cityworks)

If your GIS is built on Esri ArcGIS (the gold standard for water utilities), pairing it with Cityworks is often considered the most seamless native approach.

• How it works: Cityworks was explicitly built on top of Esri's ArcGIS Esri Asset Package data model. There is no complex middleware syncing geometry back and forth because the Esri geodatabase is the asset repository.
• Best for: Utilities heavily invested in Esri looking for a true GIS-centric public asset management system.

2. The Enterprise Middleware / Integration Platform (Geonexus)

If you are running a heavy-duty EAM like IBM Maximo, Hexagon EAM (HxGN EAM) , or SAP , but your operations and engineering teams refuse to leave ArcGIS, you need an enterprise integration layer.

• How it works: Instead of writing custom, fragile API scripts that break during software updates, utilities use specialized enterprise integration platforms like the Geonexus Integration Platform (GIP). GIP provides out-of-the-box, no-code/low-code bidirectional synchronization between Esri ArcGIS and enterprise EAM/CMMS tools. It flags data discrepancies, handles map services, and maps attributes cleanly.
• Best for: Larger utilities or municipalities where the enterprise EAM and Esri GIS must remain separate systems of record, but need automated, reliable alignment.

3. All-in-One Enterprise Cloud Suites (Infor, Oracle, or Hexagon)

If your utility is already standardized on a massive ERP/EAM framework, leveraging native modules might make the most sense.

• How it works: Platforms like Hexagon EAM or Infor EAM feature robust linear asset management and built-in GIS mapping components that reduce the need for external third-party sync tools.
• Best for: Organizations looking to collapse multiple software vendors into a single corporate ecosystem, though migration costs and change management are high.

To help narrow down which path fits your utility, tell me:

• What GIS platform (e.g., Esri ArcGIS) and CMMS/EAM (e.g., Maximo, Infor, Cityworks) are you currently running?
• Is your preference to keep them as distinct systems synced via middleware or move toward a single integrated platform?
• Are your pain points mostly around work orders not showing on the map or asset ID mismatches between engineering and maintenance?

For a water utility, the best EAM/GIS integration solution is usually not a custom sync between two separate databases. The stronger pattern is to make GIS and EAM share a common asset model, with clear system-of-record ownership. For many water utilities already invested in Esri, the leading approaches are:

1. GIS-centric EAM: Trimble + Esri — best fit for many municipal water utilities

Architecture:

• ArcGIS Utility Network = authoritative asset location, connectivity, and network model
• Cityworks AMS = work orders, inspections, preventive maintenance, service requests
• Both operate against the same GIS asset foundation rather than maintaining duplicate asset inventories

This is often the cleanest model for water because most water assets are inherently spatial:

• water mains
• valves
• hydrants
• meters
• service lines
• pump stations
• tanks
• pressure zones

A successful pattern is:

ArcGIS Utility Network
        |
        | (shared asset IDs / services)
        |
Cityworks AMS
        |
        |
Work orders • PM • inspections • field workflows

San Juan Water District, for example, implemented ArcGIS Utility Network with Cityworks so that GIS became the authoritative asset source and work management could use those assets directly, eliminating duplicate data maintenance. Esri Cityworks is widely used in water/wastewater because it was built around GIS-centric asset management rather than treating maps as an add-on.

2. Enterprise EAM + GIS integration: IBM + ArcGIS — best for large or multi-utility organizations

Choose this if you have:

• electric + water + wastewater + gas under one enterprise asset platform
• complex asset hierarchies
• heavy regulatory reporting
• existing IBM Maximo expertise

Typical architecture:

ArcGIS
(asset location + network intelligence)
        |
        | APIs / integration services
        |
Maximo
(asset lifecycle + maintenance + cost history)

This can work extremely well, but it requires disciplined integration governance: asset IDs, synchronization rules, ownership, and change management. Henderson Utility Services, for example, integrated ArcGIS and Maximo across hundreds of thousands of assets.

3. Middleware integration — use only when you must keep existing systems

If replacing your CMMS is not realistic, use:

• REST APIs
• enterprise service bus
• ETL/data pipelines
• event-driven integrations

Avoid:

• nightly database copies
• manual Excel exports
• two-way uncontrolled synchronization

The biggest failure mode is ending up with:

• GIS says valve A exists at location X
• CMMS says valve A exists with a different ID and maintenance history
• field crews don't know which record is correct

Modern GIS/EAM implementations increasingly favor vendor-supported integrations and web services over fragile point-to-point database synchronization.

What I would recommend for a typical water utility

Small-to-mid municipal water utility (most common case)

ArcGIS Utility Network + Cityworks AMS

Best balance of:

• GIS alignment
• field usability
• valve/hydrant/main workflows
• inspections
• asset history
• lower integration complexity

Large regional utility or combined utility

ArcGIS + Maximo (or SAP/Oracle if already standardized)

Best when enterprise asset governance matters more than GIS-native workflows.

The implementation details matter more than the software

Before selecting a platform, establish:

1. Asset master strategy

• Which system owns asset IDs?
• Who creates new assets?
• Who retires assets?

2. Common identifiers

• GIS GlobalID ↔ EAM asset number mapping

3. Asset hierarchy Example:

Water Treatment Plant
  └── Pump Station
      └── Pump
          └── Motor

4. Field workflows

• leak repair
• valve exercising
• hydrant inspection
• meter replacement
• main breaks

5. Data quality rules

• no orphan work orders
• no assets without location
• no maintenance history detached from assets

A useful decision rule:

• “GIS is our asset inventory and operations revolve around maps” → Cityworks
• “We need enterprise-wide asset management across many business units” → Maximo/SAP/Oracle
• “We only need to connect existing systems” → API-based integration

If you share your utility size (connections/miles of pipe), current GIS platform (Esri or other), and CMMS (Maximo, SAP, Cityworks, Lucity, etc.), I can narrow this to a recommended target architecture.

If the core problem is GIS and CMMS being separate systems with duplicated asset records, I’d strongly favor a GIS-native EAM architecture for a water utility—especially if you’re already an Esri shop.

My short answer

Best overall for a water/wastewater utility: ArcGIS Utility Network + Cityworks.

Trimble Cityworks is unusually well suited because it was built around Esri rather than bolted onto a separate GIS. A strong target architecture is:

ArcGIS Utility Network = authoritative spatial/asset model ↓ Cityworks = work, inspection, service request & maintenance management ↓ Field Maps / mobile = field execution ↓ SCADA / AMI / customer systems / ERP = connected systems

San Juan Water District is a particularly good example: it moved to ArcGIS Utility Network + Cityworks so the CMMS could work directly from authoritative GIS features rather than maintaining a duplicate asset database. The utility reports eliminating duplicate data/workflows and being able to trace the network during water-main repairs.

Why I'd rank the options this way

The important distinction is that Cityworks changes the architecture, whereas Maximo/Hexagon/SAP generally require you to integrate two independently designed systems.

If you already have Maximo

I wouldn't automatically replace it.

There are good examples of large water utilities successfully connecting ArcGIS and Maximo. Cobb County Water System, for example, had ArcGIS and Maximo that had drifted almost a decade apart. It ultimately implemented the Geonexus Integration Platform to synchronize the two environments.

The City of Henderson's water/wastewater operation is another example: it has more than 348,000 synchronized assets between ArcGIS and Maximo and uses Geonexus to address the integration/version-lock problem created by custom scripts.

IBM's own Maximo Utilities offering supports water treatment and wastewater and includes GIS capabilities through Maximo Spatial.

So if you're already heavily invested in Maximo, I'd evaluate:

ArcGIS Utility Network + Maximo + Geonexus

rather than ripping out Maximo.

Geonexus is particularly interesting because it provides a supported integration layer between ArcGIS and systems such as Maximo, SAP and Hexagon rather than forcing you into brittle point-to-point scripts.

The architecture I'd recommend

The biggest mistake would be to define the project as merely "integrate GIS with CMMS."

I'd instead establish system-of-record ownership.

For example:

Then use a stable asset ID to tie everything together.

That is much better than trying to make GIS and EAM two-way mirrors of each other.

The key design principle

I'd aim for:

One asset, one authoritative identity, many systems consuming it. Not:

GIS asset ↔ synchronization engine ↔ CMMS asset ↔ synchronization engine ↔ ERP asset. The latter is how utilities end up with the exact silo problem you're describing.

And this isn't theoretical. San Juan Water's previous architecture duplicated GIS data into its CMMS and created asset-naming/integrity problems. Moving to Utility Network + Cityworks allowed Cityworks to work against production GIS features instead.

One caveat

If you're a very large enterprise utility with substantial requirements around inventory, procurement, complex work management, fleet, labor, financial integration, capital projects, etc., I'd give Maximo a very serious look. IBM specifically positions Maximo Utilities across electric, gas, water treatment and wastewater on one platform.

But if your primary pain is:

"Our water network lives in Esri, while maintenance lives in a separate CMMS, and we're constantly reconciling the two,"

then Cityworks + ArcGIS Utility Network is probably the architecture I'd put at the top of the shortlist.

If you tell me (1) your current GIS (Esri/other), (2) current CMMS/EAM, (3) approximate number of water/sewer assets or connections, and (4) whether you're municipal or investor-owned, I can give you a much more specific 3-option architecture and vendor shortlist, including where I'd put the integration layer and which system should own each data domain.

There is no single "best" product in a vacuum, but rather the right architectural approach depending on whether your organization is GIS-centric or EAM/CMMS-centric . Because water utilities rely heavily on spatial accuracy (valves, pipes, hydrants) and heavy maintenance scheduling, bridging the gap requires a framework where data flows seamlessly without dual-entry.

The top integration solutions and architectures generally fall into three proven categories:

• The GIS-First/Native Approach (Trimble Cityworks): If your engineering and GIS teams are the source of truth and you want work orders built directly on top of Esri ArcGIS, Trimble Cityworks is widely considered the gold standard. It doesn’t "integrate" via middleware; it embeds maintenance management directly into the Esri geodatabase.
• The Enterprise/Deep Asset Approach (Hexagon EAM or IBM Maximo): If your operations are driven heavily by complex plant maintenance, reliability engineering, and heavy asset depreciation, platforms like Hexagon EAM or IBM Maximo offer powerful native GIS connectors (such as Esri integrations) that sync enterprise work history directly to map features.
• The Unified/Single-Database Approach (OpenGov EAM): For smaller-to-midsize municipal water utilities trying to escape the silo trap entirely, unified systems like OpenGov EAM combine GIS mapping, work orders, and capital planning into a single connected platform so you never have to worry about sync failures between two separate databases.

Choosing the Right Path Forward

1. Identify your System of Record: Determine whether GIS (Esri) or your CMMS should drive asset creation. If an asset is added in the field or GIS, it should automatically spawn in the EAM.
2. ** Leverage Esri Utility Network:** Modernize your spatial data model using the ArcGIS Utility Network framework. Any modern EAM integration you choose must be compatible with this architecture to handle complex sub-surface water tracing and isolation.
3. Avoid Custom Middleware if Possible: Opt for out-of-the-box native connectors (like Esri-to-Cityworks or Esri-to-Hexagon/Maximo) rather than custom-coded API scripts that break during software updates.

To help narrow down the ideal solution, tell me:

• What is your current GIS software (e.g., Esri ArcGIS, QGIS) and current CMMS/EAM?
• Is your utility a smaller municipality , a county district , or a large enterprise utility?
• Do you prefer a single unified software or keeping your current core platform and adding a bridge/connector?

Yes. If the core problem is “our GIS and CMMS are separate systems and constantly drift out of sync,” I would not start by buying another generic integration/middleware product. For a water utility, the best architecture is usually GIS-centered asset management, with the GIS/utility network as the authoritative source for where the asset is and how it connects, and the EAM/CMMS as the authoritative source for maintenance, labor, cost, materials, and work history.

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 gives you a connected network model for mains, valves, hydrants, pumps, meters, etc., including topology and tracing.

Trimble Cityworks then puts work orders, inspections, service requests and asset management directly into that GIS-centric environment.

A particularly relevant example is San Juan Water District. They moved to ArcGIS Utility Network + Cityworks specifically because their old CMMS/GIS arrangement required synchronization and was producing asset duplication and data-integrity problems. Their resulting architecture uses the Utility Network as the authoritative data source, with Cityworks reading the GIS services directly.

That's almost exactly the problem you're describing.

Why I like it for water:

• One authoritative asset ID
• GIS remains authoritative for spatial/network information
• Work history stays associated with the mapped asset
• Field crews can start/complete work from the map
• Network tracing can support isolation/outage planning
• Less custom synchronization code
• Much easier to expose the same asset to engineering, operations and maintenance

Esri's own water-utility guidance also recommends moving away from old point-to-point database integrations toward vendor-supported web-service integrations, with ETL reserved for cases where real-time exchange isn't necessary.

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

If your utility is already heavily invested in IBM Maximo, I'd look seriously at:

ArcGIS Utility Network ↔ Geonexus Integration Platform ↔ Maximo

rather than trying to rip out Maximo.

This is not theoretical. Cobb County Water System had ArcGIS and Maximo that had become badly out of sync, with work orders and assets no longer being consistently reflected in both systems. They implemented the Geonexus Integration Platform to establish bidirectional synchronization.

Likewise, Henderson's water/wastewater utility had roughly 348,000 synchronized assets between ArcGIS and Maximo and selected Geonexus to replace its custom synchronization scripts. The platform provides bidirectional synchronization and integration monitoring without requiring custom code.

That's a very compelling reference architecture if your CMMS is Maximo.

3. Another Maximo option: ActiveG

If your priority is GIS-driven field workflows rather than simply keeping two databases synchronized, I'd also evaluate ActiveG's Nash Workflows.

It provides code-free workflows between ArcGIS and EAM systems such as Maximo using REST APIs, including inspection and maintenance workflows built around ArcGIS field applications.

For example:

ArcGIS Field Maps / Survey123 → inspection → create Maximo work order → execute maintenance → return status/history to GIS

That's much more valuable operationally than simply replicating asset tables.

The architecture I'd recommend

I'd aim for something like:

                 ┌──────────────────────────┐
                 │     ArcGIS Utility        │
                 │        Network            │
                 │                          │
                 │ AUTHORITATIVE NETWORK    │
                 │ • Asset ID               │
                 │ • Location               │
                 │ • Connectivity            │
                 │ • Network topology        │
                 │ • Valve/main relationships│
                 └────────────┬─────────────┘
                              │
                    API / supported connector
                              │
                 ┌────────────▼─────────────┐
                 │       EAM / CMMS          │
                 │                          │
                 │ AUTHORITATIVE WORK DATA  │
                 │ • Work orders             │
                 │ • PMs                     │
                 │ • Labor                   │
                 │ • Materials               │
                 │ • Costs                    │
                 │ • Maintenance history      │
                 └──────────────────────────┘
                              │
             ┌────────────────┼────────────────┐
             ▼                ▼                ▼
         Field crews      Operations       Engineering
       Field Maps/etc.    dashboards       planning

The important design decision is not to create a third "master asset database."

Instead, explicitly define ownership:

GIS owns

• spatial location
• network connectivity
• asset geometry
• network relationships
• GIS attributes

EAM owns

• maintenance history
• work orders
• preventive maintenance
• labor
• materials
• costs
• failure/repair history

Shared

• enterprise asset ID
• asset type
• operational status
• criticality
• selected condition attributes

That eliminates the fundamental cause of the silo problem.

Cityworks vs. Maximo

My rule of thumb:

Choose Cityworks if you're primarily a water/wastewater/public-works organization and Esri is already strategic. Its GIS-centric architecture is a major advantage.

Choose Maximo if you need a sophisticated enterprise EAM platform spanning water plus other asset-intensive departments, or you already have substantial Maximo investment. Then use a supported ArcGIS integration layer rather than building synchronization scripts yourself.

And I would strongly avoid custom database-to-database synchronization as the long-term answer. Esri specifically notes the upgrade/version-lock risks of that approach.

Bottom line

If I were evaluating this for a water utility today, my #1 architecture would be:

Esri ArcGIS Utility Network + Trimble Cityworks, with GIS as the network/asset-location system of record.

If you're already a Maximo shop, I'd instead shortlist:

ArcGIS Utility Network + Maximo + Geonexus

and compare that against Maximo + ActiveG Nash for workflow integration.

The key is that the procurement question shouldn't simply be “Which CMMS integrates with GIS?” It should be “Which platform gives us one authoritative asset identity and eliminates bidirectional data drift?” That's the distinction that tends to make these projects succeed.

The "best" solution for bridging the gap between GIS and your Computerized Maintenance Management System (CMMS) / Enterprise Asset Management (EAM) system depends largely on whether you want a GIS-centric architecture or an enterprise integration middleware approach.

For water utilities specifically, where linear assets (pipes, valves, hydrants) live and die by their spatial coordinates, here is how the top solutions break down:

• The GIS-Centric Leader: Trimble Cityworks
  • Best For: Utilities deeply standardized on Esri ArcGIS.
  • Why it works: Cityworks is uniquely "GIS-centric," meaning Esri’s geodatabase is the primary database of record for your assets. Work orders, inspections, and service requests are tied directly to the spatial features. If you are moving toward or already utilizing Esri's ArcGIS Utility Network, Cityworks natively respects those features, subtypes, and connectivity models without needing a secondary database sync.
• The Enterprise Heavyweights: Hexagon EAM or IBM Maximo
  • Best For: Large-scale or multi-departmental utilities (water, wastewater, electric, and gas combined) that manage complex vertical infrastructure alongside linear networks.
  • Why it works: Hexagon EAM (formerly Infor EAM) and IBM Maximo Application Suite offer superior reliability-centered maintenance, inventory management, and linear referencing capabilities. However, because they are EAM-centric rather than GIS-centric, you need a robust synchronization strategy to keep them aligned with Esri.
• The Dedicated Integration Middleware:
  • Best For: Organizations that already have an established EAM (like Maximo, Hexagon, or Infor) and an established Esri GIS, and need a reliable bridge between them.
  • Why it works: If you aren't looking to rip and replace your current CMMS or GIS, GIP provides a configurable, map-aware, no-code/low-code integration tool. It automates bi-directional data synchronizing, handles data transformations (like moving from geometric networks to the Utility Network), and prevents "version lock" during software upgrades.

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

• What CMMS/EAM software are you currently running?
• Are you currently using (or migrating to) Esri's ArcGIS Utility Network?
• Is your primary pain point daily work order mapping or long-term asset data synchronization?

If you share which specific GIS software (e.g., Esri ArcGIS) and which CMMS/EAM system you are currently using, I can give you a more specific architectural recommendation or migration path.

If your water utility already runs Esri ArcGIS, my first choice would be Trimble Cityworks AMS + ArcGIS Utility Network. The key reason is that it attacks the silo problem at the architecture level rather than simply building another synchronization layer.

My recommendation

1. Best fit for most water utilities: Cityworks + ArcGIS Utility Network

This is particularly strong when GIS is already your authoritative source for water assets. Cityworks is designed around ArcGIS rather than treating GIS as an external system. A good target architecture is:

ArcGIS Utility Network → authoritative asset/network model
Cityworks → work, maintenance, inspections, service requests, labor/costs
ArcGIS Field Maps/other Esri apps → field data capture
ERP/finance → purchasing, accounting, inventory where appropriate

A real-world San Juan Water District implementation uses ArcGIS Utility Network and Cityworks with production GIS features read directly by the CMMS, eliminating duplicated GIS data. They report being able to see maintenance history against GIS assets, perform network traces for outages, and create work orders in the field.

That's fundamentally different from:

GIS database ↔ ETL/API ↔ CMMS asset database

which tends to recreate the silo you're trying to eliminate.

2. Best alternative for a very large/complex enterprise: IBM Maximo + ArcGIS

I'd favor Maximo if you have a sophisticated enterprise EAM requirement—large asset hierarchy, extensive maintenance planning, inventory/procurement, complex facilities/plant assets, or a broader corporate Maximo strategy.

Maximo has mature ArcGIS integration through Maximo Spatial, including ArcGIS feature services and map-based asset management.

The tradeoff is that Maximo is an EAM platform that happens to integrate very well with GIS, whereas Cityworks is much closer to a GIS-centric EAM/CMMS. For a water distribution utility where location, connectivity, valves, hydrants, mains, meters, isolation zones, and field work are central, that distinction matters.

The architecture I'd aim for

The most important decision isn't actually "Cityworks vs. Maximo." It's who owns what data.

The critical principle is one asset identity, not two synchronized asset databases.

Esri's own water-utility guidance specifically describes the industry moving away from database-level point-to-point integrations toward vendor-supported, standards-based GIS/EAM integrations; ETL is appropriate when real-time exchange isn't required.

Why I'd lean Cityworks for your situation

If your problem statement is literally:

"Our GIS data is siloed from our CMMS."

then I'd investigate Cityworks first, particularly if you're already an Esri shop.

You can get to a model where a dispatcher or field technician clicks a valve on the map and immediately sees:

• asset information
• maintenance history
• open work
• inspections
• service requests
• failure history
• related assets
• network connectivity
• isolation/trace information

…and can create or execute the work without copying the asset into another database.

That's precisely the kind of workflow San Juan Water implemented.

One important caveat

Don't jump directly into implementing Utility Network or an EAM integration.

I'd first establish an enterprise asset model and authoritative-ID strategy. Esri itself recommends resolving major data-quality and configuration issues before deploying the Utility Network into production Enterprise services.

Then I'd run a pilot around one high-value workflow—water-main break → isolation trace → work order → field repair → as-built/GIS update → maintenance history. If that workflow works cleanly end-to-end, you've proven the architecture rather than just proving that two APIs can exchange records.

Bottom line:
ArcGIS Utility Network + Cityworks is my default recommendation for a GIS-centric water utility. ArcGIS + Maximo is the stronger choice when you need a heavyweight enterprise EAM across a larger, more complex organization.

If you tell me which GIS (ArcGIS Enterprise/Online, Utility Network or legacy geodatabase), which CMMS/EAM, approximate number of water assets/connections, and whether you have an ERP like SAP/Oracle, I can narrow this down to a specific target architecture and integration pattern.

Yes. For a water utility where GIS and CMMS/EAM are currently siloed, I’d strongly favor a GIS-centric asset-management architecture rather than trying to make two independent systems behave like one.

My top recommendation: ArcGIS Utility Network + Trimble Cityworks / Unity Maintain

If you’re already an Esri shop, this is probably the cleanest fit.

Target architecture:

ArcGIS Utility Network → authoritative asset/network record
↕
Trimble Cityworks / Unity Maintain → work management, inspections, maintenance, asset lifecycle
↕
Mobile field apps → crews update work, inspections, GPS/location, photos, redlines

Trimble describes Cityworks as a GIS-centric asset-management platform, and its current Unity Maintain product is the cloud-first evolution of Cityworks.

The important architectural decision is that you don't duplicate your GIS asset database into the CMMS. GIS remains authoritative for where the asset is and what it is, while EAM remains authoritative for maintenance history, labor, materials, costs, schedules, and work. That's much healthier than maintaining two competing asset masters.

A particularly relevant example is San Juan Water District, which implemented ArcGIS Utility Network + Cityworks with the Utility Network as the authoritative source. Cityworks reads the GIS features directly, eliminating duplicated GIS data and allowing maintenance history to be associated with the actual GIS asset.

When I'd choose Maximo instead

If you're a larger utility with complex enterprise asset management requirements, IBM Maximo is the other serious contender.

ArcGIS Utility Network + IBM Maximo is a strong architecture when you need things like:

• sophisticated preventive/predictive maintenance
• complex work planning and scheduling
• labor/crew management
• inventory and storerooms
• procurement
• asset financials
• treatment-plant as well as distribution-asset management
• enterprise-wide EAM beyond the water utility

IBM specifically offers Maximo Utilities capabilities for water treatment and wastewater treatment, and Maximo Spatial provides map-based asset/work-order management.

There are also mature ArcGIS–Maximo integration patterns. For example, Henderson, Nevada's water utility has more than 348,000 synchronized GIS/Maximo assets and uses the Geonexus Integration Platform for bidirectional synchronization.

The decision I'd make

One thing I would not do

I wouldn't solve this with a giant custom database synchronization project.

Esri's own water-utility guidance notes that older point-to-point/database integrations can create version-lock and upgrade problems. Modern integrations increasingly use vendor-supported web services/COTS connectors, with ETL reserved for information that doesn't need real-time exchange.

So I'd establish system-of-record rules first:

• GIS: asset ID, location, geometry, connectivity/topology, network attributes
• EAM: work orders, maintenance history, labor, materials, costs, PM schedules, failure history
• Integration: shared asset identifier + event/API synchronization
• Field: one workflow that lets the crew see the asset and its maintenance history without re-entering information

For a water distribution system, the payoff is particularly big because Utility Network can support network tracing/isolation workflows. Cityworks currently supports connecting to an Esri Utility Network layer for tracing.

Bottom line: If you tell me (1) what GIS you have, (2) what CMMS/EAM you have, (3) approximate number of water assets, and (4) whether you're primarily distribution, treatment, or both, I can narrow this down to a recommended architecture and integration approach—including whether Cityworks vs. Maximo makes more sense for your utility.

For a water utility, bridging the gap between GIS and a CMMS/EAM depends heavily on your existing software ecosystem and whether your organization is "GIS-centric" or "EAM-centric." Because water assets (valves, hydrants, pipes, pumps) are inherently spatial, a completely siloed approach cripples emergency isolation tracing, work order history, and regulatory reporting.

The industry standard solutions fall into three distinct architectural paths:

• The Native GIS-Centric Approach (Cityworks AMS + Esri ArcGIS): If your primary source of asset truth lives in Esri ArcGIS (especially if you are leveraging or migrating to the ArcGIS Utility Network ), pairing it natively with Cityworks AMS is often the gold standard. Because Cityworks is built directly on the Esri geodatabase, there is no messy data synchronization layer or translation required for basic asset and work activities. The map is the database.
• The Enterprise Middleware Approach (IBM Maximo / Hexagon EAM + Esri + Geonexus): If you are a larger utility running an enterprise powerhouse like IBM Maximo or Hexagon EAM for deep lifecycle costing, inventory, and linear asset management alongside an Esri GIS, a loose coupling via specialized integration middleware—such as the Geonexus Integration Platform or ActiveG MapEngine —is typically the best route. This approach uses automated data reconciliation and REST APIs to keep both systems as systems-of-record without forcing a risky, rigid custom point-to-point code that breaks during software updates.
• The Unified Single-Vendor Ecosystem (Infor Public Sector / Oracle WAM / SAP): If your utility is already heavily standardized on a broad ERP or enterprise cloud suite, leveraging that platform's native public sector/utility module with its packaged GIS connector eliminates third-party finger-pointing when bugs arise, though they rarely match the pure spatial agility of an Esri-first shop.

Best Practice Checklist for Water Implementation

Regardless of the software pairing you choose, a successful integration needs to follow a few strict rules:

1. Establish a clear System of Record: Designate GIS as the undisputed master for location, spatial relationship, and connectivity (e.g., pipe segments and valve tracing), while EAM/CMMS owns financial valuation, condition scores, and maintenance history.
2. Enforce bi-directional sync with error reporting: Avoid one-way data dumps that overwrite field updates. Implement tools that run regular comparisons and generate discrepancy logs so retiring a hydrant in the field doesn't get "lost" in a database queue.
3. Equip field crews with offline-capable spatial mobile tools: Water operators fixing a main break 10 feet underground often lose cellular connection; they need local device caching that syncs seamlessly the second connectivity returns.

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

• What GIS platform and CMMS/EAM are you currently running?
• Roughly how many active assets are in your inventory?
• Have you already adopted or planned a migration to the Esri Utility Network?