By Matt Marnell
The IBM License Metric Tool (ILMT) is required for IBM Passport Advantage customers that are using sub-capacity processor value unit (PVU) licensing and is recommended for full capacity licensing. Customers are required to generate ILMT reports and keep them for a period of 2 years. These reports must be provided if there is a software license audit. The advantage of virtualization, or sub-capacity, licensing is that customers only have to purchase licenses for the processor-core capacity allocated to the virtual machine(s) or hardware partition(s) that are running that IBM application, rather than license the full capacity of the physical server or group of servers. This can save you some real money on your IBM licenses.
So, you have to use ILMT… what else do you need? Basically, ILMT is a simple, limited-scope inventory tool that reports only on PVU capacity per product for full and sub-capacity licensing terms. It is not a license management solution since it— (a) does nothing to optimize license consumption based on entitlements, or reduce software spend, (b) does nothing to inventory or manage the multitude of non-PVU IBM license models, not to mention inventory and license management for all the other software vendors’ products, and (c) does nothing to manage or report on your contracts, users, or payment schedules. A complete, optimized software license management solution does all of these things across a wide range of software publishers, license models and license agreements, for hundreds of thousands of applications.
In addition, ILMT reports are not very configurable and are cumbersome to use to manage exceptions—for example, bundled licenses such as limited-use DB2 and WebSphere that are included with so many other IBM software products, apps with a choice of models such as Lotus CEO User versus PVU+CAL, etc. And being able to easily track persistent exceptions is important since the tool may misidentify hardware, improperly count the same virtual machine (VM) multiple times on different physical hosts, and incorrectly assign PVU values to products. It often requires skilled manual intervention to properly exclude exceptions. Your license management solution should be able to manage these exceptions in a much more automated way.
Optimized license management solutions don’t stand alone however. Ideally, they leverage existing tools and infrastructure to collect the data required to manage your software estate. This means having the ability to import inventory data from sources such as the ILMT and other inventory tools (Microsoft SCCM, and others). It also means having the ability to connect to procurement systems for purchase order (PO) data, HR systems for user and organizational data, and a number of other systems for contract and additional information. ILMT and other inventory tools are necessary but not sufficient to enable your organization to implement an optimized license management program that can help reduce software license and maintenance costs and maintain continuous license compliance.
[Editor’s Note: In April, 2011, IBM announced a change from PVU based licensing to the new Resource Value Unit (RVU) model for certain products (see this ELO blog).]

