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

EMBARCADERO TECHNOLOGIESEMBARCADERO TECHNOLOGIES

Best Practices for Mapping your Master Data

Landscape

Rob Loranger – Product Manager | ER/Studio

EMBARCADERO TECHNOLOGIES

2

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)


3

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


4

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?


Complex Data EnvironmentsEvolution:• 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)


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 …


What makes a useful map useful



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


10

Links between master data


Classification through Metadata: Attachments

11

Site

Site ID

Elevation UOM Code (FK)

Province ID (FK)

Geographic Time Zone ID (FK)

Site Type ID (FK)

Site Code

Site Official Name

Site Common Name

Site Latitude

Site Longitude

Site Elevation

Site Effective Date

Site Expiry Date

Business Object: Site

Business Value: High

Master Data Class: Master

Equipment Component

Equipment Component ID

Equipment Status ID (FK)

Equipment Component Type ID (FK)

Volume UOM (FK)

Site ID (FK)

Manufacturer ID (FK)

Equipment Status Reason ID (FK)

Equipment Component Name

Equipment Component Functional Tag

Equipment Component Label

Equipment Reference Number

Roll Up Subcomponents Volume

Equipment Component Nominal Volume

Equipment Latitude

Equipment Longitude

Equipment Elevation

Equipment Component Model Number

Eqipment Component Part Number

Equipment Component Serial Number

Equipment Component Effective

Equipment Component Expiry

Equipment Component Note

Business Object: Equipment Component



Equipment Status

Equipment Status ID

Equipment Status Name

Business Object: Equipment Status


Master Data Class: Reference

Equipment Group Detail

Equipment Group Detail ID

Equipment Group Type ID (FK)

Equipment Component ID (FK)

Equipment Group Detail Effective

Equipment Group Detail Expiry

Business Object: Equipment Group Type

Business Value: Medium


Equipment Group Type

Equipment Group Type ID

Equipment Group Type Name

Equipment Group Type Note

Business Object: Equipment Group Type

Business Value: Medium


Equipment Component Type

Equipment Component Type ID

Equipment Category ID (FK)

Equipment Hierarchy Level ID (FK)

Equipment Component Type Name

Equipment Component Type Symbol

Equipment Component Type Allow Components

Equipment Component Type Note

Business Object: Equipment Component Type

Business Value: Low

Master Data Class: Reference

is location for

describes current state of

is a member of

has

defines type of


Data Source Mapping: additional context


13

Increase Business Meaning: Glossary/Terms


14

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. Centralize5. Spread the word


Design Layers

15


16

Design Layers


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

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


19

Naming Standard Example


20

Data Lineage


21

Multi-level models


Share Across Business & IT

Central Store of Metadata

Modeling Teams

• Business Analysts

• Executives

• App and DB Developers• Data Stewards

• DBAs


23

Map Master Data to Related Terms


24

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


25

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


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


Thank you!

• Learn more about the ER/Studio product family: http://www.embarcadero.com/data-modeling

• Trial Downloads: http://www.embarcadero.com/downloads

• To arrange a demo, please contact Embarcadero Sales: [email protected], (888) 233-2224

• Grab our cards

27

http://www.embarcadero.com/data-modeling

http://www.embarcadero.com/data-modeling

http://www.embarcadero.com/downloads

http://www.embarcadero.com/downloads

mailto:[email protected]

Documents

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