ERP Implementation Lifecycle

ERP Implementation ERP implementation lifecycle focus on the ERP project which is carried out to make ERP up and running. ERP project is likely to go through different phases like any other project. Most often these phases do not necessarily depend on one another in a sequence, i.e. one phase might start before previous phase has finished.

ERP Implementation Also all phases that will be discussed may not be applicable in all cases. The different phases of ERP implementation are:- Pre-evaluation Screening Package Evaluation Project Planning Phase Gap-Analysis Reengineering Configuration

ERP Implementation Implementation Team Training Testing Going Live End-user training Post – implementation

Pre-evaluation Screening When the company has decided to implement the ERP the search for the convenient and suitable ERP package begins. Refers to the discussed previous lecture (“ERP Selection”) to understand the criteria used in selecting particular ERP package. Hundreds of ERP vendors exist today. All claiming to have suitable and ideal solution for your company. It is better to have a limited number of packages that aare evaluated to less than five.

Package Evaluation The objective of this phase is to find the package that is flexible enough to meet the company’s need or in other words, a software that could be customised to obtain a ‘good fit’. Once the packages to be evaluated are identified, the company needs to develop a selection criteria that will permit the evaluation of all the available packages on the same scale

Package Evaluation To choose the best system, the identification of the system that meets the business needs, and that matches the business profile. Some important points to be kept in mind while evaluating ERP software include: Functional fit with the company’s business process. Degree of integration between the various components of the ERP system.

Package Evaluation Flexibility and scalability Complexity User friendliness Quick implementation It is better to have a selection committee that will do the evaluation process.

Project Planning Phase This is the phase that designs the implementation process. Time schedules, deadlines, etc. for the project are arrived at. The project plan is developed in this phase. In this phase the details of how to go about the implementation are decided. The project plan is developed, roles are identified and responsibilities are assigned.

Project Planning Phase The organisational resources that will be used for the implementation are decided and the people who are supposed to head the implementation are identified. The implementation team members are selected and task allocation is done. The phase will decide when to begin the project, how to do it and when the project is supposed to be completed.

Project Planning Phase The phase will also plan the ‘What to do’ in case of contingencies; how to monitor the progress of the implementation; The phase will plan what control measures should be installed and what corrective actions should be taken when things get out of control. The project planning is usually done by a committee constituted by the team leaders of each implementation group headed by CIO.

Gap Analysis This is the most crucial phase for the success of the ERP implementation. Simply it is the process through which companies create a complete model of where they are now, and in which direction they want to head in the future. The trick is to design a model which both anticipates and covers any functional gaps.

Gap Analysis Some companies decide to live without a particular function. Other solutions include: Upgrade Identify the third party product that might fill the gap Design a custom program Altering the ERP source code, (the most expensive alternative; usually reserved for mission-critical installation)

Reengineering This phase involves human factors. In ERP implementation settings, reengineering has two connotations. The first connotation is the controversial one, involving the use of ERP to aid in downsizing efforts. In this case ERP is purchased with aim of reducing the number of employees.

Reengineering Every implementation will involve some change in job responsibilities as processes become more automated and efficient. However it is best to regard ERP as investment and cost-cutting measure rather than a downsizing tool. ERP should endanger business change but not endanger the jobs of thousands of employee.

Reengineering The second use of of the word ‘reengineering’ in the ERP field focus on the Business Process Reengineering (BPR) The BPR approach to an ERP implementation implies that there are two separate, but closely linked implementations on an ERP site Technical Implementation Business Process Implementation

Reengineering The BPR approach emphasises the human element of necessary change within organisations. This approach is more time consuming and has received a lot of criticism for creating a big budget and extended projects. But those who support it argue that you cannot ignore human element.

Customization This is the main functional area of ERP implementation. The Holy Grail (unwritten rule) of ERP implementation is, synchronising existing company practices with the ERP package rather than changing the source code and customising it to suit the company.

Configuration In this case business process have to be understood and mapped in such a way that the incoming ERP solutions match up with the overall goals of the company. It is not required to shut down company operations while you do a mapping process.

Configuration Instead a prototype (a simulation of the actual business processes of the company) will be used. The prototype allows for thorough testing of the “to be” model in a controlled environment. Configuring the system reveals both the strength and the weaknesses of the company business processes.

Configuration It is important for the success of ERP implementation that those configuring the system are able to explain what won’t fit into the package where the gaps in functionality occur. ERP vendors are constantly make efforts to lower configuration costs. Strategies that are currently being done include automation and pre – configuration.

Implementation Team Training Synchronously when the configuration is taking place, the implementation team is being trained. This is the phase where the company trains its employees to implement and later, run the system.

Implementation Team Training For the company to be self-sufficient in running the ERP system, it should have a good in-house team that can handle the various solutions. Thus the company must realise the importance of this phase and selects right employees with good attitude.

Testing This is the point where you are testing a real case scenarios. The test cases must be designed to specifically to find the weak links in the system and these bugs should be fixed before going live.

Going Live This is the phase where all technicalities are over, and the system is officially declared operational. In this phase all data conversion must have been done, and databases are up and running; and the prototype is fully configured and tested.

Going Live The implementation team must have tested and run the system successfully for some time. Once the system is ‘live’ the old system is removed and the new system is used for doing business.

End-User Training This is the phase where the actual users of the system will be trained on how to use the system. The employees who are going to use the new system are identified and their skills are noted. Based on their skill levels are divided into groups.

End-User Training Then each group is given training on the new system. This training is very useful as the success of the ERP system is in the hands of end-users. The end-user training is much more important and much more difficult than implementation team training since people are always reluctant to change.

End-User Training “You can have the best technology in the world, but if you don’t have a community who wants to use it and who are excited about it, then it has no purpose.” Chris Hughes Co-Founder of FaceBook.

Post – Implementation (Maintenance Mode) This is the very critical phase when the implementation phase is over. There must be enough employees who are trained to handle the problem that might occurred when the system is running. There must be technical people in the company who have the ability to enhance the system when required.

Post – Implementation (Maintenance Mode) Living with ERP systems will be different from installing them. Projects for implementing the ERP sysstems get a lot of resources and attention. However an organisation can only get the maximum value of these inputs if it successfully adopts and effectively uses the system.