ILMT is effectively mandatory if you take IBM sub-capacity licensing, but running it is not the same as being compliant. Where its automatic bundling stops, why its reports can overstate your usage, and what has to sit alongside it.
In all but a few cases, the IBM Licence Metric Tool (ILMT) is a mandatory IBM requirement for customers who take advantage of sub-capacity licensing on their software products.
Since the majority of IBM customers benefit from sub-capacity licensing, you are highly likely to face the challenges of implementing and running ILMT. So what are those challenges?
Two versions of ILMT have commonly been found in use:
Support for ILMT version 7.5 ended in 2017, so migration to version 9 became necessary. Version 9 is built on technology from another IBM product, Big Fix, which means there is no straightforward upgrade path — version 9 has to be installed as new to remain compliant.
That particular migration is now long behind most organisations, but the pattern it illustrates is not. ILMT is a product with its own lifecycle, its own infrastructure dependencies and its own upgrade projects, and none of that work reduces your licensing exposure by a single core. It is overhead you carry in order to be allowed to buy sub-capacity at all.
Faced with installing ILMT for the first time, you will quickly discover it is difficult to do. It is complex and time-consuming to configure, manage and maintain.
Once ILMT is installed and you have gained full coverage across your infrastructure, you then need to be confident it is reporting exactly what you have deployed. ILMT has been known to produce inaccurate reports. It can, for example, falsely report Tivoli Storage Manager and Spectrum Protect as separate products. Our own consultants have identified errors around media servers. Left unchecked, errors of this kind overstate your usage and inflate your licence costs.
This is the uncomfortable part of the arrangement. ILMT is the tool IBM requires you to run, and its output is the basis on which your sub-capacity position is assessed — but being wrong in IBM’s favour is not a failure mode the tool corrects for you.
Classifying IBM software correctly has a direct and material effect on what you pay. Expensive products can be bundled with lower-priced products, and instances of IBM software that fall under the DR Cold or Warm Standby definition can often be excluded entirely. Most customers are not aware of either lever, or of the impact it has on their IBM charges.
ILMT does bundle software automatically, but it is not always correct, and in most cases it requires further investigation.
Two concrete gaps:
Neither of these is a defect exactly. They are the boundary of what an automated bundler can infer without knowing the purpose of the deployment. But the boundary sits in an expensive place.
There is a third obligation that ILMT’s existence tends to obscure. IBM’s sub-capacity terms require the measured capacity to be collected at least every thirty minutes and retained historically. A quarterly report is not a sub-capacity record. If the collection frequency is not being met, the fallback is full capacity licensing, and the arithmetic changes considerably.
CerteroX SAM enforces that cycle for IBM sub-capacity and holds both the PVU and Virtual Processor Core metrics natively, so the frequency requirement is a property of the platform rather than something you monitor separately.
The practical answer is not to replace ILMT — you are required to run it — but to stop treating its output as the answer.
CerteroX SAM is designed to check and verify ILMT: to show where coverage has gaps, where the data is inaccurate, and where licence metrics need refining, including sub-capacity processor allocations. It takes a direct feed from ILMT through a dedicated connector and runs a compliance gap analysis over it, so you can see what ILMT is not telling you rather than assuming there is nothing to tell.
For the bundling problem specifically, CerteroX SAM applies Component Resolution. IBM products ship as components, and the same component can belong to different products depending on what it is being used for — which is precisely why automatic bundling struggles. Component Resolution matches deployed components to products and presents a scored suggestion, which you can review and then apply in bulk rather than resolving a component list one row at a time.
The result is an Effective Licence Position built on data you have checked, not data you have inherited, so that at renewal you are paying for what you use. And because the same platform holds the entitlement, the agreements and the evidence, the scenario modelling runs on the ILMT-derived data too — you can test a bundling decision or a standby exclusion before you commit to defending it.
If you are running ILMT and have never independently verified what it reports, that is the gap worth closing first. Talk to us.
Other posts covering the same ground.
An Oracle Unlimited Licence Agreement is only unlimited within its clauses. What certification actually asks of you, where toxic consumption creeps in, and why the measurement work has to start at the beginning of the term rather than the last six months.
Microsoft's August 2025 Product Terms changes: Extended Term standardised across programmes, Exchange and Skype for Business Server Subscription Editions, the Exchange and Windows 10 ESU programmes, and the Dynamics 365 F&O enforcement dates.
Renew, rescope or exit — an Oracle ULA gives you three routes and a narrow window to choose between them. The questions to settle first, and a six-point health check to see how ready you actually are.
Everything argued above is checkable. Name the publisher, the billing account or the platform you would argue with, and the session is built around it — the reasoning attached, not a summary slide.
No gated download at the end of it.