[client logo]

Capgemini MDM Implementation

Methodology

[project name, date]

 [client logo]

Table of Contents

1. Introduction..................................................................................................................................................... 2
2. MDM implementation Methodology................................................................................................................. 2
3. Inception Phase.............................................................................................................................................. 2
4. Elaboration Phase........................................................................................................................................... 6
5. Construction Phase......................................................................................................................................... 9
6. Transition Phase........................................................................................................................................... 12
7. Abbreviations................................................................................................................................................ 15
8. Change Log.................................................................................................................................................. 15

Prepared By Reviewed by Approved By

Name
Role Project Leader Project Manager
Signature
Date

Cover Title 1
 [client logo]

1. Introduction
1.1 Purpose of this document
This document contains the detailed methodology for Implementation of MDM.

1.2 Scope
This document details the implementation methodology for MDM. The methodology is based on MDM
implementation best practices and lessons learnt from multiple MDM engagements. This will need to
be configured and changed to meet client specific needs.

1.3 Target Audience

The intended audience for this document is

 MDM Project Leaders

 MDM Project Managers
 Development teams
 Delivery Assurance Group, Process Engineering group

2. MDM implementation Methodology

Capgemini MDM implementation methodology consists of the following phases

1. Inception Phase – Start up, Planning, DQ analysis, Requirements & Architecture

2. Elaboration Phase – Detailed Functional Requirements, Information Model and Design

3. Construction Phase - Development of MDM and ETL components

4. Transition – Testing and Deployment of the developed components

3. Inception Phase
Description of the phase
This phase is the first phase of the MDM implementation. The key activities performed in this
phase as

1. Scoping
2. Planning
3. Requirements Gathering and Validation

Cover Title 2
 [client logo]
4. Data Quality Analysis and Validation
5. High Level Architecture
Entry Criteria – Checklist

ID Item Responsible
1. Project approved Business / IT Leads
2. MDM Business Case and business funding is approved Business / IT Leads
3. Confirm MDM Assessment / Pre-study completed is completed and Client MDM Lead
recommendations included within the business case
4. Steering Team established Client Leads

 Business Sponsor
 IT Sponsor
 Information Owner

5. Core team established Client Leads /

Capgemini
 Business PM
 IT PM
 Business Data Stewards identified
 Key business SMEs
 Key IT stakeholders identified
 MDM Implementation Team
 MDM PM
 BA
 MDM Architect
 MDM Tech Lead/Off-shore PM

6. MDM&DQ Platform Strategy Document available Client / Capgemini

 Technology
 Platform
 Infrastructure

7. Draft conceptual information model defined Information owner

Tasks

ID Item Responsible
1. Conduct the Project Kick-Off Meeting IT PM
2. Project planning ITPM – Overall Plan
MDM PM – MDM
 Build End to End planning(High Level) Plan
 Build plan for inception and elaboration phase(Detailed Plan)
 Refine the estimates for elaboration phase

3. Data analysis DQ analyst

Business SME
 Data quality analysis of all source system data - Data Analyst

Cover Title 3
 [client logo]
 Define/Identify data quality rules (Match, Cleanse, etc) -
Business SME

4. Requirements Project BA
MDM BA
 Document business requirements - Business BA/Project BA
 Document draft functional requirements - MDM BA
 Document draft privacy requirements - Business BA/Project BA
 Document Non-functional requirements - Business BA/Project
BA

5. Information model Business Data

Steward, Domain BA
 Detail the conceptual information model

6. Architecture Project Arch, MDM

Arch
 Define the overall solution architecture - Project solution
architect (Source systems, consuming systems, integration
systems, End-to-end information flow)
 Define the MDM Architecture @MDM Architect

7. Infrastructure planning MDM

Implementation
 Conduct/Validate the Hardware and Software sizing in all Team
environments in alignment with MDM Strategy – Implementation
Team along with product vendor
 Conduct/Validate the MDM Logical & Physical Deployment
Topology( i.e. Servers, location, ports, network bandwidth etc )
8. Governance and PM
Verification
o Review Business Requirement Document
o Review High Level Architecture Design
o Review Conceptual Master Data Model
o Review Bill of Material (Infrastructure detail)
o Review Environment Deployment Architecture
o Review Data Assessment Report
o Review Project Plan

Exit Criteria

ID Item Responsible
1. Signed off Business Requirement Document Project Manager
2. Signed off High Level MDM Architecture Document Overall Soln Arch,
Client EA
3. Signed off Conceptual information Model Information Owner
4. Signed off Environment Deployment architecture Overall Soln Arch,

Cover Title 4
 [client logo]
Client EA
5. Signed off Non-functional requirements Overall Soln Arch,
Client EA, BAM,
ITAM/ SM
6. Signed off Project Plan (Overall & MDM) Business Sponsor,
IT Sponsor
Tools

 Project Planning – MPP

 Requirements Management – TBC
 Architecture diagram – Word/PPT
 Conceptual information model – ERWIN
 Task/Activity tracking – TBC

Templates

 PM Templates
 Project Management Plan (PMP templates)
 MPP Template
 Stakeholder Register
 Risk Register
 Issue Register
 Action Log
 Status Reporting
 MDM Reference Architecture (Capgemini and CDB MDM Architecture)
 Functional Specifications Document
 Estimation Tool – Great MDM

Cover Title 5
 [client logo]

4. Elaboration Phase
Description of the phase
This phase is the first phase of the MDM implementation. The key activities performed in this
phase as

1. Detailed Functional requirements (incl cleansing requirements)

2. Detailed Design
3. Information Models Logical and Physical Information Models
4. Infrastructure Set up
Entry Criteria – Checklist

ID Item Responsible
1. Signed off Business Requirement Document Project Manager
2. Signed off High Level MDM Architecture Document Overall Soln Arch, Client
EA
3. Signed off Conceptual information Model Information Owner
4. Signed off Deployment architecture Overall Soln Arch, Client
EA
5. Signed off Non-functional requirements Overall Soln Arch, Client
EA, BAM, ITAM/ SM
6. Signed off Project Plan Business Sponsor, IT
Sponsor
Tasks

ID Item Responsible
1. Detail functional requirements for MDM MDM BA

 Understand and analyze the business requirements & use

cases
 Map business requirements to MDM functional requirements
& use cases
 Define the MDM business rules based on the business
inputs and Data profiling results.
 Define the Match and Merge rules based on Data analysis.
 Define cleansing requirements
 Prototype the User interface of MDM(Optional)
 Prepare the functional requirements document

2. Detail design for MDM MDM Architect / Lead

Developer
 Detail the information management processes (Create,
Update, Delete)
 Design the MDM services ( Ex. Create Consumer, Search

Cover Title 6
 [client logo]
product etc)
 Design the interfaces to MDM ( Ex: User Interface, Batch,
Message queues etc)
 Define integration contracts with source and consuming
systems
 Design the Initial and ongoing data loads into MDM
 Define the data flow diagrams
 Define the system architecture (i.e includes all the source
and consuming systems for MDM, their technologies,
integration)

3. Information model MDM Architect / Lead

Developer
 Create the logical Data Model
 Create the Physical data model - Define the entities (such
as catalogs, consumer etc.), attributes, relationships,
hierarchies etc

4. Infrastructure set-up Infrastructure team

Set up development environment as per agreed sizing

5. Create Test Strategy Document Test Manager
Verification

 Review Functional Requirements

 Review Integration Contracts
 Review Detail Design
 Review Logical Data Model
 Review Physical Data Model

Exit Criteria

ID Item Responsible
1. Signed-off Functional Requirements Business BA / BAM
2. Signed-off Integration Contracts Source / Consuming
System Owners
3. Signed-off Detail Design for MDM Client Solution Architect
4. Signed-off Logical Data Model Domain Arch / Client
Solution Architect
5. Signed-off Physical Data Model Client Solution Architect
6. Development environment set up completed MDM PM
7. Updated estimates approved for construction and transition IT / Business Sponsor
phase
8. Test Strategy Document Approved ITPM
Tools

Cover Title 7
 [client logo]

 Requirements Management – Confluence

 Architecture diagram – Word/PPT (In confluence)
 Conceptual information model – ERWIN
 Task/Activity tracking – Visual Studio

Templates

 Design Document – Party Domain

 Design Document – Product Domain
 Functional Specifications Document
 Estimation Tool – Great MDM

Cover Title 8
 [client logo]

5. Construction Phase
Description of the phase

The primary objectives of the Construction phase is to complete the configuration, customization,
development & unit testing of the MDM Solution based upon the functional requirements and
baselined architecture to achieve a MDM solution ready for the system Integration testing and UAT. At
the end of the Construction Phase the project team will have a Unit tested version of the solution ready
for System Integration Testing

Entry Criteria – Checklist

ID Item Responsible
1. Signed-off Functional Requirements Business Owner
2. Signed-off Integration Contracts Source and consuming
system owners
3. Signed-off Detail Design MDM Solution Architect
4. Signed-off Logical Data Model Information Owner
5. Signed-off Physical Data Model MDM Solution Architect
6. Development environment set up Client
7. Updated plan and estimates for construction and transition MDM PM
phase
8. Configuration and coding guidelines MDM Tech Lead
9. Test data available for development Source system owners
10. Test Strategy document approved ITPM
Tasks

ID Item Responsible
1. Physical Data model implementation – MDM Configuration MDM Developer
2. MDM Development CRUD processes – eg. Create, Update, MDM Developer
Delete customer (mainly applicable to Party MDM)
3. MDM tool configuration - Configure the MDM tool to implement MDM Developer
the OOB features as per design specifications

 Configure Business Rules

 Develop and configure to enable security
 Match/Merge rule configuration - Configure the match/merge
rules as per design specifications
 Creating hierarchies as per design specifications
 Build data management workflows as per design

Cover Title 9
 [client logo]
specifications

4. •Customization - Customize the MDM solution to add features MDM Developer

over and above those of OOB as per design specifications
detailed in the Elaboration phase
5. Develop the MDM services ( Ex. Create Consumer, Search MDM Developer
product etc)
6. Configure & test Match & Merge Rules (only for Party MDM) MDM Developer
7. Develop the Integrations to MDM ( Ex:Real time, Batch, Integration Developer
Message queues)
 Develop Batch jobs - Develop batch jobs process the data
inside MDM Hub
 Develop services and batch jobs for realtime and near
realtime data load for inbound & outbound data load
 Develop scheduler scripts
 Develop Data migration scripts for initial load
 Developing routines for incremental loads
 Develop error handling
8. Develop the Initial data loads into MDM Integration Developer
9. DQ Development – Develop DQ Cleansing rules as required DQ Developer
10. Test Plan Document Test Manager
11. SIT Scripts Development Test Manager / Tester
12. Test environment preparation – Confirm test environments are Test Manager
ready for SIT for all source, consuming and MDM systems.
13. MDM & DQ Infrastructure set-up Client
 Set up QA, UA and Prod environment as per agreed sizing
Verification

 Review MDM Configuration Components

 Review ETL components
 Review DQ components
 Review and Sign off Test Plan and Scripts
 Review Test environment readiness

Exit Criteria

ID Item Responsible
1. Unit tested MDM, ETL and DQ components MDM PM
2. Signed off test plan and scripts ITPM
3. Test acceptance criteria agreed Test Manager
4. Test environments set up for QA, UA and Production ITPM, Test Manager
Tools

 Project Planning – MPP

 MDM development Tools (Client Tools)
 DQ Tools (Client Tools)

Cover Title 10
 [client logo]
 ETL Tools (Client Tools)
 Test Plan Document : MSWord
 Test Execution – HP ALM / Visual Studio (TBC)
 Configuration Management – Client tools

Templates

 Development Standards and Guidelines – Tool specific

 Development Standards and Guidelines – Tool specific

Cover Title 11
 [client logo]

6. Transition Phase
Description of the phase

The primary objective of the Transition phase is to ensure that the MDM solution is ready for
deployment into production. At the end of the Transition phase the project team will have the technical
solution deployed into production. The main activities in this phase include SIT, UAT and Production
deployment
Entry Criteria – Checklist

ID Item Responsible
1. Unit tested MDM, ETL and DQ components MDM PM
2. Signed off test plan and scripts ITPM
3. Complete test data available for development Source system owners
4. Test acceptance criteria agreed Test Manager
5. Test Environments set up for QA, UA and Production ITPM, Test Manager
Tasks

ID Item Responsible
1. System Integration Test - The objective is to validate that all MDM Developers /
software components are functionally correct and end to end Testers
data processes are working as per the requirements. This
includes testing data flow from source system to consuming
systems through MDM solution. There are typically multiple
iterations of SIT within a standard MDM SIT cycle.
2. Performance Testing - The purpose is to determine the ability of Performance Tester
the system to process expected production volumes under
defined production environment conditions, as well in peak
business conditions. This could be done manually or using
automated methods.
3. Defect Fixing after System Integration Testing & Performance MDM Developer
Testing
4. Bulk (or Initial) Load Testing – Complete data set is loaded into MDM Developer
MDM solution
5. Incremental Load Testing – CRUD processes (Create, Update, MDM Developer
Delete) of the data is tested using incremental loads. All the
business processes that need data change are tested using
incremental load testing.
6. SIT Signoff : Sign off of SIT as per agreed Acceptance criteria. ITPM
7. User Acceptance testing: The objective of this is to validate that Business PM
all the MDM / DQ solution meets all the data requirements from
business perspective.
 All the data stewardship functionalities are tested

Cover Title 12
 [client logo]
 All the data dependent consuming systems functionality is
tested
8. UAT Sign off: Sign off of UAT as per agreed Acceptance criteria Business Owner /
Information Owner
9. Support Handover and knowledge transition: Development team MDM PM
works transitions the knowledge to the Support Teams.
10. Technical Deployment Documentation– Create technical MDM, ETL, DQ
Deployment documentation development team
11. Technical Deployment – Once UAT is signed off, Technical Developers / Deployment
components for MDM, DQ and Integration are deployed into the team
Production environment
12. Initial Data Load – Load complete data set into Production Developers / Deployment
environment. This activity may also include generation of team
extracts / Services for the consuming systems to consume data
from MDM
13. Operation Acceptance Testing – Existing support teams conduct MDM Support teams
acceptance testing from operations perspective – To ensure
that solution is ready to be operated in production by the
support team.

eg. Does the Data Load complete in the time required, is all
operations documentation ready.
14. OAT Sign off – This is the final sign off by the Support team to MDM Service Manager
confirm that the system is live in production. Initial data load
may be conducted again post this if required
Verification

 Review and Sign off SIT

 Review and Sign off UAT
 Review and Sign off OAT

Exit Criteria

ID Item Responsible
1. System deployed in production environment MDM PM / ITPM
2. Support team has the knowledge and tools to support the MDM Service Manager
environment
Tools

 Project Planning – MPP

 MDM development Tools (Client Tools)
 DQ Tools (Client Tools)
 ETL Tools (Client Tools)
 Test Plan Document : MSWord
 Test Execution – HP ALM / Visual Studio (TBC)
 Configuration Management – Client tools

Templates

Cover Title 13
 [client logo]

 Deployment Document
 Additional Templates (to be added – eg. Scripts etc)

Cover Title 14
 [client logo]

7. Abbreviations
Acronym /
# Abbreviation Description / Detail
1. MDM Master Data Management

8. 2.
3.
4.
PIM
NFR
DAM
Product Information management
Non Functional Requirements
Digital Asset Management
5.
6.
7.
8.
9.
10.
11.

Change Log
Please note that this table needs to be maintained even if a Configuration Management tool is used.

Version Changes made

Number
V1.0 <First version>
V1.1 <If the change details are not explicitly documented in the table below,
reference should be provided here>
Page Changed Effective Changes effected
no by date

V1.2 <If the change details are not explicitly documented in the table below,
reference should be provided here>
Page Changed Effective Changes effected
no by date

Cover Title 15
 client logo

About Capgemini
With almost 193,000 people in over 40 countries, Capgemini is one of the
world's foremost providers of consulting, technology and outsourcing
services. The Group reported 2016 global revenues of EUR 12.5 billion.

Together with its clients, Capgemini creates and delivers business and
technology solutions that fit their needs and drive the results they want. A
deeply multicultural organization, Capgemini has developed its own way of
working, the Collaborative Business Experience™, and draws on
Rightshore®, its worldwide delivery model

www.capgemini.com

The information contained in this document is proprietary and confidential.

It is for Capgemini internal use only. Copyright © 2015 Capgemini. All rights reserved.
Rightshore® is a trademark belonging to Capgemini.