Oracle AIM Methodology


Here i Sharing an Presentation on Oracle AIM, planning to prepare a video tutorial for the same, do share your feedback.

Oracle uses AIM (Application Implementation Methodology) to manage all of its Oracle Application implementation projects. AIM can be used for many different software implementations and not just Oracle Applications. However, the methodology is purpose built for Oracle Applications and the detailed deliverables produced are designed with the Oracle Application products in mind.
The following Oracle Applications are covered by AIM:
 Oracle Financials;
 Oracle Distribution;
 Oracle Human Resources;
 Oracle Manufacturing;
 Oracle Process Manufacturing.
AIM incorporates two things. First, it is a methodology showing what tasks are required, what order they should be completed in, and what resources are required. Secondly, it provides deliverable templates for all the tasks that require them. The combination of a methodology with a deliverable templating tool makes AIM a powerful product.
One disadvantage of AIM is that is very complicated. It involves over 200 deliverables. If you tried to use them all you would be spending 18 months implementing a 3 month project. AIM is supposed to be used by experienced project managers that pick and choose the tasks they require for each project.
Oracle’s AIM is a proven approach for implementing packaged applications. It comprises a set of well defined processes that can be managed in several ways to guide you through an application implementation project. AIM provides the tools needed to effectively and efficiently plan, conduct, and control project steps to successfully implement business solutions.
AIM defines business needs at the beginning of the project and maintains their visibility throughout the implementation. It defines internal, external, and time sensitive business events and maps each event to the responding business and system processes. Using this method, the client gains an accurate understanding of the business requirements that need to be focused on during the course of the implementation.

AIM Structure
AIM is a framework of related elements. It involves phases, processes, tasks and dependencies:
The following Oracle Applications are covered by AIM:
 A task is a unit of work, which results in a single deliverable. That deliverable may take many different forms like reports, schedules, code, or test results for example.
 A process is a closely related group of dependent tasks which meets a major objective. A process is usually based on a common discipline.
 A phase is a chronological grouping of tasks. It enables a flexible way to organise tasks, schedule major deliverables, and deliver projects.
Processes and phases are explained in more detail below.

Processes
A process in AIM represents a related set of objectives, resource skill requirements, inputs, and deliverable outputs. A task can belong to only one process. Project team members are usually assigned to a process according to their specialisation and background. A brief description of the AIM processes are given below:
1. Business Requirements Definition

Business Requirements Definition defines the business needs that must be met by the implementation project. You document business processes by identifying business events and describing the steps that respond to these events.

2. Business Requirements Mapping

Business Requirements Mapping compares the business requirements to standard application software functionality and identifies gaps that must be addressed to fully meet business needs. As gaps between requirements and functionality emerge, they are resolved by documenting workarounds, alternative solutions, application extensions, or by changing the underlying business process.

3. Application and Technical Architecture

During the Application and Technical Architecture you design an information systems architecture that reflects your business vision. Using the business and information systems requirements, this process facilitates development of a plan for deploying and configuring the hardware required for a successful implementation.

4. Module Design and Build

Module Design and Build produces custom software solutions to gaps in functionality identified during Business Requirements Mapping. Custom software solutions include program modules that must be designed, built, and tested before they can be incorporated into the system.

5. Data Conversion

Data Conversion defines the tasks and deliverables required to convert legacy data to the Oracle Applications tables. The first step of this process explicitly defines the business objects that are required for conversion and the legacy source systems that store these objects. The converted data may be needed for system testing, training, and acceptance testing as well as for production.

6. Documentation

Documentation begins with materials created early in the project. Using detailed documents from the project, the writing staff develops user and technical material that are tailored to the implementation.

7. Business System Testing

Business System Testing focuses on linking test requirements back to business requirements and securing project resources needed for testing. It supports utilising common test information including data profiles to promote testing co-ordination and to minimise duplication of test preparation and execution effort.

8. Performance Testing

Performance Testing enables you to define, build, and execute a performance test. Use the results to make decisions on whether the performance is acceptable for the business and to help propose tactical or strategic changes to address the performance quality shortfall. Performance Testing is closely related to Application and Technical Architecture; they are interdependent.

9. Training

Training prepares both users and administrators to assume on the tasks of running the new application system. It includes development of materials and methods as well as administration. Instructors and courseware developers orient their material toward roles and jobs, and not toward application modules.

10. Production Migration

Production Migration moves the company, system, and people to the new enterprise system. Following production cutover, it monitors and refines the production system and plans for the future. The Production Migration process encompasses transition to production readiness, production cutover, and post-production support.

Phases
An AIM project is conducted in phases that provide quality and control checkpoints to co-ordinate project activities that have a common goal. During a project phase, your project team will be executing tasks from several processes. A brief description of the AIM processes are given below:
1. Definition

During Definition you plan the project, review the organisation’s business objectives, and evaluate the feasibility of meeting those objectives under time, resource, and budget constraints. The emphasis is on building an achievable work plan and introducing it with guidelines on how the organisation 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.

2. Operations Analysis

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

3. Solution Design

The purpose of Solution Design is to develop the detailed designs for the optimal solutions to meet the future business requirements. During this phase, project team members create detailed narratives of process solutions developed during Operations Analysis. Supporting business requirements may require building application extensions to standard features; several alternative solutions may have been defined during Operations Analysis. The project team carefully scrutinises these solutions and chooses the most cost effective alternatives.

4. Build

The coding and testing of all customisations and other custom software including enhancements, data conversions, and interfaces is done during Build. Policy and procedure changes relating to business process modifications are developed. Business system testing is performed to validate that the developed solutions meet business requirements.
If customisations, extensions, or conversions are not required, Build is still important because it includes the business system test, which is commonly conducted as a formal conference room pilot. The business system test validates the solutions and is performed in an environment that closely resembles production.

5. Transition

During Transition, the project team deploys the finished solution into the organisation. All the elements of the implementation must come together to transition successfully to actual production. The project team trains the end users while the technical team configures the production environment and converts data. Transition ends with the cutover to production, when end users start performing their job duties using the new system.

6. Production

Production begins immediately with the production cutover. It marks the last phase of the implementation, and the beginning of the system support cycle. Included in this final phase is a series of refinements and performance measurement steps. The Information Systems (IS) personnel work quickly to stabilise the system and begin regular maintenance. They will provide the ongoing support to the organisation for the remaining life of the system. During Production, you compare actual results to project objectives. System refinement begins in a controlled manner to minimise impact to end users. Finally, you start preliminary planning of the future business and technical direction of the company.

About these ads

5 responses to “Oracle AIM Methodology

  1. Pingback: Top Referred Articles on KnowOracle | Shivmohan Purohit's Oracle Applications Blog

  2. Pingback: Blog Assignment: Estimating Costs and Allocating Resources « Eworglll's Blog

  3. Pingback: ORACLE AIM | vvemula4

  4. Pingback: Oracle AIM Methodology « Oracle Applications – Business & Technology - Specialist Software

  5. No doubt and excellent presentation on AIM methodology covering all aspects and highlighting all critical assets/documents. I believe that you have included system integration testing (testing new Oracle system integrations with legacy systems, business intelligence etc.) as part of business system testing.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s