| Methodology |
| |
AlphaSoft believes in leveraging a structured process methodology to ensure consistent quality standards in every project. AlphaSoft implements Oracle Applications R11i projects using Oracle Application Implementation Methodology (AIM) Advantage 3.0. Some of the benefits of AIM are:
- Provides a Rapid deployment environment for implementing Oracle Applications
- Helps to eliminate common errors in implementation
- Business Process Guide with detailed business process flow documentation mapped to Oracle Applications functions
- Configuration Guide with detailed configuration documentation for each Oracle Application modules
- Data conversion and Interface templates and design
Application Implementation Methodology (AIM) Advantage 3.0 consists of the following phases: |
|
 |
|
Project Planning and Initiation
During the project planning and initiation phase, emphasis is placed on building a detailed and achievable work plan that establishes a balance between business drivers and efficiency. Establishing a well-defined implementation scope early in the project will give the team a common reference point and an effective way to communicate. It is also during this phase that the steering committee and program office will be established. The steering committee will be the final authority in approving scope changes, major changes in the project plan, and final Go/No-Go to production. In addition to any hardware setups, application products will be installed and patched to current release levels. |
| |
Business Requirements Definition
Business requirements definition will define the business needs that must be met by the implementation project. It is during this phase that business requirements will be mapped to standard application functionality and gaps identified. As gaps between requirements and functionality emerge, they will be resolved by documenting workarounds, alternative solutions, or by changing the underlying business process. In an accelerated implementation approach, only standard Oracle Application functionality will be implemented. Any requirements that cannot be addressed with standard functionality will be addressed outside the scope of the implementation project. |
| Back to top |
Application Configuration and Solution Design
During this phase application set-ups will be completed. It is also at this time that the data conversion process will be defined in detail. The manual method is generally preferred due to its simplicity and the time constraints associated with an accelerated implementation approach.
Project team members will also create detailed Business Procedure Documentation. Supporting business requirements may require building application extensions to standard features. While new system designs are being finalized, the application and technical architecture begins to take form. The technical staff designs a technical architecture that can support the standard application configuration and customization. |
| |
Build and Test Business Processes
If customizations, extensions, or conversions are required, they will be addressed during the Build phase.
Business system testing will be conducted via a series of conference room pilots. During the first pilot, basic application setups and functionality are tested. During the second pilot, converted or entered data, revised setups, and end-to end business processes are tested.
Participation in these activities by key finance users is essential, as it will provide them with valuable application experience that is an essential part of their training. |
| Back to top |
Pre-Production or Transition
During the transition, the project team deploys the new system into the client organization. The project team trains the users while the technical team configures the Production Environment and converts data. Also, during this phase users will perform the user acceptance test. The Transition phase ends with the switchover to production, when users start performing their job duties using the new system.
The key users take on the task of training administrators other members of the user community. |
| |
Production Migration and Support
During Production Migration, the project team will deploy the finished solution into the organization. The transition will be complete when data is converted and end users have started to use the new system. When the system is stabilized, regular maintenance and system refinement can begin. |
| Back to top |
Deliverables
An Oracle Applications R11i engagement, implemented using AIM 3.0, includes the following deliverables: |
| |
| DELIVERABLES |
| Project Phase |
Deliverable Title |
| Project Planning/Initial |
1.Project work plan and schedule
2.Acceptance procedure
3.Change control procedure and logs
4.Defect reporting and tracking procedure and logs
5.Issue tracking procedure and logs
6.Status reports
7.Completed business requirement questionnaires
8.Installed and patched applications
9.Initial project environment |
Business Requirements Analysis |
10.Business requirement scenarios
11.Reporting requirements
12.Audit and control requirements
13.Gap analysis |
| Design/Configure/Mapping |
14.Application setups
15.Design Documents |
| Build and Testing |
16.Initialized test environment
17.System test scripts for conference room pilots
18 Defect reports
19.Test summary report |
| Transition/Pre-Production/Training |
20.Initialized training environment
21.Training plan and schedule
22.High level - module level user training documentation |
| Production Migration |
23.Transition strategy
24.Initialized production environment
25.Configured applications
26.Documented support procedure
27.Production ready system |
|
| |
| Back to top |
| |
