Editorial photograph of a server rack and notepad representing IBM licensing tools
Tools · IBM

ILMT readiness check. Hold sub capacity.

Compare your IBM sub capacity and full capacity PVUs, and the exposure if ILMT is not compliant. The readiness check and the moves.

See the tools Contact Us
8Buyer Side Tools
a leading industry analyst firmRecognized
Industry Recognized
500+ Enterprise Clients
$2B+ Under Advisory
11 Vendor Practices
100% Buyer Side Independent
Key Takeaways

What every buyer should know about IBM sub capacity.

  • Sub capacity needs compliant ILMT. No ILMT means full capacity.
  • Full capacity bills every physical core. Two to four times more.
  • Scan every thirty minutes. Retain reports two years.
  • Lapsed scans are the risk. Scan discipline is the lever.
  • IBM audits sub capacity first. Keep the record audit ready.
  • Quantify the gap. Then hold sub capacity.
  • Directional only. Your environment governs.

IBM lets you license PVU products on sub capacity, paying for the cores actually running the product, but only if ILMT is deployed and scanning correctly. Without compliant ILMT, IBM can demand full capacity across every physical core.

Check the gap, then hold sub capacity.

Quick answer

IBM sub capacity licensing requires ILMT scanning at least every 30 minutes with two years of reports, and without it IBM can bill full capacity across every physical core, often 2 to 4 times more. Example: 200 physical cores with 50 running IBM products at 70 PVU each is 3,500 sub capacity PVUs versus 14,000 full capacity. See IBM License Metric Tool and IBM terms.

ILMT sub capacity readiness

How does IBM sub capacity licensing work?

IBM sub capacity licensing requires ILMT scanning at least every 30 minutes with two years of reports, and without it IBM can bill full capacity across every physical core, often 2 to 4 times more.

The ILMT requirement

Sub capacity requires ILMT installed, scanning at least every thirty minutes, with reports retained for two years. Miss the requirement and IBM reverts you to full capacity.

Sub capacity versus full capacity

Sub capacity licenses the cores running the product. Full capacity licenses every physical core in the environment. The gap is the exposure.

The PVU metric

Each core carries a PVU value by processor type. The PVU per core, times cores, sets the license quantity.

Scan discipline

Most exposure comes from lapsed scans or unmanaged hosts. Scan discipline is the compliance lever.

Audit posture

IBM audits sub capacity claims first. A clean ILMT record is the defense.

BasisLicensesRequires
Sub capacityCores running the productCompliant ILMT scanning
Full capacityEvery physical coreNo ILMT, the default penalty

Where the common advice on IBM sub capacity is wrong

The standard advice is that ILMT is an IT housekeeping task. We disagree. ILMT is a commercial control worth multiples of license cost. A lapsed scan can convert a sub capacity estate into a full capacity demand overnight. The buyer side move is to treat ILMT compliance as a board level cost control, not an afterthought, and to keep the two year scan record audit ready at all times.

Most ELAs do not break even on the second term. The buyer recommitted at a deployment forecast that overshot actual use. Model the true up eighteen months out, not at the anniversary letter, and the renewal reshapes itself.

Seven leverage points on every IBM contract

  1. Run the PVU calculator before any IBM renewal conversation. Size real entitlement first.
  2. Prove ILMT compliance before an audit notice. Sub capacity pricing depends on clean evidence.
  3. Model the ELA true up eighteen months before anniversary. Not at the true up letter.
  4. Reconcile Red Hat subscriptions against Cloud Pak VPC. Avoid paying twice for the same cores.
  5. Anchor renewal uplift caps at signing. Zero to three percent on enterprise IBM deals.
  6. Separate support cap from license discount. Subscription and support is the compounding line.
  7. Never share tool output with IBM sellers. Buyer side data only.

What to do next

  1. Run the IBM audit defense checklist as the first pass.
  2. Run the IBM PVU Calculator to size your real entitlement.
  3. Run the IBM audit readiness assessment to score exposure.
  4. Confirm ILMT is installed, reporting, and has signed quarterly PVU reports for every prior quarter.
  5. Pull deployment counts against your ELA basket for the last 12 months.
  6. Anchor renewal uplift caps before signing.
  7. Engage our IBM licensing assessment service if IBM spend is over $1M annually.

Frequently asked questions

What is IBM sub capacity licensing?

It lets you license PVU products on the cores actually running the product, rather than every physical core, provided ILMT is deployed and scanning correctly.

What does ILMT require?

IBM License Metric Tool must be installed, scan at least every thirty minutes, and retain reports for two years. Miss this and IBM can revert you to full capacity.

How big is the full capacity penalty?

It depends on the estate, but full capacity bills every physical core and commonly runs two to four times the sub capacity figure. The check quantifies your gap.

How accurate is the check?

It is directional, applying a PVU per core value to your inputs. Your processor types and contract set the final number.

What is the most common compliance failure?

Lapsed scans and unmanaged hosts. Scan discipline across the whole estate is the core control.

Is the check free?

Yes. It is free and runs in your browser. No payment and no account required.

Should we share the output with IBM?

No. It is buyer side data. Use it to hold sub capacity and prepare the audit defense internally.

How does Redress engage on ILMT?

We review the ILMT deployment, quantify the full capacity exposure, build the audit defense, and sit at the table. We are not an IBM partner.

Run our IBM PVU Calculator across your estate.
Open the calculator →
500+
Enterprise Clients
$2B+
Under Advisory
11
Vendor Practices
100%
Buyer Side
Industry
Recognized

Tool output is the anchor. Walk into the IBM meeting with a PVU number you trust and the negotiation reshapes itself.

Morten Andersen
Co Founder, ex IBM
White Paper · IBM

Read the IBM Buyer Side Framework.

A buyer side reference on the IBM estate: PVU entitlement, ILMT sub capacity, ELA true ups, and Red Hat after the acquisition. Deployment math and renewal leverage.

Independent. Buyer side. Written for CIOs, CFOs, and procurement leaders carrying IBM contracts. No vendor influence. No sales kickback.

IBM Licensing Assessment

Open the buyer side review in your browser. Corporate email only.

Open it →
More Reading

More from this practice.

All IBM articles →
IBM PVU Calculator
IBM · Article
IBM PVU Calculator
Size processor value units per core before IBM quotes you full capacity.
6 min read
IBM Audit Readiness Assessment
IBM · Article
IBM Audit Readiness Assessment
Score audit exposure across PVU, Cloud Pak, ELA, and Red Hat.
5 min read
IBM Audit Defense Checklist
IBM · Article
IBM Audit Defense Checklist
The clauses and evidence to fix before an IBM review opens.
5 min read
IBM Services
IBM · Article
IBM Services
Full buyer side advisory across PVU, Cloud Pak, ELA, and Red Hat.
7 min read
Editorial photograph of enterprise contract negotiation strategy

Ready to run the IBM math correctly?

Independent buyer side advisory. No vendor influence. No sales kickback. We sit on your side of the table when you negotiate with IBM.

Get the buyer side brief.

Monthly. One email. Zero noise.