MDM Strategy & Roadmap

17
A Strategic Business Imperative Cypress Management Group Corporation Victor Brown Managing Partner/Enterprise Architect 06/09/22 1 Managing Master Data © 2009 CMGC

Transcript of MDM Strategy & Roadmap

Page 1: MDM Strategy & Roadmap

A Strategic Business Imperative

Cypress Management Group CorporationVictor Brown

Managing Partner/Enterprise Architect

04/12/23 1Managing Master Data © 2009 CMGC

Page 2: MDM Strategy & Roadmap

What if you could … Find all of the data relevant to a Customer in one placeBe confident that the data is accurate and up to dateBe confident that the data is completeRetrieve all of the significant relationships that a

Customer has with other business entities—Marketing, Support, Finance

Send automated alerts when key Customer data changesSee/access data and relationships at any “point in time”Rely on the availability of the data (managed, high-

availability platform)And …

04/12/23 2Managing Master Data © 2009 CMGC

Page 3: MDM Strategy & Roadmap

And, what if you could … Create a view like this with a single call to a federated data service

04/12/23 3Managing Master Data © 2009 CMGC

Page 4: MDM Strategy & Roadmap

ChallengesNo trusted “Single Version of the Truth”Multiple Systems of Entry (SOE) Inconsistent data—value may vary depending on the sourcePoor quality—data may be incorrect, stale or missingData stovepipes—separate versions of data maintained in

“local” applicationsFull, accurate representation of global relationships

between entitiesNo comprehensive 360 view of key business entities

Customers Branch Offices

04/12/23 4Managing Master Data © 2009 CMGC

Page 5: MDM Strategy & Roadmap

Goals• Consistent, Accurate and Timely Enterprise Master Data

• Maximize benefits of accurate master data across the Enterprise

• Improve operational integrity and agility

• Define a roadmap to the optimal/target state

• Protect current investments

• Information as a Service (IaaS) implemented via data services

• Define process for eliciting global adoption of MDM and data services

04/12/23 5Managing Master Data © 2009 CMGC

Page 6: MDM Strategy & Roadmap

Prerequisites• Identify Preliminary Master Data Domains

• High-level business entities• Candidates for initial implementation (roadmap)

• Understand how data will be used• Use Cases• Styles of use

• Collaboration• Operations• Analytics• All of the above

• Create/implement metadata strategy

• Identify source systems• Within a data domain, is there an authoritative source? Multiple sources?• Identify consumers• Rationalize semantics

• Select appropriate MDM pattern(s)• Map pattern to business model/requirements• Employ multiple patterns when appropriate

04/12/23 6Managing Master Data © 2009 CMGC

Page 7: MDM Strategy & Roadmap

MDM Services

Inte

rfac

e S

ervi

ces

(DV

L)

Data Quality Management

Event Management

Lifecycle Management H

iera

rchy

and

R

elat

ions

hip

Man

agem

ent

Sec

urity

& P

rivac

y

Sea

rch

Logg

ing

Master Data

History Data

MetaData

Identifies events that happen in the MDM system and triggers a response

Hierarchies consist of master data entities that can logically be structured into parent–child relationships.

Relationship Services manage groupings between master data entities within the same domain and relationships across master data domains.

Security Services authorize access for users and groups to request Lifecycle Management and Search Services.

Search Services are requested by Lifecycle Management Inquiry Services and MDM Data Quality Management Services, or by an application or user interface.

Lifecycle Management Services provide business and information services to create, access, and manage master data

held within the Master Data Repository.

Data Quality Services manage data quality, standardize data, determine duplicate master data entities, and maintain cross-reference information.

ID Management

ID Management ensures consistent identification of entities in a data domain, e.g., Customer.

Database that contains CI’s master data content. This database may be external from the MDM tool’s internal data repository.

Data Virtualization (data services) provides data to consumers via a Web service interface or a virtual database interface.

Contains a record of every change to the Master data. Updated by the Logging service.

MD

M

Rep

osi

tory

Logging Services record transaction history, event history, and the changes that have been made to master data at that point in time.

Illustrates functions required for a robust MDM solution.04/12/23 7Managing Master Data © 2009 CMGC

Page 8: MDM Strategy & Roadmap

Target State Options & Considerations• Optional Patterns *

• Registry Pattern• Transactional Hub (aka, Persistent)• Coexistence (aka, Hybrid)

• Domains• Customer• Employees• Reference Data (including hierarchies)• Products• Others

• Different data domains may employ different patterns

Overarching Principle:

MDM patterns and usage will be driven by, and evolve with our business model and strategy

* Note: Terminology differs in the industry, e.g., Gartner talks about 3 hub patterns: Persistent, Registry and Hybrid.

04/12/23 8Managing Master Data © 2009 CMGC

Page 9: MDM Strategy & Roadmap

Registry Pattern• Characteristics

• Reference system• Read-only reference data for downstream consumers• Minimum data redundancy• Source systems provide data-of-record• Cleans/matches source systems’ identifying

information

• Benefits• Federates multiple sources of data• Source data is always current (but not necessarily

consistent)• Relatively quick and easy to implement

• Cons• Does not ensure quality (except for ID data)• Depends on source systems to ensure quality• Authoritative only for ID data• Cannot guarantee SLA—source systems availability

and performance dictate MDM SLA

04/12/23 9Managing Master Data © 2009 CMGC

Page 10: MDM Strategy & Roadmap

CoexistenceHybrid Pattern• Characteristics

• Reference/Master system• Source systems feed MDM—cleansed, transformed,

and integrated• Stores master data (some may not be golden record)• Can synchronize updates with source systems and

downstream systems• Duplicates are identified

• Benefits• Supports data stewards’ efforts to resolve quality

issues• Provides full MDM capabilities with minimal changes

to source systems

• Cons• Data not guaranteed to be current with source systems• Doesn’t provide maximum "agility”—some source

systems are the authority

04/12/23 10Managing Master Data © 2009 CMGC

Page 11: MDM Strategy & Roadmap

Transactional Pattern• Characteristics

• Centralized single version of the truth (golden record)• Operational component of the IT infrastructure• Supports Operations, Collaboration, and Analytical• Updates directly to MDM via services• Serves as a component of the EDW (dimensions)• Can provide augmented data, not present in sources

• Benefits• Single authoritative data• Enforces data quality and consistency• Data is current (updates are direct)• Governance and security—e. g., access, audits, attribute-level

• Cons• Cost and challenges to implement because source systems must be

modified to update MDM (possible mitigations include incremental implementation, mixed styles, hybrids)

• Operational SLAs–—availability, performance, etc.

04/12/23 11Managing Master Data © 2009 CMGC

Page 12: MDM Strategy & Roadmap

Conclusion & Best PracticeEach MDM pattern has strengths and weaknesses and

must be coordinated with the enterprise data strategyOptimal leverage of MDM typically involves a combination

of patterns Selection of the best pattern for each scenario requires

business involvement and sponsorship Implement in an iterative processClearly define the business case for each iteration

04/12/23 Managing Master Data © 2009 CMGC 12

Page 13: MDM Strategy & Roadmap

Our Roadmap (General Approach)• Target State 1

• Registry Pattern• Investment to establish platform (H/W, S/W)• Extend to provide data federation (Beneficiary)

• Target State 2—Hybrid/Transactional Hub• Evolve from Registry to Coexistence Pattern• Begin converting selected data domains to Transactional• End state is a hybrid (multi-form) pattern that uses all three patterns

• Evolutionary adoption Controls risk Provides the opportunity to learn through experience and adjust as

necessary Provides early ROI

04/12/23 13Managing Master Data © 2009 CMGC

Page 14: MDM Strategy & Roadmap

Supplementary MaterialThis document presents definitions, benefits and implementation options for planning a Master Data Management (MDM) solution. MDM, however, is most effective when it is implemented as a component of a broader enterprise data services architecture.MDM works in concert with other architectural mechanisms Enterprise Data Warehouse, data services and ODS to provide a robust IaaS “cloud.”

04/12/23 Managing Master Data © 2009 CMGC 14

Page 15: MDM Strategy & Roadmap

MDM and Enterprise Data WarehouseMDM repository may extend and supplement the Enterprise Data Warehouse by providing dimensions

04/12/23 Managing Master Data © 2009 CMGC 15

Page 16: MDM Strategy & Roadmap

MDM as a Critical Component of IaaS & Data Services

04/12/23 Managing Master Data © 2009 CMGC 16

Page 17: MDM Strategy & Roadmap

Contact

Cypress Management Group Corporation

www.cmgc.netDenver, Colorado

San Francisco, [email protected]

OrContact Victor Brown directly at

303.928.9198415.516.1369

[email protected]

04/12/23 Managing Master Data © 2009 CMGC 17