ILMT is the single tool that decides whether your sub capacity claim survives an audit.
IBM License Metric Tool deployment, health, scanning, and quarterly sub capacity reporting. We get ILMT to the state IBM will accept and keep it there through the renewal cycle.
The tool that turns sub capacity from a claim into a position.
IBM License Metric Tool is the only reporting platform IBM accepts as evidence of sub capacity entitlement consumption for PVU based products. Without an ILMT deployment that scans the eligible footprint, generates the quarterly sub capacity report, and retains the report for two years, IBM is entitled to recompute charges at full capacity. There is no third party equivalent that IBM accepts. The leading SAM tools are not accepted for this purpose.
ILMT runs on top of BigFix Inventory and inherits its discovery, agent, and scan model. A working ILMT deployment is therefore a working BigFix deployment plus the ILMT analytic and reporting layer plus a current PVU table. Most enterprises have at least one of these pieces in poor health. The most common failure is an installed tool that has not been kept current.
The ILMT expertise we bring is operational. We have walked teams through the install on POWER, Linux, Windows, and z. We have rebuilt scan coverage when teams told us coverage was complete. We have reconstructed historical sub capacity reports under audit pressure when the previous reports were missing. See the related work on the sub capacity page and the broader license consulting practice.
What we read first.
- ILMT version and patch level current.
- BigFix relays and clients reporting.
- Scan coverage against eligible product inventory.
- PVU table current within last two quarters.
- Quarterly sub capacity reports generated.
- Reports retained for two years.
- Bundling and exclusion rules applied correctly.
How we run an ILMT engagement.
Current state diagnostic
Inventory the ILMT, BigFix Inventory, and any predecessor tools in the estate. Read the existing scan coverage against the eligible product list. Run the seven health signals. Document the gap to the IBM accepted state.
Architecture and scale design
Design the ILMT server, BigFix relay topology, and agent deployment for the actual estate scale. Account for network segmentation, restricted zones, and cloud regions. Plan the upgrade or fresh install path against the agreed maintenance window.
Install, integrate, scan
Run the install. Validate scan results against the entitlement ledger. Apply software classification corrections for bundles, suites, and any non standard install path. See Passport Advantage for the entitlement side.
Reporting and operations handover
Stand up the quarterly sub capacity report generation and retention process. Train the operations team. Document the run book. Schedule the first internal audit dry run for the following quarter. Sub capacity is operational, not project work.
What you receive.
- A current state ILMT diagnostic report against the seven health signals.
- An architecture document for the target ILMT and BigFix topology.
- A deployment run book for the install and configuration.
- Scan coverage validation against the IBM eligible product list.
- Software classification corrections and exclusion rules documented.
- Quarterly sub capacity report generation and retention process.
- Operations handover and run book.
What breaks in the wild.
- ILMT deployed but never upgraded past a major version.
- BigFix relays orphaned in network zones with no path back to the server.
- Scan exclusions over applied so that genuine eligible deployments are missed.
- Bundle rules wrong so that suite components are double counted.
- PVU table six or more quarters out of date.
- Reports generated but never reviewed before sending to IBM.
- Custom application names blocking automated software classification.
How clients approach ILMT.
How long does an ILMT deployment take from scratch?
Eight to twelve weeks for a typical large enterprise. Faster for estates under 500 servers. Slower where network segmentation or platform diversity is high.
We have BigFix already. Does that help?
Yes, materially. The BigFix client base, relay topology, and patch infrastructure are reusable. The ILMT layer is an add on. The deployment timeline is roughly half.
What about ILMT on AWS, Azure, GCP?
ILMT supports cloud deployment. The IBM eligible public cloud sub capacity scheme has additional requirements on the hypervisor and on the report content. The architecture phase covers this.
Do we need ILMT for products that are not PVU based?
No. ILMT scope is PVU based sub capacity products. User based, install based, and resource value unit based products are outside ILMT. They sit in the broader entitlement ledger maintained in the license consulting workstream.
Can we run the ILMT operations in house after the deployment?
Yes. Operations handover and run book are part of the deliverables. Many clients move ILMT operations to their SAM team after the first two quarters.
Resources
Expertise
Services
Need an independent read on this area?
A senior advisor responds within 24 hours and scopes a credible engagement structure within a week.
Get an independent read on this area of your IBM estate.
Tell us where you are in the cycle. A senior advisor will respond within 24 hours with a scoped engagement structure and an availability window. No sales call, no pitch deck. We do not resell IBM software. We have no IBM Business Partner status. Our recommendations are constrained only by what is good for the buyer.
Read more on why independence matters or browse the services overview for engagement structures.
Request a conversation
Corporate email required. Personal email addresses are not accepted.