Gartner: Master Data Management Functionality

7,453 views

Published on

Gartner will further examine key trends shaping the future MDM market during the Gartner MDM Summit 2011, 2-3 February in London. More information at www.europe.gartner.com/mdm

Published in: Technology
0 Comments
6 Likes
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
7,453
On SlideShare
0
From Embeds
0
Number of Embeds
20
Actions
Shares
0
Downloads
388
Comments
0
Likes
6
Embeds 0
No embeds

No notes for slide
  • Decision Framework: Whether you decide to build or buy an MDM solution, you must understand the capabilities required. If you buy a packaged MDM solution, then perform a needs requirement test; then evaluate MDM products on the basis of an objective set of criteria that are suitably tailored and weighted for the requirement. Organizations should perform a thorough requirements analysis and create an objective, weighted set of evaluation criteria before reviewing MDM products. This provides a firm foundation for gap analysis, as well as an objective rating of products. First, determine which problem you're trying to solve, which architectural style of MDM you require, and how the registry, coexistence and transaction hub styles map to your short- and long-term needs. Second, examine the key evaluation criteria, which include: • Data model — Should be able to manage any complex relationships and map to the master customer information requirements of the whole organization, not just selected areas. • Information quality — There should be well-integrated facilities for cleansing, matching, linking and identifying data from different sources. • Integration and synchronization — This will depend on middleware at a lower level, but the solution should support the bidirectional transfer of data between the central system and peripheral systems, if necessary. • Performance and scalability — Look for proof points of transaction and batch-processing capabilities. • Business services — More-mature implementations will want to use this criterion as the basis for SOA business applications. • Technology base — The product base should be mainstream application server and development environment technologies and standards. If you're thinking of building your own MDM solution, ensure that you understand the complexity of the challenge. Otherwise, you risk underestimating the scope, which will result in time and cost overruns. Action Item: Evaluate MDM products in line with a defined set of objective, customized criteria.
  • Gartner: Master Data Management Functionality

    1. 1. MDM Functionality: You'll Need a Tightly Integrated Set of Capabilities <ul><li>Data Model </li></ul><ul><li>Extensibility </li></ul><ul><li>Industry knowledge </li></ul><ul><li>Integration and Synchronization </li></ul><ul><li>Batch and real time </li></ul><ul><li>Propagation across systems </li></ul><ul><li>Technology and Architecture </li></ul><ul><li>Architectural flexibility </li></ul><ul><li>Satisfy different use cases </li></ul><ul><li>Business Services and Workflow </li></ul><ul><li>Granular and packaged services </li></ul><ul><li>Base for SOA applications </li></ul><ul><li>Performance, Scalability and Availability </li></ul><ul><li>Batch and transaction processing </li></ul><ul><li>Planned and unplanned downtime </li></ul><ul><li>Measurement and Analysis </li></ul><ul><li>Effectiveness of MDM outcome </li></ul><ul><li>ROI, TCO </li></ul>MDM <ul><li>Information Quality </li></ul><ul><li>Data stewardship facilities </li></ul><ul><li>Semantic analysis </li></ul><ul><li>Manageability and Security </li></ul><ul><li>Integration with system management </li></ul><ul><li>Manage access rights and privacy </li></ul>

    ×