Software asset management is sold as a platform problem, solved by a six figure tool and a dedicated team. For IBM specifically, that framing does more harm than good. The products that draw audits, WebSphere, Db2, Cognos, MQ, Maximo, the Cloud Paks, are governed by a handful of metrics and a small set of rules. A buyer who understands those rules and keeps a disciplined record can defend an audit far better than an organization that bought a discovery tool, switched it on, and assumed the dashboard was the truth. The goal of software asset management on a budget is not coverage of every title on the network. It is a defensible position on the IBM products that actually carry risk.
Start with entitlement, not discovery.
Most teams begin by scanning the estate to see what is installed. That is the expensive half and the less useful one. Begin instead with what you are entitled to. Your Passport Advantage entitlement summary lists every product, every metric and every quantity you have bought. It is free, it is authoritative, and it is the document IBM measures you against. Read it, resolve each line to a product and a metric, and you have the denominator for the whole exercise without spending anything.
- Pull the entitlement summary. Map each part number to a product, an edition and a metric. This is the baseline IBM will use, so make it yours first.
- Separate the metrics. PVU and VPC are capacity based, RVU is usage based, Authorized User and Floating User are people based. The defense for each is different, so group your products by how they are counted.
- Flag the sub-capacity products. Anything licensed by PVU or VPC under sub-capacity terms depends on tracking evidence. Those are the lines where a budget approach still has to be rigorous.
Use the tool IBM already requires for free.
For sub-capacity licensing, IBM mandates the IBM License Metric Tool, and it is provided at no additional license cost for that purpose. ILMT is not optional and it is not a nice to have. Under Passport Advantage sub-capacity terms, you must deploy it within ninety days of your first eligible sub-capacity installation, keep it running continuously, generate the quarterly reports and retain them for at least two years. If those conditions are not met, IBM is entitled to charge at full capacity, counting every physical core the software could run on rather than the virtual capacity you allocated. For a budget conscious team, the single highest return activity in IBM asset management is making sure ILMT is installed correctly, scanning everything in scope, and producing reports that are actually saved. It costs nothing and it is the difference between a sub-capacity bill and a full-capacity one.
Keep a lightweight record between scans.
You do not need a configuration management database to track change. A maintained spreadsheet of entitlements against deployments, reconciled quarterly, will catch the drift that triggers audits: an edition nobody downgraded, a server that moved to a bigger cluster, a user community that quietly doubled. The point is not the format. It is the discipline of comparing what you own to what you run on a regular cadence, so a surprise never accumulates into a finding. Pair the spreadsheet with the ILMT quarterly reports and your part-number resolved entitlement summary, and you have a three document evidence base that costs nothing and answers most of what an auditor will ask.
An auditor does not score your tooling. They score your evidence. A budget program that produces a resolved entitlement summary, continuous ILMT reports and a quarterly reconciliation is in a stronger position than an expensive program that produces a dashboard nobody can reconcile to a contract. The buyer side move is to spend your effort where IBM actually measures you, entitlement, metric and sub-capacity evidence, and leave the rest to the cadence of an honest spreadsheet.
Know where the budget approach ends.
Doing this in house has a limit, and it is worth naming. When an audit letter arrives, the question is no longer whether your records are tidy but whether your position will survive a challenge: whether the PVU values were applied correctly, whether a denied sub-capacity claim can be reversed with the evidence you kept, whether the entitlement offsets IBM omitted can be credited back. That is an adversarial exercise against a counterparty that does this for a living, and it is where independent, buyer side defense earns its place. The budget program keeps you out of trouble between audits. When one starts, the records you maintained become the raw material for the defense, not a substitute for it.