Enterprise Metadata Management System  ·  View 01 of 22  ·  Context and scope

System Context

Who depends on the platform, what it harvests from, and what it pushes back out.

Editable source SVG draw.io All views
Metadata sources — 200 registered systems
Metadata sources — 200 registered systems
Warehouses & Lakehouses
Snowflake · Databricks
Warehouses & Lakehouses...
BI & Reporting
Power BI · Tableau
BI & Reporting...
ETL / Orchestration
dbt · Airflow · Spark
ETL / Orchestration...
SaaS & Operational Apps
SAP · Salesforce
SaaS & Operational Apps...
People
People
Data Consumer
analyst · scientist
Data Consumer...
Data Steward
curates a domain
Data Steward...
Domain Owner
accountable
Domain Owner...
Governance & Security
CDO · CISO office
Governance & Security...
Data Engineer
platform team
Data Engineer...
Metadata consumers
Metadata consumers
Policy Enforcement
Unity Catalog · Ranger
Policy Enforcement...
Data Quality Platform
Soda · Great Expectations
Data Quality Platform...
ITSM & Incident
ServiceNow
ITSM & Incident...
Notebooks & IDEs
embedded lookup
Notebooks & IDEs...
Enterprise Metadata Platform
Active metadata hub
Enterprise Metadata Platform...
Enterprise platforms
Enterprise platforms
Identity Provider
Entra ID · SCIM
Identity Provider...
Notification
Teams · email
Notification...
Observability
Prometheus · Grafana
Observability...
schema · usage
schema · usage
reports · fields
reports · fields
run lineage
run lineage
object metadata
object metadata
find and trust data
find and trust data
curate · classify
curate · classify
certify · approve
certify · approve
policy · audit
policy · audit
integrate · automate
integrate · automate
labels · tags
labels · tags
scope · results
scope · results
impact tickets
impact tickets
GraphQL
GraphQL
OIDC · groups
OIDC · groups
tasks · alerts
tasks · alerts
metrics · traces
metrics · traces
Enterprise Metadata Platform — System Context
Enterprise Metadata Platform — System Context
External / third party
External / third party
Person or role
Person or role
Security / platform
Security / platform
batch
batch
event / async
event / async
synchronous
synchronous
two-way
two-way
Out of scope: running quality tests, enforcing access at query time, and storing data values.
Out of scope: running quality tests, enforcing access at query time, and storing data values.
v 1.0 · owner Data & AI Architecture · date 2026-08
v 1.0 · owner Data & AI Architecture · date 2026-08
Text is not SVG - cannot display

Decisions

  • The platform is an active metadata hub, not a passive catalog: metadata flows back out to policy enforcement, quality tooling and incident management. A catalog that only absorbs becomes shelfware.
  • Federated ownership with central policy. Domains own their assets, terms and certification; the central function owns the canonical model, the policy catalogue and the stewardship SLA.
  • Four personas are first-class, not one: consumer, steward, domain owner and platform engineer each have a distinct surface. Governance and security read the same graph through the console.

Explicit non-goals

  • It does not execute data-quality tests — results are ingested from the engines that already run them (view 15).
  • It does not enforce access at query time — it publishes labels that the platforms already enforcing access consume (view 05).
  • It does not store data values. Only bounded profile statistics, and none at all for confidential or restricted assets (view 20).

Assumptions to confirm

  • 200 source systems in scope at go-live, ~40 distinct connector types.
  • 20,000 licensed users, ~2,000 daily active; single tenant, EU data residency.
  • Entra ID is the enterprise IdP and group source, synchronised over SCIM.