1. EMBARCADERO TECHNOLOGIES Best Practices for Mapping your Master Data Landscape Rob Loranger – Product Manager | ER/Studio

2. EMBARCADERO TECHNOLOGIES Agenda Who am I Why map your master data landscapes Complex data landscape Building blocks of a master data map Comprehension through modeling – Reverse Engineering – Naming Standards – Metadata extensions (attachments) – Reconciling duplicates & variants (universal mappings) 2

3. EMBARCADERO TECHNOLOGIES A bit about me… Current a product manager for ER/Studio Software Consultant for all Embarcadero database products for close to 9 years BSEE and MBA Husband and father 3

4. EMBARCADERO TECHNOLOGIES Why map your MDM landscape? A good map can help answer important questions: 1.What system contains the “golden records”? 2.How is master data used in data warehouses, marts, and other systems? 3.Where does common data exist for master data such as customers, products, employees, etc.? 4.What data is needed to create a complete view of master data? 4

5. EMBARCADERO TECHNOLOGIES Complex Data Environments Evolution: 38 years of construction 147 builders No Blueprints No Planning Result: 7 stories 65 doors to blank walls 13 staircases abandoned 24 skylights in floors 160 rooms, 950 doors 47 fireplaces, 17 chimneys Miles of hallways Secret passages in walls 10,000 window panes (all bathrooms are fitted with windows)

6. EMBARCADERO TECHNOLOGIES Complex Data Landscape 6 Comprised of: – Proliferation of disparate systems – Mismatched departmental solutions – Many Database platforms – Big Data platforms – ERP, SAAS – Master Data Hubs – Obsolete legacy systems Compounded by: – Poor decommissioning strategy – Point-to-point interfaces – Data warehouse, data marts, ETL …

7. EMBARCADERO TECHNOLOGIES What makes a useful map useful

8. EMBARCADERO TECHNOLOGIES

9. Building Blocks of a Master Data Landscape Map Document all possible master data systems – OLTP, master data hubs, ERP, eCommerce, Data Warehouses – Data, process, and lineage models are helpful Create links between common master data Metadata – Master Data classifications – Data Stewardship Business Glossaries 9

10. EMBARCADERO TECHNOLOGIES Links between master data 10

11. EMBARCADERO TECHNOLOGIES Classification through Metadata: Attachments 11

12. EMBARCADERO TECHNOLOGIES Data Source Mapping: additional context

13. EMBARCADERO TECHNOLOGIES Increase Business Meaning: Glossary/Terms 13

14. EMBARCADERO TECHNOLOGIES Perspectives & Layers 1.Different users require a different types of information. 2.Who will be using the map? – Technical or business users 3.Master Data landscape maps require layers – Conceptual, logical, and physical 4.Centralize 5.Spread the word 14

15. EMBARCADERO TECHNOLOGIES Design Layers 15

16. EMBARCADERO TECHNOLOGIES Design Layers 16

17. EMBARCADERO TECHNOLOGIES Overcome the obstacles Identify candidate databases with master data Reverse engineer existing databases into models Apply naming standards (comprehension) Classify through metadata Analyze redundancies & gaps Data lineage / chain of custody Consider an Enterprise Logical Model Multi-level models (hierarchy) Make it central and accessible 17

18. EMBARCADERO TECHNOLOGIES Comprehension: Naming Standards Extremely important – Define – Apply – Enforce Represent real world business objects Typically comprised of – Business terms and other words – Abbreviation for each – Template (specify order) – Case – Prefixes, Suffixes 18

19. EMBARCADERO TECHNOLOGIES Naming Standard Example 19

20. EMBARCADERO TECHNOLOGIES Data Lineage 20

21. EMBARCADERO TECHNOLOGIES Multi-level models 21

22. EMBARCADERO TECHNOLOGIES Share Across Business & IT Central Store of Metadata Modeling Teams Business Analysts Executives App and DB Developers Data Stewards DBAs

23. EMBARCADERO TECHNOLOGIES Map Master Data to Related Terms 23

24. EMBARCADERO TECHNOLOGIES What about ERP and SAAS? Often uncover surprises when digging through data landscapes. Where’s the master data? – Cryptic table and column names – Internal data dictionaries – Thousands of tables – Often don’t implement referential integrity in the database 24

25. EMBARCADERO TECHNOLOGIES What about Big Data? Fact or fiction? Used in specific applications Organizations are beginning to realize that constraints must be applied. Still need to follow standards Need to be incorporated in data landscape map 25

26. EMBARCADERO TECHNOLOGIES Conquering Landscape Complexity (a checklist) Reverse engineering (extensive list of platforms) Comprehensive metadata extensions (attachments) Naming standards Map between and across design layers Business glossaries Data lineage Provide data context with processes Centralization Single view across master data elements Enterprise logical model Map master data elements to business terminology 26

27. EMBARCADERO TECHNOLOGIES Thank you! Learn more about the ER/Studio product family: http://www.embarcadero.com/data-modeling http://www.embarcadero.com/data-modeling Trial Downloads: http://www.embarcadero.com/downloads http://www.embarcadero.com/downloads To arrange a demo, please contact Embarcadero Sales: sales@embarcadero.com, (888) 233-2224 sales@embarcadero.com Grab our cards 27