Service · PVU Reconciliation
PVU reconciliation, recounted on your side.
When IBM rebuilds your processor value unit position from raw inventory, it counts to its own advantage. We run an independent recalculation against your entitlements and Passport Advantage records, so the number you defend is the number you can prove. Independent and buyer side, we are not affiliated with IBM.
Core based metric · PVU per core times cores allocatedSub capacity · counted only where evidenced
What IBM does to your PVU count.
The processor value unit is a core based metric. PVU per core, around 70 PVU for a typical Intel core, multiplied by the cores allocated to the IBM software. Capacity drives the cost, and capacity is where the count goes wrong.
In an audit, IBM rebuilds the count from your inventory feed and tends to read every ambiguity its own way. A WebSphere instance using 4 of a 32 core host is 480 PVU on a clean sub capacity basis. Counted at full capacity, the same instance becomes 3,840 PVU. That is eight times the license, created by a counting choice rather than a deployment fact.
Where sub capacity evidence is thin, IBM defaults to full capacity. On LPAR and Power, allocated cores count even when idle. Mixed hypervisors, stale inventory, and the wrong PVU per core table all push the number up. Left unchecked, the reconciliation IBM hands you is the ceiling, not the answer.
How we reconcile: Contain. Reconcile. Challenge. Settle.
01
Contain
Freeze the inventory feed before it reaches IBM. Nothing is reconciled off data we have not scoped and verified.
02
Reconcile
Recompute PVU per core against the correct table, map cores to entitlements, and apply sub capacity where it holds.
03
Challenge
Dispute every full capacity default, wrong core count, and missing entitlement offset line by line, with evidence.
04
Settle
Lock the corrected position into the settlement so the count cannot drift back up at renewal.
What you get.
A defensible PVU position you own, backed by evidence IBM has to answer to.
Deliverable 01
Independent PVU recount
A full recalculation of every in scope product, core by core, against the correct PVU per core values and your real allocation.
Deliverable 02
Sub capacity validation
Each instance tested for sub capacity eligibility against your ILMT data and hypervisor type, so virtual cores are not charged as physical.
Deliverable 03
Entitlement reconciliation
Your Passport Advantage entitlements mapped to deployment, with every offset IBM left out credited back into the count.
Deliverable 04
Defense ready evidence pack
A documented position, line by line, that holds up when IBM pushes back during reconciliation and settlement.
Exposure defended.
Manufacturing · WebSphere + Db2
71%
claim reduced
Methodology challenge
Incorrect PVU values and denied sub capacity reversed against clean ILMT evidence.
Method
Recount
core by core
Capacity, corrected
Full capacity defaults reversed where sub capacity could be evidenced and proven.
Range
30 to 92%
findings reduction
Across engagements
The reduction band we have delivered across more than 500 IBM audit engagements.
Products this touches.
PVU reconciliation matters most on the core based products that draw audits.
Recount before you concede.
$250M+ in exposure defended. 500+ engagements. We mobilize within 48 hours of your audit notice. Independent and buyer side, every time.
Get audit help now →The IBM Audit Brief
Audit triggers, ILMT pitfalls, and settlement tactics for IBM software buyers.
IBM Audit
Independent, buyer side IBM software audit defense and negotiation. Not affiliated with IBM Corporation.
Independent. Not affiliated with IBM Corporation.Buyer Side · Est. 2019