Preparing an ALM entitlement reconstruction

An ALM entitlement reconstruction is the independent rebuild of what an organisation is genuinely licensed for, assembled before any vendor measurement script runs. It is the anchor of a defense, because a finding can only be challenged against a position the buyer has established for itself. Preparing that reconstruction, gathering the right records and reading them for the metric that actually governs, is the work that turns a reactive audit response into a controlled one.

Application Lifecycle Management, together with Quality Center, ALM Octane, LoadRunner, UFT, and the wider DevOps toolset that came to OpenText through the Micro Focus acquisition, is licensed through a layered set of agreements and Additional License Authorizations accumulated over years of purchases, renewals, and upgrades. The effective license position is rarely written down in one place, which is why it must be reconstructed. An audit will assert its own version of that position; the reconstruction is the buyer's independent, evidence based answer, and it is the foundation the whole defense stands on.

What an ALM entitlement reconstruction establishes

A reconstruction answers four questions for every product in the estate: what was purchased, under what metric, in what quantity, and how that maps to the current deployment. It gathers the order documents, the entitlement records, and the Additional License Authorizations, then reads them against the user inventories, license server records, and usage logs to produce a single defensible statement of the licensed position. The reason this comes first is that it is the discipline at the heart of the method, the same independent rebuild described in reconciling ALM entitlements before an audit, prepared as a deliverable rather than carried in anyone's head.

The single most consequential output of the reconstruction is the confirmed metric for each product, because the metric decides everything that follows. Whether ALM is counted by named or concurrent user is the question examined in named versus concurrent user counting in ALM audits, and the answer changes the size of the finding by the entire gap between provisioned population and peak concurrency. A reconstruction that fixes the metric removes the audit's freedom to choose the counting method that produces the largest number.

What records the reconstruction needs

The reconstruction draws on three layers of records. The contractual layer is the order history and the Additional License Authorizations, which fix what was bought and under what terms. The configuration layer is the license server records and the named or concurrent license definitions, which show how the entitlement is provisioned. The usage layer is the user inventories and session logs, which reveal who actually uses each product and how. Reading these together is what turns scattered documents into a position, and preserving them intact is the first step, because the right of OpenText to copy relevant records means the same data will anchor both the finding and the defense.

The usage layer is where the reconstruction does its most valuable work, because it is where uncleaned counts are corrected. A user inventory carries leavers, duplicates, and service accounts that a finding may treat as licensable, and stripping them out is the line by line discipline set out in defending an ALM named user overclaim line by line. Where the metric is concurrent, the reconstruction derives the peak simultaneous session figure from the logs, the method in how to challenge an ALM concurrent user headcount.

How the reconstruction anchors the defense

The reason the reconstruction is the anchor is that every later move references it. The rebuttal challenges the finding against the reconstructed position, line by line. The settlement is negotiated from the reconstructed count, not from the audit's opening figure. The forward conversion is sized to the reconstructed need. Without the reconstruction, each of these moves is improvised; with it, they are all expressions of a single, prepared position. This is also why the reconstruction must be built before the vendor script runs, so that the buyer's number exists independently rather than as a reaction to the vendor's.

A complete reconstruction also accounts for what should be out of scope entirely: retired projects, non production environments, and integration accounts that no human uses. Removing decommissioned systems is the discipline in decommissioned ALM projects still on the audit, and a reconstruction that scopes them out before the finding is written denies the audit the chance to count them in.

How we prepare a reconstruction under the four Rs

Respond. OpenText gives seven days notice before an audit and the right to copy relevant records, and the seven day notice clock starts immediately. Within that window we take over the single controlled channel and preserve the contractual, configuration, and usage records together, because the reconstruction depends on data that must be captured before anything is produced to the vendor.

Reconstruct. This is the operation the article is named for. We build the effective license position against entitlements and the Additional License Authorizations independently, confirming the metric for each product and deriving the cleaned counts the confirmed metrics require, before any vendor measurement script runs.

Rebut. We challenge every line of the finding against the reconstructed position, presenting the order history, the confirmed metrics, and the cleaned counts. The finding falls to the position the records actually support.

Resolve. We settle from the reconstructed count and, where it serves you, convert forward into an OpenPass agreement that records the confirmed metrics and the scoped estate, so the reconstruction becomes the baseline the next review must respect.

An anonymised outcome

The reconstruction matters because the remedy is severe. 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 a defense without an independent position concedes the basis of every charge. Our anonymised case files show what a prepared position achieves: an insurance ECM seat count finding fell from $7.2M to $1.6M, a 78 percent reduction built on an independent count that disqualified what the finding had treated as licensable. An ALM reconstruction does the same work, because it gives the buyer a number to defend rather than only a number to dispute.

Build the position before the script runs

The durable point is that an ALM entitlement reconstruction is the anchor of the defense, because it establishes an independent license position before the vendor measurement script ever runs. A buyer who confirms the metric, cleans the counts, and scopes the estate holds the finding to a position it prepared rather than one the audit imposed. To build the position, read reconciling ALM entitlements before an audit, named versus concurrent user counting in ALM audits, defending an ALM named user overclaim line by line, and decommissioned ALM projects still on the audit. For the full method see our ALM and LoadRunner audit defense track and our complete OpenText audit defense playbook for 2026. To prepare an ALM entitlement reconstruction before an audit hardens, open a case.