① Journal · Benchmarks
The Compuware developer tools, Topaz, Abend-AID, File-AID, ISPW, and the rest, now bill under the BMC AMI DevX family after BMC acquired Compuware in 2020. Unlike the MSU metered BMC operations tools, these are mostly seat licensed, which changes the benchmark entirely. The number that matters is how many developers actually use them, not how many seats you bought. Here is how to read Compuware (BMC) spend against real usage.
48 hour mobilization Audit notice or renewal under 18 months out? We mobilize within 48 hours.
Get expert help →When BMC (BMC Software) acquired Compuware in 2020, the Compuware developer tooling was folded into the BMC AMI DevX family. These products, the Topaz Workbench, Abend-AID, File-AID, ISPW source control, and the rest, are developer facing and are generally licensed per user or seat rather than on z/OS MSU capacity. That is a different benchmark problem from the MSU metered operations tools. Seat licensing does not move with your peak, it moves with your headcount, and headcount on the mainframe has a way of being entitled high and used low.
The mainframe developer population is aging and shrinking at many shops, yet the seat count on the contract often reflects the team as it was at the last big project, not the team as it is now. That gap is the whole benchmark. Compuware spend is rarely a rate problem. It is a count problem.
The Compuware (BMC) bill concentrates around seat counts and the bundle they sit in. The benchmark is to compare entitled seats with seats that logged real activity in the measured period:
| Spend driver | How it works | Where it drifts |
|---|---|---|
| Topaz and core dev seats | Per named user or seat | Seats entitled for a team that has since shrunk |
| Abend-AID, File-AID, ISPW | Per seat, often bundled with Topaz | Bundle scope wider than the modules teams actually use |
| Topaz Workbench inclusion | Commonly included with the DevX bundle | Paying separately for what the bundle already covers |
| Support and maintenance | Annual percentage on the seat base | Maintenance carried on dormant seats nobody reclaimed |
The pattern is seat drift. A team scales up for a modernization push, seats are added, the push ends, and the seats stay on the contract through renewal after renewal. Because the mainframe developer count rarely grows back, the gap between entitled and active seats widens every year. The largest lever is almost always reclaiming dormant seats to true the count to the working team, not negotiating the per seat price.
A defensible Compuware benchmark starts by measuring active usage, who actually opened Topaz, Abend-AID, or File-AID in the last representative period, and comparing that to the entitled seat count. The gap is the first and largest saving. Next, check the bundle scope so you are not paying breadth for modules a team never touches, and confirm you are not licensing Topaz Workbench separately when the DevX bundle already includes it. Only after the count is trued does the per seat rate become the conversation. External rate bands inform that final step, but on seat licensed tools the count comes first, every time.
The general method is in the guide on benchmarking your mainframe software spend, and the source control product is detailed in ISPW licensing. The sibling reads are benchmarking BMC spend and the skills shortage and its licensing side effects. When the Compuware (BMC) renewal lands, our Compuware (BMC) cost optimization work trues the seat count before it is re-committed. The estate view sits in the Compuware (BMC) licensing hub.