① Guide · Compuware (BMC)
BMC acquired Compuware in 2020 and folded its tools into the BMC AMI DevX line. The products are the same; the renewal is not. Here is what changed, where the new cost traps sit, and how to negotiate the bundle that BMC now puts in front of you.
The tools your developers use did not move. The contract they live in did.
Compuware (BMC) built its position on developer productivity tools that are genuinely hard to displace: Xpediter for debugging, Abend-AID for fault management, File-AID for test data, the Topaz workbench, and Strobe for performance. After the 2020 acquisition, BMC rebranded most of these into the BMC AMI DevX family, renamed several, and began renewing them as part of broader BMC AMI subscriptions rather than as the standalone Compuware agreements buyers signed originally.
For the renewal, three things shifted: the product names on the quote, the structure of the agreement, and the company across the table. Each changes how you prepare. The negotiation mechanics are on Compuware (BMC) license negotiation, and the wider BMC cost picture is on the BMC hub and BMC cost optimization. This guide maps what to expect.
The Compuware name still appears on older contracts and in every buyer search, but the quote uses BMC AMI branding. Reconcile the two before you negotiate.
| Compuware name | Current BMC AMI name | Function |
|---|---|---|
| Xpediter | BMC AMI DevX Code Debug | Interactive debugging and analysis |
| Topaz Workbench | BMC AMI DevX Workbench | Eclipse based developer environment |
| Topaz Total Test | BMC AMI DevX Total Test | Automated unit and integration test |
| Abend-AID | BMC AMI DevX Abend-AID | Fault diagnosis and resolution |
| File-AID | BMC AMI DevX File-AID | Test data management |
| Strobe | BMC AMI Strobe (performance) | Application performance measurement |
Naming reflects BMC AMI DevX branding observed as of 2026. Confirm the exact product names on your current quote, since vendor naming continues to evolve.
BMC commonly renews the former Compuware tools as a single AMI DevX subscription rather than discrete products. Per tool pricing disappears into one number, so a tool nobody uses is invisible inside the total. Insist on a per product breakdown before discussing the rate.
The DevX subscription is often co termed with other BMC mainframe agreements such as MainView and Control-M. That alignment is presented as convenience but reduces your leverage, because one expiry date forces every product to renew on the same clock. Decouple the timelines where you can.
Tools licensed on capacity rise when the machine grows, even though developer tooling value does not scale with MIPS. Validate that the capacity basis reflects how the tools are actually used, not the size of the box they happen to run on.
Under one vendor for debug, fault, test data, and performance, the muscle to evaluate alternatives atrophies. Keep at least one credible alternative costed per category, so the renewal is a choice and not a default. The exit case is what disciplines the number.
Audit notice or renewal under 18 months out? We mobilize within 48 hours. A bundled AMI DevX renewal landing soon? Map it before you respond.