Cloud Pak for Data is licensed in Virtual Processor Cores. Sub capacity rules and a maintained ILMT deployment decide whether you pay for cores used or cores owned. This guide covers the buyer side moves.
IBM Cloud Pak for Data is licensed in Virtual Processor Cores, and the VPC count is where buyers overpay. This guide covers the VPC metric, ratios, sub capacity, and the buyer side moves on an IBM data platform deal.
IBM Cloud Pak for Data bundles data and AI services on a containerized platform. It is licensed in Virtual Processor Cores, and the VPC count is the number that sets the bill.
The mistake buyers make is entitling VPC against peak capacity rather than measured consumption. Sub capacity rules and a correct ILMT deployment change the math.
Virtual Processor Core is IBM's core based metric for the platform. Each service or cartridge consumes VPC entitlement at a defined ratio.
Different services consume VPC at different ratios. A service might consume entitlement at one VPC per core, or at a fraction. Read the ratio per cartridge before you size the deal.
The platform lets you run multiple services on shared entitlement. Understanding which services share and which consume separately prevents double counting in the order.
Sub capacity licensing lets you license the cores actually used by the platform rather than every core in the underlying hardware. It requires the IBM License Metric Tool, ILMT.
Full capacity versus sub capacity on the same cluster
| Approach | Cores licensed | Requirement | Cost impact |
|---|---|---|---|
| Full capacity | All physical cores | None | Highest |
| Sub capacity | Cores used by the platform | ILMT deployed and reporting | Materially lower |
| Sub capacity, lapsed ILMT | Reverts to full capacity | ILMT not maintained | Highest, plus audit risk |
Without a maintained ILMT deployment, IBM can require full capacity licensing. Keeping ILMT current is both a cost control and an audit defense. IBM documents the requirement in its Passport Advantage terms.
Development, test, and staging environments are a frequent source of avoidable VPC cost.
Some IBM programs carry separate non production terms. Where they exist, they cost far less than full production entitlement. Confirm which apply to your cartridges.
Keep non production clusters distinct so they are measured and licensed separately, not folded into production capacity.
The common advice is that full capacity licensing is simpler and safer, so a buyer should avoid the overhead of sub capacity reporting. We disagree. In most of the IBM data platform estates we have reviewed, sub capacity through a maintained ILMT deployment removed 20 to 40 percent of entitled VPC against measured consumption. The buyer side move is to deploy and maintain ILMT, license the cores the platform actually uses, and isolate non production so it is measured separately. Treating full capacity as the safe default is paying a permanent premium to avoid a reporting task that also happens to be your strongest audit defense.
Source: Redress Compliance advisory engagement file, 2024 to 2025.
Cloud Pak for Data is priced on cores. Sub capacity decides whether you pay for the cores you use or every core you own. ILMT is the switch.
Three moves recur. Reconcile entitlement, enforce sub capacity, and time the Passport Advantage commitment.
Compare entitled VPC against measured consumption. The gap is the negotiation.
Passport Advantage discounts scale with committed volume and term. Align the commitment with a clean consumption baseline.
Primary sources: Cloud Pak for Data documentation, IBM License Metric Tool, and IBM Cloud Pak for Data product page.
Cloud Pak for Data is licensed per Virtual Processor Core, the VPC metric. Each service or cartridge consumes VPC entitlement at a defined ratio, so the total VPC count sets the cost.
A Virtual Processor Core is IBM's core based licensing unit for the platform. It maps to the processor cores available to the containerized services, measured under full capacity or sub capacity rules.
Sub capacity licensing lets you license the cores the platform actually uses rather than every physical core in the hardware. It requires a deployed and maintained IBM License Metric Tool, ILMT.
ILMT is the precondition for sub capacity. Without a current ILMT deployment, IBM can require full capacity licensing, which is more expensive and a common audit finding.
Often yes. Some IBM programs carry separate non production terms that cost far less than full production entitlement. Confirm which apply to your cartridges and isolate the environments so they are measured separately.
No. Each cartridge consumes VPC at its own ratio, and some services share a common entitlement pool. Misunderstanding the ratios leads buyers to entitle more VPC than they need.
Passport Advantage discounts scale with committed VPC volume and term. Aligning the commitment to a clean consumption baseline secures the discount without over entitling.
Deploy and maintain ILMT, license the cores actually used under sub capacity, isolate and apply non production terms, and reconcile entitled VPC against measured consumption before renewal.
IBM VPC metric mechanics, sub capacity and ILMT posture, non production terms, and the buyer side moves across the IBM data and analytics estate.
Used across more than five hundred enterprise engagements. Independent. Buyer side. Built for procurement leaders running the next renewal cycle.
IBM data platform cost is a core count. Sub capacity and ILMT decide whether that count reflects what you run or what you happen to own.
