Processor Value Units sit at the heart of IBM software licensing. Read the buyer side guide to PVU math, sub capacity rules, the ILMT obligation, audit defense, and the PVU to VPC transition replacing the metric across the IBM portfolio.
PVUs are IBM Processor Value Units, the per core capacity unit on most IBM software. A typical core attracts 70 to 100 PVUs by processor type. Sub capacity rules cut the count for virtualized environments, but only with ILMT deployed and reporting on time. IBM is migrating most products to VPC over 2024 to 2027.
Pair this guide with the ILMT compliance guide, the PVU to VPC transition reference, and the IBM audit defense playbook before the next IBM licensing review.
The Processor Value Unit normalizes IBM software pricing across processor types. A POWER core, an x86 core, and a Z core each carry their own PVU rating. The total PVU count drives the license requirement.
| Processor family | Typical PVU per core | Common workloads |
|---|---|---|
| Intel Xeon, AMD EPYC | 70 PVUs | x86 virtualization, container hosts |
| IBM POWER9 and POWER10 | 120 PVUs | AIX, IBM i workloads |
| IBM Z and LinuxONE | 100 PVUs per IFL | Mainframe and Z Linux |
| ARM and Apple Silicon | 70 PVUs | Limited IBM workload support |
| Legacy SPARC | 120 PVUs | Legacy Solaris estates |
Sub capacity rules allow PVU counts to be measured at the virtual machine level rather than the physical host. The discount can be material. The qualification rule is strict.
If sub capacity qualification fails the auditor reverts to full capacity. The PVU count multiplies by host cores, not VM cores. A small ILMT gap on one product can lift the claim by 8 to 15 times the sub capacity number. The buyer side default is monthly ILMT health checks across the estate.
The IBM License Metric Tool is the customer side obligation for sub capacity. The tool is free but the operational discipline around it is the customer responsibility.
| Check | Cadence | Risk if missed |
|---|---|---|
| Agent deployment | On every new host | Full capacity on the host |
| Product catalog update | Monthly | Misclassified products |
| Report generation | Quarterly minimum | Loss of sub capacity rights |
| Bundling rule review | Quarterly | Wrong product allocation |
| Discovery scope | Quarterly | Shadow installs missed |
Five PVU mistakes appear across most enterprise estates. Each one is fixable inside a quarter.
IBM audits open with an ILMT data request. The data quality drives the audit outcome. The buyer side response brings clean ILMT data, documented bundling rules, and a deployment to entitlement reconciliation.
PVU is not the metric IBM wants to discuss in 2026. VPC is. The renewal cycle now writes the conversion. Get the PVU baseline right before the conversion math begins.
IBM is converting most products from PVU to Virtual Processor Core, or VPC, between 2024 and 2027. VPC measures cores directly, removing the per processor multiplier. The conversion is the lever for clean up.
| Product line | Conversion status | Defended position |
|---|---|---|
| WebSphere Application Server | VPC available, PVU retained for legacy | Convert on renewal, exclude shelfware |
| DB2 family | VPC available across most editions | Convert and rebaseline named user counts |
| MQ and Integration | Mixed VPC and PVU | Map product by product |
| Tivoli and Maximo | VPC and per asset models | Pick the model with the lowest TCO |
| Red Hat OpenShift | Core based subscription | Separate metric, stack with PVU products |
The eight step checklist below moves a PVU estate from organic state to clean baseline and into the VPC conversion conversation.
Many products do, but not all. Some IBM products use named user, authorized user, RVU, or per server metrics. The PVU model covers most IBM Software Group products that run on processors. The full metric map sits in the IBM passport advantage product catalog. The buyer side review confirms the metric on every product before counting.
IBM contracts allow a grace period in some cases but the default audit position is full capacity for the lapsed period. The financial exposure can be eight to fifteen times the sub capacity number on the affected products. Recovery requires ILMT redeployment with retroactive reports, which is sometimes accepted by IBM auditors and sometimes not.
Most enterprises do, on the next renewal cycle. The VPC metric is simpler to track and aligns better with virtualized estates. The defended position picks the conversion that lowers TCO product by product. Some products on stable POWER hosts may benefit from staying on PVU for one more renewal cycle.
PVU rates are set centrally by IBM. The negotiation lever sits in the PVU quantity rather than the rate. Sub capacity application, deployment reduction, and shelfware drops are the available levers. A PVU to VPC conversion can also reset the pricing baseline on the converted product.
Most enterprises will during the transition years. The two metrics track separately. ILMT continues to manage the PVU products. The VPC products track outside ILMT, usually inside the customer SAM tool. The buyer side framework runs both reports monthly and reconciles at renewal time.
OpenShift uses its own subscription metric. ILMT may discover OpenShift but the licensing is a Red Hat core based subscription separate from the IBM passport advantage products. Customers running stacked IBM and OpenShift products track each metric independently. The renewal conversation usually covers both in parallel.
Redress runs IBM PVU reviews as a focused engagement before every passport advantage renewal or audit. The work covers ILMT health, entitlement reconciliation, shelfware identification, audit defense, and the PVU to VPC conversion plan. Most engagements deliver the first 10 to 20 percent inside three months.
Read the related Vendor Shield, Renewal Program, Benchmark Program, Software Spend Assessment, Benchmarking framework, about us, management team, locations, and contact pages.
A buyer side framework for ILMT compliance, the PVU baseline, and the VPC transition. Includes the ILMT health check template, the entitlement reconciliation worksheet, the bundle interpretation guide, and the PVU to VPC conversion map used across hundreds of IBM engagements.
Independent. Buyer side. Built for CIOs and procurement leads carrying IBM software estates or facing an IBM audit. No vendor influence. No sales kickback.
Open the white paper in your browser. Corporate email only.
Open the Paper →The IBM audit opened with an ILMT data request. We ran a pre audit health check, fixed three agent gaps, and reconciled entitlement to deployment. The full capacity exposure dropped from twelve million to under two before settlement.
We have run 500+ enterprise clients across 11 publishers. Every engagement starts with one conversation.
ILMT enforcement patterns, PVU to VPC conversion movement, passport advantage renewal data, IBM audit triggers, shelfware reduction tactics, and the wider IBM commercial leverage signals across every engagement.
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.
