'' Am giving you the over all view and the stages of Project implementation and the

documents used

First Stage : Analysis

Document used :
RD 120 - Requirement Gathering - As Is To Be Process
BR 150 - Fit GAP Analysis (Its been done on the basis of above doc)

Second Stage : Designing

Document used :
BR 100 : Set up Document for the Functional Consultants
MD 200 : Set up Document for the Technical Consultants

Third Stage : Build - DEMO / PROTO TYPE

Document used :
BR 050

Fourth Stage : Testing

Document used :
TE 050

Fifth Stage : Go Live

Six Stage : Post Production

All these documents are the part of AIM (Oracle Application Implementation
Methodology) but not all companies are using the same AIM instead they are using their
own giving different names but the formats of all the documents are more or less same.

Hope this will clear all the doubts, if any question you can revert here or shoot me a mail to
good_looking_bad_character_glbc@yahoo.com (its just an id :P )

hi
MD50,MD70,MD60,MD20 are the documents prepared by the functional and technical
persons while they are going to implement and after implementation.

functional cons take the specifications from the client and they will prepare the document
to tech people as thier requirements is tat..

Hi Jamal,

You need to know and understand what is exactly the meaning of the BR & MD documents
are for.

BR Documents : Business Requirement Documents, which is primafaciely done by the

Functional Persons of the Implementation Team like Funtional Project Leads / Managers.
These documents are the Set up Documents, which is 100% based on the BR 120 -
Business Requirement Gatherings as provided by the business.

You can say these are As Is process. So BR 100 is the To Be Process after you gather all
sorts of info from the Biz and map in the Oracle Systems.

MD Documents : Modular Designing Documents, which are is primafaciely done by the

Technical Persons of the Implementation Team like Technical Project Leads / Project
Manager. These documents are the Design Documents, which is again based on the BR 120
- Business Requirement Gathering as provided by the business.

These MD's are of basically discussed any customization needs or any special behaviaour
oracle system should work which is not the Standard Oracle Funtionality. These also
discussed about the tables and the Interface Tables or forms which are going to be used in
the particular modules. Thses also discussed about the High Level Designs like Flows of
the Business and all.

These MD's are basically made after you all Functional Design and if there is no work
around Oracle System provides for a particular Test Scenario and there is no other way
other than to go for the Customization.

Now I suppose you can understand what is the basic difference between these two.

Now as a Funtional Consultant you need to always go for the BR - 100, that is set up doc.
and in your scenario ( as you said that you have created in GL - COA / CAL / CVR etc)
you have to document all these into BR 100.

The first version of the BR100 will probably be used to build the TEST environment. Any
changes required as a result of problems encountered will be incorporated into the next
version of the BR100, which will then be used to build (say) the UAT environment. In
parallel with these environments, there will probably be a DEVELOPMENT environment
and it may be that there will be changes required to the BR100 because of issues
encountered there. The "Final" version of the BR100 will probably then be used to build
both the PRODUCTION and TRAINING environments.

Let me know thru mail if anything else you require.

Regards
Srinu,

Documentation is playing vital role in Application Development.

Application Implementation Methodology (AIM) is the root for the same.

In Development cycle, there are many documents required for various requirements.

MD.50 is Desgin Document(Functional resource will design), which explore all design
methods like its road-map, which includes all design setups.
MD.70 is technical Document(Technical resource will design), which show all Technical
Details like Coding, Maping and Logics.

Various documents for different scope and criterias such as

1.Implementation
2.Customization
3.Conversions

Each stage is having set of documents.

Hope, you got little stuff about the same.

-----------------------------------------------------------------------------------------------------

Comment by Rangaraj Chandrasekar on November 20, 2008 at 9:19pm

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 Define Business and Process StrategyBP.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 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

4. Application and Technical Architecture [TA] - This outlines the infrastructure

requirements to implement oracle applications.
TA.010 Define Architecture Requirements and StrategyTA.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 StrategyMD.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 strategyCV.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 strategyDO.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 strategyTE.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 StrategyPT.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 StrategyAP.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 Learning ware
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
------------------------------------------------------------------------------------------------
Re: If any person ask what you know about AIM? How briefly we can explain b'coz we
cont expalin AIM in short time. Answer
#1
AIM methodology consists of 6 phases

Definition
Operation Analysis
Solution Design
Build
Transition, And
Production ...u can explain all of this phases if to
be
answered in a short span of time

Is This Answer Correct ? 3 Yes 2 No

0
Phanirajctr
Re: If any person ask what you know about AIM? How briefly we can explain b'coz we
cont expalin AIM in short time. Answer
#2
AIM stands for Application Implementation
Methodology.

Commonly this is know as AIM documents.

There are different AIM documents such as

MD050,MD070,CV040,MD120,-----

With the help of AIM documents ,one can develop and

do the
task allocated according to it.

Is This Answer Correct ? 2 Yes 1 No

0
Murali

Re: If any person ask what you know about AIM? How briefly we can explain b'coz we
cont expalin AIM in short time. Answer
#3
AIM is an Application Implementation Methodology
which is
being followed for Oracle Apps Implementation
project(ERP).
It consists different phases and processes. They are
Phases :
Definition
Operation Analysis
Solution Design
Build
Transition, And
Production
Processes :
Project Management
Business Process Mapping
APplication and Technical Architecture
Module Design and Build
Data Conversion
Documentation
Business System Testing
performance Testing
Adoption and Learning
Production Migration

Each process has it's own standard templates(RD 20,

RD 50,
MD50,MD60,MD70,TE40,etc) to caputre various business
scenarios,etc.
If we follow these processes, phases and using
standard
(important) templates then we won't be missing out
any of
the implementation steps while implementing our ERP
system.

Thanks and regards

Murugan

Is This Answer Correct ? 6 Yes 0 No

0
Murugan
Re: If any person ask what you know about AIM? How briefly we can explain b'coz we
cont expalin AIM in short time. Answer
#4
AIM (Application Implementation Methodology) is the
process
for implementing any ERP package.

The process steps are:

1.Planning (Which includes project kick off -
Internal and
External)
2. Business Process Modelling (Requirements &
Solution
Design)
3.Design, Build and Testing (SIT testing)
4.UAT (User Acceptance Testing)
5.Go-Live
6.Support..
each step in this process has an extensive
explaination of
various steps involved.