The biggest SAP estate in the region
Saudi Aramco's SAP deployment is one of the largest enterprise SAP estates in the world. The company implemented SAP R/3 in three stages between 1997 and 2003, covering finance and accounting, materials supply, plant maintenance, contracting and procurement, warehousing, projects and capital planning, and knowledge management. The deployment has continued to expand since. Saudi Aramco has more recently rolled out SAP Fiori for Plant Maintenance, the modernised user-experience layer that the global SAP customer base is migrating to. The work is real and the scale is consequential.
ADNOC operates a comparable SAP footprint. Kuwait Oil Company, Qatar Energy, the Bahrain operations of Bapco, the Oman Oil and Gas customers — each major Middle East enterprise runs a meaningful SAP estate with the Plant Maintenance and Enterprise Asset Management modules at the heart of the operational technology stack. The integrators that operate these deployments are well-established. The institutional knowledge runs deep.
The conversation worth having is not whether SAP PM and EAM are competent products. They are. The conversation is what staying on the platform for the next contract cycle actually costs against the operational reality of an asset-intensive upstream business, and where the conversation about ownership starts to be a sensible one. The number is not the headline licence. The number is everything around the licence at the scale these enterprises run at.
What the EAM bill actually contains at upstream scale
The licence cost at a major Middle East enterprise is the smallest visible line on the EAM bill. Four cost layers compound on top of the licence.
The system integrator engagement. The Plant Maintenance configuration that runs the enterprise's maintenance strategy is configured against the institutional history of two decades of refinement. The integrator's bench operates the configuration. Major changes — a new field coming online, a new asset class entering the maintenance plan, an integration with a new IIoT layer — are billable engagements at scale. The total integrator cost across the upstream operations typically exceeds the SAP licence by a multiple.
The work-order economics. The enterprise's maintenance organisation runs work orders at a volume that the EAM module was designed to handle, but the unit economics of the workflow inside the module have not improved at the rate the broader software industry has. The work-order lifecycle, the parts-and-labour planning, the safety-and-permit-to-work integration, the shutdown-and-turnaround coordination — each runs against the EAM configuration. The technician hours that the workflow consumes are the dominant cost.
The integration tax against the operational technology layer. The OT layer — the DCS, the SCADA, the historians, the IIoT platforms, the digital-twin programmes that the enterprises have invested in over the last decade — connects to SAP through integration boundaries the integrator has built. Each integration is a separate configuration with its own change-control overhead. The total cost across the OT integration footprint is materially larger than the SAP licence and grows with every OT initiative the enterprise launches.
The certification and audit cadence. Upstream operations carry regulatory expectations from the supervisory authorities. The release certification cycle on SAP changes against the operational asset registry runs at a cadence the integrator's pricing model anticipates. Each release affects the audit trail the enterprise presents to the supervisor. The certification work is billable.
Sum these four against the licence. The total EAM operating cost at a major Middle East enterprise is a multiple of the headline number. The multiple has grown faster than the enterprise's other technology line items.
What "the cost of staying" actually means
Staying on the platform is not a zero-cost decision. Three structural trends are pushing the EAM cost trajectory in one direction.
The integrator labour rate is rising. The talent pool that operates a tier-one SAP PM configuration at scale is finite. The labour rate has grown faster than the enterprise's own salary bands. The retainer cost is structurally on an upward trajectory.
The vendor's AI extension catalogue is the next upsell. SAP has positioned the AI surface on PM as the next-cycle revenue motion. The Joule-branded surfaces for maintenance work-order assistance, the agentic surfaces for shutdown coordination, the predictive surfaces for asset reliability — each is being pitched at the Middle East upstream enterprises as the AI-native modernisation path. Each is priced inside the SAP commercial envelope.
The operational technology landscape is evolving faster than the EAM release cycle. The IIoT and digital-twin investments the enterprises have made over the last decade are generating signals that the EAM module ingests imperfectly. The gap between what the OT layer can produce and what the EAM can consume is widening, not narrowing.
What an alternative architecture looks like
We do not propose retiring SAP at a major Middle East upstream enterprise. The clinical-equivalent argument applies with particular force in upstream. The safety architecture, the supervisory audit posture, the institutional knowledge embedded in the configuration, and the operational dependency on the workflow are real. The conversation worth having is which workflows the enterprise should own outright on its own infrastructure, with the SAP estate continuing to handle the workflows where the existing dependency is genuinely load-bearing.
The pattern is workflow-led. Pick the workflow where the per-asset cost is most painful, build the owned alternative against the real estate, run the parallel-validation period the safety architecture requires, retire the SAP-vended surface for that workflow on a fixed date. The licence at the next renewal reflects the smaller surface area.
Workflows that move first in upstream tend to be the data and analytics layers that sit on top of the work order, not the work-order surface itself. The maintenance-intelligence layer that synthesises the work-order history against the OT signal. The reliability-engineering analysis surface. The turnaround planning workspace that the planning team uses outside the EAM. The contractor-management surface that the procurement team coordinates with the operations team through.
The work-order surface itself stays on SAP. The safety architecture stays on SAP. The supervisor's audit trail stays on SAP. The workflows around the core move to owned software at the enterprise's pace.
The Middle East dimension
Three dimensions are specific to a Middle East upstream context.
The asset base is multi-generational and operationally complex. Middle East fields range from mature producers under enhanced-recovery operations to recent developments with the latest IIoT instrumentation. The EAM configuration carries this complexity. The owned-workflow stack handles the complexity through architecture the enterprise's team designs against the operating reality, not against the vendor's standard template.
The supervisor's posture on operational technology is rigorous. The Saudi authorities, the UAE federal and emirate-level regulators, the Kuwait and Qatar supervisory frameworks — each has detailed expectations on how operational technology change is authorised at supervised institutions. The owned-workflow architecture lets the enterprise author the audit trail against the supervisor's specific expectations rather than against the vendor's documentation.
The institutional capability is mature. The enterprises have invested deeply in their own platform engineering and operational technology functions. The talent to operate the owned-workflow stack is in the building, not at the integrator.
The saasinator perspective
The case for owning maintenance workflows in upstream is not a case against SAP. SAP PM and EAM are competent products and the deployments have served the enterprises well for two decades. The argument is for matching the cost structure to the value the workflow generates. The work-order surface and the safety architecture are commodity — running them on SAP is rational. The maintenance intelligence, the reliability analysis, and the turnaround planning are differentiating — running them on rented software at compounding cost is not.
The enterprise that runs the first owned workflow successfully has changed the institutional default. The next workflow is a smaller decision than the first. The next contract cycle with SAP is a different conversation.
What to bring to the diagnostic
The diagnostic for an upstream engagement is 15 working days. Bring the EAM module breakdown, the integrator retainer schedule, the OT integration inventory, and the safety-and-supervisory posture the operations team operates against. The output is the workflow recommendation, the architecture sketch, and the first-quarter scope. Book a diagnostic at /diagnostic.