Oracle HCM Cloud Review

Fully integrated HCM Cloud solution


What is our primary use case?

It has many use case like HR administration, recruitment management, performance management, learning, ...

What is most valuable?

It is very user-friendly. Most of the UI is very intuitive so you don't need to follow a course to use it. Of course you have one single UI regardless of your roles, so you don't have to log into separate applications depending on whether you're HR or just a normal employee. The solution evolves quickly (4 major updates per year)

What needs improvement?

Sometimes implementation documentation is a bit behind. Some customers like to manage things themselves after the initial implementation and they find that a bit difficult.

Also -but I think that this is the case for all solutions with such a functional extent- you feel that different teams are working on the different modules, but this is normal because everybody has their own specialization.

In the next release, I would like to see a some further updates to the recruitment module. I would like to see the preboarding extended so that it sends out notifications through personal email. That would be very useful.

For how long have I used the solution?

I have been implementing Oracle HCM Cloud for the last six years.

What do I think about the stability of the solution?

It's fairly stable.

What do I think about the scalability of the solution?

it's very scalable. You can request more users to be added. You don't have to pay extra for scalability, but of course, you pay for a number of users that are using this system. If you're having a tremendous increase in the users, then, of course, you end up by paying more. (If you would have an on premise solution you might need to have your servers expanded in this case so that would cost you too).

How are customer service and technical support?

The technical support depends. Overall, they're good. You've got some that are really, really good and you've got some that are less good. It depends on who you get and how well you describe your issue. If your issue gets to the wrong team, then, of course, then it seems like the team isn't helping but it's because you didn't describe it properly. 

How was the initial setup?

The initial setup is straightforward. Some customers make it complex. Every customer thinks they're something special and some customers realize in the end that the most basic features would have been better for them than all the complex things they wanted initially. They're used to telling the developer, "We want this that way" and that's not the way it works in the cloud. This tends to make things more complicated. It is not that difficult. You do need some technical background for formulas and stuff, but it's not rocket science. Some customers make it more difficult than it should be.

The time it takes to deploy depends on how many modules and special cases you want. Typically things differ from country to country, different sites have different rules behind it. The time it takes to deploy all depends on how complicated you make it, how many countries you want to do, and how many modules you want to implement.


What other advice do I have?

My advice would be: Keep it simple. Make sure that your customer is aware of the processes in the solution and show them those before asking them what they want.

Make sure that the customer understands what there already is so they don't start freewheeling. 

I would rate it a nine out of ten.

Disclosure: My company has a business relationship with this vendor other than being a customer: Partner.
1 visitor found this review helpful
Add a Comment
Guest
Sign Up with Email