Why this guide exists.
IBM publishes thousands of pages of licence terms. The contractual perimeter spans the International Passport Advantage Agreement, the IBM Customer Agreement, the License Information document for each product, the typical Enterprise Agreement amendment stack, and the operational guidance for sub capacity, ILMT, and the IBM Licence Service. The buyer side reading this material in real time, against an active deployment or an active negotiation, is at a structural disadvantage.
The aim of this pillar guide is a single coherent reference for the buyer side. It is not a substitute for the contract. It is a compressed map that points to the right contractual reference, the right operational discipline, and the right next step. The guide is written from the chair of an independent advisor. We do not sell IBM software. We have no resell margin. The view that follows reflects the buyer side interest only.
If you want a faster orientation by topic, the IBM Licensing FAQ answers the most common single point questions. For the product specific reference, see the IBM Product Licensing Guide. For the sub capacity specific reference, see Sub Capacity Explained.
1. The IBM commercial programmes.
Almost every commercial IBM software relationship sits inside one of three programme structures: Passport Advantage, Passport Advantage Express, or an Enterprise Agreement.
Passport Advantage.
The default programme for mid market and enterprise buyers. The framing contract is the International Passport Advantage Agreement. Entitlement is purchased by Suggested Volume Point band. The buyer accrues volume to drive into the next discount band. Support and Subscription (S and S) renews annually. Most product families across IBM software are sold under this programme.
Passport Advantage Express.
The small footprint version of the same programme. The terms are similar but the volume band entry points are lower. Express buyers cannot stack into the same discount tier as enterprise buyers. The Express agreement is rarely the right vehicle once a buyer crosses the medium enterprise threshold and the migration to standard Passport Advantage is itself a negotiation event.
Enterprise Agreement.
The bespoke contract that sits on top of Passport Advantage. The EA amends the standard PA terms for the duration of the agreement and typically introduces a multi year commitment, a fixed discount schedule, custom metrics, fixed S and S uplift, or a true up and true down framework. The EA is the document that most materially affects the buyer side over the multi year horizon. The negotiation of the EA is a discrete advisory engagement, separate from the operational compliance work. See contract negotiation for the full advisory frame.
The IBM Customer Agreement (ICA) sits beneath both. It is the standing legal frame for the IBM relationship and is rarely re negotiated in the same cycle as the commercial documents.
2. The IBM licence metrics.
The licence metric is the unit of entitlement. The same product is frequently available under multiple metrics, and the right choice is a buyer side decision. The defining metrics across the IBM portfolio are:
| Metric | What is counts | Where it is used |
|---|---|---|
| PVU | Processor Value Units. Per core, weighted by chip type. | Most middleware and analytics products. Sub capacity eligible. |
| VPC | Virtual Processor Core. One per virtual CPU, with sub capacity allowed. | Cloud Paks, modern middleware, watsonx product family. |
| RVU | Resource Value Unit. Counted on a defined resource scale. | Storage, networking, security products. |
| UVU | User Value Unit. Counted by user with tiered scaling. | Collaboration, document, and some analytics products. |
| Authorized User | Named, identified user. | Cognos, DataStage, some Db2 editions. |
| Concurrent User | Simultaneous user. | Some legacy collaboration products. |
| Server | Per physical server. | Some appliances and a small set of legacy products. |
| MSU | Million Service Units per hour, four hour rolling peak. | System z Monthly License Charge software. |
| Engine | Per database engine instance. | Some Informix and DataStage configurations. |
| RU | Resource Unit. Variable scale per product. | watsonx.ai inference and training capacity. |
For PVU based products the per core weighting depends on the chip type. The IBM PVU optimisation work is the buyer side discipline of choosing the right hardware for the workload to minimise the PVU count at no operational cost. For VPC products the count is one per vCPU and the sub capacity treatment is automatic once the IBM Licence Service is correctly deployed. For mainframe MLC the four hour rolling peak determines the monthly charge and the mainframe licensing work is largely about controlling that peak.
3. Sub capacity licensing and ILMT.
Sub capacity is the entitlement framework that allows a customer to license a product to the virtual CPU footprint rather than the full physical capacity of the underlying server. For most PVU based products on most virtualisation platforms (VMware, KVM, AIX LPAR, IBM PowerVM, z VM, certain Microsoft Hyper V configurations, certain Solaris zones) sub capacity is available, provided the customer meets the operational requirements.
The operational requirement that most often goes wrong is the deployment of IBM License Metric Tool (ILMT). To remain sub capacity eligible, the customer must deploy ILMT, scan the eligible servers continuously, generate the quarterly Audit Snapshot reports, retain them for two years, and respond to IBM audit requests with the data. If any of these conditions is not met, the buyer falls back to full capacity licensing on the affected servers. The full capacity fallback is the single largest avoidable cost in most enterprise IBM estates.
The deep dive on this topic is in Sub Capacity Explained and in the ILMT deployment expertise page. The white paper companion is the Sub Capacity Licensing Guide and the ILMT Deployment Playbook.
4. Cloud Paks and Red Hat.
The Cloud Paks are the modern IBM platform offerings, each bundled with Red Hat OpenShift Container Platform entitlement. The Cloud Pak licence is sold by VPC and includes a defined OpenShift entitlement per Cloud Pak VPC. The bundle calculus is the central question. A buyer running standalone OpenShift subscriptions and a Cloud Pak in parallel is typically double paying for the same OpenShift capacity.
The Cloud Pak portfolio.
The current portfolio includes Cloud Pak for Applications, Integration, Data, Watson AIOps, Security, Business Automation, and Network Automation. Each carries different ratios for bundled OpenShift, different metric mappings for the embedded IBM products, and different upgrade paths from the standalone equivalents. The Cloud Paks expertise page walks through the entitlement ratios. The white paper companion is the Cloud Pak Licensing Guide.
Red Hat overlap.
The most common Red Hat licensing mistake is to fail to draw down the bundled OpenShift entitlement. A buyer running 500 standalone OpenShift subscriptions while also operating two Cloud Paks that include 200 bundled OpenShift node entitlements is paying for 200 nodes twice. The remediation is to retire the duplicated standalone subscriptions at the next renewal cycle. The Red Hat expertise page covers the full picture and the OpenShift Licensing Deep Dive walks through the reconciliation methodology.
watsonx is the AI native product family that sits adjacent to the Cloud Pak portfolio. watsonx.ai, watsonx.data, and watsonx.governance each have distinct entitlement structures based on Resource Units, foundation model class, and token consumption. The pricing of watsonx is materially different from the rest of the portfolio.
5. Mainframe licensing.
System z carries two distinct licensing regimes: Monthly License Charge (MLC) for the foundational stack (z/OS, CICS, IMS, Db2 for z/OS, MQ for z/OS) and International Program License Agreement (IPLA) for most additional software. MLC charges scale on the four hour rolling peak MSU consumption captured by the Sub Capacity Reporting Tool (SCRT). IPLA charges are typically a fixed entitlement.
The four hour rolling peak is the central operational lever for mainframe cost. A workload that hits a brief midnight batch peak drives the MSU charge for the entire month. The discipline of capping the peak through workload smoothing, defined capacity LPARs, or container pricing structures is the highest yield cost lever in the mainframe estate. The deeper reference is the mainframe expertise page and the Mainframe MLC and IPLA Guide.
Tailored Fit Pricing is the newer IBM offering that consolidates the peak and provides a flatter cost profile. The decision to migrate to Tailored Fit Pricing is a multi year commercial question and is rarely the right move for a stable workload, but it is often the right move for a growth workload.
6. Pricing and discounting.
IBM list pricing is published in the Passport Advantage price file. The realised buyer price is the function of three layered discounts: the volume discount band (driven by the Suggested Volume Points the buyer accrues), the bid discount on a specific transaction, and any Enterprise Agreement discount that overlays both. The benchmark discount range across major IBM product lines varies between roughly 30 percent for steady state mature lines and 70 to 80 percent for strategic transformation deals.
The buyer side leverage on discount is fundamentally three things: documented benchmarks for the same product on comparable terms, a credible alternative or no decision option, and the timing of the conversation. A buyer arriving 90 days before renewal has negligible discount leverage. A buyer arriving 18 months ahead and running a parallel evaluation has materially more leverage. The full discounting reference is in the IBM Discount Structures guide and the IBM Discount Benchmarks white paper.
7. The IBM audit cycle.
IBM audits enterprise customers on a roughly three year cycle, with the cycle compressed for customers that have recently undergone a merger, divestiture, major architectural change, or contractual restructuring. The audit letter typically arrives from one of two IBM teams: the in house Software Compliance Group or a contracted third party audit firm.
The audit interception work is the buyer side discipline of treating the audit as a structured commercial conversation rather than a fact finding mission. The first 30 days after the audit letter set the trajectory for the entire engagement. The contractual rights the buyer holds in this period are documented in the audit rights guide. The triggers that drive the audit selection are documented in the audit triggers guide. The settlement methodology that closes the engagement is in the settlement negotiation guide.
The audit defense engagement is the most time pressured of the buyer side advisory engagements. The audit defense service is the dedicated practice for this work. The white paper companion is the IBM Audit Defense Playbook.
8. Renewal and Passport Advantage.
The renewal conversation is the single highest leverage commercial moment in the IBM relationship. The Support and Subscription stream represents the bulk of the multi year cost of an IBM estate. The renewal sequencing, the multi year commitment, the trade up versus swap rights, the harvest of shelfware, and the discount tier negotiation all happen in the renewal cycle.
The 18 month runway is the operational unit. A buyer that begins the renewal work 18 months ahead can run a parallel evaluation, document a benchmark position, harvest unused entitlement, and arrive at the IBM conversation with three credible commercial postures. A buyer arriving at month three has none of those things.
The renewal negotiation guide walks through the playbook. The Passport Advantage guide covers the programme structure. The white paper companion is the Passport Advantage Renewal Guide.
9. Ten common pitfalls.
- ILMT deployed but allowed to drift. Sub capacity eligibility lost on the affected servers.
- Standalone OpenShift subscriptions duplicated by Cloud Pak bundled OpenShift entitlement.
- Tivoli monitoring agents propagated without an inventory. Agent count discovered to be many times the licensed entitlement.
- MQ Advanced workloads running on MQ Standard entitlement. The edition gap is invisible until audit.
- Db2 features (Advanced Security, Replication, Federation) consumed without verifying the edition entitlement covers them.
- Mainframe four hour rolling peak unmanaged. A nightly batch peak charges the entire month at the peak.
- Passport Advantage Enterprise Agreement renewed without harvesting the unused entitlement first.
- Acquired entity IBM contracts not novated. The acquirer carries inherited risk on contracts it does not control.
- Cloud Pak entitlement under drawn. The buyer pays for the bundle and uses a fraction of the capacity.
- Renewal cycle started too late. The buyer has no leverage and accepts the IBM proposal as offered.
Each of these is its own preventable cost item. The license harvesting work picks up the unused entitlement. The license consulting service covers the broader operational discipline. The License Harvesting Methodology white paper documents the formal process.
10. Frequently asked questions.
Is IBM Licensing Experts an IBM Business Partner?
No. We are independent. We are not an IBM Business Partner, reseller, or affiliate. We do not earn margin on IBM software. Our advisory is constrained only by what is good for the buyer. The full statement is on the why independence matters page.
How long does an IBM licensing engagement take?
A compliance baseline is typically four to eight weeks. An audit defense engagement runs four to six months from receipt of the audit letter to settlement. A renewal advisory engagement runs 12 to 18 months ahead of the renewal date. The full engagement frame is on the services overview.
Do you replace the in house licensing team?
No. We work alongside the in house team. The in house team carries the operational continuity. We carry the independent commercial frame, the benchmark data, the IBM specific contractual reading, and the audit and renewal playbooks. Most of our engagements run as a partnership with an internal Software Asset Management or Procurement function.
What does an engagement cost?
Engagements are scoped by deliverable and run as fixed fee or capped time and materials. A typical compliance baseline lands in the mid five figures. A typical audit defense engagement lands in the mid six figures and routinely recovers 5x to 10x the fee against the IBM opening settlement number. A typical renewal advisory engagement is priced relative to the multi year commitment value. The contact page is the entry point for a specific scoping conversation.
Where should I start?
Start with the topic closest to the question on your desk. If the question is renewal, the negotiation service and the renewal guide are the right reading. If the question is an arriving audit, the audit defense service and the audit playbook are the right reading. If the question is the general compliance posture, the license consulting service and the sub capacity guide are the right reading.
The connected pillars across the blog.
The IBM Audit Complete Guide.
Triggers, contractual rights, data review scope, the settlement methodology, the 120 day audit cycle. The companion pillar for buyers facing an active audit.
Read the audit pillarThe IBM Renewal Negotiation Guide.
Renewal calendar, multi year structures, discount benchmarks, the ELA versus Passport Advantage decision, the buyer side levers. The companion pillar for renewal cycles.
Read the negotiation pillarWhere to go next.
The natural next reading depends on the question. For the operational compliance frame, continue to the sub capacity guide and the ILMT deployment reference. For the negotiation frame, continue to the discount structures guide and the discount benchmarks white paper. For the audit frame, continue to the audit triggers guide and the audit defense service. The complete white paper library and the insights blog remain available for ongoing reference.
For a scoped advisory conversation, the contact page is the entry point. A senior advisor responds within 24 hours and scopes a credible engagement structure within a week. The about page and the why independence matters page document the firm.
Ready to put this work into practice?
An independent senior advisor on your IBM estate. No resell margin, no IBM relationship to protect, no time pressure to push a product. Just the buyer side view.