Xentrl Assurance Pipeline map wireframe v1.4

The Anaplan pipeline map

Every promotion in your Anaplan landscape, where it came from, where it went, and what authorized it.

Pipeline map showing one development model promoting into two parallel test and production branches, with one branch marked behind.
Pipeline map showing one development model promoting into two parallel test and production branches, with one branch marked behind.

What every line on this map carries

A promotion here is not a movement of metadata with a timestamp on it. Each one arrives with the things that make it answerable later.

Authorization, attached

  • Approved to be scheduled, then approved to be initiated
  • Requester, approver, and executor recorded as distinct roles
  • The approval bound to this promotion, not filed near it

Content and state

  • The revision tag, carrying the work items it was raised for
  • The comparison made before it moved, retained
  • The backup taken of the target, and who took it
  • Every step in the sequence, timestamped, with the user who performed it


A year later, the question of what this line was and who allowed it is a retrieval.

Three states a governed landscape holds

Authorization attached to the change

The approval exists before the change and travels with it.

Nothing reaching production outside the path

Changes that arrived another way are identified within minutes and put in front of someone who can determine whether they were intended.

What was approved is what is running

The running state is compared against the approved baseline, and the comparison leaves its own record.

Was What's Running Approved?

Why the authorization and the approved state have to sit outside the platform they describe, what conventional software architecture settled on over three decades, and what that means for an Anaplan landscape under audit.

Download the PDF