PVU Reconciliation: The Independent Recalculation

Why you recalculate independently

The IBM audit number is a position, not a fact. It is built on the IBM reading of your deployment, frequently at full capacity and frequently without the entitlement offsets you are owed. An independent recalculation gives you a defensible counter number, grounded in evidence rather than in auditor assumptions.

What goes into the recalculation

• Hardware inventory and the actual processor models in service.
• PVU per core ratings read from the IBM PVU table for that silicon.
• Cores allocated to each eligible product, not just installed.
• Hypervisor eligibility and the sub-capacity caps in place.
• ILMT quarterly reports across the lookback period.
• Entitlements from your Passport Advantage records.

The order matters

Reconcile before you respond. We run our own PVU and sub-capacity calculation against your entitlements before IBM finishes theirs, so the conversation starts from your evidence instead of reacting to a number IBM has already committed to internally. The Reconcile step sits between Contain and Challenge in our method for exactly this reason.

Common corrections

A recalculation almost always recovers ground. The recurring items are predictable.

• Wrong per core rating applied to the processor.
• Full capacity charged where sub-capacity was genuinely earned.
• Entitlement offsets IBM left out of its math.
• Bundled use counted twice against separate entitlements.

From recalculation to settlement

The recalculation is not an academic exercise. It becomes the spine of the challenge, item by item, and then the basis of the settlement number. A position built on your own reconciled evidence is far harder for IBM to move than a reactive objection raised after the fact.