We defend ALM, Quality Center, ALM Octane, LoadRunner, UFT, Dimensions and AccuRev estates against OpenText compliance findings. The opening number reads named users where concurrent applies and counts peak Vusers as a permanent entitlement. We hold the metric to its definition.
ALM, LoadRunner and the wider DevOps suite came to OpenText through the Micro Focus acquisition and are governed by the Micro Focus Additional License Authorizations. Those authorizations define whether a product is licensed by named user, concurrent user, or another metric, and a DevOps finding turns on reading that definition correctly. The vendor opens by counting the broadest population it can, pricing the gap at list, with back maintenance and audit costs added.
Two overclaims dominate. The first is named versus concurrent user counting: many ALM and Quality Center deployments are licensed for concurrent access, yet a finding counts every named account that ever logged in as though each required a dedicated license. The second is Vuser counting in LoadRunner, where a brief peak during a load test is priced as a permanent entitlement even though Vusers are consumed only during test execution. Around these sit further traps:
Dimensions and AccuRev add their own user and stream metrics, and ALM Octane introduces pipeline and DevOps user questions. The defense begins by establishing the licensed metric for each product, then holding the count to concurrency and actual execution rather than the inflated named population.
We take over within the seven day notice window, agree an NDA, and route every request for ALM and LoadRunner usage data through a single controlled channel.
We rebuild the effective position against the Additional License Authorizations, establishing the named or concurrent metric for each product before any vendor measurement runs.
We prove concurrency from usage evidence, count Vusers against actual test execution, strip non production environments and decommissioned projects, and challenge the baseline line by line.
We settle on the buyer's terms and, where useful, convert forward into a clean OpenPass agreement with defined ALM metrics and audit protections.
The decisive evidence is concurrency and execution data. Session logs show peak simultaneous users against a concurrent license, and LoadRunner run records show when Vusers were actually consumed. Those figures, not the raw named population, define a defensible finding. The full method is set out in the four Rs and in the complete OpenText audit defense playbook.
ALM and LoadRunner findings follow the same shape as the rest of our practice. The opening number rests on a count that ignores the licensed metric, and the defensible figure emerges once concurrency and execution evidence replace the named population. Across more than 200 defended OpenText and Micro Focus audits, the firm record holds steady.
For the mechanics that apply across every product line, start with how to respond to an OpenText seven day audit notice and the reading Micro Focus ALAs paper.
Fortify sits in the same DevOps estate, where seat and access counting raises parallel questions.
Track 05The Additional License Authorizations define whether each DevOps product is named or concurrent.
Track 08A converted agreement turns a defended DevOps finding into clean forward terms.
We take over within the seven day notice window. Buyer side only. Founded in 2020 by former vendor compliance leadership. Not affiliated with OpenText Corporation.