Processor Value Units (PVUs) are IBM's primary licensing metric for enterprise software. Whether you're deploying IBM WebSphere Application Server, DB2, Informix, SPSS, or Enterprise Content Management, IBM measures your license consumption in PVUs. Despite being IBM's most-used metric, PVU licensing remains widely misunderstood by enterprise buyers, leading to over-licensing, audit exposure, and millions of dollars in avoidable costs.
This guide explains how PVU licensing actually works, how to calculate your PVU requirements, the critical distinction between full-capacity and sub-capacity licensing, ILMT deployment requirements, and the negotiation strategies that produce meaningful cost reduction.
What Is IBM PVU Licensing?
A Processor Value Unit is IBM's attempt to create a standardized metric for licensing software across heterogeneous server architectures. Instead of charging per-core (where all cores are treated equally), IBM charges per-PVU, where the number of PVUs per physical core depends on the processor type, generation, and speed.
Why? IBM's rationale is that a modern Intel Xeon processor is more powerful than an older Intel processor, so it should cost more per core. The PVU model attempts to normalize for this difference. In practice, it's a mechanism that increases IBM's pricing flexibility and complexity — and shifts the burden of interpretation onto the buyer.
IBM publishes official PVU conversion tables that specify the PVU value for each processor type. A typical conversion looks like this: Intel Xeon Platinum 8280 (28 cores) = 100 PVU per core. IBM Power E1050 (32 cores) = 140 PVU per core. The conversion is based on the processor's theoretical compute power, but IBM updates these tables quarterly, sometimes raising values for existing processor generations.
PVU licensing applies at the server level. If you have a physical server with 16 cores rated at 100 PVU per core, your full-capacity licensing requirement is 1,600 PVUs — regardless of whether you're using 2 cores or all 16.
How PVU Values Are Assigned
IBM maintains comprehensive PVU conversion tables, but the basics are these: Intel Xeon processors typically range from 70–120 PVU per core depending on generation. AMD EPYC processors are generally 80–110 PVU per core. IBM POWER processors (used in Power Systems) are typically 100–150 PVU per core. Older Intel Xeon E5 generation processors are rated at 70–80 PVU per core.
IBM's PVU table distinguishes between processor families, generations, and even specific SKUs. A 3rd-generation Intel Xeon Platinum 8280 is rated differently than a 2nd-generation 8280. The differences are often subtle — 5–15% variations — but across a large deployment, they compound.
Here's the critical problem: you must use the PVU value that corresponds to the specific processor installed on your server, not the processor your server model "typically" includes. Two servers of the same model may ship with different generation Xeons depending on availability when they were ordered. If you assume a lower PVU value than what's actually installed, you'll be under-licensed, triggering audit exposure.
To determine your PVU value accurately: use your server's CPU model number (visible in BIOS or via system utilities like `dmidecode` on Linux), cross-reference it against IBM's official PVU conversion table, and confirm the result with your IBM account team or licensing advisor before committing to a contract.
Full Capacity vs Sub-Capacity Licensing
This is the most important distinction in PVU licensing, and where most enterprises make expensive mistakes.
Full-Capacity Licensing means you pay for all processor cores in the physical server, regardless of how many cores are actually consumed by IBM software. If you have a 32-core server with 100 PVU per core, you owe IBM 3,200 PVUs, even if IBM software only runs on 4 cores.
Sub-Capacity Licensing allows you to pay only for the processor cores allocated to the logical partition (LPAR) or virtual machine running IBM software. If that same 32-core server is partitioned into four 8-core LPARs, and IBM software runs on only one partition, you pay for 8 cores × 100 PVU = 800 PVUs instead of 3,200 PVUs.
In virtualized and cloud environments, sub-capacity licensing can reduce your PVU obligation by 50–80%. This is why it matters so much.
The critical requirement: To claim sub-capacity licensing, you must deploy and properly configure IBM License Metric Tool (ILMT). Without ILMT running continuously and reporting data to IBM, you lose the right to sub-capacity licensing and default to full-capacity. IBM will enforce this during audits without exception.
ILMT: The Sub-Capacity Prerequisite
IBM License Metric Tool (ILMT) is IBM's software agent that monitors processor allocation in real time. For sub-capacity licensing to be valid, ILMT must:
- Be installed and running on every server where IBM software executes
- Continuously monitor the number of processor cores allocated to the partition/VM running IBM software
- Report data to IBM on at least a weekly basis
- Maintain historical records for at least 90 days
- Accurately identify which IBM products are running on each partition
If ILMT is not deployed, not running, or misconfigured, you cannot claim sub-capacity licensing. Period. IBM auditors will verify ILMT deployment as the first step in any audit. If they find ILMT is missing or non-functional, they'll immediately classify your environment as full-capacity and calculate your liability based on all cores in the physical server.
Common ILMT failures include: deployment only on production servers (but not dev/test); ILMT installed but data collection disabled; ILMT reporting gaps (weeks or months where data wasn't transmitted to IBM); ILMT misconfigured to report incorrect partition sizes; and ILMT not updated to recognize new processor types or new product releases.
We've seen clients assume they're on sub-capacity licensing for years, only to discover during audit that ILMT was non-functional for half that period. The audit settlement then covers the entire lookback period — often 2–5 years of back-payments at full-capacity rates.
PVU in Virtualized and Cloud Environments
PVU licensing becomes exponentially more complex in virtualized infrastructure. IBM distinguishes between different types of virtualisation:
Physical partition (LPAR on Power Systems, zones on Solaris): Counted as cores allocated to the partition at all times. If a partition has 8 cores allocated (even if idle), you pay for 8 cores.
VMware vSphere or Hyper-V VMs: Counted as cores allocated to the VM. IBM measures this via ILMT integration with the hypervisor. IBM counts the vCPU allocation at the time of audit snapshot, not the peak usage.
AWS, Azure, or IBM Cloud: IBM charges per-core per-month based on the instance size you select. No ILMT required. IBM Cloud offers the most favorable PVU rates (20–30% discount vs on-premises), but you pay whether the instance is running or idle.
Container/Kubernetes deployments: This is IBM's newest gray area. ILMT support for containerised deployments is incomplete. If you run IBM software in containers, you may not be able to claim sub-capacity. Clarify this with IBM before deploying.
Hybrid environments (some workloads on-premises, some on cloud) require careful auditing. IBM will audit both environments separately, and the rules differ. On-premises deployments must have ILMT. Cloud deployments use per-core-month charges. Ensure you're tracking both separately and neither over- nor under-licensing.
How IBM Audits PVU Compliance
During a Software Compliance Review, IBM auditors will:
First, verify ILMT deployment. They'll request reports showing ILMT is installed, running, and reporting data. If ILMT is missing or broken, the audit immediately defaults to full-capacity calculations.
Second, they'll reconcile deployed software against your licensed software. ILMT should show which IBM products are running on which servers. IBM will compare this to your license agreement and any point-product licenses.
Third, they'll measure peak usage. For sub-capacity environments, IBM uses 30-minute polling intervals. The peak usage in any 30-minute window during the audit period (typically 90 days) becomes the basis for licensing calculations. Even a brief workload spike drives your entire licensing requirement.
Fourth, they'll calculate exposure. If your peak usage exceeded your licensed capacity, IBM will demand payment for the overage — plus interest and audit fees (typically 5–10% of the settlement amount).
Fifth, they'll look for shadow IT and unlicensed deployments. IBM often discovers IBM software running on servers you didn't realise were covered by IBM licensing (development boxes, BI servers, test environments). These become additional exposure.
Strategies to Reduce PVU Costs
Right-size and consolidate workloads. Before you deploy IBM software on a large number of small VMs, consolidate to fewer, larger partitions. This reduces the total PVU footprint. If you can move 10 separate 4-core VMs to a single 16-core logical partition, you reduce PVU count from 10×4 to 1×16 (assuming the processor type remains the same).
Move to IBM Cloud. IBM Cloud PVU rates are 20–30% lower than on-premises. If your workload is variable or spiking, Cloud can be significantly cheaper because you only pay for cores actually used in any given month. On-premises full-capacity licensing requires you to provision for peak demand even if peak only occurs for a few hours per month.
Implement license harvesting. Review your active IBM software deployments. Kill off pilot projects, development-only instances, and workloads that could be migrated to alternative platforms (open-source, cloud-native, or competing vendors). Each core you decommission reduces PVU liability.
Negotiate via ELA. If your current spending is high, negotiate an IBM Enterprise License Agreement (ELA) with embedded escalation caps and flexible capacity allowances. ELA pricing is typically 30–45% below point-product rates, and a well-negotiated ELA includes growth provisions that allow you to add capacity at the current contract rate rather than paying mid-term upgrade penalties.
Use sub-capacity aggressively. Ensure ILMT is deployed everywhere, running correctly, and configured to report the most granular partition/VM allocation. The more accurately you measure sub-capacity, the lower your liability.
Common PVU Licensing Mistakes
Not deploying ILMT. This is the #1 mistake. Organisations assume they're on sub-capacity when they're actually on full-capacity because ILMT was never deployed. The cost difference is typically 200–400%.
Assuming processor types. You must use the actual PVU value for the processor installed on your server, not the processor type listed in the server's data sheet. Verify via system utilities and cross-reference against IBM's official PVU table.
Misconfiguring partitions or VMs. If ILMT is configured to report incorrect core allocations, your sub-capacity calculation is wrong. Audit and validate your partition/VM core assignments quarterly.
Counting development and test. Development, test, and UAT environments require the same licensing as production — they count toward your PVU total. If you're deploying IBM software in 10 separate environments (dev, test, staging, production across multiple regions), all 10 count. Plan accordingly.
Ignoring shadow IT. IBM discovers IBM software running on servers you didn't realise were covered. Conduct a thorough software inventory audit annually. Use ILMT to generate reports of all IBM software running in your environment.
FAQ
Can I move IBM software between servers without re-licensing? No. Each unique server (identified by hardware serial number and processor configuration) is a separate licensing entity. If you move IBM software from a 16-core server to a 32-core server, your PVU requirement increases. However, if you move the software to a logical partition on the same physical server, the PVU count remains the same (the partition core count, not the physical server count, determines licensing).
What happens if my workload varies seasonally? IBM uses peak usage in any 30-minute window across the audit period. If your workload is 4 cores in winter and 16 cores in summer, you're licensed for 16 cores year-round. If you can forecast seasonal demand, consider moving to IBM Cloud for the peak-demand season and turning off on-premises capacity — this could reduce annual PVU cost by 30–40%.
Are there any processor types with lower PVU rates? Older processor generations (Intel Xeon E5, AMD Opteron) have lower PVU values, but they're being phased out of datacenters. They're not a cost-saving strategy; they're an end-of-life reality. Don't hold onto old hardware for licensing purposes.
Can I negotiate PVU rates directly with IBM? No. IBM's PVU metric and conversion table are fixed — you cannot negotiate the underlying PVU value per core. However, you can negotiate discount rates applied to PVU consumption (e.g., 35% off standard PVU pricing) through an ELA or point-license agreement. This is where your negotiating leverage lies.