After detailing in our previous articles the preparatory phase and selection process that led us to choose Maps System, this latest article focuses on the actual implementation of the project and the lessons learned from this experience.

The project phase: between satisfaction and learning

Highlights

The deployment of Maps System has been distinguished by several positive aspects:

1. A committed project team
   We benefited from the high availability of our teams, on both the business and technical sides. This mobilization, sometimes difficult to achieve in this type of project, was a key success factor.

2. A robust parameter-setting methodology
   Maps System has demonstrated real maturity in its approach to parameterization, with a proven, structured methodology.

The data bible: a fundamental task

One of the most crucial aspects of the project was the creation of the “data bible”. Although tedious to draw up, this exhaustive document proved absolutely essential. For each piece of data to be referenced, we documented :

• Its origin (source system)
• Destination (target systems)
• Update frequency
• Its owner
• Its technical manager
• Associated quality rules
• Validation processes

This painstaking, albeit time-consuming, work has enabled us to :

• Clarifying responsibilities
• Establish clear processes
• Guarantee the consistency of the repository
• Facilitating future maintenance

Management processes and rules

The project also involved :

1. An in-depth review of existing data management processes
2. Development of specific rules for

   :Polylang placeholder do not modify

Areas for improvement

Technical training

One notable point of improvement concerns the training of key technical users. This took place prior to parameterization on a generic environment. In retrospect, this approach was not optimal:

• Difficulty in projecting concepts onto our real-life context
• Need to “relearn” when actually setting parameters
• Time lost in the transition from training to practice

Business involvement underestimated

Although we had anticipated a high level of business involvement, the actual scale of the project exceeded our initial forecasts. This involvement proved necessary on several levels:

• During initial setup
• In the training phase
• For process validation
• In the test phase
• For routine maintenance

One of the aspects to be taken into account in this type of project is the fact that, by their very nature, the professions have many other actions to carry out in their day-to-day work, and that initiating such a project is an additional constraint for them.

Key lessons for system sustainability

A tool at the heart of the IS

It is crucial to understand that a Master Data Management tool is not a peripheral tool, but rapidly becomes a central component of the information system. Its long-term viability depends on :

• A strong commitment at the start
• A long-term commitment
• Clear, active governance
• Well-defined maintenance processes

The importance of the MDM referent

A major learning point is the need to appoint a dedicated MDM referent. His or her role is manifold:

• Be the single point of contact for trades
• Provide Level 1 support for parameterization
• Maintain overall system consistency
• Steering future developments
• Ensuring compliance with governance rules

This is crucial not only for the launch, but also for the entire life of the tool.

Skills transfer

A fundamental aspect of long-term success is the organization of skills transfer. It is essential to :

• Plan this transfer right from the start of the project
• Identify key skills to be passed on
• Organize regular training sessions
• Document processes and technical choices
• Plan periods of work in pairs

The aim is to gradually gain autonomy over the tool, reducing dependence on external service providers.

Conclusion

Implementing an MDM is a complex project that goes far beyond the purely technical. Our experience shows that it is first and foremost a data governance project that requires :

• A strong commitment from the organization
• A rigorous methodology
• A long-term vision
• Dedicated resources

Success depends as much on the quality of the tool chosen as on the organization’s ability to make it its own and sustain it over time. It’s a significant investment, but one that, if well managed, can profoundly transform an organization’s data management.

End of the series of articles on our MDM project