A guide to the concepts, patterns, and blueprints of Master Data Management
MDM is a cornerstone for SOA enabling IT architects and solution designers
Foreword is written by Aaron Zornes, the Chief Research Officer of The MDM Institute
Illustrates how SOA and MDM are linked and can be applied to the enterprise
Provides an end to end scope and use case scenario of the topic SOA and MDM
Table of Contents
Foreword: Ambuj Goyal
Foreword: Aaron Zornes
About the Authors
Chapter 1: Introducing Master Data Management
1.1 Introduction to Master Data Management
1.2 Why an MDM System?
1.3 What Is a Master Data Management System?
1.4 Business Benefits of Managed Master Data
Chapter 2: MDM as an SOA Enabler
2.2 Brief Introduction to SOA
2.3 Information as a Service
2.4 MDM as a Service
Chapter 3: MDM Reference Architecture
3.1 Definitions and Terms
3.2 Conceptual Architecture Overview
3.3 MDM Conceptual Architecture
3.4 Architecture Principles
3.5 MDM Logical Architecture
3.6 MDM Component Model
3.7 Component Relationship Diagram
3.8 Master Data Management Component Interaction Diagrams
Chapter 4: MDM Security and Privacy
4.2 Information Risk Management for Master Data
4.3 Security Considerations in MDM
4.4 Logical SOA Security Architecture
4.5 Applying the Security Reference Model to MDM
Chapter 5: MDM Architecture Patterns
5.1 Introduction to Patterns
5.3 MDM Architecture Patterns Overview
5.4 MDM Hub Patterns
5.5 Information-Focused Application Integration Patterns
5.6 Process-Focused Application Integration Patterns
5.7 Enterprise System Deployment Patterns
5.8 Pattern Selection and Pattern Composition
Chapter 6: PIM-MDM Solution Blueprints
6.1 Introduction to Master Data Management Solutions Blueprints
6.2 Terms and Definitions
6.3 New Product Introduction (NPI) Solution Blueprint for Consumer Electronics Industry
6.4 Global Data Synchronization Solution Blueprint for Retail
6.5 PIM-RFID Solution Blueprint for Track & Trace
Chapter 7: CDI-MDM Solution Blueprints
7.2 Master Patient Index Solution Blueprint for Healthcare
7.3 Cross- and Up-Sell Solution Blueprint for Banking & Insurance
7.4 Fraud and Theft Solution Blueprint for Banking and Insurance
7.5 Self-Service Website Solution Blueprint for Telco
Chapter 8: MDM Integration Blueprints
8.1 Introduction to MDM Integration Blueprints
8.2 Leveraging Data Warehouse (DW) Systems for MDM Integration Blueprint
8.3 SAP Application Integration Blueprint
Chapter 9: Master Data Management and Data Governance
9.2 MDM Project Lifecycle and Data Governance
9.3 Data Stewardship
9.4 Data Quality
Appendix A: MDM User Roles
A.1 User Roles for Solution Evaluation
A.2 User Roles for Solution Development
A.3 User Roles for Solution Administration and Operation
A.4 The Solution User
A.5 Relations between User Roles
Appendix B: Software and Solution Offerings for MDM Deployments
B.1 Analytic Services
B.2 Enterprise Application Integration using ESB
B.3 External Data Providers
B.4 Information Integration Services
B.5 Master Data Management Services
B.7 Track and Trace Solutions
B.8 Links to Relevant Homepages
Appendix C: Master Data Management and Regulations
Appendix D: Standards and Specifications
Appendix E: Glossary & Terms
What Is This Book About?
Master Data Management (MDM) refers to the disciplines, technologies, and solutions that are used to create and maintain consistent and accurate master data for all stakeholders across and beyond the enterprise. Enterprise Master Data Management: An SOA Approach to Managing Core Information explains key concepts of MDM, the business value of MDM, and how to architect an Enterprise Master Data Management Solution. The book is a comprehensive guide to architecting a Master Data Management Solution that includes a reference architecture, solution blueprints, architectural principles, and patterns and properties of MDM Systems. The book also describes the relationship between MDM and Service-Oriented Architectures, and the importance of data governance for managing master data.
Chapter 1: 'Introducing Master Data Management' describes the fundamental concepts of master data and MDM. We describe the key characteristics of a Master Data Management System and how the MDM System's ability to manage master data provides benefits to the enterprise. We also introduce the reader to multiple MDM methods and implementation styles.
Chapter 2: 'MDM as an SOA Enabler' describes the relationship between MDM and Service-Oriented Architectures. We demonstrate how MDM and SOA work together to help in the achievement of business and IT goals related to managing master data, and explain why we view MDM as an enabler for any SOA-style solution. The chapter includes topics such as SOA concepts, SOA principles, service granularity, service composability, and information services.
Chapter 3: 'MDM Reference Architecture' describes the functional characteristics of the Master Data Management Reference Architecture. We describe how to position and design a Master Data Management Solution within an enterprise. We describe the type of functionality required to deliver a Master Data Management Solution, identify the major architectural building blocks, and then demonstrate how those architectural building blocks collaborate in the delivery of MDM functionality.
Chapter 4: 'MDM Security and Privacy' describes the role of security and privacy in an MDM architecture and deployment. We provide insight into developing an understanding of the value of and the risks to master data and then offer guidance for the tasks of selecting and applying the appropriate security controls. We then describe in depth the types of security services that provide the appropriate controls and how those services can apply to the implementation of an MDM Solution.
Chapter 5: 'MDM Architecture Patterns' provides an overview of architecture patterns often encountered in MDM deployments. We describe in detail the architecture patterns that helped to shape the MDM Reference Architecture. The architecture patterns encountered were either new architecture patterns, variations of existing architecture patterns, or known architecture patterns that were applied in the area of Master Data Management.
Chapter 6: 'PIM-MDM Solution Blueprints' introduces the concept of MDM Solution Blueprints; in this chapter, we explain the relationships between architecture patterns and business patterns for PIM-MDM solutions. The Solution Blueprints are based on the MDM Reference Architecture. Based on specific business requirements for product information management, we describe a variety of PIM-MDM Solution Blueprints for several industries and solution scenarios.
Chapter 7: 'CDI-MDM Solution Blueprints' explains the relationships between architecture patterns and business patterns for CDI-MDM solutions. The Solution Blueprints are based on the MDM Reference Architecture. Based on specific business requirements for customer data integration, we describe a variety of CDI-MDM Solution Blueprints for several industries and solution scenarios.
Chapter 8: 'MDM Integration Blueprints' provides further guidance on how to integrate an MDM System into an existing IT landscape. We provide guidance and describe sample integration scenarios, such as integrating the MDM System with a Data Warehouse and integrating an MDM System with an SAP application for the authoring of data.
Chapter 9: 'MDM and Data Governance' explores the critical nature of data governance in Master Data Management, and how people, process, and technology work together to leverage master data as an enterprise asset. We explore the critical nature of data governance in Master Data Management and the direct and indirect roles that the architecture for the MDM Solution can play in enabling data governance.
Who Should Read This Book
Enterprise Master Data Management: An SOA Approach to Managing Core Information has content that should appeal to a diverse business and technical audience, ranging from the executive level to experienced MDM practitioners and especially those new to the topic of Master Data Management. Newcomers to the topic of MDM, and even SOA, will certainly benefit from the chapters that introduce MDM, that explain security and privacy, and that show how MDM complements the development of a SOA.
Readers with a strong technical background, such as Enterprise Architects, System Architects, and Information Architects, should enjoy reading the detailed content that provides technical guidance for implementing Master Data Management. Technical guidance covers a broad range of topics--implementation styles, methods of use, SOA, security and privacy, architecture patterns, and data governance--which are then all brought together into the Master Data Management Reference Architecture and a set of solution blueprints that span CDI-MDM, PIM-MDM, and MDM Integration Blueprints.
Executives trying to gain an understanding of Master Data Management, and even those who are already in the process of deciding how to proceed, will benefit from the content that introduces Master Data Management, data governance, and the solution blueprints.
What You Will Learn
This book is a comprehensive guide to understanding (1) the importance of Master Data Management, (2) the need for an MDM System, and (3) methods of architecting a Master Data Management Solution. We cover a wide range of topics in our discussions of the use of disciplines, technologies, and solutions to implement Master Data Management. Readers of this book have the opportunity to increase their knowledge about a broad range of topics related to MDM--from both a business and a technical perspective. Readers will learn the answers to the following questions about Master Data Management, which constitute its core concepts:
What is Master Data Management, and why is there a need for managed master data?
How can an MDM System provide a consistent understanding and trust of master data entities?
What is the relationship between SOA and MDM, and how can MDM enable the implementation of a SOA solution?
How can a security architecture to maintain the security and privacy of master data be implemented?
What are the core architectural principles, properties, and patterns for MDM Systems?
What data governance is critical for the management of master data?
In addition to learning MDM's core concepts, the reader will understand how they are incorporated into the design for a Master Data Management Solution. The MDM Reference Architecture provides the reader with a reference architecture that describes the functional characteristics of an MDM Solution implementation within an enterprise. MDM Integration Blueprints, PIM-MDM and CDI-MDM, and Solution Blueprints then provide the reader with knowledge of how to use the reference architecture and architecture patterns to implement a specific solution to solve a specific set of business problems.
How to Read This Book
There are several ways to read this book. The most obvious way to do it is to read it cover to cover to get a complete end-to-end picture of Enterprise Master Data Management. However, the authors organized the content in such a way that there are four basic reading paths through the book.
To understand the key concepts of Enterprise Master Data Management, we suggest reading Chapter 1, Introducing Master Data Management; Chapter 3, MDM Reference Architecture; and Chapter 9, MDM and Data Governance. This path should provide the reader with a clear understanding of Master Data Management, data governance, and how to implement MDM within the enterprise.
To understand the key concepts for designing Enterprise Master Data Management Architectures, we suggest that the reader start with Chapter 1 in order to gain an understanding of the need for an MDM System, methods of such a system's use, and implementation styles. Chapter 2 describes the relationship between MDM and SOA, and how SOA principles can be applied to the design of the solution. Chapter 3 explains the MDM Reference Architecture--the foundation for any MDM deployment--from an architectural perspective. Chapter 4 details aspects of the MDM Reference Architecture that are related to MDM Security and Privacy.
For the reader who is interested in detailed knowledge about solution blueprints, Chapter 8, MDM Integration Blueprints would be of interest to those readers who desire further integration details. Based on the objectives of the reader, Chapter 9, MDM and Data Governance, should be considered for each of the suggested reading paths. The suggested reading paths are as follows:
PIM-MDM Solution Blueprints: If the reader is investigating solutions for the Product master data domain, they are described in Chapter 6. Reading that chapter has prerequisites, though. The reader should be familiar with Chapters 1, 2, and 3. Because the solution architectures are based on the MDM Component Model, a sound understanding of the MDM Reference Architecture is necessary. Explaining certain aspects of a solution also requires an understanding of MDM Security and Privacy, which are described in Chapters 4 and 5. Chapter 5 also explains key areas of the solution architecture.
CDI-MDM Solution Blueprints: Solutions focused on customer master data are described in Chapter 7, which has the same prerequisites as the PIM-MDM Solution Blueprints--namely, Chapters 1, 2, 3, 4, and 5.
What Is Not Covered
This book covers many of the key business and technical aspects of Master Data Management and is a comprehensive guide to architecting a Master Data Management Solution, but it does not provide project planning management methodology or an MDM Solution Architecture based on software products. IT Architects will make design decisions and select software products capable of meeting the functional and nonfunctional requirements for a specific solution by considering the existing hardware and software infrastructure for the specific IT environment. Based on our experience, we have provided the reader with a comprehensive guide to designing an MDM Solution. We have also explained the criteria that the reader should use when selecting software for the MDM System. In Appendix B, Software and Solution Offerings for MDM Deployments, we offer a listing of Solution offerings and software products grouped according to the MDM Logical System Architecture. We also provide the reader with the links to relevant Web pages for the providers of those solution offerings.
There are organizational and IT aspects that should be considered as part of the implementation and deployment of an MDM Solution. The people who are developing a project plan and implementation strategy need to consider the priority of the business problems being addressed, technology gaps, and the current information management capabilities of the organization. We provide guidance throughout the book on how to address some of these aspects, but we have not dedicated any additional chapters to this set of topics. However, the reader will find in Appendix A, MDM User Roles, a summary of the types of user roles, responsibilities, and associated skill descriptions for the various types of roles that we have seen on MDM projects. The primary focus of our efforts has been on providing the reader with the information required for an understanding of the need for Master Data Management and with a comprehensive guide to designing an MDM Solution.
Throughout this book, we mention a number of regulations that can influence how to configure, manage, and protect a Master Data Management environment. To help understand those relevant regulations and their scope, we have collected information about each regulation and provided a summary in Appendix C, Master Data Management and Regulations. We include a table that includes other information about each regulation, such as industries affected, master data domain, and Web site addresses where more information about the regulation is available. The book's text has frequent footnote references that direct the reader to Appendix C for further information.
We also refer to a number of industry and technical standards throughout the book and have chosen to include a description of those standards in Appendix D, Standards and Specifications. We do not use footnotes to direct the reader to Appendix D when a standard is mentioned, but we do encourage readers to refer to that appendix if they are unfamiliar with a particular standard. Appendix D contains a table that identifies the standard, provides a link to a Web site for further information, and presents brief notes about the standard.
Many of the chapters have references to additional sources of information that can provide further information about the subject being discussed. External references for each chapter are identified at the end of each chapter and referenced as footnotes. Each reference follows a format that includes the appropriate information relative to the reference, such as the author's name, title of the book or article, date of publication, publisher, ISBN, and Web site.
About the Authors
Allen Dreibelbis has 30 years of experience in the IT Industry. He spent 16 years providing system integration and consulting services to public-sector clients while working for IBM. His expertise spans enterprise architecture, software development, complex systems integration, and Master Data Management. Allen currently is an Executive Architect in the IBM Software Group World-Wide Information Platform and Solutions Acceleration Team. He developed the Master Data Management Reference Architecture in 2006 while collaborating with colleagues across the IBM SWG Information Platform and Solutions organization and the IBM Information on Demand Center of Excellence. He provides customer briefings and training on the Master Data Management Reference Architecture and conducts architecture workshops for customers on implementing Master Data Management Solutions within their enterprises. Allen holds a B.S. in Computer Science from Pennsylvania State University.
Eberhard Hechler is a Senior Certified IT Architect (SCITA) and Executive IT Architect. He joined the IBM B÷blingen Lab in Germany in 1983 as a junior programmer. Eberhard worked more than two years on an international assignment with the IBM Kingston Lab in New York, and he has worked on projects in software development, performance optimization and benchmarking, solution architecture and design, software product planning, management, technical consultancy, and technical alliance management. In 1992, Eberhard began to work with DB2« for MVS, focusing on testing and performance measurements of new DB2 versions. Since 1999, his focus has been on Information Management and DB2 UDB on distributed platforms. He is currently the Technical Enablement Architect for IBM Information Platform & Solutions, working with System Integrators throughout Europe. Eberhard holds a M.S. in Mathematics (Diplom- Mathematiker) from Hamburg University.
Ivan Milman is a Senior Technical Staff Member at IBM, focusing on security and governance in the Information Management area within the IBM Software Group in Austin, Texas. Over the course of his career, Ivan has worked on a variety of distributed systems and security technology, including OS/2« Networking, DCE, IBM Global Sign-On, and Tivoli« Access Manager. Ivan has also represented IBM to standards bodies, including The Open Group and IETF. Prior to his current position, Ivan was the lead architect for the IBM Tivoli Access Manager family of security products. Ivan is a member of the IBM Security Architecture Board and the IBM Data Governance Council. Ivan is a Certified Information Systems Security Professional and a Master Inventor at IBM, and has been granted 12 U.S. patents.
Martin Oberhofer joined IBM in the IBM Silicon Valley Labs in the United States as a developer for database technology. After returning to Germany, he joined the IBM B÷blingen Lab, from which he still works as a Technical Consultant and member of the World-Wide IBM Software Group Master Data Management Center of Excellence. His areas of expertise include database technologies, Java software development, MDM architecture, and IT systems integration. His special focus area is integrating MDM systems into the operational IT landscape by synchronizing and distributing master data with SAP application systems. He provides architecture workshops to customers and system integrators. He holds a M.S. in Mathematics from the University of Constance, Germany.
Paul van Run has almost 10 years experience in MDM and 15 years in IT. At DWL, he was part of the R&D leadership team developing DWL Customer, one of the first dedicated CDI products on the market. After the acquisition of DWL by IBM in 2005, he became a Senior Technical Staff Member, and he is responsible for the architecture of the IBM Master Data Management products: MDM Server (formerly WebSphere« Customer Center) and WebSphere Product Center, both market leaders in their segments. Before coming to DWL, Paul worked as a software developer in the insurance industry for an ING Group subsidiary in Canada. Paul holds a M.S. in Information Science from the Technical University of Eindhoven, the Netherlands, and a M.S. in Computer Science from the University of Waterloo, Canada.
Dan Wolfson is an IBM Distinguished Engineer and the chief architect and CTO for the Information Platform and Solutions segment of the IBM Information Management Division of the IBM Software Group. He is responsible for architecture and technical leadership across the rapidly growing areas of Information Integration, Master Data Management, and Industry Models. Dan's previous roles include CTO for Business Integration Software and chief architect for Information Integration Solutions.
Dan has more than 20 years of experience in research and commercial distributed computing, including transaction and object-oriented systems, software fault tolerance, messaging, information integration, business integration, metadata management, and database systems.