Se ha denunciado esta presentación.
Utilizamos tu perfil de LinkedIn y tus datos de actividad para personalizar los anuncios y mostrarte publicidad más relevante. Puedes cambiar tus preferencias de publicidad en cualquier momento.

Master Data Management

25.175 visualizaciones

Publicado el

Quick review of what's MDM

Publicado en: Empresariales, Tecnología

Master Data Management

  1. 1. Master Data Management Compiled by Sung Kuan [email_address] Disclaimers
  2. 2. What is MDM? <ul><li>It is a systematic approach to clean up customer data so that business can managed efficiently and grow effectively. </li></ul><ul><li>It help business to move towards “single version of truth about the customers” </li></ul><ul><li>The strategy, architecture and technology deals with customer data constitute known as Customer Data Integration or CDI. </li></ul>
  3. 3. Why MDM? <ul><li>Regulatory compliance </li></ul><ul><li>Privacy and data protection </li></ul><ul><li>Safety and security </li></ul><ul><li>Meaningful data mining </li></ul><ul><li>You can’t control what you don’t know </li></ul><ul><li>You can’t measure what you don’t control </li></ul>
  4. 4. Courting Strategy <ul><li>Start small and demonstrate value </li></ul><ul><li>Look for business drivers that give the most benefits and ‘quick win’ </li></ul><ul><li>Explore the ideas and gather feedbacks </li></ul><ul><li>Identify the service, its level, its costs, its limitations, its potential, its stakeholders </li></ul><ul><li>Craft a story aka draft business proposal </li></ul><ul><li>Propose to do a pilot before full implementation. If pilot fails, the project is better to be terminated as the organization is not ready. </li></ul>
  5. 5. How to propose MDM? (high level) <ul><li>CEO and senior management commitment </li></ul><ul><li>Understand the business drivers </li></ul><ul><li>Understand the resource requirements </li></ul><ul><li>Understand the strategic risks </li></ul><ul><li>Provide estimate of the benefits e.g. reduce workload, more sales, reduce costs </li></ul><ul><li>Output: Board Approved Business Plan </li></ul>
  6. 6. How to propose MDM? (middle level) <ul><li>Provide training to project team so as to establish common lingo and working styles </li></ul><ul><li>Define goals and objectives of project </li></ul><ul><li>Set boundaries and rules of engagement </li></ul><ul><li>Plan and keep agreement sacred </li></ul><ul><li>Output: Business Approved Project Plan </li></ul>
  7. 7. How to propose MDM? (low level) <ul><li>Conduct risk assessment or ‘operationally what can go wrong’? </li></ul><ul><li>Reduce risk, if not apply compensatory control </li></ul><ul><li>Optimize work breakdown structure </li></ul><ul><li>Plan regular and consistent project reviews </li></ul><ul><li>Output: Team Agreed Implementation Plan </li></ul>
  8. 8. How to do MDM <ul><li>Architectural considerations </li></ul><ul><li>Data control considerations </li></ul><ul><li>Customer integration considerations </li></ul><ul><li>Measure the benefits / values / savings </li></ul>
  9. 9. Architectural Considerations <ul><li>Meta-data driven Service Oriented Architecture – Reference Architecture Viewpoint </li></ul><ul><li>ER diagram </li></ul><ul><li>Data Governance </li></ul>
  10. 10. Data Control Considerations <ul><li>Risk Taxonomy (transaction, reputation, strategic & compliance) </li></ul><ul><li>End to End Security </li></ul><ul><li>Access (XACML, User provisioning & entitlements) </li></ul><ul><li>Nonrepudiation </li></ul><ul><li>Visible Security Architecture </li></ul>
  11. 11. Customer Identification Considerations <ul><li>Use unique attributes to minimize matching errors along with discrimination attributes (e.g. match first_name, last_name, birthday, social security number to identify an individual) </li></ul><ul><li>Define matching rules </li></ul><ul><li>Understand Effect of Chaining </li></ul>
  12. 12. Measure & Evaluate <ul><li>The objective is to provide assurance that benefits are realized, if not what went wrong and what went right. </li></ul><ul><li>Review the financial figures presented in business case, project plan and determine if it exceeded expectations or not. </li></ul><ul><li>Identify soft benefits e.g. improve morale, less stress, increase compliments, reduce complaints, less sick leave etc </li></ul>
  13. 13. Summary
  14. 14. Disclaimers <ul><li>This slides is for my personal understanding only and will not be 100% accurate but please feel to use it for your work. </li></ul><ul><li>Your feedback is most welcome to improve on it. </li></ul>
  15. 15. Reference <ul><li>Berson, A. & Dubov, L. (2007). Master Data Management and Customer Data Integration for a Global Enterprise. United States of America: McGraw Hill </li></ul><ul><li>ITGI. (2007). IT Governance Implementation Guide 2 nd Edition. </li></ul>
  16. 16. Reference Architecture Viewpoint
  17. 17. Visible Security Architecture