How one of the world’s largest energy companies reduced Oracle support spend by $15M over three years through licence termination, third-party support migration, and contract restructuring. Without disrupting operations or triggering compliance risk.
Chevron, one of the world’s largest integrated energy companies with operations in over 180 countries and annual IT spend exceeding $2 billion, was paying approximately $28M per year in Oracle support and maintenance. Over two decades of Oracle deployments, acquisitions, and organic growth, the company’s Oracle estate had grown to include thousands of processor and named-user-plus licences spanning Oracle Database Enterprise Edition, Oracle E-Business Suite, Siebel CRM, WebLogic, Oracle Fusion Middleware, and numerous specialised options and packs.
Leadership recognised that a significant portion of this support spend was no longer justified. Legacy systems had been replaced by cloud alternatives. Acquired entities had brought duplicate licences. Several middleware deployments were running at less than 10% utilisation. Yet Oracle’s annual support renewal continued to escalate with automatic 4 to 8% annual uplifts built into the contract. Creating a growing budget line that delivered diminishing value.
| Metric | Before | After | Impact |
|---|---|---|---|
| Annual Oracle support spend | $28M | $23M | $5M/year reduction (17.9%) |
| Cumulative 3-year savings | — | — | $15M |
| Licences terminated | ~3,200 (various metrics) | 0 (terminated) | $2.8M/year support eliminated |
| Products on third-party support | Oracle-supported | Rimini Street | $1.4M/year savings (50% reduction) |
| Contract uplift rate | 4–8% annual | 3% capped | $800K/year avoided escalation |
| Operational disruption | — | — | Zero |
Chevron’s savings did not come from a single dramatic move. They resulted from a disciplined, multi-layered approach. Identifying unused licences for termination, migrating low-risk products to third-party support, and renegotiating the remaining Oracle contract with hard data and competitive leverage. Each layer compounded the others.
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.
1. Legacy shelfware. Multiple Oracle products, particularly Siebel CRM modules and several Fusion Middleware components, were running at less than 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 generating $24K/year in support, with cumulative support payments exceeding $240K. 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.
| Problem Area | Products Affected | Annual Support Cost | Utilisation |
|---|---|---|---|
| Legacy shelfware | Siebel CRM, BI Publisher, Oracle Forms | $3.8M | <10% |
| Acquisition duplicates | Database EE, E-Business Suite modules | $2.1M | Redundant |
| Middleware at low use | WebLogic, SOA Suite, IDM | $1.6M | 15–25% |
| Over-priced escalation | All products (uplift compound) | $800K/year excess | — |
Map every Oracle support line item to a live system. For each CSI (Customer Support Identifier), confirm which production environment it supports and whether that system is still in active use. Any support contract without a corresponding live system is an immediate termination candidate.
Check for acquisition-inherited duplication. If your company has acquired other organisations that used Oracle, compare their ordering documents against your own. Duplicate entitlements for the same product are common.
Dispel the termination myth. Dropping Oracle support does not forfeit your perpetual licence rights. You retain full rights to use the software. You simply lose access to patches, updates, and Oracle’s support portal.
Our independent Oracle licensing specialists conduct comprehensive support audits, identify shelfware, manage third-party support transitions, and negotiate improved Oracle contract terms. Fixed-fee engagements with guaranteed ROI.
Oracle Licence Management Services →The first phase 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.
Complete CSI and ordering document inventory. The team compiled a master inventory of all Oracle Customer Support Identifiers (CSIs). 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.
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) were associated with products or options that were either no longer deployed, deployed but non-functional (installed but never used), or deployed in decommissioned environments that had not been formally shut down in Oracle’s records.
Utilisation and business criticality assessment. For products still deployed, the team assessed utilisation and business criticality on a four-tier scale.
| Tier | Definition | Support Strategy | Examples |
|---|---|---|---|
| A — Mission Critical | >70% utilisation; no viable alternative | Retain Oracle Premier Support | Database EE (production ERP), RAC, Data Guard |
| B — Important but Substitutable | 40–70% utilisation; alternatives exist | Evaluate third-party or negotiate better rates | E-Business Suite (select), WebLogic (API gateway) |
| C — Low Use / Sunset Path | 10–40% utilisation; planned retirement | Move to third-party support | Siebel CRM (migrating to Salesforce), Oracle Forms |
| D — Shelfware / Zero Use | <10% utilisation or no deployment | Terminate support immediately | BI Publisher, unused DB options, Texaco EBS modules |
Financial quantification. The audit identified $8.3M in total addressable support waste. Tier D (immediate termination): $2.8M/year for products with zero or near-zero deployment. Tier C (third-party support candidates): $2.8M/year for products on a planned sunset path, yielding approximately $1.4M/year by moving to third-party support at 50% of Oracle’s rate. Tier B (renegotiation candidates): $2.7M/year where Oracle’s escalated pricing was significantly above market.
Phase 2 focused on the lowest-risk, highest-impact action: terminating Oracle support on Tier D products. Those with zero or near-zero utilisation.
Formal termination process. Oracle’s support termination 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. 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. Where options needed to be separated, the team restructured CSIs before termination.
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 (suggesting termination could “trigger a review”), reinstatement penalties (150% of back-support), and bundled discount threats (claiming removal would eliminate pricing benefits on remaining products). The advisory team confirmed these were unfounded: support termination does not create licence non-compliance, reinstatement risk is zero for products being permanently retired, and the terminated products were on separate line items with independent pricing.
| Terminated Product | Licence Metric | Annual Support Eliminated |
|---|---|---|
| Siebel CRM (replaced by Salesforce) | Application User | $1.1M |
| Oracle BI Publisher (never activated) | Named User Plus | $280K |
| E-Business Suite — Texaco legacy modules | Application User | $620K |
| Database Options (Partitioning, OLAP — unused) | Processor | $440K |
| Oracle Forms (partially decommissioned) | Named User Plus | $360K |
| Total terminated | — | $2.8M/year |
The terminations were processed over two quarterly cycles. Total time from audit completion to full termination: 5 months.
Identify zero-use products first. Products not deployed anywhere are zero-risk termination candidates. No operational impact, no compliance risk, no reinstatement concern.
Document your compliance position before notifying Oracle. Conduct a full licence compliance assessment before sending termination notices. This ensures you have a defensible position if Oracle initiates an audit in response.
Do not be intimidated by reinstatement fees. The 150% back-support penalty only matters if you plan to return to Oracle. For products being permanently retired, reinstatement cost is irrelevant.
Use our Oracle assessment tools to identify shelfware, duplicate licences, over-provisioned options, and audit exposure across your Oracle estate.
Start Free Assessment →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. Chevron migrated these to third-party support, achieving approximately 50% cost reduction while maintaining full operational support coverage.
Product selection criteria. The advisory team applied strict criteria. No planned upgrades (products on a stable, static version with no planned upgrades were ideal candidates). Mature, well-understood technology (products in production for 5+ years with experienced in-house teams). And non-zero-day vulnerability profile (products not exposed to the internet had lower security patch urgency).
| Product | Oracle Support Cost | Third-Party Cost | Annual Savings | Rationale |
|---|---|---|---|---|
| Siebel CRM (legacy data) | $1.2M | $600K | $600K | Migrating to Salesforce; 18-month sunset |
| WebLogic (internal apps) | $480K | $240K | $240K | Stable v12c; no internet exposure |
| Oracle SOA Suite | $360K | $180K | $180K | Legacy integrations; migrating to MuleSoft |
| E-Business Suite (HR modules) | $760K | $380K | $380K | Transitioning to Workday; 24-month sunset |
| Total | $2.8M | $1.4M | $1.4M/year | — |
Provider selection. 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 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.
Transition execution. The migration followed a phased approach over 8 weeks, including a parallel support period (2 weeks) where both Oracle and Rimini were active. 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.
The final element addressed Tier A and Tier B products remaining on Oracle Premier Support. The goal was not to leave Oracle but to restructure the commercial terms.
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 and was incentivised to protect the remaining ~$21M in annual support revenue. Additionally, Chevron’s demonstrated willingness to move products to third-party support (not just threaten it) gave the renegotiation credibility.
| Term | Before | After | Annual Impact |
|---|---|---|---|
| Support uplift rate | 4–8% annual (varied by CSI) | 3% capped across all CSIs | ~$800K/year avoided escalation |
| CSI consolidation | 47 active CSIs | 12 consolidated CSIs | Simplified admin; reduced billing errors |
| Flex-down rights | No reduction rights | 10% annual reduction permitted | Future flexibility as cloud migration continues |
| Audit co-operation clause | Unlimited audit scope | Defined scope; 90-day notice | Reduced compliance risk and disruption |
| Payment terms | Annual prepayment | Quarterly in arrears | ~$5M working capital benefit |
The uplift cap. The most financially significant term change was capping annual support escalation at 3%, down from rates that ranged from 4% to 8%. On a $21M remaining support base, the difference between 3% and the average 5.5% escalation rate compounds dramatically. In Year 1, the savings is approximately $525K. By Year 3, cumulative avoided escalation reaches approximately $800K/year. Over a 5-year horizon, this single term change is projected to save Chevron over $4.5M.
CSI consolidation. Consolidating from 47 CSIs to 12 eliminated significant administrative overhead. Each CSI had its own renewal date, uplift rate, and billing cycle. 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.
| Savings Source | Year 1 | Year 2 | Year 3 | 3-Year Total |
|---|---|---|---|---|
| Licence termination (Tier D) | $2.8M | $2.8M | $2.8M | $8.4M |
| Third-party support (Tier C) | $1.4M | $1.4M | $1.4M | $4.2M |
| Contract restructuring | $525K | $680K | $800K | $2.0M |
| Billing error elimination | $120K | $120K | $120K | $360K |
| Total annual savings | $4.85M | $5.0M | $5.12M | $15M |
Zero operational 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.
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, cloud consumption trends, and third-party support performance metrics. In the 18 months since the programme completed, Chevron has avoided approximately $1.2M in additional unnecessary Oracle purchases through this governance process.
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.
“We had been paying Oracle support on products we hadn’t used in years. The phased approach gave us confidence at every step. Terminating shelfware was obvious once we had the data. Third-party support was seamless. And the contract restructuring locked in protections that will save us millions over the next five years.”
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 to 30% of their Oracle support spend is addressable through termination alone.
2. Layer your approach. Chevron’s three-phase structure was deliberate. Phase 1 (termination of unused licences) carried zero operational risk and delivered immediate savings. This built internal confidence for Phase 2 (third-party support), which required more organisational buy-in. Phase 3 (contract restructuring) was only possible because Phases 1 and 2 had created genuine negotiation leverage.
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 have documented your compliance position and confirmed your contractual rights. 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.
5. Contract terms matter as much as price. The escalation cap alone (3% vs 4 to 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 Oracle relationship.
| Lesson | Implication for Your Organisation |
|---|---|
| Audit before you negotiate | You cannot negotiate what you do not measure. Map every CSI to a live system. |
| Terminate shelfware first | Zero-use products = zero-risk termination. Easiest, fastest savings. |
| Use third-party support strategically | Ideal for sunset products. Not ideal for products you are actively upgrading. |
| Cap escalation contractually | Uncapped 5%+ annual uplifts compound dramatically. A 3% cap saves millions. |
| Create leverage through action | Actually terminating and migrating products creates leverage. Threatening does not. |
| # | Action | Timing | Expected Outcome |
|---|---|---|---|
| 1 | Compile complete Oracle CSI and support inventory. List every active CSI, products covered, annual fee, and current uplift rate. | Weeks 1–2 | Single source of truth for Oracle spend |
| 2 | Map each supported product to a live system. Confirm production, dev, or test deployment. Anything without a live system = termination candidate. | Weeks 3–6 | Identify shelfware (typically 15–30%) |
| 3 | Classify products by A/B/C/D tier framework. Assess utilisation and business criticality. | Weeks 6–8 | Prioritised action plan with quantified savings |
| 4 | Execute Tier D terminations. Formal support termination notices for zero-use products. | Weeks 8–14 | Immediate annual savings |
| 5 | Evaluate third-party support for Tier C. Shortlist providers, negotiate terms, plan phased transition. | Weeks 10–18 | ~50% cost reduction on sunset products |
| 6 | Renegotiate Oracle terms for Tier A/B. Focus on escalation caps, flex-down rights, CSI consolidation. | Months 4–8 | Structural protections over contract term |
| 7 | Implement quarterly governance. Utilisation reviews, third-party performance, new purchase justification. | Ongoing | Sustained savings; prevents cost creep |
Expected outcome by organisation size:
| Annual Oracle Support Spend | Typical Addressable Savings | Projected 3-Year Impact |
|---|---|---|
| $5M–$10M | 15–25% | $2.3M–$7.5M |
| $10M–$25M | 18–30% | $5.4M–$22.5M |
| $25M–$50M+ | 20–35% | $15M–$52.5M |
Through a three-phase programme: (1) terminating support on unused/shelfware products ($2.8M/year), (2) migrating sunset-path products to third-party support at 50% cost reduction ($1.4M/year), and (3) renegotiating contract terms on remaining products, including capping annual escalation at 3% ($800K+/year). The cumulative three-year savings totalled approximately $15M.
No. Dropping Oracle Premier Support does not affect your perpetual licence rights. You retain full rights to use the software. You simply lose access to Oracle patches, updates, and support portal. This is a common misconception that costs enterprises millions in unnecessary support payments.
Oracle charges 150% of cumulative back-support, meaning 100% of the support fees for every year the product was off support, plus a 50% penalty. This makes reinstatement expensive for long gaps. However, this cost is only relevant if you actually plan to return. For products being permanently retired, reinstatement risk is zero.
Ideal candidates are mature, stable products on a fixed version with no planned upgrades, not exposed to internet-facing security risks, and preferably on a sunset/retirement path. Common examples include Siebel CRM, Oracle Forms, older E-Business Suite modules, and WebLogic instances used for internal applications.
For stable, mature products, third-party providers typically deliver equivalent or superior support quality with faster response times and dedicated named engineers. The cost is approximately 50% of Oracle’s fee. The trade-off is losing access to Oracle patches and new version upgrade rights, which is irrelevant for products you are not upgrading.
Oracle may initiate an audit in response, occurring in approximately 30% of cases. However, support termination does not create compliance exposure. If you have documented your licence compliance position before taking action, an audit is manageable. Having independent audit defence expertise available during this period is advisable.
A CSI (Customer Support Identifier) is Oracle’s unique reference for tracking support entitlements. Each CSI is linked to specific Oracle products and generates its own billing. Many enterprises hold dozens of CSIs accumulated over years. Consolidating them simplifies management, reduces billing errors, and creates clearer negotiation leverage.
Enterprises with $5M+ in annual Oracle support spend typically identify 15 to 35% in addressable savings through shelfware termination, third-party support migration, and contract restructuring. Organisations that have grown through acquisition or maintained Oracle relationships for 10+ years find savings at the higher end.
A typical engagement spans 6 to 14 months: 6 to 10 weeks for the initial assessment, 2 to 4 months for termination execution and third-party transition, and 3 to 6 months for contract renegotiation (ideally aligned to the renewal cycle). Quick wins from shelfware termination can be realised within 3 to 4 months.
Yes. Redress provides end-to-end advisory: licensing and support assessment, third-party support transition management, Oracle contract negotiation, and audit defence. All fixed-fee, 100% vendor-independent. No commercial relationships with Oracle or any third-party support provider.
Most enterprises are paying Oracle support on products that have been replaced, duplicated through acquisitions, or never deployed. Our independent advisory team identifies every dollar of waste and builds a structured plan to eliminate it. Without disruption, without compliance risk.