The metric families, the agreements, and why IBM behaves differently. Three knowledge checks along the way, and 4 clips from a senior licensing analyst.
This is a taught session, not a talking head. The instructor works through analyst grade slides, and three times the video stops on a question with four options on screen. Pause, commit to an answer, and the next slide explains which option is right and why each of the others is wrong. 4 times in the session the frame splits and a senior licensing analyst gives the view from inside real SAP negotiations, and the instructor picks the clip apart when the slides return.
The full narration of this session, section by section, for reading and reference. Guest analyst clips are marked.
Welcome to IBM Licensing Mastery. I am glad you are here, because this is a subject that costs organisations a great deal of money for reasons that are almost entirely avoidable. Twenty sessions, about twenty minutes each, and by the end you will be able to look at an IBM estate and say what it should cost, what it does cost, and where the difference is. Today is the map. What IBM actually licenses, which documents decide the answer, the four metric families, and the one structural feature that makes IBM different from every other vendor in your portfolio. Three knowledge checks along the way. Let's begin.
Five objectives for today. First, name the four things that decide your position: the metric, how it is deployed, what your entitlement record says, and the support annuity underneath it. Second, read the agreement stack, because knowing which document settles a question saves you weeks. Third, recognise the metric families and know which one carries the risk. Fourth, understand the sub capacity bargain, which is the single most important commercial mechanic in IBM licensing. And fifth, be able to start on any IBM estate, with four questions that tell you within an afternoon whether you are looking at a routine position or an expensive one.
So, why is IBM different? Four things frame it. The licence comes with two obligations rather than one: a deployment right, and an ongoing measurement duty that keeps the affordable count available to you. The default is worse than you expect, because failing the conditions does not produce a fine, it produces full capacity, counted across every core the workload could run on. Audits are run by third parties that IBM commissions, which makes the process procedural and evidence driven rather than relationship driven. And paper beats memory, because most findings are administrative and the defence is a dated record. Let me hand over, because this framing deserves saying plainly.
Guest analyst clip.
An administrative shape rather than a technical one. Hold on to that, because it is genuinely good news. Administrative problems are cheap to prevent and cheap to fix, and almost everything in this course comes back to doing a small amount of unglamorous work on a schedule.
Right, the agreements, and there are four documents in play. The IPLA, the International Program License Agreement, is the base: what a program is, what use means, warranty and liability. Passport Advantage is the volume purchasing and support programme, which is where bands, points, renewals and the sub capacity terms live. The License Information document is per product and per version, and this is the one that defines your metric, carries restricted use language and hides the surprises. And the order forms record what you actually bought, in what quantity, under which agreement number and on what date. The practical habit here is simple: when somebody tells you what a metric means, ask which License Information document and which version. The answer is usually a link, and it usually ends the discussion.
First knowledge check. Where is the definition of a product's licence metric? A, in the IPLA, since that is the master agreement. B, in the product's License Information document, for that version. C, in the Passport Advantage agreement. D, on the order form, next to the part number. Pause here and pick an answer before you continue.
B. The License Information document is product and version specific, and it carries the metric definition, the restricted use language and any bundled entitlements. A gives you the general licence terms but not the counting rule. C gives you the purchasing and support programme, including the sub capacity conditions, but it will not tell you what a Virtual Processor Core means for your particular product. And D names the metric without defining it, which is exactly the gap that arguments live in. Version matters as well, because definitions change between releases and you are held to the one you licensed.
Now the metric families, and there are effectively five. Capacity metrics, so processor value units, virtual processor cores, resource value units and mainframe MSUs, where the number follows the hardware or virtual capacity the software can run on rather than what it uses. User metrics, authorized, concurrent and floating, counted by named access or by simultaneous sessions. Install metrics, counting things, which are simple to audit and simple to defend. Consumption models, application points and credits, which move with usage. And managed metrics, counting what the product administers rather than where it runs. Here is the thing worth remembering: capacity metrics hold nearly all of the money and nearly all of the exposure, because the count follows infrastructure, and infrastructure changes without anybody telling the licensing team.
Which brings us to what you actually own. Five points. The Passport Advantage portal is a purchase history rather than an entitlement position, and those are different things. Acquisitions arrive with their own paper, so different agreement numbers, different bands, sometimes different terms for the same product. Bundled rights are real and limited, because entitlement that ships inside another product usually carries restricted use language: it counts, but only for that use. Lapsed support is not lapsed licence, since a perpetual licence survives a dropped renewal even though the right to new versions does not. And so the register has four sources rather than one. Let me be blunt about the portal, because this assumption is nearly universal.
Guest analyst clip.
The only version of your position that survives contact with an auditor. And notice the timescale in that: a few weeks of assembly, once, then maintained at purchase and at renewal. Compare that with finding the same documents in a fortnight while somebody is waiting for your response.
Second knowledge check. You run one capped four core workload on a large virtualised cluster. What do you owe? A, four cores worth, since that is what it can consume. B, four cores worth, but only if your sub capacity reporting is in order. C, the whole cluster, always. D, whatever the peak measured usage was last month. Pause here before you continue.
B, and this is the whole session in one question. Sub capacity is an entitlement you qualify for, not a state of the world. The product has to be eligible, the virtualisation technology has to be eligible, the tool has to be deployed and current, and the reports have to be generated and retained. A states the answer everybody assumes and quietly skips the condition that makes it true. C is what you owe when the condition fails, so it is the expensive default rather than the rule. And D describes how you might reasonably think about consumption, but IBM counts what the workload can access, not what it happened to use last month.
So let us be precise about the two counts. Full capacity counts the machine: every activated core available to the program, used or not. Sub capacity counts the boundary: the capped partition or virtual machine the software can actually run in. Clusters widen that boundary, because where a workload can move, the count can follow it, which makes mobility settings a licensing decision as much as an architecture one. The multiplier between the two is not marginal. And the fallback is automatic, in the sense that nobody has to prove intent: if the reporting is not there, the full capacity number is simply the one on the table. Let me put an actual number on that gap.
Guest analyst clip.
The best paid work in the discipline. That is not a figure of speech. Four hours a quarter of unglamorous checking, against a number that on a mid sized cluster runs into seven figures. There is nothing else in this course with that return.
Now the annuity, because Subscription and Support is the decision you make every single year. It is charged on licence value, so shelfware costs you annually rather than once, and it compounds with the uplift. Dropping it keeps the licence, so you retain the right to run what you have at the version you have, without fixes or support. Coming back is expensive, because reinstatement is priced specifically to discourage the round trip, so treat a drop as a decision rather than a saving. Renewal is your one calendar date, the moment each year when the vendor needs something from you, which is the working definition of leverage. And count what is on it first, because most estates renew support on products nobody has opened in years.
Five failures, and between them they create most of the findings I have ever seen. The tool was installed and forgotten: present, out of date, missing agents on new hosts, producing reports nobody reads or keeps. Infrastructure moved and licensing did not hear, so a cluster grew or a workload became mobile and the countable boundary changed silently. Bundled entitlement used beyond its restriction, which is the embedded database that was fine inside its product and is not fine serving something else. Support renewed on autopilot, meaning years of annuity on products with no users. And the entitlement never got assembled, so every question becomes a research project under time pressure while an auditor waits for an answer.
Last knowledge check. What is the first thing to establish on an unfamiliar IBM estate? A, the total spend with IBM. B, whether the measurement tool is deployed, current, and its reports retained. C, which products are deployed and where. D, when the next support renewal falls. Pause here and pick an answer before you continue.
B. It is one question, it takes an afternoon, and the answer tells you which kind of estate you are dealing with. If the reporting is clean, everything else is ordinary asset management. If it is not, there is a full capacity exposure sitting behind a perfectly reasonable deployment, and it is growing quietly. A tells you the size of the relationship rather than the size of the risk. C matters and comes second, because the tool is what makes the deployment countable in the first place. And D is the leverage question, worth knowing and not the thing you check first. Let me give you the full starting sequence.
Guest analyst clip.
Whether somebody did those four things, or nobody did. So here is what good looks like, and it is where this course lands in twenty sessions. One named owner, part of a role rather than a department, accountable for the position and present when infrastructure changes are designed. Reporting that is checked rather than assumed: tool current, agents on every host, the quarterly report generated, reviewed and filed. An entitlement register that is maintained at purchase and at renewal, rather than reassembled under audit pressure. A licensing gate on infrastructure change, so a new cluster or a new mobility setting gets the capacity question answered first. And one page, four times a year: deployment, entitlement, gap, and what changes before the next renewal.
Three sentences to take away. IBM licensing attaches an operational obligation to a commercial one, because the affordable way of counting capacity is conditional on measurement and reporting you perform continuously, and the fallback when that fails is full capacity rather than a penalty. The metric that applies to you is defined in the product's License Information document rather than in the master agreement, and your entitlement is assembled from four sources rather than downloaded from one portal. And capacity metrics hold nearly all of the exposure, because the count follows infrastructure that changes without telling anybody, which is why the first question on any IBM estate is whether the reporting is real. Next session, we take the contract stack apart properly.
Homework before session two, about an hour, and the first item is the one that matters. One, ask the measurement question: is the tool deployed, is it current, are reports being generated, and can somebody actually produce last quarter's? Two, list your capacity metric products, so anything licensed by processor value units, virtual processor cores, resource value units or MSUs, because that list is where the money is. Three, find your agreement numbers, and ask why there is more than one. Four, open one License Information document, pick your largest product, and read the metric definition end to end once. And five, note the support renewal date and roughly what it costs, because you will use it in every later session.
Five guides to go alongside this, all on redresscompliance dot com. IBM licensing explained is the estate, the metrics and the agreements in one document, which is the reference version of today. IBM PVU and sub capacity licensing covers the conditions, the tooling and the full capacity fallback in detail. IBM Passport Advantage explained goes into bands, points, renewals and what the portal does and does not show you. IBM audit defence covers how the third party review runs and what evidence actually decides it. And the IBM licensing assessment page describes what an independent review of an estate covers, if you want to see the shape of the work.
That is session one. The thing to take away is that IBM attaches a job to the licence, the affordable count is conditional on doing that job, and the fallback is expensive enough to be worth four hours a quarter. Next time, the contract stack: IPLA, Passport Advantage, the License Information document, and which one actually binds you. See you then.