Utilities that use both GIS and SAP maintain records for the same physical assets in two systems. GIS holds the location and network context of each asset, while SAP supports the maintenance and work management processes around it. If the two records are not consistent, operational teams spend time reconciling them, and reports become harder to trust.
Integrating the two systems addresses only part of the challenge. Creating a single source of truth also requires clear data ownership, agreed rules for how changes move between systems, and a shared understanding of what consistent asset information means. Loudoun Water, a Virginia utility, offers a documented example of synchronized GIS and SAP in production, including what changed for its office and field teams.
One Asset, Two Systems
For a hydrant, the GIS record is a mapped feature connected to the network. In SAP, the same hydrant is managed through the utility’s enterprise asset management (EAM) processes, which SAP supports with equipment and functional location records, maintenance activities, and work orders.
When the two records do not match, the effect shows up in routine work such as service requests. A customer reports no water, a ticket is created, and a crew is dispatched to the asset location. If a location change has reached one system but not the other, the crew may be working from outdated information. In some utilities, changes like this still move between teams as a screenshot in an email, and someone on the other team re-enters the data by hand.
Why the records drift apart
GIS and SAP are usually maintained by different teams on different schedules. Every change to shared data has to reach the other system, and each manual re-entry is a chance for a typo, a missed field, or an update that never arrives. Over time, equipment, functional locations, and hierarchies stop matching, and finding the correct record means opening both systems side by side.
What a single source of truth should mean
A single source of truth is not one physical record or a third database, and it does not mean retiring GIS or SAP. It means “One asset, consistent information across systems.” Each system keeps the data it is best suited to hold, each shared field has an owner, and changes follow a defined path between the two. Clear data ownership and consistency are the foundation for reliable decisions.
Spatialitics Unity Engine, SAP certified since 2019, is built on this approach. CyberTech describes it as keeping SAP asset data and ArcGIS geospatial data continuously synchronized with zero data copy. SAP asset workflows stay in step with ArcGIS data as a result, including during S/4HANA and ArcGIS Utility Network programs.
In practical terms, zero data copy means avoiding a separate database that duplicates the asset records held in SAP and ArcGIS. Each system remains responsible for its own data, while the integration keeps the relevant information aligned according to the configured synchronization rules. This can reduce the need to maintain and reconcile a separate copy of shared asset information.
Four decisions to make before connecting anything
Before configuring anything, the SAP and GIS teams need to agree on four things.
First, decide which objects to synchronize. The objects Unity Engine synchronizes include equipment, functional locations, work orders, and notifications, along with asset hierarchies and geometry. Not every object or attribute needs to move. The records your teams already reconcile by hand are a sensible place to start.
Second, agree on ownership and direction. Typically, SAP owns business attributes such as equipment status, criticality, or maintenance plant, and ArcGIS owns location and geometry. In Unity Engine, records can be created, updated, or deleted in either direction, and direction is set by object and by attribute, so it can differ from one field to the next. Deletions need their own rule, because some utilities retire assets instead of deleting them. These ownership rules determine which system’s value takes precedence when changes conflict.
Third, set the timing for each object. Continuous synchronization is the overall result. How current each object is at any moment depends on the timing the utility sets for it. Real-time synchronization suits data that cannot wait, such as a new asset a field crew needs today. Scheduled runs suit high-volume updates, and on-demand runs handle one-off refreshes when a team needs current data right away. Set the frequency according to how the data is used and how quickly changes need to reach the other system. The first run is a full synchronization that sets the baseline, and after that only changes move.
Fourth, agree on how exceptions are handled. Conflicts follow the ownership rules from the second decision. If both systems change the same attribute before a sync runs, the owning system’s value is kept, the other system is updated to match, and the overridden change is recorded in the sync log. Every sync transaction is logged and audited. When an update cannot be applied, for example because a record fails SAP validation, Unity Engine flags it in its web-based monitoring console, and integration administrators receive a real-time alert showing which record failed and why. Teams should decide in advance who receives those alerts and who resolves them.
What this looks like in production
Loudoun Water uses Unity Engine to synchronize SAP and ArcGIS while keeping its business data in its own systems. The Virginia utility provides drinking water, wastewater, and reclaimed water services to more than 80,000 homes and businesses in Loudoun County, and Esri GIS has been its system of record for linear assets for decades. Esri’s industry blog documents the implementation.
Loudoun Water’s 2014 SAP implementation covered most of its business operations, including asset and maintenance management, and a custom toolset within SAP kept the two systems synchronized. The initial integration was successful, and users requested more synchronized objects and attributes and an improved map. Supporting that growth called for a setup that would be easier to extend and maintain, handle large datasets, and carry the utility through its planned S/4HANA move.
The new setup also had to fit the utility’s cloud-first policy, with SAP and Esri already hosted in Microsoft Azure. Loudoun Water selected a commercial solution from Spatialitics, a wholly owned subsidiary of CyberTech. Secure connections link its SAP and Esri environments to the Spatialitics cloud, which hosts only the configuration, and the utility’s technologists manage the synchronization. At the time of Esri’s November 2022 industry blog, Loudoun Water was preparing for its move to SAP S/4HANA. It was expected that the GIS integration would not complicate it, since Spatialitics Unity Engine is SAP certified.
In the published case study, Mike Beardslee, Managing Director of Technology Services at Loudoun Water, said the Spatialitics solution “meets our business needs, satisfies our strict cybersecurity requirements, is easy for us to operate, and is S/4HANA ready.”
What connected asset information changes for office and field teams
Work orders show the effect most directly. Loudoun Water’s office and field users work with them in Spatialitics Asset Mapper, the utility’s map application, which draws on the synchronized SAP and GIS data. The meter team handles its work orders there on mobile devices, planners create work orders from the map one at a time or in batches, and customer service staff can check open work orders near a caller’s location. On the technology side, Spatialitics runs the hosted solution, including routine maintenance, which leaves the utility’s technologists free to extend what is synchronized as the business requires.
What to bring to an integration roadmap review
For an integration roadmap review, bring the following:
- Current SAP and ArcGIS versions
- The shared objects, meaning the records that exist in both systems
- Data owners and system owners for those objects
- Known data-quality issues
- One pilot workflow, with its acceptance criteria
- The S/4HANA roadmap, including timing
