A global retailer believed its IBM estate was clean. An independent review found 4.8 million dollars a year of avoidable spend in sub capacity, idle entitlements, and an ELA that no longer fit.
A global retailer ran a quiet IBM review expecting a clean bill. The review surfaced 4.8 million dollars a year of avoidable spend across sub capacity, idle entitlements, and a stale ELA. This case study shows where it hid and how the buyer reclaimed it.
The retailer ran a large IBM estate across stores, distribution, and head office. It included middleware, database, and analytics products, most under sub capacity licensing.
The team believed the estate was clean. ILMT was installed, the ELA was current, and renewals had run without dispute for years.
Because nothing had gone wrong, no one had looked closely. A quiet estate is not the same as an optimized one.
The review covered deployment data, ILMT reports, the ELA schedule, and every Passport Advantage entitlement under support.
The gap between entitlement and need was large. Three findings drove most of the 4.8 million dollar figure.
ILMT was installed but misconfigured. Several servers were not captured, so IBM License Metric Tool reporting defaulted to full capacity. The retailer paid for cores it never used.
The Passport Advantage ELA bundled products retired during a prior platform consolidation. Support kept billing on software no one ran.
Where the 4.8 million dollar saving came from
| Finding | Root cause | Annual saving |
|---|---|---|
| Sub capacity at full capacity | ILMT misconfigured | About 2.9 million dollars |
| Stale ELA bundle | No fresh baseline at renewal | About 1.1 million dollars |
| Idle entitlements | Autopilot renewals | About 0.8 million dollars |
| Total | Independent review | About 4.8 million dollars |
No new software was purchased. Every dollar came from correcting what the retailer already owned and paid for.
The team rescoped ILMT to capture every relevant server and validated the reports against deployment. The sub capacity position then held.
At renewal, the retailer removed retired products and resized the bundle to actual need, using the deployment baseline and IBM software catalog as evidence.
The retailer reduced annual IBM spend by 4.8 million dollars without losing a single capability it relied on. The review paid for itself many times over in the first year.
Because the fix was structural, the saving carried into future years. The retailer also adopted a recurring review so the estate would not drift again, consistent with current IBM software licensing obligations.
A quiet estate hides cost as easily as a noisy one. The only way to know is to review entitlement, deployment, and configuration together.
The common advice is that deploying ILMT is enough to secure sub capacity pricing, so once it is installed the estate is safe. We disagree. In the retailer's case, ILMT was installed but misconfigured, and IBM was within its rights to bill at full capacity for the cores it could not see. The buyer side move is to validate that ILMT is correctly scoped, current, and capturing every relevant server, then prove the sub capacity position with clean reports. An installed tool is not a compliant position. The configuration is what counts.
Source: Redress Compliance advisory engagement file, 2024 to 2025.
The retailer did not overspend because it bought too much. It overspent because it never checked that what it owned was configured to bill correctly.
White Paper · IBM
Cut Your IBM ELA Renewal: 8 Buyer Side Levers
Eight buyer side levers that cut an IBM ELA renewal: the baseline reset, true forward exposure, product rationalization, and the Cloud Pak shift. Read it free.
An independent IBM license review found avoidable spend across misconfigured sub capacity, a stale ELA, and idle entitlements. Correcting what the retailer already owned cut annual spend by about 4.8 million dollars without buying any new software.
Sub capacity licensing lets you license IBM software for the virtual cores a product uses rather than the full physical capacity of the host. It requires the IBM License Metric Tool to be deployed and correctly configured to prove the position.
The IBM License Metric Tool was installed but misconfigured, so several servers were not captured. Without complete reporting, sub capacity products defaulted to full capacity billing, and the retailer paid for cores it never used.
An IBM Enterprise License Agreement bundles a set of products and entitlements under negotiated terms for a period. Without a fresh deployment baseline at renewal, an ELA can keep billing for products the business has already retired.
Yes. In this case every dollar of the 4.8 million dollar saving came from correcting existing entitlements, fixing configuration, and removing retired products, with no new software purchased at all.
At least annually, and always before a renewal. A quiet estate drifts as servers move and products retire, so a recurring review of entitlement, deployment, and configuration keeps the position clean.
No. The tool must be correctly scoped, current, and capturing every relevant server. An installed but misconfigured tool does not secure the sub capacity position, as this retailer discovered.
Start at least 270 days before a renewal. That gives time to validate ILMT, reconcile deployment, rebalance the ELA, and bring an evidence based position to the negotiation.
IBM ELA strategy, Passport Advantage benchmarks, sub capacity posture, and the buyer side moves across the IBM software estate.
Used across more than five hundred enterprise engagements. Independent. Buyer side. Built for procurement leaders running the next renewal cycle.
The most common IBM saving is not a discount. It is the money already leaking through misconfigured sub capacity, stale ELAs, and idle entitlements. Find it before the next renewal locks it in.
