Services · Enterprise integration
The ecosystem is the hard part.
SAP is rarely alone. Esri holds the network, Primavera holds the plan, the mobile tool holds what actually happened. Integration is where a utility program is won or quietly lost.
The symptom
Everyone is right, and the numbers still differ
Copied, not reconciled
A nightly export creates a second version of the truth and no way to tell which one is current.
Keyed twice
The same asset entered by hand in two systems, diverging from the first week onward.
Reported separately
Three teams, three extracts, three answers, and a meeting to decide which one to present.
What we integrate
Four seams, done properly
SAP and Esri
SAP Technical Objects and ArcGIS Utility Network Features reconciled on identity, not copied on a schedule. This is what Theta does.
SAP and Primavera P6
Bi-directional, event-driven synchronization of activities, dates and progress. This is what Gamma does.
SAP and mobile execution
Field capture that writes back into the order structure rather than into a parallel app database.
SAP and the analytics estate
Governed replication with lineage, so a number in the dashboard can name the record behind it.
How we do it
Reconciled, not copied.
Establish identity
Before anything moves, agree what makes two records the same asset.
Choose the direction
Per field, per object. “Both ways” without a rule is how divergence starts.
Make it event-driven
Changes propagate when they happen, not when a job runs at 2am.
Instrument the seam
A reconciliation report that a person can read, and that fails loudly.
Next step
Start with the hardest part
A short conversation about where your SAP, GIS and schedule data stop agreeing — and what it would take to bring them into line.