Professional Documents
Culture Documents
Erps - Life Cycle: Mohar Banerjee Biswas
Erps - Life Cycle: Mohar Banerjee Biswas
Erps - Life Cycle: Mohar Banerjee Biswas
• While the customization is taking place, implementation team is being trained, not
much on how to use the system but more on how to implement it
• Phase where company trains its employees to implement and later run the system
• Employees selected should be willing to change, learn new things, are not afraid
of technology and have good functional knowledge
TESTING
• Phase where you try to break the system using real case scenarios. Aim is to find
the weak limits and bugs
• Types of testing
• Unit testing – testing new and additional feature in isolation
• Integration testing – testing end to end business processes including customization,
enhancements and interfaces to external system
• Acceptance testing –testing done by users working with real data
• Security testing – testing user roles, access privileges, authorization and other security
measures. Find loopholes in system’s security
• Performance and stress testing – testing under normal business loads and also at huge
increase in transaction volumes. Ensure system doesn’t fail due to spikes in volume
GOING LIVE
• Phase where ERP is made available to entire org
• On technical side, work is complete, data conversion is done, databases are up and
running
• On the functional side, the prototype is fully configured and tested and ready to go
operational
• Once the system is live, the old system is removed and new system is used for
doing business
END USER TRAINING
• Actual users of the system would be given training on how to use the system
• Starts before system goes live
• Employees who are going to use the system are identified, skills noted, divided
into groups based on skills and training imparted to the groups
• Also job specific training is given to each employee
POST IMPLEMENTATION - (OPERATION & MAINTENANCE)
• Post implementation – when vendors and consultants leave, ensure employees are capable
enough to handle the system, fix any problem that might arise and enhancements if
required
• Going for upgrade whenever they are announced, the org should first analyze the costs and
benefits
• Maintenance activities will start shortly after implementation and operation
• Annual Maintenance costs should be budgeted during planning. Generally maintenance
costs is 20% of the ERP implementation costs. System upgrade can cost as much as 25-
33% of the implementation costs
POST IMPLEMENTATION - (OPERATION & MAINTENANCE)
• Inadequate Resources
• ERP is a very costly affair that requires a variety of resources – money, people,
software, hardware, etc
• Budget needs to be established based on likely costs as unlimited funding could not be
supported
• Items might be missed from the budget, Long implementation will escalate costs
Skilled and motivated personnel from the org is a critical factor
IMPLEMENTATION CHALLENGES
• Lack of Top Management Support
• Roles of top mgmt in early phases include developing understanding of the capabilities and
limitations of IT, establishing reasonable goals, exhibiting strong commitment, communication
of org strategy to all employees
• Research shows that project cancellations occur when senior mgmt delegates progress
monitoring and decisions at critical junctures of the project to technical experts
• Customization Issues
• Modify ERP to match org processes and data structures
• Modify org processes to match ERP
• Perform combination of above 2
• Ignore the problem
• Option 1 and 2 require understanding of the ERP and org processes and data structures
IMPLEMENTATION CHALLENGES
• Long Payback Period
• ROI runs to around 3 years
• Poor Communication and Co-operation
• Communication is important within project team, rest of the org, and with client
• Requires and org culture that emphasizes the value of sharing common goals over
individual pursuits and the value of trust b/w partners, employees, managers and
corporations
Thank You