One partner across SuccessFactors, Ariba and the core SAP landscape

Context

Umm Al Houl Power Company — a joint venture between Qatar Electricity & Water Company, K1 Energy (Mitsubishi + JERA), QatarEnergy and Qatar Foundation — commissioned the integrated water and power plant at Umm Al Houl in 2018. The plant is explicitly aligned to Qatar National Vision 2030, aiming to meet roughly 30% of national electricity demand and 40% of water demand.

A plant that provides that much of a country’s utility capacity cannot afford diffuse accountability for the operational systems that run it.

Why single-partner AMS matters for a wide SAP landscape

A landscape that spans SuccessFactors, Ariba, EAM and the manufacturing and finance modules looks like one landscape from the business’s perspective and several from the technology vendors’ perspective. In a federated AMS model, the boundary between modules is where ownership gets diffuse — an issue in the Ariba-to-MM reconciliation looks like an Ariba problem to the MM team and an MM problem to the Ariba team, and the issue stays open because nobody disagrees enough to force resolution.

Consolidating the service under a single partner collapses that boundary. The same bench that answers the SuccessFactors ticket answers the integration ticket and the finance posting ticket downstream of it. Service governance has one calendar, one SLA report and one escalation path rather than one per module.

What we deliver

A single-partner AMS covering SuccessFactors, Ariba, EAM and the manufacturing and finance modules — governed as one service rather than a federation of module-specific contracts. The backlog of SuccessFactors and Ariba issues that had accumulated across previous engagements was closed inside the first delivery horizons.

SuccessFactors and Ariba

The HR and procurement modules get the heaviest cross-system load in a plant environment — SuccessFactors for the roster, shift and payroll backbone that makes a 24x7 facility compliant to run, and Ariba for the sourcing, contract and supplier-management cycle that keeps spares and services flowing against a long-tail supplier base. Historic issues in both were worked through on a prioritised backlog with delivery windows sized to the available change windows, rather than being carried from quarter to quarter as “known issues”.

EAM and the manufacturing modules

Enterprise Asset Management runs the work-order and equipment master layer for the generation and desalination assets. The manufacturing modules — SD, MM, PP, QM — carry the water-production cycle, which operates with a lot of the same process discipline as a continuous-process plant. Change work is staged against plant outage calendars; routine support handles the day-to-day without reaching into the plant control room except where it has to.

Finance, ABAP and Fiori

Finance posts settle alongside the operational transactions — work-order costs, inventory valuation, long-term service accruals. ABAP and Fiori capacity sits on the AMS team so that enhancements requested across modules can be delivered without a separate development vendor being brought in for each. The default posture is clean-core wherever possible so that the next upgrade does not have to unpick the current round of enhancements.

Why it works

Breadth helps. The APx bench carries certified capability across all the modules UHP uses, so cross-module issues can be investigated by one squad rather than three. Teaming with Falcon Vision on the ground gives us the local presence that an integrated water and power plant expects from a critical systems supplier.

The SPOC + SDM + CSM governance model ensures the three distinct jobs — daily operations, service accountability and roadmap — are separately owned, so none of them gets quietly demoted. The CSM in particular is the continuity mechanism across the longer horizon: the person who remembers why a particular configuration decision was made and who in the business needs to be looped in before it’s changed.

What transfers

The consolidation story — one partner across HCM, procurement, asset management, manufacturing and finance under one service and one governance model — transfers to any utility, infrastructure or asset-heavy operator running a wide SAP estate. It is the service shape that generalises, not the specific modules.