Skip to main content
Zemerc
Customer stories

What changed in the operation and the governed record that supports the outcome.

Credible industrial outcomes must be traceable to the measurements, decisions, approvals and records that produced them.

How a measurement becomes a traceable outcomeMeasurementRecordControlDecisionOutcomeTraceable in both directionsWhere a customer story beginsWhere the story concludes
Flow showing how a measurement becomes a governed record, passes through control, informs a decision and supports a traceable outcome
  • 0Applications
  • 0Operating areas
  • 0Industries served
  • 0Flagship applications
The portfolio behind a story

A credible story begins with a clear evidence base.

Portfolio counts shown here describe current application coverage and are not presented as customer-performance claims.

  • 0ApplicationsEach independently operable
  • 0Operating areasFrom projects through governance
  • 0IndustriesEnergy, offshore, process, EPC
  • 0Flagship applicationsThe most established of the set
Story domains

Six domains from which customer stories may be drawn.

Each domain is supported by relevant applications, registers and controls. A customer account is published only after client approval.

By sector

Where customer stories may originate.

Select a sector to see relevant operating areas and applications.

What an engagement is intended to change

Four outcomes used to evaluate an engagement.

These statements describe how the applications are designed to work and are not presented as outcomes achieved for a named client.

  • Record established

    An existing paper or spreadsheet register can be established as a governed system record where appropriate.

  • Workflow governed

    Approval routes are enforced by application controls rather than informal practice.

  • Evidence retention

    Append-only audit history retains who changed what, when and against which revision.

  • Decision traceability

    Published figures are included only where they can be traced to the measurements and approvals supporting them.

Publishing standard

Three conditions before a customer story is published.

  • Client approval requiredNothing is published until the organisation described has reviewed and approved the account.
  • Figures remain traceableA number is published only where the supporting record can be identified.
  • Written with those involvedPublished accounts are based on the client record owner and delivery team’s reviewed input.

Could your operation support a customer story?

Engagements typically begin with a defined register, project or asset and a demonstration using representative records and controls.