Many buyers still treat their Cloud Pak and VPC metered estate as if it sits outside the sub-capacity rules. That assumption was reasonable for a while and is now wrong. The shift to the Virtual Processor Core metric pulled these products into the same tracking and reporting obligations that have always governed PVU sub-capacity, and the container model that Cloud Paks run on adds a penalty that does not exist in classic virtualization.
What changed at Passport Advantage v11.
VPC is a virtual core metric. Under Passport Advantage v11, which applied to existing customers from May 1 2023, sub-capacity reporting and ILMT extended to VPC metered products as well as the older PVU ones. The practical consequence is blunt: manual counting of VPC entitlements is no longer permitted. Where a spreadsheet of allocated cores might once have sufficed, IBM now expects the same tool-generated, continuously maintained evidence it requires for PVU sub-capacity. A Cloud Pak estate that has been tracked by hand is exposed the moment an audit looks for the reports.
The same conditions still apply.
Bringing VPC and Cloud Pak under ILMT means the familiar sub-capacity conditions carry over without softening:
- The tracking tool must be deployed within 90 days of the first eligible deployment.
- It must run continuously, with no coverage gaps.
- Reports must be generated quarterly and retained for two years.
- The data must be accurate, with agent coverage and product categorization that survive scrutiny.
Fail any of these on a VPC metered product and the default consequence is the same one PVU buyers face: IBM charges at full capacity for the affected period.
Why containers raise the stakes.
The Cloud Pak model is where the exposure becomes severe. For container and Cloud Pak deployments, non-compliance does not just default the workload to full-capacity on its host. IBM is entitled to charge for every core in the cluster. A small, properly scoped workload that loses its tracking evidence can therefore be priced against the entire cluster it runs in, which is a far larger number than a single host would ever produce. This is the trap that catches buyers who assumed their Cloud Pak entitlement was self-managing.
Staying defensible across a Cloud Pak estate.
The defensible position is the same one PVU sub-capacity has always required, applied to a more demanding surface. Confirm that ILMT or an approved tool is actually capturing the VPC metered products and the Cloud Pak components, not just the legacy PVU installs. Verify agent coverage across the cluster, not a sample of hosts. Reconcile the VPC consumption the tool reports against the entitlement you actually hold, accounting for the bundling and pooling that Cloud Paks allow. The goal is a quarterly report that proves your VPC position the way the old reports proved your PVU position.