Skip to content
Duodata
Delivered engineering workflow

The data work behind the answer, done with your team.

Agreeing a definition is the start. The data behind it still has to be shaped, checked and kept in step — transformations, facts and dimensions built alongside your engineers, in your repositories, running on your platform. This page shows what that delivered work looks like.

One worked example below: net revenue, from the agreed definition to a checked result.

Gold-layer example

From an agreed definition to a checked result

Net revenue, end to end: what it means, where the data comes from, and the check that proves the output matches the source.

On this selection, demo is a Snowflake database: DEMO.GOLD.REVENUE_BY_QUARTER.

Net revenue = gross revenue − discounts − credits

Owner: Finance. Calendar quarters, USD, non-null decimal amounts.

Fictional example. The website computes these rows locally; it does not run SQL in a warehouse.

Layers

One engineering story within your platform

A coding harness and skills may generate transformation work; your warehouse and deployment tooling execute it. The Native App focuses on semantics, not on running every ingestion or transformation step.

  1. 01

    Bronze

    Source inputs and source totals used for reconciliation.

  2. 02

    Silver

    Existing structures and transformations, including mappings into a data vault where applicable.

  3. 03

    Gold

    Generated and maintained facts, dimensions and information-mart artifacts.

  4. 04

    Semantics

    Native semantic views and metric views exposing business meaning to analytics and AI.

Free pilot

Start a free pilot

Bring the gold or silver workflow you want to simplify. We agree the scope of a free pilot together before we start.