---
title: "Data Content for AI: Rethink the Separate Semantic Layer"
description: Define data once across conceptual models, logical models, and ontology meaning. Rethink the need for a separately maintained semantic layer for AI.
image: https://www.maoperatingsystem.com/hubfs/Data-Context.png
---

[Skip to content](https://www.maoperatingsystem.com/articles/practical-ai-why-ai-requires-data-context-the-secret-to-successful-data-driven-ai-outcomes#main-content)

M&A Operating System

Open main navigation

Close main navigation

- Contact us

 Contact us

[All posts](https://www.maoperatingsystem.com/articles/all)

 November 13, 2026

# Practical AI: Why AI Requires Data Context: The Secret to Successful Data-Driven AI Outcomes

![Picture of Andrew Bush](https://www.maoperatingsystem.com/hs-fs/hubfs/Andrew%20Bush.png?width=50&name=Andrew%20Bush.png) By  [Andrew Bush](https://www.maoperatingsystem.com/articles/author/andrew-bush)  ·   8 minute read

*"Over the last few years, we have focused on helping clients improve business decision-making and risk management through better data management platforms and practices. That work has consistently centered on defining data more clearly, structuring it more effectively, and aligning it more closely to how the business actually operates. What is now becoming clear is that this same foundation is not just beneficial, it is a prerequisite for successful AI outcomes. In this article, we outline why data context sits at the center of this new age."*

## Introduction

Most organizations are investing heavily in AI. Many have modern data platforms; some have centralized data in warehouses and lakes; and all have access to powerful models. Yet many are not seeing meaningful outcomes at scale. This isn’t a model problem or a tooling problem; it’s a data problem. More precisely, it’s a lack of data context.

Traditionally, much of this knowledge lived in the heads of the data modelers who built the warehouse and the BI engineers who designed the dashboards. They knew what the records represented, which relationships mattered, and how to interpret exceptions. That understanding informed their models, queries, and reports, even when it was never written down. The game has changed. AI models are now consuming the data and generating their own queries and analyses. The business knowledge those engineers relied on needs to be captured explicitly and made available to the AI.

A semantic layer is often proposed to supply that meaning. We advocate maintaining one common data definition that combines the business understanding traditionally captured in conceptual models, logical data models, and data ontologies. That definition should drive the warehouse and the context supplied to AI, so the same business meaning is carried through both.

### The Question Has Changed

For the last decade, the dominant question in data was simple: *Does our data platform support analytics?* Today, that question is no longer sufficient. It has been replaced by something more fundamental: *Does our data support AI?*

Analytics teams and AI systems both need consistent business meaning. AI makes the gaps more visible because it can generate queries across domains without the working knowledge that experienced analysts use to interpret the data.

## What Data Context Needs to Define

Data context describes what the data represents and how it should be interpreted. It includes the subjects, attributes, identities, relationships, and business rules that people use when deciding which records answer a question.

A common definition needs enough detail to support both implementation and interpretation.

| Element | What the definition needs to explain |
| --- | --- |
| Subjects and concepts | What exists in the business, what each concept means, and where its boundaries lie. |
| Attributes and record grain | What each attribute describes and what one record represents. |
| Identity | The identifiers used across systems and the rules for recognizing the same subject. |
| Relationships and roles | How subjects relate and which roles apply at each end of a relationship. |
| Values and constraints | Allowed values, their meanings, required relationships, and validation rules. |
| Lifecycle and time | How a subject changes state, when facts apply, and how history is represented. |
| Measures and calculations | Business definitions, units, aggregation rules, inclusions, and exclusions. |
| Sources and processing | Mappings to actual data, lineage, transformations, freshness, and known limitations. |

## Data Content: One Common Definition of Everything We Need to Know About Data

A semantic layer connects business concepts and measures to the data that represents them. It helps consumers work with terms such as customer, account, and revenue while using defined relationships and calculations. Our recommendation is to include that business meaning in the common data definition used to design and maintain the data itself.

> **Data Context = Conceptual Model + Semantic Ontology**

In our approach, the **conceptual model** describes the organizational layout of data around the subjects the business manages. It establishes where the information about each subject belongs and how it relates to information about other subjects, so we can store and manage everything we know about that subject coherently. Logical data modeling makes this layout precise through attributes, identifiers, relationship structures, and constraints.

The **semantic ontology** describes the meaning needed to understand what a subject is, what it can do, and how it interacts with other subjects in business transactions and processes. It defines the concepts, contextual roles, lifecycle states, and business rules that explain those interactions. For a Person, that includes the meaning of acting as a booker, participating as a traveler, or delivering a service as a guide, and how each role relates to a booking, departure, or organization.

Consider a person who books a trip for two other people. The common model defines Person, Booking, and Departure, identifies the relationships between them, and records who booked and who will travel. Its business definitions explain how a traveler differs from a booker and which participation counts toward a repeat-traveler measure. Those definitions should guide the warehouse structures, the metric calculation, and the AI assistant answering the question.

The practical test is whether the definition contains enough information to build the data, validate it, and explain its correct use. The label attached to the model matters less than completing that work and keeping it consistent.

## Don't Build a Separate Data Ontology or Semantic Layer

We see many organizations attempting to retroactively build data ontologies and semantic layers on top of existing warehouses because they want AI to interact with their data. They have already designed the data models and built the warehouse. Now they are trying to reconstruct the business meaning in another layer, with another set of definitions to maintain.

Instead, we encourage organizations to use that demand for AI as an opportunity to change how the work is done. Pivot the design effort toward a single definition of the data that contains enough information to generate both the data models and the semantic ontology definitions. Capture the conceptual layout, logical structure, business meaning, relationships, and rules together as part of the same design process.

Maintain that common definition in version control. A change to a subject, relationship, or business rule can then be reviewed in one place, with its impact on both data structures and semantic meaning visible together. Regenerate the affected models, schemas, and semantic definitions from the approved version, and validate that the implementations remain aligned.

Where a BI tool or AI service requires its own semantic representation, generate or configure it from this shared definition. The organization maintains one authoritative source for what its data is and what it means, with the representations needed by its platforms derived from that source.

## Why AI Fails Without Context

AI systems interpret data as they query it. When context is missing, the model has to guess which entities, relationships, and field definitions apply. A syntactically correct query can then answer a different business question from the one intended.

Explicit data context gives AI defined concepts and relationships to work with. It reduces the interpretation left to the model and gives teams a basis for checking whether the resulting query follows the intended business rules.

## Common Pitfalls & How to Solve

When working with clients who are trying to understand why their AI initiatives are not generating the outcomes they expect, we consistently see one or more of the following pitfalls.

### The First Trap: No Common Data Layer

In many organizations, AI is connected directly to operational systems, each of which defines data differently. There is no shared structure, no consistent definitions, and no unified identity model. The result is fragmentation, where AI becomes dependent on a collection of disconnected sources, each with its own interpretation of the business. At that point, reliability is not just difficult; it is structurally constrained.

### The Second Trap: The Two-Layer Model

Some organizations move directly from source-shaped warehouse data to consumer-specific datasets. Transformation, consolidation, and business definitions are then recreated for individual reports and use cases. AI inherits those separate interpretations when it tries to work across them.

Consumer-specific products have a place, supported by a reusable model of the underlying subjects and their relationships. Our article on [four-layer data architecture](https://www.maoperatingsystem.com/articles/practical-data-why-two-layer-data-architectures-dont-fail-immediately-they-fail-gradually) explains how we separate sourcing, transformation, consolidation, and consumption.

### The Third Trap: Reverse Engineering Meaning

A common assumption is: *“We have all our data centralized, surely we can derive context from it.”* In practice, this rarely works. A data warehouse captures transformations, aggregations, and reporting logic, but it does not fully capture true entity definitions, relationships between entities, lifecycle and state transitions, or business meaning.

As a result, teams attempt to reconstruct context after the fact, creating both gaps and inefficiencies. The same work gets done twice: first to build the platform, and again to rediscover what the data actually means.

## Define Context First

When working with organizations, we start with what the data represents and the definitions needed to use it. We have previously written about our [data-first approach and subject-based data modeling](https://www.maoperatingsystem.com/articles/practical-data-when-your-data-models-reflect-past-leaders-instead-of-the-business-its-time-for-subject-based-data-modelling) to simplify and automate data warehouse design.

The common definition should inform the target logical model, warehouse schemas, validation rules, and semantic representations supplied to consumers. Questions about identity, roles, and business meaning can then be settled during design and maintained as the platform evolves.

## Model Around Real-World Subjects

At the core of this approach is subject-based data modeling, where data is organized around real-world entities such as people, companies, products, accounts, and transactions. Each subject is defined with attributes, identifiers, relationships, and lifecycle states. This ensures data is modeled based on what it is, not how it is used; a distinction that is critical for enabling AI to operate beyond predefined use cases.

### Codifying Data Context

The common data definition needs a maintained, machine-readable representation. We can capture it in version-controlled JSON definitions that cover the structure, meaning, and usage rules required by the business.

From that source, teams can generate database and API schemas, validation rules, documentation, and the semantic models required by their tools. Changes to a subject, relationship, or metric can be traced back to the same approved definition.

### The Missing Capability: A Centralized Data Design Authority

A **Data Design Authority** owns and maintains the common definition. Its responsibilities include conceptual and logical models, business and ontology definitions, identifiers, relationships, and the rules that connect those definitions to implemented data. This gives changes an accountable owner and keeps schemas, semantic representations, and documentation aligned as the business evolves.

### Enabling AI Through Context

AI needs access to the relevant parts of that definition when it uses the data. An assistant answering a question should be able to retrieve the applicable concepts, role definitions, time rules, and calculations, together with the mappings to the available data products or query interfaces.

Schema checks and business validation can then test whether the proposed query or result follows those rules. Maintaining the definition and making it available to consumers are both part of the implementation.

## Why This Approach Works

Maintaining one common definition reduces repeated interpretation across teams. New consumers can reuse established identities, relationships, and calculations, while changes to those definitions have a clear source and owner. Business needs can still require extensions, but each team starts from the same agreed model.

### Define Once. Use Everywhere

Most organizations still operate in a reactive model: build the data, then try to understand it. The more effective model is the opposite: define the data, then build systems that reflect that definition.

## Bonus Section: Comparing Ontology Frameworks

In our work, we have come across many frameworks used to describe data. Like everything else in this industry, there is no one-size-fits-all answer. The options include modeling languages, reusable ontologies, validation standards, and exchange formats, each addressing different parts of the problem.

| Framework or standard | What they focus on | What they are good for |
| --- | --- | --- |
| **RDF / RDFS** | Linked data, shared identifiers, classes, properties, and basic relationship hierarchies. | Connecting descriptions across sources and expressing a shared vocabulary. [Reference](https://www.w3.org/TR/rdf-schema/) |
| **OWL 2** | Formal definitions and logical axioms for classes, relationships, equivalence, and restrictions. | Making meaning precise and supporting automated inference and consistency checking. [Reference](https://www.w3.org/TR/owl2-primer/) |
| **SKOS** | Business vocabulary, labels, synonyms, classifications, and broader or narrower concepts. | Organizing terminology and mapping different teams’ vocabularies. [Reference](https://www.w3.org/TR/skos-reference/) |
| **SHACL** | Conditions that RDF data must satisfy, including required properties, types, and cardinalities. | Validating that data conforms to the expected definitions and reporting violations. [Reference](https://www.w3.org/TR/shacl/) |
| **FIBO** | Reusable definitions of financial business concepts and their relationships. | Starting from established financial-services meaning for entities, contracts, and instruments. [Reference](https://edmcouncil.org/frameworks/industry-models/fibo/) |
| **BFO** | General categories and relationships that provide a foundation for domain ontologies. | Keeping multiple domain ontologies aligned to a common conceptual foundation. [Reference](https://www.iso.org/standard/74572.html) |
| **LinkML** | Maintained schemas with classes, properties, constraints, and semantic mappings. | Generating schemas, documentation, and semantic artifacts from a shared model. [Reference](https://linkml.io/linkml/) |
| **JSON Schema** | The structure, data types, and validation constraints of JSON documents. | Defining and checking JSON records, API payloads, and data contracts. [Reference](https://json-schema.org/overview/what-is-jsonschema) |
| **JSON-LD** | Representing linked data in JSON with explicit identifiers and vocabulary references. | Exchanging ontology definitions and linked data through JSON interfaces. [Reference](https://www.w3.org/TR/json-ld11/) |

We do not necessarily recommend choosing a single solution or picking one of these frameworks to describe all your data. Step back and use the elements you need for your situation. One organization may need shared terminology and validation rules. Another may also need formal reasoning or reusable industry definitions. Bring those elements into the common definition you maintain, with enough information to generate the models and representations your systems require.

## Final Thought

Most AI strategies focus on models, tooling, and infrastructure. But the real leverage point sits one layer above all of that, in how your data is defined. AI success is not determined by how much data you have; it is determined by how well your data is understood.

At M&A Operating System, this data-first focus is the foundation of our approach to AI. We have spent years building capabilities in data definitions and logical data models, and in automating master data management and modern data platforms. Today, that same foundation enables us to deliver true data context for AI.

Through our Data Design Authority capability, we help organizations define and codify their data models, automate and align their data platforms, and enable AI to leverage their data fully. If you are looking to move beyond fragmented data and unlock real AI outcomes, the starting point is not another tool; it is properly defining your data, once and for the long term.

---

Share: [Share this page on LinkedIn](http://www.linkedin.com/shareArticle?mini=true&url=https://www.maoperatingsystem.com/articles/practical-ai-why-ai-requires-data-context-the-secret-to-successful-data-driven-ai-outcomes) [Share this page on Email](mailto:?body=https://www.maoperatingsystem.com/articles/practical-ai-why-ai-requires-data-context-the-secret-to-successful-data-driven-ai-outcomes)

## Related posts

[![Photo illustration of a stone wall foundation in the foreground with a glowing blue-and-amber rising bar chart and trend line over a blurred night city skyline.](https://www.maoperatingsystem.com/hubfs/Data%20First.png)](https://www.maoperatingsystem.com/articles/practical-data-when-use-cases-outrun-the-data)

[AI Adoption](https://www.maoperatingsystem.com/articles/tag/ai-adoption)

### [Practical Data: When Use Cases Outrun the Data](https://www.maoperatingsystem.com/articles/practical-data-when-use-cases-outrun-the-data)

[![3D illustration of multiple source-system ID tags (CRM, Billing, Web, Partner, Loyalty, Legacy, Marketing) converging into a single glowing 'Authoritative Identity' block on a pedestal, radiating out to icons for people, organizations, products, and systems.](https://www.maoperatingsystem.com/hubfs/ChatGPT%20Image%20Aug%2028%2c%202026%2c%2012_54_06%20PM.png)](https://www.maoperatingsystem.com/articles/practical-data-ai-doesnt-need-more-data-it-needs-an-identity)

[AI Adoption](https://www.maoperatingsystem.com/articles/tag/ai-adoption)

### [Practical Data: AI Doesn't Need More Data. It Needs an Identity!](https://www.maoperatingsystem.com/articles/practical-data-ai-doesnt-need-more-data-it-needs-an-identity)

[![](https://www.maoperatingsystem.com/hubfs/ChatGPT%20Image%20Mar%2016%2c%202026%2c%2004_48_49%20PM.png)](https://www.maoperatingsystem.com/articles/practical-data-when-your-data-models-reflect-past-leaders-instead-of-the-business-its-time-for-subject-based-data-modelling)

[Data Governance](https://www.maoperatingsystem.com/articles/tag/data-governance)

### [Practical Data: When Your Data Models Reflect Past Leaders Instead of the Business — It’s Time for Subject‑Based Data Modelling](https://www.maoperatingsystem.com/articles/practical-data-when-your-data-models-reflect-past-leaders-instead-of-the-business-its-time-for-subject-based-data-modelling)

[![M&A Operating System Logo](https://www.maoperatingsystem.com/hs-fs/hubfs/MAOS-Logo-sqr-1.png?width=179&height=155&name=MAOS-Logo-sqr-1.png "M&A Operating System Logo")](http://M&A%20Operating%20System)

#### A Boutique Advisory Focused on Practical, Experience-Led Execution

facebook-f icon linkedin-in icon twitter icon instagram icon

**Pages**

Home

Services

Portfolio

About

Contact

FAQ

Landing Page

Thank You

**Resources**

Blog

Watch a Demo

Academy

Webinars

Product Changes

(c) M&A Operating System 2026

```json
{
  "@context" : "https://schema.org",
  "@type" : "BlogPosting",
  "author" : {
    "@type" : "Person",
    "name" : "Andrew Bush",
    "url" : "https://www.maoperatingsystem.com/articles/author/andrew-bush"
  },
  "dateModified" : "2026-10-07T21:17:41.720Z",
  "datePublished" : "2026-04-07T19:44:05.000Z",
  "headline" : "Data Content for AI: Rethink the Separate Semantic Layer",
  "image" : [ "https://www.maoperatingsystem.com/hubfs/Data-Context.png" ],
  "mainEntityOfPage" : {
    "@id" : "https://www.maoperatingsystem.com/articles/practical-ai-why-ai-requires-data-context-the-secret-to-successful-data-driven-ai-outcomes",
    "@type" : "WebPage"
  },
  "publisher" : {
    "@type" : "Organization",
    "logo" : {
      "@type" : "ImageObject",
      "url" : "https://www.maoperatingsystem.com/hubfs/MAOS-Logo-sqr-1.png"
    },
    "name" : "M&A Operating System"
  }
}
```

```json
{
  "@context" : "http://schema.org",
  "@type" : "Article",
  "author" : {
    "@type" : "Person",
    "name" : [ "Andrew Bush" ],
    "url" : "https://www.maoperatingsystem.com/articles/author/andrew-bush"
  },
  "datePublished" : "2026-04-07T19:44:05+0000",
  "description" : "Define data once across conceptual models, logical models, and ontology meaning. Rethink the need for a separately maintained semantic layer for AI.",
  "headline" : "Practical AI: Why AI Requires Data Context: The Secret to Successful Data-Driven AI Outcomes",
  "image" : "https://www.maoperatingsystem.com/hubfs/Data-Context.png",
  "publisher" : {
    "@type" : "Organization",
    "logo" : {
      "@type" : "ImageObject",
      "url" : ""
    },
    "name" : "M&amp;A Operating System"
  },
  "url" : "https://www.maoperatingsystem.com/articles/practical-ai-why-ai-requires-data-context-the-secret-to-successful-data-driven-ai-outcomes"
}
```