Case Study: Chevron Saves $15M Through Strategic Oracle Support Optimisation and Licensing Controls

Chevron's Oracle relationship had been built over more than two decades. The company's Oracle estate was the product of organic growth, multiple corporate acquisitions (including Texaco in 2001 and Unocal in 2005), and successive technology refresh cycles that added new Oracle products while rarely fully decommissioning the old. The result was an Oracle licensing portfolio of extraordinary breadth and complexity.

The Scale of the Oracle Estate:

At its peak, Chevron held Oracle licences spanning: Oracle Database Enterprise Edition (with Advanced Security, Partitioning, Diagnostics Pack, Tuning Pack, and Real Application Clusters options); Oracle E-Business Suite (Financials, Supply Chain, HR, Manufacturing modules); Siebel CRM (inherited partly from the Texaco acquisition); Oracle Fusion Middleware (WebLogic, SOA Suite, Identity Management); and numerous Oracle BI and analytics tools. The total support bill across these products had grown to approximately $28M per year — roughly 22% of Chevron's overall Oracle spend including licence fees, support, and cloud subscriptions.

The Core Problems:

1. Legacy shelfware. Multiple Oracle products — particularly Siebel CRM modules and several Fusion Middleware components — were running at <10% utilisation or had been functionally replaced by cloud-native alternatives (Salesforce for CRM, ServiceNow for ITSM). Yet Chevron continued paying full Oracle Premier Support on these products because no one had conducted a systematic review of which support contracts were still delivering value.

2. Acquisition-inherited duplication. The Texaco and Unocal acquisitions had brought Oracle licences that overlapped with Chevron's existing entitlements. In some cases, the same Oracle Database product was licenced multiple times across different contract ordering documents — each generating its own support stream. Consolidation had never been formally executed at the licensing level, even though the underlying technical environments had been merged years earlier.

3. Unchallenged support escalation. Chevron's Oracle Ordering Documents included annual support uplift clauses ranging from 4% to 8%. Over 10 years of compounding, some product lines were paying support fees that exceeded the original licence cost. A Partitioning option originally licenced for $180K was now generating $24K/year in support — with the cumulative support payments exceeding $240K, well above what the licence had cost. This pattern was repeated across dozens of line items.

4. Fear of compliance risk. Internal teams were reluctant to terminate any Oracle support contract because of concern that doing so would trigger an Oracle audit or create compliance exposure. This "better safe than sorry" mentality had persisted for years, effectively giving Oracle an unchallenged revenue stream. In reality, dropping Oracle support does not forfeit licence rights — but this misconception was costing Chevron millions annually.

The first phase of Chevron's optimisation programme was a comprehensive audit of every Oracle support contract against actual system deployment, utilisation, and business criticality. This phase lasted approximately 12 weeks and involved collaboration between IT operations, enterprise architecture, procurement, and an independent licensing advisory firm.

1. Complete CSI and Ordering Document Inventory:

The team compiled a master inventory of all Oracle Customer Support Identifiers (CSIs) — the unique references Oracle uses to track support entitlements. Chevron held 47 active CSIs across multiple ordering documents, business units, and geographic entities. Many of these CSIs had been created during different eras of Chevron's Oracle relationship and were never consolidated. The inventory mapped each CSI to: the specific Oracle products and metrics covered, the annual support fee, the contract start date and current uplift rate, and the Oracle ordering document it belonged to.

2. System-Level Deployment Mapping:

For each CSI, the team verified whether the associated Oracle products were still deployed in production, development, or test environments. This involved working with Oracle tooling (Oracle LMS scripts and the Oracle Database feature-tracking DBA_FEATURE_USAGE_STATISTICS view) to identify actual product installations and feature activation across Chevron's global infrastructure — spanning data centres in Houston, London, Singapore, and multiple cloud environments.

The mapping revealed that approximately 3,200 licence units (across various metrics — processor, named-user-plus, and application-user licences) were associated with products or options that were either: (a) no longer deployed anywhere, (b) deployed but non-functional (installed but never used), or (c) deployed in decommissioned environments that hadn't been formally shut down in Oracle's records.

3. Utilisation and Business Criticality Assessment:

For products that were still deployed, the team assessed utilisation and business criticality on a four-tier scale:

4. Financial Quantification:

The audit identified $8.3M in total addressable support waste, broken down as follows:

Tier D — Immediate termination candidates: $2.8M/year in support for products with zero or near-zero deployment. These included Siebel CRM modules that had been replaced by Salesforce three years earlier, Oracle BI Publisher licences never activated, and database options (Partitioning, OLAP) enabled in ordering documents but never technically deployed.

Tier C — Third-party support candidates: $2.8M/year in support for products on a planned sunset path. Siebel CRM (partially still in use for legacy customer data), Oracle Forms-based applications (scheduled for modernisation), and selected WebLogic instances used only for internal non-critical applications. Moving these to third-party support at ~50% of Oracle's rate would yield approximately $1.4M/year in savings.

Tier B — Renegotiation candidates: $2.7M/year in support for important products where Oracle's escalated pricing was significantly above market. These products would remain on Oracle support, but the commercial terms needed restructuring — particularly the 8% annual uplift clauses that had compounded over a decade.

With the audit complete, Phase 2 focused on the lowest-risk, highest-impact action: terminating Oracle support on Tier D products — those with zero or near-zero utilisation. This phase required careful execution to avoid compliance pitfalls and to manage Oracle's predictable pushback.

1. Formal Termination Process:

Oracle's support termination process requires written notice — typically 30 days before the next support renewal date. Chevron's legal and procurement teams prepared formal termination notices for 14 CSIs covering the Tier D products, referencing the specific ordering documents and support line items to be terminated. The notices were sent via registered post and email to Oracle's contracts administration team, with copies retained for Chevron's records.

A critical procedural point: Oracle's contracts require that support can only be terminated for entire product lines within a CSI, not for individual options or packs. This meant Chevron couldn't simply drop the Partitioning option while retaining Database Enterprise Edition support under the same CSI. Where options needed to be separated, the team worked to restructure CSIs before termination — creating new, clean ordering documents that isolated the products being retained from those being terminated.

2. Oracle's Response and Counter-Tactics:

As expected, Oracle's sales team responded aggressively to the termination notices. Their tactics included:

Fear of compliance exposure: Oracle's account team suggested that terminating support could "trigger a review" of Chevron's licensing position — a thinly veiled audit threat. The advisory team helped Chevron respond factually: support termination does not create licence non-compliance, and Oracle's audit rights exist independently of support status. Having a clean, documented compliance position (from the Phase 1 audit) neutralised this pressure.

Reinstatement penalties: Oracle warned that if Chevron ever needed to reinstate support on terminated products, it would face reinstatement fees of 150% of back-support — the cumulative support fees for every year the product was off support, plus a 50% penalty. This is a real cost, but it's only relevant if you plan to return to Oracle support. For products being permanently retired, reinstatement risk is zero.

Bundled discount threats: Oracle claimed that removing certain products would eliminate "bundled pricing benefits" on remaining products, potentially increasing support costs elsewhere. The advisory team reviewed Chevron's ordering documents and confirmed that the terminated products were on separate line items with independent pricing — the bundling claim was unfounded.

3. Execution and Financial Impact:

The terminations were processed over two quarterly cycles. Oracle attempted to delay processing on several items, but Chevron's legal team enforced the contractual notice periods. Total time from audit completion to full termination: 5 months.

With Tier D products terminated, Phase 3 addressed Tier C — products still in active use but on a sunset path, where Oracle Premier Support was no longer delivering proportionate value. For these products, Chevron migrated to third-party support, achieving approximately 50% cost reduction while maintaining full operational support coverage.

1. Product Selection for Third-Party Support:

The advisory team applied strict criteria to determine which products were suitable for third-party support migration:

No planned upgrades: If Chevron intended to upgrade to a newer Oracle version within the next 2–3 years, staying on Oracle support made sense (to receive patches and upgrade rights). Products on a stable, static version with no planned upgrades were ideal candidates.

Mature, well-understood technology: Products that had been in production for 5+ years, with well-documented configurations and experienced in-house support teams, presented lower risk. Third-party providers excel at supporting stable, mature deployments.

Non-zero-day vulnerability profile: Products not exposed to the internet (internal middleware, back-office applications) had lower security patch urgency, making the absence of Oracle's quarterly Critical Patch Updates less impactful.

Based on these criteria, Chevron selected the following products for third-party support migration:

2. Provider Selection — Rimini Street:

After evaluating major third-party support providers (Rimini Street, Spinnaker Support, and US Cloud), Chevron selected Rimini Street based on: breadth of coverage across all four product families, named dedicated support engineers with Oracle-specific expertise, contractual SLAs matching or exceeding Oracle Premier Support response times, and Rimini's track record with other Fortune 50 energy companies.

The contract was structured as a 3-year agreement at 50% of Oracle's net support fee, with a price lock (no annual escalation) and an exit clause allowing Chevron to return to Oracle support for any individual product with 90 days' notice. This exit flexibility was important to internal stakeholders concerned about being "locked in" to a third-party provider.

3. Transition Execution:

The migration followed a phased approach over 8 weeks. For each product, Rimini Street's onboarding team: conducted a technical deep-dive with Chevron's DBA and middleware teams, documented the current configuration and known issues, established secure access to Chevron's support ticket system, and ran a parallel support period (2 weeks) where both Oracle and Rimini were active — allowing side-by-side comparison of response quality before Oracle support was formally terminated.

The transition completed with zero operational disruption. Post-migration satisfaction surveys showed that Chevron's technical teams rated Rimini's support quality as equal to or better than Oracle's — particularly noting faster response times for Siebel and WebLogic issues, where Oracle's own support teams had become less responsive as these products aged.

The final element of Chevron's optimisation programme addressed Tier A and Tier B products — those remaining on Oracle Premier Support because they were mission-critical or strategically important. For these products, the goal wasn't to leave Oracle but to restructure the commercial terms to eliminate excessive pricing and protect against future escalation.

1. Leverage Created by Phases 1 and 2:

The $4.2M in annual savings already secured through termination ($2.8M) and third-party migration ($1.4M) had fundamentally shifted the negotiation dynamic. Oracle's account team was facing a significant revenue loss on the Chevron account — and was incentivised to protect the remaining ~$21M in annual support revenue. This created an opening for Chevron to negotiate improved terms on the retained support contracts without Oracle having strong leverage to resist.

Additionally, Chevron's demonstrated willingness to move products to third-party support — not just threaten it — gave the renegotiation credibility. Oracle understood that the remaining Tier B products (E-Business Suite financials, WebLogic for critical APIs) could follow the same path if commercial terms weren't improved.

2. Key Terms Renegotiated:

3. The Uplift Cap — $800K/Year in Compounding Savings:

The most financially significant term change was capping annual support escalation at 3% — down from rates that ranged from 4% to 8% across different ordering documents. On a $21M remaining support base, the difference between 3% and the average 5.5% escalation rate compounds dramatically over time. In Year 1, the savings is approximately $525K. By Year 3, the cumulative avoided escalation reaches approximately $800K/year — because each year's saving compounds on the prior year's lower base.

Over a 5-year horizon, this single term change is projected to save Chevron over $4.5M in cumulative avoided escalation compared to the original contract terms.

4. CSI Consolidation — Administrative Simplification:

Consolidating from 47 CSIs to 12 eliminated significant administrative overhead. Each CSI had its own renewal date, uplift rate, and billing cycle — creating a complex web of renewal management. With 12 consolidated CSIs, Chevron's procurement team could manage the entire Oracle support relationship through quarterly reviews rather than continuous ad hoc renewals. This also reduced billing errors, which had previously resulted in approximately $120K/year in overpayments that required time-consuming reconciliation with Oracle.

Chevron's three-phase optimisation programme delivered $15M in cumulative savings over three years — transforming the Oracle support cost structure from an unchallenged, escalating budget line into a managed, optimised expenditure aligned with actual business value.

Operational Impact: Zero Disruption

Throughout the entire optimisation programme — spanning 14 months from audit initiation to full completion — Chevron experienced zero operational disruption. No systems went unsupported, no compliance gaps were created, and no audit was triggered. The phased approach ensured that support coverage transitioned seamlessly from Oracle to Rimini Street for Tier C products, while Tier D products were confirmed as unused before support was terminated.

Ongoing Governance:

To prevent Oracle support costs from creeping back up, Chevron implemented a quarterly Oracle licensing review process. Every quarter, the procurement and IT architecture teams assess: current Oracle product utilisation vs entitlements, any new Oracle deployments or activations (to ensure they're properly licensed and the support cost is justified), BTP/cloud consumption trends (as Chevron increasingly adopts Oracle Cloud Infrastructure for some workloads), and third-party support performance metrics (SLA adherence, ticket resolution times).

This governance cadence ensures that the $5M+/year in savings is sustained and that new Oracle purchases are challenged against alternatives before being approved. In the 18 months since the programme completed, Chevron has avoided approximately $1.2M in additional unnecessary Oracle purchases through this governance process.

Key point: The $15M in savings was not a one-time event. The annual run-rate savings of $5M+/year continues to compound as avoided escalation grows. Over 5 years, projected cumulative savings exceed $27M — making this one of the highest-ROI IT procurement initiatives Chevron has undertaken.

Chevron's experience offers a replicable blueprint for any large enterprise paying significant Oracle support fees. Here are the transferable lessons, applicable regardless of industry or Oracle estate size.

1. Start With Data, Not Assumptions:

The single most impactful action was the comprehensive audit. Without mapping every CSI to a live system, Chevron would have continued paying $2.8M/year for products that were literally unused. Most enterprises we work with discover that 15–30% of their Oracle support spend is addressable through termination alone. The data exists in your Oracle contracts and IT asset management systems — it just needs to be connected.

2. Layer Your Approach — Don't Try to Do Everything at Once:

Chevron's three-phase structure was deliberate. Phase 1 (termination of unused licences) carried zero operational risk and delivered immediate, undeniable savings. This built internal confidence and credibility for Phase 2 (third-party support) — which required more organisational buy-in because it involved changing support providers for live systems. Phase 3 (contract restructuring) was only possible because Phases 1 and 2 had created genuine negotiation leverage. Attempting all three simultaneously would have diluted focus and likely reduced outcomes.

3. Oracle Will Push Back — Be Prepared:

Every Oracle optimisation programme triggers a response from Oracle's sales team. Expect audit threats, reinstatement fee warnings, and claims about bundled pricing. None of these should change your strategy if you've done the preparatory work: documented your compliance position, confirmed your contractual rights to terminate support, and verified that no genuine "bundled pricing" clauses apply to your specific ordering documents. Having independent audit defence expertise available during this period provides essential confidence.

4. Third-Party Support Is Legitimate and Effective — For the Right Products:

Chevron's experience confirms that third-party support delivers equivalent or superior service for stable, mature Oracle products. The key is product selection: candidates should be on a stable version with no planned upgrades, not exposed to internet-facing security risks, and ideally on a sunset path. Products you're actively developing on or planning to upgrade should remain on Oracle Premier Support for access to patches and new releases.

5. Contract Terms Matter as Much as Price:

The escalation cap alone (3% vs 4–8%) will save Chevron more over 5 years than many of the individual product terminations. Flex-down rights, consolidated CSIs, improved payment terms, and defined audit scope all contribute to a healthier, more manageable Oracle relationship. Too many enterprises focus exclusively on unit price while accepting punitive structural terms that erode value over time.

Redress Compliance provides end-to-end advisory support for enterprises seeking to optimise their Oracle support and licensing expenditure. Our engagement model follows the same structured approach demonstrated in the Chevron case study.

1. Oracle Licensing and Support Assessment:

We conduct a comprehensive audit of your Oracle estate — mapping every CSI, ordering document, and support entitlement to actual system deployments. Using a combination of Oracle tooling outputs (LMS scripts, feature usage statistics), CMDB data, and contract analysis, we identify every instance of shelfware, duplication, over-licensing, and over-priced support. The assessment typically takes 6–10 weeks and delivers a detailed findings report with quantified savings opportunities by category.

2. Third-Party Support Transition Advisory:

For products identified as third-party support candidates, we manage the evaluation and transition process: shortlisting providers, negotiating commercial terms, overseeing technical onboarding, and managing the parallel support period. Our Oracle Third-Party Support Advisory Service has supported over 40 enterprise transitions with zero operational disruption.

3. Oracle Contract Negotiation:

Armed with the assessment data and any third-party migration leverage, we lead commercial negotiations with Oracle to restructure remaining support contracts. This includes escalation caps, flex-down rights, CSI consolidation, improved payment terms, and defined audit co-operation clauses. Our Oracle Contract Negotiation Service operates on a fixed-fee basis — our compensation is not tied to Oracle's pricing, ensuring completely independent advice.

4. Audit Defence (If Needed):

If Oracle initiates an audit in response to support termination or contract restructuring — which happens in approximately 30% of optimisation engagements — our Oracle Audit Defence Service provides full representation. We manage all communication with Oracle LMS, challenge their findings where applicable, and ensure any resolution is commercially fair.

Key point: Redress Compliance has no commercial relationships with Oracle, Rimini Street, or any other software vendor or support provider. Our advice is 100% independent — we recommend the approach that delivers the best outcome for your organisation, whether that means staying with Oracle, migrating to third-party, or a hybrid combination.

Every large enterprise paying significant Oracle support fees has optimisation potential. Based on Chevron's experience and dozens of similar engagements, here is a practical action plan.

Expected Outcome by Organisation Size:

These ranges reflect actual client outcomes across industries including energy, financial services, manufacturing, retail, and telecommunications. The largest savings typically come from organisations that have grown through acquisition (creating licence duplication) and those with Oracle relationships exceeding 10 years (where support escalation has compounded significantly).