1. Oracle AIM Crisp Handout by Rangaraj Chandrasekar
"A methodology is a set of guidelines or principles that can be tailored and applied to a specific
situation." In a project environment, these guidelines might be a list of things to do. A
methodology could also be a specific approach, templates, forms, and even checklists used over
the project life cycle. Therefore that was the driving factor for bringing AIM as methodology
which was initially used by Oracle consulting, which is now most acceptable methodology for
oracle application roll out.
The AIM Advantage product gives you all the tools you need to make your implementation
successful by providing guidelines for:
*
*
*
*
*
*
*
*
*
*
*
Business Process Architecture
Business Requirements Definition
Business Requirements Mapping
Application and Technical Architecture
Module Design and Build
Data Conversion
Documentation
Business System Testing
Adoption and Learning
Performance Testing
Production Migration
AIM 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 specialization and background. Brief descriptions 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
www.erpstuff.com
1/7

2. Oracle AIM Crisp Handout by Rangaraj Chandrasekar
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
utilizing common test information including data profiles to promote testing co-ordination and to
minimize 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. User 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 course ware 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 cut over, it monitors and refines the production
system and plans for the future. The Production Migration process encompasses transition to
production readiness, production cut over, and post-production support
AIM 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: This consist of review the organization's business objectives, evaluate the
feasibility of meeting those objectives under time, resource, and budget constraints. Moreover
this can be best consider as SOW(statement of work) preparation phase.
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 scrutinizes these solutions and chooses the most cost effective
alternatives.
www.erpstuff.com
2/7

3. Oracle AIM Crisp Handout by Rangaraj Chandrasekar
4. Build: The coding and testing of all customizations 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
customizations, 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
organization. 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 in house MIS/IT
Department personnel work quickly to stabilize the system and begin regular maintenance. They
will provide the ongoing support to the organization for the remaining life of the system. During
Production, you compare actual results to project objectives.
Oracle A.I.M. Methodology encompasses a project management methodology with documentation
templates that support the life cycle of an implementation. The life cycle methodology and
documentation template allows A.I.M. to be a very useful tool for managing implementation
projects successfully. This is a depiction of the A.I.M. methodology life cycle:
Application Implementation Method is a proven approach for all the activities
required to implement oracle applications. There are eleven processes of
implementation.
1. Business Process Architecture [BP] - This phase outlines:
•
•
•
•
Existing Business Practices
Catalog change practices
Leading practices
Future practices
BP.010
BP.020
BP.030
BP.040
BP.050
BP.060
BP.070
BP.080
BP.090
Define Business and Process Strategy
Catalog and Analyze Potential Changes
Determine Data Gathering Requirements
Develop Current Process Model
Review Leading Practices
Develop High-Level Process Vision
Develop High-Level Process Design
Develop Future Process Model
Document Business Procedure
2. Business Requirement Definition [RD] - This phase explains about the
initial baseline questionnaire and gathering of requirements.
www.erpstuff.com
3/7

4. Oracle AIM Crisp Handout by Rangaraj Chandrasekar
RD.010
RD.020
RD.030
RD.040
RD.050
RD.060
RD.070
RD.080
Identify Current Financial and Operating Structure
Conduct Current Business Baseline
Establish Process and Mapping Summary
Gather Business Volumes and Metrics
Gather Business Requirements
Determine Audit and Control Requirements
Identify Business Availability Requirements
Identify Reporting and Information Access Requirements
3. Business Requirement Mapping [BR] - In this phase the requirements of
business are matched with the standard functionality of the oracle applications.
BR.010
BR.020
BR.030
BR.040
BR.050
BR.060
BR.070
BR.080
BR.090
BR.100
BR.110
Analyze High-Level Gaps
Prepare mapping environment
Map Business requirements
Map Business Data
Conduct Integration Fit Analysis
Create Information Model
Create Reporting Fit Analysis
Test Business Solutions
Confirm Integrated Business Solutions
Define Applications Setup
Define security Profiles
4. Application and Technical Architecture [TA] - This outlines the
infrastructure requirements to implement oracle applications.
TA.010
TA.020
TA.030
TA.040
TA.050
TA.060
TA.070
TA.080
TA.090
TA.100
TA.110
TA.120
TA.130
TA.140
TA.150
Define Architecture Requirements and Strategy
Identify Current Technical Architecture
Develop Preliminary Conceptual Architecture
Define Application Architecture
Define System Availability Strategy
Define Reporting and Information Access Strategy
Revise Conceptual Architecture
Define Application Security Architecture
Define Application and Database Server Architecture
Define and Propose Architecture Subsystems
Define System Capacity Plan
Define Platform and Network Architecture
Define Application Deployment Plan
Assess Performance Risks
Define System Management Procedures
5. Build and Module Design [MD] - This phase emphasizes the development
of new functionality (customization) required by the client. It mainly details how
to design the required forms, database and reports.
MD.010
MD.020
MD.030
MD.040
Define
Define
Define
Define
www.erpstuff.com
Application Extension Strategy
and estimate application extensions
design standards
Build Standards
4/7

5. Oracle AIM Crisp Handout by Rangaraj Chandrasekar
MD.050
MD.060
MD.070
MD.080
MD.090
MD.100
MD.110
MD.120
Create Application extensions functional design
Design Database extensions
Create Application extensions technical design
Review functional and Technical designs
Prepare Development environment
Create Database extensions
Create Application extension modules
Create Installation routines
6. Data Conversion [CV] - Data Conversion is the process of converting or
transferring the data from legacy system to oracle applications. Ex. Transferring
customer records from the legacy to the Customer Master.
CV.010
CV.020
CV.030
CV.040
CV.050
CV.060
CV.070
CV.080
CV.090
CV.100
CV.110
CV.120
CV.130
Define data conversion requirements and strategy
Define Conversion standards
Prepare conversion environment
Perform conversion data mapping
Define manual conversion procedures
Design conversion programs
Prepare conversion test plans
Develop conversion programs
Perform conversion unit tests
Perform conversion business objects
Perform conversion validation tests
Install conversion programs
Convert and verify data
7. Documentation [DO] - Documentation prepared per module that includes
user guides and implementation manuals.
DO.010
DO.020
DO.030
DO.040
DO.050
DO.060
DO.070
DO.080
DO.090
Define documentation requirements and strategy
Define Documentation standards and procedures
Prepare glossary
Prepare documentation environment
Produce documentation prototypes and templates
Publish user reference manual
Publish user guide
Publish technical reference manual
Publish system management guide
8. Business System Testing [TE] - A process of validating the setup’s and
functionality by QA (functional consultant) to certify status.
TE.010
TE.020
TE.030
TE.040
TE.050
Define testing requirements and strategy
Develop unit test script
Develop link test script
Develop system test script
Develop systems integration test script
www.erpstuff.com
5/7

6. Oracle AIM Crisp Handout by Rangaraj Chandrasekar
TE.060
TE.070
TE.080
TE.090
TE.100
TE.110
TE.120
TE.130
Prepare testing environments
Perform unit test
Perform link test
perform installation test
Prepare key users for testing
Perform system test
Perform systems integration test
Perform Acceptance test
9. Performance Testing [PT] - Performance testing is the evaluation of
transactions saving time, transaction retrieval times, workflow background
process, database performance, etc
PT.010
PT.020
PT.030
PT.040
PT.050
PT.060
PT.070
PT.080
PT.090
PT.100
PT.110
PT.120
-
Define Performance Testing Strategy
Identify Performance Test Scenarios
Identify Performance Test Transaction
Create Performance Test Scripts
Design Performance Test Transaction Programs
Design Performance Test Data
Design Test Database Load Programs
Create Performance Test Transaction Programs
Create Test Database Load Programs
Construct Performance Test Database
Prepare Performance Test Environment
Execute Performance Test
10. Adoption and Learning [AP] - This phase explains the removal of the
legacy system and oracle application roll out enterprise wide.
AP.010
AP.020
AP.030
AP.040
AP.050
AP.060
AP.070
AP.080
AP.090
AP.100
AP.110
AP.120
AP.130
AP.140
AP.150
AP.160
AP.170
AP.180
-
Define Executive Project Strategy
Conduct Initial Project Team Orientation
Develop Project Team Learning Plan
Prepare Project Team Learning Environment
Conduct Project Team Learning Events
Develop Business Unit Managers’ Readiness Plan
Develop Project Readiness Roadmap
Develop and Execute Communication Campaign
Develop Managers’ Readiness Plan
Identify Business Process Impact on Organization
Align Human Performance Support Systems
Align Information Technology Groups
Conduct User Learning Needs Analysis
Develop User Learning Plan
Develop User Learning ware
Prepare User Learning Environment
Conduct User Learning Events
Conduct Effectiveness Assessment
11. Production Migration [PM] - The process of “decommissioning” of legacy
system and the usage (adoption) of oracle application system.
www.erpstuff.com
6/7

7. Oracle AIM Crisp Handout by Rangaraj Chandrasekar
PM.010
PM.020
PM.030
PM.040
PM.050
PM.060
PM.070
PM.080
PM.090
PM.100
PM.110
PM.120
PM.130
PM.140
-
Define Transition Strategy
Design Production Support Infrastructure
Develop Transition and Contingency Plan
Prepare Production Environment
Set Up Applications
Implement Production Support Infrastructure
Verify Production Readiness
Begin Production
Measure System Performance
Maintain System
Refine Production System
Decommission Former Systems
Propose Future Business Direction
Propose Future Technical Direction
Please send your feedback at admin@erpstuff.com
www.erpstuff.com
7/7