Talking about shared truth is one thing. Implementing it is where most organizations get stuck.
‍

Traditional Maximo–GIS integrations require custom development, long lead times, and specialist technical staff. PowerSync was designed to remove that friction entirely, allowing configuration of bidirectional integration without writing code.
‍

The following steps illustrate how quickly a typical integration can be configured.

Step 1: Connect to the GIS service

The first step is simply defining the GIS service to integrate with.
‍

This involves providing:

• A service name

• The GIS service URL

• Authentication URL

• Username and password
  ‍

Once configured, PowerSync can securely communicate with the GIS service.  

‍

Step 2: Define How Data Should Flow, Profile by Profile

Rather than treating integration as a single, monolithic process, PowerSync works through profile definitions. Each profile represents a GIS feature class and how it should interact with Maximo.
‍

This approach gives fine-grained control and reflects how asset data actually varies across classes.

Define the Profile

Each profile is given:

• A name (for example, Transformers)

• The GIS layer to interact with

• Any layer dependencies

• An optional GIS where-clause to limit which features are included
  ‍

This allows organizations to scope integration precisely, rather than synchronizing entire layers unnecessarily. In the screenshot above, the full configuration workflow is visible in the panel on the left. For the remaining screenshots, this list has been intentionally redacted to keep the focus on each step as it is completed.

‍

Choose the Synchronization Type

For each profile, the synchronization behavior is defined. Options include:

• Full synchronization

• Updates only

• Link only

• Link and insert
  ‍

This flexibility is critical; not every asset class needs the same behavior.

‍

Specify Whether the Profile Represents an Asset or a Location

‍

‍

PowerSync supports both assets and locations. This distinction ensures that data flows into the correct Maximo objects and behaves as expected downstream.

Map Asset Classifications

The relevant Maximo asset classification is selected directly.
‍

Where needed, classification hierarchies can also be constructed dynamically in Maximo based on GIS attributes, using custom delimiters. This removes the need for manual pre-configuration and keeps classifications aligned with spatial data.

‍

Match Key Fields

At this stage, the identifiers used by Maximo and GIS are mapped to each other. This ensures records remain linked correctly across systems and enables reliable bidirectional updates.

‍

Define the Description Logic

Record descriptions in Maximo can be generated using:

• Static text

• A single GIS field

• A combination of multiple GIS fields and custom text
  ‍

This allows descriptions to be meaningful and consistent without manual intervention.

‍

Configure Linear Assets (if applicable)

For linear assets, the relevant start and end measure fields are specified. This ensures linear referencing is handled correctly and remains consistent between systems.

‍

Set the Parent Location

Parent locations can be defined using:

• A fixed value

• A GIS field

• A field from a different GIS layer

• A combination of GIS fields and text
  ‍

This flexibility allows location hierarchies to be constructed accurately from spatial data.

‍

Set the Parent Asset

Parent assets are configured in exactly the same way, supporting complex asset hierarchies without custom logic.

Map GIS Attributes to Maximo Specifications

For each Maximo specification:

• A GIS attribute can be selected

• The sync direction can be defined (GIS → Maximo, Maximo → GIS, or bidirectional)

• Values can be composed from multiple GIS fields or static text
  ‍

This is where shared truth becomes explicit and governed at the field level.

‍

Map GIS Attributes to Maximo Fields

Field mapping follows the same pattern as specifications, but applies directly to Maximo fields. This consistency makes the configuration intuitive and transparent.

Test and Activate

Finally, a test run is executed.
‍

Within minutes, a fully operational bidirectional integration is live, observable in real time, configurable without code, and easy to adapt as requirements evolve.

‍

Why This Matters

What this process demonstrates is not just ease of setup, but a shift in how integration is approached.

• No long implementation cycles

• No dependency on specialist developers

• No opaque data pipelines

• No guessing where errors occurred
  ‍

Instead, organizations gain a flexible, observable, and governed way to ensure Maximo and GIS truly share the same truth.
‍

With that foundation in place, the next challenge becomes clear: how to make that aligned data visible and usable in day-to-day operations.

‍

Next in the series --> Operational Context Lives on the Map: exploring how shared asset and spatial data can be brought together into a single operational view.