Rob Loranger Product Manager ERStudio 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 ID: 547944
Download Presentation The PPT/PDF document "Best Practices for Mapping your Master D..." is the property of its rightful owner. Permission is granted to download and print the materials on this web site for personal, non-commercial use only, and to display it on your personal computer provided you do not modify the materials and that you retain all copyright notices contained in the materials. By downloading content from our website, you accept the terms of this agreement.
Slide1
Best Practices for Mapping your Master Data Landscape
Rob Loranger – Product Manager | ER/StudioSlide2
Agenda
Who am IWhy map your master data landscapesComplex data landscape
Building blocks of a master data map
Comprehension through modeling
Reverse EngineeringNaming Standards Metadata extensions (attachments)Reconciling duplicates & variants (universal mappings)
2Slide3
A bit about me…
Current a product manager for ER/StudioSoftware Consultant for all Embarcadero database products for close to 9 years
BSEE and MBA
Husband and father
3Slide4
Why map your MDM landscape?
A good map can help answer important questions:What system contains the “golden records”?
How is master data used in data warehouses, marts, and other systems?
Where does common data exist for master data such as customers, products, employees, etc.?
What data is needed to create a complete view of master data?
4Slide5
Complex Data Environments
Evolution:
38
years of
construction
147
builders
No Blueprints
No
Planning
Result:
7 stories
65
doors to blank
walls
13
staircases abandoned24 skylights in floors160 rooms, 950 doors47 fireplaces, 17 chimneysMiles of hallwaysSecret passages in walls10,000 window panes (all bathrooms are fitted with windows)Slide6
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 …Slide7
What makes a useful map usefulSlide8Slide9
Building Blocks of a Master Data Landscape Map
Document all possible master data systemsOLTP, master data hubs, ERP,
eCommerce
, Data Warehouses
Data, process, and lineage models are helpfulCreate links between common master dataMetadataMaster Data classificationsData Stewardship
Business Glossaries
9Slide10
Links between master data
10Slide11
Classification through Metadata: Attachments
11Slide12
Data Source Mapping: additional contextSlide13
Increase Business Meaning: Glossary/Terms
13Slide14
Perspectives & Layers
Different users require a different types of information.
Who will be using the map?
Technical or business users
Master Data landscape maps require layersConceptual, logical, and physical
CentralizeSpread the word
14Slide15
Design Layers
15Slide16
Design Layers
16Slide17
Overcome the obstacles
Identify candidate databases with master data
Reverse engineer existing databases into models
Apply naming
standards (comprehension)Classify through metadataAnalyze redundancies & gapsData lineage / chain of custody
Consider an Enterprise Logical ModelMulti-level models (hierarchy)Make it central and accessible
17Slide18
Comprehension: Naming Standards
Extremely importantDefineApply
Enforce
Represent real world business objects
Typically comprised ofBusiness terms and other wordsAbbreviation for each
Template (specify order)CasePrefixes, Suffixes
18Slide19
Naming Standard Example
19Slide20
Data Lineage
20Slide21
Multi-level models
21Slide22
Share Across Business & IT
Central Store of Metadata
Modeling Teams
Business
Analysts
Executives
App and DB Developers
Data Stewards
DBAsSlide23
Map Master Data to R
elated Terms23Slide24
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 tablesOften don’t implement referential integrity in the database
24Slide25
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 map25Slide26
Conquering Landscape Complexity (a checklist)
Reverse engineering (extensive list of platforms)
Comprehensive metadata extensions (attachments)
Naming standards
Map between and across design layers
Business glossariesData lineage
Provide data context with
processes
Centralization
Single view across master data elements
Enterprise logical model
Map master data elements to business terminology
26Slide27
Thank you!
Learn more about the ER/Studio product family:
http://
www.embarcadero.com/data-modeling
Trial Downloads: http://www.embarcadero.com/downloadsTo arrange a demo, please contact Embarcadero Sales: sales@embarcadero.com
, (888) 233-2224Grab our cards
27