Oracle Cloud HCM/ERP : Managed Services vs Inhouse vs Hybridadmin
Oracle cloud Fusion management is quite different from managing a on-premise R12 or 11i EBS instance.
Most companies who have on-premise EBS will have a team of functional analysts and EBS developers and Applications DBAs managing the EBS suite.
In the cloud environment though, the team structure can look quite different.
1. First of all there are no DBAs needed. However, there is a sort of a requirement for a Technical Architect who can coordinate with Oracle regarding patch management, SR resolution, instance refresh and other aspects. This is an ongoing exercise, since Oracle applies quarterly patches to fusion. The quarterly patch is applied on the first weekend of the month to a non-prod pod and then you get a two week period to test it before it is applied to Production. Plus there are ongoing issues regarding environment regarding performance. So think of this role as a Head DBA or a Technical Architect. This person then has a team of DBAs who are basically Oracle folks.
2. Secondly, the need for developers is now limited to Reports development and interfaces.
3. The most heavy aspect is a need for functional analysts. You will roughly need one functional analyst each for Finance, Procurement, HCM and other modules.
There are a lot of managed services vendors who offer full services. The question becomes whether you should rely fully on the vendor or have a full in-house team of resources or a hybrid model.
A hybrid model would work best since you dont want to be fully reliant only on the managed services vendor and lose all competency. Also, building a full inhouse team would be very expensive.
A hybrid model where you keep the technical architect role and few key functional roles in house would be the most appropriate model.