Application Implementation Methodology (AIM)

Application Implementation Methodology (AIM)

Application implmentation methodology which is refered as AIM is developed by the oracle which provides consultants with an integrated set of Templates, Procedures, Powerpoint presentation, Spreadsheets and Project Plans for implementing the application. AIM has a defined set of project tasks, each task has some deliverable, each deliverable document has a template.Widely known implementation methodology among oracle applications community.

Application implementation methodology is a six phased implementation methodology:
1. Definition Phase
2. Operation Analysis Phase
3. Solution Design Phase
4. Build Phase
5. Transition Phase
6. Production Phase

Phases are briefly explained below, some of the tasks will ovelap between phases.

1. Definition Phase:
During this phase you work on the project plan, scoping and conduct the feasibilty study taking into account project resources like time, people and budget.

2. Operation Analysis Phase:
Main activities in this phase are requirements gathering, finalizing future business reguirements, GAP analysis and conversion startegy.

3. Solution Design:
Create designs for future business process requirements, customizations and module configurtions are finalized.

4. Build Phase:
Coding and testing of customizations, enhancements, interfaces and data conversion. In additions multiple Conference Room Pilots (CRP) testing the integrated system. At the end of the build phase you will have working, tested application for the business.

5. Transition Phase:
Deliver finished application to the client. Major activities in this phase are End-user training and support, management of change, and data conversions.

6. Production Phase:
Go-Live, production support and maintanance.

Using AIM is not mandatory but advantages of AIM overweigh the disadvantages. Some times having your own methods and templates will save time, resources and prove to be more effective. Some consulting companies widely use excel based templates even today. I use both the formats depending on the complexity of the process and volume of the setup data. It is good to have overall idea of the whole process but not everybody will use every format, you typically use the templates that are specific to your area of work.

You as a consultant is not expected to know each and every format and template.

Advantages:
- Good for complex and big projects as it reduces the risk of ERP projects.
- Builds documentation library, knowledge management, project communication made easy
and reference material.
- Readily available formats.

Disadvantages:
- Difficult to scale down the AIM process for small companies
- Cost involved with documenting every task of project tasks
- Small customers prefer custom formats to AIM formats
- AIM formats are not comletely required for simple processes.

Note:
AIM phases are similar to SDLC phases but with oracle application specific tasks and templates, so it is not completely incorrect to call it "Oracle SDLC". For detailed notes and information on formats for each deliverable refer to AIM Handbook from Oracle.