More than 70% of Master Data Management fails to reach full ROI due to inadequate implementation. I tried to highlight some of key areas to watch for during MDM implementation.

1. What makes Master
Data Management
Projects Complex?
By
Deenbandhu Prasad

2. • Dual Role Aggregator and Consolidator
• Hub-and-Spoke Architecture
• Multi Domains
• Multi Interfaces
• Batch
• Near-Real Time
• Real Time
• Streams
MDM
CHARACTERISTICS

3. HOW TO ASSESS THE
COMPLEXITY OF
MDM PROGRAM?

4. • Up-Stream source system
feeding data into MDM
• Data Model &Data Quality
different between systems
• Number of sources increases
the complexity of matching
and survivorship process
• Different CDC processes by
source via their
communicating interface
SOURCE SYSTEMS
MDM
HUB

5. • Business subject area which is
going to be mastered.
• Example: Customers, Products,
Accounts , Locations
• Talend MDM Suite Supports
Multi-Domain
• Number of Domains increases
the complexity and implementation
effort
• Each domain needs to mastered
separately and then linked together.
DOMAINS
Domains
Party
Customers
Patients
Partners
Suppliers
Products Locations
Sites
Franchises
RDM Others
Accounts

6. • Master Data record is sum of the its
attributes and Sub objects.
• Example of Attributes :
Date of Birth of Person
Established Date of Organization
• Example of Sub Objects :
Contact Methods (Phone[work, home] , Email)
Addresses (Work , Home)
• It is important to understand the
cardinality of attributes and Sub objects
w.r.t to Master Record
• Match and Survivorship logic directly
derived by these attributes and Sub
Objects
DOMAIN’S SUB OBJECTS
Party
Individual
Names
Address
Contact
Methods
Privacy
Preferences
Business
Name
Address
Contacts
Sites

7. • Initial Load - Strategy to match
and perform survivorship on the
Full Volume of Sources system
• Incremental Load - Strategy to
match and perform survivorship
on the daily flows
• Strategy to On-board new
Systems via Initial Load and
integrate as part of Incremental
Load
• Directly impact performance
and SLAs
VOLUME

8. • Capability of publishing
Master Data to Down Stream
Application
• Down Stream Application can
expect data via different
interfaces (Batch, Queues etc.)
• Data Masking of Federated
Master Data
• Handle Cyclical Update
between MDM and Sources
System which is both Up-Stream
& Down-Stream Application
DATA FEDERATION
MDM
HUB

9. MDM COMPLEXITY MATRIX
Complexity Low Medium High
# of Domains < 3 < 5 > 6
# of Sub-
Entities < 6 < 8 > 10
Volume < 100k < 3M > 4M
Data Sources < 3 < 4 > 5
Data
Federation
Interface
1 < 3 > 3

10. FACTORS CONTRIBUTING TO COMPLEXITY
• Sources Systems
• Domains
• Sub Entities
• Volume
• Data Federation
• Implementation Style
• Registry
• Co-Existence
• Consolidation
• Centralized