>
Journal · ELA, ULA and Optimization

Annual true up forecasting for IBM estates.

ELA, ULA and Optimization · Buyer side

A true-up is only a surprise if you let IBM count first. Forecast the number from your own deployment data and the annual reconciliation becomes a budget line you control. The buyer who models the true-up sets the starting point, not IBM.

Many IBM agreements carry a periodic true-up, the point at which deployment growth above your entitled quantities is reconciled and paid for. Under an enterprise or unlimited arrangement it can take the form of a certification of usage at the end of the term. Either way the dynamic is the same: usage has grown during the period, and the agreement now asks for an accounting of it. Buyers who treat the true-up as something that happens to them get a number handed over and a short window to react. Buyers who forecast it arrive already knowing the answer.

Forecasting matters because the true-up is the moment deployment drift becomes a bill, and deployment drifts constantly. New environments, scaled out clusters, a product switched on for a project, capacity added for a migration that was supposed to be temporary. None of that is visible as cost until the reconciliation surfaces it. A buyer side forecast pulls that visibility forward, turning a year of quiet growth into a quantified, defensible position before the conversation with IBM begins.

What moves the number

A credible forecast tracks the drivers that change consumption against entitlement, product by product, across the period.

Why the buyer should count first

When IBM produces the number, it is built on IBM's reading of your deployment, and that reading rarely credits the offsets in your favor by default. A buyer who has modeled the true-up can check IBM's figure line by line, apply the entitlement offsets that belong in it, and challenge the assumptions that inflate it. This is the same discipline that lands thirty to fifty percent of audit findings on average: reconcile independently, then dispute the gap. A forecast is that reconciliation done early, before there is a deadline attached.

How we forecast it

We build the true-up model from your deployment and entitlement data, projecting consumption against entitled quantities for each metered product and folding in the offsets that reduce it. The output is a defensible number the buyer can budget for and defend, and a clear view of where growth should be optimized or where shelfware can absorb it. When the true-up or certification finally lands, it meets a buyer who already knows the answer and can negotiate from it.

What this means under audit

A forecasted true-up is a controlled true-up. Model your consumption against entitlements before IBM does, apply your offsets, and the annual reconciliation becomes a planned budget line you can defend, instead of a number handed to you with a clock attached.

True-up coming up?

Our Audit Negotiation engagement models the true-up from your own data and applies the offsets IBM leaves out, so you negotiate from a number you built.

See Audit Negotiation →

The IBM Audit Brief

Audit triggers, ILMT pitfalls, and settlement tactics for IBM software buyers.

IBM Audit

Independent, buyer side IBM software audit defense and negotiation. Not affiliated with IBM Corporation.

Services
Audit DefenseAudit NegotiationILMT RemediationSub-Capacity Defense
Products
WebSphereDb2CognosCloud Pak
Company
AboutContactJournalWhite Papers
Independent. Not affiliated with IBM Corporation.Buyer Side · Est. 2019