AIM Methodology

GE ConfidentialTCS Internal

balan babuOracle CoE – Seepz ODC30-6-2004


What Is AIM?

Oracle’s Application Implementation Method(AIM) is a proven approach for implementingOracle Applications.


Oracle Application Implementation Methodology

Processes Phases


PHASES…


Where this fits?


Phase I - Definition

During the definition phase, the business and the system requirements are analysed. Based on the future business model, the technical architecture is decided.

Deliverables:

"Current Business Baseline" (RD020) for signoff of Phase I


Phase II - Operation Analysis

Based on the business requirements from the phase I, the project team develop business scenarios to assess the level of fit between the business requirements & the standard functionality available. Gaps are identified & corresponding solutions are developed.

Deliverables:

Signoff documents for phase II --

"Business Requirement Definition“ – RD050

"Business Requirement Mapping“ – BR030

"Customisation Plan“


Phase III - Solution Design

In this phase, detailed designs for the optimal solutions to meet the business requirements will be done. Detailed narratives for the process solutions developed in the analysis phase are also created by the process team.

Deliverables:

Signoff documents for phase III

Create Application Extensions Functional Design- MD.050

Create Application Extensions Technical Design- MD.070


Phase IV - Build

The testing of all customisations, data conversions and interfaces is done in this phase. Policies & procedures related to the business process modifications are also developed. The business system testing & performance testing of the system is also done in this phase.

Deliverables:

Signoff documents for phase IV

" Conference Room Pilot Testing Signoff "

" User Acceptance Test Signoff "


Phase V - Transition

The finished solution is deployed in this phase. The project team trains the end users & the technical team configures the production environment & converts the data.

Deliverables:

Signoff documents for phase V

"Training Schedule"

" User Manual"


Phase VI - Production

This phase starts when the users start performing the transactions in the new system. The activities included in this phase are the refinements in the processes & the performance measurement steps.

Deliverables:

ins Direction Recommendations

" End Report " for sign off of Phase VI .


Processes…


Business Process Architecture (BP)

- Understanding of the organization’s business processes- Determine the change required and to design the new or changed business processes.

Documents:

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


Business Requirement Definition (RD)

Business Requirements Definition defines the business needs that mustbe met by the implementation project.The business processes are documented after identifying thebusiness events and detailing the process steps that respond tothe business events.

Documents:

RD.010 - Identify Current Financial and Operating Structure (Core)RD.020 - Conduct Current Business Baseline (Core)RD.030 - Establish Process and Mapping Summary (Optional)RD.040 - Gather Business Volumes and Metrics (Core)RD.050 - Gather Business Requirements (Core) RD.060 - Determine Audit and Control Requirements (Core) RD.070 - Identify Business Availability Requirements (Core)RD.080 - Identify Reporting and Information Access Requirements (Core)


Business Requirement Mapping (BR)

The business requirements stated would be compared with thesoftware standard functionality and gaps that must be addressedto meet the business requirements are identified. These gapswill be resolved by documenting the workarounds or by changingthe underlying business process. However, if a customisationis required, the efforts for the same will be estimated separately.The work may be started after sign off on the businessrequirement definition.

Documents:

BR.010 - Analyze High-Level Gaps (Core)BR.020 - Prepare Mapping Environment (Core)BR.030 - Map Business Requirements (Core)BR.040 - Map Business Data (Core)


Business Requirement Mapping (BR)

Documents:

BR.050 - Conduct Integration Fit Analysis (Optional)BR.060 - Create Information Model (Optional)BR.070 - Conduct Reporting Fit Analysis (Core) BR.080 - Test Business Solutions (Optional)BR.090 - Confirm Integrated Business Solutions (Core) BR.100 - Define Application Setups (Core) BR.110 - Design Security Profiles (Core)


Application and Technical Architecture (TA)

A plan will be made for deploying and configuring the informationsystem architecture to meet the defined business requirements.This work will be done along with the business requirementdefinition and mapping process.

Documents:TA.010 - Define Architecture Requirements and Strategy (Core) TA.020 - Identify Current Technical Architecture (Optional)TA.030 - Develop Preliminary Conceptual Architecture (Optional)TA.040 - Define Application Architecture (Optional) TA.050 - Define System Availability Strategy (Core)


Application and Technical Architecture (TA)

Documents:

TA.060 - Define Reporting and Information Access Strategy (Optional)TA.070 - Revise Conceptual Architecture (Optional)TA.080 - Define Application Security Architecture (Optional)TA.090 - Define Application and Database Server Architecture (Optional)TA.100 - Define and Propose Architecture Subsystems (Optional) TA.110 - Define System Capacity Plan (Core)TA.120 - Define Platform and Network Architecture (Core)TA.130 - Define Application Deployment Plan (Optional) TA.140 - Assess Performance Risks (Core)TA.150 - Define System Management Procedures (Core)


Module Design and Build (MD)

Custom software solutions like forms, reports; triggers, and alerts will be built for gaps in functionality identified in BusinessRequirement Mapping.

Documents:

MD.010 - Define Application Extension Strategy (Optional)MD.020 - Define and Estimate Application Extensions (Optional)MD.030 - Define Design Standards (Optional) MD.040 - Define Build Standards (Optional)


Module Design and Build (MD)

Documents:

MD.050 - Create Application Extensions Functional Design (Optional) MD.060 - Design Database Extensions (Optional)MD.070 - Create Application Extensions Technical Design (Optional) MD.080 - Review Functional and Technical Designs (Optional) MD.090 - Prepare Development Environment (Optional)MD.100 - Create Database Extensions (Optional) MD.110 - Create Application Extension Modules (Optional)MD.120 - Create Installation Routines (Optional)


Data Conversion (CV)

A high-level data conversion plan will be developed during analysisstage of the project.Work on analysis, design, construction, testing, integration andimplementation of data conversion process, manual and/orautomated, as defined by the business system requirements will betaken up subsequently.Identification of interface points with the legacy system, if any,will be done during analysis stage of the project. Work on analysis,design, construction, testing, integration and implementation of interfaces will be taken up subsequently.

Documents:CV.010 - Define Data Conversion Requirements and Strategy (Optional) CV.020 - Define Conversion Standards (Optional)


Data Conversion (CV)

Documents:

CV.030 - Prepare Conversion Environment (Optional) CV.040 - Perform Conversion Data Mapping (Optional)CV.050 - Define Manual Conversion Procedures (Optional)CV.060 - Design Conversion Programs (Optional)CV.070 - Prepare Conversion Test Plans (Optional)CV.080 - Develop Conversion Programs (Optional) CV.090 - Perform Conversion Unit Tests (Optional)CV.100 - Perform Conversion Business Object Tests (Optional)CV.110 - Perform Conversion Validation Tests (Optional)CV.120 - Install Conversion Programs (Optional) CV.130 - Convert and Verify Data (Optional)


Documentation (DO)

A detailed user and technical documentation tailored to theimplementation will be prepared by the core team for all the abovesaid processes.

Documents:DO.010 - Define Documentation Requirements and Strategy (Core) DO.020 - Define Documentation Standards and Procedures (Optional)DO.030 - Prepare Glossary (Core)DO.040 - Prepare Documentation Environment (Optional) DO.050 - Produce Documentation Prototypes and Templates (Optional) DO.060 - Publish User Reference Manual (Optional)DO.070 - Publish User Guide (Optional) DO.080 - Publish Technical Reference Manual (Optional)DO.090 - Publish System Management Guide (Optional)


Business System Testing (TE)

Configuration of some selected business scenarios will be doneas per the business requirements and demonstrated tobusiness users in a Conference Room Pilot (CRP) session.Minor gaps may be identified during CRP session, which shall beaddressed by required change in configuration and final CRP.

Documents:

TE.010 - Define Testing Requirements and Strategy (Core) TE.020 - Develop Unit Test Script (Optional)TE.030 - Develop Link Test Script (Optional)TE.040 - Develop System Test Script (Core)TE.050 - Develop Systems Integration Test Script (Optional)


Business System Testing (TE)

Documents:

TE.060 - Prepare Testing Environments (Core)TE.070 - Perform Unit Test (Optional)TE.080 - Perform Link Test (Optional)TE.090 - Perform Installation Test (Optional) TE.100 - Prepare Key Users for Testing (Core) TE.110 - Perform System Test (Core)TE.120 - Perform Systems Integration Test (Optional)TE.130 - Perform Acceptance Test (Core)


Performance Testing (PT)

Integrated business cycle testing will be conducted to verify the technical and functional performance of the system.Any architecture or functional changes if required will be done tomeet the requirements.

Documents:

PT.010 - Define Performance Testing Strategy (Optional) PT.020 - Identify Performance Test Scenarios (Optional) PT.030 - Identify Performance Test Transaction Models (Optional) PT.040 - Create Performance Test Scripts (Optional) PT.050 - Design Performance Test Transaction Programs (Optional)


Performance Testing (PT)

Documents:

PT.060 - Design Performance Test Data (Optional)PT.070 - Design Test Database Load Programs (Optional)PT.080 - Create Performance Test Transaction Programs (Optional) PT.090 - Create Test Database Load Programs (Optional)PT.100 - Construct Performance Test Database (Optional)PT.110 - Prepare Performance Test Environment (Optional)PT.120 - Execute Performance Test (Optional) PT.130 - Create Performance Test Report (Optional)


Adoption and Learning (AP)

Work instructions and user manuals will be tailored for theend users by the core team. The end users will also be trained by the core team to perform the necessary business functions.

Documents:

AP.010 - Define Executive Project Strategy (Optional) AP.020 - Conduct Initial Project Team Orientation (Core) AP.030 - Develop Project Team Learning Plan (Core)AP.040 - Prepare Project Team Learning Environment (Core)AP.050 - Conduct Project Team Learning Events (Core)


Adoption and Learning (AP)

Documents:

AP.060 - Develop Business Unit Managers' Readiness Plan (Optional)AP.070 - Develop Project Readiness Roadmap (Core)AP.080 - Develop and Execute Communication Campaign (Core) AP.090 - Develop Managers’ Readiness Plan (Optional)AP.100 - Identify Business Process Impact on Organization (Optional)AP.110 - Align Human Performance Support Systems (Optional) AP.120 - Align Information Technology Groups (Optional)AP.130 - Conduct User Learning Needs Analysis (Optional)AP.140 - Develop User Learning Plan (Core)AP.150 - Develop User Learning ware (Optional)AP.160 - Prepare User Learning Environment (Core)AP.170 - Conduct User Learning Events (Core) AP.180 - Conduct Effectiveness Assessment (Core)


Production Migration (PM)

The finished solution will be deployed in the organization afterascertaining the production readiness. The transition will be completed when the data is migrated to the new system and the users start performing transactions in the new system.

Documents:

PM.010 - Define Transition Strategy (Core) PM.020 - Design Production Support Infrastructure (Core)PM.030 - Develop Transition and Contingency Plan (Core)PM.040 - Prepare Production Environment (Core) PM.050 - Set Up Applications (Core)


Production Migration (PM)

Documents:

PM.060 - Implement Production Support Infrastructure (Core) PM.070 - Verify Production Readiness (Core)PM.080 - Begin Production (Core) PM.090 - Measure System Performance (Optional)PM.100 - Maintain System (Core) PM.110 - Refine Production System (Optional) PM.120 - Decommission Former Systems (Optional)PM.130 - Propose Future Business Direction (Optional)PM.140 - Propose Future Technical Direction (Optional)


AIM Implementation Approaches


ProjectApproachPaths

AIM Methodology

Documents

Transcript of AIM Methodology