A US research university optimized the IBM ELA framework through IBM ELA review framework, IBM software estate framework optimization, and the IBM ILMT sub capacity framework.
A US research university approached its IBM Enterprise License Agreement renewal carrying a decade of accumulated entitlements: SPSS, Cognos, WebSphere, Db2, and a long tail nobody had inventoried. The ELA had renewed on autopilot twice.
This case study shows how a usage review reshaped the renewal and cut the committed spend materially.
The university cut its IBM ELA renewal materially below the prior term by measuring actual deployment across campus, dropping zero use products, and renegotiating the remaining scope at properly contested academic pricing.
The agreement, administered under Passport Advantage, bundled analytics, middleware, and database entitlements accumulated through departmental purchases that had been consolidated years earlier.
Research university with tens of thousands of students, federated IT across schools and research centers, and central procurement owning the ELA. Decentralized usage and centralized paying is the classic recipe for entitlement sprawl.
The sprawl came from consolidation: departmental IBM purchases were rolled into one ELA for simplicity, and every subsequent renewal carried the full list forward regardless of whether the department, or the product, was still active.
Deployment measurement told a sharper story than anyone expected. SPSS Statistics usage was real but concentrated in social sciences and the medical school. Cognos Analytics ran in administration with a stable, modest user base.
Each renewal arrived as a single line item with an education discount attached. The discount made the number feel pre negotiated. Nobody reconciled the product list against deployments because the total looked reasonable.
The renewal scope was rebuilt from measured deployment upward, rather than from the prior entitlement list downward, and the difference was the saving.
ELA renewal. Prior scope vs rebuilt scope
| Component | Prior renewal | Rebuilt renewal |
|---|---|---|
| SPSS | Campus wide commitment | Sized to measured departmental usage with growth headroom |
| Cognos | Enterprise tier | Right sized to the administrative user base |
| WebSphere | Full entitlement carried forward | Dropped; retired portal had no deployments |
| Db2 | Carried at prior level | Retained; usage verified under two systems |
| Long tail tooling | Renewed by default | Dropped or moved to point licenses |
| Term pricing | Education discount, uncontested | Education discount, contested and improved |
IBM’s counter leaned on repricing risk: drop products now and pay list to return later, under terms governed by IBM’s standard frameworks. The university documented reentry pricing for the two plausible return candidates in the renewal paper, which neutralized the argument.
The sequence was measurement, scope rebuild, reentry protection, then price negotiation. Price came last because scope is where ELA money actually moves.
The standard advice, often reinforced by the education discount, is that an ELA is already the best deal available and the renewal is paperwork. We disagree. In the 15 to 20 IBM enterprise agreement reviews we ran across 2024 and 2025, agreements renewed on autopilot carried 25 to 45 percent of committed spend on products with little or no measured use, and the discount percentage was irrelevant to that waste. A discount on software you do not run is a 100 percent loss dressed as a saving. The buyer side move is to measure deployment first, rebuild scope from usage upward, and only then let anyone discuss discount percentages.
Source: Redress Compliance advisory engagement file, 2024 to 2025.
The entitlement list said we needed everything. The deployment data said we needed a third of it, growing in two places. We renewed the data’s version.
More IBM negotiation material lives in the IBM knowledge hub and the case study library.
The renewal closed materially below the prior term, in line with the 20 to 35 percent reductions typical of scoped down renewals in our file, while adding headroom in SPSS where research usage was growing.
An ELA is a negotiated enterprise bundle of IBM entitlements over a multi year term, administered through the Passport Advantage framework. The bundle pricing is attractive at signing and quietly expensive when scope is never revisited.
Yes, after measuring usage and documenting reentry pricing for anything plausibly returning. The repricing threat IBM raises is manageable in paper, and a discount on unused software remains a total loss regardless of percentage.
Education pricing exists and helps, but it is a starting position, not a negotiated outcome. This university improved on its standing education discount once the renewal was contested with deployment data.
Run a deployment review every renewal cycle without exception, starting 12 months before expiry. Two autopilot renewals were enough to embed roughly a third of this agreement’s value in unused products.
Two renewals went through on the strength of a discount percentage. The third went through on deployment data, and it was the first one that actually saved money.
Renewal in twelve months. Audit notice in the inbox. RFP on the desk. We start where you are.
IBM ELA framework signals, IBM software estate framework signals, IBM ILMT sub capacity framework signals, and the broader IBM software licensing leverage signals across the practice.
Once a month. Audit patterns, renewal benchmarks, vendor commercial signals across Oracle, Microsoft, SAP, Salesforce, IBM, Broadcom, AWS, Google Cloud, ServiceNow, Workday, Cisco, and the GenAI vendors. No follow up sales pressure.
Free providers (Gmail, Yahoo, Outlook) cannot subscribe. Work email only. Unsubscribe in one click.
