Exstream transactional versus capacity metrics

There is a quiet but expensive distinction at the heart of many Exstream findings: whether the buyer is licensed for what the system produced or for what the system could produce. A transactional metric charges by actual output, the documents or communications genuinely generated. A capacity metric charges by provisioned ability, the throughput or volume the deployment was sized to handle. The two are not the same, and they rarely produce the same number. Exstream transactional versus capacity metrics is the difference between paying for consumption and paying for headroom, and an audit that treats provisioned capacity as if it were produced output charges the buyer for volume it never created.

This article draws the distinction, shows where a finding blurs it, and explains how a buyer holds the line. It supports our Exstream and customer communications audit defense practice and links up to the complete OpenText audit defense playbook for 2026.

What each metric actually measures

A transactional metric is consumption based. It asks how many documents, pages, or communications the system genuinely produced over a period, and it charges against that produced volume. It is the metric most buyers expect, because it tracks use. A capacity metric is provisioning based. It asks what the deployment was configured to support, the cores, the throughput, the sized volume ceiling, and it charges against that capacity whether or not the capacity was ever fully used. A buyer can be licensed on either basis, and which one applies is a question the agreement and its order documents answer, read against the Additional License Authorizations where the product is governed by them. Establishing which metric governs is the foundation laid in what an Exstream volume based license metric is.

Where the finding blurs the two

The blur happens when a finding measured on a transactional metric is inflated using capacity logic, or when a capacity figure is treated as though it were produced volume. The most common pattern is reading the system's sized throughput, the volume it was provisioned to handle at peak, and presenting that figure as if it were the volume produced. Provisioning for a peak is prudent operation, not consumption, and a buyer sizes a platform above its average load precisely so it can absorb statement cycles and seasonal surges. Charging that headroom as produced output is the capacity for consumption error described in how OpenText measures Exstream usage in an audit, and it compounds the peak window problem set out in how Exstream volume metrics inflate an audit finding.

How a buyer holds the distinction

The defense is to establish which metric the contract actually uses, then to insist the measurement follow that metric rather than the one that produces the larger number. A buyer holds the distinction by:

• Reading the licensed metric from the agreement, so the basis of charge is settled before any figure is discussed.
• Producing transactional records of genuine output where the metric is transactional, tied to the contractual unit and scoped to production.
• Refusing to let provisioned capacity stand in for produced volume, showing the gap between what was sized and what was generated.
• Reading a representative period, so neither metric is inflated by a peak.

This is part of the wider reconciliation described in reconciling Exstream entitlements before an audit, where the licensed metric and the genuine usage are established together.

How the four Rs apply to the metric question

The method settles the metric early and defends it precisely. In the respond stage the firm takes the single controlled channel inside the seven day notice window, so neither a capacity figure nor a raw transactional export reaches the vendor unmanaged. In the reconstruct stage it reads the licensed metric from the contract and rebuilds usage on that basis, before any vendor measurement script runs. In the rebut stage any place the finding substitutes capacity for transaction, or a peak for a representative period, is challenged at its source. In the resolve stage the settlement reflects the correct metric and the forward agreement states the metric unambiguously, so the next audit cannot blur consumption with provisioning.

A representative outcome

In a recent engagement, an Exstream finding had been built by reading the platform's provisioned throughput, the volume it was sized to handle at peak, and presenting that capacity figure as produced output. The buyer's actual transactional volume, the communications genuinely generated over a representative period, was well below the provisioned ceiling. Once the buyer established that its agreement charged on a transactional basis and produced the output records to prove genuine volume, the capacity based figure fell away. The matter settled well below its opening number, consistent with the reductions the firm sees across customer communications matters, with nothing introduced beyond what the production records contained.

Transactional versus capacity in one line

Exstream transactional versus capacity metrics decide whether the buyer pays for output produced or capacity provisioned, and a finding holds only when it charges on the metric the contract actually uses. Settle the metric, prove the transactions, and the headroom drops out of the number. To see how the corrected metric becomes a settlement, read reducing an Exstream finding with volume evidence, and to settle the metric on your own finding you can open a case with our team.

For the first week after a notice arrives, read the OpenText seven day notice response white paper.