ILMT within 90 days: the rule that voids sub-capacity.
Sub-capacity licensing can cut an IBM bill by an order of magnitude, but it carries a hard deadline. ILMT must be deployed within 90 days of your first eligible deployment, or IBM is entitled to charge the full physical capacity of every host.
Sub-capacity licensing is the difference between paying for the cores your IBM software actually uses and paying for every core in the physical host. The gap is large. WebSphere using four of a host's thirty two cores is 480 PVU under sub-capacity and 3,840 PVU at full-capacity, an eight fold difference on a single server. That benefit is not automatic. It is conditional, and the first condition is the 90 day rule.
What the rule says
To claim sub-capacity, you must deploy an approved measurement tool within 90 days of the first eligible sub-capacity deployment. For most environments that tool is the IBM License Metric Tool, ILMT, though IBM also recognizes approved alternatives such as Flexera One ITAM and HCL BigFix Inventory. Deploy it inside the window and the sub-capacity clock starts cleanly. Miss the window and IBM is entitled to charge full physical capacity for the period that was not measured.
Why the deadline is missed so often
The 90 days runs from first eligible deployment, not from the day someone remembers ILMT. A team stands up a new WebSphere or Db2 instance to hit a project date, the measurement tool is treated as a later task, and the window quietly closes while the software runs in production. By the time anyone checks, the period is already exposed, and no amount of later tooling retroactively measures a quarter that was never instrumented.
- The 90 days starts at first eligible deployment, not at go live of ILMT
- An approved tool is required: ILMT, Flexera One ITAM, or HCL BigFix Inventory
- A late deployment does not retroactively cover the unmeasured period
- Full-capacity charging applies to the gap, host by host
Deployment is necessary but not sufficient
Hitting the deadline is only the first of several conditions. The tool must then run continuously, and you must generate and retain quarterly reports for two years. ILMT also miscategorizes installs and needs manual correction, so a tool that is technically present but misconfigured or unreviewed can still fail to support the sub-capacity claim. The 90 day rule opens the door; continuous, accurate operation keeps it open.
What to do if the window was missed
A missed deadline is a defendable position, not an automatic loss. The exposure is bounded by the unmeasured period, and the correct response is to deploy and stabilize the tool now, document the timeline precisely, and reconcile what can be evidenced against what IBM is claiming. In an audit, the difference between a full-capacity default and a negotiated outcome is the quality of that timeline and the evidence behind it.
The 90 day rule is the gate to every sub-capacity saving you expect. Deploy an approved tool within 90 days of first eligible deployment, then run it continuously, because a period that was never measured is a period IBM can charge at full physical capacity.
Common questions
Missed the window, or unsure when it started?
Our ILMT Remediation engagement stabilizes the tool, documents the deployment timeline, and rebuilds a defensible sub-capacity position from where you are now.
See ILMT Remediation →The IBM Audit Brief
Audit triggers, ILMT pitfalls, and settlement tactics for IBM software buyers.
Independent, buyer side IBM software audit defense and negotiation. Not affiliated with IBM Corporation.