Implementation Approaches

Implementation Methodology

The project should be executed via methodology that everything should be driven by “BUSINESS PROCESS”. The input to technical development team should be the catalogue of process validated by the process team. The catalogue of process should divide all processes that exist in the project scope into unique processes, sub-processes within those processes and activities within those sub-processes. The breakdown can be seen in the list of catalogue of process:

1. Project Preparation

The purpose of this phase is to provide initial planning and preparation for the Project. Although each project has its own unique objectives, scope and priorities, the steps in the phase one, help identify and plan the primary focus areas to be considered. As we prepare for implementation, there are important issues we must address at the beginning of the project, including:

• Defining project goals and objectives
• Defining project goals and objectives
• Defining implementation strategy
• Defining the overall project schedule and implementation sequence,
• Establishing the project organization and committees and
• Assigning resources
• User Training
• System Management
• Detailed Project planning for going live
• Cut over plan
• Data loading

2. Business Blueprint and Process Simplification

The purpose of this phase is to create the Business Blueprint, which is a detailed documentation of the simplified business process, which will cover all the processes documented in the AS IS phase.

Deliverables -

• Refine the original project goals and objectives
• Define the baseline scope
• Refine the overall project schedule
• Develop System Environment and Technical Blue Print
• Business Organization Structure
• Business Process Document

3. Realization

The purpose of this phase is to implement business and process requirements based on the Business Blueprint. The objectives are final implementation in the system, an overall test and the release of the system for productive (live) operation. The system is configured in two work packages, namely Baseline (major scope) and Final (remaining scope). Multiple module tests and the integration tests are carried out during this phase.

Deliverables -

• System Management
• Final Configuration and Confirmation of the system
• Creation of layout sets
• Establish Authorization Concept and Profiles
• Final Integration Test report
• End user documentation and Training Material

4. Final Preparation

The purpose of this phase is to complete the final preparation, including testing, user training, system management and cut over activities, to finalize the readiness to go live. This final preparation phase also serves to resolve all crucial open issues. Data collection and Data loading activity is done during this phase. Users are also trained during this phase. On successful completion of this phase, one is ready to run the Business on the productive system.

Deliverables -

• User Training
• System Management
• Detailed Project planning for going live
• Cut Over Plan and
• Data Loading

5. Go live and support

The purpose of this phase is to move from a pre-production environment to a live productive operation. After loading the closing balances in the system it is handed over to users for productive use. We must set up a support organization for users, not just for the initial critical days of your productive operations but also to provide long term support. During this phase, users have many questions. There must be a solid user support organization easily accessible to all users. This phase is also used to monitor system transactions and to optimize overall system performance.

Deliverables -

• Production Support Procedures
• Project Conclusion:
  ERP is not an IT tool but it is a business solution. It cuts across all business functions. Hence it brings a change for every one performing the processes covered by ERP. If the change is not communicated to the users properly it may develop a resistance, which can be detrimental to the project.