IBM licensing runs on hundreds of metrics, but three of them decide most of your position. What Processor Value Units, Resource Value Units and the user-based family actually measure, and what has to be true of your inventory before any of it reconciles.
Understanding IBM licensing is not straightforward. IBM’s catalogue is large and the metrics attached to it are many, so building an IBM Effective Licence Position can be one of the most complex jobs in the data centre. A potential labyrinth of terms, conditions, metrics and scenarios sits between you and a defensible number. So where do you begin?
Rather than trying to boil the ocean by looking at every IBM licensing option, my advice is to start with the three that will have the largest effect on your position. Get these right and you make real progress towards an accurate Effective Licence Position (ELP) for your IBM software:
The Processor Value Unit (PVU) metric is the most widely known of the IBM licensing metrics. IBM states that PVU is “a unit of measurement used to determine the licensing cost of IBM products. It is based on the type of processor that is deployed on the server where the software is installed. For each product, you must acquire the appropriate number of PVUs that is defined for the specific processor on which the software is installed.”
“The number of required PVUs is based on the processor technology and the number of processors that are available to the software product. For PVU-based licensing, IBM defines a processor as a ‘processor core on a chip’. An example might include a dual-core processor chip that has two processor cores. PVUs are assigned per core, not per processor. The number of PVUs that are assigned to a processor core is defined in the PVU per core table.”
Of course, it does not stop there. Virtualisation allows a portion of your physical server resources to be used by a virtual server — half the capacity of a processor, say. IBM permits this sub-capacity licensing, but only where measurement is in place: you have to be able to show, over time, how much capacity a virtual server consumed and which IBM products were installed on it, both currently and historically.
That measurement requirement is the part organisations most often underestimate. IBM’s sub-capacity terms expect an inventory cycle of no more than thirty minutes and require you to retain the history, not just the current snapshot. CerteroX SAM enforces that cycle, holds PVU and Virtual Processor Core metrics natively, and connects to ILMT so the two data sets can be compared rather than trusted blindly — including a compliance gap analysis that shows where ILMT coverage stops.
The Resource Value Unit (RVU) is the most open of the IBM licensing metrics. To determine your entitlement you need different information depending on the product in question. Examples of things you may need to track include the number of “unique individuals or entities tracked by the program”, the number of “mobile interactions”, or the number of “managed active processor cores”.
Where the RVU is managed active processor cores, it can be tracked by the same sub-capacity measurement as PVU above. Where it is not, you are counting something specific to that product, and the definition in your agreement is the only definition that matters. Read it before you build the count.
User-based licensing is not a single IBM metric but a collection of similar ones. The most common is Authorized User. Once a user is assigned as an Authorized User, the licence may not be reassigned to another user — unless the original user is being replaced on a long-term or permanent basis.
Other IBM user-based metrics include:
One of the key things to consider with user-based metrics is whether a ratio applies. In some cases the more volume you buy, the more you get for your money, and it is worth investigating this to understand what your true licence capacity really is.
The other consideration is administrative. User-based products have historically been counted by hand — scripts run against a server, extracts pulled from a management console — and that is exactly where positions rot. CerteroX SAM imports users, groups and organisational structure from Active Directory and meters actual application usage through AppsMonitor, with first-used and last-used tracking and a rolling 90-day utilisation window, so a user-based count can be built from inventory rather than reassembled by hand each quarter. It still needs a working joiners, movers and leavers process behind it. Without one, it remains very easy to find yourself exposed purely through poor user administration.
Understanding the main IBM metrics will help you towards optimising your IBM licensing position and spend. But there is more to an IBM ELP than the metrics, and it is a job often best left to specialists. You must be able to:
Step two is where most tools quietly fail. IBM products are shipped as components, and the same component can belong to several products depending on what it is being used for. CerteroX SAM handles this with Component Resolution, which matches deployed components to products and presents a scored suggestion you can review and apply in bulk, rather than leaving you to reconcile a component list by hand.
Doing all five accurately — in a way that leaves you neither overspending nor exposed to an IBM compliance finding — takes more than a working knowledge of the metrics. The stakes are too high to get it wrong.
If you have the skills but not the technology, CerteroX SAM combines discovery and inventory across your IBM footprint with IBM-specific licence management, including bundling and the sub-capacity metrics described above. If you are not confident you have either the skills or the technology in place, Certero also delivers this as a managed service.
Not sure what your IBM licensing position actually requires? Talk to us and we will work through where you are strong, where you are exposed, and what it would take to close the gap.
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.