AIM Application Implementation Method

AIM

Where Used: New implementations & re-implementations of Oracle’s E-Business Suite

Defining Characteristics:

• Developed exclusively for Oracle Applications
• Core & Optional tasks provide flexibility
• Projects are generally Time and Materials (Build to Suit)
• Methods –

What are They?

• Road map for getting something done
• so we don’t miss something important
• so we don’t dwell on something that is unimportant
• so we don’t reinvent the wheel
• Common language/process of communication
• Common place to identify and document forward progress and decisions
• A proven approach that can be consistently repeated
• Representative of best practicesMethods.

Benefits of Using a Method

• Well defined work plans
• Reduced learning curve
• Pre-defined guidelines, standards, and deliverable templates
• Higher quality results
• Path to successReduced risk
• Better communicationProjects delivered on time and on budget

There are eleven processes of implementation.

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

- 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

- 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

- 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 GapsBR.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

- 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.

- 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.

- 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.

- Documentation [DO]

Documentation prepared per module that includes user guides and implementation manuals.

- Business System Testing [TE]

A process of validating the setup’s and functionality by QA(functional consultant) to certify status.

- Performance Testing [PT]

Performance testing is the evaluation of transactions saving time, transaction retrieval times, workflow background process, database performance, etc

- Adoption and Learning [AP]

This phase explains the removal of the legacy system and oracle application roll out enterprise wide.

- Production Migration [PM]

The process of “decommissioning” of legacy system and the usage(adoption) of oracle application system.