UVU and Other Less Common IBM Metrics
Most attention goes to PVU, RVU and VPC, but IBM products are licensed on a long tail of other metrics. User Value Units, authorized users, concurrent users and resource based counts each have their own counting rules. The unfamiliar metric is often where the quiet exposure sits.
Beyond the headline metrics
PVU is core based, RVU is tied to a resource quantity such as managed users or devices, and VPC counts virtual processor cores. Around those three sit a set of less common metrics that govern specific products. They draw less scrutiny internally, which is exactly why they accumulate drift between what you bought and what you run.
User Value Units
User Value Units, or UVU, work like PVU but applied to users rather than cores: a population of users is converted into value units using a banded scale, so the cost per user can change as the count crosses thresholds. The exposure comes from counting the wrong population, for example including inactive or duplicate accounts, or failing to notice that crossing a band changes the requirement.
Authorized and concurrent users
- Authorized user: licensed per named individual with access, whether or not they log in. Stale accounts that retain access still count, so deprovisioning discipline is a license control.
- Concurrent user: licensed by the number of simultaneous sessions. Exposure appears at peak, so an average usage view understates the requirement.
- Resource based counts: some products meter on managed entities such as endpoints or processors managed, which can grow silently as the estate grows.
Why the unusual metric is risky
Less common metrics share a pattern: the counting rule is specific, the internal owner is often unclear, and the deployment grows faster than anyone reconciles. An audit applies the precise rule, and a metric nobody owned becomes a finding. Because reporting and ILMT now extend to VPC metered products and manual counting is no longer permitted there, the safe assumption is that IBM can measure more of your estate automatically than it once could.
Getting ahead of it
Inventory every IBM product by its actual license metric, not by the metric you assume. For each unusual metric, identify the precise counting basis, assign an owner, and reconcile the count to entitlement on the same cadence you would for PVU. The goal is that no metric is a surprise when the data request arrives.
An audit does not limit itself to the metrics you watch most closely. UVU bands, authorized users with stale access, and concurrent user peaks each carry their own counting rule, and the unowned metric is the one that becomes a finding. Inventory every product by its real metric, assign ownership, and reconcile each count to entitlement before IBM does it for you.