① Compuware (BMC) · MSU optimization
BMC bought Compuware in 2020 and rebranded the tools as AMI DevX, but Xpediter, File-AID, Abend-AID and Strobe still run on the same mainframe capacity, and capacity still sets the charge. We optimize the MSU position before the next renewal, or the move to consumption licensing, freezes it.
48 hour mobilization Audit notice or renewal under 18 months out? We mobilize within 48 hours.
Get expert help →Compuware (BMC) is now an integration story. After BMC acquired Compuware in 2020, the developer and operations tools were folded into the BMC AMI portfolio: Xpediter became BMC AMI DevX Code Debug, ISPW became BMC AMI DevX Code Pipeline, Topaz Workbench became BMC AMI DevX Workbench for Eclipse, and File-AID, Abend-AID and Strobe took the AMI naming. The names changed. The capacity meter underneath did not.
Several of these tools are licensed against mainframe capacity, which means the MSU rating of the LPARs they run on, not your actual use of the product, sets the bill. As the estate grows, the charge grows. BMC has also been steering mainframe customers toward consumption based licensing tied to measured MSU utilization, where a single baseline year can set the cost floor for the term. Either way, the MSU figure is the number that decides what you pay, and it is the number most buyers never independently validate.
Worked example · confining a capacity licensed tool
| Scope | Rated capacity | Relative charge basis |
|---|---|---|
| Full sysplex rating (as billed) | 3,200 MSU | 100% |
| LPARs that actually run the tool | 1,150 MSU | 36% |
| Recoverable if scope is corrected | 2,050 MSU | 64% of the metric base |
Illustrative figures. The principle is constant: a capacity licensed tool should be rated on the capacity it runs on, not the capacity the contract defaulted to.
Four steps
BMC negotiates the AMI portfolio with full visibility into the capacity metric and a clear preference for moving customers onto consumption terms. We level that. BMC's team faces a counterparty that has independently validated the MSU figure, confined each tool to its real footprint, and modeled the consumption option both ways. The billed capacity gets questioned. The baseline year gets contested. The renewal becomes a negotiation over a number you can defend rather than one the vendor handed you.
The typical outcome across our work, $180M+ negotiated over 500+ engagements, is a 20 to 35 percent improvement on addressable spend, with the contract protections worth as much as the discount over the term.
BMC rebranded most of the portfolio under AMI DevX after the 2020 acquisition. Xpediter is now Code Debug, ISPW is Code Pipeline, Topaz Workbench is Workbench for Eclipse. Buyers and old contracts still use the Compuware names, which is why reconciliation matters. See ISPW licensing.
Several are licensed on mainframe capacity, so the MSU rating of the LPARs they run on sets the charge. As capacity grows with hardware, the bill grows whether or not your use changed.
Confine capacity licensed tools to the LPARs that run them, validate the billed MSU against your own SCRT data, and remove development tooling entitlements that no longer match team size. See SCRT explained.
Sometimes. It can suit a shrinking or volatile estate but transfers measurement risk to you, and the baseline year sets the floor. We model both before recommending either, and never let the vendor set the baseline unchallenged.
12 to 18 months before renewal, or immediately if BMC has proposed consumption licensing or issued an audit notice. The MSU baseline is easiest to influence before the measurement window begins.
The measurement that validates or disputes the MSU you are billed.