IBM License Models Explained: PVU, VPC

IBM licenses many products through the Processor Value Unit metric inherited from the mainframe era. Newer cloud delivered products use Virtual Processor Cores. Resource Value Units cover seat or workload metered products. The Enterprise License Agreement layers an unlimited deployment commit on top.

Each metric carries a different audit posture. The PVU model relies on the IBM License Metric Tool. The VPC model uses container metering. The ELA carries certification risk at the term end.

Read this article alongside the IBM Audit Defense Kit, the IBM knowledge hub, the IBM advisory practice, and the Vendor Shield subscription.

Key Takeaways

What a CIO and head of procurement need to know in 90 seconds

PVU is the legacy metric. Processor Value Units weight each core by a published value. Sub capacity rules require ILMT.
VPC is the cloud metric. One Virtual Processor Core licenses one container vCPU.
RVU covers workload metered products. Resource Value Units count seats, instances, or transaction volume.
ELA layers an unlimited commit. Often three years, with a certification motion at the end.
ILMT is mandatory for sub capacity. No ILMT means full capacity licensing at audit.
IBM Passport Advantage is the contract vehicle. Most order forms reference Passport Advantage terms.
Eight specific levers move every IBM deal. Read each before signing the renewal.

Processor Value Unit metric

The PVU metric is the oldest live IBM license model. Each physical core carries a PVU weight published by IBM. The PVU weight depends on the CPU family.

PVU weights by CPU family

CPU family	Typical PVU per core	Common products
Intel Xeon scalable	70	WebSphere, MQ, Db2
AMD EPYC	70	WebSphere, MQ, Db2
IBM Power 9 and Power 10	120	Db2, WebSphere on Power
IBM z mainframe	Separate metric (MIPS or MSU)	CICS, IMS, Db2 for z

Sub capacity versus full capacity

Sub capacity licensing counts only the cores allocated to the IBM workload, not the entire physical host. Sub capacity requires ILMT data with quarterly reporting.

Full capacity counts every core on the physical host. The default if ILMT data is missing or stale.

Virtual Processor Core metric

The VPC metric is IBM's modern container metric. One VPC licenses one container vCPU. The model is simpler than PVU.

Where VPC applies

Cloud Pak for Data. Data and AI workloads on Red Hat OpenShift.
Cloud Pak for Integration. MQ, App Connect, API Connect on OpenShift.
Cloud Pak for Business Automation. BAW, ODM, BPM on OpenShift.
Cloud Pak for Security. QRadar and Guardium on OpenShift.
Cloud Pak for Watson AIOps. Operational intelligence on OpenShift.

PVU to VPC conversion

The Cloud Pak migration converts PVU based products into VPC entitlements. The conversion ratio depends on the source product and the target Cloud Pak.

Source product	Typical PVU to VPC ratio	Notes
WebSphere Application Server	70 PVU per 1 VPC	Cloud Pak for Apps
MQ Advanced	70 PVU per 1 VPC	Cloud Pak for Integration
Db2 Advanced	70 PVU per 1 VPC	Cloud Pak for Data
API Connect	120 PVU per 1 VPC	Cloud Pak for Integration

Resource Value Unit metric

RVU covers products that count something other than processor cores. The unit may be users, agents, transactions, or storage volume.

Common RVU products

Tivoli Asset Management. Per asset or per user RVU.
QRadar SIEM. Per Events Per Second RVU.
Maximo Application Suite. Per user or per asset RVU.
Watson Discovery. Per document RVU.
Sterling B2B Integrator. Per partner connection RVU.

Enterprise License Agreement and IULA

The IBM Enterprise License Agreement provides unlimited deployment rights for a defined product list across a defined term. The ELA carries a certification motion at the end.

ELA mechanics

Term length. Three years is standard. Five year terms appear on larger commits.
Product list. A defined set of IBM products gets unlimited deployment.
Certification. At term end the customer certifies the deployed quantity. The number becomes the forward license count.
Conversion right. The certified quantity can convert to Cloud Pak VPC entitlements.

IULA differences

Vehicle	Term	Renewal posture	Best fit
ELA	3 to 5 years	Certify then renew	Growing IBM estate
IULA	Perpetual	Maintenance renews annually	Mature IBM estate
Passport Advantage transactional	1 year subscription	Annual renew	Stable workloads

ILMT compliance and audit posture

The IBM License Metric Tool is mandatory for sub capacity licensing. Without ILMT the audit defaults to full capacity counting.

ILMT requirements

Deployment within ninety days. Of installing the first PVU based product.
Quarterly data uploads. The ILMT report must be retained.
Two years of history. ILMT data must cover the past two years.
Scan accuracy. The ILMT scan must capture all virtualized hosts running IBM software.
BigFix integration. ILMT relies on BigFix for endpoint data collection.

ILMT gaps are the most expensive avoidable cost on an IBM audit

The most common audit finding is missing or stale ILMT data. Without compliant ILMT reports, IBM converts the sub capacity licensing to full capacity at the audit. The resulting bill often runs into seven figures on a mid sized IBM estate. The buyer side response is a quarterly internal ILMT review with documented evidence.

Eight negotiation levers on IBM

The buyer side has eight specific levers across the IBM negotiation. Each maps to one cost line or one risk line.

Eight levers worth pursuing

Lock ILMT compliance. Run quarterly internal reviews to prevent full capacity defaults.
Right size the ELA. Match the product list to actual deployment plans.
Plan the certification. Build a quarterly deployment roadmap to control certification volume.
Convert to Cloud Paks where it fits. Negotiate the PVU to VPC ratio.
Cap the renewal escalator. Hold at two to four percent.
Insert a divestiture clause. Reduce on business unit divestiture.
Lock the audit posture. Define the measurement method and frequency.
Document the exit posture. Data egress, transition support, and a published off ramp.

Typical savings ranges

Lever	Cost line	Typical saving	Effort
ILMT compliance	Audit exposure	Significant	Medium
Right size ELA	ELA fee	10 to 20 percent	Medium
Cloud Pak conversion	Maintenance line	15 to 30 percent	High
Cap escalator	Term cost line	10 to 15 percent	Medium
Audit posture lock	Audit defense	Significant	Low

IBM licensing reads as a metric exercise. The cost line moves with ILMT discipline, the ELA scope, the Cloud Pak conversion ratio, and the renewal posture. Each is negotiable before the next certification motion.

What to do next

The eight step checklist is the buyer side starting position on every IBM renewal or certification.

Audit ILMT health. Confirm quarterly reports for the past two years.
Map the metric mix. PVU, VPC, RVU, and ELA counts.
Score the Cloud Pak conversion. Compare PVU spend against VPC equivalent.
Plan the certification. Quarterly deployment review against the ELA scope.
Cap the renewal escalator. Hold at two to four percent.
Lock the audit posture. Define the measurement method and frequency.
Insert divestiture protection. Reduce on business unit sale.
Document the exit posture. Data egress and transition support.

Frequently asked questions

What is the difference between PVU and VPC?

PVU is the legacy Processor Value Unit metric that weights each core by a published value depending on the CPU family. VPC is the modern Virtual Processor Core metric that licenses one container vCPU as one VPC. Most new Cloud Pak products use VPC. Many traditional IBM products still use PVU.

Is ILMT mandatory?

Yes for sub capacity licensing. The IBM License Metric Tool must be deployed within ninety days of installing the first PVU based product, with quarterly reports retained for two years. Without compliant ILMT data, IBM defaults audits to full capacity counting.

What is an IBM ELA?

An Enterprise License Agreement provides unlimited deployment rights for a defined product list across a defined term, typically three to five years. At term end the customer certifies the deployed quantity, which becomes the forward license count. The ELA carries a certification motion that drives the renewal posture.

What is the PVU to VPC conversion ratio?

The ratio depends on the source product and the target Cloud Pak. Typical ratios sit at 70 PVU per VPC for WebSphere, MQ Advanced, and Db2 Advanced. API Connect carries 120 PVU per VPC. The ratio is negotiable on larger deals.

Does IBM still sell perpetual licenses?

Yes through the IULA vehicle. IULAs grant perpetual unlimited deployment with annual maintenance. New IBM acquisitions increasingly push toward subscription or Cloud Pak VPC models. The choice between perpetual and subscription depends on the maturity of the estate.

How does Redress engage on IBM negotiations?

Redress runs IBM engagements inside Vendor Shield, the Renewal Program, the Benchmark Program, and the Software Spend Assessment. The work covers ILMT health checks, ELA right sizing, Cloud Pak conversion math, and the audit posture. Always buyer side, never IBM paid.

How Redress engages on IBM

Redress runs IBM licensing reviews inside the Vendor Shield subscription, the Renewal Program, the Benchmark Program, and the Software Spend Assessment. Every engagement is led by a former IBM commercial executive on the buyer side.

Read the related benchmarking, about us, locations, and contact pages.

Vendor Advisory

Cloud & Emerging

Programs

Assessments

Research

Knowledge Hubs

Assessment Tools

IBM License Models. PVU, VPC, RVU, ULA Explained.