IBM Licensing in 2026 — PVU, ILMT, Cloud Paks and the ELA dance.

How IBM counts what you owe.

IBM software is licensed under a handful of metrics that map back to Passport Advantage. The Processor Value Unit (PVU) is the dominant per-core currency for most middleware — WebSphere, MQ, DB2, Cognos, Information Server, Tivoli. Each chip family has a published PVU rating: 70 PVUs per core for most Intel Xeon, 100 PVUs for older Power generations, 120 PVUs for current Power10. Resource Value Units (RVUs) cover certain analytics and security products on a managed-resource basis. Virtual Processor Cores (VPC) is the newer subscription metric that Cloud Paks use on OpenShift. Authorized User and Concurrent User remain for desktop, modelling and select developer tools.

The metric you bought is rarely the metric that fits the deployment two refresh cycles later. In our experience across 340+ engagements, the most common IBM compliance gap is a workload that has migrated from a 70-PVU core to a 120-PVU core without the customer updating the entitlement count. The audit finding is mechanical and the back-bill is immediate. Track every hardware refresh against the PVU table; do not assume the per-core multiplier stays constant. A periodic software license compliance assessment catches a refreshed core before IBM's auditor does — turning a mechanical back-bill into a planned, budgeted true-up.

Sub-capacity and ILMT

Sub-capacity licensing — the right to count only the cores actually allocated to a workload, not every core on the host — is conditional on the IBM Licence Metric Tool (ILMT). ILMT must be installed within 90 days of first eligible deployment, configured to discover the eligible software, and generate quarterly audit reports retained for two years. Customers who miss any of those obligations forfeit sub-capacity by default. IBM compliance teams treat ILMT gaps as a high-yield audit trigger: a missed quarter on a single VMware cluster can flip 8 cores of licensed entitlement into 128 cores of full-capacity exposure overnight.

Authorized User Single Install vs. Floating User

For developer and modelling products — Rational, InfoSphere, SPSS — IBM uses Authorized User Single Install (AUSI) and Floating User metrics. AUSI binds a named individual to a single instance; Floating User permits any user up to a concurrency cap. The metric choice affects price, but it also affects audit treatment: AUSI counts every install regardless of usage, while Floating User counts peak concurrency. Customers running developer tools across multiple environments should validate that the metric in the contract matches the actual deployment pattern. We have seen six-figure exposures driven entirely by a metric mismatch.

The contract architecture most buyers never read.

Passport Advantage is the master agreement under which most IBM perpetual and subscription licenses are bought. The hierarchy is Passport Advantage Agreement → International Programme Licence Agreement (IPLA) → Licence Information document → Proof of Entitlement. The Licence Information document is where IBM defines product-specific terms, including which metric applies, which sub-components are included, and what restrictions limit the entitlement. Buyers who treat the Proof of Entitlement as the contract miss the binding LI document where most audit disputes are resolved.

Subscription & Support — the annuity

IBM Subscription & Support (S&S) is the annual maintenance fee attached to every perpetual licence on Passport Advantage. S&S typically runs at 20–22% of perpetual list price per year. IBM allows S&S to be reduced at anniversary, but only at the SKU level and only with explicit removal — there is no automatic shelfware mechanism. Customers who let S&S renew on the default anniversary without affirmatively de-scoping unused entitlements pay for shelfware indefinitely. The largest single S&S saving we have negotiated for an enterprise client was £4.1M annual, captured by reviewing twelve years of Proof of Entitlement against current deployment.

The subscription model that replaces the catalogue.

Cloud Paks are IBM's packaged software bundles for OpenShift — Cloud Pak for Integration, Cloud Pak for Data, Cloud Pak for Watson AIOps, Cloud Pak for Business Automation, Cloud Pak for Security. Each Pak is licensed by Virtual Processor Core (VPC), with a flexible internal allocation between the component products. The economic logic is that a customer with 1,000 VPCs of Cloud Pak for Integration can run any mix of the underlying products — MQ, App Connect, API Connect, DataPower, Aspera — as long as total consumption stays within the VPC envelope.

VPC conversion factors

Cloud Paks include published conversion factors that let a customer migrate from a Passport Advantage PVU entitlement to a Cloud Pak VPC entitlement. The conversion ratios favour IBM more often than the customer — 1 PVU often maps to less than 0.01 VPC, which sounds attractive but masks a significant unit-of-value shift. We routinely re-negotiate the conversion ratio during ELA renewal, using parallel deployment plans on Red Hat OpenShift or alternative platforms as leverage.

How IBM audits actually get scheduled.

IBM no longer operates a single in-house audit team analogous to Oracle LMS. Most enterprise audits are commissioned through Deloitte, KPMG, or smaller specialist firms acting as IBM's authorised reviewer. The audit notice typically arrives 30–90 days before fieldwork begins, and the scope is defined by the IPLA — broadly, IBM is entitled to verify entitlement and usage of any Passport Advantage product. Triggers we see consistently: ILMT non-reporting, ELA expiry without renewal commitment, large hardware refresh, public cloud migration, M&A integration, and Passport Advantage anniversary 18–24 months after a known business event.

Engagement protocol

The defensive posture is to channel all audit communication through a single appointed contact, provide only the data the IPLA contractually requires (not the broader extract auditors typically request), and run the ILMT and entitlement reconciliation internally before sharing any output. IBM audit firms are accustomed to customers handing over raw deployment scans without scoping — the resulting findings rarely match the actual licence position. Our average claim reduction across IBM audit engagements is 71%, and the largest savings come from rebuilding the entitlement record from Proof of Entitlement documents the customer already possessed.

Seven levers that actually move IBM price.

IBM's commercial team operates against an internal deal model that pre-anticipates the standard customer asks. To move price beyond the routine discount, buyers need to introduce levers IBM has not modelled into the proposal. Across our engagements, these are the seven that consistently change the outcome.

1. OpenShift parallel deployment. A credible workload migration to Red Hat OpenShift or a non-IBM container platform forces IBM Cloud Pak renewal team to defend the VPC pricing.
2. S&S de-scoping at anniversary. Affirmative removal of unused entitlements before S&S renews captures shelfware reduction that disappears in steady state.
3. Sub-capacity reconciliation. A clean ILMT history and rebuilt PVU map is the single largest source of audit settlement reduction.
4. Cloud Pak conversion ratio. Renegotiating the PVU-to-VPC factor at ELA renewal often captures 20–35% effective price reduction.
5. ELA scope sculpting. Removing low-utilisation products from the ELA at renewal protects against forced bundling.
6. Term length flexibility. Three-year ELA terms with annual flexibility clauses typically beat five-year fixed terms on TCO when the deployment is changing.
7. Audit waiver. A narrowly scoped audit-waiver clause in the renewal agreement protects the next 12–24 months of estate change.

Internal next steps

If you are reading this in advance of an IBM event — audit notice, ELA renewal, Cloud Pak conversion, hardware refresh — three actions consistently de-risk what follows. First, reconstruct your Proof of Entitlement library against the current Licence Information documents and validate the metric on every SKU. Second, audit ILMT continuity for every sub-capacity product across the last eight quarters. Third, baseline S&S against entitlement-in-use, not against historical purchase. The IBM Licensing & ELA Guide walks through each of these in detail.