MSG Team's other articles

12363 The Argument against Planned Obsolescence

Planned obsolescence is often considered to be a part of the capitalist ideology. The supposed logic behind planned obsolescence is that capitalist companies put inferior components in their products. As a result, these products do not last as long. Since the products break down sooner, the customers are forced to buy new products. Opponents of […]

9577 How Chinese Corporations Are Going Global?

China has seen rapid development in the past two or three decades. It has become the export powerhouse of the world. However, Chinese companies were always considered to be the cheap imitators. Chinese companies were earlier contractors for American and European countries who provided cheap labor to assemble their high tech products. However, this has […]

11983 Why India Inc. Must Prepare for a Perfect Storm of Converging Crises

The Perfect Storm of Converging Crises: Covid 19, Depressed Economy, and Social Unrest India is staring at a Perfect Storm of converging crises including a depressed economy that is further hit by the Coronavirus Shock, the Pandemic itself that needs management and handling, and social unrest stemming from ham handed handling of the pandemic as […]

10514 Operations Scheduling and Workplace Planning

Introduction Scheduling and workplace planning is the final step in operation planning and design. Operation’s scheduling and workplace planning is implemented during transformation of input to output. Scheduling deals with production of required quantity of product within the required time frame. Workplace planning deals with allocation of resources with priority to work job with first […]

12555 Business Continuity Management Planning around the World

In these turbulent times when the business environment is characterized by uncertainty and fraught with risks of all kinds, companies have to plan for contingencies and emergencies. The disaster preparedness that companies exhibit goes a long way in making them adjust to the changing circumstances when disaster strikes. For instance, companies may have to deal […]

Search with tags

  • No tags available.

Like any other project, ERP implementation goes through various interconnected phases. These phases may be sequential but at occasions overlap. Normally, every phase has entry criteria, which needs to be fulfilled before the commencement of the phase. A phase is deemed to have completed when pre-determined deliverables are achieved.

Various phases of ERP implementation, for a typical ERP project, are mentioned below:

  1. Project Establishment

    Project Establishment will comprise of the following activities:

    • Mobilization.
    • Project teams formation
    • Project plan detailing and fine tuning

    For a successful implementation, several types of skills are required. To ensure that the requisite expertises are available to the project, different teams are formed, consisting of members from the organization and vendor.

    • Project board
    • Competence center team, mostly represented by IT personnel of the organization.
    • Key users team.
    • Consultants’ team.
    • Project Implementation Committee.
    Entry Criteria
    • Vendor Project Team on site.
    • Organizations implementation team tentatively identified.
    Deliverables
    • Project Administration Plan.
    • Project standards document.
    • Project board formation.
    • Project Implementation Committee formation.
    • Competency Centre Team formation.
    • Key Users Team formation.
    • Delivery and Installation of vanilla ERP Application.
  2. Procedure Development

    In this phase, key users and competence center team map the existing functional processes with the functions available in the vanilla ERP application, in conjunction with the vendor team. The following activities will occur in an iterative manner.

    • Process mapping
    • Gap detection
    • Work-around identification
    • Organizational impact analysis
    Deliverables
    • Business Model through flow chart.
    • Customization Design Specification document for identified modifications.
    • Draft Procedure Manual
    • Acceptance Test Plan and Data
  3. Application Software Customisation

    This phase includes program development for all modules using the Customization Design Specification Document, unit testing and system testing of all modules. The individual programs will be unit tested, based on test plans developed by the vendor. This phase may be carried out at offshore.

    Next, the developed and unit tested application software will be system tested during this phase. The system testing will be based on the acceptance test plan and test data provided by the organization. Thereafter it will be installed on the Designated Computed System.

    Entry Criteria
    • Acceptance Test Plan and Test Data
    • Customization Design Specification Document for identified modifications
    Deliverables

    Customized unit and system tested application software.

  4. Acceptance Testing

    The focus of user acceptance testing is to exhibit that the system works. From the user’s point of view, acceptance testing is the final quality control procedure to determine whether the software product is performing as expected.

    Entry Criteria

    Availability of customized unit and system tested application.

    Deliverables
    • Tested Application Software
    • Updated procedure manual
  5. End User Training

    All identified end users will be trained in the specific functions they are required to work. The training will be conducted by vendor.

    Entry Criteria
    • Tested Application Software
    • Updated procedure manual
    Deliverables
    • End users trained as per training plan
  6. Conference room trial

    This phase deals on the simulation of the actual business environment. The following activities will occur iteratively during this phase:

    • Identification and entry of representative data
    • Simulation of the business model
    • Business Model enhancement
    • Finalization of procedure manual

    As the team reviews the data model, the business model that is prepared in the Procedure Development stage may undergo some changes.

    Entry Criteria
    • Tested Application Software
    • Updated procedure manual
    Deliverables
    • Final Procedure Manual
    • Final Business Model
  7. Data Loading

    This is the migration phase where data from existing manual/legacy operations are transferred to System’s database using interface programs or utilities available within the ERP package. The following activities will occur:

    • Data conversion & loading
    • Establishment of Access Rights and Passwords
    Entry Criteria
    • Final Procedure Manual.
    • Final Business Model
    Deliverables
    • Data Loading Completed
  8. Live trial

    Once the Final Business Model is ready and database is loaded, the system is ready to go live. This phase will allow users to work on the application software with real time data.

    Entry Criteria
    • Data Loading Completed
    • Trained End Users.
    Deliverables
    • Live Trial completed

Article Written by

MSG Team

An insightful writer passionate about sharing expertise, trends, and tips, dedicated to inspiring and informing readers through engaging and thoughtful content.

Leave a reply

Your email address will not be published. Required fields are marked *

Related Articles

Cost Estimate and Accounting in ERP

MSG Team

Configuration Control and Setting Up of Base in ERP System

MSG Team

Change and Risk Management in ERP Implementation

MSG Team