In last week’s ERP implementation tip, I wrote about the importance of creating a turn-by-turn project roadmap.
This week, I outline 5 crucial steps to building an actionable, manageable and measurable ERP implementation project plan.
Read More
In last week’s ERP implementation tip, I laid out 5 crucial steps to building an actionable, manageable and measurable project plan.
This week, I offer some guidance on how to train the core team so that it can execute the ERP implementation project plan.
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 described how to structure an intensive, 4-course program to train your core team on the selected ERP system.
Now, after having successfully completed its training, your core team is ready to restructure the business processes to accommodate the new ERP system. In this week’s tip, I offer some advice on process mapping as well as on managing the related change and risk issues of your ERP implementation project.
In last week’s ERP implementation tip, I offered some general advice about managing the business process mapping phase of your ERP implementation project.
The mapping phase is made up of four sub-phases, each constituting a separate project deliverable. Over the next four weeks, I will break down the each of these four deliverables, starting with the business scenario list, below.
In last week’s ERP implementation tip, I offered 7 keys to developing a business scenario list during the process mapping phase of your ERP implementation project.
This week, I discuss the next project deliverable in the mapping phase: completion of the draft blueprint whitepaper documents.
In last week’s ERP implementation tip, I outlined a 7-part structure to draft effective blueprint whitepapers.
This week, I explain how to build a Gaps and Issues Database to keep problems from torpedoing your ERP implementation project. The Gaps and Issues Database is the third of four deliverables that must be completed during the business process 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.
If your business is like most, it’s probably paying between 18% and 25% of its ERP licence fees annually for maintenance and support. To put this in perspective, a mid-sized business paying $300,000 in license fees would see a yearly maintenance bill of about $54,000. The big question is: “Is this business getting $54,000 of value out of its maintenance contact?”.
Canadian manufacturers and distributors are increasingly turning to ERP to help them improve their fortunes, especially in the face of low-cost foreign competition and the high Canadian dollar.
