Cloud Pak for Data Licensing and Conversion Math
Cloud Pak for Data is metered in Virtual Processor Cores, and most buyers arrive at it by converting older entitlements they bought under a different metric. The ratio used in that conversion, and the reporting that backs it, decide whether the deployment is covered or exposed. The conversion math is the audit, before any auditor arrives.
How Cloud Pak for Data is metered
Cloud Pak for Data is licensed in Virtual Processor Cores, the VPC metric that Passport Advantage moved to for the Cloud Pak family. A VPC is a virtual core made available to the software. Where a deployment runs in containers on a virtualized platform, you license the virtual cores assigned to the workload rather than every physical core in the host, but only when the reporting conditions are met. Since the Passport Advantage version 11 terms, sub-capacity reporting and the IBM License Service apply to VPC metered products, and manual counting is no longer permitted. That last point catches buyers who still treat Cloud Pak entitlements like the spreadsheet era of PVU.
Where the conversion math comes from
Few buyers buy Cloud Pak for Data from a clean sheet. Most carry forward entitlements from Db2, the analytics estate, or other middleware bought in PVU, and convert them into VPC under a trade up or bundle ratio set in the offering terms. The ratio is the whole game. A favorable ratio turns a large legacy PVU pool into a generous VPC entitlement. An unfavorable one, or a ratio applied to entitlements that were never eligible for the trade, leaves a gap that surfaces the moment IBM counts the running cores. The conversion paperwork, not the deployment, is where the number is won or lost.
- VPC is the unit: Cloud Pak for Data counts virtual processor cores assigned to the software, not physical sockets
- The ratio is contractual: the PVU to VPC trade up rate lives in your offering terms, and IBM will hold you to it exactly
- Eligibility is per entitlement: not every legacy license qualifies for conversion, and an ineligible one converted anyway is a finding
- Reporting is mandatory: the IBM License Service must capture the VPC consumption continuously, the same duty as ILMT for PVU
How buyers keep Cloud Pak for Data defensible
We rebuild the conversion from the source entitlements forward: which legacy licenses were traded, at what ratio, and whether each was eligible under the terms in force at the time. Then we reconcile the resulting VPC entitlement against what the License Service actually reports running, so a gap is sized accurately rather than swept to full cluster counting. Where the conversion was applied correctly and the reporting is clean, the position holds, and a finding that ignored the trade up evidence is challenged with the contract record that created it.
An auditor looking at Cloud Pak for Data will compare your VPC entitlement to the virtual cores the License Service reports, then test whether your entitlement was built on a valid conversion. If the trade up ratio, the eligibility of the source licenses, or the continuous reporting cannot be shown, the easy ruling is to charge the running cores against a smaller entitlement, or in a container shortfall, the whole cluster. Reconstruct the conversion math and prove the reporting before the audit does the arithmetic for you.