Value and Implications of Master Data Management (MDM) and Metadata Management

Prepared for: Dimitris A Geragas

GARTNER CONSULTING Project Number: 330022715

CONFIDENTIAL AND PROPRIETARY This presentation, including any supporting materials, is owned by Gartner, Inc. and/or its affiliates and is for the sole use of the intended Gartner audience or other intended recipients. This presentation may contain information that is confidential, proprietary or otherwise legally protected, and it may not be further copied, distributed or publicly displayed without the express written permission of Gartner, Inc. or its affiliates. © 2015 Gartner, Inc. and/or its affiliates. All rights reserved. Enterprise Information Management Background

Enterprise Information Management (EIM) is about

. Providing business value

. Managing information (EIM) to provide business value

. Setting up a business and IT program to manage information

EIM is an integrative discipline for structuring, describing and governing information assets across organizational and technological boundaries.

Enterprise Information Management (EIM) is about how information gets from a multitude of sources to a multitude of consumers in a relevant, timely and consumable way?

…includes large volumes, variety, or high velocity data? Big Data CEO

Master Data Marketing …can be consistent across business units and across time? Mgt (MDM) Business …can be used to monitor performance and make decisions? Intelligence (BI) Finance Sales Business …can be used to draw conclusions and make predictions? Analytics (BA) Customer Data Quality Service …is it clean enough and good enough to use? (DQ) Information Smart …no ambiguity on who is accountable for what? Machines Governance Metadata …can be enriched and reused? Management

Different Hymn Sheets One Hymn Sheet Operations Customer Service Operations Customer Service

OR? Ops Sales Mfg. Ops Sales Mfg. Process Process Process Process Process Process

Master Data: A consistent and uniform set of identifiers and attributes that describe the core entities of the enterprise, and are used across multiple business processes.

Widely shared among organizational/functional units Are worth Consistent across viewpoints managing

Foundational and valuable to the operation and the business Can be managed Stable over time

Master Data Management: Technology-enabled discipline in which business and the IT organization work together to ensure the uniformity, accuracy, stewardship, semantic consistency, and accountability of the enterprise's official, shared master data assets.

Vision

Strategy

Metrics

Information Governance

Organization and Roles

Information Life Cycle

Enabling Infrastructure

Master Analytic Other Social Content Data Data Data Data …? Master Data Management CONFIDENTIAL AND PROPRIETARY 330022715 | © 2015 Gartner, Inc. and/or its affiliates. All rights reserved. 10 MDM Vision and Strategy Critical Vector – Implementation Styles

Downstream reporting or Low control, autonomous Consolidation Registry analytics environments . Nonintrusive to the business . Nonintrusive to edge . BI is the business platform applications . Any industry . Emphasis is on remote data . BI strategy depended and application-to- . No attempt to clean up application integration source . Distributed governance . Faster to implement than coexistence and centralized

Large-scale distributed High-control, top-down Coexistence Centralized model environments . Largest change to . Largest change to information infrastructure application infrastructure . Greatest need to mirror data . Hugely invasive to the . Global and local governance business . Greatest risk over control, . Centralized governance security . Greatest control over access, . Focused on shared services security . Focus on common services

Information Governance establishes decision rights, and assigns authority for MDM

Information Governance

What Decisions Who Makes How Are Decisions Have to Be Made the Decisions Made

Establish Assign Encourage Policy Responsibility and Enforce

CONFIDENTIAL AND PROPRIETARY 330022715 | © 2015 Gartner, Inc. and/or its affiliates. All rights reserved. 12 MDM Organization and Roles Organization and Roles forms the group and organizational structures to implement MDM

Executive

Steering Stewardship Sponsor Committee Data StewardsData StewardsData Stewards Governance Group EIM Leader

Data StewardsBusinessData RepresentaStewards - tives Management Architecture Management and EIM Administration IA Manager Group

Implementation

Design Group Integration Group Storage Group Delivery Group

Information Life Cycle depicts the flow of information and activities where MDM is focused

Enabling Infrastructure provides the technology capabilities to implement the EIM

Analytics Transaction Content Hybrid

Specialized Capabilities

Information Semantic Styles Manage Metadata Common Capabilities

Describe Organize Integrate Share Govern Implement

Social Documents Transactional IT/OT Image Audio Text Video Mobile Search Data Engine

Semantic Identification Authority Store Transformation Data Quality

Syntactic Discovery Usage Access

Lineage Trust Contextual Origin Security Disposition

The answer to all strategic EIM-related dilemmas is “both.”

There are NO RIGHT OR WRONG answers in EIM, and the most powerful factor is the reallocation of authority and movement of money.

Ultimately, EIM requires a POLITICAL POWER SHIFT in the organization.

The answer to all Data Quality implementation EIM- related dilemmas is “it Historical Unstructured depends.”

There are NO RIGHT OR WRONG answers in EIM, Agility Data Consistency and the most powerful factor are the priority and needs of the client.

Structured Operational Ultimately, EIM requires a DELIBERATE and ARCHITECTED approach Speed in the organization.

Business Case Revenue and Cost Mission and Value

Scope Value Chain and Company State and City Level; Agency

Domain GL; Employee; Location; Customer GL; Employee; Citizen

Risk Tolerant Averse

Sharing Promoted Restricted or Temporary

Security Technical Enablement Physical Data Vaults

Authority Process and Technology Enforced Policy Driven

Topology Multiple Registry

. Clear Vision and Tight Scope – Determine what you really want to achieve and what you need to govern . Strong Leadership and Sponsorship – Identify and secure a business sponsor to promote the effort and ensure the business stakeholder participation . Consisted and Objective Semantics – Strive for the “single version of the facts” and not for the “single version of the truth” . Stratify Scope – Manage Semantics, Syntactic, and Instances differently at different levels of scope . Comprehensive Viewpoint – Design the strategy and target state to play the tradeoff among governance, organization, processes, and technical infrastructure . Clear Communications in Business Terms – Express what the stakeholder will get out of it in their terms . Tight Stakeholder Collaboration – Establish a common work environment and a cross-business/IT team with the business leading and IT enabling . Pragmatic Approach – Follow the money, do what you can and not what you want . Respect the Culture – Minimize impact

Improve business process agility 17% 11% 17%

Improve business process outcomes 14% 14% 11%

Create internal/operational efficiencies 6% 11% 20%

Improve customer relations/service 11% 11% 11%

Drive revenue growth 11% 11% 9%

Enhance decision making 9% 11% 9%

Cut costs/improve margins 9% 9% 6%

Improve compliance and risk management 11% 3% 6%

Reduce time to market 6% 11% 0%

Improve supplier or partner relations 3% 3%

Drive innovation 3% 3%

0% 5% 10% 15% 20% 25% 30% 35% 40% 45% 50% Ranked 1st Ranked 2nd Ranked 3rd

Undergoing a redesign of Defining business case & Current deployment is existing operations objectives fully operational (multi- 11% domain – one MDM 19% solution) 3% Single domain has been been implemented & now working on other Gathering policy, domain(s) regulation & compliance 6% requirements 6% Mid-stage implementation: partially complete 11% Vendor selection or RFP Early stage 20% implementation: just initiated 9% Finding internal resources to guide & champion Piloting or prototype project(s) 6% 9%

Technology Solutions Stewardship Responsibility

Custom built Don’t know Users in a (or plan to Users in IT 11% Not yet fully Shared Cloud- build) our 9% established based MDM own solution Built (or Service 9% technology 6% plan to reporting to 6% build) IT around a 3% purchased Subscription MDM Users in a or third- component Users in the Shared party (with or business Service solution without 29% reporting to 3% other tools the like DQ, DI) business 31% 11% Purchased or built Purchased around (or plan to several purchase) a Shared MDM complete between IT products MDM and and/or technology business solution solution 39% 17% 26%

Financial ledger or account 38% 3% 17% 41%

Employee 30% 13% 17% 40%

Location or site 28% 10% 41% 21%

Customer or citizen 21% 35% 38% 6%

Product or services 19% 23% 52% 7%

Hierarchy or grouping 15% 18% 33% 33%

Asset 14% 10% 17% 59%

Supplier 13% 20% 30% 37%

Purchased part 12% 12% 35% 42%

General 8% 29% 33% 29%

0% 10% 20% 30% 40% 50% 60% 70% 80% 90% 100% Already deployed Currently implementing Considering or plan to implement in 12-18 mo. No plans at this time