Cognos on Cloud Pak for Data: conversion math.

From user tiers to platform cores

Standalone Cognos is counted by user role, where consumers, authors and administrators sit in different tiers. Delivered through Cloud Pak for Data, Cognos is consumed as a service on a platform metered in Virtual Processor Core. The conversion does not simply rename your licenses. It restates the value of your existing user entitlements into a VPC allowance through a defined ratio, and from that point the question is no longer how many users of each type you have, but how much platform capacity the Cognos service consumes. Organizations that keep thinking in user counts after the move lose visibility of the position they are actually entitled to.

The ratio is the lever

The conversion ratio translates prior entitlement into VPC, and a small difference in the ratio applied moves the whole position. An audit can apply a less favorable ratio than the one your conversion was actually entitled to, or ignore entitlement that should have carried across the move entirely. Because the ratio multiplies across your full prior estate, an incorrect ratio is not a rounding error, it is a systematic inflation. Reconstructing the conversion you were entitled to, and crediting the user entitlement that converted into VPC, is the first move in challenging the count.

Container sub-capacity rules apply

VPC metered products fall under ILMT based sub-capacity reporting since Passport Advantage version 11, which reached existing customers on May 1 2023. On a container platform, that has teeth: where the Cloud Pak deployment cannot demonstrate a clean sub-capacity position, IBM can charge for all cores in the cluster, not just the cores running Cognos. A measurement gap in one part of the platform can therefore be sized against the entire cluster. As with any sub-capacity exposure, this usually traces to a measurement deficiency that can be corrected rather than a real over consumption.

Rebuilding the conversion you were owed

The defense reconstructs three things in order: the ratio your conversion was entitled to, the user entitlement that should have carried across into VPC, and the actual VPC the Cognos service consumes under proper ILMT measurement. With those three established, an inflated finding usually collapses toward the position you genuinely hold. On an enterprise estate where Cognos sat alongside Maximo, reconciling actual usage to entitlements removed the excess claim and cut $2.8M of over deployment at renewal.