IBM software is priced on a small set of metrics that behave very differently from one another. The bill is decided by which metric applies, whether sub capacity is in force, and whether ILMT is reporting cleanly.
IBM licensing in 2026 turns on four metrics, the sub capacity rules that cap them, and the License Metric Tool that proves your counts. Get those right and the rest follows.
IBM licensing looks complex because the metrics differ so much. In practice the bill turns on a few decisions. Which metric applies. Whether sub capacity is active. Whether ILMT proves your counts.
Get those three right and IBM becomes manageable. Get them wrong and an audit defaults to the worst case. This guide walks the metrics and the buyer side moves.
IBM licenses through Passport Advantage, its volume program. Most products map to one of four metrics, and the metric decides how you count.
The IBM Passport Advantage program publishes the agreements and metric definitions that govern each product.
IBM metrics, how you count, and the main risk (2026)
| Metric | Used for | How you count | Main buyer risk |
|---|---|---|---|
| PVU | WebSphere, MQ, middleware | Cores times value unit factor | Full capacity without ILMT |
| RVU | Management and analytics | Per managed resource | Resource growth over time |
| VPC | Cloud Paks | Virtual cores times ratio | Paying for unused bundle breadth |
| Authorized user | User facing tools | Per named person | Counting dormant accounts |
Under full capacity, PVU licensing counts every physical core the software could run on. In a virtualized estate that number is brutal. Sub capacity licensing fixes it by counting only the virtual cores allocated.
The catch is evidence. IBM grants sub capacity only where the License Metric Tool is deployed and producing reports. The License Metric Tool documentation sets the deployment and reporting duties.
If ILMT is missing on a server, IBM can default that server to full capacity. A small coverage gap can swing a finding by hundreds of cores. ILMT hygiene is the single highest leverage control in the IBM estate.
Cloud Paks license on virtual processor cores. Each Cloud Pak bundles a set of entitled programs, and a VPC ratio converts the underlying products into the Cloud Pak metric.
The benefit is flexibility across the bundled products. The risk is assuming the bundle is cheaper by default. IBM publishes the Cloud Pak entitlements, and the buyer move is to check whether you will use the bundle breadth before paying for it.
An IBM Enterprise License Agreement trades discount for commitment. It can be the right structure, but it locks scope. The buyer move is to enter with a clean deployment baseline, not the vendor estimate.
Lead with shelfware removal. IBM estates carry middleware that has not run in production for years. Cutting it before renewal lowers the base the discount applies to. Discount on shelfware is still spend on shelfware.
IBM also offers enterprise agreement structures that pool entitlements. Read the true up terms carefully. A flexible looking ELA can carry a costly annual reconciliation.
The standard advice is to chase a bigger discount and roll the estate into an ELA at renewal. We disagree. In roughly 6 of 10 IBM estates we reviewed, the larger number was not the discount, it was the shelfware and the full capacity exposure from ILMT gaps. An ELA negotiated on a bloated baseline simply locks in a discounted version of overspend. The buyer side move is to fix ILMT coverage, remove undeployed middleware, and rebaseline the estate before any discount conversation. Discount applied to a clean footprint beats a deeper discount applied to a number you should never have been paying.
Source: Redress Compliance advisory engagement file, 2024 to 2025.
In an IBM estate the discount rate is rarely the biggest number. The biggest number is the capacity you are licensing but never use.
IBM prices most software on four metrics: processor value unit, resource value unit, virtual processor core, and authorized or concurrent user. The metric that applies to a product decides how you count and how the bill scales.
PVU stands for processor value unit. IBM assigns a value unit factor to each processor type, and you multiply cores by that factor. Without sub capacity, PVU counts every core the software could run on.
Sub capacity lets you license only the virtual cores allocated to a workload rather than all physical cores. IBM grants it only where the License Metric Tool is deployed and producing regular reports.
The License Metric Tool is your evidence for sub capacity. If ILMT is missing or not reporting on a server, IBM can default that server to full capacity counts, which sharply increases a finding.
Cloud Paks license on virtual processor cores. Each Cloud Pak bundles entitled programs, and a published ratio converts those programs into the VPC metric counted against the workloads that run them.
An IBM Enterprise License Agreement trades a deeper discount for a committed scope. It can simplify buying, but it locks the estate and often carries an annual true up that needs careful forecasting.
Most IBM overspend comes from full capacity exposure due to ILMT gaps and from middleware that is owned but never deployed. Both are fixable before a renewal without negotiating a single point of discount.
Confirm ILMT coverage on every server, reconcile your deployments against entitlements, and remove undeployed products. Walk in with a defensible deployment baseline rather than relying on the vendor estimate.
IBM Passport Advantage metrics, sub capacity posture, ILMT readiness, ELA exit moves, 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.
We sit on your side when you negotiate with the major software publishers. Independent, benchmarked, and built for the renewal in front of you.
Contact Us