① Compuware (BMC) · Audit defense
A Compuware (BMC) audit runs on the vendor's seat counts, the vendor's capacity reading, and the vendor's reconciliation of legacy Compuware paper against BMC terms. We mobilize within 48 hours and contest all three.
Two metrics, one audit, and a brand that changed owners.
Compuware became part of BMC in 2020, and the mainframe developer portfolio now sits inside BMC alongside the AMI DevX tooling. The estate still carries the Compuware product names buyers know: Topaz Workbench, Xpediter, Abend-AID, File-AID, Hiperstation, ISPW, ThruPut Manager, and Strobe. What changed is the paper behind them. Audits and license reviews typically probe the seams where decade old Compuware contracts meet current BMC terms.
The portfolio mixes licensing metrics, and that mix is where the money hides. Developer tools such as Topaz, Xpediter, Abend-AID, and File-AID commonly license by named user or seat, while performance and runtime products such as Strobe commonly license by machine capacity. A review that counts active developers against a stale seat entitlement, then separately reads capacity growth against the runtime tools, can stack two findings on one estate. Each product has to be reconciled against the metric its own contract specifies, not the metric the audit team finds most productive.
Audit timing is rarely accidental. Reviews commonly appear near a BMC renewal, after a developer headcount change, or where legacy Compuware paper is up for consolidation into a current BMC agreement. That is not a reason for alarm; it is a reason for strategy, because the audit and the renewal are usually the same negotiation wearing two letterheads.
One controlled channel for all auditor communication and data requests, established before any data moves. Scope, timeline, and confidentiality are negotiated at the start, while you still have a say in them.
Every generation of Compuware and BMC paper assembled into one entitlement position: seat and user rights on the developer tools, capacity tiers on Strobe and the runtime products, sites, LPAR rights, and the amendments everyone forgot. The vendor's data only means something against this baseline.
Seat based products are counted against actual named users, not nominal headcount. Capacity based products are recalculated against entitled MSU. The two are never allowed to overlap into a double recovery on the same estate.
Seat inflation, bundled component claims, and capacity assumptions are tested against the contract language that actually governs, not BMC's current standard terms. The gap between legacy Compuware paper and today's terms is commonly where the findings collapse.
Residual exposure is traded deliberately: for caps, for seat true down rights, for renewal terms, for exit rights. The settlement is drafted so it cannot quietly become next renewal's uplift baseline.
500+ engagements. $180M+ negotiated. The pattern library matters.
We have sat across this playbook enough times to know which findings are load bearing and which are negotiating theater. With reconciled seat data, reconstructed capacity entitlements, and the original Compuware paper in the room, the conversation shifts from "pay the findings" to "here is what the contract actually says, and here is what we both know about the BMC renewal." Reviews that opened as large compliance claims commonly end as settlements tied to forward terms both sides can live with.
If the BMC renewal is the nearer threat, start with BMC renewal advisory or the broader Compuware (BMC) hub. For the tooling itself, see the Topaz Workbench licensing page. For the core discipline, see our mainframe audit defense service, and for the first moves after any notice, the guide to responding to an audit notice.
Seat and user counts on Topaz and the developer tools, capacity entitlements on Strobe and the runtime products, deployment beyond licensed LPARs or sites, and bundled components in use but never separately entitled. The reconciliation of legacy Compuware paper against BMC terms is where most disputes start.
Developer tools commonly license by seat; runtime and performance tools commonly license by capacity. An audit that counts seats one way and capacity another can stack two findings on one estate unless each product is reconciled against its own contracted metric.
Acknowledge receipt, commit to nothing, and set a single controlled channel before any data moves. Informal early answers and raw data shared without scope agreement are the two most common sources of avoidable exposure.
Vendor audit math is an opening position built on vendor favorable interpretations. Independent recalculation commonly moves findings materially, and settlement structure can convert residual exposure into forward protections.
Commonly, yes. Compuware sits inside BMC, so findings surface as leverage on the broader BMC renewal and renewals settle audit exposure. We run them as one negotiation so a settlement never quietly becomes a worse renewal.