Post on 05-Apr-2018
8/2/2019 Gaurav Patni
1/37
Master Data Management
for Omni-Channel Retailing
Gaurav Patni, Technology Integration Leader, David Jones Limited
8/2/2019 Gaurav Patni
2/37
Disclaimer
The views and recommendations provided inthis presentation are solely those of the author
(Gaurav Patni) and do not represent those of
David Jones Ltd.
8/2/2019 Gaurav Patni
3/37
MDM for Omni-Channel Retailing
Framework for developing MDM project roadmap
Key activities and artefacts in MDM project
lifecycle
Best practices for delivering MDM in an omni-
channel retail environment
8/2/2019 Gaurav Patni
4/37
Customer expectations are changing
Retailers must adapt or risk losing their customer
8/2/2019 Gaurav Patni
5/37
Omni-Channel Retailing is the new mantra
Omni-Channel enables single view of the custome
8/2/2019 Gaurav Patni
6/37
Technology is at the core of Omni-Channel
Central, federated technology applications and
MDM help create an omni-channel experience
MDM
8/2/2019 Gaurav Patni
7/37
MDM is the conduit for omni-channel operations
8/2/2019 Gaurav Patni
8/37
Enterprise Information Management Framework
Enterprise Information Management
Project Management
Master Data Management
Integration
Application
Technical Architecture
Training and Performance Management
Plan Analyze Design Build Test Deploy
Service Introduction
Information Management Journey
DataGovernance
Data
Quality
Project
Requirements
Prerequisites
Data
Architecture
MDM roadma is overned b EIM framework
8/2/2019 Gaurav Patni
9/37
Pre-requisites for MDM projects? Data Management and Architecture Assessment on 6 key capability
domains: Data Governance, Data Structure, Data Architecture, Master
Data & Metadata, Data Quality and Data Security. The assessmenthelps prioritize the pain points and create a Data Managementroadmap.
? Data Governance enables effective management of shared dataassets in the context of overall IT delivery. It addresses both functionaland technical issues; internally and externally available data; skillsdevelopment and resource management.
? Data Quality - Data Management initiatives should always be initiatedwith a data profile assessment to gain understanding of data integrity.
? Project Requirements - Align MDM Projects with enterprise project
requirements, e.g. Retail ERP or Data Warehousing or EnterpriseIntegration tool implementation.
8/2/2019 Gaurav Patni
10/37
Data Quality Impact
8/2/2019 Gaurav Patni
11/37
MDM Project Lifecycle
Plan Design Build Test DeployAnalyze Business case
Program roadmap
High level MD
entities
Solution blueprint
MDM tools &
technology
Integration,
Synchronization &Harmonization
requirements
Migration,
Transformation
/Conversion
requirements
MD entities
Align with
business
processes
Align DW/ BI
environment
Align with existing
applications
Align validationrules
Metadata
relationship with
MD entities,
processes & user
roles
Integration,
Synchronization &
Harmonization
requirements
Transformation/Co
nversion &
Migration
requirements
Master catalog for
MD entities
Groupings &
hierarchies of
attributes
Align validation
rules
Ownership of MD
entitles for security& audit purposes
Enterprise MD flow
Interfaces for
legacy/ host
integration
Mapping rules for
Synchronization,
Integration &
Harmonization
Mapping rules for
Migration &
Transformation/
Conversion
MD catalog/
repository
Attribute validation
ruled
Application
workflow
User interface
design
Detailed dataconversion design
Integration
technical design
Interface
agreements
Test MD validation
rules
Test application
workflow
Test security of
data attribute and
workflow
Prepare and
execute producttest
Prepare for data
migration
Transformation/
Migration/
Conversion
activities
Deployment
environment
Migrate
application
Pilot application
8/2/2019 Gaurav Patni
12/37
Key tasks and artefacts:
1. Develop business case
2. Develop MDM program roadmap
3. Identify and define high level master data entities
4. Develop high level solution blueprint
5. Identify MDM tools and technology
6. Identify integration, synchronization and harmonization
requirements7. Identify migration, transformation/conversion
requirements
Plan Design Build Test DeployAnalyze
MDM Project Lifecycle Plan Phase
8/2/2019 Gaurav Patni
13/37
Sample artefact - Program RoadmapPlan Design Build Test DeployAnalyze
8/2/2019 Gaurav Patni
14/37
Measures the directional improvements using ProfitLogic forecast on the business
1. Rate at which forecast error
decreases:Average number weeks until theforecast merges to the actual
performance of items
3. Actual OOS vs. target OOSVariance of actual out-of-stock vs. target
out-of-stock date by Sub and Class
2. Percentage of items with poorforecasts:
a) Percentage of all forecasted items that
resulted in poor forecastsb) Percentage of poor forecast by
reason(bad like item, bad scaling, notenough history, low rate of sale)
FrequencyReport
Chain, Sub?? Monthly
??
Metric Measurement Approach
Responsible
Vendor
Vendor
Measured at
Chain, Sub Monthly
?? VendorChain, Sub Monthly
Forecast Accuracy
Sample artefact - Solution MetricsPlan Design Build Test DeployAnalyze
8/2/2019 Gaurav Patni
15/37
Sample artefact - Business Process InventoryPlan Design Build Test DeployAnalyze
8/2/2019 Gaurav Patni
16/37
8/2/2019 Gaurav Patni
17/37
Sample artefact Tool Selection ScorecardPlan Design Build Test DeployAnalyze
8/2/2019 Gaurav Patni
18/37
Analysis
Req
IDRequirement Description
Business
AreaCR Status Release Comments
RequirementsDocument
Reference
2Track multiple names for building - specifically LegalName, Marketing Name PM 1
If a building has morethan one name, then
multiple addresses
will be set up for onecompany/building,
and they will be linked
using related addressbook fields.
3
Track total cleanable square footage at the building
level PM 1
Cleanable Sq Ft will
be tracked usingBuilding Log. LC =
PR, AMID = PR02.
4Enforce validation of area for GLA such that sum ofunits does not exceed total building area by date PM 1
PM Constant to
validate GLA will beturned on.
5
Track various building metrics to support the cost
allocation process for centralized contracts. Inparticular, track non-cleanable sf by building for
communication to vendors and auditing of vendor
invoices. (needed by procurement) PM 1
be tracked using
Building Log. LC =
PR, AMID = PR02.Vacancy Credit
Amount will betracked in Building
Logs. LC = PR,
AMID = PR01.
Sample artefact - Requirements Traceability MatrixPlan Design Build Test DeployAnalyze
8/2/2019 Gaurav Patni
19/37
Key tasks and artefacts:
1. Analyze master data (MD) entities
2. Align business processes with MD entities
3. Align MD entity constructs with DW/BI environment4. Align MD application architecture with existing applications
5. Analyze MD validation rules and align with businessprocesses and user roles
6. Identify metadata relationship with MD entities, processes &user roles
7. Analyze and plan for integration, synchronization &harmonization requirements
8. Analyze and plan for transformation/conversion & migrationrequirements
MDM Project Lifecycle Analyze Phase
Plan Design Build Test DeployAnalyze
8/2/2019 Gaurav Patni
20/37
1. Data Object Definition
1.1. Data Structure Diagram
1.2. Object Attributes
1.2.1. Data Object #1
Attribute
Name
Repository
ApplicationSpecific Info
Application
Attribute
Type Is
Key
Is Req Notes/Issues
1.3. Object Triggering Event(s) (source business objects only)
Event Action Issues/Comments
Sample artefact - Master Data DefinitionPlan Design Build Test DeployAnalyze
8/2/2019 Gaurav Patni
21/37
Sample artefact - Master Data Rules, StandardsPlan Design Build Test DeployAnalyze
8/2/2019 Gaurav Patni
22/37
Sample artefact - Conceptual Data ModelPlan Design Build Test DeployAnalyze
8/2/2019 Gaurav Patni
23/37
Marketing & Sales Lead
Printing &
PublishingOffice Segment
Segment Lead
Sales Personnel
Large Customers
Segment Lead
Sales Personnel
Large Customers
Key Accounts
Key AccountManager
C-Segment Sales
(Call Center)
Back Office Head
Back Office
Sales Personnel
Medium Customers
Sales Personnel
Medium Customers
Key Account
Sales Personnel
Note: A Role does not represent a position
Logistics
? Define overall Action Plan
? Determine Product Prices? Develop Segment Goals? Develop Segment Action Plan
Role Description
CorrespondingProcesses
Responsibilities
? The Marketing & Sales Lead is responsible for coordinating all activities within Sales and
leading the sales team. He / she decides on the overall sales st rategy together with MillManagement
? Define sales specific strategy and targets
? Define segment specific goals? Instruct Segment Leads? Define Segment Prices (together with segment leads)
?Monitor overall sales performance with respect to quantity, price and payment terms? Report Performance to Mill Management? Track performance of segments? Define Marketing Instruments and activities
Interfaces?Mill Management? Sales Personnel
Role Title ?Marketing & Sales Lead
?Analytical Skills
? Communication Skills? Sales Experience
Skills &
Qualifications
? Financial Analysis? Leadership Skills? Marketing & Sales Knowledge
? Finance? Segment Leads
? Manage Accounts Receivable? Develop Personal Sales Objective
? Demand Forecasting? Performance Tracking
Substitute: Segment Lead
? Customers
Sample artefact - Roles & ResponsibilitiesPlan Design Build Test DeployAnalyze
8/2/2019 Gaurav Patni
24/37
8/2/2019 Gaurav Patni
25/37
Start Date Event Expected Duration End Date
13 Jan 2001 Conversion test 3 weeks 3 Feb 20014 Feb 2001 CDB extract 8 hours 5 Feb 2001
6 Feb 2001 Validate CDB andload
70 hours 9 Feb 2001
11 Feb 2001 AMS Extract 24 hours 12 Feb 200113 Feb 2001 Merge and Load 12 hours 14 Feb 2001
14 Feb 2001 Contingency 5 days 18 Feb 200118 Feb 2001 Apply catch-up
transactions12 hours 19 Feb 2001
20 Feb 2001 "Go live"
Sample artefact Conversion PlanningPlan Design Build Test DeployAnalyze
8/2/2019 Gaurav Patni
26/37
Key tasks and artefacts:
1. Design master catalog for MD entities
2. Design groupings & hierarchies of attributes
3. Define MD validation rules and align with businessprocesses & user roles
4. Define ownership of MD entitles for security & audit purposes
5. Design enterprise MD flow
6. Design interfaces for legacy/host integration
7. Define mapping rules for synchronization, integration &harmonization
8. Define mapping rules for migration & transformation/conversion
MDM Project Lifecycle Design Phase
Plan Design Build Test DeployAnalyze
8/2/2019 Gaurav Patni
27/37
ReceiveCustomerRequest
1.0
DetermineRequest Type
1.1
Standard
1.1.1
ProvideStandardReports
1.2
DiagnoseRequestN
Y
1.3
GoodStanding
1.4
HandleImmediate
Y
1.3.1
UpdateStanding
N
1.3.2
Exit Process
N
1.3.3
Bring CustomerCurrent
Y
1.5
Respond toRequest Y
1.4.1
Route to BestQualified
N
1.4.2
PerformAdditionalDiagnosis
1.4.3
HandleImmediate
1.4.4
Respond toRequest
Y
1.4.5
Schedule OpenRequestN
Connector
Legend
High Level
Process
Process Decision
Transportation Exit
Process
Common
Process
Final
Outcome
Even
t
Input/Output
Stor
e
Sample artefact Business Process Activity DiagrPlan Design Build Test DeployAnalyze
8/2/2019 Gaurav Patni
28/37
Sample artefact Sequence DiagramPlan Design Build Test DeployAnalyze
8/2/2019 Gaurav Patni
29/37
Sample artefact Interface InventoryPlan Design Build Test DeployAnalyze
8/2/2019 Gaurav Patni
30/37
ORACLE
SQL*
Loader
Program
Custom
PL/SQL
Program
Custom Oracle
Staging Table(s)
Open Interface
Table(s)
Oracle Base
(Production)
Table(s)
Cleansed
Legacy Extract
File(s)
Single Request1
32
Standard Oracle
Import
Program
4
Sample artefactApplication conversion flow diagPlan Design Build Test DeployAnalyze
8/2/2019 Gaurav Patni
31/37
Key tasks and artefacts:
1. Build master data catalog/repository
2. Configure/customize attribute validation rule
3. Configure application workflow
4. Perform user interface design
5. Perform detailed data conversion design
6. Perform integration technical design
7. Develop interface agreement
MDM Project Lifecycle Build Phase
Plan Design Build Test DeployAnalyze
8/2/2019 Gaurav Patni
32/37
Key tasks and artefacts:
1. Test master data validation rules
2. Test application workflow3. Test security of data attribute and workflow
4. Prepare and execute product test
5. Prepare for data migration
MDM Project Lifecycle Test Phase
Plan Design Build Test DeployAnalyze
8/2/2019 Gaurav Patni
33/37
8/2/2019 Gaurav Patni
34/37
Ref #
Data
Entry
Time Task Description Owner
User
Mgr
Req'd
by Done StartDate
End
Date
1 Planning, Management & Hand-Over
1.1 Create Deployment Plan/Calendar 18-May 30-May 16-May 18-May
1.2 Coordinate deployment activities N/A N/A 17-May 20-Jul
1.3 Develop alternate/contingency deployment calendar N/A 30-May 30-May 30-May
1.4 Carry out Operational Test with ITSS 1-Jun 1-Jun 1-Jun 1-Jun
1.5 Carry out Production Readiness Review 6-Jul 6-Jul 5-Jul 6-Jul
1.6 Define final user test. 4-Jul 6-Jul 6-Jul 6-Jul
1.7 Carry out final user test. 6-Jul 8-Jul 6-Jul 8-Jul
1.8 System signed-off 9-Jul 9-Jul 18-Jul 20-Jul
1.9 Ensure all entries on Issue logs are Closed and Actioned 20-Jun 20-Jun 20-Jun
1.10 Deliverables handed-over (ABC Company) 26-Jul 20-Jul 20-Jul
1.11 Internal project deliverables/documentation content and delivery date agreed 19-Jun 19-Jun 19-Jun 19-Jun
1.12 Project hand-over completed (to Customer Services) 25-Aug 8-Jul 25-Aug
1.13 End of Project party fully organized 28-Jun 8-Jun
1.14 Siebel King / Queen agreed upon 1-Aug
2 User Teams & Resources for Roll-out
2.1 Confirm exact composition of workflow team 18-May 30-May
2.2 Confirm composition of HOCS team to remain on CS3 after go-live 18-May 30-May
2.3 Confirm composition of all other teams (names & numbers) 18-May 30-May
2.4 Communicate compositions of teams (expectation of users staying on CS3) 13-Jun 15-Jun
2.5 Support rota agreed for 3 weeks post implementation, inc weekends 25-May 17-May
2.6 Revised support rota agreed for 3 weeks post implementation, inc weekends 5-Jul 9-Jul
2.7 Support rota agreed for last 4 of 7 weeks post implementation, inc weekends 26-Jul
Sample artefact Deployment Work PlanDeployPlan Design Build TestAnalyze
8/2/2019 Gaurav Patni
35/37
Sample artefact Migration Request FormDeployPlan Design Build TestAnalyze
8/2/2019 Gaurav Patni
36/37
Leverage EIM for iterative development of MDM
Enterprise Information Management
Project Management
Master Data Management
Integration
Application
Technical Architecture
Training and Performance Management
Plan Analyze Design Build Test Deploy
Service Introduction
Information Management Journey
DataGovernance
Data
Quality
Project
Requirements
Prerequisites
Data
Architecture
8/2/2019 Gaurav Patni
37/37
Questions
Gaurav Patni
http://au.linkedin.com/in/gauravpatni
gauravpatni