Dataplanedataplane

    Data Lineage

    See Where Every Field Comes From, and What It Feeds

    Lineage connects raw source columns to the business meaning your teams trust, and keeps that connection current as sources evolve. So when a column drifts or a feed changes, you can see which definitions, and which decisions, sit downstream before anyone files a ticket.

    The Idea

    Lineage Is Only Useful When It's Anchored to Meaning

    Every number on an executive dashboard started life as a raw column in a warehouse, an ERP extract, or an application database. Catalogs and warehouses document that a column exists. They don't tell you what it represents to the business, which definition it satisfies, or which decisions ride on it. That gap is where trust erodes.

    Dataplane builds lineage around your ontology, a record of which raw column populates which business attribute, kept current as sources drift. Anchored to those mappings, you can answer the two questions every data leader asks: what is this number built on, and what breaks if its source changes?

    Why It Matters

    Visibility That's Rooted in Meaning, Not Table Shape

    When a number looks wrong, the first question is always the same: where did this come from? Anchored to your business definitions, lineage answers that the fast way, and answers the reverse question every leader fears: what just quietly broke?

    Source-to-Attribute Mapping

    Every business attribute traces back to the exact raw column that populates it, at field-level granularity, not a coarse table-to-table diagram that hides where the real dependency lives.

    Blast Radius, Before It Lands

    When a source schema changes or a vendor renames a column, see which definitions, reports, and decisions sit downstream before anyone files a ticket. Impact analysis becomes a query, not a fire drill.

    Meaning That Travels With the Field

    Every mapped attribute carries its business definition with it: what the field represents, which source populates it, and the rules it must satisfy. That context follows the data wherever it goes.

    One View for Governance

    Roll lineage up into a single surface: which sources feed which attributes, where two divisions quietly disagree about the same data, and where one change ripples widest. Visibility that catalogs structurally can't produce.

    How It Works

    From Raw Column to Blast Radius, in Four Steps

    Follow a single field from the systems that record it to everything that depends on it, with the meaning intact the whole way.

    Step 1

    Every Number Starts as a Raw Column

    The same business fact is recorded under a different name in every system: a credit limit lives in the warehouse, the ERP, and an app database, each with its own column name and code. Nothing in the schema says they mean the same thing.

    One business fact · three columns
    dim_cust.acct_valWarehouse
    CUSTOMER.CREDIT_LIMITERP
    accounts.limit_usdApp DB
    Three columns. One real meaning. The schema can't tell.
    Step 2

    Mapped to What the Business Means

    Dataplane maps each raw column to the business attribute it populates, anchored to your ontology. The mapping is maintained as part of how your data is transformed and aligned, not redrawn by hand, so it stays current as sources drift.

    Mapped to one attribute
    dim_cust.acct_val
    CUSTOMER.CREDIT_LIMIT
    accounts.limit_usd
    Business attribute
    Customer · Credit Limit
    Definition + rules attached · kept current
    Step 3

    Carried Forward to Everyone Who Relies On It

    From a single attribute, trace forward to everything it feeds: dashboards, models, and the agents reading from your ontology. Each consumer inherits a clear record of what grounds the number it shows.

    Customer · Credit Limit
    Dashboards
    Models
    Agents
    Each consumer inherits what grounds the number it shows
    Step 4

    When a Source Drifts, the Blast Radius Lights Up

    A vendor renames a column or an upstream feed starts sending nulls. Instead of a confused stakeholder days later, you see exactly which definitions and which downstream consumers are about to break, before anyone files a ticket.

    CUSTOMER.CREDIT_LIMIT
    renamed · sending nulls
    Dashboards
    Models
    Agents
    The blast radius is visible before anyone files a ticket.

    Outcomes

    Trace Every Number, Stand Behind It

    0×

    faster to trace a questioned number back to its source

    0%

    of source changes caught before they reach a dashboard

    0%

    of mapped attributes traced to a source column

    Know What Your Data Is Built On, and What Depends on It

    See how Dataplane traces every field from source to consumer, anchored to your semantic model, so drift never breaks you silently again.

    Explore related capabilities: Data Ontology, Data Quality, and Agentic Systems.