AI Executive Office — CXO Assistant Platform  ·  View 12 of 30  ·  4 · Data

Data Flow — Source to Answer

Where data comes from, at what cadence, and what happens to a batch that fails its quality gate.

Editable source SVG draw.io All views
Sources ERP tables + OData Procurement REST Projects REST Documents SharePoint Supply chain events Ingest CDC pull 15 min Scheduled copy nightly Eventstream seconds Document crawl delta · 4 h Land Bronze as received Quality gate row count · schema Quarantine flagged, not dropped Conform Canonical mapping tenant config Entity resolution supplier · project Silver conformed Serve Warehouse star schema Semantic model measures Search index + ACL Entity graph edges Freshness register per source Consume Tool plane typed reads Detection sweep hourly Power BI same measures fails staleness on every answer Data Flow — Source to Answer, with Cadence External / third party Interface / broker Queue / topic Data store Decision point Risk / gap Application we own Security / platform failure / alternate synchronous No source is real-time by default. Each declares a freshness contract, and the answer states which one it used. v 1.0 · owner Data & AI Global Practice · date 2026-09

Decisions

  • No source is real-time by default. Each declares a freshness contract, and the platform publishes the staleness rather than hiding it. "What changed since yesterday?" is only answerable for sources whose contract supports it
  • A failed quality gate quarantines the batch and flags the affected measures. It does not drop the rows and it does not silently serve the previous load as though it were current
  • Power BI reads the same semantic model. The platform does not build a parallel definition of a KPI that the finance team already owns

Deliberate omissions

  • Document ingestion is shown as one box here; view 14 is the pipeline
  • Entity resolution is drawn as a single step. It is a queue with a human review path in practice, which is a programme-level workstream rather than a diagram

Risks

  • Entity resolution across ERP, procurement and projects is the hardest data problem in the platform and the one most likely to be underestimated. "Which suppliers affect projects already at financial risk?" is unanswerable until supplier identity is resolved across three systems
◀  Data Architecture — Zones by Rebuildability All views Canonical Data Model  ▶
Solution Architecture v1.0 · Azure-native, multi-tenant, sovereign-capable · Data & AI Global Practice · 2026-0912-data-flow