AIM methodology

What are the main distinctive elements of AIM. Below is a brief summary of the AIM methodology that I had the opportunity to use during the implementation of the Oracle eBS system. I also know that IFS uses similar AIM assumptions.
The main elements of Application Implementation Methodology [[AIM]] are:

  • focus on change management and improvement of business processes;
  • a modular approach allowing faster gaining benefits from a working solution;
  • customer support implemented by IFS throughout the entire life cycle of the solution;
  • the possibility of basing on generic models when modeling business processes;
  • implementation philosophy in the form of “implementation packages”, allowing for effective quality control and timeliness.

The system implementation can be modular. Each module implementation project is carried out in three phases:

1. Implementation analysis

  • defining the implementation goals;
  • defining business processes and focusing on critical processes;
  • identification of needs regarding processes and organization, applications and information technology;
  • detailed planning of the next phase.

The result: a ready solution concept.

2. Implementation

  • modeling of new business processes and work procedures;
  • user training;
  • preparation of an application supporting new business processes;
  • providing modifications, integration and data migration;
  • configuration of the system platform and database.

The result: a solution consisting of applications supporting prepared business processes.

3. Starting up

  • verification of models of business processes and work procedures;
  • training of end users;
  • data migration;
  • preparation for care after start-up;
  • system switching;
  • review of the implementation results.

The result: starting work in the new system.