Oracle renewal SLA negotiation points.

Oracle Premier Support carries a published Service Level Agreement framework that most customers never examine in detail. The standard SLAs are accepted on a take it or leave it basis on the assumption that they cannot be opened. On large renewals, they can be. This article walks through the four SLAs that matter most to customer outcomes, the standard Oracle position on each, and the buyer side mark up we propose.

The framework

Oracle Premier Support divides incidents into four severity levels. Severity 1 is a complete production outage. Severity 2 is a severe impact but not a complete outage. Severity 3 is a non production issue or a workaround acceptable production issue. Severity 4 is a question or feature request. Each severity carries a response time SLA and an escalation path. The Service Request, opened through My Oracle Support, is the system that carries the SLA in operational practice.

The standard published response times are 1 hour for Severity 1, 4 hours for Severity 2, 24 hours for Severity 3, and 48 hours for Severity 4. These are response times, not resolution times. Resolution times are not committed in the standard SLA. The distinction matters because most customer dissatisfaction with Oracle support stems from extended resolution windows, not extended initial response.

SLA 1 the response time

The response time is the time from the customer's opening of a Service Request to Oracle's first substantive engagement on that SR. The standard 1 hour Severity 1 commitment is not always met in practice. We have seen Severity 1 SRs sit unattended for 4 hours on a Sunday evening, and Severity 2 SRs sit for 12 hours on a Monday morning.

The buyer side mark up is a contractual remedy for missed response. We negotiate a credit against the next year's support fee equal to one day of pro rata support for each missed Severity 1 response and one day for every two missed Severity 2 responses. Oracle resists this in initial conversation but signs it on sufficiently large renewals. The credit framework also gives the customer a measurable enforcement mechanism rather than the standard escalation path which can stall.

SLA 2 the resolution time

Standard Oracle Premier Support does not commit a resolution time. The buyer side ask on a large renewal is a tiered resolution commitment. For Severity 1, a resolution or an Oracle approved workaround within 24 hours. For Severity 2, within 5 business days. For Severity 3, within 30 business days. For Severity 4, best effort.

Oracle will sign these only on large renewals and only with substantial qualifications. The qualifications are usually acceptable to the customer because they exclude the cases where the resolution depends on third party software or on a customer environmental issue. The remaining cases are the cases where Oracle is genuinely accountable, and on those the commitment is real. Audit defense is a related service where SLA quality matters for an entirely different reason.

SLA 3 the escalation path

Oracle's standard escalation path runs from the Service Request engineer to the team lead, then to the duty manager, then to the regional support manager, then to the global support escalation team. The path is documented in Oracle's My Oracle Support knowledge base. The standard path can take 24 to 72 hours to traverse on a Severity 1 incident.

The buyer side mark up is a named contact escalation. For large customers, Oracle will assign a named Technical Account Manager and a named Customer Success Manager. The TAM and the CSM become the first call escalation contacts and bypass the standard queue. The customer pays for this through the support fee structure but on large estates it is almost always worth the cost. For deeper procurement maturity discussion see Oracle procurement maturity model.

SLA 4 the patch and update commitment

Premier Support carries the right to access patches, security updates, and Critical Patch Updates as they are released. The default contract language commits Oracle to make patches available on a published calendar. It does not commit Oracle to deliver a patch within any specific window if the customer is the one who reports the underlying defect.

The buyer side mark up is a Customer Reported Defect SLA. We negotiate language that obliges Oracle to acknowledge the defect within 5 business days of the customer's submission, to provide a workaround within 30 business days, and to ship a permanent fix within the next regularly scheduled patch update for the affected product. Oracle signs this on customers running large Database or EBS footprints. For Oracle EBS coverage see Oracle E-Business Suite.

What we ask for that is not strictly an SLA

Beyond the four formal SLAs, the support relationship carries operational commitments that are not formally service levels but materially affect customer outcomes. We negotiate language around each on large renewals.

The geographic support coverage clause specifies the regions and the languages in which support is delivered. For multinational customers, support that is only available in English from a single time zone can create production risk. We negotiate explicit geographic and language coverage for at least the customer's three largest deployment regions.

The technical environment retention clause specifies how long Oracle retains the diagnostic and trace files the customer uploads in connection with a Service Request. Oracle's default retention is short. For customers in regulated industries that require evidence retention, the default is inadequate. We negotiate a retention extension to at least seven years.

The version certification clause specifies which versions of Oracle programs Oracle commits to support against which versions of the operating system, the chip architecture, and the third party software stack. The standard certification matrix is published in My Oracle Support and is subject to change. On a large renewal we negotiate language that locks in the certification matrix at the renewal date and prevents Oracle from de certifying a configuration the customer is actively running.

The engagement model

SLA negotiation typically rides on the broader renewal engagement. The price of the renewal is the headline number. The SLAs are where the operational risk lives. We mark up the SLAs on every renewal over a defined size threshold, under success fee structure where the savings on the headline number justify the engagement and the SLA improvements are written into the contract as additional consideration. For the broader renewal framework see Oracle Renewal Negotiation. For the contract term context see Oracle Contract Terms. For Oracle EBS specifically see Oracle E-Business Suite. For the underlying framework download The Oracle Negotiation Playbook.