{"id":9551,"date":"2021-06-15T09:07:36","date_gmt":"2021-06-15T16:07:36","guid":{"rendered":"https:\/\/www.qad.com\/blog\/?p=9551"},"modified":"2021-06-15T09:09:04","modified_gmt":"2021-06-15T16:09:04","slug":"erp-go-live-expecting-the-unexpected","status":"publish","type":"post","link":"https:\/\/www.qad.com\/blog\/2021\/06\/erp-go-live-expecting-the-unexpected","title":{"rendered":"ERP Go-Live: Expecting the Unexpected"},"content":{"rendered":"

[vc_row][vc_column][vc_single_image image=”9552″ img_size=”full”][vc_column_text][Scene Opens in a Typical Conference Room at the Acme Manufacturing Company]<\/span><\/i><\/p>\n

The ERP team has completed the Business Process Workshops and has an agreed-upon functional scope. The various process team members have resolved configuration issues through Conference Room Pilots. End users and shop floor operators have carried out User Acceptance Testing. Next comes the dynamic data cut-over and go-live.<\/span><\/i><\/p>\n

The anticipation is palpable \u2013 a combination of thrilling excitement and held breaths \u2013 that all will go according to plan.<\/span><\/i><\/p>\n

[Suspenseful music plays in the background]<\/span><\/i><\/p>\n

This scene plays out in companies all over the world, every day. But will your ERP Go-Live be a Blockbuster or a Box Office Flop?<\/span><\/p>\n

What Does the ERP Go-Live Process Look Like?<\/span><\/h2>\n

When an ERP implementation gets to the go-live date, the teams are prepared, the implementation team has cut-over the static data and is ready to cut-over the dynamic data, users have been trained and the team has tested the system for every scenario they can think of. Whilst it\u2019s impossible to plan for every unexpected issue, QAD\u2019s <\/span>industry best practices<\/span><\/a> for go-live result in an <\/span>effective ERP implementation<\/span><\/a>.<\/span><\/p>\n

Generally, go-live is scheduled over a weekend. Users log off the old system on Friday and come back on Monday ready to use the new system. It\u2019s all about working manually between those two days for the shortest period possible, then catching up on the weekend\u2019s transaction once the new system is live.<\/span><\/p>\n

With our large global customers that operate 24\/7, we understand the strategic importance of the go-live process, which requires the joint team to maintain exceptional focus and attention during this time. With global projects, the first go-live is a chance to implement a pilot of the global core model at one major, or a wave of smaller plants. This would then be followed by more waves of roll out to other plants or businesses.<\/span><\/p>\n

A successful go-live is characterized by quantifiable statistics about resolving issues in a rapid, agile and effective manner, with good communication and escalation plans in place. All the teams are on alert to make sure the process goes as expected. Senior level management is available to deal with any escalated issues. QAD deploys a period of \u201chyper-care\u201d after go-live that lasts between one and four weeks as the project team hands over operations to the support team.<\/span><\/p>\n

A recent QAD blog post describes the <\/span>benefits of ERP go-live success<\/span><\/a>.<\/span><\/p>\n

Who\u2019s Involved in ERP Go-Live?<\/span><\/h2>\n

The ERP implementation teams from the customer and QAD come together at go-live to launch the new system. From the customer, the implementation team includes:<\/span><\/p>\n