17. RESTRICTED
Confidential
Master Data provides truth Reference Data provides context
Airlines Geographies Airports
Time zonesCurrencies Cost Centers
Segments Legal Entities Standards
Metadata provides meaning
Business glossary
Ownership
Entities Attributes
Data Dictionary
Integrations
DQ Rules
KPI Reports
Customers Travel Agencies Services
Products Organization Locations
Resources Employees Suppliers
How we describe
things
Metadata
How we classify
things
Reference
Data
How we manage
important things
Master
Data
Clarity & Trust
A trust framework for enterprise apps
Enterprise applications and analytics need to rely on accurate, trustworthy shared data assets.
19. RESTRICTED
Confidential
Page 19
Conclusion and advices…
1. High level (exec) sponsorship is mandatory for the success of any MDM Project
è Do not under estimate resistance to change
è Mitigate risks of disruption on existing products / processes
2. Manage expectations carefully
è Data Quality of often the root cause of wider problems
è MDM is often just an enabler for other projects that bring the real value to the Business stakeholders
3. Keep in mind the value is obtained by the usage of the Referential
è MDM Referential is useless if the data is not used/consumed by every one
è Integration of the MDM Referential with other systems (BI, CRM, Portals, SOA, BPM…) has a cost
(System integration, data migration,…) and dependencies with the target system.
è Plan MDM Integrations with consuming systems/solutions at the early stage of the MDM Project
4. As a starting point: bottom up initiatives (Proto, PoC), focusing on small use case, can
contribute on Data Quality and MDM awareness.
è Start with a business case that is visible and achievable in a reasonable timeframe and budget
è Help stakeholder understand how their DQ problems can be solved by MDM, get their buy in.
è Switch to a Top down approach when awareness is there.