Monitoring your own ILMT posture quarterly.
Sub capacity licensing rests on ILMT evidence that has to hold for every period, not just on audit day. A quarterly self review catches the missing agent, the miscategorized install and the stale report while they are still cheap to fix. Run on IBM's own cadence and the audit finds nothing the review missed.
Why a quarter is the right interval
The sub capacity rules are specific about cadence. ILMT must run continuously, generate reports at least every quarter, and those reports must be retained for two years. The audit lookback reads that same trail, so a gap in any quarter is a gap IBM can price. Reviewing on the same quarterly rhythm aligns your checks to the exact evidence the auditor will request, which means nothing accumulates unseen between reviews.
The cost of a missed quarter is not abstract. For any period an agent was not reporting, the sub capacity claim on that host can be voided, and the cores default to full capacity. With WebSphere on four of thirty two host cores, that is the difference between 480 PVU and 3,840 PVU for the affected window. A lookback that spans two to five years multiplies a single lapse across every quarter it touched.
What to check each quarter
- Agent coverage. Confirm an agent is installed and reporting on every host that runs IBM software. A silent host is the most common void.
- Categorization. ILMT mislabels installs by default. Verify each product is bundled and categorized correctly so the count is not inflated or understated.
- Report generation. Confirm the quarterly report actually generated and is archived, not just that the tool is running.
- Version and patch level. An outdated ILMT build can miss new processor types and misread core counts.
- Entitlement alignment. Compare the reported peak against what you hold, so an overrun is visible the quarter it happens.
From checklist to defensible position
A quarterly review is only as good as the record it leaves. The point is not to run a report and move on, but to keep a dated, retained trail that shows the sub capacity conditions were met every quarter. That archive is the position you hand an auditor, and it is far stronger when it was assembled in calm quarters than when it is reconstructed under a notice. The review turns ILMT from a tool you hope was working into evidence you can prove was working.
IBM reads ILMT period by period, so your defense has to hold period by period too. A quarterly self review on IBM's own cadence keeps every window covered, every report retained, and every category correct. Do it routinely and an audit confirms what you already know. Skip it and the lookback finds the quarters you did not.
Want a clean posture before the notice?
Our Audit Defense engagement reviews your ILMT trail, corrects categorization, and builds the retained evidence that holds under a lookback. We mobilize within 48 hours of an audit notice.
See Audit Defense →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.