OFICIAL Databricks Newsroom Gadgets · Jul 21, 2026

Why R&D Data Belongs in the Lakehouse

In brief · 4 sentences
Based on Databricks Newsroom · Jul 21, 2026

Databricks and cellcentric detail a four-year effort to build a governed AI context layer for R&D data, integrating Unity Catalog, Lakehouse Federation, and MCP for human and agent access.

Why R&D Data Belongs in the Lakehouse
Databricks Newsroom — Databricks
Key points
·
Main topic: the reason R&D Data Belongs in the Lakehouse.
·
Category affected: gadgets and hardware.
·
Figures mentioned: 27, 90, 2.0.
·
The information comes from an official source.
·
The next step is to watch availability, pricing and real-world impact.

The useful question is what changes for users, developers or buyers, and whether the announcement stays industry context or becomes something people can actually use.

cellcentric, a joint venture of Daimler Truck and Volvo Group, describes its shift from siloed R&D data sources to a unified governed context layer built on Azure and Databricks over four years. The company integrated Unity Catalog for governance, Lakehouse Federation to include on-premises SQL sources, and Delta Sharing for cross-boundary data exchange. The result, the Data Hub, serves as both a marketplace for employees and an MCP server for AI agents, ensuring consistent access controls and traceability.

The Data Hub’s foundation is exemplified by the Fuel Cell Passport, an internal data product that consolidates five enterprise systems—including SAP S/4HANA and IoT telemetry—across seven hierarchy levels. The product refreshes daily and uses a state-based temporal model to support engineering investigations. Daily data quality checks ensure completeness, while a context-coverage badge tracks documentation progress, turning after-the-fact cleanup into an actionable metric during development.

Governance remains central to the Data Hub’s operation, with identity and access flowing through Azure AD and Unity Catalog. Agents access data only through the authenticated user’s identity, ensuring they cannot bypass governance or write to production systems. The architecture supports multiple AI clients, including custom agents on Databricks Model Serving and Claude via Foundation Model APIs, all operating within the same permission boundary as human users.

Observability is embedded through Unity AI Gateway and MLflow tracing, enabling structured analysis of agent interactions and continuous evaluation of context, tools, and responses. Engineers now work within AI-assisted environments connected to the Data Hub’s MCP, allowing agents to assist with pipeline scaffolding and documentation while maintaining human oversight. The company states this marks the first time it has a single, governed entry point for data discovery and natural-language interaction, subject to existing access controls.

Original source → Deals on Clipraptor.com →
Extracted signals · detected in the story
WhyData BelongsLakehouseUnity CatalogLakehouse FederationMCPDaimler TruckVolvo GroupOurD-heavy27902.0