1. What You Need before You Deploy Master Data Management Presented by Malcolm Chisholm Ph.D. Telephone 732-539-3406 – Fax 407-264-6809 mchisholm@MasterDataMgmt.com www.refdataportal.com © AskGet.com Inc., 2007. All rights reserved Metadata Professional Organization

2. © AskGet.com Inc., 2007. All rights reserved Malcolm Chisholm Ph.D. is an independent consultant focusing on and Enterprise Information Management with a special emphasis on Master Data Management. He has over 25 years of experience in IT, and has worked in a variety of sectors, including finance, government, manufacturing, and insurance. Malcolm is the author of Managing Reference Data in Enterprise Databases and How to Build a Business Rules Engine and frequently writes and speaks on these topics. He is a columnist in DM Review and will have an expert channel in the B-eye Network. He runs two Web sites www.refdataportal.com and www.bizrulesengine.com. You can contact him at mchisholm@refdataportal.com Malcolm Chisholm

3. AGENDA © AskGet.com Inc., 2007. All rights reserved Understanding Master Data Discovering Master Data

4. Understanding Master Data © AskGet.com Inc., 2007. All rights reserved

5. Issue: It’s All Very Fuzzy MDM is Not as Mature as Other Areas (e.g. DW) MDM concepts are not mature Neither are many MDM tools Methodologies are not clear MD can be highly specific. Different enterprises have different needs. All this makes MDM / DQ issues difficult. Master Data Master Data Warehouse ProductCustomer Maturity ? © AskGet.com Inc., 2007. All rights reserved

6. Is Data just Data? What Can We See In A Data Model? © AskGet.com Inc., 2007. All rights reserved

7. Metadata Reference Data Transaction Structure Data Enterprise Structure Data Transaction Activity Data Transaction Audit Data Enterprise Information Architecture Increasing: Volume of Data Population Later in Time Shorter Life Span Increasing: Per Value Data Quality Importance Semantic Content Most Relevant To Design Most Relevant To Outside World Most Relevant To Business Most Relevant To Technology © AskGet.com Inc., 2007. All rights reserved

8. Layers of Data Metadata – Usually describes the structure of databases. Found in a database’s system catalog. Sometimes included in database tables. Reference Data – Codes and descriptions. Tables containing this data usually have just a few rows and columns. Transaction Structure Data – The parties to the transactions of the enterprise. E.g. Customer, Product. Enterprise Structure Data – Data that describes the structure of the enterprise. E.g. organizational or financial structure. Transaction Activity Data – Traditional focus of IT – in many enterprises the only focus. Transaction Audit Data – Data that tracks the life cycle of individual transactions. Includes server logs. © AskGet.com Inc., 2007. All rights reserved

9. What Is Reference Data? Definition of Reference Data: Reference Data is any kind of data that is used solely to categorize other data found in a database, or solely for relating data in a database to information beyond the boundaries of the enterprise. Also known as: Lookup Data, Domain Values. Some people regard any data imported into a database, or not updated by a system as reference data. © Askget.com Inc., 2006. All rights reserved

10. What Is Transaction Structure Data? Definition of Transaction Structure Data: Data that represents the direct participants in a transaction, and which must be present before a transaction fires. Definition of Transaction Activity Data: Data that represents the operations an enterprise carries out Some people do not think of data that represents all participants in a transaction as Master Data. They only recognize some, e.g. Product, Customer. © Askget.com Inc., 2006. All rights reserved

11. What Is Enterprise Structure Data? Definition of Enterprise Structure Data: Data that permits business activity to be reported or analyzed by business responsibility. Some people call it “hierarchies” or “dimensions”. © Askget.com Inc., 2007. All rights reserved

12. Metadata Reference Data Transaction Structure Data Enterprise Structure Data Transaction Activity Data Transaction Audit Data Master Data Master Data = Reference Data (Code Tables, Taxonomies) + Transaction Structure Data (Product, Customer) + Enterprise Structure Data (CoA, Org. Structure) © AskGet.com Inc., 2006. All rights reserved

13. Reference Data Transaction Structure Data Enterprise Structure Data Specific Data Management Tasks for Each Category of Master Data © AskGet.com Inc., 2006. All rights reserved Semantic meaning of codes Standards Discovery Manage Multiple Identities Historical Hierarchies Determine specific management tasks for each category of MD “One size fits all” approaches to MDM will not work Categorize your data in a data discovery process prior to MDM

14. Discovering Master Data: The Problem of the Data Landscape © AskGet.com Inc., 2007. All rights reserved

15. The Data Landscape You need to know what data is out there You need to know where to find it Then you can categorize it and do MDM © AskGet.com Inc., 2007. All rights reserved

16. Data Landscape May Be Big Assume 25 databases Assume 100 tables per database Assume 20 columns per table 25 x 100 x 20 = 50,000 columns What if 10% of these columns are Master Data? …Maybe your enterprise is bigger… © AskGet.com Inc., 2007. All rights reserved

17. Data Landscape Typically Not Well Known Do knowledge management artifacts exist? Are there processes to keep them in synch? © AskGet.com Inc., 2007. All rights reserved Suite of Logical Data Models Maybe Enterprise Data Model? Physical Databases Documentation Metadata Repository Data Dictionary

18. You will never have enough analysts to map the data landscape They could be doing more productive things It becomes project-based (remember Y2K) As soon as they did some, it would change Detailed tasks for MDM – especially looking at content © AskGet.com Inc., 2007. All rights reserved Effort too Big for Forward Analysis 50,000 columns? Infer Semantics? Categorize based on content? Catalog Master Data?

19. Automated mapping of data landscape is becoming possible Have a good probability of identifying Master Data This is a new activity for Enterprise Information Management (formerly Data Administration) © AskGet.com Inc., 2007. All rights reserved Only Hope is Tools Repository Tool Metadata-aware Examine Content Infer Categorize Physical Databases Map Data Landscape Metadata Reference Data Transaction Structure Data Enterprise Structure Data Transaction Activity Data Transaction Audit Data

20. But We Need a Methodology MDM is a complex multi-dimensional problem If it was easy it would have been done long ago A tool for mapping the data landscape and discovering Master Data must be integrated into an overall methodology EIM must develop the methodology before deploying the tool © AskGet.com Inc., 2007. All rights reserved Mapping Identify Master Data Categorize Master Data Goals Data Mart Dimensions Workflow for Quality … … Metadata Management Identify Metadata to Gather Build Repository … MDM Governance Who owns what Issue Resolution … …and a great deal more…

21. What You Need before You Deploy Master Data Management © AskGet.com Inc., 2007. All rights reserved Questions and Answers Presented by Malcolm Chisholm Ph.D. Telephone 732-539-3406 – Fax 407-264-6809 mchisholm@MasterDataMgmt.com www.refdataportal.com Metadata Professional Organization September 11, 2007