In last week’s ERP implementation tip, we laid out the key components of an actionable data migration plan.
This week, we circle back and cover customizations, personalizations and interface projects. These projects are intended to extend the functionality of the ERP or IT software into areas that are not covered by out-of-the-box functionality.
In last week’s ERP implementation tip, we laid out the key concepts of data migration. This week, we breakdown the four key components of an actionable data migration plan.
In last week’s ERP implementation tip, we discussed the end-user training phase – the phase during which the implementing organization’s employees are taught how to incorporate the new system into their daily work routines.
We now start our discussion of data migration. Given the importance of this topic, it will span two tips. In this week’s tip, we cover the key concepts. In next week’s tip, we will explain how to tie these various concepts together into an actionable migration plan.
In last week’s ERP implementation tip, we discussed the integrated pilot phase – the third of three systems testing phases in an ERP implementation project.
With the testing complete, the implementing organization suddenly finds itself under-the-gun to make sure that its troops are ready to work in the new operating environment.
In this week’s tip, we discuss the end-user training phase – the phase during which the employees are taught how to incorporate the new system into their daily work routines.
In last week’s ERP implementation tip, we covered the Departmental Pilot phase – where the teams tested all business processes in the new IT system. In the tip previous to that, we discussed the Conference Room Pilot phase – the first round of system tests where only a sampling of the business processes were tested.
In this week’s tip, I walk you through the final round of ERP systems tests before cutover: the Integrated Pilot testing phase.
In last week’s ERP implementation tip, we covered the Conference Room Piloting (CRP) phase, where the core team tests the 80% business scenarios and scripts in the ERP system.
In this week’s tip, I walk you through the second round of ERP implementation systems tests: the departmental pilot (DP) phase.
In last week’s ERP implementation tip, I offered 4 tips to help you manage the walkthrough presentations in your ERP implementation project.
In this week’s tip, I walk you through the first in a series of ERP systems tests: the conference room pilot (CRP).
In my previous ERP implementation tip, I broke down the six key elements of a change management plan, including the training plan.
This week, I discuss the eighth ERP implementation project deliverable: the walkthrough presentation.
In my previous ERP implementation tip, I identified potential pockets of change resistance and discussed how an effective change management plan can drive ERP implementation success and diffuse potentially fatal project resistance.
This week, I break down six key elements of a change management plan, including the training strategy. The change management plan completes the fourth and final deliverable in the project mapping phase.
In last week’s ERP implementation tip, I explained how to build a Gaps and Issues Database to keep ERP problems from torpedoing your project. This week and next, I delve into the fourth and final deliverable of the project mapping phase: the change management plan.
Agtech providers of precision agriculture and robotic solutions providers are transforming agriculture and farming operations. Pemeco helps its agricultural technology clients implement standard, scalable business processes to drive their high-growth businesses.
