IBM PVU licensing: how the per core math really works.

IBM PVU licensing prices software by processor value units assigned per core, and the gap between full capacity and sub capacity counting, policed by ILMT, is where most of the money and most of the audit risk lives.

What is a PVU and how is it counted?

A processor value unit is IBM's per core pricing weight. Every processor family carries a PVU rating per core, typically 70 or 100 for common x86 server chips, and the license requirement is the rating multiplied by the cores available to the software.

Entitlements are bought and tracked through IBM Passport Advantage. The same product can need wildly different PVU counts depending on the hardware underneath it, which is why infrastructure changes silently change license positions.

Why do core counts explode in clusters?

Mobility. If a VM can move across a cluster, full capacity rules can count every core the VM could touch, not just where it runs today. Cluster design is therefore a licensing decision, not only an infrastructure one.

How does sub capacity licensing actually work?

Sub capacity licensing lets you license the cores assigned to the partition or VM instead of the whole physical machine, under IBM's sub capacity terms. The discount versus full capacity is routinely 50 to 80 percent on virtualized estates.

The terms attach conditions: eligible virtualization technology, eligible products, and continuous measurement with quarterly reporting. Miss a condition and the protection evaporates, retroactively.

• Eligible technology: the virtualization platform must be on IBM's eligible list.
• Continuous measurement: the tooling must run and retain reports, not just exist.
• Quarterly reports: reports must be generated and kept for at least two years.
• Whole estate logic: gaps in coverage expose the uncovered portion to full capacity.

What does the full capacity fallback cost?

In our 2024 to 2025 file, full capacity recalculations in audit claims ran 3 to 8 times the sub capacity position the customer believed it held. The fallback is the single most expensive clause most IBM customers have never read.

Why is ILMT the center of every PVU conversation?

The IBM License Metric Tool is the contractual instrument of sub capacity eligibility. It discovers IBM software, measures core consumption, and produces the quarterly reports the terms require.

ILMT problems are operational, not conceptual: agents missing from new VMs, scanner failures after patches, unclassified software piling up, and reports nobody generates. Each gap converts silently into full capacity exposure.

1. Deploy ILMT agents through the standard VM build so coverage is automatic.
2. Reconcile ILMT inventory against your CMDB quarterly; investigate every gap.
3. Classify new discoveries within 30 days; unclassified items rot into findings.
4. Generate, review, and archive quarterly reports with two year retention.
5. Audit your own ILMT health twice a year as if IBM were doing it.

Does end of support software change the PVU position?

It changes the risk profile. Products past their date in the IBM software support lifecycle still need licenses, and audits flag them because estates stop watching software they plan to retire.

How do you control PVU costs at renewal and beyond?

PVU cost control is capacity hygiene plus negotiation timing. The estate that knows its own sub capacity position can shrink entitlements to match, challenge conversion ratios, and walk into renewals with evidence instead of fear.

• Right size entitlements: surrender or shelve PVU entitlements the measured position no longer needs.
• Challenge Cloud Pak ratios: PVU to VPC conversion offers deserve independent modeling; ratios are negotiable.
• Design clusters for licensing: dedicated IBM clusters or host affinity rules cut countable cores.
• Keep audit currency: a clean ILMT record is worth more in negotiation than any discount argument.

When should you consider moving off PVU metrics?

When IBM offers conversion to Cloud Pak VPC terms at a ratio that beats your measured PVU position, or when subscription products replace the function. Model both against two renewal cycles; conversion offers improve when declined the first time.

Where the common advice on IBM PVU licensing is wrong

The standard advice treats ILMT as an annoying compliance checkbox to delegate to a junior SAM analyst. We disagree. In roughly 25 to 35 IBM engagements Morten Andersen ran between 2024 and 2025, ILMT health was the single largest financial variable on the table, worth more than every discount negotiation combined, because the full capacity fallback recalculates exposure at 3 to 8 times the believed position. The buyer side move is to treat ILMT as a financial control with executive ownership, audited internally twice a year. A tool that decides whether you license 8 cores or 64 is not a checkbox; it is the contract.

What the engagement data shows

Three cuts of our advisory engagement file frame the size of the opportunity.

What to do next

Five moves turn this analysis into a lower invoice on the next renewal.

A sequence you can run this quarter

1. Map every IBM PVU product to the hardware and clusters it runs on.
2. Verify ILMT agent coverage against the CMDB and close every gap.
3. Generate and archive the quarterly reports the sub capacity terms require.
4. Recalculate your believed position and stress test it at full capacity.
5. Right size entitlements against the measured position before renewal.
6. Model any Cloud Pak conversion ratio independently before accepting it.

White Paper · IBM

IBM PVU to VPC Transition

IBM is moving Processor Value Unit licensing to Virtual Processor Core. Read it free.

Read the white paper

Frequently asked questions

What is a PVU in IBM licensing?

A processor value unit is IBM's per core pricing weight. Each processor family carries a PVU rating per core, commonly 70 or 100 on x86 chips, and the license requirement is that rating multiplied by the cores available to the software.

What is the difference between full capacity and sub capacity PVU licensing?

Full capacity counts every activated core in the physical machine or cluster the software can reach; sub capacity counts only the cores assigned to the partition or VM. Sub capacity typically saves 50 to 80 percent on virtualized estates but requires compliant ILMT measurement.

Is ILMT mandatory for IBM sub capacity licensing?

Effectively yes for most estates. IBM's sub capacity terms require continuous measurement with quarterly reporting, and ILMT is the standard instrument. Without compliant coverage the terms default the estate to full capacity, retroactively.

How expensive is the full capacity fallback in an IBM audit?

In our 2024 to 2025 engagement file, full capacity recalculations ran 3 to 8 times the sub capacity position customers believed they held. It is the largest single exposure line in most IBM audit claims.

How does virtualization affect PVU counts?

Mobility rules can count every core a VM could reach across a cluster, not just where it runs. Cluster design, host affinity, and dedicated IBM clusters are therefore direct licensing levers.

Should you convert PVU entitlements to Cloud Pak VPCs?

Only after independent modeling. Conversion ratios are negotiable and improved after first refusal in our file; accept when the ratio beats your measured PVU position across two renewal cycles, not before.