Editorial photograph of an enterprise data center
Article · IBM · Sub Capacity and ILMT

IBM sub capacity licensing. The 8x ratio.

A four socket sixty four core server licensed at full capacity costs eight times what the same server licensed at sub capacity costs. The 8x ratio compounds across every virtualized host. ILMT compliance is the operational discipline that makes the ratio real.

Contact Us IBM Practice
40 to 70%Reduction on PVU count
QuarterlyILMT cadence
Industry Recognized
500+ Enterprise Clients
$2B+ Under Advisory
11 Vendor Practices
100% Buyer Side Independent

IBM sub capacity licensing is the single highest leverage commercial discipline on the IBM software estate. Sub capacity reduces the licensable PVU count by 40 to 70 percent versus full capacity licensing on virtualized infrastructure. The right is conditional on ILMT (IBM License Metric Tool) compliance with quarterly reporting and 24 month report retention. Customers without compliant ILMT lose sub capacity rights and pay full capacity at every audit. The compliance discipline is operationally simple but consistently neglected, and the audit risk is the single largest exposure on most IBM estates.

This guide covers the buyer side framework. The sub capacity mechanic and the 8x licensable ratio. The ILMT operational requirements. The audit risk profile and how IBM's audit team identifies non compliance. The remediation timeline for customers with lapsed ILMT. The renewal mechanics that make sub capacity reclassification the highest leverage move at every IBM ELA renewal. For the broader IBM context read the IBM Security and Storage CIO playbook. For the audit response read IBM audit defense playbook.

1. The sub capacity mechanic

IBM PVU based products are licensed at a per core PVU rating multiplied by the number of cores where IBM software runs. Full capacity licensing counts every core in the host. Sub capacity licensing counts only the cores actually used by IBM software inside virtualized environments. The economics differ dramatically.

Full capacity versus sub capacity licensing on a representative virtualized host.
ConfigurationCoresPVU ratingTotal PVU
Host (4 socket, 64 core)6480 PVU per core5,120 PVU
IBM software allocation (8 cores)880 PVU per core640 PVU
Full capacity licensing645,120 PVU
Sub capacity licensing8640 PVU
Ratio8 to 1 in favor of sub capacity
The 8x ratio compounds across every virtualized host

An enterprise estate with one hundred virtualized hosts running IBM software on a portion of cores per host carries an 8x licensable PVU exposure if ILMT is not compliant. Customers running 100,000 PVU full capacity often carry an actual sub capacity entitlement of 12,500 to 25,000 PVU. The remediation typically pays back in the first audit settlement avoidance.

2. ILMT operational requirements

ILMT compliance has three operational requirements that must be met continuously. Failure on any one of the three forfeits sub capacity rights at audit.

  • ILMT installed and operational. ILMT must be installed on every host running IBM PVU based software. The tool must be operational and current with software inventory updates.
  • Quarterly reports generated. ILMT must generate the IBM Software Inventory and the High Water Mark reports on a quarterly cadence. The reports must be produced within 30 days of the quarter end.
  • Reports retained for 24 months. The quarterly reports must be retained for 24 months and made available on audit request. Reports older than 24 months may be archived; reports inside the 24 month window must be immediately retrievable.

3. The audit risk profile

IBM's audit team systematically identifies ILMT non compliance as a primary audit finding. The audit process typically runs in three phases. First, IBM requests the customer's ILMT reports for the last 24 months. Second, IBM validates the reports against the customer's deployment data and identifies hosts without compliant ILMT coverage. Third, IBM reclassifies the affected hosts to full capacity licensing and issues a finding for the difference.

The four most common ILMT compliance gaps that produce audit findings.
GapFrequencyAudit impact
ILMT not installed on a subset of hostsMost common gapAffected hosts reclassified to full capacity (8x licensable PVU)
Quarterly reports missedCommon at customers without operational disciplinePeriods without reports treated as full capacity
ILMT installed but inventory incompleteCommon after platform migrationsHosts with incomplete inventory treated as full capacity
Reports retained less than 24 monthsLess common but high impactInability to demonstrate compliance for the affected periods

4. Remediation timeline

ILMT remediation runs over six to twelve weeks for typical enterprise estates. The timeline depends on the size of the estate, the diversity of the platform, and the operational discipline available. Customers with prior ILMT experience can compress the timeline; greenfield deployments take the longer end.

  1. Weeks 1 to 2. Installation. Deploy ILMT across every host running IBM PVU based software. Configure the inventory scan and the network communication.
  2. Weeks 3 to 4. Initial inventory scan. Run the first complete inventory scan. Validate the host coverage against the asset management baseline. Remediate gaps.
  3. Weeks 5 to 8. Data validation and report generation. Generate the first quarterly report. Validate the data against deployment evidence. Document the operational run book.
  4. Weeks 9 to 12. Operational discipline. Establish the quarterly cadence. Document the retention process. Brief the operational team on the audit response sequence.

5. Sub capacity at renewal

The IBM ELA renewal is the highest leverage moment for sub capacity reclassification. Customers entering renewal with restored ILMT compliance can reclassify the licensable PVU count from full capacity to sub capacity, typically reducing the contracted PVU base by 40 to 70 percent. The reclassification cascades through the renewal pricing because the support fee is calculated as a percentage of the licensed PVU value.

6. Common pitfalls

  1. Pitfall one. Treating ILMT as IT operational hygiene. ILMT is a contractual licensing requirement. The compliance discipline must sit with vendor management and procurement, not be delegated to IT operations.
  2. Pitfall two. Skipping the report retention discipline. Reports must be retained for 24 months. Customers who delete reports after the quarter passes lose the ability to demonstrate compliance retroactively.
  3. Pitfall three. Assuming greenfield deployments are automatically sub capacity. Sub capacity rights require ILMT compliance from day one. New deployments without ILMT installed and reporting are full capacity licensed.
  4. Pitfall four. Ignoring platform migrations. Migrations to new infrastructure require ILMT redeployment. Hosts without coverage during the migration window are full capacity exposed.
  5. Pitfall five. Letting the IBM account team drive the audit timeline. Customers with active ILMT remediation programs should engage IBM regional sales leadership to defer audit cycles until remediation completes.

FAQ

What is IBM sub capacity licensing?

Sub capacity licensing is the contractual right to license IBM PVU based products on the cores actually used by IBM software, rather than every core in the host machine. The economics are dramatic: the licensable PVU count drops by 40 to 70 percent on virtualized hosts. The right requires ILMT compliance with quarterly reporting and 24 month report retention.

What is ILMT?

ILMT is IBM's License Metric Tool. It is the audit grade software inventory tool that documents IBM software deployment for sub capacity reporting. ILMT must be installed on every host running IBM PVU based software, must generate quarterly reports, and the reports must be retained for 24 months.

What happens if ILMT compliance lapses?

Customers without compliant ILMT lose sub capacity rights and revert to full capacity licensing on every audit. The reclassification multiplies the licensable PVU count by four to eight times.

How long does ILMT remediation take?

Six to twelve weeks for typical enterprise estates. Two weeks for ILMT installation and configuration. Two weeks for the initial inventory scan. Two to four weeks for data validation and report generation. Two to four weeks for documentation of the operational discipline.

What savings does ILMT remediation produce at renewal?

Restoring sub capacity rights through ILMT remediation typically reduces the licensable PVU count by 40 to 70 percent on the affected products.

Does Vendor Shield cover ILMT remediation?

Yes. The Vendor Shield subscription covers IBM in every tier including ILMT remediation, sub capacity reclassification at renewal, and the broader IBM commercial framework.

Run the audit defense readiness checklist against your IBM ILMT estate.
Open the Checklist →
White Paper · IBM

Download the IBM audit defense guide.

The full framework. ILMT remediation, sub capacity reclassification, ELA renewal preparation, and the eight clause redline library for IBM contracts.

IBM Audit Defense Guide

Open the white paper in your browser. Corporate email only.

Open the Paper →
40 to 70%
PVU reduction
8x
Full vs sub ratio
Quarterly
ILMT cadence
24 months
Report retention
100%
Buyer side

We had ILMT installed but the quarterly reports had been missed for three of the last six quarters. IBM's audit team reclassified the affected period to full capacity and issued a four point seven million dollar finding. Redress remediated ILMT compliance, restored historical evidence where available, and negotiated the settlement to one point one million on a multi year subscription.

Group Chief Financial Officer
European banking group
Continue Reading

More from this practice.

IBM Practice →
Editorial photograph of IBM Security
IBM · Playbook
IBM Security and Storage CIO Playbook
PVU and RVU mechanics, sub capacity, ILMT, ELA renewal, eight negotiation moves.
18 min read
Editorial photograph of audit defense
IBM · Audit
IBM Audit Defense Playbook
The full IBM audit response sequence. Settlement structure, dispute mechanics.
18 min read
Editorial photograph of IBM services
IBM · Practice
IBM Services Practice
The full IBM advisory practice. ELA, audit, sub capacity, Cloud Pak.
14 min read
Editorial photograph of corporate office
IBM · Hub
IBM Knowledge Hub
Every IBM article, case study, and assessment in one place.
12 min read
Editorial photograph of Vendor Shield
Program · Vendor Shield
Vendor Shield Subscription
Always on advisory across the eleven publisher portfolio.
10 min read
Editorial photograph of corporate skyline

Vendor proposals are not contracts.

Twenty years on the buy side. 500+ enterprises. $2B in client savings.

IBM intelligence, monthly.

ELA renewal benchmarks, ILMT compliance signals, sub capacity audit movements, and the redline movements we see across the IBM practice each month.