IBM PVU to VPC Transition | White Paper

The Short Version

If you read nothing else

Bottom Line

IBM is shifting from PVU to VPC across its software portfolio. The published conversion ratios favor IBM. Buyers who model both metrics, validate ILMT readiness, and refuse to accept the transition without negotiated ratios save 15 to 30 percent on the metric change alone. Buyers who accept the default conversion overpay.

Key Takeaways

Five conclusions

VPC is not PVU. Virtual Processor Core counts cores in the virtual machine. PVU counted processor value units across the host. The math is different.

Conversion ratios are negotiable. Published ratios are the opening offer, not the final. Push for ratios that reflect actual deployment.

ILMT still applies. Sub capacity rules still require ILMT under VPC. The 90 day rule still holds. Readiness is mandatory.

Audit risk shifts. Transition windows create audit risk. Document every workload before the transition. Audit posture is the defense.

Negotiate before transition. Transition timing is leverage. Refuse to convert in the same window as a renewal or audit.

Recommendations by Role

What to do this quarter

Chief Information Officer

Inventory every IBM PVU based deployment and map to VPC equivalent
Validate ILMT is collecting on every host before transition
Refuse to transition during an active audit cycle

Procurement

Demand the conversion ratio in writing before signing
Refuse default ratios for products you are right sizing
Negotiate the transition timing as separate from renewal

SAM and IT Operations

Run a 90 day ILMT report before any VPC measurement
Document every virtualization host and the cores assigned
Identify products where the metric change inflates exposure

The Framework

Eight ideas

1. The Metric Shift

IBM is moving from PVU (processor value unit, host based) to VPC (virtual processor core, VM based) across many products. The shift simplifies but changes economics.

2. PVU Recap

PVU counts processor value units per host. The PVU table assigns values by chip generation. Sub capacity allows licensing the VM rather than the host, with ILMT.

3. VPC Mechanics

VPC counts virtual cores assigned to the VM. The math is direct. The minimum core counts and rounding rules still favor IBM.

4. Conversion Ratios

IBM publishes conversion ratios from PVU to VPC. The published ratios favor IBM. Negotiate the ratio for products you actually deploy.

5. ILMT Under VPC

Sub capacity rules still require ILMT. The 90 day continuous collection rule still applies. Readiness is mandatory before any measurement.

6. Cloud Workloads

Cloud workloads under VPC have different rules than on premises. Confirm the VPC count for each cloud platform. Document workload mobility.

7. Audit Posture

Transition windows create audit risk. IBM may audit before transition to lock the PVU count, or after to validate the VPC count. Be ready for both.

8. The Negotiation

Conversion ratios are negotiable. Transition timing is leverage. Refuse to transition in the same window as a renewal or audit. Stage the change.

Reference

Acronyms

PVUProcessor Value Unit

VPCVirtual Processor Core

ILMTIBM License Metric Tool

SAMSoftware Asset Management

VMVirtual Machine

ELAEnterprise License Agreement

Methodology & Sources

This white paper draws on Redress Compliance engagements, public vendor documentation, and the active Redress benchmark program.

About the Author

Morten Andersen

Co Founder, Redress Compliance

Connect on LinkedIn →

Vendor Advisory

Cloud & Emerging

Programs

Assessments

Research

Knowledge Hubs

Assessment Tools

IBM PVU to VPC Transition: A Buyer Playbook

Apply it to your IBM situation.