erp rollout
DESCRIPTION
ERP-SAPTRANSCRIPT
Facilities M anagementEngineering Projects 1
America’s 3.0 America’s 3.0 Development ProjectDevelopment Project
Business Deployment Plan
� The SAP and Business Process Redesign started in 1997.
� Development of the Facility Management module started in April 1998.
� Development of the Project Systems module started in November1998.
� Deployments are planned by business groups:
� Rubber Products global deployment: June 2000
� Pharmaceutical deployments: July 2001 and October 2001
� Polychem global deployments: July 2003
� Crop Protection global deployments: January 2004
Facilities M anagementEngineering Projects 2
America’s 3.0 America’s 3.0 Development ProjectDevelopment Project
Project Team Structure
SUPPLY CHAIN MANAGEMENT
SUPPLY CHAIN MANAGEMENT
SAP STRATEGYSAP STRATEGY P S I P S I BASISBASISQA / QCQA / QCINFO EXCHANGEINFO EXCHANGEMETHODOLOGYMETHODOLOGY SVC MANAGEMENTSVC MANAGEMENT
ENTERPRISEENTERPRISE
APPLICATIONDEVELOPMENTAPPLICATION
DEVELOPMENTMASTER
DATAMASTER
DATA
FINANCEFINANCE
APPLICATIONDEVELOPMENTAPPLICATION
DEVELOPMENTMASTER
DATAMASTER
DATA
PROCUREMENTPROCUREMENT
APPLICATIONDEVELOPMENTAPPLICATION
DEVELOPMENTMASTER
DATAMASTER
DATA
FAMOUSFAMOUS
APPLICATIONDEVELOPMENTAPPLICATION
DEVELOPMENTMASTER
DATAMASTER
DATA
EDUCATIONEDUCATIONSECURITYSECURITYB T IB T IMASTER DATA
MASTER DATA
APPLICATIONDEVELOPMENTAPPLICATION
DEVELOPMENT
CUSTOMERCUSTOMER
APPLICATIONDEVELOPMENTAPPLICATION
DEVELOPMENTMASTER
DATAMASTER
DATA
Facilities M anagementEngineering Projects 3
America’s 3.0 America’s 3.0 Development ProjectDevelopment Project
Pharmaceutical Deployment Scope
� Create a Capital Project and a Work Breakdown Structure
� Purchase Equipment on a WBS
� Create a Capital Project and a Network / Schedule
� Purchase Equipment on a Network / Schedule
� Perform Planning, Tracking and Cost Controlling
� Implement Cross Application Time Sheets (CATS)
� Implement Standard Reporting (Planned and Actual)
� Combine a Capital and Expense Project
� Perform Collective Processing - Settlement / Closure
Facilities M anagementEngineering Projects 4
America’s 3.0 America’s 3.0 Development ProjectDevelopment Project
Deployment Plan Milestones
� Develop the BPR Process, Business Requirements and Scope
� Prepare Scripts and Configuration Documents
� Review and Revise Standards and Procedures
� Demonstrate SAP and BPR Functionality to the Customer
� Perform Data Cleansing
� Perform Unit, Integration, and User Acceptance Testing
� Train Key Users and End Users
� “Go Live” with the SAP Deployment
� Post “Go Live” Support
Facilities M anagementEngineering Projects 5
America’s 3.0 America’s 3.0 Development ProjectDevelopment Project
Scripting/ Config
Technical Objects
America’s 3.0 Development Project Timeline for PH and DS Implementation
M J J A S O N D J F M A M J J A S O N D 2000 2001
M J J A S O N D J F M A M J J A S O N D
DS UATDS End User
Training
Go-Live Week
DS Post Deployment
Support
DS Final Data Cutover
UAT Planning
DS ValidationPH Validation
PH Post Deployment
Support
PH End User Training
Go-Live Week
PH Final Data Cutover
PH UAT
UAT Planning
Development Frozen
Integration Test
Q Box Prep Data Cutoverto Q
Merge Client/ALE Test/Unit Test
Integration Test Planning
Validation
Dev Box Prep
Facilities M anagementEngineering Projects 6
America’s 3.0 America’s 3.0 Development ProjectDevelopment Project
High Level Deliverable ActivitiesDeliverable Complete
� Demonstrate business scenarios (Design Demos) 09/29/00 � Scripts written, configured and sand box tested 08/31/00� Merge client, ALE and unit test 11/17/00� Integration testing for (PH, DS) 03/02/01� User Acceptance testing (PH) 03/30/01� End user training (PH) 05/25/01� Final Production Load (PH) 05/25/01� Go Live (PH) 06/04/01� Post Deployment support (PH) 08/31/01� User Acceptance testing (DS) 07/27/01� End user training (DS) 09/21/01� Final Production Load (DS) 09/21/01� Go Live (DS) 10/01/01� Post Deployment support (DS) 12/21/01
Facilities M anagementEngineering Projects 7
America’s 3.0 America’s 3.0 Development ProjectDevelopment Project
Project Management Concepts and Tools� Initial summary and milestone schedules are developed by each
team leader using MS Power Point.� Resource and cost plans are developed using MS Excel.� Budgets for each team are established, compiled with other
team budgets and submitted for approval.� Budgets are managed using the legacy accounting system.� Each team presents its list of detail activities and reviews the list
with the other team’s list.� The total list of activities is compiled into a MS Project Plan.� Each activity represents a deliverable.� Team representatives meet to establish relationships between
activities. � The project plan is driven primarily by predecessors and
successors. � Scorecards are developed to monitor detail progress for scripts,
technical objects, test completion progress, etc.
Facilities M anagementEngineering Projects 8
America’s 3.0 America’s 3.0 Development ProjectDevelopment Project
Project Management Concepts and Tools (Continued)� The scorecard data is summarized and manually entered into
the project plan.� Scripts, configuration documents, test documents, etc. are
stored in an electronic project notebook. This is used to validate actual completion of data.
� The project plan is updated weekly. Scorecard data may be updated daily, if necessary.
� Each team develops its own detail work plan.� Personal “one on one” contact is the method used to update the
work plan.� Project progress is measured by completion of deliverable
activities. � Resource planning is managed at a team level. Teams, not
names are assigned to activities.� Actual Costs are collected and reviewed monthly using the
legacy accounting program.
Facilities M anagementEngineering Projects 9
America’s 3.0 America’s 3.0 Development ProjectDevelopment Project
Examples - MS Project Work Plan
Facilities M anagementEngineering Projects 10
America’s 3.0 America’s 3.0 Development ProjectDevelopment Project
Examples - Script and KIA ScorecardScript Scorecard
POINT 136 33 24% 44 32%Dialog 233 52% 121 52% 133 57%EF&A 439 2% 9 2% 17 4%EPP 247 72% 177 72% 177 72%Famous 163 47% 76 47% 66 40%Total 1218 22% 416 34% 437 36%
Notes: 1) Progress overall is based on the status of each scriptStatus Value DefinitionIntialized 0% Script "shell" in EPNDraft in Progress 10% Some fair amount of work has been done Documented 40% Script and confiuration doucments are written but not yet in DevelopmentDraft Complete 70% Reviewed and approved by the team Unit Tested 100% Unit testing complete and successful
2) Total Complete is based only on the number of scripts that are successfully unit tested
Key Integration Areas#
# % # % # % # % # %POINT 490 263 53.7% 97 19.8% 77 15.7% 53 10.8% 148 30.2%EF&A 29 22 75.9% 6 20.7% 0 0.0% 1 3.4% 1 3.4%EPP 24 11 45.8% 13 54.2% 0 0.0% 0 0.0% 0 0.0%Famous 19 19 100.0% 0 0.0% 0 0.0% 0 0.0% 1 5.3%IT 2 2 100.0% 0 0.0% 0 0.0% 0 0.0% 0 0.0%Total 564 317 56.2% 116 20.6% 77 13.7% 54 9.6% 150 26.6%
Planned CompleteBlank Open Testing Complete
Team Total Scripts
% Complete Actual
Total Complete Planned
% Complete Planned
Progress Overall (%)
Total Complete Actual