Energy Corporation: $8.2M Oracle Cloud Cost Saved Before Contract Signature

The Challenge

A large energy corporation with operations across six countries was executing a board-approved cloud transformation programme. The strategic decision had been made to migrate 60% of Oracle workloads to OCI — Oracle's own cloud platform — on the basis that BYOL (Bring Your Own Licence) rights would minimise incremental licence cost. The cloud team had negotiated a three-year OCI Universal Credits commitment of $14M directly with Oracle's cloud sales team, with board sign-off expected within six weeks.

Three critical misunderstandings had been embedded into the business case during the 18-month internal planning process. First, the team assumed all existing on-premises Oracle Database EE licences qualified for BYOL across all OCI service tiers. They did not — Oracle SE2 licences cannot be used for BYOL on OCI Exadata Cloud Service, and 40% of the planned BYOL deployments were on SE2. Second, they had modelled Oracle Support Rewards as a simple 25% credit against all OCI spend. Support Rewards are capped at 33% of annual OCI commitment, require specific CSI-to-tenancy linking that must be completed before spend occurs, and are only available for support contracts that are current and correctly registered. The energy company had six separate CSIs across merged entities — none had been linked. Third, the deployment plan included Oracle Database Management Packs (Diagnostics Pack, Tuning Pack) in BYOL configurations where these packs require separate licences.

When a board member with prior Oracle commercial experience flagged the BYOL rules as a potential concern, the company sought independent review. We were engaged with six weeks to contract signature.

Our Approach

1. BYOL Eligibility Mapping

   We mapped every Oracle Database licence in the estate against OCI BYOL eligibility requirements, service tier by tier. Oracle's BYOL rules differ significantly across OCI services: Database Cloud Service (Base Database), Exadata Cloud Service, and Autonomous Database have different BYOL qualification criteria. Oracle SE2 licences are explicitly excluded from BYOL on Exadata Cloud Service. Of the 40% of planned deployments on SE2, we designed an alternative: routing SE2 workloads to OCI Base Database with standard compute-based pricing, which proved more cost-effective than upgrading SE2 to EE for BYOL purposes. This restructure alone saved $2.8M in Year 1 by avoiding EE upgrades Oracle's team had positioned as necessary.

2. Support Rewards Activation

   Oracle's Support Rewards programme requires CSI numbers to be linked to the OCI tenancy before cloud spend occurs — credits cannot be applied retroactively to spend that preceded the CSI linking. The energy company had six CSIs from three merger events. We coordinated the CSI consolidation with Oracle's support team, verified that all support contracts were in good standing, and completed the tenancy linking before contract signature. This activated $1.1M in annual Support Rewards that would otherwise have been permanently lost.

3. Universal Credits Consumption Modelling

   OCI Universal Credits provide flexibility across services, but over-commitment to credits that cannot be consumed within the contract term has no refund mechanism. We built a workload-by-workload consumption model projecting monthly OCI credit usage against the proposed $14M commitment. The model identified $2.3M in credits allocated to services the energy company was unlikely to deploy within the three-year term. We recommended restructuring the commitment to reduce Year 1 Universal Credits by $2.3M and add a contractual option to increase in Years 2 and 3 based on actual consumption.

4. Contract Negotiation

   Armed with a corrected commercial model, we entered negotiation with Oracle's cloud sales team. Oracle's team initially resisted changes, citing the board-approved timeline. We presented the corrected BYOL analysis, the Support Rewards activation documentation, and the consumption model. Oracle revised their position. Final terms: $3.1M reduction in Year 1 commitment, flexible growth mechanism for Years 2–3, and explicit contractual permission to reallocate credits across OCI service categories without triggering a compliance review.

5. Management Pack Compliance Review

   Before go-live, we reviewed the planned Database Cloud Service configurations to ensure Database Options (Diagnostics Pack, Tuning Pack, Real Application Clusters, Advanced Security) were either included in the BYOL licence entitlement or excluded from the deployment. Oracle's cloud pricing includes some options at certain service tiers and excludes them at others — the deployment architecture required specific configuration to avoid inadvertent management pack usage without entitlement.

The Results