① Journal · Vendor negotiation
Compuware is now BMC, and the developer tools live inside AMI DevX under the same consumption mechanics. Five levers move the number, and the first is to stop negotiating it as a separate deal. Here is where the leverage really sits.
The Compuware deal is now a BMC deal.
Negotiating Compuware (now BMC) mainframe tools changed the day BMC acquired Compuware in 2020 and folded the developer line, including Abend-AID, File-AID, Xpediter, and Topaz, into AMI DevX. They are no longer a standalone vendor relationship; they sit inside BMC's consumption mechanics, governed by the same measured baseline and the same annual true up that govern the rest of the BMC estate. The single most common mistake buyers make is negotiating the Compuware renewal as if it were still separate, which leaves the leverage of the broader BMC relationship unused.
That reframes the exercise. The buyers who win a Compuware renewal treat it as part of the BMC deal, reduce the measured baseline the tools meter against, and trim the toolset to the seats and products in active use. The five levers below run in roughly that order, structure and baseline first, scope and displacement next, bundling last. Read this with our Compuware (BMC) publisher hub and our Compuware renewal advisory page.
What each lever moves · the BMC structure and the baseline set the floor the rest then shape
| Lever | What it moves | When it pays most |
|---|---|---|
| The AMI DevX fold in | Whether you negotiate one BMC deal or two | Before treating Compuware as separate |
| MSU baseline | The measured capacity the consumption model bills on | Before the commitment and the next true up |
| Toolset scope | Which DevX products and seats stay in the deal | Where unused seats or shelfware sit on the order |
| Displacement | Whether BMC keeps the debug and file tools at all | Where IBM ADFz equivalents are credible |
| Bundling | The leverage of the full BMC relationship | When the broader BMC deal is in negotiation too |
Product names and packaging change; verify the current ones on your own order. The order is the durable part: structure and baseline lower the floor, and scope, displacement, and bundling price what is left.
The most expensive assumption is that Compuware is still a separate vendor. The tools live in AMI DevX under BMC's consumption mechanics, so the renewal is governed by the same baseline and true up as the rest of your BMC estate. Negotiate it inside the BMC relationship, where the leverage compounds, not as an isolated line.
One vendor, one negotiation.
Where the DevX tools meter against measured capacity, the same baseline work that lowers the rest of the BMC bill lowers this one. Reduce and validate the measured MSU before the commitment is set, so the consumption model reconciles against a clean number rather than an inflated one for the whole term.
Lower the meter before you commit to it.
Abend-AID, File-AID, Xpediter, and Topaz are bought in bundles that rarely match actual use. Inventory which tools and seats are active, and keep the rest out of the deal. Developer tool entitlements are easy to over provision and easy to trim once you have an honest picture of who uses what.
Pay for the seats in use, not the seats sold.
The debug and file utility layer has real alternatives. IBM Application Delivery Foundation for z/OS, with Fault Analyzer, File Manager, and Debug Tool, overlaps with Abend-AID, File-AID, and Xpediter. A costed plan to move one of these changes the conversation from the size of the increase into whether BMC keeps the work.
A real alternative on one tool disciplines the rest.
Because Compuware sits inside BMC, the largest leverage is the full BMC relationship. Align the DevX renewal with the broader BMC negotiation so the total spend is on the table at once, and use the combined value rather than letting BMC reprice each piece on its own schedule.
Negotiate the whole, not the parts.
④ The order that wins
Treating Compuware as separate is the vendor's advantage. Treating it as BMC is yours. Negotiate the whole relationship, then price what is left.
Typical reduction negotiated on renewal spend
Mainframe spend negotiated on the buyer side
Engagements delivered since 2019
Treating it as a BMC deal. The tools live in AMI DevX under BMC's consumption mechanics, so the renewal is governed by the same baseline and true up as the rest of your BMC estate. Negotiating it inside the broader BMC relationship is where the leverage compounds.
As part of AMI DevX, commonly under BMC's consumption mechanics with the bill following measured capacity and reconciled at an annual true up. Some developer tooling is scoped by usage or environment, so confirm the metric for each product on your own order.
On the debug and file layer, yes, with effort. IBM Application Delivery Foundation for z/OS overlaps with Abend-AID, File-AID, and Xpediter. A costed plan on one product changes the conversation from the size of the increase to whether BMC keeps the work.
Early enough to align the DevX renewal with the broader BMC negotiation and to do the baseline and scope work, usually months ahead. The leverage is larger when the full BMC spend is on the table. See our Compuware renewal advisory and Abend-AID licensing.
Related: Compuware (BMC) publisher hub · Abend-AID licensing · negotiating with BMC · negotiating with IBM
Audit notice or renewal under 18 months out? We mobilize within 48 hours.
Get expert help →