① Journal · Compuware (BMC)
Compuware (BMC) tools now renew on BMC paper inside the AMI DevX family, and CES license checkout meters seats against entitlement so checkout creep becomes a true up. Here are five recurring Compuware price patterns, and the buyer counter to each.
The discount is on the DevX package. The seat checkout and the BMC rewrite are where the bill moves.
Compuware (BMC) is the developer tooling heritage inside BMC, covering Topaz, Xpediter, Abend-AID, File-AID, and Strobe, now grouped under the BMC AMI DevX family. The patterns that move a Compuware bill are partly transition patterns and partly metering patterns. Since alignment, the tools renew on BMC paper, and the first renewal after that alignment tends to rewrite legacy Compuware terms onto the BMC standard while packaging the developer tools into a broader AMI program that obscures what you actually run.
The metering pattern is specific to these tools. They are commonly administered through Compuware Enterprise Services, which meters license checkout against entitled seats or developers, so when concurrent checkout across the development organization exceeds the entitled count, the gap surfaces as a true up priced into the renewal. Checkout creep is easy to miss because it accumulates one developer at a time. Some products also carry a capacity component tied to MSU, so a single bundled number can hide both a seat driver and a capacity driver. Countering Compuware is about reconciling checkout to real concurrent use, separating the seat metric from the capacity metric, and holding the legacy terms through the BMC rewrite. Read this with our Topaz Workbench licensing page and the Compuware (BMC) publisher hub.
What we commonly observe · the pattern and the buyer counter
| Price pattern | What it looks like | Buyer counter |
|---|---|---|
| CES seat checkout creep | Concurrent checkout drifts above the entitled seat count | Reconcile checkout to real concurrent use, right size seats |
| BMC rewriting | Legacy Compuware terms reset onto the BMC standard | Hold the legacy terms as the renewal baseline |
| AMI DevX bundling | Developer tools packaged so use is hidden | Value each tool on its own use, drop the idle |
| Mixed seat and capacity metrics | One bundled number hides a seat and a capacity driver | Separate the metrics and validate each independently |
| Annual support uplift | Compounding maintenance increase on stable tooling | Cap the annual increase and fix the list reference |
Patterns are what we commonly observe across buyer side engagements, not statements of BMC or Compuware policy, and may change. Your CES checkout data, entitlement, and contract govern the real number.
CES meters license checkout, so the seat figure the renewal is priced on reflects accumulated checkout, not necessary concurrent use. Pull the checkout data, measure true concurrent demand across the development organization, and right size the entitled seat count to that figure before the renewal. Checkout creep that goes unexamined becomes a permanent line; corrected early, it is a reduction you bank.
Price the seats you use at once, not the seats ever opened.
A bundled DevX number can hide a seat driver and a capacity driver that move on different mechanics. Split them apart, validate the seat count against CES checkout and the capacity component against MSU consumption, and negotiate each on its own terms. A single blended figure is the vendor's convenience; two clean metrics are your leverage.
Two metrics, valued separately, beat one blended number.
The legacy Compuware agreement, not the fresh BMC DevX template, is your baseline. Carry its metrics, caps, and discount structure into the renewal and require BMC to justify any change rather than accepting the standard book as the starting point. Pair that with a cap on the annual support uplift and a fixed list reference, and the alignment to BMC stops being a quiet repricing event.
The old contract is the floor, not their new package.
④ Where the Compuware number is countered
The package discount is what they show. The checkout, the metrics, the rewrite are what count. Reconcile checkout, split the metrics, hold the terms.
Typical reduction negotiated on renewal spend
Mainframe spend negotiated on the buyer side
Engagements delivered since 2019
Tools like Topaz, Xpediter, Abend-AID, and File-AID are administered through Compuware Enterprise Services, which meters checkout against entitled seats. When concurrent checkout exceeds entitlement the gap surfaces as a true up at renewal. Reconcile checkout to real concurrent use and right size the seat count. See Topaz Workbench licensing.
Compuware is part of BMC, and its tools now sit within BMC AMI DevX and renew on BMC paper. The first renewal after alignment commonly rewrites legacy terms onto the BMC standard and bundles the tools. Hold the legacy terms as the baseline. See the Compuware (BMC) publisher hub.
It is a mix. The developer tools are commonly seat or developer based through CES checkout, while some products carry a capacity component tied to MSU. Separate the seat metric from the capacity metric and validate each independently. See Strobe vs IBM APA.
Reconcile CES checkout to real concurrent use, separate the seat and capacity metrics, and hold the legacy terms through the BMC rewrite with the annual uplift capped. Our contract review protects the legacy terms and our cost optimization right sizes the seats. See also BMC price increase patterns.
Related: Compuware (BMC) publisher hub · Topaz Workbench licensing · BMC price increase patterns · Compuware audit defense · cost optimization
Audit notice or renewal under 18 months out? We mobilize within 48 hours.
Get expert help →