Commercial · Compuware (BMC)

Compuware (BMC) mainframe license negotiation.

Compuware (BMC) is the developer productivity stack you almost certainly run: Xpediter, Abend-AID, File-AID, Topaz, Strobe. Since BMC acquired Compuware in 2020, these tools renew as part of bundled BMC AMI subscriptions where the price per tool disappears. We make it visible again, and negotiate it down.

When a tool joins a bundle, its price stops being a line you can argue with. That is the point.

Compuware (BMC) negotiations follow a pattern shaped by the 2020 acquisition. The tools your developers depend on, Xpediter for debugging, Abend-AID for fault management, File-AID for test data, Strobe for performance, were rebranded into the BMC AMI DevX family and increasingly renew as a single subscription rather than discrete Compuware agreements. That subscription is often co termed with other BMC mainframe paper such as MainView and Control-M, so the renewal you receive blends products that have nothing to do with each other and prices them as one take it or leave it number.

The bundle is a negotiation tactic, not a constraint on you. Per tool usage can be measured independently, debuggers and fault tools have credible alternatives, and the co termed BMC agreements can be separated so each is negotiated on its own merits. BMC's broader cost behavior, and the levers that move it, are covered on the BMC hub and in BMC mainframe cost optimization. The Compuware specific renewal dynamics are mapped in Compuware renewals under BMC ownership.

Our approach

01

Unbundle the subscription

Every Compuware (BMC) tool, its current BMC AMI name, its metric, and its true cost separated from the bundle. You cannot negotiate a number you cannot see, so the first job is making each tool a line item again.

02

Measure real tool usage

Which tools are actually used, by how many seats, on which LPARs. Across these estates we commonly find tools that were bundled in years ago and quietly fell out of use; retiring them beats negotiating their rate.

03

Build the credible exit

IBM and ISV alternatives assessed and costed for the tools where displacement is real, debug, fault management, and test data in particular. The walk away does not need to cover the whole stack; it needs to be evidenced enough that BMC prices the risk of losing it.

04

Separate the co termed paper

Where the Compuware subscription is co termed with MainView, Control-M, or other BMC AMI agreements, we decouple the timelines so each renews on its own evidence rather than being carried by the bundle.

05

Structure and run the calendar

Escalator ceilings, capacity protections, and exit language negotiated while leverage exists, on a sequence that starts 12 to 18 months out. When the engagement starts late, we compress: a renewal under 18 months out mobilizes within 48 hours.

What changes with us in the room

$180M+

Mainframe spend negotiated across IBM, Broadcom, and BMC paper

500+

Engagements delivered since 2019

20 to 35%

Typical renewal reduction against the vendor's opening position

48 hour mobilization

Audit notice or renewal under 18 months out? We mobilize within 48 hours. A bundled BMC AMI subscription quote on your desk? Start before you sign.

Get expert help

Frequently asked questions

Does BMC still sell the Compuware products?

Yes. After BMC acquired Compuware in 2020, the developer productivity tools were folded into the BMC AMI DevX line. Xpediter is now sold as Code Debug, Topaz Total Test as Total Test, and the Topaz Workbench as the AMI DevX Workbench, while Abend-AID, File-AID, and Strobe keep their names. Buyers still search the Compuware names, and the contracts often still carry them. Product level detail sits on the Xpediter licensing page.

How are Compuware (BMC) renewals structured now?

Commonly as a bundled BMC AMI subscription rather than separate Compuware line items, often co termed with other BMC mainframe paper such as MainView or Control-M. Bundling makes per product pricing hard to see and is where overpayment hides. Annual escalators and capacity based uplifts are typical.

Can we drop individual Compuware tools at renewal?

Often yes, but it depends on the tool. Debuggers and fault management tools have IBM and ISV alternatives that make a credible exit case. Source code management and test data tools are stickier. The negotiation does not require dropping everything; it requires an evidenced exit case for enough of the bundle that BMC prices the risk.

When should we start a Compuware (BMC) renewal?

12 to 18 months before expiry, the same window we use for any major mainframe vendor. Usage of each tool needs validating, alternatives need costing, and co termed BMC agreements need untangling before the vendor controls the clock. If your renewal is closer than that, we compress and mobilize within 48 hours.

A bundled BMC AMI quote on your desk? Make the price visible.

Get expert help