oAppsNET employs a proven approach that standardizes and streamlines the implementation process while optimizing time, quality and the efficient use of resources. Our implementation approach leverages both Oracle’s Application Implementation Methodology (AIM), the industry standard for implementing the Oracle E-Business Suite, and our extensive application and industry experience.
There are six phases in the oAppsNET implementation approach:
In order to create momentum while optimizing human and financial resources, several activities have been identified as "catalysts" for a successful project initiation. A "Readiness Checklist" is used to communicate prerequisite tasks prior to the formal initiation of the project. Progress in these areas will shorten the critical path while creating a solid foundation for the project.
A number of activities on the Readiness Checklist include:
- Prepare project facilities, equipment, technical infrastructure, and initial Oracle environment (instance)
- Identify and assign Project Team Leads and resources
- Define and communicate preliminary roles and responsibilities for the Client Project Team resources
- Work with the oAppsNET Project Manager to develop and confirm the Implementation Strategy. This includes the Implementation Approach and the Implementation Scope.
- Work with the oAppsNET Project Manager to begin development of the detailed Microsoft Project Plan. This includes the task list, timelines, assigned resources, etc..
In addition, the oAppsNET and the Client Project Managers will review the standards to be followed during the project for:
- Status reporting and meetings
- Steering Committee meetings and reporting
- Project team training
- Change control and gap management/resolution
- Risk management
- Issues management
- Quality acceptance
2. Operations Analysis:
The oAppsNET and the Client teams will review the business requirements for the project, as well as the legacy processes being followed today and potential / desired changes. Following the requirements review, the team will prepare for and conduct the first Conference Room Pilot (CRP). CRP1 will begin the knowledge transfer process and educate the Client Project Team Members about the specific functionality to be used by the Client. Each of the processes being implemented will be reviewed and key functionality will be demonstrated in the Oracle applications. CRP1 will result in key configuration decisions being made and potential gaps in the out-of-the-box applications being identified.
The following tasks will also be completed during this phase:
- Project kick off meeting
- Project Team Oracle Navigation training
- Preliminary workaround recommendations
- Develop instance strategy
- Define reporting and information access strategy
3. Solution Design:
The primary objective of this phase is to fully design and configure the business solutions that satisfy the requirements gathered during the Operations Analysis phase. During this phase, the Client Distributing Project Team Members will participate in small group workshops with oAppsNET Functional Consultants to develop the business processes to be implemented, determine the application setups to support the processes, validate the reports, interfaces, conversions and extensions requirements, and document the Client Distributing Oracle processes.
The following tasks will be completed prior to the Build phase:
- Confirm reports, interfaces, conversions and extensions (RICE) requirements
- Initial configuration of Oracle for the Client
- Analyze high-level gaps
- Develop end-user training strategy and plan
- Confirm integrated business solution (design)
- Define (RICE) design and build standards
This phase focuses on developing the functional and technical specifications that support the identified RICE requirements. Upon approval of each spec, development work commences. In conjunction with these efforts, the functional team prepares for and conducts the second CRP. CRP2 testing focuses on detailed testing of the Oracle processes (less the RICE) through ‘real-life’ scenarios.
The following tasks will be completed prior to the Transition phase:
- Develop CRP test scripts
- Document application setups / configuration
- Configuration changes, as necessary, by application
- Unit testing of RICE after development
- Perform sample conversions
The primary activity of the Transition phase is the system integration testing (CRP3), which is intended to test the comprehensive system functionality and integration using detailed, cross-functional Test Plans. It is during this time that the bulk of the knowledge transfer for the project occurs. Close working relationships are formed to continuously refine configuration and the related processes to create optimal business solutions for the Client. Our objective in this testing is to simulate a production environment thereby reducing exposure during the Production phase of the implementation. The Transition phase is also used to finalize all open issues from testing and begin preparing the users for all aspects of being in production.
The following tasks will be completed prior to the Production phase:
- Refine CRP Test scripts
- Perform required conversions
- Conduct integration testing, including RICE
- The Client designs develops end-user training materials
- Define system responsibilities
During this phase, the Client's functional and technical teams will put the business process and applications design through the last round of testing - User Acceptance Testing. The project team is augmented by representatives of the business from affected locations for the execution of the test scenarios. Acceptance testing is performed in a production ready, fully integrated system that allows for a thorough examination of functionality and performance. The Client will then evaluate the results of this final testing effort and make the ‘go/no go’ decision. The Client's trainers will provide formal end-user training during this phase.
The following tasks will be also completed prior to "Go-Live":
- Process team training and acceptance testing
- Create detailed transition / cutover plan
- Complete final system preparations and configuration of Oracle Production environment
- Assign responsibilities to users
Final conversions are then performed into the production instance, according to a detailed cutover plan. Once all of the tasks associated with the cutover plan are successfully executed and the Client is using the system in the Production Oracle environment, oAppsNET works with the Client support staff to provide support to the end users and confirm the operation of the production system. This support continues through the execution of all of the implemented business processes including the first month-end close. Throughout the month, oAppsNET will continue the transition of responsibility to the Client production support organization.
The following tasks will be completed prior to the conclusion of the implementation:
- Support first time transactions
- Conduct business process audit in Production
- Monitor first month-end close
- Project wrap-up / Quality Assurance