The Seven IBM Licensing Metrics You Must Know

Almost every IBM finding traces back to a metric the buyer never fully understood. Get the metric right and the count follows; get it wrong and you are arguing about the wrong number. These are the seven measures that decide what you owe and where audits land. Know the metric before you defend the count.

Why the metric is the whole argument

An IBM entitlement is a quantity of a unit, and the unit is the metric. The product, the edition, and the deployment all matter, but the metric is what an auditor multiplies to reach exposure. Buyers who treat all licenses as interchangeable miss that a processor based metric and a user based metric behave nothing alike under scrutiny. The seven below cover the great majority of a typical IBM estate, and knowing which one governs each product is the first move in any defense.

The seven metrics

• PVU, Processor Value Unit: a core based metric. The value units assigned per core, for example roughly 70 PVU for a common Intel core, times the cores allocated to the software. It ties cost to hardware capacity and is where sub-capacity disputes live.
• RVU, Resource Value Unit: a usage based metric tied to a resource quantity such as managed devices or users, not to the processor. The chargeable amount tracks how much of the resource the software manages.
• VPC, Virtual Processor Core: the Cloud Pak and container metric. Since Passport Advantage version 11, sub-capacity reporting and the IBM License Service apply to VPC metered products, and manual counting is no longer permitted.
• Authorized User: a named person granted access, counted per individual regardless of whether they log in. Removing access does not remove the requirement unless the entitlement is reduced at renewal.
• Concurrent User: the number of users accessing the software at the same time, which can be lower than the authorized population but needs evidence of the true peak to defend.
• Install or Floating User: counted by the number of installations or by a shared pool of access rights, common in tooling and analytics, where uncontrolled installs quietly exceed the count.
• Resource based metrics: a family of measures tied to a managed quantity such as terabytes, endpoints, or transactions, where the resource definition itself is often the point of dispute.

How buyers use the metrics defensively

We start every reconciliation by confirming the governing metric for each product against the entitlement record, because a finding built on the wrong metric collapses on its own. Where a processor metric applies, we recalculate the cores and test the sub-capacity position. Where a user metric applies, we map actual authorized or concurrent counts to the entitlement rather than accept a headcount sweep. The discipline is the same across all seven: the count is only as valid as the metric it sits on.