Congratulations ! The decision has been made, the solution is worked out so let’s implement but – Why all the prep work ? Simple answer is the undertaking of implementing an ERP system is a major project involving large amounts of resources such as people, monies and a project that is usually completed by a business every 10 years or so. Therefore, it is important that the implementation planning takes place to ensure a smooth and effective transition into the organisation.
The main task pre-implementation is having a fully defined and documented process for each function that everyone understands – believe it or not in our experience many businesses and their employees do not always have fully defined and documented processes that everyone understands and follows in the course of the business operations.
The first step in any ERP implementation for a business is to define the scope of what is to be included in the ERP. This will involve identifying:
This blog outlines:
Using what you have to hand or create new? …….. Businesses will possibly have some form of documentation describing their business – this may be a Quality Manual, Visio flows, and/or word documents. For any document to aid the implementation of your ERP solution to be effective it should show how a process links within the business organisation, the process itself and resources involved. If what is to hand does not allow for this then it may be easier all round to create new to achieve how, what and who to the processes.
One identified risk after understanding the importance of defining the business process and requirements upfront but then maintain these and expectations throughout the implementation lifecycle.
ERP systems such as Epicor can be very scalable and adaptable so it is important that the software vendor has a good understanding of how the business operates, what the business does, how a business process works, as ultimately the ERP implementation and software should fit the way a business operates.
Without any defined business process, the ERP vendor faces a problem, namely ‘what questions do we need to ask?’
One of the first steps an ERP implementation consultant from Aspera Solutions will complete is to gather the required information about how the business operates and this will usually involve a Process Review.
The process review is the mechanism by which the business and the software vendor come together to review how the business operates and what they do.
There are three key areas to this:
Often you will hear a customer say ‘the consultant never asked us about that’ or a consultant saying ‘the customer never told me that’. How often during an ERP implementation is a project phase delayed or moves off track because it becomes apparent that a process has not been fully understood or defined? Or on a wider issue, a process has not been considered at all and is critical to the business operation?
So the ‘what questions do we need to ask’ becomes ‘what do we need to know?’
Having a defined business process model outlining the key business areas and processes will assist in the requirements gathering process.
The process model can then be used as a measurable tool throughout the implementation to ensure that processes meet the business needs.
The process model below can then be used to:
Steve Watson a Lead Consultant in Aspera solutions, who has many years experience as a Business Analyst, Project Manager, Consultant with the Epicor ERP product. Working with businesses embarking on the road of implementing ERP, he has found one of the key areas that will help the success of a businesses project of implementing ERP is the prep work such as fully defined and documented processes.