This guide is for SAP owners and IT operations leads at Gulf oil, gas and petrochemical operators. It is also for the JV partners who share those systems. It shows how an SAP AMS operating model for oil and gas must differ from a generic application support contract.
First, it covers how you class and prioritise tickets when a work-order blocker sits next to a routine password reset. Then it covers how the change calendar bends around turnarounds and shutdowns. It also covers how you design coverage across remote sites and 24×7 operations against Gulf working weeks. Next, it explains how hypercare hands over to BAU while an S/4HANA programme is still running, and what the Solution Manager end date means for your ALM tooling. It closes with what to put in your AMS RFP and an FAQ. Where a point is our design guidance rather than a sourced fact, we say so.
To establish the industry context first, start with our oil and gas SAP practice page. It covers the solution footprint rather than the operating model. This post assumes you have already made that decision, so it deals with how support runs afterwards.
1. SLA by ticket class: why one severity scale fails in this vertical
A single P1 to P4 ladder, applied uniformly, produces two predictable failures in oil and gas landscapes. First, it over-prioritises a finance report that one user cannot run. Second, it under-prioritises a Plant Maintenance order release that is holding up a permit-to-work on a live asset. The fix is to classify tickets by business object first, then apply severity within the class.
The tables below hold Altivate-authored design guidance. They give a starting structure for a statement of work. So calibrate them against your own site criticality register and your own asset hierarchy. These are illustrative planning ranges, not a service commitment and not benchmark data.
Work-order blockers and spares ticket classes
| Ticket class | What it looks like | Priority | Illustrative first-response range | Illustrative restore or workaround range | Owner |
|---|---|---|---|---|---|
| PM/EAM work-order blocker | Maintenance order cannot be created, released, confirmed or technically completed; notification cannot be converted to an order; order status stuck so the work centre cannot proceed. SAP’s Plant Maintenance data model description centres on maintenance orders and maintenance notifications with their related causes, activities and tasks. Because field work is executed against those objects, an order-level fault stops execution rather than only reporting. | Critical when a safety, flaring or production-critical asset is affected; high otherwise | 15 to 30 minutes, 24×7 for critical assets | 2 to 4 hours to workaround; permanent fix per change process | AMS functional L2/L3 with site maintenance super-user |
| MM and inventory for spares | Reservation or goods issue failing against a maintenance order; spares unavailable because stock, batch or storage-bin data disagree; purchase requisition not converting for a critical spare; cycle-count discrepancies on rotable items | High when it blocks a released work order; medium otherwise | 30 minutes to 1 hour in business hours | 4 to 8 hours to workaround, often by manual issue and later reconciliation | AMS logistics L2 with warehouse and procurement leads |
Joint venture close and integration ticket classes
| Ticket class | What it looks like | Priority | Illustrative first-response range | Illustrative restore or workaround range | Owner |
|---|---|---|---|---|---|
| JV and FI close | Cutback or cutback reversal not posting as expected; equity adjustment or suspense and unsuspense items out of balance; cash call update or netting step failing; partner billing not producing the expected statement. SAP’s joint venture accounting model has the operator keep the books and distribute to partners by ownership share, and the month-end cycle runs through these named steps. | Critical during the close window; high in the days before it | 1 hour during close, 4 hours outside it | Same business day during close; next business day otherwise | AMS FI/CO and JV functional L3 with the finance close lead |
| Integrations: SCADA/historian and PI hand-offs | Measurement, meter or loading data not arriving in SAP; a queue backing up; duplicate or stale records after a reconnect; a downstream system rejecting a payload. In downstream, the Terminal Automation System interface in SAP Oil & Gas (downstream) exchanges loading information such as pick-ups, shipments, goods movements and physical inventory counts with an external system over IDocs and ALE or RFC, so failures tend to surface in interface monitoring as stuck or rejected messages, not as a screen error. | Critical where custody transfer or loading is halted; high otherwise | 30 minutes to 1 hour | 2 to 6 hours to restore flow or run a controlled manual fallback | AMS integration L2/L3 with operations technology and the third-party system owner |
Access and GRC tickets, and how to read the ranges
| Ticket class | What it looks like | Priority | Illustrative first-response range | Illustrative restore or workaround range | Owner |
|---|---|---|---|---|---|
| Access and GRC | Locked or expired user blocking a shift handover; missing authorisation on a maintenance or goods-movement transaction; segregation-of-duties conflict flagged after a role change; emergency access required during a shutdown window | High when a shift cannot start or a critical transaction is blocked; medium otherwise | 15 to 30 minutes for shift-critical; 2 to 4 hours for standard requests | 1 to 2 hours for standard role assignment; emergency access per your control procedure | AMS security L2 with the GRC and internal controls owner |
Three design notes help you read those tables.
- The ranges are wide on purpose. They describe planning bands for a contract conversation, not a published service level. You should set your numbers from your own criticality register, your shift pattern and the number of sites in scope.
- Owner does not mean sole resolver. The named owner is accountable for the ticket’s progress, including the hand-off to the third-party system owner on integration tickets. That hand-off is where you lose most elapsed time.
- Access and GRC sits inside the AMS, not beside it. In a shift-based operation, a locked user is a production event. Treating access requests as an HR-adjacent service with a two-day turnaround is a common and avoidable design fault.
Run support for these classes is the core of our SAP application managed services model. The model aligns with ITIL across L1 to L3, with SLAs by priority and monthly service reviews. Before you sign, confirm with your provider what it actually delivers against each class.
2. A change calendar built around turnarounds and shutdowns
As we use the term here, a turnaround means a planned stoppage of a unit or plant. Maintenance, inspection and modification work happens in a compressed window. The SAP changes needed to support that work have to be in place before the window starts and stay frozen while it runs. Shutdowns follow the same logic at smaller scale.
This is a planning concept we apply to SAP change control, not an SAP product feature. We make no claim that SAP provides a built-in turnaround or shutdown management capability.
The practical consequence is that your change advisory board cannot run on a fixed weekly rhythm. Instead, it has to run against a calendar that follows the turnaround schedule. That calendar needs explicit freeze rules that everyone, including the programme team, knows in advance.
Freeze phases from turnaround preparation to thaw
| Phase | Window | Change policy |
|---|---|---|
| Steady state | Outside any turnaround planning or execution window | Normal CAB. Standard changes pre-approved; normal changes on a weekly cycle; emergency path available with post-implementation review |
| Turnaround preparation | Illustratively 8 to 12 weeks before the freeze; set it from your own turnaround schedule | Elevated scrutiny. Changes to PM order types, work centres, spare parts master, bill of materials and printing or labelling are allowed but must be listed on a turnaround readiness register with a named owner and a rollback note |
| Hard freeze | From the start of the shutdown or turnaround until the unit is back in normal operation | No changes to PM, MM, JV or interface configuration. Emergency changes only, approved by a named business and IT authority, recorded and reviewed within two working days of the freeze lifting. Access changes needed to staff the window are processed as a pre-agreed exception class |
| Soft freeze / stabilisation | Illustratively 1 to 2 weeks after restart | Defect fixes and the reviewed emergency changes only. No enhancements. Plan for post-turnaround data clean-up and backlog confirmation in this window |
| Thaw and backfill | After stabilisation, before the next preparation window | Deferred changes re-enter the normal cycle. Turnaround lessons learned feed the next preparation register |
Two conditions that make the freeze calendar work
Two points decide whether this calendar works in practice. First, the freeze has to bind the S/4HANA programme as well as run support. Otherwise, transport collisions and conflicting test cycles will do the damage that the freeze exists to prevent.
Second, the calendar must work as a shared artefact with the maintenance and operations planners. It cannot be an IT document that circulates after the dates are final. If your AMS provider is not in the turnaround planning meeting, they will receive a freeze rather than help to shape one.
3. Coverage model: four design options, chosen by the buyer
Coverage is where oil and gas requirements diverge most sharply from a generic AMS contract. This happens because the operations pattern and the support pattern are not the same shape. Remote and unmanned sites, night shifts and a 24×7 control room all exist alongside a corporate working week. That working week is not uniform across the region.
The four options below are designs to choose between. They do not describe the footprint that Altivate delivers. Confirm with your provider what it actually delivers before you treat any of them as available.
Four coverage options compared
| Option | When it fits | Trade-off |
|---|---|---|
| On-site presence | Multiple plants with heavy EAM usage and super-users who need a physical counterpart for shift handovers, go-live support and turnaround windows | Best for tacit knowledge and relationship depth. Higher cost per seat, harder to staff for 24×7, and the single-site expert becomes a bus-factor risk |
| Remote, business-hours aligned | A single-country operation with a stable business hours pattern and a well-documented estate | Lowest cost and easiest to govern. Leaves night-shift and weekend events to an on-call rota, which must be explicitly contracted rather than assumed |
| Offshore, extended hours | Requirement to cover a longer daily window and to absorb volume peaks such as close and turnaround preparation without adding on-site headcount | Wider daily coverage at moderate cost. Requires strong knowledge transfer, written procedures and explicit escalation rules, or the first real incident exposes the gaps |
| Follow-the-sun | Assets or JV partners spread across time zones, with a genuine need for live L2 capability around the clock | Broadest live coverage. Highest coordination overhead, real hand-off losses, and it only works if the knowledge base and ticket notes are good enough for a different team to act on |
Working weeks across the UAE and Saudi Arabia
Whichever option you choose, resolve the working-week question explicitly in the contract. The region is not uniform, and the Gulf working week is not one thing.
- The UAE federal government adopted a four and a half day working week with Saturday and Sunday as the official weekend. This took effect on 1 January 2022. That describes the federal government sector only. Private-sector and emirate-level patterns differ, and the same source notes that Sharjah differs. Your operator’s own calendar may differ too, so use this as evidence that regional patterns vary, not as your calendar.
- Under Saudi labor law, Friday is a weekly rest day. An employer may substitute another day for some workers after notifying the relevant labour office. Do not assume your Saudi support desk and your Saudi operations team share the same rest-day pattern. Likewise, do not import an English translation of the law as your HR policy. Confirm the applicable pattern with the operator’s HR and legal teams.
For an SLA, this means that elapsed-time clocks need a defined calendar per site and per service. Agree that calendar in writing. A four-hour restore target that runs through a rest day is a different commitment from one that pauses. Both are defensible, but leaving it ambiguous is not.
4. Running the S/4HANA programme in parallel with run support
Many operators are not choosing between a programme and steady state. They run both, on the same landscape, with the same scarce functional experts. The operating model has to say who owns what. Otherwise, hypercare quietly becomes permanent and BAU becomes a queue that nobody owns.
The definitions come first. SAP describes hypercare as the period after go-live that occurs before operational responsibility fully transfers to the production support team. SAP calls the phase after it the Run phase, in which further stabilisation and optimisation of operations take place. The split below is our recommendation for how to apply those definitions in a multi-site oil and gas landscape. It is design guidance, not SAP doctrine.
Who owns each activity during hypercare and after transition to Run
| Activity | During hypercare | After transition to Run |
|---|---|---|
| Incident triage and resolution | Programme team owns, with AMS embedded in the same queue so knowledge moves with the tickets | AMS owns; programme resources exit unless a defect is confirmed as programme-introduced |
| Defect versus enhancement decision | Programme owns, with a written definition of what counts as a defect against the signed scope | AMS owns the assessment; enhancements route to a separate change budget and board |
| Configuration and transport control | Programme owns the transport landscape and the change calendar, including any turnaround freeze | AMS owns within the agreed change calendar; programme changes need a slot like anyone else |
| Data quality and master data | Joint, with the programme accountable for migration-related data and the business for ongoing maintenance | Business owns the data; AMS owns the controls, monitoring and error handling around it |
| JV close and period-end support | Programme supports, with AMS observing the first close cycles to learn the operator’s specific sequence | AMS owns; the close calendar is a fixed commitment in the service scope |
| Knowledge transfer | Programme to AMS, using knowledge transfer, shadowing and reverse shadowing so AMS demonstrates the fix rather than watching it | AMS maintains the knowledge base as a service deliverable, not as an afterthought |
| Exit criteria | Agreed in advance: open defect thresholds, ticket volume trend, and a defined number of clean close cycles and maintenance cycles | Hypercare formally closed with a signed handover; the programme team’s residual obligations are listed by name |
Putting the ALM migration on the programme plan
SAP recommends completing the move to SAP Cloud ALM before mainstream maintenance for Solution Manager ends. The same source restates that end date as 31 December 2027. Your programme and your ALM migration may both be running. If so, put them on one plan with one owner for the transport and tooling cutover. Otherwise, the change calendar in section 2 becomes unenforceable. For the programme side, see our success story on an SAP S/4HANA 2022 migration for a leading oil and gas company in Saudi Arabia.
5. The ALM and tooling hook: Solution Manager’s end date is in your AMS contract
Mainstream maintenance for SAP Solution Manager ends on 31 December 2027. That date has a direct consequence for AMS. List which Solution Manager functions your AMS team relies on today, because each of them needs a successor before that date. An operating model that assumes Solution Manager is available at the far end of a three-year contract is not an operating model. It is an assumption.
The two practical questions for your RFP are these. Who owns the ALM transition? Does the effort sit inside or outside the AMS scope? Ask both explicitly. Suppose the provider says it will run Solution Manager until it stops and deal with the transition later. In that case, you have found a gap in the proposal.
For the fuller picture, see our companion post on moving from SAP Solution Manager to Cloud ALM before 2027. It includes the tooling comparison and the sequencing.
Business Suite 7 dates for hybrid estates
One related date matters if you still run Business Suite 7 components alongside S/4HANA. SAP provides mainstream maintenance until end of 2027 for SAP Business Suite 7 core applications. Optional extended maintenance is also available for three years from the beginning of 2028 until the end of 2030, at a premium of two percentage points on the maintenance basis. SAP restated in October 2026 that mainstream maintenance remains available through 31 December 2027. So if a hybrid estate is in scope, put the Business Suite 7 dates in the contract alongside the Solution Manager date.
6. What to put in your SAP AMS RFP for oil and gas
AMS RFP checklist for an oil and gas SAP landscape
- Ticket taxonomy, not just severities. Require the bidder to respond to your ticket classes, including PM/EAM work-order blockers, MM spares, JV and FI close, integrations and access/GRC, with first-response and restore ranges stated separately.
- Service calendar per site. Ask for the working calendar each service level will run on, and how rest days and public holidays pause or do not pause the clock.
- Turnaround and shutdown alignment. Ask for the bidder’s method for building a freeze calendar with your planners, and for evidence of how the tracking of deferred changes continues through to thaw.
- Coverage model, stated plainly. Require the bidder to state exactly which coverage models it delivers, in which locations, with which hours, and which of them go to subcontractors.
- Hypercare exit criteria. Ask for the definition of defect versus enhancement and the exit thresholds, in writing, before the programme starts.
Transition, knowledge transfer, interface, JV close and spares items
- ALM transition ownership. Require a named owner and an in-scope or out-of-scope position for the move off Solution Manager before 31 December 2027.
- Named knowledge transfer mechanics. Shadowing, reverse shadowing and the knowledge base as a service deliverable, with the artefacts listed.
- JV close specifics. Require the bidder to describe its experience with cutback, equity adjustment, suspense processing, cash call update, netting and partner billing, and to name the roles that will support your close calendar.
- Interface ownership boundaries. For loading and measurement interfaces, state who owns the SAP side, who owns the external system, and what mechanism drives a cross-boundary ticket to closure.
- Spares and warehouse angle. If inventory performance is in scope, include it: our post on warehouse optimization with SAP EWM covers the warehouse side of spares availability.
Our SAP AMS buyer’s guide is the companion paper for this checklist.
The operating model is the differentiator, not the rate card
Rates and a severity ladder are easy to compare across proposals. What is harder to compare is whether the operating model’s design starts from a plant that cannot stop, a close cycle that cannot slip, a turnaround window that cannot move and a JV structure that multiplies the reporting load.
Agree the ticket taxonomy, the freeze calendar, the coverage calendar and the hypercare exit criteria before commercial negotiation. After you sign the contract, none of them is cheap to retrofit.
And treat the Solution Manager date as a design constraint from day one. A three-year AMS contract signed in 2026 will outlive it.
Get an SAP AMS scoping call for oil and gas
Altivate is an SAP Gold Partner. Bring your ticket classes, your turnaround calendar and your S/4HANA timeline, and we will work through the operating model with you before you go to RFP.
Frequently asked questions
What makes an SAP AMS operating model for oil and gas different from a standard AMS contract?
Four things. Tickets are classified by business object, with Plant Maintenance work-order blockers treated as production events rather than as application issues. The change calendar is driven by turnaround and shutdown windows with explicit freeze rules. Coverage is designed around 24×7 operations and remote sites against working weeks that vary across the Gulf. And JV accounting close cycles become fixed commitments in the service scope rather than a finance side activity.
Should SLAs be based on response time or restoration time?
Both, stated separately, because they answer different questions. First response tells you how quickly someone competent engages. Restore or workaround tells you when the business can proceed. In oil and gas the second matters more, but the first is what exposes a provider that has sold a queue rather than a capability. Any published ranges should be labelled as illustrative planning bands unless the provider is contractually committing to them.
How do you handle change freezes during a turnaround?
By agreeing the calendar before the turnaround schedule is fixed. In our design guidance, a preparation phase with a readiness register precedes a hard freeze during execution, in which only emergency changes approved by a named business and IT authority are allowed. A short stabilisation period follows restart. The freeze must bind the S/4HANA programme as well as run support, and it must be built with the maintenance planners rather than imposed on them.
Who owns hypercare, and when does it end?
SAP defines hypercare as the period after go-live that occurs before operational responsibility is fully transferred to the production support team, followed by the Run phase in which operations are stabilised and optimised. In practice the programme team owns triage and configuration during hypercare, with AMS embedded in the same queue, and ownership transfers at agreed exit criteria: open defect thresholds, ticket volume trend, and a defined number of clean close and maintenance cycles. Get those criteria written before the programme starts.
How does the end of Solution Manager maintenance affect an AMS contract?
Mainstream maintenance for SAP Solution Manager ends on 31 December 2027, and SAP recommends completing the move to SAP Cloud ALM before that date. Because an AMS team’s monitoring and change-control routines may depend on that tooling, your RFP should require a named owner and an in-scope or out-of-scope position for the transition. A multi-year AMS contract signed now will outlive Solution Manager.
Can an AMS provider cover 24×7 operations across Gulf working weeks?
That is a design choice, not a given. On-site, remote business-hours, offshore extended-hours and follow-the-sun models each trade cost against coverage and knowledge depth, and each has a different failure mode. The working week itself is not uniform: the UAE federal government moved to a four and a half day week with a Saturday and Sunday weekend from 1 January 2022, while under Saudi labor law Friday is a weekly rest day that employers may substitute for some workers. Agree the service calendar per site in writing, and confirm with your provider what it actually delivers rather than what the proposal implies.
Sources
SAP Support Portal, transition to SAP Cloud ALM (mainstream maintenance for SAP Solution Manager ends 31 December 2027) and SAP Business Suite 7 maintenance strategy page (mainstream maintenance until end of 2027 for core applications; optional extended maintenance 2028 to 2030 at a premium of two percentage points), accessed 4 November 2026; SAP News Center, 18 June 2026 on the Cloud ALM transition and 7 October 2026 on Business Suite 7 maintenance beyond 2030, accessed 4 November 2026.
SAP Help Portal, joint venture accounting (operator remits venture expenses, collects revenues and distributes to partners by ownership share; month-end processes including cutback, equity adjustment, suspense and unsuspense, cash call update, netting and partner billing), SAP Oil & Gas downstream Terminal Automation System interface (loading information exchanged with an external system via IDocs and ALE or RFC, covering pick-ups, shipments, goods movements and physical inventory counts), and the Plant Maintenance analytics data model (maintenance orders and maintenance notifications with related causes, activities and tasks), accessed 4 November 2026; SAP Activate roadmap for SAP S/4HANA (hypercare occurs before operational responsibility is fully transferred to the production support team; operations further stabilised and optimised in the Run phase), accessed 4 November 2026.
UAE government portal on federal government working hours (four and a half day week, Saturday and Sunday weekend, effective 1 January 2022), accessed 4 November 2026; Saudi Ministry of Human Resources and Social Development, English excerpt of the Labor Law (Friday as a weekly rest day, substitution for some workers after notifying the labour office), accessed 4 November 2026.
Notes
Operating model content in sections 1 to 4 and the RFP checklist is Altivate design guidance, not sourced fact. Dates and product lifecycle commitments can change; confirm current status with SAP before relying on them. This guide is general information, not legal or contractual advice.
