Cloud Pak licensing and the VPC metric.

What a Virtual Processor Core is.

VPC counts the virtual cores available to the Cloud Pak software, with the same sub-capacity logic that governs PVU: you license the cores the software can use rather than the full physical host. A Cloud Pak entitlement is a pool of VPCs, and different components draw from that pool at different ratios depending on the program. The principle that matters for audit is that the entitlement is consumed by reachable virtual capacity, not by a headcount or an install count.

Why v11 changed the rules.

Under Passport Advantage v11, in effect for existing customers from May 1 2023, sub-capacity reporting and ILMT obligations were extended to VPC-metered products. Manual counting of virtual cores is no longer permitted. In practice that means a Cloud Pak deployment now has to be discovered and reported by an approved tool exactly as a PVU product does. Organizations that adopted Cloud Paks before this shift, and never moved their reporting onto ILMT, frequently carry a reporting gap they are unaware of until the audit letter arrives.

• VPC sub-capacity now depends on ILMT or an approved equivalent, not spreadsheets
• The tool must be deployed within 90 days of first eligible deployment
• It must run continuously, with quarterly reports retained for two years
• Container deployments must be discovered, not estimated, to hold the claim

The cluster-wide trap.

Cloud Paks usually run on containers, and container non-compliance carries the harshest default in IBM licensing: where the sub-capacity conditions are not met, IBM charges for all cores in the cluster, not only the cores the workload used. A small Cloud Pak footprint on a large OpenShift or Kubernetes cluster can therefore produce a finding far larger than the actual consumption. This is the same shape as the VMware cluster rule, amplified by the container default.

What this means under audit.

A Cloud Pak finding lives or dies on whether the VPC reporting was sound for each period in scope. The buyer side defense reconstructs what the approved tool recorded quarter by quarter, confirms the deployment dates against the 90 day window, and challenges any cluster-wide charge for periods where the conditions were in fact met. This is the Reconcile and Challenge work of Contain, Reconcile, Challenge, Settle: prove the contained VPC count on the evidence before the number is ever negotiated.