HomeDefense Tracks › Exstream & CCM
Track 06 · Exstream & CCM

Exstream and customer communications audit defense.

We defend Exstream and customer communications management estates against OpenText compliance findings. The opening number is built on volume metrics that count the same communication more than once, channel by channel. We reconcile the metric to what was actually produced.

The Trap

What OpenText measures, and where the Exstream finding inflates.

Exstream came to OpenText through the Micro Focus acquisition and is governed by the Micro Focus Additional License Authorizations. Unlike a seat based product, Exstream and the wider customer communications management suite are typically licensed on volume, which makes the metric definition the whole game. A communications finding opens by counting output at the broadest possible unit and pricing the difference to your entitlement at list, with back maintenance and audit costs added.

The central overclaim is output channel counting. A single customer communication may be produced once and then rendered to print, email, web, and archive. A finding that counts each channel as a separate licensed unit multiplies one document into several, inflating the volume dramatically. Around this sit further traps:

  • Document overcharge, where multi page or composite documents are counted in a way the authorization does not support.
  • Non production and test volume, sample runs and proof of concept output counted against production entitlement.
  • Batch and API jobs counted at the transaction rather than the communication level.
  • Decommissioned applications whose historical volume is still swept into the count.

The defense rests on the production record. Reconciling what was actually generated, at the unit the authorization defines, against the inflated channel by channel reading is where a volume based finding comes down. The communication, not the rendering, is the thing that was licensed.

How We Defend It

The four Rs, applied to Exstream and CCM.

fn_01
R

Respond

We take over within the seven day notice window, agree an NDA, and route every request for Exstream volume data through a single controlled channel.

0 to 7 days
fn_02
R

Reconstruct

We rebuild the effective position against the Additional License Authorizations, establishing the exact volume unit the authorization defines before any vendor measurement runs.

3 to 8 weeks
fn_03
R

Rebut

We collapse multichannel output back to the communication, strip non production and test volume, remove decommissioned applications, and challenge the document count line by line.

4 to 12 weeks
fn_04
R

Resolve

We settle on the buyer's terms and, where useful, convert forward into a clean OpenPass agreement with a defined volume metric and audit protections.

4 to 10 weeks

The decisive material is the production volume report. Showing what was generated at the communication level, and how it maps to the authorization's unit, replaces the inflated channel count with a defensible figure. The full method is set out in the four Rs and in the complete OpenText audit defense playbook.

The Pattern

What a defended volume finding looks like.

Exstream findings follow the same shape as the rest of our practice. The opening number rests on a count that multiplies one communication across its channels, and the defensible figure emerges once production evidence maps output to the licensed unit. Across more than 200 defended OpenText and Micro Focus audits, the firm record holds steady.

200+
OpenText and Micro Focus audits defended since 2020
68%
Average reduction in the initial compliance finding
$90M
Cumulative claims mitigated against vendor positions
Related Field Notes

Reading on Exstream audit defense.

For the mechanics that apply across every product line, start with how to respond to an OpenText seven day audit notice and the reading Micro Focus ALAs paper.

Adjacent Tracks

Where communications estates overlap.

Under an Exstream volume finding? Open a case.

We take over within the seven day notice window. Buyer side only. Founded in 2020 by former vendor compliance leadership. Not affiliated with OpenText Corporation.