A lot of things are important in MDM: DQ capabilities, match & merge, workflows, user friendliness, integration and connectivity, the data model, .... The most important is to start with a very good understanding of your company's needs and processes before you start selecting a tool.
Search for a product comparison in Master Data Management (MDM) Software
Business Intelligence Consultant at a tech consulting company with 501-1,000 employees
User
2018-04-06T16:32:07Z
Apr 6, 2018
Know what you objectives that need to be accomplished prior to developing a plan to procure an MDM solution. What are your use cases? How much flexibility, scalability will be needed? How much time will it take to get up to speed on the product? How much integration with your existing data structures does it have built in? How much customization will need to be done? What is the method of building out that customization? What will be the cost of training power users to be able to reliably interact with the product? What is the budget for the project? How much buy in does the organization have for the need of an MDM solution? In many cases where the company is small and the data is smaller and experienced Data Architect will replace the need for an MDM Solution. There are a million questions, get answers to all of these prior to exploration?
Flexibility to implement your use cases quickly and easily. Being locked into a fixed schema, an inflexible data quality process or a limited UI means users won't embrace the solution and you will struggle to meet your MDM goals.
What is master data? Master data is the crucial, all-important data that all businesses rely on to function on a regular, day-to-day basis. It is the core data at the heart of the business process and describes the relationship of the environment and how it relates to the complete business process. Master data encompasses all the data used throughout the entire business process life cycle. It can include - but is not limited to - such relationship processes as: clients (both internal...
A lot of things are important in MDM: DQ capabilities, match & merge, workflows, user friendliness, integration and connectivity, the data model, .... The most important is to start with a very good understanding of your company's needs and processes before you start selecting a tool.
Know what you objectives that need to be accomplished prior to developing a plan to procure an MDM solution. What are your use cases? How much flexibility, scalability will be needed? How much time will it take to get up to speed on the product? How much integration with your existing data structures does it have built in? How much customization will need to be done? What is the method of building out that customization? What will be the cost of training power users to be able to reliably interact with the product? What is the budget for the project? How much buy in does the organization have for the need of an MDM solution? In many cases where the company is small and the data is smaller and experienced Data Architect will replace the need for an MDM Solution. There are a million questions, get answers to all of these prior to exploration?
Flexibility to implement your use cases quickly and easily. Being locked into a fixed schema, an inflexible data quality process or a limited UI means users won't embrace the solution and you will struggle to meet your MDM goals.