+ All Categories
Home > Data & Analytics > Master Data Management - A Practitioner's View - Hemant Patil - 18/6/15

Master Data Management - A Practitioner's View - Hemant Patil - 18/6/15

Date post: 07-Aug-2015
Category:
Upload: bcs-data-management-specialist-group
View: 291 times
Download: 1 times
Share this document with a friend
Popular Tags:
8
BCS – DAMA, UK Master Data Management – Practitioner’s View 18 June, 2015
Transcript
Page 1: Master Data Management - A Practitioner's View - Hemant Patil - 18/6/15

BCS – DAMA, UKMaster Data Management – Practitioner’s View

18 June, 2015

Page 2: Master Data Management - A Practitioner's View - Hemant Patil - 18/6/15

Hemant Patil

100

Excellence

Enterprise Architecture – Deploying MDM reference architectures, information strategy formulation, toolset evaluation / selection, architecture governance forums

Solutions Architecture – Early engagement in project life-cycles, proposing solution options, securing sign-off through gating mechanisms, representations on Technical Design Authorities

Delivery - Lead Designer / Business Architect for BI, Data Warehousing and MDM projects, Technical Lead

Experience

Hemant is an Information Architect with over 18 years of experience, who specialises in helpingorganisations use information as a strategic asset. He has worked in Banking and Insuranceorganisations across UK, India and the Nordics. Key accounts are Aviva, Royal Bank of Scotland, UBS,Thomson Reuters and Nordea AB

Hemant has worked in Advisory and Delivery roles in large and complex organisations to help –

Improve the customer experience by removing inefficiencies in the sales and service processesthrough effective deployment of Customer MDM architectures

Generate actionable information out of a plethora of data assets littered across the enterprise byproposing and implementing Business Intelligence strategies

Enhance the trust in data as well as agility of IT change by creating the right Data Qualitymanagement frameworks and Data Ownership / Stewardship structures

Page 3: Master Data Management - A Practitioner's View - Hemant Patil - 18/6/15

What is Master Data?

101

Master data is the currency of the business processes in your organisation

Master Data

Used to describe the operations of

an organisation

Adds a business context to basic

data, thus turning it into

“information”

Metadata

Reference Data

Enterprise Structure Data

Transaction Structure Data

Transaction Activity Data

Data About Datae.g. Data models & definitions, Business rules,

technical information, operational data, audit data…

Codes and Descriptionse.g. List of values, SIC codes, Instrument ids…

Organisation Structurese.g. Sales / Legal Hierarchies, Business Topology,

Reporting structures…

“Nouns” of the Enterprisee.g. Customers (Parties), Vendors, Product,

Employee…

Health information for the Enterprisee.g. Account balances, sales volumes, inventory…

Page 4: Master Data Management - A Practitioner's View - Hemant Patil - 18/6/15

What is Management of master data?

102

Policies, procedures, organisation structures and technology required of management of key data entities in your organisation

Master Data Management

Page 5: Master Data Management - A Practitioner's View - Hemant Patil - 18/6/15

Implementing MDM – A Practitioners Approach

103

Structured, methodical approach, tempered with the right level of ambition

Formulate The Project

ProjectDefinition

Design & Profile ImplementationCommunicateCommunicateCommunicate

GOVERNANCE

• Assess and baseline MDM maturity

• Set a level of ambition

• Create the business case

• Confirm project scope

• Define delivery team and methodology

• Identify key risks

• Check for cross program dependencies

• Identify golden sources

• First pass data profiling

• Model the MDM domain(s)

• Define MDM architecture

• Choose a toolset

• Set up a DQ Framework

• Build and test

• Cut – over, migration, adoption

• Harmonise data

• Set up DQ monitoring

• Set up end user support

• Set up Data Ownership and Stewardship

• Create communication capsules

• Deploy on various channels – intranet sites, blogs, forums

• Road shows

MDM Strategy Project CharterLogical & Technical

Design

SOE / SOR, DQ Framework

Socialisation StrategyTypical deliverables

Page 6: Master Data Management - A Practitioner's View - Hemant Patil - 18/6/15

What could go wrong

Improper / incomplete bench-marking

Unclear business case

Poor architecture and strategy

Technology acquisition before anything else

Siloed MDM delivery

Lack of business participation – Governance structures, mind-set change, business process refinement

104

A large proportion of MDM projects fail

Page 7: Master Data Management - A Practitioner's View - Hemant Patil - 18/6/15

Culture of Transformation and of Right Usage of Data

105

Its not all about technology…

To-Be Data Culture

Improved behavior imbibed in mainstream business processes

Behaviour, Values, Norms

Strategy, Structure &

Goals

Processes & PracticesLeadership

Sub - optimal As- Is Data

Culture Cultural Discovery• Assessment of current behaviours

• Gap analysis against Target State

• Roadmap to address gaps

Cultural Transformation• Identify change champions

• Training and Coaching

• Integration incentive strategy

Cultural Integration• External and internal communication

• Events and motivational tools

Page 8: Master Data Management - A Practitioner's View - Hemant Patil - 18/6/15

Thank You

106

Excellent Architects. Globally.

[email protected]/in/hemantpatil1/

+44 7557 059147


Recommended