Journal / Case Studies / How a Manufacturer Cut OCI Costs 42%
Case Studies

How a Manufacturer Cut OCI Costs 42%

Published Apr 9, 2026 · 9 min read · OCI Specialists · Independent OCI advisory
How a Manufacturer Cut OCI Costs 42%

A manufacturing company running its Oracle estate on Oracle Cloud Infrastructure had a problem familiar to many: the bill kept rising, nobody could fully explain why, and the assumption that cloud would be cheaper than the data centre it replaced was quietly proving false. This anonymized case study describes how that estate was brought back under control, cutting OCI spend by forty two percent without reducing performance or capability. The client is anonymized by sector, but the numbers and the methods are real.

It is one of the case studies behind our OCI case studies and benchmarks pillar, and the cost reduction it describes is the same forty percent pattern documented across sectors in OCI cost optimization benchmark data.

The situation

The manufacturer had migrated to OCI two years earlier in a lift and shift that prioritised speed over efficiency, which was a reasonable choice at the time but left a great deal of waste baked into the estate. Compute shapes had been chosen by matching or exceeding the on premises servers they replaced, on the safe assumption that bigger could not hurt. Storage had been provisioned at the highest performance tier across the board. Non production environments ran around the clock. The licensing model had been carried over unexamined from the data centre.

None of this was visible as a single problem, which is why it had persisted. The bill was simply a large number that grew, and without anyone whose job was to question it, it grew unchallenged. The finance team knew the spend was high but lacked the technical detail to challenge it, and the engineering team was focused on delivery rather than cost. The estate needed an independent look from someone whose only job was to find the waste.

What we did

The work began with an assessment that measured what the estate actually used rather than what it had been given. That measurement is the foundation of all cost optimization, because waste is invisible until usage is compared to provisioning. The assessment revealed exactly the pattern expected: compute sized far above real demand, storage paying for performance the data did not need, environments running when nobody was using them, and a licensing arrangement that no longer fit.

From that measurement came four streams of work, each addressing one source of waste. None of them touched the performance the business actually experienced, because each removed only capacity or cost that was not delivering value. The four streams, and what each contributed, are set out below.

Right sizing the compute

The largest single saving came from right sizing the compute. Shapes that had been chosen with a generous safety margin were resized to match the demand the measurement revealed, which in most cases meant a substantial reduction. Because the resizing was based on real usage data with headroom for genuine peaks, performance was unaffected; the estate simply stopped paying for cores and memory it never used. This stream alone accounted for the largest part of the forty two percent.

The discipline that made this safe was measurement before action. Right sizing on a guess is dangerous; right sizing on data, with a margin for peaks, is simply removing waste. The principle is the same one set out in our cost benchmark data: the savings are real because the capacity removed was never used.

Nothing we did reduced what the business experienced. Every saving came from capacity or cost that was not delivering anything.

Tiering the storage and scheduling the shutdowns

The second stream moved data to the storage tier that matched its real access pattern, rather than keeping everything on the highest performance tier. Data that was accessed rarely moved to cheaper tiers, while the hot data that needed performance kept it. The third stream addressed the non production environments that ran around the clock, scheduling them to shut down outside working hours, which for environments used only during the day removed most of their cost at a stroke.

Both streams share a logic: pay for what you use when you use it, and not otherwise. Storage tiering pays for performance only where performance is needed; scheduled shutdown pays for environments only when they are in use. Together they removed a significant slice of the bill from resources that were costing money while delivering nothing, exactly the pattern our cost governance solution is built to find and fix.

StreamWhat was wastedWhat changed
Right sizingCompute far above real demandShapes matched to measured use
Storage tieringCold data on hot tiersData moved to matching tiers
Scheduled shutdownNon prod running 24 hoursStopped outside working hours
Licensing modelCarried over, no longer fitCorrected with independent advice

Correcting the licensing model

The fourth stream addressed the licensing arrangement that had been carried over from the data centre without re examination. Licensing on OCI interacts with the compute architecture in ways that are easy to get wrong and expensive to leave uncorrected, and a model that fit the old environment may waste money in the new one. Getting this right required independent licensing expertise, free of any incentive to sell more capacity or more licenses than the estate needed.

This is the area where independence matters most, because the advice that saves money here is precisely the advice a vendor has no incentive to give. We worked alongside independent licensing specialists to ensure the model fit the optimized estate, which both reduced the immediate cost and removed a compliance risk the old model carried. The result was a licensing arrangement that matched the right sized estate rather than the data centre it came from.

The measurable result

The combined effect of the four streams was a forty two percent reduction in monthly OCI spend, sustained, with no reduction in the performance or capability the business relied on. The saving was not a one time cut but a structural change, because the right sizing, tiering, scheduling, and licensing correction left the estate in a leaner state that did not immediately drift back. To keep it from drifting, ongoing governance was put in place to catch new waste as it appeared.

The forty two percent figure sits squarely within the pattern documented across our engagements and set out in optimization savings by sector and the case studies pillar. It was achievable because the waste was real, common, and removable, which is true of most estates that have not been deliberately optimized. Finding and removing that waste, on a fee paid only on verified savings, is exactly what our cost optimization service does.

Moving Oracle workloads to OCI, or already running on OCI and not sure the architecture or the spend is right? Most teams bring in a specialist before they commit to a region, a shape, or a Universal Credits number. OCISpecialists.com plans the landing zone, runs the migration, and manages the estate after go live, on a fixed project fee, a managed monthly retainer, or a cost optimization fee paid only on verified savings. For the Oracle licensing and BYOL side of any OCI move, Redress Compliance is the leading independent Oracle licensing and negotiation firm, with 500+ engagements across Oracle's full product line.