IBM licensing experts are independent, buyer-side advisors who control your IBM cost and compliance risk. We validate PVU and RVU counts, confirm sub-capacity eligibility and ILMT reporting, strip shelfware out of Passport Advantage, and negotiate renewals on your side. This page sets out what we do and how the engagement runs.
Last reviewed 6 June 2026 by the Atonement Licensing IBM practice.
Most IBM overspend traces back to four things: metrics counted on full capacity when sub-capacity applies, ILMT deployed late or reporting incorrectly, shelfware carried renewal after renewal, and Cloud Pak bundling that buyers accept without modelling. We fix all four. Our advisors represent buyers exclusively, work on fixed fees, and have negotiated more than $2.4B in enterprise software contracts.
Talk to an IBM licensing expertMetric validation, sub-capacity and ILMT compliance, and Passport Advantage renewal negotiation, all from the buyer's side.
We reconcile your deployed IBM estate against your Passport Advantage entitlements. We validate PVU and RVU counts, check Authorized User and Resource Value Unit metrics, and find the gap that an IBM audit would otherwise surface first.
We confirm you qualify for sub-capacity, that ILMT is deployed correctly, and that reports are generated and retained on the schedule the Passport Advantage terms require. This is the single biggest driver of IBM compliance findings.
We benchmark your renewal, remove shelfware, model Cloud Pak conversions, and resist unjustified uplifts. Buyers without representation routinely accept the first number IBM presents, which is exactly where money leaks.
A controlled, four-stage engagement that gives you a defensible IBM position and a lower total cost.
We map every IBM product you run against your Passport Advantage Proof of Entitlement records. We document deployment, virtualisation and the metric attached to each part number, so the picture is complete before any decision is made.
We test your sub-capacity eligibility and ILMT reporting, model full-capacity exposure where the conditions are not met, and quantify the risk in money. You see where you stand before IBM ever asks. Read our breakdown of full versus sub-capacity licensing.
We strip out shelfware, right-size metric counts, and benchmark your pricing against what comparable enterprises pay. We model Cloud Pak bundling so you know the real cost of consolidation rather than IBM's headline.
We negotiate the Passport Advantage renewal or new purchase on your behalf, holding the line on price, metrics and terms. Where an audit is open, the same work becomes your IBM audit defense.
A Processor Value Unit, or PVU, is IBM's per-core licensing metric. Every processor core carries a PVU rating set by IBM's published PVU table, which keys off the processor brand and model. You license the total PVUs the software is eligible to run on, so the count depends directly on which cores the workload can reach. Reading the table wrong, or licensing every physical core when only a subset runs the software, is one of the most common and most expensive IBM errors.
Resource Value Units, or RVUs, apply to products priced on a resource the software manages rather than the processor it runs on, such as managed servers, users or terabytes. RVU tiers step down in price as volume rises, so the count and the tier both matter. We validate which metric applies to each part number, confirm the count, and check that the tier you are charged at matches the volume you actually hold. For the detail, see our guides to IBM PVU licensing and the wider IBM licensing guide.
Sub-capacity is where the largest IBM savings and the largest audit risks sit at the same time.
Full capacity licenses every physical core in a server. Sub-capacity lets you license only the virtual cores assigned to the IBM software, which is far cheaper on large hosts. Sub-capacity is available only on approved virtualisation technologies and only when you meet the reporting conditions.
Under the IBM Passport Advantage sub-capacity terms, the IBM License Metric Tool must be installed within 90 days of first eligible deployment, generate reports at least quarterly, and retain those reports for two years. Miss any of these and IBM can charge for full physical capacity.
ILMT installed late, bundle data not reconciled, or reports never reviewed. We fix the configuration, validate the output, and keep the evidence audit-ready. See our notes on ILMT and sub-capacity licensing.
The commercial layer where price, metrics and Cloud Pak bundling are decided.
Passport Advantage is IBM's volume licensing programme, and the Subscription and Support line on it renews every year. That recurring fee is where most negotiable money sits. IBM applies uplifts, carries shelfware forward, and presents Cloud Pak bundles as a simplification when the real question is whether the bundle costs less than the parts you actually use.
We benchmark the renewal against comparable deals, challenge uplifts, and model every Cloud Pak conversion against your real consumption before you commit. Bundling can lower cost or quietly raise the floor for the next renewal, and the difference is only visible if you model it. Our clients see 38% average savings across engagements, and we hold the line on the terms that protect the next cycle. For the playbook, read our guide to IBM Passport Advantage, the common IBM bundling traps, and our IBM renewal strategy. The IBM negotiation playbook sets out the tactics in full.
Request an independent IBM reviewIBM exposure rarely spreads evenly. It clusters in a handful of product families where the metric is complex, the deployment is virtualised, or the bundle terms are easy to misread. Db2 and the data platform are usually priced on PVUs with heavy sub-capacity exposure. WebSphere Application Server, including Network Deployment, carries the same PVU pattern across clustered and containerised estates. MQ and the integration stack are frequently over-deployed in non-production. Cognos and the analytics tools mix Authorized User and PVU metrics that are simple to count wrong.
Cloud Paks add another layer, because they convert legacy part numbers into Virtual Processor Core entitlements that you can spend flexibly across the bundle. That flexibility is useful, but it also changes how usage is measured and reported, and it resets the baseline for your next renewal. We review each family against your entitlements, flag the parts most likely to draw an audit, and document the position so it holds. For the detail, see our guides to Db2 licensing, WebSphere licensing, MQ licensing, Cloud Pak licensing, and the audiaudit triggers guide.
Continue across our IBM advisory practice and research.
Independent, buyer-side advice. We respond within one business day.
Weekly vendor licensing and negotiation intelligence for enterprise buyers.