A PVU, or Processor Value Unit, is the unit IBM uses to measure and license software based on server processing power rather than the number of people using it. If your IBM Cognos Analytics or Planning Analytics environment is licensed this way, IBM cares about the cores in your server, not the headcount accessing it.
That distinction sounds simple, but it drives real cost decisions: which servers you can put Cognos on, whether a sub-capacity agreement is worth negotiating, and whether it still makes sense to license PVUs at all now that IBM offers a SaaS path.
What Does a PVU License Actually Cover?
A PVU license is assigned to the Analytic Server and grants access to the basic server functions that other Cognos user roles depend on. The number of PVUs you owe is based on the number of activated processor cores available to the program, multiplied by a PVU-per-core rating that IBM assigns to that specific processor.
Not every core is priced the same. IBM's rating depends on processor vendor, brand, model, and how many sockets are in the server. Most modern x86 Intel Xeon and AMD EPYC cores rate at 70 PVUs on a 2-socket server, climbing to 100 or 120 PVUs per core on 4-socket and larger configurations. Older or non-Intel/AMD architectures, and higher-end POWER and System z chips, are rated separately. IBM publishes and updates the full PVU tables directly, so always check the current numbers before you budget: IBM's Processor Value Unit tables.
What Does a PVU Calculation Actually Look Like?
Here's a simplified version of the math, using IBM's currently published rating. A 2-socket server running a modern Intel Xeon or AMD EPYC processor rates at 70 PVUs per core. If that server has 8 cores per socket, that's 16 activated cores available to Cognos, so 16 cores multiplied by 70 PVUs equals 1,120 PVUs required for that server under Full Capacity licensing.
Bump that same workload up to a 4-socket server and the per-core rating jumps to 100 PVUs, even with the identical processor family, because IBM's tables price higher socket counts differently. That's the “oversizing” problem in a nutshell: doubling your sockets for future growth doesn't just double your PVU count, it can also push you into a higher per-core rate. It's one more reason to run the numbers before you finalize hardware, not after.
Do I Have to License PVUs for the Entire Server?
Not necessarily, but only if you've set up sub-capacity licensing correctly. If you oversized your hardware for future growth, licensing every physical core on that box (known as Full Capacity licensing) can cost far more than you expected. IBM's alternative is Sub-Capacity (Virtualization Capacity) licensing, which lets you license only the cores actually made available to Cognos in a virtualized environment, rather than every core on the physical server.
Sub-capacity is a real cost lever, but it comes with real requirements, and IBM has tightened enforcement on this in recent years. To stay eligible, you must run an eligible virtualization technology, use an approved tracking tool such as the IBM License Metric Tool (ILMT), HCL BigFix Inventory, or Flexera One, and keep that tool actively deployed and reporting. If ILMT (or an approved equivalent) isn't installed and reporting correctly, IBM can revoke your sub-capacity eligibility retroactively and bill you at full capacity for every core on the server. See the official Sub-Capacity Licensing Terms for the current requirements before you assume you qualify, and check our ILMT Questions and Answers post if you're not sure whether your current ILMT deployment actually meets them.
PVU vs. Authorized User: Which One Applies to You?
On-premises, several Cognos modules give you a choice between PVU and Authorized User licensing, and the two metrics answer completely different questions. An Authorized User license doesn't care how many cores your server has; IBM only counts named users. A PVU license doesn't care how many users you have; IBM only counts cores and their PVU rating.
TM1's Analytic Server, for example, has historically required a PVU-based license to function, regardless of how the rest of your environment is licensed. Other modules, like some Cognos Analytics consumer roles, let you pick either metric. As a rule of thumb: the more named users you have relative to your server capacity, the more the PVU model tends to cost-justify itself, and vice versa. Since IBM revises these terms by product and by agreement, confirm the current rules for your specific license using IBM's PVU licensing FAQs or talk to us before you assume last year's model still applies.
Does PVU Licensing Apply to Test and Dev Environments?
Yes, if you're on the PVU metric. Authorized User licenses let the program run on any number of computers or servers, with each authorized user able to access any number of instances at once, so there's typically no separate Non-Production license required. PVU licenses work differently: if users are accessing a Test or Dev environment, you need separate Non-Production PVU licenses for that environment. This is one of the most common compliance gaps we find during license reviews, because it's easy to stand up a test server and forget it needs its own entitlement. If you want the scenario-by-scenario version of this (gateway-only servers, mobile, Content Manager, and more), our Cognos Analytics PVU Q&A post walks through the specific edge cases we get asked about most.
Does Any of This Still Matter If You're Moving to SaaS?
For a growing number of Lodestar clients, no, and that's a meaningful shift since this post was first written. IBM Cognos Analytics on Cloud (the SaaS version) is priced per user, in Standard or Premium tiers, with IBM hosting and managing the infrastructure. There's no PVU calculation, no ILMT deployment, and no sub-capacity negotiation, because you're no longer licensing server capacity at all.
If you're still on-premises, PVU and Authorized User licensing remain very much in play, and understanding them is what protects you in an audit. If you're evaluating a move to SaaS, the PVU question becomes one of the reasons to make the switch rather than something to manage long-term. We've written more about what that migration path looks like in practice in our guide to migrating Cognos Analytics from on-premises to SaaS.
How Do I Calculate My PVU Requirement?
Start with IBM's own PVU calculator, which walks you through processor architecture, server vendor and brand, processor model, and core count to produce a PVU total. You'll want your hardware documentation on hand before you start; if you're not sure how to identify your processor model, IBM also publishes a model number discovery guide alongside the PVU tables.
In practice, most of the license reviews we run for clients turn up the same handful of issues: PVUs calculated against the wrong processor rating, sub-capacity claimed without current ILMT reporting to back it up, or Non-Production environments that were never separately licensed. Any one of those can turn into a costly finding in an IBM audit.
How Lodestar Solutions Can Help
PVU and Authorized User licensing decisions affect real budget and getting them wrong is the kind of mistake that surfaces at the worst possible time, during an IBM audit. If you want a second set of eyes on your Cognos Analytics or Planning Analytics licensing, or you're weighing whether a sub-capacity agreement or a move to SaaS makes more sense for your environment, our IBM Cognos Analytics team can walk through your specific setup with you. Schedule an advisor call and we'll help you figure out exactly where you stand.
