Data model

One structure. One canonical model. Four ERPs.

The landscape dashboard reads the SAP enterprise structure from S/4HANA and ECC R/3. The maintenance dashboards never read SAP AUFK, Oracle WIP_ENTITIES or Maximo WORKORDER directly. Adapters map each source into the same canonical entities, and the reporting layer reads those entities or the pre-aggregated KPI snapshots.

Canonical entities

11 core entities

Swipe to see all columns →

EntityPurposeKey fields
Functional locationWhere the work happenscode, parent, plant, cost centre, criticality
EquipmentThe assetasset tag, manufacturer, serial, linear/measure, replacement value
Maintenance planPreventive scheduleplan code, cycle, next due, task list
NotificationRequest or breakdownnumber, equipment, priority, malfunction start/end, state
Work orderExecution headernumber, order type, dates, actual cost, state
OperationIndividual stepoperation number, work centre, planned/actual hours
Material componentSpares reserved or consumedmaterial, quantity, unit cost
Time confirmationLabourtechnician, hours, work date, final flag
Asset meter / readingUsage and conditionmeter type, reading, unit, reading date
Failure reportReliability codesproblem, cause, remedy, failure mode, downtime
KPI snapshotPre-aggregated executive dataperiod, cost, RAV, MTBF, MTTR, PM compliance

SAP enterprise structure

Before a work order is counted, the landscape dashboard resolves the company code, plant and business area behind it. The same eight structure objects are read from S/4HANA and ECC R/3, with separate configurations for each system.

Open SAP landscape

Swipe to see all columns →

ObjectTableKeyPurpose
CompanyT880RCOMPConsolidation unit above the company codes
Company codeT001BUKRSLegal entity, currency, chart of accounts and fiscal year
PlantT001WWERKSOperating site, address, business area and maintenance ownership
Business areaTGSBGSBERCross-company management segment used in financial postings
Controlling areaTKA01KOKRSCost accounting scope and controlling currency
Sales organizationTVKOVKORGSales channel ownership and pricing responsibility
Purchasing organizationT024EEKORGProcurement ownership and purchasing conditions
Storage locationT001LLGORTMaterial storage within a plant

Reporting star

The analytical layer is a star schema. Facts carry the grain; dimensions carry the drill paths. Power BI or the Django workspace can read the same gold tables.

Facts

  • FactWorkOrder
  • FactNotification
  • FactPMCompliance
  • FactDowntime
  • FactCost
  • FactRCA

Dimensions

  • DimDate
  • DimPlant
  • DimFunctionalLocation
  • DimEquipment
  • DimWorkCentre
  • DimStatus
  • DimCatalog

Medallion flow

Raw ERP payloads are kept for replay. The silver layer conforms types, units and status maps. The gold layer is the signed-off KPI mart.

Bronze

Raw OData/REST payloads, append-only, source hash and cursor.

Silver

Canonical entities, deduplicated by external id, status mapped to core state.

Gold

Star schema, KPI snapshots, RLS-ready plant and org-unit columns.

Field ownership

Bidirectional integration only works when ownership is explicit. The connector never overwrites a field the CMMS owns.

ERP owns

  • Master data: functional locations, equipment, materials
  • Status, costs and confirmations
  • Maintenance plans and task lists

CMMS owns

  • Permit to work, isolation and LOTO
  • Checklists, RCA, CAPA and QA findings
  • Local notes, photos and shift handover