ILMT, the IBM License Metric Tool, is the free IBM-provided software that discovers and measures processor value unit consumption across an estate, and deploying it within 90 days of first sub-capacity eligibility, configuring it correctly, and retaining its quarterly reports for two years is the express contractual condition for licensing IBM products at sub-capacity rather than full-capacity rates. Miss any of those obligations and IBM is entitled to bill every eligible product at full capacity, which on a large virtualized cluster is routinely three to ten times the sub-capacity number.
What ILMT measures
ILMT scans the servers where IBM software runs, identifies each product, maps it to its PVU metric, and calculates the peak processor value units consumed in each measurement window. For virtualized environments it reads the virtual machine configuration, so a four-vCPU virtual machine on a 64-core host is measured on its four vCPUs, not the full host. That capped measurement is the entire value of sub-capacity licensing, and ILMT is the only IBM-sanctioned way to prove it.
| What ILMT reads | What it produces | Why it matters |
|---|---|---|
| Installed IBM products | Product-to-PVU mapping | Identifies what must be licensed |
| Virtual machine core allocation | Peak PVU per product | Caps the bill at virtual, not physical, capacity |
| Quarterly peak usage | Audit-grade report | Is the evidence IBM accepts for sub-capacity |
The three ILMT obligations
Sub-capacity eligibility depends on three obligations that IBM treats as strict. ILMT must be installed within 90 days of the first sub-capacity-eligible deployment. It must be configured to scan every relevant server at least every 30 minutes and generate reports at least quarterly. And those quarterly reports must be retained for at least two years and produced on demand during an audit.
Compliance warning: The most common ILMT finding is not a missing tool, it is a partial one. A server that ILMT cannot reach, an agent that stopped reporting, or a product ILMT failed to recognize all default to full-capacity billing for that product. IBM auditors look first for gaps in scan coverage, because each gap converts a sub-capacity entitlement into a full-capacity liability. Reconcile ILMT coverage against the actual server inventory every quarter, not only before a renewal.
Why it matters to buyers
ILMT is where IBM compliance is won or lost, because it is the only evidence that turns a full-capacity entitlement into a sub-capacity bill. A correctly run ILMT deployment on a 64-core host running a four-vCPU WebSphere instance licenses 280 PVUs, not the roughly 4,480 PVUs the full host would demand. The same gap, multiplied across a virtualized estate, is why ILMT discipline is the foundation of every IBM cost position. Our IBM advisory practice reviews ILMT coverage before it feeds an audit, and the full measurement and audit context sits in the IBM licensing complete guide. The downstream audit mechanics are covered in IBM license audit.
Deploying ILMT correctly
Correct ILMT deployment is an operational discipline, not a one-time install. The tool consists of a central server and scanners that report from each managed endpoint, and its accuracy depends on every relevant server being discovered, scanned on schedule, and recognized as running the IBM products it actually hosts. A scanner that fails silently, a new virtual machine that is never added, or a product version ILMT does not yet recognize each create a coverage gap that defaults to full-capacity billing. The practical regime is a quarterly reconciliation of ILMT coverage against the live server inventory and the deployed IBM product list, with every exception investigated before the quarterly report is finalized. IBM expects the report to be generated at least once a quarter and the underlying data retained for two years, so the report archive is itself a compliance asset that must be maintained rather than regenerated on demand. Buyers who treat ILMT as set-and-forget routinely discover during an audit that coverage drifted months earlier, by which point the gap has already converted entitlements to liabilities across several reporting periods.
What ILMT failure costs
The financial consequence of an ILMT failure is rarely a small correction. Because each unproven product reverts to full-capacity licensing, a single uncovered host running several PVU-metered products can generate an audit finding many times the sub-capacity entitlement the customer believed it held. On a heavily virtualized estate, a coverage gap that persisted across a few quarters routinely produces seven-figure findings, since IBM applies full-capacity rates to every affected product for every period the gap existed. That asymmetry, a free tool guarding a very large liability, is why ILMT discipline returns more than almost any other IBM control. Treating the quarterly report as evidence to be protected rather than paperwork to be filed is the practical difference between a contained audit and an expensive one.