Editorial photograph of an enterprise IBM ILMT review at the contracted IBM audit framework
IBM · ILMT · Guide

IBM ILMT Guide. Deploy, configure, operate. Keep the PVU sub capacity discount in force.

The ILMT deploy framework, the ILMT configuration framework, the ILMT scan cadence framework, the audit snapshot retention framework, and the buyer side moves on the IBM PVU sub capacity framework.

Contact Us IBM Practice
500+Vendor engagements
4 to 10xSub capacity baseline
Industry Recognized
500+ Enterprise Clients
$2B+ Under Advisory
11 Vendor Practices
100% Buyer Side Independent

The IBM License Metric Tool is the gateway to sub capacity pricing, and an estate that deploys, configures, and operates ILMT correctly keeps the discount in force and stops full capacity audit findings.

Key takeaways

  • Sub capacity gate: ILMT is the precondition for sub capacity PVU pricing.
  • Ninety day rule: reports must be generated and retained on schedule.
  • Deployment scope: every sub capacity eligible server must be covered.
  • Configuration: bundling and exclusions must reflect real deployments.
  • Operation: quarterly reports and two years of retention are the standard.
  • Audit defense: clean ILMT history is your strongest evidence.

Why does ILMT matter so much?

ILMT is the precondition for sub capacity licensing. Without it in force, IBM expects full capacity, which licenses every core in every eligible server.

The financial gap between sub capacity and full capacity is large. IBM sets out the requirement on its sub capacity licensing page and the tool itself on the IBM License Metric Tool page.

What does IBM require?

  • Deploy within 90 days: ILMT must be live on eligible servers.
  • Report quarterly: generate and retain reports on schedule.
  • Retain two years: keep historical reports for audit.

How do you deploy ILMT?

Deploy the server and agents across every sub capacity eligible machine. Coverage gaps are where audit findings appear.

Install the ILMT server, push agents to each eligible host, and confirm discovery. IBM provides the requirement detail in its Passport Advantage terms.

IBM ILMT lifecycle and audit exposure

PhaseRequirementIf missed
DeployLive within 90 daysFull capacity applies
ConfigureAccurate bundlingPVU overstated
OperateQuarterly reportsDiscount lost
RetainTwo years of historyNo audit defense

How should you configure ILMT?

Configuration must mirror your real deployments. Bundling, component exclusions, and product assignments all change the PVU result.

Where does configuration go wrong?

Overstated bundles inflate consumption, and missing exclusions count software you are not running. Both cost money. Review assignments against actual installs.

How do you operate ILMT day to day?

Operation is the discipline that keeps the discount. Generate reports quarterly, review them, and retain two years of history.

  • Schedule: automate the quarterly report run.
  • Review: check for coverage gaps each cycle.
  • Retain: archive reports for two years.

How does ILMT support audit defense?

A complete report trail is the defense. Keep the evidence aligned with IBM Passport Advantage terms on the Passport Advantage page so a review confirms sub capacity eligibility on sight.

Where the common advice on ILMT is wrong

The common advice is that installing ILMT is enough to secure sub capacity pricing. We disagree. In roughly 12 of the 30 IBM estates Morten Andersen reviewed in 2024 to 2025, ILMT was deployed but not operated, with missed quarterly reports or coverage gaps, and at audit those estates faced full capacity findings worth 20 to 40 percent more despite the tool being present. Deployment is the entry ticket, not the protection. The buyer side move is to treat ILMT as an operated control with scheduled reports, full server coverage, and two years of retained history, because the report trail is what defends the discount.

Operations analyst reviewing IBM License Metric Tool quarterly reports
The retained quarterly report trail, not the tool install, is what defends a sub capacity claim at audit.
40%
Audit gap from missed reports
90
Days to deploy ILMT
2 yr
Report retention required

Source: Redress Compliance advisory engagement file, 2024 to 2025.

ILMT installed is a ticket. ILMT operated is the defense. Audits read the report trail, not the install date.Morten Andersen, Co Founder, Redress Compliance

What to do next

  1. Deploy ILMT on every sub capacity eligible server within 90 days.
  2. Confirm agent coverage with no gaps across the estate.
  3. Configure bundling and exclusions to match real installs.
  4. Automate the quarterly report generation.
  5. Retain two years of reports for audit defense.
  6. Review coverage and configuration every cycle.
Run the IBM Audit Defense framework against your actual IBM PVU framework in under five minutes.
Open the Tool →
4 to 10x
Sub capacity baseline
11 moves
Buyer side framework
30 min
Discovery scan cadence
500+
Enterprise clients
100%
Buyer side

IBM framed the audit framework as the immediate full capacity finding across the broader IBM PVU framework. Redress reframed the framework around the customer's actual IBM product framework. Material commercial saving against IBM's opening full capacity framework finding.

Group IT Director
Global insurance carrier
Deep Library

More on this topic.

IBM Practice →
IBM Services Practice
IBM · Practice
IBM Services Practice
The IBM services practice.
20 min read
IBM Knowledge Hub
IBM · Hub
IBM Knowledge Hub
The IBM knowledge hub.
20 min read
IBM Audit Defense
IBM · WP
IBM Audit Defense Guide
The IBM audit defense framework.
8 min read
IBM Vendor Management
IBM · Pillar
IBM Vendor Management Playbook
The IBM vendor management playbook.
18 min read
IBM Audit Playbook
IBM · Pillar
IBM Audit Playbook
The IBM audit playbook.
15 min read
Editorial photograph

Stop overpaying. Start negotiating.

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

IBM intelligence, monthly.

IBM PVU framework signals, ILMT framework signals, IBM audit framework signals, and the broader IBM licensing leverage signals across the practice.

Frequently asked questions

What is the IBM License Metric Tool?

The IBM License Metric Tool, or ILMT, is IBM's tool for measuring Processor Value Unit consumption across an estate. It is the precondition for sub capacity licensing, which lets you license partitions rather than whole servers.

Why is ILMT required for sub capacity?

IBM requires ILMT in force to grant sub capacity pricing. Without it, IBM expects full capacity licensing, which counts every core in every eligible server and is materially more expensive.

What is the 90 day rule?

The 90 day rule means ILMT must be deployed and live on eligible servers within 90 days of the first sub capacity eligible installation. Missing the window can forfeit the sub capacity entitlement.

How often must I generate ILMT reports?

You must generate reports at least quarterly and retain them. Quarterly reporting and a two year retention history are the standard IBM expects to see at audit.

How long must I keep ILMT reports?

You should retain at least two years of ILMT reports. That historical trail is the evidence that defends a sub capacity claim if IBM audits the estate.

What happens if ILMT is misconfigured?

Misconfiguration distorts the PVU result. Overstated bundling inflates consumption while missing exclusions count software you do not run. Both move cost, so configuration must mirror real deployments.

Does installing ILMT guarantee sub capacity pricing?

No. Installation is only the entry ticket. The discount depends on operating ILMT with scheduled quarterly reports, full server coverage, and retained history. Deployed but unoperated estates still face full capacity findings.

How does ILMT help in an audit?

A clean ILMT history is your strongest audit evidence. Complete coverage and a retained quarterly report trail demonstrate sub capacity eligibility and prevent full capacity findings worth 20 to 40 percent more.