① Journal · Operating Discipline
There are two audits of your mainframe stack. One is run by the vendor, to find what you owe. The other you run yourself, once a year, to find what you are overpaying and where your leverage sits. Buyers who skip the second one walk into every renewal with a worse map than the people across the table. Here is the six part self audit that fixes that, and the table that turns it into a working checklist.
Whoever holds the better inventory controls the renewal.
Mainframe estates drift. Capacity grows quietly, products arrive through bundles nobody fully read, metrics shift underneath you when a vendor is acquired, and shelfware accumulates every time a project ends without anyone cancelling the license. None of this announces itself. It simply sits there, compounding, until a renewal or an audit letter forces a reckoning, and by then you are reconstructing your own estate under time pressure while the vendor arrives with a complete picture. That asymmetry is where money is lost, and it is entirely avoidable.
The fix is unglamorous and it works: audit your own stack once a year, on your schedule, before anyone audits it for you. A yearly self audit means you always know your product list, your metrics, your consumption peaks, your renewal dates, and your shelfware. It lets you correct over deployment quietly, retire what you no longer use, and challenge the vendor's measurement with your own numbers. It is also early warning, surfacing the renewal while there is still eighteen months to build a position. This is the same discipline behind our quarterly license governance rhythm, scaled to a yearly deep pass, and it pairs directly with our vendor scorecard.
What to inventory · what you are looking for · the leverage it creates
| Part | What to inventory | What you are looking for |
|---|---|---|
| Product list | Every licensed product across all publishers, mapped to the machine and LPAR it runs on | Products you license but no longer run; modules added by bundle that nobody uses |
| Metrics | The pricing metric for each product: MSU, MIPS, capacity, core, seat, instance | Metric mismatches, peak based charges that overcharge bursty workloads, transition opportunities |
| Consumption | Actual peak four hour average and usage per product, from SMF and SCRT | Gaps between licensed capacity and real consumption; products priced above what you use |
| Cost | Annual cost per product and per publisher, with three year trend | Silent uplifts, products whose cost has outrun their value, concentration risk |
| Renewal dates | Every term date, notice window, and auto renewal clause | Renewals inside the eighteen month leverage window; clauses that lock you in by default |
| Shelfware | Licensed but unused or barely used products and capacity | Drop candidates and capacity to hand back; the cleanest savings in the stack |
Each row is a question the vendor can already answer about you. The self audit makes sure you can answer it first, and usually better.
You stop reacting to the vendor's number. You arrive with your own.
The practical difference shows up in the first renewal meeting. A buyer without a current self audit spends the early weeks reconstructing the estate, which means the vendor sets the agenda and the baseline. A buyer with a fresh audit walks in already knowing which products are shelfware, which metrics overcharge, which capacity can be handed back, and which renewals fall inside the window where the vendor needs the deal more than you do. The conversation starts from your evidence rather than theirs, and the difference in outcome is the difference between accepting a quote and negotiating one.
The audit also defuses the vendor audit before it starts. When you already know your deployment to the LPAR, an inbound audit letter is a process to manage rather than a threat to survive, because there is nothing to discover that you have not already found and corrected. The yearly cadence is what makes this real. A one time audit decays the moment the estate drifts again, but an annual pass keeps the inventory current so that whenever a renewal or an audit arrives, the map in your hands is the better one. Pair the output with our audit notice response protocol and our three year budget model.
Pick a month with no major renewal and run the audit then, every year. A fixed slot keeps it from slipping, and running it away from a deadline means the findings inform the next renewal rather than scrambling the current one.
A recurring date beats a good intention.
Build the product list from contracts, then check it against what actually runs in SMF and SCRT. The gap between what you license and what you consume is where both the shelfware and the over deployment hide.
Contracts say what you bought; SMF says what you use.
The audit's most valuable output is a calendar. Mark every term date and notice window so nothing renews on autopilot and every negotiable contract gets the lead time a real position requires.
A renewal you see early is a renewal you can shape.
Close the audit with two lists: products and capacity to retire, and metrics or measurements to challenge. Those lists are the agenda for the year and the opening position for the next renewal.
An audit that ends in a list is an audit that pays.
⑤ The discipline that pays
The vendor audits you to find what you owe. Audit yourself first, to find what you are overpaying. Once a year, on your schedule, before anyone else does.
Typical reduction negotiated on renewal spend
Mainframe spend negotiated on the buyer side
Engagements delivered since 2019
A buyer side self audit: a yearly review of every mainframe product you license, the metric it is priced on, what you actually consume, what it costs, and when it renews. It is the opposite of a vendor audit. The vendor audit finds what you owe; the self audit finds what you overpay, what you no longer use, and where your leverage sits before the next renewal.
Because whoever holds the better inventory controls the conversation. If the vendor arrives with a complete picture and you arrive with a partial one, every ambiguity resolves in their favor. A self audit means you already know your products, metrics, peaks, and shelfware, so you can correct over deployment quietly and challenge their measurement with your own.
At least yearly, and more often near a major renewal. The estate drifts continuously as capacity grows, bundles add modules, and shelfware accumulates. An annual cadence catches the drift while it is small and keeps the inventory current for whenever a renewal or an audit letter arrives, so you are never reconstructing the estate under time pressure.
Two lists and a calendar: products and capacity to retire, metrics and measurements to challenge, and every renewal date in the next eighteen months. Those become the year's agenda and the opening position for the next renewal. See our license negotiation service for how we turn audit findings into a negotiated outcome.
Related: quarterly license governance · building a vendor scorecard · responding to an audit notice · license negotiation
Audit notice or renewal under 18 months out? We mobilize within 48 hours.
Get expert help →