Answer the module review questions listed below. 1.Why is the readiness process
ID: 3765132 • Letter: A
Question
Answer the module review questions listed below.
1.Why is the readiness process so important to an ERP implementation?
2.What project areas need to be assessed in a readiness process?
3.What is included (and not included) during the stabilization timeframe?
4.Why is knowledge transfer important to the long-term stability of the ERP system?
5.What are the 5 areas addressed in post-production support
Part 2: You were tasked to provide training for a user group for a new ERP system that your organization is about to launch. Prepare two agendas; the first training is for the user group before the system “Go- live,” and the second agenda for the user group after “Go-Live.” What items will you cover in each training session? How would the training session be conducted? Explain your answer.
Explanation / Answer
1) If there is no readiness process to an ERP implementation that it is impossible for project for go-live with any type of assurance. It is important for the ERP implementation that readiness process start early for the go-live date and repeated in every month.
The readiness process is important to an ERP implementation
Rediness review and a detailed report needs to be available to senior management.
The process should be repeated every month to six weeks until the system is ready. This is to clarify all open issues, takss and activies required for the project team to address.
2) All project areas across the entire span of the project need to be assessed in a readiness
process. Some of the areas included are the infrastructure, development, configuration,
conversion, testing, training, communications, operation, command central, reporting,
and users.
3)
During the stablization timeframe the following is included: users getting familiar with the system and new process, monitoring the infrastructure for response time, backups are taken appropriately and sme’s are available to help many users. It doesn’t include any development of the ERP system during this phase.
4) Knowledge transfer is important to long term stability because it helps to reduce many
problems associated with moving from implementation to production. As the teams are
likely to change in different phases, especially in the Go-Live and Stabilization phases, a
smooth transfer of knowledge is critical to ensuring the smooth transition from
implementing to stabilizing the software. The first task should include a thorough
knowledge management plan to monitor the transition between phases.
5) The 5 areas addressed in post production support include: Training, beginning prior to
going live and continuing after; “Go-Live” Support, a system for when users require
assistance; Data Validation, a way to test users and ensure they are proficient in using the
system; Data Correction, to update bad data; and updating with new features.
Part 2: Firstly, the project team did not test the legacy interfaces with live data or production
data. Inadequate testing of the legacy interface came to the fore when the customer orders
could not be taken by the system. The company lost $160 million due to this issue.
Added to the above issue was the fact that the contingency plan did not work properly.
Not enough time was spent on the back-out plan.
Another major issue was the planning around training of the new system. Training was
administered before the Go-Live Date without any refresher courses just before the
implementation date. This resulted in many questions as well as ineffective usage of the
system by the users.
Related Questions
drjack9650@gmail.com
Navigate
Integrity-first tutoring: explanations and feedback only — we do not complete graded work. Learn more.