• Oracle’s Application Implementation Method (AIM) is a proven approach for implementing Oracle Applications.
  • –      Support for All Oracle Application Product Families
  • –      Support for All Aspects of the Project (Project life cycle)
  • –      Focus on Meeting Requirements and Return On Investment Goals
  • –      Scalable to Meet Specific Project Requirements
  • –      Designed For Quicker Implementations

• AIM projects are conducted in phases.
  • Definition
  • Operation analysis
  • Solution
  • Build
  • Transition
  • Production
• These phases provide quality and control checkpoints to coordinate project activities that have a common goal.
• During a project phase, your project team will simultaneously be executing tasks from several processes.

Definition:

• During Definition, you plan the project, review the organization’s business objectives, understand the business processes, and evaluate the feasibility of meeting those objectives under time, resource, and budget constraints.
• The emphasis is on building an achievable workplan and introducing guidelines on how the organization will work to achieve common objectives.
•  Establishing scope early in the implementation gives the team a common reference point and an effective way to communicate. Strategies, objectives, and approaches are determined for each AIM process, providing the basis for the project plan.In addition, the Communication Campaign for the project is begun

Operations Analysis:

• During Operations Analysis, the project team develops the Business Requirements Scenarios based on deliverables from Definition that are used to assess the level of fit between the detailed business requirements and standard application functionality.
• Gaps are identified and new proposed solutions are developed.
• The analysis results in a proposal for conducting business operations under the envisioned application technical architecture.
• Proposed solutions for gaps evolve into detailed designs during the Solution Design phase

Solution Design

• The purpose of Solution Design is to develop the detailed designs for the new system to meet the future business requirements.
• During this phase, project team members create detailed Business Procedure Documentation

Build

• The coding and testing of all customizations and other custom software, including application extensions, data conversions, and interfaces, is done during the Build phase.
• Business system testing is performed to validate that the functionality meets business requirements.
• Finally, during Build the production support infrastructure is designed and a Transition and Contingency Plan is developed

Transition

• During Transition, the project team deploys the new system into the organization.
• All the elements of the implementation must come together to transition successfully to actual production.
• The project team trains the users while the technical team configures the Production Environment and converts data.

Production

• Production begins immediately with the production cutover.
• It marks the last phase of the implementation and the beginning of the system support cycle.
• A series of refinements and performance measurement steps is included in this final phase.
•  The information technology personnel work quickly to stabilize the new system and begin regular maintenance. They provide the ongoing support to the organization for the remaining life of the system.
• During Production, you compare actual results to project objectives and determine if improvements can be made.
• Controlled system refinement begins to minimize the impact to users.
• Finally, you start preliminary planning of the future business and technical direction of the company.