Upload
sarvesh-yadav
View
154
Download
1
Tags:
Embed Size (px)
DESCRIPTION
Importance of ERP implementation Risk identification in ERP implementation Minimizing risk in ERP implementation
Citation preview
1
Post ImplementationA PRESENTATION BASED ON CASED STUDY OF HP’ POST IMPLEMENTATION PROCEDURE
2
Overview
About
• Importance of ERP implementation
• i* modelling in real time problems
What will you learn?
• Risk identification in ERP implementation
• Minimizing risk in ERP implementation
• Importance of IT in business
3
Phases in Post-Implementation
Go Live Readiness: Readiness Checkpoint; Assessment of Development, configuration, conversion, testing, training, communications, operations, command central, reporting and users.
ERP Training: Training for system users by trainer having experience in respective dept.
Stabilization: Preparation of subject matter excerpts. Helps users to operate in correct way.
Post Production Support: Managing daily system operation and ensuring correct working by Training , Go-live support, Data Validation, Data correction, Patches and fixes.
Knowledge Transfer: Documenting project monitoring and tracking collaboration and communication, subject matter expertise and lesson learned repository.
Implication for Management: Identify the issue and focus resources and efforts. Comprehensive knowledge transfer when consultant, staff, implementation partner staff and end-user leave.
4
Product Life cycle chart
Implementation Operation and post production
Application Management
Required Maintenance
Testing
Base personnel
Major upgrades
Resource requirement
Production
High
Med
Low
Go-Live
Backlog
New
Modules
Developm
entD
esign and gap
Project preview
5
Case Study : SAP ERP Implementation, HP
Issues Identified in failure of ERP implementation of HP
• Gap B/w training and going live : Users forgot the details to use the system
• Shortcoming in ERP testing procedure: Development of robust testing procedure and test data is essential in ERP implementation.
6
Process Flow: SAP ERP Implementation, HP
Interaction b/w project manager, project sponsors and implementation team
SD (Strategic Dependency) diagram for Process Flow
Project manager
Funds
Requirements
Approve Changes
Implementation of ERP
Business Sponsor
Implementation Team
7
Current Training
Training should be a continual and ongoing process in ERP implementation: Allows end users to understand new procedures in better way.
Providing most of the training in the essential transaction before going live very important: Prevents users from forgetting at time of use.
Informing users about where process is used and implication on overall system: They remain concerned about making mistakes.
Availability of Real-time Data: Helps understanding the system in better way and eliminates fear of making mistakes.
Examination for Users: It helps to identify the understanding progress of user hence knowing whether they are ready to go live or not.
Hierarchal training procedures: It makes problem solving easier and manager can act as mentor.
8
Current training procedure at HP
SD (Strategic Dependency) diagram for Training procedure at HP
ERP trainer and consultant
Logistics team
Project Manager
Authorization Team
Training Course Material
EmployeesCourse Material
Stationary and Transportation
Stationary and transportation
Course Material
Stationary and Transportation
Course Material
Creation of login ID
Training of ERP
Creation of Login Id
Creation of Login IDs
Training of ERP
9Recommendation to HP for training Procedure
To-and-fro relationship between various actors involved, namely, The Core Team, The Trainers, and The End Users (Employees)
Trainer’s training at beginning of implementation: Utilize the software to complete end to end business process and impart trainer to keep End-user training closely related to overall corporate strategy. Selection of Training Schedule
Management of Geographic Constraints
Establishment of training schedule
Definition of training Assessments
Scheduling proper end-user training development from your go-live date: It will prevent delay between training and going live which was major failure for HP implementation fail.
10
Continued…..
Scheduling proper end-user training development from your go-live date: It will prevent delay between training and going live i.e. incompetent training, which was major reason for failure of HP ERP implementation. Trainer should provide the training to End users in following 3 modules: General End –User training
Selected End-User Training
Effective Training Assessment
11
Problems in Testing Procedure at HP
No testing of modules were present
No robust test plan and development data
Testing was not done on the basis of real time Data and customer.
12
Testing procedure at HP
Dependency of testing coordinator, project manager, implementation team, tester and user.
SD (Strategic Dependency) diagram for Testing procedure at HP
Implementation team
Testing Coordinator
Project manager User
TesterCompletion of Implementation
Integration testing
System testing User acceptance testing
Unite Testing
Develop test cases
Test case specification
13Recommended testing procedure at HP
Tester is not only required to do unite testing , system testing and integration testing but also parallel testing and stress testing using the real data and real customers
SD (Strategic Dependency) diagram for Recommended Testing procedure at HP
Test Team Coordinator
User Acceptance
TestingUserTester
Parallel Testing
Stress Testing
Integration Testing
System testing
Unit testing
14
Risk Assessment and Management
Risks Database failure/Overload: Due to presence of many backlog orders risk of database failure is very
high. Have a backup system to handle the database overload will mitigate the risk to great extent.
Inconsistency/Incompatibility: The compatibility gap between legacy system and new system (SAP) is a big risk in any ERP implementation project. Manual updating of transactions of various modules of legacy system can make many format compatible.
15
Database failure
Confirm order
Stock check
Update Database
Payment success
Backup database User friendly
messages
Order confirmation
No Order confirmation
No DB Update
Technical snag
Order Backlog
OrderOrder module
Update Status
Efficient Service
DB..Failure
DB Failure handling
Backup DB handling
16
Inconsistency/Incompatibility
LegacySAP
DB Update
Updating of modules
Order sequencing
Time Consuming
Order priority
Manual Updating
DB Update
OrderOrder
PositionCompartment