Product Licensing Cluster

IBM Cognos Licensing.

Cognos Analytics is split licensed between a server side metric (PVU) and a user side metric (Authorized, Concurrent, or Mobile User). The buyer side discipline is the named user inventory reconciliation. This article is the operational reference.

Read time 10 min Updated May 2026 By IBM Licensing Experts
Analytics dashboard view representing IBM Cognos reporting
Independence statement. IBM Licensing Experts is an independent advisory firm. We are not an IBM Business Partner, reseller, or affiliate. We have no resell margin tied to our recommendations and we do not earn revenue from any IBM product line. Read more on why independence matters.

Why Cognos licensing is split.

Cognos Analytics is the IBM enterprise reporting and analytics platform. The licensing is split between a server side and a user side. The server side scales with the workload footprint and is sub capacity eligible. The user side scales with the named user inventory and depends on the named user reconciliation discipline. Most enterprises manage the server side adequately and underestimate the user side reconciliation. The user side gap is the most common Cognos compliance finding.

1. The server side: PVU.

The Cognos platform server (the Dispatcher, the Content Manager, the report rendering engine) is licensed by PVU on the workload footprint. The metric is the standard PVU per core metric and is sub capacity eligible. The buyer side discipline is the ILMT scan and the Audit Snapshot retention. See PVU explained and ILMT guide.

2. The user side: Authorized, Concurrent, Mobile.

The Cognos user side is licensed by named user. Three variants exist. The Authorized User is the most common. Each named user that has access to a Cognos role consumes one Authorized User entitlement, regardless of frequency of use. The Concurrent User is a smaller pool sized to the simultaneous user count. The Mobile User is a separate entitlement covering mobile access. The variants are not interchangeable and the same user counted under one variant cannot be substituted under another without a procurement event.

3. The user inventory discipline.

The Cognos user gapA typical enterprise Cognos deployment grows organically. Reports proliferate, user access widens, the named user inventory is not retired as employees leave or change roles. Five years after the initial licence purchase, the named user inventory is two to three times the licensed entitlement. The audit reads the Cognos user catalog, identifies the named users with active role assignments, and produces an Authorized User shortfall finding. The settlement is several hundred user licences priced retrospectively.

The buyer side discipline is the quarterly user inventory reconciliation. Read the Cognos user catalog, list the named users with active role assignments, reconcile against the HR active employee list, retire the inactive users from Cognos. The discipline is one operational hour per quarter and prevents the largest single Cognos audit finding. See self assessment guide.

4. Sub capacity on the server.

The Cognos PVU server side is sub capacity eligible on the recognised virtualization platforms. The ILMT discipline applies in full. The Cognos specific consideration is the multi tier deployment. Cognos typically runs across several tiers (Dispatcher, Content Manager, Application Tier). Each tier is independently scanned and each consumes PVU from the same Cognos entitlement pool. See sub capacity explained.

5. Cognos and Cloud Pak for Data.

Cognos has an inclusion in Cloud Pak for Data. The Cloud Pak for Data entitlement covers Cognos as a service inside the bundled VPC frame. A buyer with both a standalone Cognos entitlement and a Cloud Pak for Data deployment that uses Cognos is consuming entitlement from both. The reconciliation at renewal is the bundling decision. See Cloud Pak strategy and Cloud Pak Licensing Guide.

6. Audit posture on Cognos.

Cognos in an audit is reconciled on the two axes. The server side PVU against the ILMT Audit Snapshot. The user side named user inventory against the Authorized, Concurrent, or Mobile User entitlement. The auditor reads the Cognos user catalog directly. The buyer side defence is the prepared user inventory reconciliation, with the documented retirement record and the active named user count tied to the HR record. See audit defense playbook and audit defense service.

Ready to put this work into practice?

An independent senior advisor on your IBM estate. No resell margin, no IBM relationship to protect, no time pressure to push a product. Just the buyer side view.

Schedule a consultation All services