How Daunat mapped its applications and data flows to plan its IT modernization
To scope its production planning and MES projects and identify rationalization opportunities, Daunat's IT department used Boldo to build a shared view of its applications, their dependencies and how they connect to master data and business processes.
At a glance
Daunat is a snack food manufacturer with five production sites. With support from CGI, it built its functional map in Boldo and documented its applications and the interfaces between them. The map is now the shared repository teams use to prepare changes to production planning and MES, and to assess options for optimizing the architecture.
Teams keep it up to date themselves, without relying on an expert. They use it to scope projects faster and involve the right people from the start.
- Sector: food manufacturing, snacks
- Production sites: 5
- Revenue: EUR 330 million
Knowledge of the IT landscape, scattered across teams and files
A mid-sized manufacturer's IT landscape grows project by project and site by site. The information exists, but it is spread across several files and a handful of experts, which makes every project slower to scope.
Daunat's IT department wanted a shared map of its IT landscape, maintained by its own teams, so that every modernization project would start from a common baseline.
Project goals
- Bring knowledge of the IT landscape into one repository the teams maintain
- Get a well-documented view of the application portfolio
- Map the interfaces between applications and the core data they exchange
A pace that fits around day-to-day IT work
Daunat's IT department led the project. Sébastien Weyl, an enterprise architect at CGI, structured the approach and coached contributors through the modeling work, directly in Boldo.
Training · 2 days
Workshops to define needs, get started with Boldo and set up the mapping framework.
Initial mapping · one quarter
An enterprise architecture effort, guided by an expert CGI architect, to define the IT master plan and build a culture of decentralized mapping across teams.
Governance and day-to-day use · ongoing
The map is governed, and teams update it often and rely on it to prepare projects.
How the IT department uses the map
Prepare production planning and MES changes
Find the connected applications, the interfaces affected and the owners to involve in scoping.
Assess rationalization options
Spot applications that meet similar needs, then review how they are used and what depends on them before deciding to retire one.
Share knowledge of the IT landscape
Help teams find the information a project needs and add to it, in a single repository.
Model and share business processes
Describe processes together, link them to the applications and data behind them, and make them available to the relevant teams.
Illustrative diagram of data flows around a manufacturing ERP
Before changing the ERP, see what depends on it
The flow map shows which applications exchange data with the ERP and what data moves between them. Project scope and the teams to involve can then be defined from shared information.
Spotting overlapping applications is not enough to decide to retire one. The map supports that decision by showing how each application is used and what depends on it. For a detailed approach, see our page on scoping application migrations.
Ease of adoption and flexibility in how we use the information made the difference: everyone finds, updates and uses the map without relying on an expert. It has become our shared reference for scoping complex projects.
Are you the CIO of a mid-sized company? See how Boldo helps CIOs understand and transform their IT landscape.
Plan your IT transformation with a shared view of your systems
Planning an ERP change or an application rationalization? Tell us about your project.