How to challenge an ALM concurrent user headcount

A concurrent ALM license is metered by peak simultaneous sessions, not by the total number of accounts that exist, so the way to challenge an ALM concurrent user headcount is to replace the account total with the real concurrency data. Almost every inflated concurrent finding rests on the same mistake: counting everyone who could log in rather than the most who ever did at once.

The concurrent model exists precisely so that a large population of occasional users can share a smaller number of simultaneous sessions. A team of two hundred testers, most of whom touch ALM only now and then, might run comfortably against a concurrent entitlement a fraction of that size, because the system caps simultaneous sessions and the population never all logs in together. An audit that ignores this and counts the full provisioned population against the concurrent pool charges for a scenario that never happens. Because the EULA places compliance on the licensee, the burden of producing the concurrency evidence sits with the buyer, and that evidence is exactly what dismantles the inflated count.

What a concurrent ALM headcount should measure

The correct measure for a concurrent license is the peak number of simultaneous sessions over the audited period, drawn from the session logs the system already keeps. That single figure, the high water mark of concurrent use, is what the entitlement is sized against, and everything above it in the account list is irrelevant to the concurrent count. The challenge therefore has two halves: first establish that the license is genuinely concurrent rather than named, the distinction set out in named versus concurrent user counting in ALM audits, and then produce the session data that shows the real peak.

The mistake the audit makes is treating identity as the unit when the entitlement meters simultaneity. Once the license is confirmed as concurrent, the total account count carries no weight, and the only number that matters is the measured peak. Producing that figure from the session logs, cleanly and verifiably, is the core of the challenge, and it rests on the same documentation discipline as documenting concurrent ALM users for a rebuttal.

How to build the concurrency challenge

Confirm the model first

The challenge only applies if the license is concurrent, so the first step is to confirm the model in the entitlement, because arguing concurrency against a genuine named license wastes effort, the point made in named versus concurrent user counting in ALM audits.

Pull the session data

The peak simultaneous session figure comes from the system logs over the audited period. Presenting it cleanly, with the methodology stated, is the substance of documenting concurrent ALM users for a rebuttal.

Set aside the account total

Once the model is confirmed and the peak established, the provisioned account count drops out of the concurrent analysis entirely, the same separation of population from active use applied in reducing a LoadRunner finding with concurrency evidence.

How we challenge a concurrent headcount under the four Rs

Respond. OpenText gives seven days notice before an audit and the right to copy relevant records. We take over the single controlled channel and ensure the session logs and the entitlement records are preserved together, because the concurrency challenge depends on both.

Reconstruct. We build the effective license position by confirming the concurrent model and measuring the peak simultaneous session figure from the logs, before any vendor measurement script runs and fixes a higher number in place.

Rebut. We challenge every line that counts the provisioned population against the concurrent pool, replacing the account total with the measured peak. The finding falls by the difference between the two.

Resolve. We settle on the peak based count and, where it serves you, convert forward into an OpenPass agreement that records the concurrent metric and how it is measured, so the next review cannot revert to counting accounts.

An anonymised outcome

The reason the concurrency challenge matters is the remedy behind the finding. On noncompliance the licensee is deemed to have acquired licenses at then current list price, owes back maintenance and support, owes first year maintenance on the new licenses, and reimburses the cost OpenText incurs performing the audit, so collapsing an inflated account total to the real peak can remove a very large block of charge at once. Our anonymised case files show reductions of this scale across the estate, including an insurance ECM seat count finding reduced from $7.2M to $1.6M, a 78 percent reduction built on disqualifying accounts that did not belong in the count. A concurrent ALM headcount yields to the same logic: measure the peak, set aside the population, and the inflation disappears.

Let the session data set the number

The lasting lesson is that a concurrent ALM license is defended with data, not argument: the session logs already hold the only figure that matters, and the challenge is simply to put that figure in front of the audit in place of the account total. A buyer who confirms the model and produces the measured peak holds the finding to what the entitlement was actually sized for. To prepare the position, read reconciling ALM entitlements before an audit and the model distinction in named versus concurrent user counting in ALM audits. For the full method see our ALM and LoadRunner audit defense track and our complete OpenText audit defense playbook for 2026. If an ALM finding has counted accounts against a concurrent license, open a case.