Welcome To CDMP Study Group!
☺
WE WILL BEGIN MOMENTARILY
CDMP Study Group
Chapter 10
Reference & Master Data
July 14, 2021
CDMP Study Group
Chapter 10
Reference & Master Data
July 14, 2021
Agenda
• Facilitator
• Introductory Note
• Chapter 10 – Reference & Master Data
• Introduction
• Guiding Principles
• Comparison of the Two
• Concepts of Reference and Master Data
• Key Processing Steps
• Data Sharing Architecture
• Reference and Master Data Activities
• Implementation Guidelines
• Important Metrics
• Q&A
• Next Session
New England Data Management Community
Facilitator
Mary Lynn Early
▪ I work for Accenture as a Data Management
Consultant
▪ Primarily in life sciences and healthcare
CONTACT INFO:
EMAIL: marylynnearly007@[Link]
PHONE: 617-943-4371
: /IN//marylynnearly
New England Data Management Community
Introductory Note
➢This study group is offered as a service of DAMA New England for DAMA New England
members. It not an official, DAMA International authorized training course because DAMA-I has
not yet created an authorized trainer program.
➢The purpose of this group is to help prepare members to take the CDMP. We will do so by
reviewing the content of chapters of the DMBOK2.
➢The chapter makes no claims for the effectiveness of the sessions or the ability of participants to
pass the CDMP exam after having attended. In fact, you should plan on doing a lot of individual
study to pass the exam.
New England Data Management Community
Chapter 10: Reference & Master Data
Reference and Master Data Management includes
ongoing reconciliation and maintenance of core
critical shared data to enable consistent use across
systems of the most accurate, timely, and relevant
version of truth about essential business entities.
New England Data Management Community
Reference and Master Data Introduction
Reference Data Both are critical context of transaction data
Management Master Data Management
Entails control over master
Provides control over domain
values & identifiers that enable
values & definitions
consistent use across systems
• Codes & descriptions Single version of:
• Classifications • Various domains, such
• Mappings as:
• Hierarchies • Customers, Accounts
Enterprise HWY • Materials
“List of Values (LoV)”
• Products
“Taxonomy” “Golden Record”
“Cross Reference” “Version of Truth”
“Master Values”
New England Data Management Community
Goals and Guiding Principles
Goals:
• Complete, consistent, current and authoritative across the organization
• Enables sharing across enterprise functions and applications
• Lowering cost and reducing complexity of data usage and integration through standards, common data
models and integration patterns
Guiding Principles:
• Shared Data –Managed so they are shareable across the organization
• Ownership – Belongs to the organization; require a high-level of stewardship.
• Quality – Both require ongoing quality monitoring and governance.
• Stewardship – Business Data Stewards are accountable for controlling and ensuring the quality of data
• Controlled Change – Require defined processes for managing
• Master data is the best understanding of what is accurate and current; matching rules should be applied
with caution and oversight and changes should be reversable.
• Reference data should follow a process and changes should be communicated before they are
implemented.
• Authority – Master data should only be replicated from the system of record. A system of reference may be
required to enable sharing across an organization.
New England Data Management Community
Differences Between Master and Reference Data
This type of data could be a subset of the other. B
A. Master Data
This type of data provides context for transaction data. C
This type of data is usually has fewer rows and columns. B
B. Reference Data
This type of data is usually reduces risk with ambiguous A
identifiers.
C. Both This type of data is requires a trusted version of truth for A
each instance of conceptual entities.
This type of data is shared and should be managed at the C
Enterprise level.
This type of data often resides outside of the organization. B
New England Data Management Community
Exploring Reference Data Concepts
Lists Proprietary/Internal Ref. Lists Industry Ref Data
• Simple cross Reference: US = United • Common words or terms for a value • Industry or Gov’t bodies that establish
States that may be shared across systems codes
• Expanded list with definitions • Ex: Account Status • Ex: International Classifications of Diseases –
• Languages may affect list structure • “List of Values” LOV Diagnosis and Procedure codes (ICD10
Taxonomies Ontologies
• Enable content classification and multi-faceted navigation to
• Characterize data; relate to information
support BI
beyond boundaries of the organization
• Maintain hierarchical classifications using super and sub relations
• Ex: Content Management; Topic Map
• Ex: Industry reference codes, such as NAICs – North America
(concepts in a domain and relationship that
Industry Classifications
holds them together)
Code Description Parent Code
44000 Retail Trade 44000 Geographic or Geo-Statistical Computational
• Ex: Census Bureau Reports describe • Foreign exchange calculations rely on
44500 Food & 44000 …
populations demographics, etc. that managed time-stamps
Beverage
is used for marketing purposes • Typically third-party provided
• MSA
Metadata about • To ensure lineage and currency are understood and maintained, track the details about a reference
Reference Data data set, such as: Name, Data Provider, Provider Source, Version Number, Version date, etc.
New England Data Management Community
Exploring Master Data Concepts
Data about business entities --- A real-world object (person, organization, place or thing)
Legal or Financial
Common Types Party Product Location
Structure
Or Domains that
Are “Mastered”: • Individuals and • Products / Services • Contracts • Ability to track and
organizations • PLM – Product • Centralized and share location info,
• Roles: Customers, Lifecycle Mgmt. combined – such as:
patients, vendors, • PDM – Product support • Addresses
employees, Data Mgmt. negotiations / • Plants, facilities
suppliers, etc. MSAs
• ERP - Ent Resource
• Challenges: roles, Planning • Location Reference
qty sources, • Typically in ERP: Data can support
• MES – Manuf.
customer • Chart of Accounts this – geopolitical
Execution Sys
engagement data: Countries,
• CRM – Prod data in • Cost Centers
Customer Rel states, counties,
• Profit Centers
Mgmt. etc.
System of Record – authoritative system where data is created/captured and maintained
System of Reference – where reliable records are retained to support transactions and analysis; e.g. MDM, Data Sharing
Hubs, Data Warehouses
New England Data Management Community
Exploring Master Data, continued
An MDM System should be managed to provide:
• A “Trusted Source” - the best version of the truth
• A Single View or 360⁰ View
• Encompasses data from multiple source systems
• Rules are developed for the matching and merging processes and
the formulation of the final “record”
The “Golden Record”
Master Data Management (MDM) defined by Gartner:
“…a technology-enabled discipline…business and IT together…to ensure uniformity, accuracy,
stewardship, semantic consistency, and accountability of the enterprise’s shared Master Data
assets…”
New England Data Management Community
MDM Key Processing Steps
•Validation – i.e.
cleansing Entity Resolution &
Data Acquisition •Work processes that
•Standardization – Identifier Management support the resolution
•Terms and definitions conforms to defined of match fall-out or
•Align these across the standards •Process of matching* weak/bad matches
•Planning, evaluating
Enterprise and incorporating •Enrichment – adding •Over time lessons
•Deterministic vs.
•Should be a “business” sources attributes to inform Probabilistic learned can improve
versus “technical” view entity resolution, i.e. rules in the MDM
•Receive, assess D&B DUNS numbers •False Negative and False
(profile), evaluate, Positives technology
pilot, DQ, Data Validation, •Identity resolution –
Data Model
Stewardship, integrate Standardization and rules-based formation of
Management Data Sharing &
Enrichment the final record
Stewardship
•Essential to maintain
history to “Undo” if
needed
•ID Management – Global
and x-Ref Info
Note – *Different match rules require different workflows
- Duplicate identification – DS manual merging
- Match-link rules – identify and cross-reference matches without updating the content of the cross-referenced record
- Match-merge rules – match and merge into a single unified record; if rules apply across systems, update
New England Data Management Community
Data Sharing Architecture – Three Approaches
Approach Description Pro Con
Registry Index points to Master Data in the various Easier to implement; fewer Complex queries to assemble MD
systems of record. changes to systems of record from multiple systems; more
business rules needed
Master Data is managed in systems of record.
Transaction Hub Applications interface with the hub to access Enable better governance and Costly to remove functionality to
and update Master Data. provide a consistent source of update Master Data from existing
Master Data. systems of record.
Master data exist only in the Transaction Hub
and is the System of Record for Master Data.
Consolidated A hybrid of Registry and Transaction Hub. Eliminates the need to access Entails replication of data; will be
Systems of record manage master data local to directly from the systems of latency between the hub and
their applications. record. systems of record.
Master Data is consolidated and made available Provides an Enterprise view with
form a data-sharing hub – the system of limited impact on systems of
reference for Master Data. record.
New England Data Management Community
Data Sharing Architecture
Example of hub-and-spoke architecture
DW or DM • MD hub handles interactions with spoke items
such as source systems, data stores, etc.
• Minimizing the number of integration points
• A local hub can extend and scale the MD hub
MDM Tools and Techniques
• Requires data integration, data remediation, Op
Data Stores, data sharing hubs or specialized
MDM applications
• Vendors offer subject area solutions or custom
services/solutions
• Packaged solutions to jumpstart a program
Source/Adapted: How to identify the correct Master Data subject areas & tooling for your MDM initiative, Christopher Bradley
[Link]
New England Data Management Community
Reference Data (RD) and Master Data (MD) Activities
RD & MD – For both, business and technical drivers are
usually to create efficiencies, save costs
Define Drivers and requirements
RD – Identify internal and/or external sources
MD – Assess structure and quality of source data Evaluate / Assess Sources
RD – Consider volatility, freq. of updates & consumption model
MD – Consider data consumption & sharing models: align with
business strategy Define Architectural Approach
RD – Model codes, descriptions and other info needed, such as
metadata to track change history
MD – Model the subject area; introduce canonical model
Model the Data Sets
RD – Ensure ref data remains current; facilitate maintenance
across business units
MD – Stewards to resolve close /questionable matches; resolve
Define Stewardship and Maintenance
match issues
RD – Roadmap and requirements for adoption
MD – Deploy unidirectional loops to maintain consistency
Establish Policies
New England Data Management Community
Organization and Culture Change
• Both are forms of data integration – implementation principles for data integration and interoperability apply
(Chapter 8)
• Centralized data – reference and master data – often requires people to relinquish control
• One accurate view provides benefits
• KEY – proper and strong Data Governance
• Adhere to Master Data Architecture
• Monitor data movement
• Manage Reference Data change
• Establish Data Sharing Agreements
Anticipate required organization change and utilize Data
Governance and Data Stewardship.
New England Data Management Community
Reference and Master Data Metrics
• Data quality and compliance
• Data change activity
• Data ingestion and consumption
• Service Level Agreement (SLAs)
• Data Steward coverage
• Total Cost of Ownership (TCO)
• Data sharing volume and usage
Tips:
• Vendor tools may provide canned reports and dashboards
• Consider the metrics when you define your processes
• Don’t forget about the operational metrics IT can provide
New England Data Management Community
Q&A
New England Data Management Community
STUDY GROUP MATERIALS
Study group presentations will be posted on CDMP Study Group page, on DAMA New England website, in the Schedule &
Agenda section.
New England Data Management Community
NEXT SESSION
New England Data Management Community
HOMEWORK
Next up: Chapter 12 – Metadata Management
New England Data Management Community