IBM Practice
IBM License Models. PVU, RVU, and the cost levers.
IBM sells the same product several ways. Read the PVU and RVU metrics, the sub capacity rules, and the renewal levers before you sign the next true up.
IBM sells the same product several ways. Read the PVU and RVU metrics, the sub capacity rules, and the renewal levers before you sign the next true up.
IBM prices software through a handful of metrics that look interchangeable and are not, and the renewal quote rarely tells you which one is cheaper for your estate.
IBM measures most software by capacity, not by people. The two metrics you meet most often are Processor Value Unit and Resource Value Unit. Both scale with usage, but they count very different things.
PVU is a points value assigned to each processor core. The points depend on the chip type, so the same core count can carry a different PVU total on different hardware. RVU counts a managed resource, such as a server, a user, or a terabyte, depending on the product.
IBM publishes the current metric definitions in its Passport Advantage PVU licensing terms, and the points values sit in IBM's PVU points table.
You take the core count, multiply by the PVU rating for that processor, and license the total. A 16 core server at 70 PVU per core needs 1,120 PVU. The rating is the variable buyers forget, and it moves the number more than the core count does.
RVU prices by a resource the product manages. The catch is that the resource count can grow silently as the platform spreads, so an RVU bill can climb without any new purchase order. Track the managed resource the same way you track headcount on a user metric.
IBM license metrics at a glance
| Metric | Counts | Best fit | Audit risk |
|---|---|---|---|
| Processor Value Unit | Cores times chip rating | Middleware on dedicated hardware | High without ILMT |
| Resource Value Unit | A managed resource | Tools that scale by usage | Medium, count creeps |
| Authorized User Single Install | Named person, one install | Small fixed populations | Low |
| Concurrent User | Simultaneous sessions | Shared, low concurrency tools | Low |
Sub capacity is the rule that lets you license only the cores assigned to a workload rather than every core in the box. It is the single largest cost control on a virtualized IBM estate, and it depends entirely on tooling.
IBM requires the IBM License Metric Tool to be installed and producing quarterly reports. Without those reports, IBM is entitled to measure full physical capacity, which on a large cluster can be several times your real usage.
The benefit is lost not by overuse but by paperwork. A lapsed agent, an unpatched server, or a missed quarterly report converts a clean sub capacity position into a full capacity exposure. Treat ILMT as a compliance system, not an optional add on.
The metric sets the count. The buy model sets how you pay for it. IBM offers perpetual licenses with annual support, fixed term licenses, and consumption style arrangements through cloud and Cloud Pak packaging.
IBM details the container based packaging on its Cloud Paks product page, and the standard terms sit in the Passport Advantage agreements. Price every path across a full five years before you let a discount on year one decide the model.
The standard IBM seller pitch is that moving everything to Cloud Pak entitlements simplifies licensing and saves money. We disagree. In roughly two thirds of the estates we benchmarked in 2024 and 2025, the platform move raised five year cost once the conversion ratio and the unused container capabilities were priced honestly. The buyer side move is to map each workload to its cheapest metric first, fix the sub capacity reporting, and only then test whether a Cloud Pak conversion beats the metric you already hold. Simplicity on a slide is not the same as a lower invoice.
Source: Redress Compliance advisory engagement file, 2024 to 2025.
On an IBM estate the cheapest license is the one that matches the metric to how the workload is actually consumed, not the one the account team quoted first.
The renewal is where you recover the stranded capacity. Bring a current ILMT report, a decommissioning log, and a costed comparison of the metrics. IBM negotiates against evidence, not assertions.
IBM often raises measurement questions in the quarter before a renewal. Keep ILMT current, keep deployment records, and answer in writing. A defensible position turns audit pressure into a routine renewal.
For hands on help mapping these models to your estate, independent IBM licensing experts run entitlement reviews, PVU baselines, and renewal positioning.
PVU licensing multiplies the core count by a points rating set for the processor type, then licenses the total. Headcount is irrelevant, so the chip rating and the virtualization design drive the number more than anything else, and confirming the rating for your exact processor is the first check.
PVU counts processor cores times a chip rating, so it scales with hardware. RVU counts a managed resource such as servers, users, or terabytes, so it scales with usage independently of hardware. The two are not interchangeable, and the cheaper one depends on how the specific product is consumed.
Yes, if you license any product on a sub capacity basis. Without current ILMT reports IBM is entitled to measure full physical capacity, which on a virtualized cluster can be several times your real usage and turns a routine renewal into a large true up.
Sub capacity is the rule that lets you license only the cores assigned to a workload rather than every core in the server. It is the largest single cost control on a virtualized IBM estate, but it depends on continuous, compliant ILMT reporting to hold.
Perpetual plus support carries the highest year one cost and the lowest five year cost for stable, fully deployed estates. Fixed term is cheaper to enter and more expensive over five years, so it fits projects with a defined end date. Always model both across five years.
In our 2024 to 2025 reviews, stranded capacity and unused entitlements ran 20 to 40 percent of the renewal value. Most of it came from capacity sized for a historical peak, or tied to hardware that had since been decommissioned or virtualized away.
Yes. You can reconcile entitlements to live, in use capacity and drop the difference at renewal, provided you bring a current ILMT report and a decommissioning log as evidence. IBM negotiates against documented usage, not against assertions.
Keep ILMT reports current, retain deployment and decommissioning records, and answer every measurement request in writing. A defensible sub capacity position converts audit pressure into a routine renewal rather than a full capacity true up event.
The metric map, the sub capacity rules, the ILMT obligations, and the renewal levers that cut an over provisioned IBM estate.
Used across more than five hundred enterprise engagements. Independent. Buyer side. Built for procurement leaders running the next renewal cycle.
