Oracle AIM Methodology
Oracle Application Implementation Methodology (AIM) is a rapid
implementation methodology. This process equips project team members
with skills and tools to effectively and efficiently plan, conduct and control
project steps in order to deliver business solutions to clients.
AIM uses the following set of tools to produce quality deliverables:
Project definition
Business Process Analysis (BPA):
Business Process Mapping
Setup and Validation
Customization
Business System Testing
User Acceptance
User Training
Data Migration
Production Go-Live and Support
AIM Footprint
AIM Dimensions Sample
Overview of AIM
Applications Implementation Method (AIM) is a proven method for
implementing Oracle Applications
Method: A roadmap representative of leading practices of getting
something done.
Support for all Oracle Application Product Families
Support for all aspects of the project
Tried and tested globally
Focus on meeting requirements and ROI goals
Scaleable to meet specific project requirements
Updates are a mouse click away
Designed for quicker implementations
Project Phases
Idea
Inputs
Project management team
Project Initial Intermediate Phases Final
Phases Phase Phase
Project Charter Plan Acceptance
Management
Baseline Approval
Outputs Scope
Statement
Progress Handover
Project
Product
Deliverables
Product & Project Life
Cycles
Product
Life Cycle
Product Operations
Business Plan Idea
Project Initial Phase Intermediate Phases Final
Life Cycle Phase
Fundamental Elements of AIM
Task Task dependency
RD.020 RD.050
Define
Conduct Current Gather
Application
Business Business
Setups
Baseline Requirements
Deliverable Phase Process
BR.100
Application
Setups
Key Implementation Activities
Definition Operation Analysis Solution Design Build Transition Production
Conduct
Gather Define Perform Perform Verify
Current
Business Application System Acceptance Production
Business
Reqmts Setups Testing Testing Readiness
Baseline
RD.050 BR.100 TE.110/120 TE.130 PM.070
RD.020
Develop Develop
Map Develop
High-Level Future Begin
Business System
Process Process Production
Reqmts Test Scripts
Design Model PM.080
BR.030 TE.040
BP.070 BP.080
Define &
Develop
Estimate
Unit/Link
Appl
Test Scripts
Extensions
TE.020/030
MD.020
Appl Create
Perform
Extension Appl
OK Unit/Link
Designs Extension
Testing
MD.050/060/070 Designs
TE.070/080
MD.100/110/120
NO Yes
Goal of Each Phase
Phase Goal
Plan the project and
Definition
define requirements
Map requirements, identify
Operations Analysis gaps, and determine
conceptual architecture
Design extensions and
Solution Design identify proposed
application setups
Goal of Each Phase
Phase Goal
Create the application
Build extensions and perform
system wide tests
Migrate to the production
Transition
environment
Production Maintain and evaluate system
Definition Phase
Definition Operations Solution Build Transition Production
Analysis Design
Goal: Plan the project and define requirements
Objectives of the Definition Phase
• Define the project scope clearly (planning)
• Identify unifying vision and business objectives
• Facilitate project startup decisions
• Understand current business processes
• Review leading practices
• Design improved business processes
• Verify senior executives’ buy-in to the project
• Develop preliminary conceptual architecture
Solution Design Phase
Definition Operations Solution Build Transition Production
Analysis Design
Goal: Design extensions and identify proposed
application setups
Objectives of the Solution
Design Phase
• Produce a design that meets functional
requirements
• Document the design specifications
• Define proposed application setups and test
plans
• Design the application security architecture
• Develop designs for extensions, interfaces, and
conversion programs
• Develop test scripts
• Analyze user learning needs and develop user
learning plan
Build Phase
Definition Operations Solution Build Transition Production
Analysis Design
Goal: Create the application extensions and perform
system wide tests
Objectives of the Build Phase
Prepare the development environment
Develop, test, and accept custom software
– Application extensions
– Interface programs
– Data conversion programs
Develop and accept all documentation deliverables
Set up, test, and accept application software
Develop user learning ware and user learning
environment
Blue Cards
Transition Phase
Definition Operations Solution Build Transition Production
Analysis Design
Goal: Migrate to the production environment
Objectives of the Transition Phase
Install data conversion programs and automated
utilities
Convert and verify legacy data
Perform acceptance testing
Train user personnel
Prepare the production environment and configure
the applications
Implement the production support infrastructure
Verify production readiness
Begin to use the production system
Production Phase
Definition Operations Solution Build Transition Production
Analysis Design
Goal: Maintain and evaluate system
Objectives of the Production Phase
• Provide agreed-upon levels of user support
• Measure system performance and enhance as
required
• Maintain the production system
• Decommission former systems
• Propose and plan the future business and technical
direction
• Devote attention to post implementation issues
such as user acceptance, productivity, and human
performance support
Blue Cards
Eleven Processes
Definition Operations Solution Build Transition Production
Analysis Design
Business Process Architecture (BP)
Business Requirements Definition (RD)
Business Requirements Mapping (BR)
Application & Technical Arch. (TA)
Module Design and Build (MD)
Data Conversion (CV)
Documentation (DO)
Business System Testing (TE)
Performance Testing (PT)
Adoption and Learning (AP)
Production Migration (PM)
Goal of Each Process
Process Goal
Provide the framework for
Business Process
changing business processes with
Architecture (BP)
the implementation of applications
Business Requirements Define the business requirements of
Definition (RD) the new applications system
Create an acceptable and feasible
Business Requirements
solution that is proven and well
Mapping (BR)
documented
Application and Design an information system
Technical Architecture architecture to realize the
(TA) business vision
Goal of Each Process
Process Goal
Module Design and Design and develop customizations
Build (MD) to satisfy functionality gaps
Convert and test all necessary
Data Conversion (CV) legacy data for the operation of the
new system
Augment Oracle Applications manuals
Documentation (DO) with information about customizations
and business procedures
Business System Test the quality of all elements of
Testing (TE) the applications
Goal of Each Process
Process Goal
Define, construct, and execute a
Performance Testing (PT)
performance test
Foster acceptance of the new
Adoption and Learning (AP)
applications by all users
Migrate the organization,
Production Migration (PM) systems, and people to the new
enterprise system
Business Process Architecture (BP)
Process Definition Operations Solution Build Transition Production
Analysis Design
BP Process
Goal: Provide the framework for changing business processes
with the implementation of applications
Objectives of the Business Process
Architecture (BP) Process
• Identify the core processes within the scope of
the project
• Create a baseline to measure performance
improvements
• Document current process models
• Create a strategy for improving the business
and refining the processes
• Review leading practices
• Produce a vision and high-level designs for
the future
• Define detailed future process models P&TR
Business Requirements Definition (RD)
Process Definition Operations
Analysis
Solution
Design
Build Transition Production
BP Process
RD Process
Goal: Define the business requirements of the new
applications system
Objectives of the Business
Requirements Definition (RD) Process
• Understand the business requirements for
the new system
• Document the organizational and financial
structure of the business
• Quantify the transaction and data volumes
• Develop a set of business requirements
scenarios
• Define the audit and control requirements
• Document the reporting requirements of the
organization RD.020
Business Requirements Mapping (BR)
Process Definition Operations Solution Build Transition Production
Analysis Design
BP Process
RD Process
BR Process
Goal: Create an acceptable and feasible solution that is proven
and well documented
Objectives of the Business
Requirements Mapping (BR) Process
• Establish application fit to business requirements
• Identify gaps and propose initial alternatives and
feasible bridges to gaps
• Prove designs through demonstration
• Trace business requirements to application solutions
• Create a model that depicts information flows
• Define detailed setup parameters
Application and Technical Architecture
(TA) Process
Definition Operations Solution Build Transition Production
Analysis Design
BP Process
RD Process
BR Process
TA Process
Goal: Design an information system architecture to realize the business vision
Objectives of the Application and
Technical Architecture (TA) Process
• Define a systems framework to realize the business
and information systems vision
• Confirm compatibility of the new architecture with the
existing information systems
• Design an architecture that is compatible with the
detailed business requirements
• Design a technical architecture to support the
immediate processing capacity requirements and
provide for future growth
Module Design and Build (MD) Process
Definition Operations Solution Build Transition Production
Analysis Design
BP Process
RD Process
BR Process
TA Process
MD Process
Goal: Design and develop customizations to satisfy
functionality gaps
Objectives of the Module Design
and Build (MD) Process
• Design customizations to satisfy business needs not met
with the standard applications
• Design application extensions that you can easily
maintain and upgrade to future releases of the
applications
• Build modules according to the design specifications
• Develop automated functions and detailed instructions to
install customizations in the testing and production
environments
Blue Cards
Data Conversion (CV) Process
Definition Operations Solution Build Transition Production
Analysis Design
BP Process
RD Process
BR Process
TA Process
MD Process
CV Process
Goal: Convert and test all necessary manual data for the
operation of the new system
Objectives of the Data Conversion (CV)
Process
• Convert essential business information from manual
to the new applications
• Verify that converted data is accurate and supports
the needs of the business
Documentation (DO) Process
Definition Operations Solution Build Transition Production
Analysis Design
BP Process
RD Process
BR Process
TA Process
MD Process
CV Process
DO Process
Goal: Augment Oracle Applications manuals with information
about customizations and business procedures
Objectives of the Documentation (DO)
Process
• Produce a manual that shows the users how to use
application extensions (user reference manual)
• Produce a set of procedures for using the application in
response to day-to-day business events (user guide)
• Assemble the documents that describe the technical
details for the maintenance staff (technical reference
manual)
• Produce set of procedures for managing the system
(system management guide)
Business System Testing (TE) Process
Definition Operations Solution Build Transition Production
Analysis Design
BP Process
RD Process
BR Process
TA Process
MD Process
CV Process
DO Process
TE Process
Goal: Test the quality of all elements of the applications
Objectives of the Business System
Testing (TE) Process
• Establish an approach to testing that leverages
business requirements and processes
• Prepare test scripts early in the development and
implementation life cycle
• Build on and reuse testing materials throughout the
testing cycle
• Confirm that the business solutions meet business
requirements
• Confirm that the system complies with Century Date
standards
• Produce well-tested, high-quality systems Blue Cards
Performance Testing (PT) Process
Definition Operations Solution Build Transition Production
Analysis Design
BP Process
RD Process
BR Process
TA Process
MD Process
CV Process
DO Process
TE Process
PT Process
Goal: Define, construct, and execute a performance test
Objectives of the Performance
Testing (PT) Process
• Define, construct, and execute one or more
performance tests on the entire system or particular
components of the system
• Assess the performance characteristics of some aspect
of the new system
• Manage the performance quality in the implementation
• Mitigate performance risks
• Establish a performance test model and environment
that can be used throughout the project and into
production operation
Adoption and Learning (AP)
Process
Definition Operations Solution Build Transition Production
Analysis Design
BP Process
RD Process
BR Process
TA Process
MD Process
CV Process
DO Process
TE Process
PT Process
AP Process
Goal: Foster acceptance of the new applications by all users
Objectives of the Adoption
and Learning (AP) Process
• Align business objectives and technology capabilities
throughout the organization
• Establish a measurement system to ensure that
expectations are met
• Establish executive sponsorship and management
advocacy
• Promote open communication
• Develop teamwork within project team
• Align job roles to meet new performance expectations
• Create a user-friendly environment for learning
Core and Optional Tasks Across Phases
Definition Operations Solution Build Transition Production
Analysis Design
BP
RD
BR
TA
MD
CV
DO
TE
PT
AP
PM
Core Task Optional Task
Q&
A
Q U E S T I O N S
A N S W E R S
