Oracle A.I.M. Methodology Documentation and their uses

Enhance your project documentation process with Oracle Applications Implementation Methodology (AIM)

Having supported many software implementations including those of ERP systems, its found that the project documentation is one area which requires significant improvement. Often just finding the project documentation is difficult enough and once this frustrating process is completed you find that the documentation is inadequate. This makes it very difficult to support such implementations and any new users of such software have to rely on learning from previous users whose availability is often in question. Although poor documentation can be attributed to poor project management, in many instances the documentation is not done simply due to the effort involved and the lack of awareness as to which tools are available to facilitate the process. This article highlights how Oracle AIM advantage simplifies the documentation process and can also be used as a tool to effectively manage Oracle Applications project implementations.

AIM Overview
In my communications with a number of Oracle Applications implementer’s, its surprising to find that there is very little awareness surrounding AIM and it is very rarely used for implementations. However, I have personally found it to be very useful in managing and documenting the Oracle Applications projects. Its also believed it compares favorably and in many instances betters project management tools being used for other ERP system implementations.

AIM consists of a project management methodology together with the underlying documentation templates that support the tasks you perform within this methodology. This combination of a methodology together with documentation templates makes AIM a powerful tool for assisting implementation participants in running and managing projects successfully. The methodology can be used for any other software implementations but obviously the true value of AIM will be only be realized when it is used in conjunction with the Oracle specific document templates.

The Methodology and Structure
The methodology used is similar to traditional software project management methodologies. There are six phases within the project, these are…

  1. Definition – establish the business objectives and related requirements. Define the project work plan
  2. Operations Analysis – analyze the operations and determine fit between organizational requirements and standard application functionality.
  3. Design – develop detailed designs for the optimal solutions to meet the future business requirements.
  4. Build – physical software system build and testing
  5. Transition – developying the finished solutions into the organization
  6. Production – go LIVE!

Within these phases are the various processes – see the listed processes in below figure…

The Oracle Application Implementation Methodology (AIM) is a proven approach for implementatino of Oracle Applications across business domains. This approach has been developed by oracle in constants collaboration within its partner network.

“AIM provides tools needed to effectively and efficiently plan, conduct, and control project steps to successfully implement new business systems.”

Application Implementation Method is a proven approach for all the activities required to implement oracle applications.

There are ELEVEN PROCESSES of AIM implementation, which are as follows…

1.Business Process Architecture [BP]

This phase outlines:
+ Existing Business Practices
+ Catalog change practices
+ Leading practices
+ Future practices

  • BP.010 Define Business and Process Strategy
  • BP.020 Catalog and Analyze Potential Changes
  • BP.030 Determine Data Gathering Requirements
  • BP.040 Develop Current Process Model
  • BP.050 Review Leading Practices
  • BP.060 Develop High-Level Process Vision
  • BP.070 Develop High-Level Process Design
  • BP.080 Develop Future Process Model
  • BP.090 Document Business Procedure

2. Business Requirement Definition [RD]

This phase explains about the initial baseline questionnaire and gathering of requirements.

  • RD.010 Identify Current Financial and Operating Structure
  • RD.020 Conduct Current Business Baseline
  • RD.030 Establish Process and Mapping Summary
  • RD.040 Gather Business Volumes and Metrics
  • RD.050 Gather Business Requirements
  • RD.060 Determine Audit and Control Requirements
  • RD.070 Identify Business Availability Requirements
  • RD.080 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 Analyze High-Level Gaps
  • BR.020 Prepare mapping environment
  • BR.030 Map Business requirements
  • BR.040 Map Business Data
  • BR.050 Conduct Integration Fit Analysis
  • BR.060 Create Information Model
  • BR.070 Create Reporting Fit Analysis
  • BR.080 Test Business Solutions
  • BR.090 Confirm Integrated Business Solutions
  • BR.100 Define Applications Setup
  • BR.110 Define security Profiles

4. Application and Technical Architecture [TA]
This outlines the infrastructure requirements to implement oracle applications.

  • TA.010 Define Architecture Requirements and Strategy
  • TA.020 Identify Current Technical Architecture
  • TA.030 Develop Preliminary Conceptual Architecture
  • TA.040 Define Application Architecture
  • TA.050 Define System Availability Strategy
  • TA.060 Define Reporting and Information Access Strategy
  • TA.070 Revise Conceptual Architecture
  • TA.080 Define Application Security Architecture
  • TA.090 Define Application and Database Server Architecture
  • TA.100 Define and Propose Architecture Subsystems
  • TA.110 Define System Capacity Plan
  • TA.120 Define Platform and Network Architecture
  • TA.130 Define Application Deployment Plan
  • TA.140 Assess Performance Risks
  • TA.150 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 Define Application Extension Strategy
  • MD.020 Define and estimate application extensions
  • MD.030 Define design standards
  • MD.040 Define Build Standards
  • MD.050 Create Application extensions functional design
  • MD.060 Design Database extensions
  • MD.070 Create Application extensions technical design
  • MD.080 Review functional and Technical designs
  • MD.090 Prepare Development environment
  • MD.100 Create Database extensions
  • MD.110 Create Application extension modules
  • MD.120 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 Define data conversion requirements and strategy
  • CV.020 Define Conversion standards
  • CV.030 Prepare conversion environment
  • CV.040 Perform conversion data mapping
  • CV.050 Define manual conversion procedures
  • CV.060 Design conversion programs
  • CV.070 Prepare conversion test plans
  • CV.080 Develop conversion programs
  • CV.090 Perform conversion unit tests
  • CV.100 Perform conversion business objects
  • CV.110 Perform conversion validation tests
  • CV.120 Install conversion programs
  • CV.130 Convert and verify data

7. Documentation [DO]
Documentation prepared per module that includes user guides and implementation manuals.

  • DO.010 Define documentation requirements and strategy
  • DO.020 Define Documentation standards and procedures
  • DO.030 Prepare glossary
  • DO.040 Prepare documentation environment
  • DO.050 Produce documentation prototypes and templates
  • DO.060 Publish user reference manual
  • DO.070 Publish user guide
  • DO.080 Publish technical reference manual
  • DO.090 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 Define testing requirements and strategy
  • TE.020 Develop unit test script
  • TE.030 Develop link test script
  • TE.040 Develop system test script
  • TE.050 Develop systems integration test script
  • TE.060 Prepare testing environments
  • TE.070 Perform unit test
  • TE.080 Perform link test
  • TE.090 perform installation test
  • TE.100 Prepare key users for testing
  • TE.110 Perform system test
  • TE.120 Perform systems integration test
    TE.130 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 – Define Performance Testing Strategy
  • PT.020 – Identify Performance Test Scenarios
  • PT.030 – Identify Performance Test Transaction
  • PT.040 – Create Performance Test Scripts
  • PT.050 – Design Performance Test Transaction Programs
  • PT.060 – Design Performance Test Data
  • PT.070 – Design Test Database Load Programs
  • PT.080 – Create Performance Test Transaction Programs
  • PT.090 – Create Test Database Load Programs
  • PT.100 – Construct Performance Test Database
  • PT.110 – Prepare Performance Test Environment
  • PT.120 – 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 – Define Executive Project Strategy
  • AP.020 – Conduct Initial Project Team Orientation
  • AP.030 – Develop Project Team Learning Plan
  • AP.040 – Prepare Project Team Learning Environment
  • AP.050 – Conduct Project Team Learning Events
  • AP.060 – Develop Business Unit Managers’ Readiness Plan
  • AP.070 – Develop Project Readiness Roadmap
  • AP.080 – Develop and Execute Communication Campaign
  • AP.090 – Develop Managers’ Readiness Plan
  • AP.100 – Identify Business Process Impact on Organization
  • AP.110 – Align Human Performance Support Systems
  • AP.120 – Align Information Technology Groups
  • AP.130 – Conduct User Learning Needs Analysis
  • AP.140 – Develop User Learning Plan
  • AP.150 – Develop User Learningware
  • AP.160 – Prepare User Learning Environment
  • AP.170 – Conduct User Learning Events
  • AP.180 – Conduct Effectiveness Assessment

11. Production Migration [PM]
The process of “decommissioning” of legacy system and the usage(adoption) of oracle application system.

  • PM.010 – Define Transition Strategy
  • PM.020 – Design Production Support Infrastructure
  • PM.030 – Develop Transition and Contingency Plan
  • PM.040 – Prepare Production Environment
  • PM.050 – Set Up Applications
  • PM.060 – Implement Production Support Infrastructure
  • PM.070 – Verify Production Readiness
  • PM.080 – Begin Production
  • PM.090 – Measure System Performance
  • PM.100 – Maintain System
  • PM.110 – Refine Production System
  • PM.120 – Decommission Former Systems
  • PM.130 – Propose Future Business Direction
  • PM.140 – Propose Future Technical Direction

BrightStar Documentation team has experts who can help you with all of the above documentation needs. Please contact us at to discuss further….



Leave a Reply

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

You are commenting using your 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