An OCI Universal Credits commitment reshaped from $14M to $6.5M.
A telecommunications group had committed to an annual OCI spend disconnected from its consumption forecast, with on premises licences it could have brought to the cloud left unused.
A telecommunications group had committed to an annual OCI spend disconnected from its consumption forecast, with on premises licences it could have brought to the cloud left unused.
The client was a telecommunications group migrating workloads to Oracle Cloud Infrastructure under a Universal Credits commitment. The commitment had been signed during the initial migration enthusiasm at an annual figure of $14M, sized against an optimistic forecast of how quickly the group would move workloads into OCI. The actual migration ran slower and the actual consumption ran well below the commit.
Universal Credits work as a prepaid commitment drawn down by consumption across OCI services. Commit too high and the group pays for capacity it never uses, because unused commitment generally does not roll over indefinitely and is effectively forfeited. The group was on track to underconsume its commit by a wide margin, paying for cloud it was not using while its on premises Oracle estate continued under separate support.
Compounding the waste, the group held substantial on premises Oracle Database licences that it was entitled to bring to OCI under Bring Your Own Licence. BYOL dramatically reduces the OCI consumption rate for database workloads because the licence cost is already sunk on premises. The group had been consuming OCI database services at the full licence included rate rather than the far lower BYOL rate, drawing down its commit faster per workload while simultaneously paying support on idle on premises entitlements.
The group faced a commitment renewal and needed to right size the commit to real consumption, correct the BYOL position, and avoid locking in another oversized commitment for the next term.
The Measure phase built a true consumption model. We analysed actual OCI usage across compute, storage, and database services over the preceding periods and projected forward against the real migration roadmap rather than the original optimistic forecast. This produced a defensible consumption range that was less than half the standing commit.
In parallel we mapped the group's on premises Oracle entitlements that were eligible for Bring Your Own Licence on OCI. The group held Database Enterprise Edition licences with active support that could be applied to its OCI database workloads, converting them from the full licence included consumption rate to the much lower BYOL rate. We modelled the consumption impact of switching every eligible database workload to BYOL, which materially reduced the credits drawn down per workload and therefore the commit the group needed to carry.
We then modelled the commercial structure. A right sized commitment aligned to real consumption, combined with a BYOL position applied across eligible workloads, produced a commit requirement of $6.5M, less than half the original. We also modelled the flexibility terms, because a commitment that is right sized but rigid can still trap a group if consumption shifts. The objective was a commit that matched consumption and had room to flex.
In the Negotiate phase we took the consumption model and the BYOL analysis to the renewal. Because the model was grounded in the group's own usage data and the BYOL entitlements were documented, the reshaped commit was defensible rather than a request for a discount. We negotiated the commit down to the consumption aligned figure and corrected the rate applied to database workloads to BYOL.
The Convert phase secured the forward position. The renewed agreement aligned the commit to the consumption model, applied BYOL across all eligible database workloads, and built in flexibility to adjust the commit if the migration roadmap changed materially. The group stopped paying for cloud it was not using and stopped paying twice for database licences it already owned.
The group was paying for cloud it never used while paying support on the very licences it was entitled to bring to that cloud. The commit corrected both at once.
The annual commitment reshaped from $14M to $6.5M, a reduction of 54 percent, with BYOL applied across eligible database workloads. The table shows the drivers of the reduction.
| Exposure category | Oracle claim | Settled |
|---|---|---|
| Original commit (optimistic forecast) | $14.0M | n/a |
| Right sizing to real consumption | -$4.8M | applied |
| BYOL rate on database workloads | -$2.7M | applied |
| Reshaped consumption aligned commit | $6.5M | $6.5M |
The renewed agreement tied the Universal Credits commit to the documented consumption model rather than a forecast, so the group commits to what it will actually use. Bring Your Own Licence was applied across every eligible database workload, ending the double payment of OCI database consumption and on premises support on the same entitlements.
A flexibility provision allows the commit to be revisited if the migration roadmap changes materially, preventing the group from being locked into another oversized commitment. The group now manages its OCI spend against real consumption with its on premises entitlements working for it in the cloud rather than sitting idle.
For the buyer side perspective on this product line, our Oracle Cloud and OCI licensing team and our Oracle Database licensing practice work the same playbook on every engagement. Compare outcomes across the full case study library.
If an OCI Universal Credits commitment was sized against a forecast rather than consumption, a usage model and a BYOL review usually reveal a much smaller defensible commit.
Request a Consultation