The go-live milestone

We will address the go-live in two aspects: namely, the technical go-live and the functional go-live.

The technical go-Live

During the technical go-live, the following aspects should be in place:

  • Synchronization of the development environment and the production environment should be finalized. A clear cut-off, in terms of functionality that is implemented and functionality that is not implemented (i.e. those that are left for a later phase or that are not critical for go-live) should be communicated to the management and users.
  • All master data and operational data required for go-live should be finalized and be ready for upload.
  • Hardware servers and software should now be in a redundant environment.
  • The network environment and settings should be finalized and in place.
  • Lock down access to the system to prevent changes being made accidentally.
  • Technical sign-off by the infrastructure management.

The functional go-live

The goal of a go-live is to ensure that it is as much of a non-event as possible. When the systems starts functioning for users it should be reflective of the processes as designed and agreed. User should have been through test scenarios and be capable of handling basic system functions:

  • Super users and system trainers should be on hand to assist with the issues that arise, and there may be a list of repetitive questions that can be clearly communicated. Compile a daily list of these questions and communicate the answers to staff where relevant.
  • A help desk should be ramped up where there are many users that can use a call centre environment.
  • The project team should meet daily to address the most pertinent issues and give feedback to the management team and users.
  • Regular management meetings with the project team should be in place so as to ensure feedback at the correct levels of the project.

A Compiere standard implementation project plan

The following briefly depicts a standard Compiere implementation project plan, which will include:

  • The Pre-implementation phase: This would include the sales, negotiation, and scoping of the requirements.
  • The Implementations phase:This phase includes the setting up of infrastructure, development, and training aspects.
  • The Go Live:This is the time of data migration from the old environment to the new, as well as users starting to use the new environment.
  • The post implementation phase: This phase involves finalizing procedures documentation, snaglists, and maintenance.
  • Project closure: This includes the aspects of agreement such as hand-over of ownership to the enterprise.

The Compiere pre-implementation project plan

This phase of the project involves pre-sales, scoping, and defining user requirements and finalizing the negotiations regarding costing and other requirements. Aspects of the project plan can be illustrated as follows:

The Compiere pre-implementation project plan

The implementation project plan

The aspects of the implementation phase will include the infrastructure environment, the initial assessment of data, development of customizations, configuring the system to user requirements, and is illustrated as follows over the next five illustrations:

  • Project plan illustration 1: Implementation plan.
The implementation project plan
  • Project Plan illustration 2: Implementation plan continues.
The implementation project plan
  • Project Plan illustration 3: Implementation plan continues.
The implementation project plan
  • Project Plan illustration 4: Implementation plan continues.
The implementation project plan
  • Project Plan illustration 5: Implementation plan continues.
The implementation project plan

The go-live milestone project plan

The go-live milestone includes infrastructure and the functional go-live of the systems as follows:

The go-live milestone project plan
..................Content has been hidden....................

You can't read the all page of ebook, please click here login for view all page.
Reset