An IBM ELP is a claim. Treat it like one.

After an audit, IBM's team analyzes the data you submitted, compares it against the entitlements on record, and produces an Effective License Position: their statement of deployment versus entitlement, and therefore of any shortfall. The document carries the authority of process and detail, and buyers commonly treat it as settled. It is not settled. Every number in it rests on three things you can examine: the data that was submitted, the method used to measure consumption, and the entitlement records IBM chose to match against.

Each of those is a place where the position can move. The buyer side job is not to argue in the abstract; it is to rebuild the position independently and show, line by line, where the vendor's version diverges from the validated truth.

For sub-capacity licensed products, your charge should reflect the Rolling 4-Hour Average peak, not the machine's full rated capacity. But that benefit depends on clean, continuous SCRT reporting. Where a month of SCRT data is missing or rejected, the common default is to bill that period as if the box ran flat out. On a large machine the gap between full capacity and actual R4HA is enormous, so a few missing months can dominate the entire finding. Reconstructing and validating that history, against your own SMF records, frequently moves an ELP more than any other single action.

We rebuild the position independently before accepting any of the vendor's arithmetic: validate the SCRT and R4HA data, reassemble entitlements in full, hold scope to the contract, and check every conversion. Then we present the counter position as evidence, not assertion. Directionally, across 500+ engagements and $180M+ in negotiated mainframe spend, validated challenges typically bring findings and the settlements that follow 20 to 35 percent below the opening claim. On an active finding, we mobilize within 48 hours.