Implementing Multi-entity MDM

Joe Young – Lexmark Sr. Manager EIMRajesh Shewale – WIPRO Program Manager

Agenda

• Overview of Lexmark’s MDM Program• Data Domains• 4 Step Approach• Multiple Styles• Example of process• Governance Model• High Level Architecture• Results

Lexmark Products and Coverage

C935 Series

X945e X644e

C532n/C532dn

Color and Mono Laser

Laser Multifunction

X500n/X502n

C530dn

C780 Series

C500n

X560n

C782 Series

X854e

Wireless Inkjet AIOs

X9575X6575X6570X4875

Industry Coverage

Lexmark Master Data Management

• Master Data Management and Data Governance Program with strong business and IT participation• Multiple Domains• Quality Data to Transactional Systems and Business Intelligence• Enable successful ERP Migration and CRM upgrades• Comprehensive use of Enterprise data management tools including SAP MDM, BO Metadata Manager, BO Data Insight, BO Data Services, SAP Enterprise Portal

Material

Supplier Person

Customer

Product

Our Approach

Baseline and

Profile1st Quality

Assessment

CRUD

Processes

Cleanse and

Manage

Baseline

and Profile

4 Step Process

PeopleBusiness Leads

Data Architects

System Integrator

Business Leads

Data Stewards

Data Architects

System Integrator

Business Leads

Process Owners

Data Architects

System Integrator

Business Leads

Data Stewards

Data Architects

Support team

Technology

Data InsightData Insight

Data Services

SAP MDM

SAP Enterprise Portal

SAP MDM / EP

Data Services

Metadata Manager

Scope of MDM Domains

Material

Vendor Person

Customer

Product

•Two MDM repositories•Legal Entity•MDM Account

•150+ attributes•Consolidation/Harmonization/ Centralization•End User Customer, Partners –Phase 1•Consumers – Phase 2

•Centrally managed in HR Source System•Primary focus on process improvement to fix Data Quality issues

•Supplier MDM Repository•125+ Attributes•Consolidation and Centralization

•Product MDM Repository•30+ attributes•Data Governance Organization•Consolidation and Centralization

•Material MDM Repository•35+ attributes•Consolidation and Centralization

Multiple Entities…Multiple Styles

•Analysis of business processes for each domain–Customer

•Centralized for - New ERP, SFA•Harmonized for - Call Center•Consolidated for - Non-strategic systems

–Product•Centralized for all systems

–Material•Harmonized for all systems

–Vendor•Centralized for all systems (with ERP roll out)

– Person•Stays wholly within PeopleSoft

Example of Customer Process

Automated

Data Steward/ Business Owner Intervention

B

C

D

A Handles error code 1040,1041,1051,1052,1054,1055,1056

B

Handles error codes 1020,1030,1040,1060,2000,2010,

2020,2030,2040,2050,3000,3010,3020,3030,3040,3050,3060,3070,

3080,3090,3100,3110,4000,4010,5000,5010,5020,6000

C Handles error code 6010and 9999

Records for D&B Processing

D&B Processing

Data Preparation for SAP MDM

Data Movement into SAP MDM

End

Source System Data Extraction

Customer Data Consolidation

Data Validation

Customer Name and Address Standardization & Cleansing

Handling non D&B stamped records

Populate Legal EntityPopulate Sold-To

BillTo – SoldToLinkData Owner Review and Override

Begin

Exception Processing

Exception Processing

Step1

Step2

Step3

Step4

Step5

Party-Role & Party Type Association

Records for D&B Processing

D&B Processing

Data Preparation for SAP MDM

Data Movement into SAP MDM

End

Source System Data Extraction

Customer Data Consolidation

Data Validation

Customer Name and Address Standardization & Cleansing

Handling non D&B stamped records

Populate Legal EntityPopulate Sold-To

BillTo – SoldToLinkData Owner Review and Override

Begin

Exception

Processing

Exception Processing

Step1

Step2

Step3

Step4

Step5

Party-Role & Party Type Association

A

B

C

Data Governance Structure

People Process

StewardshipData Architecture

StandardsGuidelines

DirectionAuthority

Resources Commitment

Executive Leadership

Data Governance

Data ManagementData AnalysisData Capture

Process ControlsBusiness Rules

Error Resolution Quality Review

Data Governance Office

Data Governance Office

DomainData Management

Team

DomainData Management

Team

Data Governance Council

Data Governance Council

EIM Architecture

10

Consolidation Harmonization Centralization

EnterprisePortal

Guided Procedures Adobe

Bus

ines

s O

bjec

ts

Dat

a Se

rvic

es

Inte

grat

ion

Ariba

CRM

Sales Out

……

ECC

CRM

BI

EDW

MDM

ProductMaterialsVendor

Customer

Data Manager

Impo

rt M

anag

er

Synd

icat

or

APIsAnd

Web Services

Content Providers:DnB

Data EnrichmentController

Web App Server

JDE

10

BOMM

The good and the…

• NA • EMEA

• EMEA

• Bite what you can chew

• Global design• 5 weeks

• 80% global Design• 5 weeks

• Working withIT as well as business

• Offshore Centric• 10 weeks

• Offshore Centric• 14 weeks

• Global delivery model

• Have businessResources dedicated to testing• 4 weeks

• Extended UAT• 6 weeks

• Basic trainingprior to UAT

• Expected lower exceptions• 3 weeks

• DQ not as good as Expected• In Process

• Shared DQ reality earlier

• Started with 6 systems• 4 weeks

• Focus on EMEAas per ERProll-out

• Settled on4 systems• 8 weeks

Scope Systems Design Develop Testing Deploy

Planned

Actual

Went Well

•Cross program impacts

•Need to iterate, but have to limit

•Touching common components

• True end to end testing is tough

• Cannot over communicate

•Many moving parts in the infrastructure

Challenges

Our results so far• People

– Established Data Governance Org• 7 Data Stewards (new, full time)• 20+ Business Process owners

• Architecture– New infrastructure

• 5 new applications - 20+ new servers

• Data Processed– Data extracted from 9 core systems

• 300K+ customer records• 75k+ material records• 5K+ product records• 8K+ supplier records

– We have delivered both Master and Non-Master data to our ERP program

• Over 100k Master records • Over 1.5M Non-Master records

Lexmark Master Data Journey

DestinationDestinationMDMMDM

Organization

Technology

Process

Compliance

Starting Point Starting Point --AsAs--Is ChallengesIs Challenges

Lack of linkage between process and technologyNo defined KPIs around data

TransitionTransition Interim DestinationInterim DestinationPhase 1 Phase 1

Lack of socialized policies in place

Multiple legacy systemsNew ERP coming on line

New Data Governance organization still learningMultiple entry and control points for similar MD

New Data Governance organization defining policies and proceduresRefinements to roles and responsibilities

Define Enterprise Data Model / ArchitectureDefine integration framework with ERP/legacy apps

Developing MD stewardship processEducating the business on MD stewardship

Organizational awareness of MD process through engagement

Policy enforcement of data standards and procedures in placeStructured GovernanceTeam in place, managing MD process and policies

Centralized MDM Solution Single source of Truth

Common data repositoryFoundation for centralized framework Foundation for the ERP implementation

Defined MD stewardship processIdentified KPIs being measured and reported

Organization is complying with MD policy & procedure inconsistentlyBroad awareness of MD governance

Complete ownership established Fully functional Data Governance bodyOrganization aligned and support MDM vision

Defined, measured MDM process end to endProcess that successfully navigates the risk/speed tradeoff

Organization has ownership in MDM processesFunctions report their own compliance metrics for MDM

Business Transformation

Legacy Systems

MDM

ERP

Master Data Master Data

MDM will handle master data (Global Master data)ERP will handle rest of the data (Local Master Data)MDM will go live firstEnsure no duplication of processes between MDM and ERPStart with consolidation, proceed to harmonization and

then march to centralization

Data Migration

Other Systems

MDM Project Team

CONFIDENTIAL© Copyright 2007 Wipro Ltd 15

Lexmark & Wipro Program Manager

Lexmark Program Director

LexmarkEnterprise Architect’s

NA, EMEA, LAD, APG

India

Onsite teamTrack leads

Offshore team

Program Management Team

Lexington

Lexington

Customer Data Owner

Product Data owner

Person Data Owner

Material Data Owner

Supplier Data Owner

Data Stewards

Data Process Owners

Good part of Journey

• Strong Leadership– Lexmark IT as well as business

• Strong Partnership– Lexmark and WIPRO, including SAP

• Business involvement throughout SDLC– Involvement in design and also during development and Unit

testing

• ERP Program in parallel– Kept MDM program on tight leash.

• Focus on Data Quality– Should be single focus of MDM program

Challenging part of Journey

• Better data profiling– Would have assisted better decision earlier in the project

• Material – Lack of ownership– Political struggle

• Person– Legal requirements

• ERP Program in Parallel– Unavailability of business users time– Change focus from global to local at times

• Resource turnover– Clear communication of resource duration– Unexpected departures

Best Part of the Journey

• Executive sponsorship• Data Quality Focus• Clear understanding of risk at start• Partnership working as expected• Recommend Multi-entity implementation

– Yes we can

Wipro MDM portfolio

Information Quality AssessmentBusiness Case BuilderMDM Roadmap

MDM Reference ModelMDM Reference ArchitectureMaster data governance services

Product & custom solutionsImplementation acceleratorsMDM foundation frameworks

StandardizationDe-duplicationEnrichment

• Q & A

Thank You

MDM/Data Governance Organization

DataGovernance

LeadProgram Management

1 SAP (Part Time)1 Lexmark (Full Time)

1 Wipro (Full Time)

Data Governance Council

CustomerLead

CustomerOwner

PartnerLead(s)

EnterpriseArchitect

DataStewards

Part TimeResources

ProductLead

ProductOwner

PartnerLead(s)

EnterpriseArchitect

DataStewards

Part TimeResources

MaterialsLead

MaterialsOwner

PartnerLead(s)

EnterpriseArchitect

DataStewards

Part TimeResources

SupplierLead

SupplierOwner

PartnerLead(s)

EnterpriseArchitect

DataStewards

Part TimeResources

Partner Lead

TechnicalImplementation

Architect

ApplicationInstallation

HardwareInstallation

DevelopmentLead(s)

DevelopmentPM

PersonLead

PersonOwner

PartnerLead(s)

EnterpriseArchitect

DataStewards

Part TimeResources

DevelopmentTeam

SAP Prof. Services

1 MDM Principal Consultant1 DQ Principal Consultant1 DQ Senior Consultant

1 Metadata Manager Consultant

White = Full Time

Blue = Part Time