Beruflich Dokumente
Kultur Dokumente
Pharmaceuticals
The Pharmaceutical segment's broad portfolio focuses on unmet medical needs across several therapeutic
areas: oncology; infectious disease; immunology; neuroscience; cardiovascular and metabolism. It includes
products in the anti-infective, antipsychotic, cardiovascular, contraceptive, dermatology, gastrointestinal,
hematology, immunology, neurology, oncology, pain management, urology and virology fields.
TO:
North America
Domain:
D i M
Material
i lDData
Platform: One ERP System
Global
Domain: Material Data
Platform: Multiple ERP Systems
Disconnected • Absence
Ab off centrall tooll has
h resulted
l d in disparate
di local
l l solutions
l i
• Scalability / extensibility are curbed
Tools • Significant manual effort to get reports with consistent data
• Enable business processes to be efficient, complete, accurate (end 2 end) by ensuring data
is standardized at the appropriate level and remains fit for its intended use in the business
Standard • Enabling effective business decision making as data, its purpose, and its relevance to
b i
business process are wellll understood
d d by
b the
h business
b i
• Define Data Ownership & Accountability
• Ensure
E that
h data
d is
i off appropriate
i quality
lit (accuracy,
( completeness,
l etc.)) to meet business
b i
Accurate needs
• Enforcement of Data Standards
• Ensure the quality of data is readily available to put awareness of compliance / efficiency
risks with the business
Visible • Ensure that data is appropriately stored, segmented, standardized, etc. (overall data model)
to support business intelligence (access to raw data)
• Visibility to Master Data Management Process
• Enable efficient business processes by ensuring data within that process is valuable and
Gain Support
pp from Senior Leadershipp
Identify Functional Owners
Share Ownership:
Data that is consumed by multiple departmental processes or material types.
Condense Ownership:
Where we want to drive global standardization and there is no value in site
differentiation.
Functional Area:
Dependant on the accuracy of the data.
Local Domain:
Data specific to a site or system, ownership resides in that level. No broader use
expected.
expected
Initial
Assessment
2050
Prioritization
227
Value
Assessment
39
Target
30
Assessment whether implementing the data standard for a data element will reduce the data complexity
Reduction of Data
Priority
Priority 0 = None
0 None ‐ 0%, 1
1 = Minimal Reduction
Minimal Reduction ‐ 11‐25%,
25%, 3
3 = Limited Reduction
Limited Reduction ‐ 26
26‐75%,
75%, 9
9 = Significant Reduction
Significant Reduction ‐ 76
76‐100%
100% (i.e.
(i.e.
l
Complexity
reduces interfaces)
Standardization Needed to Define if standardization is needed for a current, future, or potential project.
Priority Enable other GPSG 0 = None ‐ No need for seen, 1 = Potential Long Term Need ‐ Need foreseen within the next 12 months
initiatives 3 = Potential Short Term Need ‐ Need foreseen within the next 1‐3 months, 9 = Immediate Need ‐ Current need exists
Defines the frequency that the field is changed or maintained ‐ 9 = Never changes, 3 = Changes 1‐3 times a year ,1 =
Priority Frequency of Change
Changes Weekly, 0
Changes Weekly, 0 = Changes Daily
Changes Daily
Financial assessment or estimation that considers the total cost to implement a data standard for a data element. Includes
Effort Cost ($) resources needed to define, implement, train and maintain the data standards within the source systems.
0 = High (>$250K), 1 = Medium (>$5K and <$250K), 3 = Low (<$5K), 9 = None
People impact that quantifies the changes or additions to an organizations responsibilities or process re‐design due to data
standards.
Effort Impact to Organization
0 = High ‐
g Significantly impacts organizational operations,
g y p g p , 1 = Medium ‐ Some impact to organizational operations
p g p
3 = Low ‐ Minimally impacts organizational operations, 9 = No impact to organizational operations
Identification of the number of systems affected by the implementation of data standards. The more systems that a field is
Effort System's Impacted standardized across adds more value to that standard.
0 = None, 1 = Single (1 system), 3 = Multiple (>1 system),9 = Enterprise (JNJ)
400
300
Priority
y
200
100
0
0 LH 20 40 60 80 100 LL 120
Effort
3. Define Standard:
- Business Defines Requirement
4. Approach to Standardizing
- Consolidation (MDM)
- Procedural Control
- Harmonization Across ERPs
5. Roadmap
p
- Next Standardization Steps
- Timing / Alignment with ERP Roadmap
Current Master
Data Lifecycle
Management
M t
Processes
Excel
ERP-1
Forms
Informatica
Scanned
S
Docs
d
ERP-2 KPI /
Metrics
Data Data
Workflow &
Tool
ERP-3 Profiling Monitoring
Quality
Proactive Data View Product for Single Source Manage Profile Data
Quality Consolidation of data into Global Metadata Monitor Data Quality
values
26
Supply Chain
Global Global
Global Global
ds
Procurement Finance
Finance Planning
Project Data Need
Example
Standardized
Financial Flow Cross‐Platform
Cross Platform Financial Flow
Automation Planning,
Commodity Automation
Demand Mgmt
Codes
SAP MDM
Single source for product master data
Duplication check
Global data values
Having business partners that understand how data interacts with their processes
is critical when definingg standards for a global
g supply
pp y chain.
[ SESSION CODE:
0702