The initial setup was complex and data was lost during the implementation.

I would rate my experience with the initial setup an eight out of ten. It is fairly easy to set up. It helps me a lot in terms of building competency because you need logical thinking rather than a lot of technical acumen to configure the application. 

So if you know the concept of HR data, like how HR data works, how the organizations work, how the business structure works. What hierarchy is. In that case, if you know the concept, it becomes really easier to configure the system.

Workday is a SaaS application. So it's always on cloud. We are not using a hybrid cloud or private cloud. It's a public cloud. Private cloud is going to be expensive. We did that. We tried to do that for Amazon, but it was expensive.

We are in the process of implementing Workday internally. We have extensive experience with Workday, having helped Expedia migrate from PeopleSoft to Workday. We are currently supporting them in advanced compensation and payroll reporting on the NHR side.

We are currently implementing it internally for PeopleTech. Earlier, we used Oracle Fusion for our US location, but the plan is to implement Workday for all locations, including the US, Canada, India, and Singapore.

 The initial setup is easy and I rate it a 10 out of 10.

I would rate the setup of the solution an eight out of ten. The tool is deployed on the cloud. The solution’s implementation took only hours to complete.

Setting up Workday is straightforward.

It's very easy to set up. It's not overly complex or difficult. 

I'm not technical and did not handle the deployment and therefore cannot speak to how long it took or the exact process. It was a global rollout. It may have taken six months to a year. 

I'm not sure what the maintenance process looks like. It is a centrally managed application. I don't know which team actually covers it. Here in Greece, we have some application subunits that can support end-users, however, not the actual technical team. It is somewhere in the world. I don't know if it is in America, or if it is in India. I really don't know.

The initial setup of Workday is simple.

I rate the initial setup of Workday an eight out of ten.

The initial setup of Workday is not difficult. Workday provides a blank canvas for you to work with, but they also give you guidance and tools to help you get started. As you progress and bring a team with skills on board, you can then build upon the initial setup. Overall, the setup process is complex.

The initial setup was easy for me. It might be complicated for some. I rate the process a ten out of ten. 

It is highly complex, and the level of complexity depends on what functionality you're rolling out. If you're rolling out payroll and converting from a legacy system, that's going to be complex. All in all, Workday does a good job to help you be successful, but nevertheless, it's still complex. 

It definitely takes months. A lot depends on the size of the organization. Workday has started to market towards smaller customers or organizations with under 500 employees, which is unique and something new for their business model. Typically, that wasn't their bread and butter. It has always been the medium enterprises or large enterprises. Their sales pitch is that they can stand those customers in 16 weeks. That generally tends to be more in the neighborhood of 20 weeks. If you're a big customer with over 5,000 employees or in the neighborhood of even 50,000 employees, it's not unreasonable that your deployment could take a year or more. Even with Oracle, SAP, or PeopleSoft, your deployment is going to be the same. There's just no way you're going to roll out all the change management and all that technology in a short amount of time. It just wouldn't be feasible.

The product can be deployed on the cloud.

The initial setup of this solution is very easy, and the deployment will take a maximum of one week to complete.

It's straightforward, but you need to know it in order to work on it. You need training on Workday.

I was not part of the initial Workday setup so I don't really know.

The initial setup was complex but manageable. I have worked on a couple of deployments. The last one within the last year was supposed to take eight months, but it took a year and a half. That was mainly because of the integrations taking a lot longer than I anticipated and problems with the vendor who was implementing it. The vendor did a series of missteps that didn't help.

It was easy to install. 

I was not involved with the deployment. I can't do it because I don't know how to do it.

Workday's installation is straightforward. 

From a reporting standpoint, there's not much configuration or setup required at all.

The initial setup is straightforward. 

It is a SaaS solution. I just need to access the website.

The initial setup is very straightforward. Deployment took two years but was smooth because it's a huge implementation across 32 countries. And it took us only two.

The installation is complex. There are two reasons for this. One is that you need a Workday partner to implement the setup for you. In order to be a partner, you have to have an organization or group of consultants who are trained by Workday to implement the product and support it. It is a closed environment and Workday keeps everything pretty much in check. It is complex in the fact that you have to have somebody — either Workday or a Workday partner — implement it for you.

The deployment will usually anywhere from three months to 12 months or more. It depends on the number of users or the number of modules and how complex the expectations are for the implementation. All the different flavors of how complicated an organization wants the implementation to be — all that becomes a factor in the length of the deployment.

The number of people required for maintenance on Workday varies around the same sort of desire for complexity. You usually have at least one person in-house to watch the implementation and you will have a contract with somebody to supply you with support. That might be a partner contracted for 800 hours a year or whatever the specific terms might be. Then you "lose it as you use it" or you have an ongoing maintenance contract with somebody.

I rate the ease of setup a six out of ten. The product is not easy to implement. It is difficult to understand the setup at first. The tool is not that informative for us to understand the whole picture. The solution is deployed on the cloud. The deployment took us two years.

The initial setup is very straightforward. That’s the amazing thing about it. Epic is able to explain to you the processes of getting what you need. It's AI-driven, and once you get on there are certain templates necessary that you've got to have. You have got to go in and reregister yourself, however, it's already pulled all the information.

For us, on the hospital project, there was a whole lot of front-end work that had to be done. However, that's why we wanted the solution - to tie all this together and have it centralized, at least the data processing and data mining aspects.

The smartest thing the hospital did is they rolled everything out by business unit. They made sure that each campus was well integrated and then there was a final assimilation. That was smart on their part, as opposed to saying, “All the nurses have this now, and all the doctors have this, all the ERs can work on it now.”

The initial setup is quite easy. Anyone who has the domain knowledge can do it. It was around a seven-month journey. We implemented it module-wise in various phases. We did two modules per month. We first did the Team module. After that, we went into the Absence module and then into the Performance module.

It's very easy to set up and flexible to configure. 

Setup was not complex as our implementation partner defaulted most configurations, but it could be wrong. We need to look back after implementation.

In the beginning it is difficult to wrap your head around the in-memory pieces, and which configuration drives what functionality. It’s like any other software in that manner, and it’s about digging in and learning it.

The technical implementation was straightforward with data dumps and use of their well-documented API’s. The complication came in applying policies to the system and training our users. The complexity was, and continues to be, enabling the power user to take advantage of the power of the tool without reaching out for help.

The beauty of it being a SaaS product is that we are always on the most recent version and we always opt for an early upgrade when there are new releases.

It was straightforward. I would rate it a three out of five in terms of the ease of setup.

The deployment is a little bit complex and I had to purchase additional support hours to complete it. It did not take a long time, although it was also not quick. If you consider what is probably common for most people implementing any type of system that size, I was probably about six weeks late on the deliverable.

Straightforward.

Complex, as it's moving to a different system, getting the stakeholders together, and making them make decisions.

The initial setup is straightforward.

The length of time required to deploy Workday depends on the complexity of the requirements. The average is probably one week.

The initial setup is pretty simple.

You may need some help, but it's not very complex.

Depending on the complexities, it can take two to three months to deploy.

The initial setup was easy. It's on the cloud, so you just set how many users you need and they activate it and that's it. 

The setup normally takes around a week. The time it takes depends on the technicalities and functionalities. 

Initial setup was simple.

The initial setup is not straightforward. 

The installation is not so straightforward and could be faster. 

Its duration depends on the model one is using and can range from three to six months.