1 / 18

Chapter 7: ERP Implementation & Training

Chapter 7: ERP Implementation & Training. User Training Maintenance. Organizational Change from ERP. Productivity decline Jobs redefined, new procedures established, ERP fine tuned, organization learns to process new information streams Productivity gain

karen-armstrong
Download Presentation

Chapter 7: ERP Implementation & Training

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Chapter 7:ERP Implementation & Training User Training Maintenance

  2. Organizational Change from ERP • Productivity decline • Jobs redefined, new procedures established, ERP fine tuned, organization learns to process new information streams • Productivity gain • Develop new skills, structural changes, process integration, add bolt-ons • Payoff • Transform organizational operations to efficient level

  3. Critical Success Factors • What the organization must do well to succeed • For IS Projects: • Top management support • Inherent in ERP • Clearly stated objectives • Inherent in ERP • End User involvement

  4. ERP Project Failure

  5. ERP Critical Success FactorsUmble et al. (2003) • Clear understanding – strategic goals • Top management commitment • Project management implementation • Great implementation team • Cope with technical issues • Organizational commitment to change • Extensive education & training • Data accuracy • Focused performance measures • Resolution of multi-site issues

  6. Implementation Strategy OptionsMarkus et al. [2000] • Business Strategy • Total local autonomy • Headquarters control – financial only • Headquarters coordination • Network coordination • Total centralization • Software Configuration • Single/multiple financial/operations • Technical Platform • Centralized/Distributed • Management Execution • Big bang/Phased rollout

  7. Implementation StrategiesMabert et al. [2000]

  8. Implementation Strategies • Big bang seemingly cheapest • Dangerous • Often makes sense in ERP if carefully planned • Phased rollout reduces risk • Especially good for large organizations

  9. Levels of IS/IT Failure • Corresponding failure • Don’t meet design objectives • Process failure • Not on time &/or not within budget • Interaction failure • System not used as designed • Expectation failure • Return not what stockholders expected

  10. Factors in ERP Implementation FailureWillcocks & Sykes [2000]

  11. Features of Successful ERP ImplementationWillcocks & Sykes [2000] • IT Leadership • Business systems thinking • Relationship building • Have needed technical platform • Ability to troubleshoot • Informed buying • Contract efforts coordinated • Suppliers held accountable • Long-term relationships with suppliers

  12. Strategies to Attain Success

  13. User Training • Focus on business processes • Not on using system • Explain why • Don’t skimp on time • Show why new system superior to old

  14. Training Delivery Formats • Web-based virtual training • Computer-based training • Video courses • Self-study books • Pop-up help screens

  15. ERP MaintenanceNah et al. (2001) • Corrective • Incorporate vendor patches, fix problems • Adaptive • Implement new features, internal customization, implement interfaces • Perfective • New versions • Preventive • Monitor response time, errors, track maintenance activities

  16. ERP System Migration • Over time, need to adopt changes • Minor modifications • Maybe system replacement • Vendors change products • WHY • The longer the time between upgrades, the harder • Easier to support a smaller number of software versions • Migrations can increase sales of seats, add-ons

  17. User Reasons to Migrate • Added functionality • Compliance with new standards • Discontinued vendor support • Customer problems in linked systems

  18. Summary • Time, cost, functionality tradeoff • In ERP, functionality the most important • Critical success factors • Top support & clear objectives inherent in ERP • Need User Involvement • Phased implementation reduces risk • but increases time • Once installed, still many pitfalls • Vendors change products • User training critical

More Related