Get documents about "Business Administration and Management Ppt - PDF
W
Description
Business Administration and Management Ppt document sample
Document Sample
Information Systems
Dow's Master Data Management Business Processes
Chemical Industry SAP Users Group (CISUG)
April 2006
Jim Whyte / 04-2006 UNRESTRICTED - May be shared with anyone Page 1
Information Systems
Agenda
• Background – Master Data Management at Dow
• Data Architecture, Strategy and Roadmap
• Master Data Management
• Data Governance
Jim Whyte / 04-2006 UNRESTRICTED - May be shared with anyone Page 2
Information Systems
Global Codes Introduction
Historic view on global codes in Dow
‘Global codes are the key cornerstones to achieve integration of transaction
systems, and enable reporting across functions and businesses.’
• 1970’s and 80’s:
Area codes (e.g. Product, Customer, Market hierarchy), supporting local / area
applications
• Late 80’s - early 90’s:
Created global codes to support SAP-R2 implementations
Implemented global Codes Admin system (INCA) to centrally maintain and
distribute codes data (globally common data segments)
• Late 90’s:
Further explore use of global codes in other global applications (Data Warehouse)
and for other work processes, like Market/Sell, Manufacturing, etc.
Note: Reference data = Codes data = Master data
Jim Whyte / 04-2006 UNRESTRICTED - May be shared with anyone Page 3
Information Systems
Global Codes Introduction
Global Codes Subjects implemented to-date
Market Structures
Competency
Product Structures (VBM)
Bus. Upper structure Person
Planned Product Specified Material
Material
Trade Product
Substance
Document
Business Partner roles
Facility / Location
v
Organizational Unit Other
Geography
Dow Company Area Mgt. Groups Organization
Payment Terms Location
Units of Measurement
Currency
1990 1995 2000
Jim Whyte / 04-2006 UNRESTRICTED - May be shared with anyone Page 4
Information Systems
Existing Master Data Objects
• Customer • Area Management Group
• Supplier • Language
• Employee • Substance
• Contractor • Currency
• Global Material • Cost Center
• General Ledger • Business Structure
• Country • Industry Structure
• Primary Geopolitical Subdivision • Work Process
• Secondary Geopolitical Subdivision • Function
• Place (City) • Client
• Site Group • Company
• Site • Unit of Measure
• Facility • Payment Term
• Area Management Group • Planned Product
• Trade Product
Jim Whyte / 04-2006 UNRESTRICTED - May be shared with anyone Page 5
Information Systems
Data Architecture Principles
Jim Whyte / 04-2006 UNRESTRICTED - May be shared with anyone Page 6
Information Systems
Data Principles
Data architecture is based on a foundation of
principles that govern data integration / sharing
• Shared Data is an Enterprise • Reference Environment
Resource
• Reference Code
• Data Administration
• Meta-data Repository
• Data Ownership
• Meta-data Content
• System of Record
Ensure Alignment Between Data Principles and Project Design
Jim Whyte / 04-2006 UNRESTRICTED - May be shared with anyone Page 7
Information Systems
Shared Data Strategy
Data that spans more than one application or Dow work process
and/or is exchanged with parties external of the enterprise
Federated– Data that is Enterprise Shared Entities
shared/exchanged between Dow and External
any external party Party
Work or Data
Process Source
Enterprise – Data that is TDCC
shared/exchanged internally within
Dow, across more than one Work Work Work non-TDCC
Process Process Process
Exchanged
Work process – Data that is Federated
shared/exchanged across more than Entities
one application within one work
process Common Work Process Entities
The goal is to document those data objects (data subjects/entities, etc.) that are both
basic and critical to the business.
• By basic, we mean that it is probably mentioned many times a day in normal
conversation.
• By critical, we mean that the business would be nonexistent, or completely different
without this concept
Jim Whyte / 04-2006 UNRESTRICTED - May be shared with anyone Page 8
Information Systems
Data Architecture Roadmap: 2015
Data Architecture Vision
Best in class delivery of the right information at the right time, in the right place for the right party, to make informed and timely
decisions.
Mission
Reusable, accurate, integrated and reliable information to support business activities..
Key Strategic Emphasis - Geographies
Data Architecture Elements of Solution
Governance Information Sharing Interoperability Data Access Data Quality Practices &
(Reuse) Standards
• Establish data ownership • Encourage the • Leverage service • Security data • Establish data quality • Establish management
along with data leverage and reuse provider solutions and classifications and measures for all practices, guidelines
stewardship roles and of business critical proactively work with functional roles drive the business critical data and standards to ensure
responsibilities to data across the partners, suppliers and access authorization assets, regardless of long-term sustainability.
proactively manage extended standards organization process. Classification data type. Implement
information risk, regulatory enterprise. to facilitate adoption of of data is required in control plans to
compliance and ensure industry standards. order to define roles and ensure the data is
enterprise shared data is access levels to ensure routinely audited and
“fit for purpose”. the right data to right “fit for purpose”.
people.
Jim Whyte / 04-2006 UNRESTRICTED - May be shared with anyone Page 9
Data Architecture – Expanded View
Information Systems
Profile Cleanse Enrich/Augment Monitor
Data Quality
External /
ERP CRM HR Maintenance
3rd Party
Cust Vend Loc GMID Pers Cust Pers Loc Loc Org Pers Vend Equip Pers Loc GMID Cust
Reference DV Reference DV Reference DV Reference DV Reference DV
Ref DV
Ref DV
INCA eMail
Data Quality
Data (Hub)
Ref DV
Ref DV
File
Other Warehouse Shares
X-Ref
Master Data
Maintenance Eco-System
Ref DV
Ref DV
Legacy Load Mapping Maintenance Wholesale Doct’s
Publish Subscribe Use Registry
Tables
Master Data
Ref DV
Ref DV
External / Retail
Repository Archive
3rd Party Tables
ETL EAI Replication Enterprise Integration Bus Publish Subscribe
Name Business Rules
Enterprise Data Repository Format Ownership
Length Transform Rules “Metadata” Definition System of Record
Jim Whyte / 04-2006 UNRESTRICTED - May be shared with anyone Page 10
Information Systems
Corporate Data Model
World Map View: In much the same way a world map is used to show the continents, nations, bodies of
water and their relationships, the corporate data model is used to show all of the concepts or subject areas of
a corporation and their relationships (i.e. show the “big picture” for the enterprise).
Comprehensive: The existing CDM really represents only a Reference data (INCA) view of the enterprise.
There had been no attempt to date, to document the key business transaction related data entities or
relationships that the corporation depends on to operate.
End-to-End Process: Although still a work in progress, this streamlined conceptual data model depicts both
the reference and transaction subject data areas, along with their key inter-relationships. Using this model,
you can walk through the high level end-to-end process flows of:
Lead Manage
• Objective to Organization • Order to Cash
• Capital to Competency • Procure to Pay
• Stimulus to Strategy • Raw Material to Finished Good
• Concept to Production
• Requirements to Resource
• Threat to Response
Use: The intended audience for this model includes: the architect team, SA’s, LAS’s, CMIT’s and Program
Managers. We can leverage this model to get agreement on the meaning of data subjects and relationships
(context), perform high-level impact analysis, project scoping and opportunities for data reuse (planning), to
resolve name and definition clashes and relationship conflicts (issue resolution).
Jim Whyte / 04-2006 UNRESTRICTED - May be shared with anyone Page 11
Corporate Data Model
Information Systems
opportunities for strategic alliances
has business requirement
buys
PRODUCT SALES PRODUCT
DEVELOPMENT develops sold via
ORDER / CONTRACT
Substance Service negotiates
generates
Sale
Property is stored as Saleable
generates
Product Purchase
Compound
Recipe REVENUE
funds PORTFOLIO
MANAGEMENT
Product Sales
Business Idea/Concept Business
Investments EXPENSE
defines Technology
Cash Mgmt
manufactures Capability Raw Material
INVENTORY PRODUCTION Royalities
Supplies
MRO Item Engineering manages determines
SARD
Production
Saleable
...
Product Quality sells accumulates
negotiates
is consumed by ORGANIZATION
Raw Material Maintenance
Company incurs
Intermediate provides
labor for
Function
PERSON
Business complies with
is moved by Dow Employee delegate tasks to REGULATION
is consumed by Non-Dow Government
PURCHASED PRODUCT Regulation establishes
owns
ASSET Dow Policy BUSINESS PARTNER
Raw Material
is stored as
Equipment Industry Std. Customer
MRO Item
is negotiated utilizes
Intellectual Supplier
Property
Service Shareholder
B-n-A
LOCATION Society
is located at
MATERIAL MOVEMENT
is located at Dow Internal
Transport occurs between is located at
Geopolitical
Shipment
Electronic
Jim Whyte / 04-2006 UNRESTRICTED - May be shared with anyone Page 12
Information Systems
Data Architecture
What are we trying to manage? Layered Data Hierarchy
KPI’s, Hierarchies,
Sales Reports,
Historical Categories and
Inventory, etc.
Reporting reporting dimensions
How the data will
Purchase Orders, Transactional
Transaction Data behave in the
Sales Orders
transaction systems
Data applies only
Pricing, Next Generation Conditional Dynamic in specific situations
BOMs Opportunities Master Data (if this customer & material,
than this price)
Master Data defines
Material, 50+ MDM
Master Data Stable the structure and how it
Customer, Objects behaves in the
Person
transaction systems
Configuration data
Order Type,
Reference / Configurable Data Static defines your
Plant Configuration 2000 R/2 Tables
system and limits of
all the elements
Reference: PWC MDM 01/2006
Jim Whyte / 04-2006 UNRESTRICTED - May be shared with anyone Page 13
Information Systems
Master Data Management
Jim Whyte / 04-2006 UNRESTRICTED - May be shared with anyone Page 14
Information Systems
Master Data Management
A Core Control Point for Data Integration
Decouple master information
from individual transaction Master Data
Master Data Management is
applications
a set of disciplines,
technologies, and solutions
used to create and maintain
Ensure consistent master Transactional
Historical /
consistent, complete,
information across transactional Systems
Analytical
contextual and accurate
and analytical systems Systems
business data for all Master
Data
stakeholders (users, and
applications)data
Address master
across and For All Types of Master Data
beyond the enterprise
issues strategically, not just …products, organizations, locations, trading partners,
“after the fact” in the data employees, customers, equipment, assets, accounts,
warehouse policies…
Reference: IBM SOA and MDM Overview – 01/2006
Jim Whyte / 04-2006 UNRESTRICTED - May be shared with anyone Page 15
Information Systems
Review of MDM definition / objectives
Master Data Management (MDM) is both a business strategy
and a technical solution.
Master Data Management includes the:
• People/organization
80%
• Processes and
• Technology 20%
used to administer and govern reference data shared and
exchanged across the extended enterprise.
A Master Data Management strategy and solution are critical to
managing corporate information in a consistent, controlled, and
“single-view” capable manner.
Jim Whyte / 04-2006 UNRESTRICTED - May be shared with anyone Page 16
Information Systems
MDM Components
• People / Organization
• Data Ownership, stewardship, roles and responsibilities
• Process
• Create, Update, Discontinue, Outsee, Archive, Purge
• Technology
1. Code Maintenance (supporting Dow business requirements)
2. Data Quality (profile, analyze (gaps), cleanse and monitor)
3. Data Integration (load, distribute, replicate and retrieve)
4. Metadata (business and technical documentation)
Jim Whyte / 04-2006 UNRESTRICTED - May be shared with anyone Page 17
Information Systems
What is a Global Code?
• Globally common master / reference data
• Customer, Supplier, Material, Product Hierarchy…
• Globally common attributes
• Customer: Name, Address, Corporate HQ…
• Material: Name, Characteristics, Class, UofM…
• Application agnostic
• Identical for every legal and business entity
• Enterprise KPI’s / reporting dimensions
Administered on a global basis
Jim Whyte / 04-2006 UNRESTRICTED - May be shared with anyone Page 18
Information Systems
MDM Strategic Direction - Summary
• Master/reference Data (Enterprise Shared Data) is application agnostic
• Principle of “One”:
» Single system of record for each data object
» Single data owner for each data object
» Single, unique code for each data object instance
» Single system of reference, providing a single view of each data instance for the
enterprise (data hub)
» Single data definition - values represent the same meaning across all systems
and files
» Single data format (data standard) for each data object
» Data flows in a single direction, from data source to the system of reference
• Consistent:
» operating discipline (GCEC Best Practices)
» tools (maintenance, DQ/Cleansing, Distribution, Replication)
» process (maintenance, distribution, replication, audit trail, ILC mgmt)
» data content across:
• Legal Entities, Work Processes, Applications, Instances, Clients,
Companies, Plants,
• Data is optimized for data consumption vs. data capture
» Presentation of information for Legal / regulatory requirements takes precedence
over Dow management requirements
Jim Whyte / 04-2006 UNRESTRICTED - May be shared with anyone Page 19
Information Systems
MDM - Data Quality Framework
Strategy / Approach
Governance
• Establish the vision, strategy, principles, and controls
Identify Assess Source Normalise Validate
Measure
• Identify source
systems and
• Analyse the
nature of the
• Identifies and
isolates the data
Analyze
• Standardise data
values and
• Corrects, verifies,
cleanses and
(Profile) and
system of record data elements in data formats according
(Cleanse) appends data
category structures to business rules based on a set of
(federated, (includes 3rd Party algorithms
enterprise, work references)
process, app)
Enrich Match Consolidate Distribute Measure Report
• Enhances the Improve
• Searches and • Combines • Combines Control
• Qualifies and • Provides
data by identifies unique data unique data quantifies the reporting about
appending (Enrich/Augment)
duplicate elements from elements from (Monitor)
number and data quality
value –added records matched matched types of and status
information records into a records into a defects
single source single source
Jim Whyte / 04-2006 UNRESTRICTED - May be shared with anyone Page 20
Information Systems
Strategy: Dominant Master Data Source
Single system of record for each master data object, controlled distribution and
replication via consistent publish and subscribe rules.
Dow
Creation &
ERP MDM
Maintenance
Strategy
CRM
Distribution
Master Data HR Data (Hub)
Management Warehouse
PLM
Enterprise-wide common
data objects and attributes Other…
“Single view” of Master Data
are maintained in an
available in the data
application agnostic system Transaction systems add “localized
warehouse (data hub)
data” to the enterprise common data.
Transaction systems can be the
system of record for unique master
data.
Jim Whyte / 04-2006 UNRESTRICTED - May be shared with anyone Page 21
Information Systems
Managing the Strategic Data Objects
Logical Data View Physical Data View
Steering Team Data Class
Strategy –
Enterprise View
Data Subject Application
Project Team
Data Entity Physical Data Obj
Definition Content Implementation
Business Rules Execution Run the Business
Attribute Field
GCEC MET and Best Practices
Governance Leverage/Reuse Interoperability Data Access Data Quality Practices & Stds
TA 3.0 Framework
Jim Whyte / 04-2006 UNRESTRICTED - May be shared with anyone Page 22
Information Systems
Candidate New Master Data Objects
• Person • User
• Equipment • Building
• MRO Commodity (Catalog Items) • Region / Territory
• Equipment Groups • Substance
• Equipment Specification • Container
• Parts Management • Transportation Type
• Manufacturers • Organization
• Parts • Contact Mechanism
• Warehouse • SAP Organizational Structure
• Warehouse Item • New mySAP tables & Objects
• Hierarchies, Reporting Structures • Others…TBD
Jim Whyte / 04-2006 UNRESTRICTED - May be shared with anyone Page 23
Information Systems
Data Stewardship Roles & Responsibilities
Technology People &
“X-Work Process alignment” Process Aligned”
“Work Process “Business and Shared Service Aligned”
Strategy / Corp view Definition / Rules Content / Execution
Data Stewardship Steering Team
Oversight, information policy, funding, data
Data Stewardship Steering Team quality measurement targets, stewardship program
Corporate Data Architect W.P. Data Steward Managerial/Process Leader
Data Strategy, reconcile Work Mgmt ownership of data Business accountability for
Process views; Maintain Corporate definition/rules for a data timely, correct, accurate data
Model , Principles & Standards; subject leveraged across the in the business/function
Maintain processes in data Corporation
Project Team
Data Focal Point (D&M Team) Data SME Data Producers
Architecture compliance in projects; Implementation of data Input of data in accordance
initiate potential new Data Objects; definition, rules, operating with rules; front-line
manage X-WP Data Subjects discipline; support of accountability for data quality
data producers
Jim Whyte / 04-2006 UNRESTRICTED - May be shared with anyone Page 24
Information Systems
Master Data Governance
• Global Codes Expertise Center
Jim Whyte / 04-2006 UNRESTRICTED - May be shared with anyone Page 25
Information Systems
Global Codes Expertise Center
The Global Codes Expertise Center provides vision, direction, technology and support services needed to
continuously improve the quality of Master Data. We also promote the integration of Master Data across
Dow's business systems and work processes to reduce operating costs and maximize data value.
The key objectives for the Global Codes activities includes:
• Create a model for staffing codes projects
• Establish well-defined roles and responsibilities
• Eliminate rework
• Standardize tools, policies and processes
• Reduce number of handoffs
• Improve timeliness and quality of decision-making
• Continue to improve codes process
• Key enabler for implementing in half-the-time, twice the volume, with equal quality
Jim Whyte / 04-2006 UNRESTRICTED - May be shared with anyone Page 26
Information Systems
Global Codes Functional Areas & Sub-Processes
Global Codes
Codes
Operations
Expertise Projects
& Support
Center
STRATEGIC TACTICAL OPERATIONAL
DIRECTION INITIATIVES SUPPORT
Define & Maintain Create Code Solutions Maintain and
Best Practices Support Codes
Plan & Assign
Manage Quality Codes Resources Manage Quality
(Strategic) (Tactical)
Create & Maintain Code Strategy
Jim Whyte / 04-2006 UNRESTRICTED - May be shared with anyone Page 27
Information Systems
Ownership versus Management of Data Subjects
Ownership
Supply Commerci Procureme Manufactu
Quality Finance
Chain al nt ring
Codes Material Liable Facility
Customer Vendor SMC
(Master Upper Customer Site
MRO Titles
Data) Structure Cost Site Group
Materials Center
Geo
Contacts World
Field Area
C&D
Seller and Currency
Bom’s
Industry Company
Routings
Assignmen
Freight
ts
Rates
Manage Life Implement, Support, Design, Technology, Systems, Improvement,
Cycle Work Process MET, Training, Data Maintenance, Metrics, Monitoring
Jim Whyte / 04-2006 UNRESTRICTED - May be shared with anyone Page 28
Information Systems
Master Data Management - Data Ownership
Procurement
Raw Materials, Packaging Materials, Vendor, Equipment, Spares, Capital, MRO – Contracts, Leases, Land,
Supply Chain
Commercial Materials, Geopolitical, Unit of Measure, Plan Level Data, BOM,s Routings, Freight Rates,
Record and Report
Business Upper structure, Plan Product, Company, Cost Center, Currency, Liable Customer, Payment Terms,
Area Management Group…
EH&S
Substance, Hazardous Materials
Quality
Specified Material, Title
Market / Sell
Customer, Trade Product, Field Seller Assignments, Industry Assignments
Manufacturing
Facility, Site, Site Group
Human Resources
Employee Number
Develop & Commercialize Technology
Research & Development Material Coding
Jim Whyte / 04-2006 UNRESTRICTED - May be shared with anyone Page 29
Information Systems
MDM Styles to be Considered
Governance
0 1 2 3 4 5
Decentralized Centralized
Dow
Stewardship
0 1 2 3 4 5
Siloed Enterprise Wide
Dow
Maintenance
0 1 2 3 4 5
Operational App Application Agnostic
Dow
Data Integration
0 1 2 3 4 5
None Real-time
Dow
Jim Whyte / 04-2006 UNRESTRICTED - May be shared with anyone Page 30
Related docs
