Capacity definitions in Micro Focus ALAs

Capacity metrics are where the largest Micro Focus findings are built, because capacity scales with the estate and a small misreading multiplies fast. Capacity definitions in Micro Focus ALAs decide what is measured, how it is measured, and over what period, and each of those choices can be read in a way that favours the finding. A buyer who understands the defined capacity unit can challenge a measurement that the contract never authorised.

This field note explains how capacity is defined in an Additional License Authorization, the measurement choices that inflate findings, and how to challenge them. It pairs with our ALA and entitlement review track.

What a capacity definition specifies

A capacity metric in an ALA is more than a number. The definition specifies the resource being counted, whether cores, processing units, throughput, or volume, the unit in which it is expressed, and frequently the basis on which it is measured over time. A grant for a defined capacity is a grant to operate within that boundary as the contract describes it, not a promise that the buyer will never momentarily approach it. The defined basis is the controlling fact.

Burst versus sustained

The most consequential measurement choice is whether capacity is read as a sustained level or a peak burst. Many systems spike briefly under load and settle far below the spike. An auditor who records the peak and treats it as the licensed level produces a finding far larger than the sustained operation justifies. Where the ALA defines capacity as a sustained measure, the burst is not the basis for the grant, and a finding built on burst values overreaches.

Measurement window and method

Capacity also turns on the window over which it is measured and the method used to capture it. A short window catches spikes; a representative window reflects normal operation. The tool that gathers the data, and whether it ran during typical or atypical load, shapes the result. A buyer is entitled to ask how a capacity figure was measured, over what period, and whether the method matches the definition in the grant.

Virtualization and partitioning

On virtualized and partitioned systems, capacity definitions interact with the rules for how cores or processing units are counted. An auditor may count the physical host where the ALA counts the assigned partition, or the reverse. Reading the capacity definition together with any virtualization and partitioning language is essential, because the two clauses jointly decide the licensable figure.

Challenging a capacity finding

The challenge is evidentiary and definitional at once. We establish the defined capacity unit and basis, obtain the measurement method and window, and test whether the figure in the finding reflects the sustained, contractually defined measure or a peak the grant never referenced. Where the two diverge, the finding is reduced to the defensible level. In a recent engagement, separating burst from sustained on a high throughput system removed the majority of a capacity based shortfall, mirroring the result in our E-03 case file, where an events per second and connector finding moved from $6.0M to $1.8M, a 70 percent reduction.

Capacity and the deployment topology

Where capacity is counted depends on how the system is built. A clustered deployment, an active passive pair, or a tiered architecture each present a different licensable surface, and the ALA language decides which nodes count. An auditor who sums capacity across every node, including passive and standby members, can overstate the licensable total substantially. Reading the capacity definition together with the standby and clustering provisions establishes which nodes are actually in scope, and it frequently removes passive members the opening figure counted as if they were live.

The right to see and reproduce the measurement

A capacity finding is a measurement, and a measurement can be examined. The buyer is entitled to understand what tool produced the figure, when it ran, over what interval, and against which definition. Where the measurement cannot be reproduced or does not match the contractual basis, the finding rests on data the buyer never agreed to accept. Insisting on a transparent, reproducible measurement that matches the defined capacity unit is a legitimate and often decisive part of the defense, because an unexamined number is not a proven one.

Converting a capacity dispute into a clean forward position

Once a capacity finding is reduced to its defensible level, the remaining question is how to license forward without repeating the dispute. A well drafted forward agreement defines the capacity metric precisely, fixes the measurement basis as sustained where appropriate, and writes in the standby and clustering treatment, so the next review starts from agreed definitions rather than contested ones. Resolving the present finding and closing the ambiguity that produced it are two halves of the same work, and doing both is how a capacity dispute stops recurring.

Capacity headroom is not overuse

A subtle but common error treats provisioned headroom as if it were licensed consumption. Systems are routinely provisioned with capacity above normal load so they can absorb growth and failover, and that headroom may never be used in production. Where the ALA licenses a measured capacity rather than the capacity a server is physically capable of, unused headroom is not a shortfall. Distinguishing provisioned capacity from measured, contractually relevant capacity removes a category of finding that counts what the hardware could do rather than what the licensed metric actually measures.

Preparing the capacity evidence in advance

Capacity disputes reward preparation more than almost any other kind. A buyer that already holds its own measurement, taken over a representative window against the contractual definition, enters the conversation with a credible figure rather than waiting to react to the vendor's. That preparation also reveals where genuine exposure exists, so it can be addressed deliberately rather than discovered under audit pressure. Holding an independent, definition aligned capacity record is the single most effective way to keep a capacity finding from running away from the facts.

Capacity is the highest leverage line in a finding

Of all the metrics in the Micro Focus catalogue, capacity offers a buyer the most leverage, precisely because it scales. A correction to a named user count adjusts a bounded figure, but a correction to a capacity basis, from peak to sustained, or from physical host to assigned partition, can move a finding by a large multiple across an entire estate. That is why capacity deserves the closest reading and the most rigorous evidence. The same property that makes a capacity misreading expensive makes a capacity correction powerful, and a buyer who masters the definition holds the line that moves the number most.

For the full method, read the complete OpenText audit defense playbook, and for capacity defense across products see our ALA and entitlement review track. If a capacity measurement drives your finding, open a case.