CDO Demonstration EnvironmentDemo data

Data Lineage

Trace the Executive Sales Dashboard to its sources.

Demo data

Illustrative trace: Executive Sales Dashboard. Timestamps show latest demo activity at each node, not a single synchronized refresh.

Trace for “Executive Sales Dashboard”

· read from the top down

  1. Business view

    Executive Sales Dashboard

    Owner: Demo Executive Office

    Last update 10:35 AM

    Transformation: Executive KPI aggregation

    sourced from

  2. Intelligence

    Sales Intelligence

    Owner: Sales Operations

    Last update 10:30 AM

    Transformation: Region and brand roll-up

    sourced from

  3. API

    Unified Sales API (/sales/orders v2.3)

    Owner: Enterprise Applications

    Last update 10:28 AM

    Transformation: Standard sales model

    sourced from

  4. Control plane

    Integration Hub

    Owner: Integration Team

    Last update 10:26 AM

    Transformation: Validation, routing, retries

↑ Parallel source systems

SAP ERP

Billing documents extract

Enterprise Applications · 10:22 AM

POS & Sales

Store sell-out events

Sales Operations · 10:25 AM

Distributor System

Order file ingestion

Channel Management · 10:14 AM

Why executives care

When two reports disagree, lineage could help explain the difference: you can see which source, which transformation and which refresh time produced each figure — and who owns the data.

Why IT cares

Impact analysis before change. If the distributor file schema changes, lineage shows every API, flow and dashboard downstream that must be regression tested.

Current trace summary

  • 3 source systems · 1 API · 1 intelligence layer
  • Latest source activity: POS & Sales at 10:25 AM
  • Distributor System: 12 invalid records; 296 awaiting delivery at 10:14 AM
  • Data owner of record: Sales Operations