Cognos Authorized User vs PVU licensing.

Two metrics, two ways to miscount.

Cognos Analytics offers Authorized User licensing, where you license named individuals by the role they hold, and PVU licensing, where you license the cores the server runs on regardless of how many people use it. Authorized User suits a defined, identifiable population where roles are stable. PVU suits broad or anonymous access where counting people is impractical. The audit risk differs sharply: Authorized User exposure comes from undercounted or upgraded roles, while PVU exposure comes from full capacity defaulting on virtualized hardware.

Where role-based counting breaks down.

Cognos roles are tiered. An Analytics Viewer who can only consume content is licensed differently from an Analytics Explorer or Administrator who can author and model. The common finding is role creep: a user provisioned as a viewer is later granted authoring capability, but the entitlement was never upgraded. IBM counts the capability the account holds, not the label it was bought under. Shared or generic accounts and service identities reaching Cognos through embedded dashboards add further uncounted access.

• Viewer, Explorer and Administrator roles each carry a different entitlement
• Granting authoring capability to a viewer upgrades the license required
• Indirect access through embedded or white-labeled dashboards still counts
• PVU on a virtual host needs sub-capacity and ILMT or it defaults to full capacity

Picking the metric the estate actually fits.

The right metric depends on the shape of the user base. A contained team of identifiable analysts is usually cheaper under Authorized User; a large or fluctuating audience embedded across applications is usually safer under PVU, where you stop counting people altogether. The mistake is letting the deployment drift away from the metric on the entitlement, because the audit measures the gap between the two, not the intent behind the original purchase.

What this means under audit.

A Cognos finding usually reduces to whether each user was counted at the right role and whether the metric still fits the estate. Under Contain, Reconcile, Challenge, Settle, the Reconcile step maps every active account to its true capability, strips duplicate and dormant entries, and tests whether a metric change would have lowered the requirement. The Challenge step then disputes inflated role counts on the evidence. Getting the count right is what turns an opening Cognos claim into a number worth negotiating down.