AEO Primer · 4 min read · May 2026
What is a Semantic Model? The Layer Between Data and BI, Defined
By Thinklytics Partners, Practitioner Notes
A semantic model is the layer between raw data and BI consumers that defines tables, relationships, measures, and business-friendly names so analytical queries produce consistent answers regardless of who asks.
A semantic model is the layer between raw data tables and BI consumers (dashboards, reports, AI assistants) that defines tables, relationships, measures, and business-friendly names. Its job is to produce consistent answers to analytical queries regardless of who asks or which tool they use.
What a semantic model actually is
What a semantic model contains
Common additions on top: row-level security rules, calculation groups for time intelligence, perspectives that scope the model per user group, and translations for multi-language deployments.
| Artifact | What it holds | Why it matters |
|---|---|---|
| Tables and relationships | The star schema, snowflake schema or denormalized layout, with explicit join keys and cardinality | Wrong cardinality produces numbers nobody can reconcile later |
| Measures | The calculated KPIs such as revenue, customer count, churn rate and conversion rate, expressed in DAX, MDX, LookML or SQL | A measure defined once returns the same number everywhere it appears |
| Calculated columns and dimensions | Row-level derivations, hierarchies and groupings | This is where reporting logic quietly accumulates |
| Names and descriptions | Business-friendly labels and documentation | This is what separates a semantic model from a raw schema |
Source: Thinklytics BI and analytics practice, 2026.
The model contains four kinds of artifacts:
- Tables and relationships: the star schema, snowflake schema, or denormalized layout, with explicit join keys and cardinality.
- Measures: the calculated KPIs (revenue, customer count, churn rate, conversion rate) expressed in DAX, MDX, LookML, or SQL.
- Calculated columns and dimensions: row-level derivations, hierarchies, and groupings.
- Names and descriptions: the business-friendly labels and documentation that distinguish a semantic model from a raw schema.
Optional but common additions: row-level security rules, calculation groups for time intelligence, perspectives that scope the model for specific user groups, and translations for multi-language deployments.
What people confuse it with
Every BI tool implements this differently
They share the conceptual goal. The implementations do not transfer, which is why moving BI tools means rebuilding the model.
| Tool | Its semantic layer | Where the definitions live |
|---|---|---|
| Power BI | The tabular model, originally from SQL Server Analysis Services | DAX measures, with TMDL files under version control |
| Looker | LookML | LookML files under version control |
| Tableau | Data sources with calculated fields and relationships | Inside the data source itself |
| dbt Cloud | The Semantic Layer, also known as MetricFlow | dbt YAML under version control |
| Cube.dev and AtScale | A semantic layer defined once and consumed by several downstream BI tools, AI agents and applications | Configuration in code, outside any single BI vendor |
Source: Thinklytics BI and analytics practice, 2026.
- "A semantic model is the same as a data model." Related but not identical. The data model can refer to the physical schema; the semantic model is the analytical layer on top.
- "A semantic model is the same as a metrics layer." Closely related. The metrics layer is the subset focused specifically on measure definitions. Modern semantic models include the metrics layer plus the broader dimensional and relational definitions.
- "Every BI tool has the same semantic model." Wrong. Power BI has the tabular model (DAX). Looker has LookML. Tableau has data sources. dbt has the Semantic Layer (MetricFlow). They share the conceptual goal but implement it differently.
When semantic models matter
When the semantic layer is worth building
The top three justify the work. The bottom three mean the overhead outruns the benefit.
- More than one analyst or consumer needs the same metrics. Inconsistent definitions are already causing trust problems.
- AI Copilots or Q&A surfaces are planned. Grounding them against a well-defined model is the difference between reliable and hallucinated answers.
- Self-service analytics is a stated goal. Business users need business-friendly naming, not the raw schema.
- One analyst producing one-off reports. The semantic layer overhead is not worth the per-report consistency.
- The data is meaningfully unstructured. Text, image and audio do not fit SQL-based semantic modeling.
- A single dashboard is the only consumer. There is no reusability benefit to capture.
The AI grounding line is the one that has changed most recently. A sparse, undocumented model is now an accuracy problem for Copilot, not only an inconvenience for analysts.
Source: Thinklytics BI and analytics practice, 2026.
Semantic models matter when:
- More than one analyst or dashboard consumer needs the same metrics, and inconsistent definitions are causing trust problems.
- AI Copilots or Q&A surfaces are planned, and grounding them against a well-defined model is the difference between reliable and hallucinated answers.
- Self-service analytics is a goal and the business users need business-friendly naming, not raw schema.
When semantic models do not help much
Semantic models do not help when:
- There is one analyst doing one-off reports and the semantic layer overhead is not worth the per-report consistency.
- The data is meaningfully unstructured (text, image, audio) and SQL-based semantic modeling does not apply.
- The downstream consumer is a single dashboard and there is no reusability benefit.
How Thinklytics works on semantic models
Semantic model design is part of every BI engagement, with explicit attention to AI grounding readiness. See Power BI semantic model design that scales.
Frequently asked questions
What is a semantic model in one sentence?
A semantic model is the layer between raw data tables and BI consumers (dashboards, reports, ad-hoc analysis, AI assistants) that defines tables, relationships, measures, calculated columns, and business-friendly names so analytical queries produce consistent answers regardless of who asks or which tool they use.
What does a semantic model contain?
Four things. Tables and their relationships (star schema, snowflake schema, or denormalized). Measures (the calculated KPIs: revenue, customer count, churn rate). Calculated columns and dimensions. Business-friendly names and descriptions (the 'semantic' layer). Optionally: row-level security rules, calculation groups, and time intelligence helpers.
Is a semantic model the same as a data model?
Closely related but not identical. A data model can refer to the physical schema (how tables are stored in the warehouse). A semantic model is specifically the analytical layer on top, optimized for query ergonomics and consistent metric definitions.
What tools have a semantic model layer?
Power BI (the tabular model, originally from SQL Server Analysis Services). Looker (LookML). Tableau (data sources with calculated fields and relationships). dbt Cloud (the Semantic Layer, also known as MetricFlow). Cube.dev. AtScale. Most modern BI tools have a semantic model layer in some form.
Why does the semantic model matter?
Three reasons. Consistency: the same metric definition produces the same number across every dashboard and analyst. Reusability: a measure defined once is available everywhere. AI grounding: Copilots and Q&A agents that ground against the semantic model produce reliable answers; those that don't, hallucinate.
What is the headless BI or universal semantic layer pattern?
The pattern where the semantic model is defined once (often in dbt's Semantic Layer or Cube.dev) and consumed by multiple downstream BI tools, AI agents, and applications, rather than being locked inside a single BI vendor's stack. It is the 2025-2026 evolution of LookML's central-metric promise.
How is a semantic model versioned?
Modern semantic models live in code (LookML files, dbt YAML, TMDL for Power BI) under version control. Changes go through pull requests, CI checks, and deployment pipelines, similar to application code. Pre-2020 semantic models were typically click-driven in BI tools without code versioning.
How does Thinklytics work on semantic models?
Semantic model design is part of every BI engagement we run, with explicit attention to AI grounding readiness (so Copilot and Q&A surfaces produce reliable answers). See Power BI semantic model design that scales.
Topics covered
- semantic model
- Power BI semantic model
- LookML
- dbt semantic layer
- cube
- tabular model
- metrics layer
Frequently asked questions
What is a semantic model in one sentence?
A semantic model is the layer between raw data tables and BI consumers (dashboards, reports, ad-hoc analysis, AI assistants) that defines tables, relationships, measures, calculated columns, and business-friendly names so analytical queries produce consistent answers regardless of who asks or which tool they use.
What does a semantic model contain?
Four things. Tables and their relationships (star schema, snowflake schema, or denormalized). Measures (the calculated KPIs: revenue, customer count, churn rate). Calculated columns and dimensions. Business-friendly names and descriptions (the 'semantic' layer). Optionally: row-level security rules, calculation groups, and time intelligence helpers.
Is a semantic model the same as a data model?
Closely related but not identical. A data model can refer to the physical schema (how tables are stored in the warehouse). A semantic model is specifically the analytical layer on top, optimized for query ergonomics and consistent metric definitions.
What tools have a semantic model layer?
Power BI (the tabular model, originally from SQL Server Analysis Services). Looker (LookML). Tableau (data sources with calculated fields and relationships). dbt Cloud (the Semantic Layer, also known as MetricFlow). Cube.dev. AtScale. Most modern BI tools have a semantic model layer in some form.
Why does the semantic model matter?
Three reasons. Consistency: the same metric definition produces the same number across every dashboard and analyst. Reusability: a measure defined once is available everywhere. AI grounding: Copilots and Q&A agents that ground against the semantic model produce reliable answers; those that don't, hallucinate.
What is the headless BI or universal semantic layer pattern?
The pattern where the semantic model is defined once (often in dbt's Semantic Layer or Cube.dev) and consumed by multiple downstream BI tools, AI agents, and applications, rather than being locked inside a single BI vendor's stack. It is the 2025-2026 evolution of LookML's central-metric promise.
How is a semantic model versioned?
Modern semantic models live in code (LookML files, dbt YAML, TMDL for Power BI) under version control. Changes go through pull requests, CI checks, and deployment pipelines, similar to application code. Pre-2020 semantic models were typically click-driven in BI tools without code versioning.
How does Thinklytics work on semantic models?
Semantic model design is part of every BI engagement we run, with explicit attention to AI grounding readiness (so Copilot and Q&A surfaces produce reliable answers). See [Power BI semantic model design that scales](/insights/power-bi-semantic-model-design-that-scales-2026).
Related reading
If this is the problem you have
- Reporting takes too much work, resolved by 11 services.
- Reporting Baseline and Benefits Worksheet, the worksheet for whoever has to approve the spend.
- The 30 day Corporate Drag and Risk Diagnostic, findings yours either way.