Before data can drive every aisle, warehouse and recommendation, someone has to build the foundations
Before
with no shared architecture or governance: a risk of widespread technical debt
After
data initiatives delivered
data initiatives delivered
domains: ML/AI, BI, streaming
continuous engagement
Intermarché, France's third-largest food retail network, launches an ambitious data program: reduce product stockouts, tailor store assortments, know each customer better and accelerate its e-commerce. A dedicated Data Factory is set up to run the initiatives in parallel: ML, BI reporting, real-time streaming. But building fast without a solid architecture means piling up invisible debt that will eventually bring production to a halt.
SITUATION BEFORE
- Operational baseline
- A fledgling Data Factory running more than 15 initiatives in parallel (ML/AI, BI, e-commerce streaming) with no shared reference architecture, each team inventing its own foundations.
- Teams affected
- All the Data Factory teams and the business teams consuming their output (supply chain, stores, e-commerce): a risk of widespread technical debt eventually blocking production.
- Hidden costs
- Without a reference architecture, technical debt builds up silently across 15+ simultaneous initiatives. What was meant to speed things up would have ended up slowing them down.
- Why it was not solved earlier.
- The Data Factory was created to move fast: the pressure to deliver ML and BI use cases left little room for cross-cutting architecture work upfront.
THE STORY
OUR APPROACH
5 steps to get there
Architecture scoping and business study
For each initiative: analysis of the business processes involved, mapping of the data objects, assessment of the maturity of the available sources, and selection of the ingestion, integration and delivery patterns suited to the use case. The outcome: an architecture sheet shared between the Data Factory and the business teams before any development starts.
Modeling and governance for each project
Working with project teams on data modeling (schemas, relationships, granularity), writing the data dictionary, tracing data lineage and defining quality patterns. Every domain (ML/AI, BI, streaming) follows the same conventions, which keeps pipelines readable and maintainable over time.
ML & AI initiatives
Architecture and governance of the machine learning use cases: product recommendation engine, performance comparison across stores, and deeper customer insight. For each model put into production: definition of the features, the training data flows and the delivery interfaces to the business applications.
Reporting & operational management
Design of supply chain dashboards to monitor stockouts and logistics flows, and of store dashboards for store managers. Scoping of reporting needs with the business teams to ensure a consistent reading of performance at every level of the organization.
Industrializing the data architect function
Structuring the data architect role within the Data Factory: architecture review templates, a pattern library by type of initiative, an onboarding process for new projects. The goal: enable the Data Factory to take on new use cases without starting from scratch every time.
RESULTS
The measurable impact
More than 15 initiatives delivered to production across three complementary domains: ML recommendations and customer insight, supply chain monitoring and store dashboards, real-time streaming for e-commerce, all built on a shared architecture and lasting governance.
Is your organization launching a data program? Nobori Partners steps in from the scoping phase to lay down the architecture and governance that will keep your initiatives sustainable over time
Book a discovery callSIMILAR CASE STUDIES
operating subsidiaries with IT systems to coordinate
After 25 years, a digital retailer split into 6 operating subsidiaries and its architecture function could no longer keep up. Nobori Partners built a shared business/tech language, mapped functions and data, and repositioned the function.
Read the case studysaved on back-office processing
Blank, the Crédit Agricole group neobank for freelancers, was growing fast, but its operations teams were flying blind, held back by a DynamoDB architecture designed for scalability, not for analysis. In 4 months: a real-time pipeline, self-service dashboards, 1 FTE freed up.
Read the case study