AI · 27 October 2026
Oracle Adds Business Semantic Layer to Ground AI Agents in Enterprise Data
Oracle has expanded its Autonomous AI Lakehouse with a Business Semantic Layer to give AI agents consistent definitions of enterprise data, with capabilities promised within 12 months. The move aims to make AI-generated insights more accurate, according to reporting by InfoWorld citing an Oracle statement.
What happened
Oracle has expanded its Autonomous AI Lakehouse with a Business Semantic Layer, a feature designed to give AI agents a consistent understanding of enterprise data. According to InfoWorld, which cites an Oracle statement, the aim is to make AI-generated insights more accurate and to help organisations scale agentic applications across business functions.
The layer builds reusable models of enterprise data. It combines catalogue annotations, SQL annotations imported from Oracle AI Database, and analytic views suggested by AI. Together these capture dimensions, measures, hierarchies, calculations and key performance indicators (KPIs), so that the same business definitions apply wherever the data is used.
These models feed Oracle's natural-language querying, data retrieval and analytics capabilities, including Select AI. The intention is that queries and insights rest on shared definitions rather than on each tool's own reading of the data. Oracle said the new capabilities will be available within the next 12 months.
Why it matters
The main point of this announcement is that the limiting factor for enterprise AI agents is often not the model but the meaning attached to the data it draws on. A semantic layer turns scattered tables and ad hoc definitions into a governed vocabulary that agents can reuse. That changes how an organisation operates: a question about revenue or customer retention should produce the same answer whether it comes from a dashboard, a chat interface or an automated workflow.
For leaders in experience and digital transformation, consistency of this kind determines whether AI can be trusted with decisions that affect customers and staff. When agents work from conflicting definitions, the result is wrong answers at the point of service and extra checking for employees. Shared definitions reduce that friction and make it easier to extend agentic tools into new functions without rebuilding the underlying logic each time.
The Renascence take
Most of the coverage will focus on the agents themselves. The more useful question is whether the organisation has agreed what its own numbers mean, because agents amplify whatever ambiguity already exists.
Most readers will hear "AI agents" and think about capability, but the real risk is cognitive: when every team defines churn, margin or active customer differently, an agent simply automates the confusion faster. The behavioural principle underneath is shared mental models, which reduce the effort needed to interpret information and build trust in it. A customer-obsessed operator should treat the 12-month roadmap as a prompt to audit its KPI definitions now, before any agent is allowed to answer a customer or make a recommendation.
Sources
This briefing was written by our Newsdesk, synthesising reporting from the outlets below. Follow the links for the original coverage.
FAQ
Questions we get on this topic
More in AI
Stay ahead of CX
Get the signal, not the noise.
The stories shaping customer experience — plus the Journal and Experience Loom — in your inbox.


