Relationship context is an essential capability because it allows AI to reason over information that reflects how the organization actually works, not just what individual Limitations of Semantic Layers for Enterprise AI Context documents say.” “A context layer connects those relationships and is often the difference between simple information retrieval and making trustworthy decisions,” says Tony Grout, chief product and technology officer at M-Files. Several solution providers announced branded products for these capabilities, including Atlassian’s Teamwork Graph, SAP Knowledge Graph, and Snowflake semantic views. I understand that these countries may not have the same data protection laws as the country from which I provide my personal information. Get monthly curated content, technical resources, and event updates designed to support your Salesforce Architect journey.
Data 360 functions as a headless BI https://aicurated.com/ layer that natively powers Tableau Next, with calculated insights as the core architectural mechanism. Before it acts, it runs a vector search across the customer’s support history, surfacing a transcript where the customer flagged a billing issue three weeks earlier. That definition becomes the single source of truth across the organization.
And the architectural gap between governing a SQL query and governing an autonomous analytical agent is much wider than most enterprises realize. Since 1994, her research has explored how organizations generate business value from data assets. Organizations that do this well can scale AI faster, at lower cost, and with greater confidence that their data is being used in appropriate ways. The researchers recommend that AI Risk Management Framework organizations take three actions to ensure that their investments generate value. A semantic layer can also help AI models and agents interpret enterprise data with context, leading to more accurate and less risky outputs. In a 2024 survey of 349 executives, just 21% rated their organizations’ data curation practices as somewhat or very well developed.
Level 3: Catalog & Business Definitions (Governance Layer)
Smaller organizations may not need all the layers, especially if data sources are relatively clean, have simple relationships, and are developed using business-friendly terms. Safely developing these assets requires starting with tightly scoped use cases and grounding your security controls in how modern collaboration actually happens,” Torgerson says. David Torgerson, VP of technology and security at Lucid Software, says the most critical security Generative AI Risk Management Framework consideration isn’t just restricting access but rather ensuring clean documentation and visible workflows.
It assembles runtime context from both structured and unstructured systems to provide the information needed for decision-making.” “Once meaning is established, the next challenge is understanding what is relevant, and this is where a context layer comes in. It’s important to understand that knowledge graphs are often implemented with graph databases.
Without business context, agents produce technically correct but practically useless analysis. It’s domain knowledge — the accumulated understanding of how your business actually works — and most semantic layers have no mechanism to store, version, or serve it. Business context tells the agent what the metric means in your organization’s specific reality. But most implementations were designed for a world where humans ask questions and interpret results.
Best Practices for Creating a Performant Semantic Model in Tableau Semantics
Build a semantic layer for agentic AI with EDB Postgres AI and Amazon Bedrock AgentCore Artificial Intelligence – Amazon Web Services (AWS)
Build a semantic layer for agentic AI with EDB Postgres AI and Amazon Bedrock AgentCore Artificial Intelligence.
Posted: Tue, 03 Nov 2026 08:00:00 GMT source
It can also capture organizational expertise, including judgments about data quality and exceptions to standard business rules. That context has become increasingly important as organizations expand their use of generative AI, the researchers write. It sits between an organization’s data and the people or machines using it, explaining what the data represents, how different pieces relate to one another, and which rules govern its use. Organizations may also have different standards for data quality, access, permitted uses, and regulatory compliance. Different systems may label the same customers, products, or transactions in different ways and apply different definitions and rules. As companies deploy generative AI AI Act tools and agents, many are discovering that giving an artificial intelligence system access to enterprise data is not equivalent to giving it the context needed to understand that data.
Looker’s semantic layer governs Gemini Enterprise data for user trust
When any tool can connect to anything, the architecture underneath determines whether those connections produce reliable results or compounding inconsistency. In the meantime, architects can bridge semantic systems today using platform APIs, with tools like Claude, Codex, or Cursor, generating translation code without waiting for native vendor tooling. A multi-org Data 360 strategy built on Data Cloud One, it standardizes identity resolution, semantic models, and governance across business units while each org retains federated autonomy. The semantic layer exists to enforce one definition, one lineage chain, one governed understanding of what a metric means. Not all enterprise data lives in Salesforce, and physically ingesting everything creates a duplication problem that a semantic layer is designed to prevent.
- The semantic layer provides the necessary constraints and context that enable AI Agents to operate reliably and deliver trustworthy insights.
- The semantic layer’s compiler, armed with the codified business logic and understanding of the underlying data model, takes care of generating the correct, optimized SQL query.
- In conclusion, for organizations looking to harness the power of AI Agents for data analytics, a semantic layer is not merely an option – it is a fundamental prerequisite.
- However, just as a human analyst needs a solid understanding of the business and its data to perform effectively, so too do AI Agents.
- Level 3 (Governed Knowledge) — persistent business context, fiscal calendars, organizational rules.
- If you’re evaluating purpose-built platforms that provide agent-ready governance natively, deployment timelines are typically 6-10 weeks for enterprise implementations.
- For organizations where the bottleneck is data access, Snowflake Cortex solves the problem.
- Close this gap by either extending your semantic layer with custom infrastructure or evaluating purpose-built analytics platforms that embed semantic governance within a broader agent-ready architecture.
- The remaining 80% — context, knowledge, memory, orchestration — requires architectural capabilities that most standalone semantic layers were not designed to deliver.
You need to understand where it ends and where agent-ready governance begins — then close the gap incrementally. Your semantic layer includes persistent business context — fiscal calendars, business event timelines, domain-specific rules, investigation history, and accumulated organizational knowledge. Each investigation starts from scratch, ignoring everything the organization has already learned.