IBM PVU Optimization: $4.2M Avoided

The Situation

A global manufacturing group with facilities across North America, Europe, and Asia Pacific had been running IBM middleware and database software — including IBM WebSphere Application Server, IBM Db2, and IBM MQ — for over a decade. The group's IBM estate had grown organically through acquisition, with licences purchased across four separate subsidiary entities under different Passport Advantage agreements over an eight-year period.

When the group's IT finance director initiated a software asset management review ahead of an infrastructure consolidation programme, the internal SAM team identified what appeared to be a significant mismatch between the group's IBM Processor Value Unit (PVU) entitlements and the PVUs consumed by its virtualised server estate. An initial internal estimate placed the potential compliance exposure at approximately $4.2M — based on IBM's standard PVU sub-capacity pricing for the server configurations in use.

Before engaging with IBM, the group's procurement director brought in IT Negotiations to conduct an independent assessment. This decision proved critical — our team identified multiple errors in the internal PVU calculation methodology before a single conversation had taken place with IBM's licence compliance team.

The Challenges

IBM PVU licensing is among the most technically complex in the enterprise software market. Our team identified four distinct issues that had each contributed to the inflated internal exposure estimate:

• Incorrect full-capacity PVU application in a sub-capacity eligible environment. The internal SAM team had calculated PVU consumption using full-capacity methodology — counting every physical processor core in each server. However, the group's VMware vSphere environment was eligible for IBM's sub-capacity licensing under ILMT (IBM Licence Metric Tool), which allows PVU calculation based only on the virtual processor cores allocated to each VM. This single error accounted for the majority of the $4.2M estimate.
• ILMT deployment gaps in acquired entities. IBM's sub-capacity licensing requires continuous ILMT deployment and data retention. Three of the four subsidiary entities — all acquired in separate M&A transactions — had not had ILMT deployed for sufficient periods to qualify for sub-capacity treatment under IBM's standard policy. Without remediation, IBM's position would default to full-capacity calculation for those entities, eliminating the PVU reduction.
• PVU table version mismatches. The internal calculation had used an outdated IBM PVU table that had since been revised. Several server processor types used by the group had their PVU values changed in subsequent IBM PVU table releases — in most cases favourably. The internal estimate had applied higher PVU values than IBM's current table required.
• Entitlement consolidation opportunity across Passport Advantage agreements. Because each subsidiary entity held a separate Passport Advantage agreement, the group was unable to offset surplus entitlements in one agreement against shortfalls in another. IBM's consolidation process offered a mechanism to address this — but only if engaged proactively before any formal compliance discussion commenced.

Our Approach

IT Negotiations deployed a two-person specialist team: an IBM licensing expert with deep ILMT and sub-capacity methodology experience, and a commercial negotiator with a background in Passport Advantage restructuring. The engagement ran across four workstreams over 10 weeks.

Workstream 1 — Independent PVU Recalculation. We rebuilt the group's PVU calculation from the ground up using ILMT data from the entities where ILMT had been deployed correctly, and applying the current IBM PVU table. The corrected sub-capacity calculation reduced the apparent PVU consumption by 38% versus the internal full-capacity estimate — transforming the compliance gap into an entitlement surplus in two of the four entities.

Workstream 2 — ILMT Remediation for Acquired Entities. For the three entities where ILMT had not been deployed continuously, we worked with the group's infrastructure team to deploy ILMT across the remaining estate and establish a compliant data retention posture. We then prepared a technical narrative for IBM explaining the acquisition history and the ILMT deployment gaps as a consequence of post-acquisition integration timelines — a framing IBM's licence compliance team accepted in lieu of defaulting to full-capacity calculation for the affected entities.

Workstream 3 — PVU Table and Configuration Corrections. We identified seven server types in the group's estate where the IBM PVU table had been updated since the internal estimate was prepared. Applying the correct, current PVU values reduced the calculation further. We also identified two server configurations where the physical processor type had been miscategorised — each running at a lower PVU value than the internal estimate had assumed.

Workstream 4 — Passport Advantage Consolidation. Working with IBM's licence compliance and Passport Advantage teams, we negotiated a consolidation of the group's four separate Passport Advantage agreements into a single enterprise agreement. This allowed surplus entitlements from two entities to offset the residual shortfalls in the other two — eliminating the compliance gap entirely at zero cost. For more on how IT Negotiations approaches IBM engagements, see our IBM advisory service page and audit defence capability.

The Results

The group's $4.2M IBM PVU compliance exposure was resolved at zero cost — with no new licence purchase, no retrospective payment, and IBM's acceptance of the group's ILMT deployment posture as compliant going forward. The engagement produced four material outcomes:

The group now operates with a single consolidated Passport Advantage agreement, correct ILMT deployment across its entire estate, and a documented sub-capacity licensing posture reviewed and accepted by IBM. The annual licence cost for the IBM middleware and database estate was also reduced by approximately $680,000 per year as a result of the Passport Advantage consolidation — a benefit that will compound across each future renewal cycle.

The IT Finance Director noted that the fixed-fee engagement cost was recovered within the first year through licence cost savings alone, with the $4.2M liability avoidance representing the primary value case. This pattern — where the compliance risk avoidance dwarfs the advisory fee — is typical of IT Negotiations' IBM engagements. See our Software Audit Defence Playbook and the FinOps Maturity Model for further frameworks on managing enterprise licence risk.

Related Resources

Free guides for enterprises managing IBM licence complexity: