Product Type: Market Research Report
Published by: Bloor Research
Published: May 2006
Product Code: R3467-8Description Master data is an age old problem that started the minute there were multiple packaged applications that were each designed to hold their own versions of data in order to function. To tackle this problem, initially the thought was to eliminate the issue altogether by implementing a single ERP system. When it proved unrealistic
to move to one enterprise application implementation, the data mart teams stepped in to pull the disparate data together to provide consistent departmental views of information for reporting. Then, when business processes were required to cross application silos, separate application integration teams looked to reconcile data for transactional flow. The result was multiple transactional systems, multiple reporting environments and multiple application integration technologies—all with their own version of the information truth. With this complexity and high investment in place, IT is now being challenged by the business to provide:
- Enterprise-wide access to information for decision-making.
- Enterprise-wide business processes that have the agility to cross application and corporate boundaries.
- Enterprise regulatory compliance.
The experience of the past has proved that the elimination of complexity is not achievable. Therefore the focus has moved to how best to leverage the existing environment and reconcile data across existing silos so that the business can run against a common definition—and so this is the age of master data management.Table of Contents - Introduction
- MDM market definition
- Business purpose
- Breadth of data
- Architectural approach
- Key components of Master Data Management
- Data access
- Key identification
- Record management
- Hierarchy management
- Registry/Repository/Hub
- Data governance
- Operations and security
- Interoperability services
- Enabling technologies required for MDM
- Data integration
- Process workflow
- Data quality
- Data delivery
- MDM within broader Information Management
- The Bullseye scoring method
- The Landscape Bullseye
- Domain dashboards
- Summary of Results
- Criteria for inclusion
- Vendors—Registries
- Vendors—Repositories
- Vendors—Hubs
- Conclusion
- Appendix A—The Bullseye scoring criteria
- Scores and details
- Scores against primary criteria
- The Landscape Bullseye
- Domain dashboards
- Solution views
- Interpreting the results
- Appendix B—Vendor summary table
- MDM activity and characteristics
- Scores and comments
- Appendix C—Vendor details
- Appendix D—Further information
- Appendix E—About the author
- Bloor Research Overview
- Copyright & Disclaimer
|
|
