Share this on:
What You'll Learn
A semantic layer sits between an organization’s data and the people or systems using it. It explains what the data represents, how different data assets relate to one another, and which rules govern their use. It is the layer that tells an AI agent what “revenue,” “customer,” or “active user” means, so the agent stops guessing from raw table names and starts answering from definitions the business has already agreed on. By 2030, Gartner expects universal semantic layers to be treated as critical infrastructure, alongside data platforms and cybersecurity, not an optional analytics upgrade.
What a semantic layer does
A semantic layer standardizes a handful of things that would otherwise be defined differently everywhere. Examples include metrics, dimensions, relationships, and access rules. These definitions live in one place and get consumed everywhere, without any tool reinventing the logic.
That is the part that makes AI agents trustworthy rather than merely fast. An agent querying raw tables has to infer all four of these on its own, every time. An agent querying a semantic layer inherits definitions someone already got right.
Why AI agents fail without shared business meaning
When information is pulled from applications, documents, and data platforms, the business context that gives it meaning is often stripped away in the process.
Different systems label the same customers, products, or transactions differently, and apply different rules for what counts and what doesn’t.
Gartner’s research is direct about the consequence. Without a clear understanding of the relationships and rules inside an organization’s data, agents cannot operate accurately and are far more likely to hallucinate, introduce bias, and produce unreliable results.
The practical failure looks like this. An agent with raw access to enterprise data has to infer what a metric means, then deliver a confidently wrong answer with the same voice it uses for a right one. Multiply that across every team, every dashboard, and every AI tool asking the same question a different way, and the organization ends up with a system where the correct answer depends entirely on which tool happened to ask it.
How top data & AI platforms are building the semantic layer
Every major platform is converging on the same principle. And that is – define meaning once and let agents consume it everywhere, while building from different starting points.
Salesforce
built its semantic layer, Tableau Semantics, natively into Data 360. Semantic Models are first-class Salesforce metadata, governed definitions of metrics, dimensions, and relationships that human analysts and Agentforce agents query from the same source, so a figure an agent gives a customer matches the figure an analyst reports to a regulator.
Snowflake
Splits its context layer in two. Horizon Context is the governed foundation, semantic views storing business logic directly in the warehouse. Cortex Sense sits above it as a runtime layer, assembling context from query history, metadata, and dashboards the moment an agent asks a question. In Snowflake’s own testing, a frontier agent grounded in this context layer answered complex enterprise questions correctly 86.3% of the time with direct SQL access alone, and at roughly a third of the query cost.
Databricks
Announced Genie Ontology at its Data + AI Summit in June 2026. A self-improving knowledge graph, also currently in preview, fed by three new Unity Catalog capabilities – –
- Business Glossary for authoritative term definitions
- Domains for scoping which context an agent can see
- Metrics for governed, reusable KPI definitions queryable from SQL, BI tools, and agents alike.
That Metrics layer is open source and built to the Open Semantic Interchange standard. In Databricks’ own internal benchmark, agent accuracy reached 84.5 percent when grounded in governed definitions of terms like “engagement,” compared with 52.4 percent for the strongest general-purpose agent working without that context.
Informatica
Takes the governance-first route through its Business Glossary and CLAIRE AI. Authoritative business terms and policies, feeding CLAIRE’s natural language and data quality agents so a term like “customer” or “policy” holds one definition.
Why a semantic layer is a governance discipline
Most organizations frame the semantic layer as an analytics upgrade. Gartner’s framing argues otherwise. Semantic layer belongs alongside data platforms and cybersecurity as core infrastructure. The moment “revenue” is defined once, someone has to own that definition, arbitrate when finance and sales disagree on it, version it as the business changes, and keep it correct as new sources arrive.
An agent generating queries against raw tables has to reconstruct that judgment on every single question. An agent generating queries against governed metric definitions inherits it, which is the real distinction between a semantic layer and a text-to-SQL shortcut that happens to work in a demo.
That governance discipline is also what keeps a semantic layer accurate over time. A semantic layer built without active ownership degrades the same way ungoverned data does.
How LumenData builds the semantic layer for enterprises
LumenData is a trusted partner with Informatica, Salesforce, Snowflake, and Databricks, & many more leading data and AI platforms. Most enterprises run more than one of these platforms. Salesforce for customer workflows, Snowflake or Databricks for the warehouse and lakehouse, and increasingly, agents that need to reason across all of them at once.
Each platform’s native semantic layer works exactly as designed within its own ecosystem. The opportunity comes when an agent needs to reason across more than one, where a shared definition has to travel with the data instead of living inside a single platform.
That’s what LumenData builds. Our own architecture pattern – Informatica governance feeds a Data 360 semantic layer that activates Agentforce. This is how we define business meaning once, at the governance layer, using Informatica’s business glossary, catalog, and lineage as the single source of truth.
We enforce that one definition everywhere it gets consumed, in Data 360’s Tableau Semantics, in Snowflake’s Horizon Context, in Databricks’ Unity Catalog Metrics. This way, “revenue” means the same thing no matter which platform’s agent is asking.
The organizations getting real value from enterprise AI are the ones whose business meaning is defined once and trusted everywhere it is asked.
Ready to build the semantic layer that can help drive enterprise AI success ? Explore LumenData’s Enterprise Data Management services to see how we architect the data-to-agent workflow from the governance layer up.
Connect today.
About LumenData
LumenData is a leading provider of Enterprise Data Management, Cloud and Analytics solutions and helps businesses handle data silos, discover their potential, and prepare for end-to-end digital transformation. Founded in 2008, the company is headquartered in Santa Clara, California, with locations in India.
With 150+ Technical and Functional Consultants, LumenData forms strong client partnerships to drive high-quality outcomes. Their work across multiple industries and with prestigious clients like Versant Health, Boston Consulting Group, FDA, Department of Labor, Kroger, Nissan, Autodesk, Bayer, Bausch & Lomb, Citibank, Credit Suisse, Cummins, Gilead, HP, Nintendo, PC Connection, Starbucks, University of Colorado, Weight Watchers, KAO, HealthEdge, Amylyx, Brinks, Clara Analytics, and Royal Caribbean Group, speaks to their capabilities.
For media inquiries, please contact: marketing@lumendata.com.
Ready to Build the Semantic Layer That Drives Enterprise AI Success?
Authors
References
- Gartner: Lack of Semantics Causes Inaccurate AI Agents and Wasted Spending
- Gartner: Top Predictions for Data and Analytics in 2026
- Snowflake: Cortex Sense for Enterprise AI Agents
- Snowflake: Horizon Context
- Databricks: Introducing Genie One, Genie Agents, and Genie Ontology
- Databricks: What's New with Unity Catalog at Data + AI Summit 2026
- Informatica: Business Glossary vs. Data Catalog


