Let’s start reviewing how we will be executing Cloud Applications Implementation of Oracle HCM/ERP/CX Cloud for any customer project. We usually execute the Oracle Applications project based on the methodology available from Oracle, earlier during Oracle’s e-business suite implementation we were following AIMS methodology, which later on with Release 12 of EBS, OUM Oracle Unified Methodology was introduced. Most of the time we took a number of key phases and deliverables from OUM/AIMS and create our own implementation methodology but primarily based on these two approached or methods. OUM was aligned to the PMI phases so it becomes easy for all of us to co-relate the phases and take necessary steps from OUM to build our own approach some time to satisfy internal IT protocols. if you are interested difference between AIMS vs OUM, you can link my earlier post on this, OUM vs AIMS. Now with the rapid market change to Cloud adoption and Oracle’s own Software as a Service products leads to a new approach, therefore, Oracle has introduced Cloud Application Services Oracle Unified Method (CAS OUM), a lightweight approach to implementing cloud services with the focus of out-of-the-box features implementation.

In all these approaches, we usually cover all the tasks of any implementation project from start to Go-Live including post-production support. what I am going to discuss here primarily 2 below topics.

1. Executing Implementation project as per Cloud Application Services Oracle Unified Method (CAS OUM) a lightweight approach to implement cloud services with the focus on out-of-the-box features implementation. Overall discussion on this approach and
2. Executing actual tasks/steps to configure HCM/ERP Application, we know these steps are part of overall project plan but here I am just bringing out to focus on actual Configuration of the HCM/ERP Application.
   • as a first scenario, we will be working on HCM Cloud configuration.

Cloud Application Services Oracle Unified Method

This approach is for Oracle SaaS products like HCM Cloud, ERP Cloud, Sales Cloud, and Service Cloud to cover implementation of standard/out of the box features and other tasks like integration, data loads, and any other project-specific documentation and training. This approach has 5 phases:

1. Project Design
2. Configure
3. Validate
4. Transition
5. Realization

This is the detailed Cloud Project Implementation flow,

Source: Oracle OUM

Detailed information on these phases can be found from Oracle OUM

Core and Optional Tasks

CAS OUM has introduced the concept of Core and Optional Tasks as part of the Cloud Applications Implementation project plan.

• Core Tasks are the minimum mandatory steps to implement out of the box functionality of Cloud application.
• Optional Tasks to meet additional project-specific requirements based on the scope and situation. for example additional training or custom integration with on-premise applications. These optional tasks are categorized into Training, documentation, Extensible Items/extensions/custom reports, Data loads, Integration, and any other. Guidelines are provided in the CAS OUM for you to decide which optional tasks is required or not.

A few of very famous deliverables based on AIM are presented here as differences between CAS OUM and AIM:

[supsystic-tables id=2]

Share your thoughts and let’s learn together, how CAS OUM is being used to implement Cloud SaaS projects. #SocialLearning

This is a short overview of Cloud Applications Implementation methodology and later on, I will try to cover detailed presentation on this topic but now we will move into 2nd point of our discussion that is:

Executing/completing actual steps/tasks required to implement HCM Cloud, we will start as a sample project.