1. 22-10-2008
This Presentation Courtesy of the
International SOA Symposium
October 7-8, 2008 Amsterdam Arena
www.soasymposium.com
info@soasymposium.com
Founding Sponsors
Platinum Sponsors
Gold Sponsors Silver Sponsors
Master Data Management
Establishing a Strong SOA Foundation
Chris Madrid
cmadrid@microsoft.com
1
2. 22-10-2008
Objectives & Takeaways
Objectives Takeaways
• Understand what • There are many
Master Data different
Management means in approaches.
the industry.
• This isn’t easy.
Agenda
What problem does this solve?
How are these problems
addressed?
What are the implementation
options?
What are the key differences?
Start Making Investments
Questions & Answers
2
3. 22-10-2008
What problem does this solve?
Distribution of Data
Identification of Data
Consistency of Data
Quality of Data
Availability of Data
N-tier Paradigm
Application Application
Owner Owner
UI UI
Logic Logic
Data Data
3
4. 22-10-2008
Distributed Data
Friction Points
BUSINESS
R&D
Business
Focus on
siloed by
document
IT
exchange
Business model
Technology
model
IIS
ERP
Solutions
impose
Inward
constraints
technology
PLM
driven view CRM
TECHNOLOGY Applications
4
5. 22-10-2008
How are these problems addressed?
BUSINESS
Business
Requirements & Solutions Aligned
Focus Architecture
on Processes
service
Business model
Service model IT Architecture
Soft boundaries and Strategy
Technology model
Focus
on
Outward Services contract
business- Solution
driven view
Architecture
TECHNOLOGY and Delivery
Enterprise Architecture
Composite Applications
Portals Smart Clients
Service Oriented Architecture
Services BPM EAI
Master Data Management
CDI EDW ODS
5
6. 22-10-2008
Establish Master Data
Trustworthiness, Trustworthiness,
Trustworthiness
MDM is a set of capabilities
• Data Aggregation
• Data Mapping
• Data Normalization
• Data Standardization
Data Aggregation
Includes the common attributes found in
each data store.
Includes the unique attributes found in
each data store.
Establishes a one stop shop for retrieving
data.
6
7. 22-10-2008
Data Mapping
Identification of data elements
representing the same entity attribute
• Surname
• LastName
• LName
• FamilyName
Data Normalization
Improves the consistency of data.
• Phone Numbers
• Social Security Numbers
• Postal Code
7
8. 22-10-2008
Data Standardization
Data consistency is not enough.
• Date formats could very well be consistent
across systems, but could represent different
time zones.
Resulting Context
8
9. 22-10-2008
What are the implementation
options?
Topologies
Merge Models
Topologies
Centralized Distributed
9
10. 22-10-2008
Merge Models
Single Updateable Node
• Central Master Data
• Local Master Data
Multiple Updateable Nodes
Single Updateable Node – Central
Master Data
10
13. 22-10-2008
Differentiating Data Concepts
MDM is relational model.
EDW is dimensional model.
Having an ODS does not mean you have
adopted MDM.
An EDW may use data from the MDM solution.
Start Making Investments
Key to realizing potential of SOA.
Many benefits of MDM can be realized
without vendor products.
Identify systems of record.
Move to single updates if possible.
13