ERP News

Methodology to bridge information gap in ERP Implementation

Adopting the right implementation methodology is a bigger challenge than selecting the right ERP solution. A right methodology can bridge the information gap effectively in an ERP implementation. Mainly advised methodology covers
444 0

Let’s Start With the Methodology to bridge information gap in ERP Implementation

Adopting the right implementation methodology is a bigger challenge than selecting the right ERP solution. A right methodology can bridge the information gap effectively in an ERP implementation. Mainly advised methodology covers

1 – Project Preparation – Identifying information and resources. This is the first phase to collect all the necessary information needed for the implementation. This includes :

  • Seeking senior-level management/stakeholder support
  • Listing and defining clear project objectives
  • Prepare a stakeholder plan, define roles
  • Design the communication model
  • Design an efficient decision-making process
  • Building a qualified and capable project team.

The better the foundation and clear objectives are defined the lesser the information gap. Basically, the objective of this phase is also to define the scope of the project

2 – Business Requirement

In this step, the process owners and ERP consultants lead meet to discuss and document the requirement. Depending upon the size of the Implementation workshops on business requirement runs for 3–4 months in all the areas chosen for ERP for example Sales, Purchase, Finance, CRM etc. The sign off at the end of each document freezes the requirement for each module. This is a very important step as all the new requirements that arise in later phases is termed as a GAP and higher gaps affect the scope and budget of the project. Hence it is important to clearly understand and document the requirements for months in workshops.

2 – Business Blueprint

Also, known as general design, this is the next step after all the business requirements are signed off. The first step in doing the blueprint is to document all the processes and prepare a workflow for example. In this phase you also explain what’s covered in the standard solution or what will be delivered as part of a bespoke functionality. A bespoke functionality is something that does not come as a part of standard product offering and needs to be developed using the programming language that comes with the product. Again, this step needs to be signed off before moving to next.

3 – Realisation

The purpose of this phase is to implement business and process requirements based on the Business Blueprint defined in the previous step. To ensure all the processes documented in previous two steps the objectives of realization phase does the baseline config and prepares the system in the development environment.

4 – Configuration and Testing (System, Integration, and UAT)

Once the baseline config is done, the system gets ready for detailed config including building any bespoke functionality. You can split this phase into different steps, the key components are built, testing and getting user acceptance. Once the solution is ready the same people who provided the requirements for the first step finally check the solution and ensure all the requirements are met. UAT is termed as User Acceptance Test and it can result in raising of defects or change request if all the requirements are not met. Defect and change request is very normal in any ERP Implementation projects. Through this, we are reducing the gaps. UAT is the last step before moving on to the final preparation and then go-live

5 – Final Preparation

There are other steps which may not be in the scope of this question, but cutover activities, data migration etc are done in the Final prep.

6 – Go live and Early Life Support

And finally, once all the steps are signed off (with lots of ups and downs generally) solution goes live. A date is defined for Go Live during the 1st phase and entire project plan is prepared to ensure the deadline is met.

So in summary, if the foundation is rightly set, there will be lesser gaps and right methodology can help you lessen your gaps.

 

This Article (Methodology to bridge information gap in ERP Implementation) was written by Faraz Mohsin(CEO, ERPINNEWS)

EIN ORIGINAL

Leave A Reply

Your email address will not be published.

*

code