Data modelling is always big concern before designing repository in SAP MDM solution design and in fact not only for SAP MDM wherever data involved in an organization and where client needs to manage their data. Some of them also feels it a part of best practice now. Data modeling techniques and methodologies are used to model data in a standard, consistent, predictable manner in order to manage it as a resource.
Here I would like bring a different point or process in between as when we are dealing with pre stage of data modelling, I would name it a WORKSHOP. This is a time when you will deal in business blue printing phase of MDM engagement to take a close look at the exact problem area wihich relates to master data.
This is the time when by involving in long discussion along with the data domain owner and process owner of particular master data objects we have to analyse the quality of their most valuable organizational assets.
This creates a foundation for design a repository from the scratch based on clients needs and also to customize the standared repository based on their needs again. This is quite obvious when it creates to the point data model we can have below benifts
- MDM repository performance can be measure and can be in control from start and some scope can also be defined for it for future enhancement.
- The overall solution design along with future enhanements could be clear in very initial phase of project.
So it may sound weird but the long discussions and keeping all business process owners of master data happy with getting their proper sign off for the data problems and data owns by them and start the modeling of data from there in order to design a repository and overall solution from there can be consider as a real success of WORKSHOP. more on it can also be seen in one of SAP MDM life cycle approach MDM lifecycle approach.
PS: all of these are my own views, It may or may not reflect as Standared way for MDM Solution.
