MDM - In Transit

mdmintransit

As organizations undergo large scale multi-million dollar IT transformations and undertakes multi-year multi-phase implementation approach, it is very critical to answer below key master data management questions to develop a holistic master data conceptual design roadmap in support of overall solution architecture that transit through multi-year project phases.

1) How should the new master data life cycle process looks like?

a) Which IT systems should be part of master data creation process?

b) Which IT systems should be consumers of master data to support downstream business processes?

c) Which IT systems should retire in which phase of the project?

d) How to address the business process gaps that were supported by retired system(s)?

2) Which system(s) should continue to generate the master data unique identifier?

3) How MDM design should help to create a consistent process for master data creation, consolidation and enrichment?

a) How MDM design should transit in unison with other IT systems involved in supporting master data life cycle process through each project phase?

b) How MDM should be leveraged to enrich master data attributes to substantiate a complete master data record rather than polluting downstream package systems through heavy customization?

4) Are there opportunities to lay foundation for governance process for master data and fine-tune it over the period?

a)How do we design a streamlined workflow-based governance process to ensure on-going master data integrity across systems?

b) Can we centralize rules management? Can we leverage rules established in custom/package/third party systems?

5) What should drive the archive process of master data?

a) How should we improve master data life cycle process and transactional processes in order to prevent data growth in IT systems?

b) Can we create an integrated data archive solution that will be primarily driven through transactional systems in support of data retention policies?

6) How the master data solution design could be extended to reference data management?

a) How to centralize reference data management into single IT system and distribute across system landscape there by achieving single version of truth?

b) How to create governance based solution design for locally managed reference data?