IBM Licensing Guide 2026. PVU, RVU, VPC, MSU.

IBM software runs on eight active license metrics. PVU and VPC dominate WebSphere, MQ, Db2, and Cognos. RVU covers IBM Maximo and IBM TRIRIGA. MSU runs the z16 mainframe. Authorized User, Concurrent User, Resource Value Unit, and Floating User cover the legacy stack. Every metric exposes a different audit posture and a different renewal lever.

The 2026 renewal math turns on three questions. Is the ILMT report accurate and current for sub capacity licensed products? Does the ELA wrap the metric mix at the right unit, or does per product licensing clear deeper discount? And does the renewal carry a true forward or true up clause that converts headroom into a billing event?

Read this alongside the IBM knowledge hub, the IBM license models page, the sub capacity and ILMT compliance guide, the audit defense playbook, and the Vendor Shield subscription.

The eight active IBM license metrics in 2026

Every IBM software line maps to one of eight metrics. Recognizing the metric is the precondition for negotiating the unit and managing the audit posture.

Metric by metric overview

Metric	What it counts	Typical product fit	Audit risk
PVU (Processor Value Unit)	Weighted physical or virtual processor cores	WebSphere, MQ, Db2, Cognos	High. ILMT mandated for sub capacity.
VPC (Virtual Processor Core)	Virtual processor cores	Cloud Pak family, modern middleware	Medium. Simpler than PVU.
RVU (Resource Value Unit)	Managed assets, transactions, units	Maximo, TRIRIGA, Tivoli Storage	Medium. Volume metric.
MSU (Million Service Units)	Mainframe processing capacity	z/OS, CICS, IMS, Db2 z/OS	Medium. SCRT reporting required.
Authorized User	Named user with right to access	Legacy Notes, Rational, Cognos AU	Low. Static metric.
Concurrent User	Simultaneous user count	Legacy applications	Low. Static metric.
Floating User	Pool of named users with rotating use	Rational, Engineering Lifecycle	Low. Pool tracking.
Resource Value Unit (RVU MAPC)	Managed asset, processor, or core	Tivoli, IBM Storage	Medium. Asset count.

Three rules that govern every IBM metric

• Metric mix drives the discount. IBM gives a deeper discount on the metric where the buyer has scale, not across every line equally.
• ILMT is mandatory. Sub capacity PVU licensing without a current ILMT report defaults to full capacity, often 3 to 5 times the cost.
• True up is annual. IBM ELA paper carries an annual true up clause that converts growth into a billing event at the contract unit.

PVU and sub capacity licensing

Processor Value Unit is the IBM legacy metric on WebSphere, MQ, Db2, and Cognos. The metric weights physical or virtual processor cores by chip family, with values ranging from 30 to 120 PVU per core.

PVU weight by chip family

Chip family	PVU per core	Common workload
Intel x86 modern	70	WebSphere, MQ, Db2 on Intel
AMD EPYC modern	70	WebSphere, MQ, Db2 on AMD
IBM Power9 and Power10	120	WebSphere on AIX, Db2 on Power
IBM Z (zIIP, ICF)	120	Mainframe specialty engine
ARM Neoverse	30	Cloud Pak on Graviton or Ampere

Sub capacity rules that matter

• ILMT installed and reporting. The IBM License Metric Tool must run on every cluster and report quarterly.
• Two quarter retention. ILMT reports must be retained for two quarters minimum to demonstrate compliance during an audit.
• Full capacity default. Without ILMT, the sub capacity rule falls back to full capacity licensing on every physical core in the cluster.

RVU and consumption metrics

Resource Value Unit prices Maximo, TRIRIGA, Tivoli Storage Manager, and a portion of the IBM Storage software stack. The metric counts managed assets or transactions, not users or cores.

RVU examples

• Maximo RVU. One RVU per asset managed. 5,000 assets is 5,000 RVUs.
• TRIRIGA RVU. One RVU per square metre managed. A 500,000 square metre portfolio is 500,000 RVUs.
• Tivoli Storage Manager RVU. One RVU per Terabyte managed under backup.

VPC and virtual processor core

Virtual Processor Core is the new IBM default on Cloud Pak for Applications, Cloud Pak for Data, Cloud Pak for Integration, and the modern middleware stack. The metric counts virtual processor cores, with a 1:1 mapping to vCPU on most cloud platforms.

VPC versus PVU side by side

Aspect	PVU	VPC
Metric base	Weighted core	Virtual core
ILMT requirement	Mandatory for sub capacity	Required but simpler
Audit risk	High	Medium
Pricing complexity	High (weight table)	Low (per vCPU)
Sub capacity ratio	Variable by chip	1:1 by default

MSU and mainframe pricing

Million Service Units is the IBM Z metric on z/OS, CICS, IMS, and Db2 z/OS. The metric counts mainframe processing capacity, with the four hour rolling average (4HRA) driving the bill on Workload License Charges and the Tailored Fit Pricing on the modern alternative.

MSU pricing options on z16

• Workload License Charges (WLC). The legacy metric. Bills against the four hour rolling average peak.
• Tailored Fit Pricing (TFP). The modern metric. Bills on aggregate monthly consumption, sub capacity by default.
• Country Multiplex Pricing (CMP). Aggregates MSU across multiple machines in one country for a single bill.

ILMT and compliance posture

The IBM License Metric Tool is the gatekeeper on every sub capacity PVU and VPC license. ILMT is free for IBM customers, but the compliance posture is the buyer obligation.

ILMT compliance checklist

• Install on every cluster. ILMT runs on a central server with agents on each licensed host.
• Refresh quarterly. The quarterly bundle file must be applied within 30 days of release.
• Retain reports. Two quarters of ILMT reports retained, ideally two years for ELA buyers.
• Reconcile against entitlement. Monthly internal review against the IBM Passport Advantage Online entitlement.
• Document exceptions. Any host not covered by ILMT must carry full capacity licensing.

IBM ELA mechanics

The IBM Enterprise License Agreement bundles PVU, VPC, RVU, and authorized user metrics under one master subscription. The ELA carries a three year term with a documented growth allowance and an annual true up.

ELA structure components

• Bundled metric scope. Documented product list with metric and quantity for each line.
• Growth allowance. 10 to 25 percent annual growth allowance before the true up triggers.
• True up clause. Annual review of consumption versus entitlement, with growth above the allowance billed at the contract unit.
• Renewal mechanics. Three year renewal at the year three consumption level, not the year one baseline.

Seven renewal levers on an IBM contract

The seven levers procurement carries to the table

1. ILMT compliance audit. Run an internal ILMT audit 6 months before the renewal and document compliance.
2. Metric mix shift. Move workloads from PVU to VPC where the modern Cloud Pak path exists.
3. ELA scope rationalization. Audit unused PVU on legacy WebSphere, MQ, or Cognos and drop the lines at renewal.
4. Mainframe MSU optimization. Move from WLC to Tailored Fit Pricing on workloads that benefit from sub capacity by default.
5. RVU true down. Audit managed asset counts on Maximo and TRIRIGA and align to the actual portfolio.
6. Growth allowance widening. Negotiate a 20 to 25 percent annual growth allowance in the ELA before the true up triggers.
7. Term ramp lever. Trade a three year ELA with a year one ramp for a deeper unit on year two and three.

What to do next

The eight step checklist takes an IBM estate from a rep sourced renewal quote to a buyer side renewal position.

1. Inventory every IBM product line by metric and by current quantity.
2. Run an ILMT compliance audit against the sub capacity PVU and VPC scope.
3. Audit managed asset counts on Maximo, TRIRIGA, and Tivoli Storage.
4. Map the MSU profile on every z/OS LPAR and decide WLC versus TFP.
5. Score the ELA growth allowance against actual consumption growth.
6. Draft the metric mix shift target with the seven levers above.
7. Open the renewal 9 months early with the metric mix case in writing.
8. Lock the term, growth allowance, and true up cap in a renewal LOI before the SOW.

Frequently asked questions

How Redress engages on IBM licensing reviews

Redress runs IBM advisory inside the Vendor Shield subscription, the Software Spend Assessment, the Renewal Program, and the Benchmark Program.

Read the related IBM hub, the IBM services page, the IBM license models page, the ILMT compliance guide, the audit defense playbook, the licensing complexity landing page, the benchmarking page, the about us page, and the contact page.