Four sources · one operating picture

Four plants.
Four ERPs.
One view.

One canonical maintenance model over SAP S/4HANA, SAP ECC, IBM Maximo and Oracle EAM. The same KPIs, the same drill-through, the same executive view — without replacing the system of record.

Synthetic data · no client data or logos · built for demonstration

Source systemsCanonical layerNov 2026
SAP S/4Yanbu Coal90.9%
SAP ECCAl-Kharj93.8%
MaximoDuba Wind95.6%
Oracle EAMJubail Gas95.8%
Canonical modelOne operating picture4 plants · 4 ERPs · one language
ERP stays the system of record.S/4 implemented · three planned

The four scenarios

Different systems. One operating language.

Start with the coal station

What is shared

The connector is the moat.

Every source system has its own tables, statuses and APIs. The wrapper maps them into one canonical model, then builds the same KPIs and drill-through on top. The ERP stays the system of record.

Canonical model

Functional locations, equipment, notifications, orders, confirmations, meters and failure codes.

ERP adapters

SAP S/4HANA OData is implemented; ECC RFC/BAPI, Oracle EAM REST and Maximo REST sit behind the same interface next.

Scope-based access

Group, region, plant and work-centre roles; financial fields masked where the role requires it.

Operational dashboards

Command centre, maintenance, reliability, permits, cost, quality and corporate views.

Canonical flow

Source → canonical → workspace

SAP S/4
SAP ECC
Maximo
Oracle EAM
OData · RFC/BAPI · REST · IDoc
Canonical maintenance model
Command centre
Maintenance
Reliability
Permits
Cost
RCA & quality