A comprehensive independent advisory on IBM Cognos Analytics, Planning Analytics (TM1), and Cognos Controller licensing, covering Authorized User, PVU, and VPC metrics, user role types, deployment models, compliance risks, and optimization strategies.
Executive Summary: IBM Cognos is a suite of analytics and performance management tools, including Cognos Analytics (BI and reporting), Planning Analytics (TM1, budgeting and forecasting), and Cognos Controller (financial consolidation). Understanding how these products are licensed is crucial for IT Asset Managers to optimize costs and stay compliant. Cognos licensing involves different deployment models (on-premises vs cloud), licensing metrics (Authorized User, PVU, VPC), distinct user roles, and multiple license types (perpetual, subscription, SaaS).
Organizations may use a mix of models, for example, running Cognos Analytics on-prem with PVU licenses while using Planning Analytics as a SaaS service. ITAM teams need to track both kinds of entitlements accordingly. IBM also allows deploying Cognos in containers via IBM Cloud Pak for Data, where licensing uses VPC (Virtual Processor Cores) instead of PVUs, a hybrid approach with subscription capacity licensing.
| Licensing Model | How It Works | Best For |
|---|---|---|
| Authorized User | Each individual who accesses Cognos must have their own named license. Licenses cannot be shared or pooled. No hard technical limit enforced by the software. Compliance is contractual. Example: 100 AU licenses = up to 100 active user accounts. | Known, stable user bases. Straightforward to track by counting users. |
| PVU (Processor Value Unit) | License the server capacity instead of users. IBM assigns a PVU value per core (based on CPU type). Example: 8 cores × 50 PVUs/core = 400 PVUs needed. Allows unlimited users. Compliance determined by not exceeding CPU capacity entitlement. | Large enterprises with high or fluctuating user counts where per-user licensing is impractical. |
⚠️ Compliance Warning — ILMT Requirement: If using PVU licensing on virtualized servers, IBM requires the use of the IBM License Metric Tool (ILMT) to monitor and report PVU usage. ILMT ensures you account for the correct number of virtual cores, especially for sub-capacity licensing. Failing to deploy ILMT could result in IBM defaulting your licensing to full physical capacity, a significant compliance risk that can dramatically increase required PVUs.
Not all users have the same level of functionality. IBM defines different user types that carry different license rights. Ensuring users are not given capabilities beyond their licensed role is critical. IBM audits will check role assignments against purchased entitlements.
| Role | Capabilities | Typical Users | License Cost |
|---|---|---|---|
| Analytics Administrator | Full administrative access. Manages servers, security, modeling, all platform features. Every environment needs at least one admin. | IT administrators, Cognos platform managers | 🔴 Highest |
| Analytics Explorer | Power user / advanced author. Can create and edit reports, dashboards, use most advanced features. Cannot perform system administration. | Business analysts, report developers | 🟡 High |
| Analytics User | Standard user. Can interact with content, create simple dashboards/explorations, save personal content. More limited than Explorer. | Business users who create basic reports | 🟡 Medium |
| Analytics Viewer (Consumer) | Read-only. Can view dashboards and reports created by others. Cannot create new content. | Executives, managers, broad report consumers | 🟢 Lowest |
| Analytics for Mobile | Mobile app access only. Typically counts as a Viewer in many agreements. View content via mobile devices. | Field teams, mobile-only users | 🟢 Lowest |
🚨 Critical Risk — Role Misassignment: If a Viewer-level user is accidentally granted Explorer capabilities, that person consumes an Explorer license entitlement. The Cognos system's "Manage > Licenses" feature provides a usage report to help administrators track this. Legacy note: Before the current model, IBM used terms like "Business Author" and "Enhanced Consumer." These have been simplified into the above roles. Ensure you map old license documents to current role definitions if you've upgraded or mixed entitlements.
In IBM's Cognos Analytics on Cloud offerings, licensing is subscription-based and user-counted. You subscribe to named user seats (e.g. Viewer seat vs. Analytics User seat). IBM manages all backend capacity, so you don't directly worry about PVUs. The system may enforce user counts. You won't be able to exceed enabled users without purchasing more. However, you should still internally govern role assignments, as having every user set as Administrator when only a few admin licenses were purchased would violate your terms.
Planning Analytics on-prem requires BOTH server capacity licenses (PVUs) AND user licenses (Authorized Users). This is not either/or. You must have enough of both. For instance, a company might own 1,000 PVUs of Planning Analytics and 200 user licenses to support deployment. Failing to license either dimension is a compliance gap.
| Deployment | Metric | How It Works |
|---|---|---|
| On-Premises (Local) | PVU + Authorized User | TM1 server engine licensed by PVU (based on server cores, tracked with ILMT). Every user who accesses Planning Analytics also needs an Authorized User license, regardless of role (modeler, contributor, or read-only). No "free read-only" user exists. |
| Cloud (SaaS) | User Subscription | IBM charges per user subscription. The subscription covers the TM1 server in IBM Cloud. You don't separately license PVUs. You manage user access so you don't exceed your subscription count. IBM provides an admin portal for adding/removing named users. |
| Hybrid / Bridge | Mixed | IBM offers "bridge to cloud" programs to convert on-prem licenses into cloud subscriptions with credits. May grant dual entitlement (both on-prem and cloud) during transition, but this is temporary. Inventory current entitlements carefully to avoid paying twice. |
⚠️ Compliance Warning — Planning Analytics User Counting: Unlike Cognos Analytics, Planning Analytics does not have multiple named user role flavors with different pricing. All users, whether modelers who design cubes or contributors who only input data, consume one Authorized User license each. A company with 3 administrators/modelers and 20 contributors needs 23 Authorized User licenses. If someone leaves, you can reassign their license to a replacement after removal.
| Aspect | On-Premises | Cloud (SaaS) |
|---|---|---|
| Metric | Authorized Users (named users). IBM differentiates between Administrator users and Standard (Contributor) users, separate SKUs, often at different costs. | User subscription. IBM typically does not distinguish between admin and regular users for pricing. All count the same. |
| Example | 2 Administrator + 20 Standard User licenses. No more than 2 users should have the Controller admin role; no more than 20 standard users. | 22 user subscriptions. Any user can be assigned admin rights as needed without a separate license type. |
| Enforcement | Controller may not enforce the count in software. It's on the honor system and subject to audit. Use built-in License Management report (v10.4.1+) or manually count active users. | System may enforce user limits. Simpler. No need to worry about admin vs standard license breakdown. |
| Concurrent Licensing | Not used in modern agreements. IBM primarily uses named-user (Authorized User) model. If you have an older contract mentioning concurrent users, manage by monitoring peak simultaneous usage. | Named-user model. Subscription count = max users. |
| Metric | What It Is | Applies To | Key Considerations |
|---|---|---|---|
| Authorized User (AU) | Named-user licensing. Each person who uses the software (directly or indirectly) needs a license. Cannot be shared or transferred except when permanently reassigning to a replacement. | All Cognos products (Analytics, Planning, Controller) | Track the list of individuals with access. Software may allow unlimited account creation. Governance is needed. Even indirect users (e.g. certain report recipients) may need licenses. |
| PVU (Processor Value Unit) | Server capacity measure. IBM assigns a PVU value per core depending on processor model (common: 50, 70, 100 PVUs/core). Total = PVU per core × number of cores allocated to software. | Cognos Analytics (BI), Planning Analytics (TM1 server) | Allows unlimited users. ILMT required for sub-capacity (virtualized) licensing. Without ILMT, IBM defaults to full physical capacity, dramatically increasing PVUs needed. |
| VPC (Virtual Processor Core) | Newer metric for cloud/container environments. Equivalent to one virtual CPU core allocated to the software. Used with IBM Cloud Paks. | Cognos Analytics via Cloud Pak for Data | Easier to calculate in virtualized environments than PVU. VPC and PVU are separate metrics. Cannot directly convert without IBM approval. Specific to Cloud Pak / container deployments. |
| Risk Area | What Happens | Risk | How to Mitigate |
|---|---|---|---|
| Exceeding Authorized User Counts | More user accounts than licenses. New users added without purchasing additional licenses. Sharing accounts (two people using one login) violates terms. | 🔴 High | Quarterly user count audits. Ensure each real user has their own license. No generic accounts for multiple people. |
| Incorrect Role Assignments | Granting a user higher capabilities than their license type (e.g. a Viewer given Explorer access). IBM audits examine capabilities and roles of every user. | 🔴 High | Use Cognos "Manage > Licenses" report regularly. Map user groups to license types. Apply principle of least privilege. |
| Distributing Content to Non-Licensees | Interactive reports (e.g. Active Reports) sent to people without Cognos licenses. Static PDFs/printed reports are generally fine. Interactive content requires licensed recipients. | 🟡 Medium | Policy: only share interactive reports with licensed users. Train report authors on which distribution formats are allowed. |
| Processor Capacity Overuse | Running Cognos on more cores or more powerful hardware than licensed. Upgrading hardware or allocating more virtual CPUs without adjusting licenses. | 🔴 High | Always use ILMT for PVU/VPC tracking. Review ILMT reports when making infrastructure changes. Update license counts before hardware upgrades. |
| Missing or Misconfigured ILMT | Not having ILMT deployed is itself a compliance issue. IBM defaults to full physical capacity licensing, potentially multiplying your costs. | 🔴 High | Deploy ILMT within 90 days of Cognos deployment. Keep it active. Regularly check dashboards. Retain quarterly reports (minimum 2 years). |
| Planning Analytics Dual Licensing Gap | Licensing only one dimension (users but not server PVUs, or vice versa). An audit will check both independently. | 🔴 High | Treat Planning Analytics as needing two compliance checks: AU count AND PVU/core capacity. Monitor both continuously. |
| Controller Admin Account Overuse | Created 3 admin accounts on-prem but only purchased 1 Administrator license. Software may not enforce the count. Audit will catch it. | 🟡 Medium | Use Controller's License Management report (v10.4.1+) to separate admin and standard user counts. Limit admin account creation. |
| Ghost Instances in ILMT | Retired Cognos servers still appearing in ILMT tracking. Makes it look like you're using more capacity than you are. | 🟡 Medium | When decommissioning servers, remove them from ILMT. Keep documentation showing the old system was decommissioned. |
🚨 Critical Risk — Active Report Distribution: Example scenario: A company bought 100 Cognos Analytics Viewer licenses. One analyst creates an interactive Active Report and sends it to 500 other employees. Those employees don't log into Cognos, but because the Active Report allows slicing and dicing data offline, IBM considers that usage requiring a license. In an audit, IBM could demand 500 additional Viewer licenses. Static PDFs or printed reports can go to anyone, but interactive content must stay with licensed users.
| # | Recommendation | Priority |
|---|---|---|
| 1 | Maintain a central license inventory. Keep an up-to-date record of all IBM Cognos entitlements: number of Authorized Users by type (Viewer, User, Explorer, Admin), PVU/VPC entitlements, which contracts they come from, and subscription expiration dates. | 🔴 Critical |
| 2 | Deploy ILMT for all PVU/VPC-based licenses. Ensure ILMT is scanning all relevant servers. Check reports regularly for accuracy. Set up alerts if PVU consumption approaches your licensed amount. Required for sub-capacity compliance. | 🔴 Critical |
| 3 | Audit user accounts quarterly. Use Cognos "Manage > Licenses" to compare users in each role against entitlements. Review Planning Analytics clients/user lists. Check Controller's License Management report. Disable inactive accounts (6+ months without login). | 🔴 Critical |
| 4 | Align user roles with license types. Create directory groups mapped to license types (Cognos_Admins, Cognos_Explorers, etc.). Apply principle of least privilege. Give users only the capabilities they need. Prevents accidental role elevation. | 🟡 High |
| 5 | Educate stakeholders on licensing rules. Train report authors on which distribution methods are allowed. Inform IT teams not to spin up new Cognos environments without involving ITAM. Communicate policies on Active Report distribution. | 🟡 High |
| 6 | Monitor usage and optimize. Track how Cognos is actually used. Identify underutilized Viewer licenses or unused Explorer allocations. Reduce renewal counts for subscriptions or decide not to renew support on perpetual licenses not needed. | 🟡 High |
| 7 | Plan for cloud transitions. If moving from on-prem to IBM cloud, engage IBM early about how existing licenses can be transitioned. IBM may offer credits for perpetual licenses toward SaaS subscriptions. Document all agreements and update inventory. | 🟡 High |
| 8 | Keep Proof of Entitlement documents. Store all IBM Passport Advantage certificates, invoices, and correspondence in a central repository. Invaluable in case of audit or if ITAM team turns over. | 🟡 High |
| 9 | Prepare an audit response plan. Identify who gathers ILMT data, who pulls user lists, and who interfaces with auditors. Having this mapped out in advance means you can respond calmly and completely when IBM requests a Software License Review. | 🟡 High |
| 10 | Engage independent licensing experts. If managing IBM Cognos licensing becomes complex, consider independent IBM licensing advisors who can provide tailored guidance, identify optimization opportunities, and assist with audit preparation. | 🟡 High |
Watch how we help enterprises navigate IBM licensing challenges and cut costs
Redress Compliance provides fully independent IBM license management, from compliance assessments and audit defense to ELA renewals and contract negotiation. No IBM affiliation. We work exclusively in your interest.
IBM Advisory Services Book a ConsultationSee how we help enterprises eliminate IBM licensing risks and cut millions
Download our in-depth guides covering IBM audit defense, PVU optimization, and license management strategies
Read our comprehensive IBM license models guide
Explore all IBM licensing guides, case studies, and resources