Reading the License Information document for RVU counts.

RVU is a usage based metric, which means there is no processor to point at and no simple core multiplication to fall back on. What an RVU counts is defined in words, in the License Information document for the specific product and version. Teams that reconcile RVU products from memory or from a vendor conversation are reconciling against an interpretation, and in an audit the interpretation that wins is the one written in the entitlement.

Why the document is the authority

The License Information document, often called the LI, accompanies each product and sets out the metric definition, the counting rules, and any limitations or bundling restrictions that apply. For RVU products it defines the resource being counted, whether that is managed devices, managed users, processors managed, or another entity, and how that resource is tallied. Because the same product family can change its definition across versions, the LI that matters is the one for the version and entitlement you actually hold.

Finding the unit of measure

The first thing to extract is the exact unit. RVU pricing tiers and the conversion from resources to RVUs are spelled out in the document, and they are frequently banded, so the marginal RVU cost can change as the resource count rises. Reading the unit precisely tells you what to inventory: if the metric counts managed users, you need an accurate managed user count, not a license seat count or an Active Directory total, because those are different populations.

• Identify the exact resource the RVU counts, per product and version
• Read the tier bands that convert the resource quantity into RVUs
• Note inclusions and exclusions that change what falls into the count
• Confirm bundling limits that cap how a bundled entitlement may be used

Inclusions, exclusions, and bundling limits

The most contestable findings come from the fine print: what the document explicitly includes or excludes, and what scope a bundled entitlement is limited to. A classic example is a database bundled with another product under a restriction that it may only be used in support of that product. Used beyond that scope, it becomes separately licensable. The LI is where those boundaries are written, and reading them is how you both defend a correct count and identify where IBM may have over scoped a finding.

Using the LI to challenge a finding

When an audit produces an RVU finding, the LI is your primary instrument for challenging it. If IBM counted a population the document excludes, applied the wrong tier, or assessed a bundled component beyond its restricted scope, the entitlement text is the evidence that reverses it. The document cuts both ways, which is exactly why reading it before the audit, rather than during it, is the buyer side advantage.