Exstream non production and test volume scope

Production software is licensed for production. The output a system generates while it is being tested, developed against, or recovered in a drill is a byproduct of running the business, not a use of the license that the buyer pays for by volume. Yet when an Exstream audit pulls raw output exports, those byproducts arrive mixed in with genuine production, and unless someone separates them they swell the count. Exstream non production and test volume scope is the discipline of drawing that boundary clearly, so the volume the finding rests on is the volume the license was actually consumed by.

This article explains which output is non production, why it tends to creep into a finding, and how a buyer scopes it out. It supports our Exstream and customer communications audit defense practice and links up to the complete OpenText audit defense playbook for 2026.

What counts as non production volume

Non production volume is everything Exstream generates outside genuine live operation. The main categories are consistent across most estates:

• Test output, generated to validate a template, a data mapping, or a release before it goes live. It is often high in volume because testing repeats.
• Development output, produced while building or changing communications, never delivered to a customer.
• Disaster recovery and failover output, generated to prove a recovery environment works or during an actual recovery exercise.
• Quality assurance and sampling runs, produced to check formatting and accuracy, again repeating and never delivered.

None of this is communication delivered to a customer. It is the cost of running the platform responsibly, and treating it as licensable production volume charges the buyer for doing the right thing.

Why non production creeps into the finding

Non production volume enters the finding for a simple reason: raw system exports do not label themselves. A counter that records every document the engine produced does not distinguish a test run from a customer mailing unless the environment, the job, or the output stream is tagged. When the vendor measures from those raw exports, everything the engine touched is counted as use, and the burden falls on the buyer to show what was not production. This is the same dynamic described in how OpenText measures Exstream usage in an audit, where the measured figure is only as scoped as the records it was built from.

How a buyer scopes non production out

The defense is to separate environments and label output at the source, so production and non production are distinguishable in the records the vendor sees. A buyer scopes non production out by:

• Mapping the environment topology, identifying which systems are production and which are test, development, or disaster recovery.
• Tying output records to their originating environment, so a test run is identifiable as a test run.
• Reading volume over a representative period from production only, the principle behind how Exstream volume metrics inflate an audit finding.
• Documenting the boundary so it can be presented, not merely asserted, which connects to documenting Exstream output volume for a rebuttal.

Done before the notice, this scoping is part of reconciling Exstream entitlements before an audit. Done after, it is one of the four tests in how to challenge an Exstream document count.

How the four Rs apply to scope

The method treats production scope as something to establish early and defend precisely. In the respond stage the firm takes the single controlled channel inside the seven day notice window, so raw mixed exports do not reach the vendor unmanaged. In the reconstruct stage it maps environments and rebuilds production volume from production systems only, before any vendor measurement script runs. In the rebut stage the vendor's figure is challenged wherever it includes test, development, or disaster recovery output, and each inclusion is traced back to the environment that produced it. In the resolve stage the settlement reflects production only volume and the forward agreement defines production scope so the next audit cannot fold the byproducts back in.

A representative outcome

In a recent engagement, an Exstream finding had been built from exports that combined a busy production cycle with a major disaster recovery exercise and a release testing period that happened to fall in the same window. The buyer mapped its environments, tied each output stream to its source, and removed everything that was not delivered to a customer. The genuine production volume was a fraction of the measured figure. 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.

Scope in one line

Exstream non production and test volume scope is the line between volume the buyer delivered and volume it merely generated to run the platform well, and only the former belongs in a finding. Draw the line at the environment, document it, and the count returns to genuine use. To see how the scoped figure becomes a settlement, read reducing an Exstream finding with volume evidence, and to scope your own estate cleanly 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.