Minimizing business disruptions during an SAP upgrade or implementation
During software implementations and upgrades, system disruptions usually take place in the first 60 days of the go-live. Aside from the negative impact such disruptions have on operations, now time must be spent on the manual fix that's required. How can one prevent such disruptions? Is it a simple matter of performing best practices?
In this podcast, Eric Kimberling, president and founder of the ERP consulting firm Panorama Consulting Group, discusses how to prevent such disruptions during SAP ERP upgrades and implementations, as well as how to deal with them if they do occur.
Eric has 15 years of ERP consulting experience at large firms including Pricewaterhouse Coopers. He is knowledgeable in ERP software selection, ERP organizational change and ERP implementation project management. Panorama works with mid-sized manufacturing, distribution, consumer product and pharmaceutical companies in North America and Europe.
| How can you minimize disruptions during upgrades or implementations?|| |
00:57 – Are disruptions a common problem with the most recent round of upgrades to ECC 6.0?
2:07 -- What are the most common system disruptions during an SAP upgrade?
2:58 – How can IT avoid such disruptions?
4:18 – Can you elaborate on one of your recent studies, which showed that SAP implementations cause the least amount of disruption to business versus competitors such as Oracle and Microsoft?
6:10 -- What products can alleviate these "disruption headaches" when they occur?
| For more on SAP ERP upgrades|| |
Read 10 critical steps when undertaking an SAP ERP upgrade
Read some of the SAP ERP upgrade lessons learned from Lockheed Martin
Learn about an SAP FI/CO consultant's role during upgrade from SAP R/3 to ECC 6.0
Learn whether you should upgrade to ECC 6.0 from SAP ECC 4.7
This was first published in April 2009