Scribd
Upload
176 views

Different Stages in An Oracle Application Implementation Project

The document outlines the 6 key stages in an Oracle application implementation project according to the Application Implementation Methodology (AIM). The stages are: 1) Definition of Project Management 2) Operational Analysis 3) Solution Design 4) Building Stage 5) Transition Stage 6) Production Stage. Each stage involves certain activities and documentation that need to be completed to successfully move the project forward.

Uploaded by

Ram Niwas Kushwaha
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOC, PDF, TXT or read online on Scribd
176 views

Different Stages in An Oracle Application Implementation Project

The document outlines the 6 key stages in an Oracle application implementation project according to the Application Implementation Methodology (AIM). The stages are: 1) Definition of Project Management 2) Operational Analysis 3) Solution Design 4) Building Stage 5) Transition Stage 6) Production Stage. Each stage involves certain activities and documentation that need to be completed to successfully move the project forward.

Uploaded by

Ram Niwas Kushwaha
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOC, PDF, TXT or read online on Scribd
You are on page 1/ 4

Stages in an Oracle Application

Implementation Project
A Project is not a short term activity to be completed in matter of days, it requires
intensive analysis, thoughtful thinking and serious decision making in core and
critical business activities. These decisions taken at every stage are critical and
irreversible.

There is no going back after performing final step. We have to understand how a
long term project is broken up in to phases and completed smoothly. We will see
what the different stages in an Oracle Application Implementation project.

Application Implementation Methodology (AIM) has laid out various stages available
in a project.

1.) Definition of Project Management


2.) Operational Analysis
3.) Solution Design
4.) Building Stage
5.) Transition Stage
6.) Production Stage

Stage 1 - Definition of Project Management


Description
========
The success to any project is a well thought of PROJECT PLAN at the very
beginning considering the requirements and available resources. In real time the
whole project is broken in to different phases and for each phase a detailed plan
is laid out which in turns account for the overall project plan.
Project Plan must be revised whenever there is a Change in the contract or
requirement of the client

Documentation to be Prepared
======================
1.) Project Plan (Finalized or Draft)
2.) Write up about the Client and the Consultant.
Stage 2 - Operational Analysis

Description
========
This is the most Critical stage of the Project. One must devote the maximum
possible time to this stage. Any compromise on this stage may prove critical at
later stage of the project.
In this stage a Consultant, who is a total stranger to the client so far is going to
make an effort to become an expert in understanding the client business every
inch.
Only when he masters the clients business, he will be in a position to think
beyond it and provide solutions considering the impact it can have on overall
business.

In this stage a consultant must carryout following activities:-

 Clearly understand the contractual obligations made between the client and
the consultant with respect to the work to be performed.
 Detailed study on the Client business and Organization Structure
 Capture the current business process as they are following (Also known by AS
IS documentation)
 Collect the requirements from the client, managers, end users as to what they
expect from the Oracle Product
 Requirements with respect to Functional Side as well as Technical Side is
collected
 Document the bottlenecks faced with the existing system in place
 Most important point is that get the document signed from the client
( Note: Normally speaking once a requirement is expressed at this stage , it will
be taken care by the consultant, however in real time, requirements gathering
becomes a day to day activity in many clients place, which is highly
unprofessional way of working )

Documentation to be Prepared
======================

1.) RD 10 --> Current Financial and Operating Structure


2.) RD 20 --> Current Business Baseline
3.) RD 50 --> Business Requirements Scenario
Stage 3 - Solution Design

Description
========

After making serious understanding and analysis on clients current business


practices and future requirements, consultant must begin the process of
providing solutions to each and every aspect.
If a straight forward solution is not possible, think about the possibility of
workaround. Enough analysis has to be done in drafting the new business process
of the client which is going to be followed here after.
It is also known as To Be Process. Once the solution is decided on, the same
must be communicated to the client seeking acceptance. When the client is
satisfied with the solution, consultant can put an end to his research work on
providing alternate solutions.

Documentation to be Prepared
======================
1.) BP 80 --> Business Process Design (To Be process)
2.) BR 10 --> High Level Gap Analysis
3.) BR 30 --> Business Requirements Mapping
4.) MD 50 --> Application Extension Functional Design
5.) MD 70 --> Application Extension Technical Design

Stage 4 - Building Stage


Description
========
Only at this stage the work of performing setups and access to the instance
begins. Based on the Solutions and new business process (To Be) designed at
the previous stage, the consultant starts performing setting up of the Application.
In case of a functional requirement, it will be setups from the front end, in case
of technical requirements, sql scripts, and customizations will be performed.
Document all the setups that have been carried out at this stage, since it will be
useful when the production Instance is configured or when there is a system
crash or corruption of data or any hardware failure. After performing all required
setups, the system has to be tested for its readiness to carry out operations.

Documentation to be Prepared
======================

1.) BR 100 --> Application Setup


2.) TE 20 --> Unit Test Script
3.) TE 40 --> System Test Script
4.) TE 50 --> System Integration Test Script
5.) TE 120 --> System Integration Test Plan
Stage 5 - Transition Stage
Description
========
In this stage, client is exposed to the Applications for the first time to get the
comfort level. In order to make the client to get a feel of the system, user guides,
training manuals and training may be given in understanding how their business is
completely taken care by the product.
Once the client is exposed to the Applications, they normally tend to show some
interest in learning new things, which can be used for testing the system.
Once the client is satisfied with the Solutions and the way in which the system
performs, he can express his willing to accept the system. In real time,
acceptance will be taken up at two levels:-

First Level - CRP - Conference Room Piloting - here the consultant gives a
preview of the new system to the selected members of the client and gets their
feedback.
Second Level - UAT - User Acceptance Testing - Here the consultant gives
detailed demonstration on the new system to the users (Super and End), and get
the acceptance from the users that the new system meet their expectations.

Documentation to be Prepared
======================

1.) TE 130 - - > User Acceptance Test Report

Stage 6 - Production Stage


Description
========

Once CRP and UAT is approved, it is the duty of the consultant to replicate the
same in a new environment which will be used solely and exclusively for the
Production purposes only. After making the production server ready with all
setups, it is advised to clone the production server to a development or test
server, so that any value addition or future testing can be carried out
separately in future. Once the production server is ready, it is given to the client
to begin their operations, which is termed as GO LIVE. In order to assist the
client in adapting to the new system, consultant will provide them with User
Manuals and also a support consultant for a short period of time if needed.
Once the production server is ready and used, the implementation gets over, and
the client should give it in writing that he is satisfied with the implementation
taken place, which is termed as sign off ( A Big Good Bye ) !!

Documentation to be Prepared
======================
1.) User Manuals
2.) Client's sign off on the Acceptance Certificate

NOTE:-
Documentations suggested in this post are recommended when AIM is adopted.

You might also like