Dimensions CM concurrent versus named licensing

Dimensions CM can be licensed by named users or by concurrent users, and the difference between the two models decides how large a finding can be. An audit that applies named user counting to a concurrent entitlement, or that ignores which model the agreement actually grants, charges for a population the concurrent pool was never meant to cover.

Dimensions CM, the software configuration and change management product that came to OpenText through the Micro Focus acquisition, sits at the centre of a development organisation, which means a wide population touches it: developers, build engineers, release managers, and occasional contributors. That breadth is exactly why the licensing model matters. A named model charges for each individual granted access, while a concurrent model charges only for the peak number of simultaneous sessions, and most of these products are governed by the Additional License Authorizations, where the model that applies is defined rather than assumed.

How the two Dimensions CM models compare

Under a named model, every individual with an account is a licensable user, so the count is the size of the provisioned population. Under a concurrent model, the count is the high water mark of simultaneous sessions, which for a large but intermittent population is far smaller than the headcount. The two produce very different numbers for the same estate, and an audit that counts named seats against a concurrent entitlement inflates the finding by the entire gap between the provisioned population and the peak that ever logged in together. The general mechanics of this distinction are set out in named versus concurrent user counting in ALM audits.

The wider Dimensions family adds its own counting traps, because Dimensions CM and Dimensions RM are related but distinct, and the way users are counted across them is a known source of overclaim, the subject of Dimensions CM and RM user counting traps. The model question sits on top of those traps: first establish which model the entitlement grants, then apply the correct counting method to the population or the concurrency, not the other way around.

Where the model decides the finding

The decisive question in a Dimensions CM finding is which model the agreement grants, because the entitlement that governs a concurrent license is not the entitlement that governs a named one. The agreement and the Additional License Authorizations fix the model, and reading them against the deployment is the first move, the discipline described in reconciling ALM entitlements before an audit. Only once the model is confirmed does the right evidence become clear: a population list for a named model, or session concurrency data for a concurrent one.

Where the model is concurrent, the defense follows the same path as any concurrent challenge: confirm the model, then produce the peak simultaneous session figure from the logs, the method set out in how to challenge an ALM concurrent user headcount. The related source control product AccuRev raises parallel model and counting questions, explored in AccuRev user and stream license questions, and the same reasoning carries across.

How we defend a Dimensions CM model finding 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 agreement, the account inventory, and the session logs are preserved together, because the model that applies and the count that follows both depend on those records.

Reconstruct. We build the effective license position against the Additional License Authorizations before any vendor script runs, establishing whether the entitlement is named or concurrent and gathering the population or the peak concurrency that the confirmed model requires.

Rebut. We challenge every line that applies named counting to a concurrent entitlement, or that counts the provisioned population against a concurrent pool, presenting the agreement and the concurrency data. The finding falls by the difference between the model asserted and the model granted.

Resolve. We settle on the count that reflects the genuine model and, where it serves you, convert forward into an OpenPass agreement that records whether Dimensions CM is named or concurrent and how it is measured, so the next review cannot switch models to inflate the count.

An anonymised outcome

The reason the model question is worth settling is the remedy that follows a 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 reading a concurrent entitlement as named multiplies the error across every charge at once. Our anonymised case files show what correcting the basis of a count can achieve: an insurance ECM seat count finding was reduced from $7.2M to $1.6M, a 78 percent reduction built on counting only what genuinely belonged in the finding. A Dimensions CM finding responds to the same correction, because the agreement fixes the model the audit must use.

Confirm the model before you accept the count

The durable point is that Dimensions CM is defended by first settling which model the entitlement grants, because named and concurrent counting produce very different numbers for the same estate. A buyer who reads the agreement, confirms the model, and produces the matching evidence holds the finding to the basis that was actually purchased. To build the position, read named versus concurrent user counting in ALM audits and Dimensions CM and RM user counting traps, alongside how to challenge an ALM concurrent user headcount and AccuRev user and stream license questions. For the full method see our ALM and LoadRunner audit defense track and our complete OpenText audit defense playbook for 2026. If a Dimensions CM finding has applied the wrong model, open a case.