Cloud Paks replaced a hundred PVU based products with one metric and a conversion table.
Virtual Processor Cores, conversion ratios per Pak, included entitlement, and the underlying OpenShift right to run. We build the entitlement model and verify the conversion math on every Cloud Pak in the estate.
One entitlement metric for a bundle of formerly separate products.
Cloud Paks are IBM's containerized product bundles, each priced in Virtual Processor Cores. The current portfolio includes Cloud Pak for Integration, Cloud Pak for Data, Cloud Pak for Security, Cloud Pak for Watson AIOps, Cloud Pak for Business Automation, and Cloud Pak for Network Automation. Each Pak bundles a set of formerly standalone IBM products with the right to run on Red Hat OpenShift Container Platform as the underlying runtime.
The licence mechanic that matters is the conversion ratio. Each Pak publishes a ratio table that translates the source entitlement of the underlying products into VPC. Customers who already held PVU based or user based entitlement for the underlying products can convert that entitlement into Cloud Pak VPC at the published ratio. The ratios vary by Pak and by source product. The arithmetic is not difficult but the consequences are large.
The entitlement model has to track the source product entitlement, the conversion ratio applied, the resulting Cloud Pak VPC entitlement, and the deployed VPC consumption against that entitlement. Most enterprises have this in three different systems with no reconciliation. The exposure is real. Read the related work on sub capacity and Passport Advantage.
What we model for.
- Cloud Pak for Integration.
- Cloud Pak for Data.
- Cloud Pak for Security.
- Cloud Pak for Watson AIOps.
- Cloud Pak for Business Automation.
- Cloud Pak for Network Automation.
- Cloud Pak System.
How we validate conversion and consumption.
Source entitlement inventory
Pull the PVU and user based entitlement for the products bundled into each Pak in scope. This is the source entitlement that converts into VPC. Read against the Passport Advantage ledger.
Conversion ratio application
Apply the current published conversion ratios per Pak per source product. Compute the resulting VPC entitlement. Validate against the customer order records for the Cloud Pak purchase. Flag where conversion has been documented in the order, where it is implied, and where it is missing.
Deployed VPC measurement
Measure deployed VPC on the OpenShift clusters that host each Pak. Validate against the IBM Licence Service running on the cluster. Reconcile against the ILMT view where applicable. The measurement basis varies by Pak.
Position, gap, and roadmap
Document the position per Pak, the gap between entitlement and consumption, and the roadmap to close it. Identify products in the source bundle that are no longer in use and could justify a downsize at renewal.
The seven structural issues.
- Conversion ratios change as IBM updates the Pak.
- Source entitlement records get archived once the Pak is bought.
- The same source product can appear in more than one Pak.
- OpenShift entitlement is bundled but the bundle scope is finite.
- VPC measurement depends on the IBM Licence Service running correctly.
- Customers sometimes deploy Pak components outside the licensed OpenShift footprint.
- Renewals reset the Pak edition and SKU, which forces a re reconciliation.
Where the bundled OpenShift right ends.
- The Cloud Pak entitlement includes OpenShift only for nodes that run the Pak.
- OpenShift used for other workloads needs separate OpenShift entitlement.
- Mixing Pak and non Pak workloads on the same nodes triggers a measurement question.
- Worker node taints, labels, and namespaces matter to the measurement model.
- The IBM Licence Service collects the data IBM will look at in an audit.
- See the Red Hat expertise page for non Pak OpenShift.
How clients approach Cloud Pak licensing.
Should we convert standalone products into Cloud Paks?
It depends on the product mix, the Pak ratio, and the deployment plan. Conversion is often financially attractive but the loss of flexibility and the risk of stranded entitlement matter. The diagnostic produces the case both ways.
Can we run Pak components outside OpenShift?
Most Pak components require OpenShift as the runtime. A few support a non OpenShift mode for limited scenarios. The contract terms are specific and worth reading before committing.
What metric does IBM audit on for Cloud Paks?
Virtual Processor Cores consumed by Pak workloads as measured by the IBM Licence Service. Where the Licence Service is not running, IBM will compute based on the available cluster data, typically at the disadvantage of the customer.
Do sub capacity rules apply to Cloud Paks?
The Pak VPC model is its own sub capacity construct. ILMT is not the reporting tool. The IBM Licence Service is. The same discipline on coverage, retention, and reconciliation applies.
What about Watson AI and watsonx?
Some Watson products sit in Cloud Pak for Watson AIOps. The newer watsonx generation has its own licensing. The model varies by product. See the watsonx expertise page for the dedicated work.
Resources
Expertise
Services
Need an independent read on this area?
A senior advisor responds within 24 hours and scopes a credible engagement structure within a week.
Get an independent read on this area of your IBM estate.
Tell us where you are in the cycle. A senior advisor will respond within 24 hours with a scoped engagement structure and an availability window. No sales call, no pitch deck. We do not resell IBM software. We have no IBM Business Partner status. Our recommendations are constrained only by what is good for the buyer.
Read more on why independence matters or browse the services overview for engagement structures.
Request a conversation
Corporate email required. Personal email addresses are not accepted.