Types of Oracle Fusion Finance ERP Projects

 

1. Implementation

2. Supporting and Maintenance

3. Rollouts

4. Enhancements

5. Upgrade 1. Implementation      Meaning The Client was moving the data from Legacy/Source system to Oracle  Fusion and they don't know about Oracle ERP.   A. Legacy to Oracle   B. Present System to Oracle 2. Supporting and Maintenance    Meaning Client facing issues/errors after go live of the project. A. They may take support from service providers. B. These issues are called as supporting issues. 3. Rollouts Meaning Stage by stage Implementation. A. Phase1/Wave 1 B. Phase2/Wave 2 Client wants to implement for 20 countries. But client will  not implement all at one go. Firstly, they will implement for  one country/Parent. and later point of time they will implement for other  countries. 4. Enhancements   Meaning * Adding New features for existing ERP. * Modifying the Process flows Now we are using check payment method and we are moving  into electronic payment method. 5. Testing    Meaning * Build Stage * We will test all scenarios are working or not. Different types of testing’s 1. Unit Testing 2. System Integration Testing (SIT) 3. User Acceptance Test (UAT) 4. Regression Testing 1. Implementation Project  A. Agreements 1.Scope of Work/Statement of Work (SOW)   B. Methodology 1. Oracle Unified Method (OUM) Methodology 2. Agile Methodology 3. Waterfall Methodology   * Client will do business process documentation/Internal documentation.   PPT Setup Checklist Topics Covered -  Client will sign off   Open Questions/Requirements from clients   We will do Analysis and try to find solutions Send mail to resource head/Discuss internally if not possible raise an SR with oracle. Try to find Standard Solutions Setups Setup Modifications Addition of new setups Page composer/Personalization Page Customizations Descriptive Flex Fields (DFF's) Workarounds Notifications Interfaces Customizations No standard Functionality Page Composer/Personalization This is used to make the optional fields as mandatory in oracle.    Oracle Unified Method (OUM) Oracle Unified Method (OUM)    Oracle Unified Method (OUM), the new implementation metholodogy  is intended to be used for all range of products. It is a replacement  of oracle application implementation. metholodogy AIM. We were doing  mainly AIM for Oracle E-Business suite implementation projects and other projects,  recently we have started using OUM for all the projects including oracle  cloud implementations. It took some time to transform new codes of OUM, we use to  call RD050 (Gather Business Requirement), BP080 (Future Business Model),etc., but after  the OUM it takes some time to be conversant like what are the equivalent document code  names and how to call them. OUM Stages 1 Inception 2 Elaboration 3 Construction 4 Transition 5 Production   1 Inception The overriding goal of the inception stage is to have concurrence among all  stakeholders on the lifecycle objectives for the project. Therefore,  the inception phase is critical for all projects because scope of the effort,  high level requirements, and significant risk must be understood before  project can proceed. 2 Eloboration  The goal of the eloboration phase is to move development solution from the  scoping and high level requirements done during the inception phase to  developing  the detailed requirements, partitioning the solution , creating any necessary  prototypes, and baselining the architecture of the system to provide  a stable basis for the design and implementation effort in the  construction phase. 3 Construction  The goal of the Construction phase is to take the solution from detailed  requirements models, through configuration of standard packaged  software functionality, development and testing of custom components,  and integration to a system that is ready for a first release that goes  into production, often a limited release and often called a beta release.  In short, complete the development of the application system, validate that  all components fit together, and prepare the system for the acceptance  test and deployment. 4 Transition  The goal of the Transition phase is to take the completed solution from  installation onto the production system through the acceptance test to launch. of the live application, open, and ready for business. Validate that  the system is tested systematically and is available for end users.  During this phase, the new system is accepted by the customer organization,  the organization is made ready for the new system, and the system is put  into production and, if the new system replaces an old one, a smooth  cutover to the new application is provided. 5 Production  The goal of the Production phase is to operate the newly developed system,  assess the success of the system, and monitor and address system issues. This includes monitoring the system and acting appropriately to maintain  continued operation; measuring system performance; operating and  maintaining supporting systems; responding to help requests,  error reports and feature requests by users; and managing the applicable change control process so that defects and new features may be prioritized  and assigned to future releases and put into a plan for future enhancements to the application system, as well as determining, developing, and  implementing required updates.  Things that are Highlighted with Orange those are managed by service providers.     Oracle Unified Methodology 1. Inception 2. Elaboration 3. Construction 4. Transition 5.Production