Part numbers are where IBM licensing stops being abstract. The contract describes rights in prose, but the entitlement you actually hold is a list of parts, each a compact code that names a product, the way it is measured, and how long the right lasts. Auditors work in part numbers. So do reconciliations and settlements. A buyer who treats the part list as opaque is forced to accept whatever mapping IBM supplies, while a buyer who can decode it controls the comparison. The skill is not glamorous, but it is the difference between checking IBM's math and trusting it.
What a part number carries.
An IBM part identifies several things at once. It names the specific product and often the edition, so two parts for the same product family can carry different rights. It carries the license metric, whether the entitlement is counted in Processor Value Units, Authorized Users, Resource Value Units or Virtual Processor Cores, which determines how deployment is measured against it. It signals the charge type and term, distinguishing a license from annual support and renewal, and a fixed term from a perpetual grant. Decoding the part means reading all of those at once rather than matching on the product name alone.
Where loose decoding costs money.
The recurring errors are consistent, and most favor IBM if left unchallenged:
- Metric collision. A PVU part and a user based part for the same product treated as interchangeable, so the wrong measure is applied to a deployment.
- Support read as license. A renewal or support part mistaken for a license entitlement, or the reverse, distorting the owned count.
- Edition blur. A part for one edition assumed to cover features that only a higher edition part entitles.
- Term confusion. A fixed term entitlement counted as if it were perpetual, overstating coverage for the audited period.
The audit reconciliation is a part by part comparison, and whoever decodes the parts accurately controls it. If you cannot read your own entitlement list, IBM's interpretation of it stands unchallenged. The buyer side response is to resolve every part to its product, metric, charge type and term, then measure the deployment against that precise entitlement rather than a loose product match.
The buyer side position.
A clean settlement runs on decoded parts. Each line of the entitlement summary is resolved to exactly what it grants, the deployment is measured against the correct metric for each product, and any finding built on a misread part, support counted as license, the wrong edition, an expired term, is challenged with the part itself as evidence. The decoded list then anchors the settlement number and gives the forward terms a precise vocabulary, so the next reconciliation starts from agreed definitions rather than ambiguity.