RVU per managed resource: devices, users and beyond.
RVU is the metric that hides in plain sight, because it has nothing to do with CPU. It ties your licence to a counted resource: client devices, managed users, instances, endpoints. The resource drifts upward as the estate grows, and the audit risk is that the deployed count quietly passed the tier you bought.
What RVU measures
Resource Value Unit is a usage based metric. Instead of counting processor capacity, it counts a defined resource that the product manages: client devices for an endpoint tool, managed users for an access product, instances or terabytes for others. You license a quantity of that resource. Because it is decoupled from hardware, an RVU product can grow its licence requirement without a single new server, simply as the population it manages grows.
How RVU tiers work
RVU pricing is usually banded. The per unit rate steps down as the volume rises, so the first block of resources is charged at one rate and later blocks at lower rates. That tiering matters two ways. It means a precise count is needed to land in the right band, and it means crossing into a new band changes the arithmetic for everything in that band. An entitlement bought for one tier does not automatically stretch to cover a higher one, even if the headline quantity looks close.
Where the count drifts
RVU exposure is rarely a deliberate over deployment. It accumulates:
- Organic growth in the managed population, as devices, users or endpoints are added without a licence review.
- Ambiguous definitions, where what counts as a managed resource is read more narrowly by you than by IBM.
- Stale records, where decommissioned devices or departed users were never removed from the count.
- Tier creep, where the volume crossed a band boundary and the entitlement was never revisited.
The definition question is often the most valuable. What IBM treats as a countable managed resource, and whether passive, inactive or duplicate entries belong in the count, is frequently disputable, and the dispute moves the number.
Building the RVU position
The defensible position reconciles three things: the documented definition of the managed resource for that product, the actual current count drawn from a clean source, and the entitled quantity and tier you hold. Where the deployed count exceeds entitlement, the first move is to test whether every counted item truly meets IBM's definition, because removing ineligible entries can pull the number back under the tier without buying anything.
RVU findings turn on two questions: how many resources are managed, and what counts as one. Pin the product's resource definition, draw the count from a clean source, strip out stale and ineligible entries, and compare against the entitled tier. The count IBM presents is an opening position, not a fact, and the definition is where a buyer side challenge usually finds room.
Is your RVU count defensible?
Our PVU Reconciliation engagement covers the usage based metrics too, pinning the resource definition, cleaning the count, and reconciling it against your entitled tier before an auditor reads it the other way. We mobilize within 48 hours of your audit notice.
See PVU Reconciliation →The IBM Audit Brief
Audit triggers, ILMT pitfalls, and settlement tactics for IBM software buyers.
Independent, buyer side IBM software audit defense and negotiation. Not affiliated with IBM Corporation.