MDM Registry Pros and Cons

Transcription

1 Global Data Competency Adam J. White President MDM Registry Pros and Cons August 24, 2009

2 Agenda Fundamental MDM Implementation Styles PROS and CONS of Registry Style Determining MDM Style to Implement Utilities to Support MDM Role of Mastering Data Role of SOA Architecture with MDM Role of MDM Governance MDM Pitfalls 1

3 Fundamental MDM Implementation Styles Four Main Implementation Styles Transactional / Source of Record Golden Record / Best Record Hybrid (Transactional / Best Record) Registry 2

4 Fundamental MDM Implementation Styles Transactional Transactional / / Source Source of of Record Record Attributes Attributes Banking Application Customer Portlet CDI Request Reply Push Insurance Application Front end implementation Customer information captured at time of entry Applications receive their customer info from CDI Customer information may or may not reside in applications Mature state 3

5 Fundamental MDM Implementation Styles Golden Golden Record Record / / Best Best Record Record Attributes Attributes Customer Banking Portlet Banking Application CDI Customer Insurance Portlet Insurance Application Back office implementation Customer information provided by the applications Can be used to support business operations Mainly used to support Marketing and Analytics Customer information resides in applications Golden Record from trusted sources 4

6 Fundamental MDM Implementation Styles Hybrid Hybrid (Transactional (Transactional and and Best Best Record) Record) Attributes Attributes Customer Banking Portlet CDI Banking Application Customer Insurance Portlet Insurance Application Mainly an implementation model Both a front end and back office implementation Begin with Transactional supporting one application Golden / Best Record utilized until other applications move to Transactional 5

7 Fundamental MDM Implementation Styles Registry Registry Attributes Attributes Customer Banking Portlet Banking Application CDI Pointers Only Customer Insurance Portlet Insurance Application Back office implementation Only pointers to customer information are stored Customer information, after identified, is used from the application where the information resides Limited or no customer information resides in the Registry 6

8 Pros of Registry Style Minimal data mastering Supports large enterprises with large customer bases Quick to implement Cheap to implement 7

9 Cons of Registry Style Little or no functionality Used when other implementation styles are not possible Used when other implementation styles are cost prohibitive 8

10 Determining Style to Implement Business Case Business Objectives Business Requirements Enterprise Wide Functional / Technical Requirements Enterprise Wide Identify vendor product that meets functional / technical requirements RFP Process 9

11 Utilities to Support MDM Matching Utilities Search Utilities Speed important Name and Address Standardization 10

12 Role of Mastering Data Data Dictionaries Only the data specific to the process Define Approach Which style to implement What application will be first Define Scope Start small Define CDI Data Model 11

13 Role of MDM Data Governance Enterprise Application Who is the owner Domain Control What content goes into the data base Only product keys Do not architect it to be application specific Or frog walk it into being application specific 12

14 Role of SOA Architecture with MDM Enterprise Application Front end implementation Customer portlets Middleware is critical 13

15 MDM Pitfalls Vendor Data Model Must configure to support your functionality Manage Delivery Expectations When to clean up data Educate, Educate, Educate! Communicate, Communicate, Communicate! If Front End implementation Not a BI or Data Warehouse exercise Vendor may not know your business May get the B team 14

16 QUESTIONS Questions Contact Info Adam J. White Global Data Competency Phone