IBM PVU (Processor Value Unit) licensing is notoriously complex, but understanding how it works is the foundation for cost optimisation and audit defense. This guide walks through the complete PVU calculation methodology, processor factor tables, cost calculations, and 8 specific tactics to reduce IBM licensing costs through optimised deployment strategies.
Processor Value Unit (PVU) is IBM's licensing metric for middleware, database, and enterprise software products. Rather than licensing per-user or per-server, IBM licenses based on processor computing power.
Each processor type (Intel Xeon, AMD EPYC, IBM Power, etc.) is assigned a PVU factor — a multiplier representing relative processing power. The total PVU requirement for a deployment is the number of processors multiplied by their PVU factor.
Example: If you deploy IBM Db2 on a server with 4x Intel Xeon Platinum processors (100 PVU factor each), your PVU requirement is: 4 processors × 100 = 400 PVUs.
PVU factors are IBM's way of charging based on computing power. Higher-power processors have higher PVU factors, meaning higher licensing costs. This creates direct cost linkage to infrastructure decisions.
The basic formula is simple:
Want independent help negotiating better terms? We rank the top advisory firms across 14 vendor categories — free matching, no commitment.
Total PVUs = Number of Processors × PVU Factor per Processor
If you're deploying across multiple servers, sum the PVU requirements:
Server 1: 2x Intel Xeon Gold (24 cores) = 2 × 80 = 160 PVUs
Server 2: 2x Intel Xeon Platinum (32 cores) = 2 × 100 = 200 PVUs
Server 3: 4x AMD EPYC (128 cores) = 4 × 120 = 480 PVUs
Total: 160 + 200 + 480 = 840 PVUs
IBM publishes PVU factors for all supported processors. These are updated periodically as new processors are released. The following table shows common processors and their factors (2026 rates; verify current rates with IBM):
| Processor Type | Architecture | PVU Factor | Notes |
|---|---|---|---|
| Intel Xeon Platinum (3rd+ Gen) | Ice Lake / Sapphire Rapids | 100 | High core count, premium pricing |
| Intel Xeon Gold (3rd Gen+) | Ice Lake | 80 | Mid-range x86 processors |
| Intel Xeon Scalable (2nd Gen) | Cascade Lake | 70 | Older generation, lower factor |
| AMD EPYC 7002+ | Rome / Milan | 120 | High core density, aggressive pricing |
| IBM Power9 | POWER9 | 100 | IBM proprietary processors |
| IBM Power10 | POWER10 | 120 | Latest IBM processor |
Important: Always verify current PVU factors with IBM or your license administrator. PVU factors change as new processors are released. Using old factors in cost projections leads to significant errors.
Most IBM products have minimum licensing requirements. Common minimums:
Get the IT Negotiation Playbook — free
Used by 4,200+ IT directors and procurement leads. Oracle, Microsoft, SAP, Cloud — all covered.
Example with minimum: A single-processor system with a Xeon Gold (80 PVU factor) would normally require 80 PVUs. But with a 100 PVU per-processor minimum, you must license 100 PVUs. The minimum adds 25% cost premium for underutilised systems.
Once you know your PVU requirement, calculate total cost:
Total Cost = Total PVUs × Price per PVU × Term Length (years)
For example: 840 PVUs × $500/PVU = $420,000 per year. Over a 3-year term: $1,260,000 total.
Price per PVU varies significantly by product, volume, and negotiation. Enterprise list price is typically $400–$600 per PVU; negotiated prices are commonly $200–$400 per PVU depending on volume and competitive pressure.
While IBM controls official PVU factors, you can negotiate factor reductions as part of renewal agreements. Request reductions of 5–10% based on volume, multi-year commitment, or competitive alternatives. Even 5% factor reduction saves 5% annually.
Minimums are often negotiable. If your calculated PVU is 600 but IBM's 400 minimum applies, you're paying premium on 400 underutilised PVUs. Push to align minimums with actual deployment.
If you deploy IBM software on only some processors in a multi-processor system (using partitioning, containers, or VM isolation), negotiate to pay for only those processors. This requires technical controls and IBM approval, but saves 30–40% for targeted deployments.
Before purchasing new hardware, calculate IBM licensing costs. A processor upgrade that improves compute 20% might increase IBM licensing costs 40%. Consider the total cost of ownership, not just hardware. Sometimes staying on current hardware is more cost-effective than upgrading.
AMD EPYC processors typically have higher PVU factors than Intel Xeon, but offer better price-to-performance hardware costs. Evaluate whether hardware cost savings offset higher IBM licensing costs. For some workloads, Intel provides better total economics.
Consolidating multiple lower-capacity systems onto fewer high-capacity systems might reduce total PVU count if utilisation improves. However, verify this before consolidating — moving from 5×100 PVU systems (500 total, meeting minimums) to 2×250 PVU systems (500 total) provides no savings.
IBM sometimes applies incorrect PVU factors to invoices or usage reports. Audit your latest IBM bill to verify factors match current IBM-published factors. Errors 5–10% are not uncommon and worth recovering.
The per-PVU price is often more negotiable than PVU factor itself. High-volume organisations should benchmark their per-PVU cost and push for competitive rates. Enterprise list price might be $500/PVU; negotiated price for strong customers can be $250/PVU.
PVU factors change annually. New processor generations often get lower factors. Using a 2024 factor for a 2026 processor costs you 10–15% in unnecessary licensing. Always use current IBM PVU tables.
PVU is calculated per processor (socket), not per core. A 2-socket server with 16-core processors has 2 processors, not 32. Common mistake: counting cores and dividing by cores/processor, then multiplying PVU factor by cores.
Minimum requirements apply even if calculated PVUs are low. Not accounting for minimums creates cost projection errors of 30–50% for small deployments.
List price PVU calculations overstate actual costs. If you've negotiated 40% discount from list price, use discounted rates in cost projections. Using list price in planning creates unnecessary budget cushions.
Understanding PVU licensing is the foundation for cost optimisation and audit defense. Let us match you with an IBM licensing specialist.