Going Live - successfully implementing an ERP system

End User Training is a Critical Success Factor in ERP Projects.

Learn Item #25 gives an overview of what should be considered.

And here you will find a simple template how a Training Concept can look like:

All Activities carried out during the ERP Project have one Goal: the Successful Introduction of Processes, System and Data on the Day of Go Live.

The implementation period begins with business and technical activities for the conversion to the new process and system environment. Learn Item #26 introduces these activities.

And here You can find a Go Live Planner for the timing of all preparation activities:

Before the Go Live of the ERP system, several so-called integration tests should be carried out to test the system functionalities under as “real” conditions as possible.

As already discussed in the lesson “Ensuring User Acceptance”, a first integration test can be performed at the end of the preparation phase.

At the end of its rework phase, (another) integration test should be performed, which is equivalent to a simulation of the Go Live:

Learn Item #27 outlines the contents of the final system acceptance before Go Live.

The Go Live is carried out according to a Planned and Logged Procedure (see Go Live Planner).

As already mentioned in the Lesson “Go Live Preparation”, a Go Live procedure is created by the project team and approved by the management. The contents of this procedure determine the course of the Go Live.

How to proceed is explained in Learn Item #28.

During the Stabilization Phase, the ERP System Functions are Checked and Flaws are Eliminated.

For this purpose, a simplified form of the continuous improvement process can be applied, as described in Learn Item #29.

After the completion of each stabilization phase, it can make a lot of sense to organize a “lessons learned workshop” in order to learn from past mistakes for further projects or releases.

Here you can find a short video tutorial, what exactly “Lessons Learned” are and how to carry out a successful Lessons Learned Workshop:

Only when the Stabilization Phase of the Current Release is complete, a new Releasse can be rolled out.

Learn Item #30 describes, when another release can be rolled out.

After Successful Implementation of Optimized Business Processes and
a Powerful ERP System, the Final Phase is the Completion of the Project.

Learn Item #31 outlines the essential points in this regard.

After implementation of the ERP system, various services are still required for which resources must be available in the company.

The average service life of an ERP system is seven to eight years and triggers regular “dates” for process optimization when new versions are to be released or someday the current ERP system is to be replaced by a new one.