Ceridian Dayforce HCM is a cloud-based platform encompassing HR, payroll, benefits, and talent and workforce management. It provides companies with a scalable framework and real-time data, such as continual pay calculations, to enable efficient decision-making.
N/A
ServiceNow IT Service Management
Score 8.4 out of 10
N/A
ServiceNow is a fast-growing service management provider that went public in 2012. Built on the ServiceNow Now Platform, the IT Service Management bundle provides an agent workspace with knowledge management, and modules supporting issue tracking and problem resolution, change, release and configuration management, and (on the higher tier ITSM Professional plan) ITAM and software asset management.
Ceridian Dayforce is well suited in payroll where the system has multiple functions to audit, review, and process payroll. According to the new Ceridian Dayforce functionality coming soon the use of AI technology to engage in payroll in a more efficient way is a great way to scale this area of the system.
In our organization, we are using ServiceNow extensively. Change Management, Incident Management, Problem Management, Time tracking are few modules which we use extensively. This sort of model will work for any product or service based companies as the product is built on ITIL framework. So this product will be suited for small or large scale companies to better organize and add controls and track SLA's for technology or business process.
When I have a number of requests to make, for example a request to add a dozen or so user accounts to more than one group account in Active Directory , I can put all the needed information into the initial form, add it to my "shopping cart" and all of that information remains on the screen for the next item for which I only need to edit a few items (like the AD group name in this example), and keep adding them to the shopping cart until I have them all. When I "Check Out" each of those items is generated as a separate task under the one request. It simplifies and expedites the creation and tracking of these kinds of requests.
I can easily and quickly see what tickets are currently assigned to me in order to prioritize them and remain aware of my workload.
Numerous fields for CIs can be used when trying to find the entry for a particular item. For example, IP Address, server name, raw text, classification, and so on.
To help with making sense out of related tasks, when a task is assigned to me and I need to open another task for a different team to work in order to complete my task, I can open a sub-task from my ticket so that the relationship between the two can be pulled up later into reports. For example, I may have a task to build a new vm, and need to open tasks for networking, security accounts, software installation and so on. By opening sub-tasks from my assignment, the time spent by all parties concerned is tied together for more meaningful cost accounting.
It is hard to find areas for improvement, the tool is very powerful. That said, building the CMDB still involves some manual interaction which was not how it was presented in demos.
The CMDB data is almost too deep and detailed. When you build the relationship map it can be so large that it is overwhelming. You can limit this, but the default maps are massive if you are discovering lots of device classes.
The product is expensive. Since they are the leader in the industry and the product has tons of features, they definitely charge for it!
We are highly invested in Ceridian's Dayforce product. It give us the flexibility and scaling that our growing company needs. Its potential reaches beyond the basic HR functions to the decision making that our Management Team needs. Ceridian is always innovating the employee and employee experiences to offer cutting edge options.
To be completely honest setting up a new ticketing system can be a pain in the ass. Once you have it setup and customized the way you want it, you don't want to switch unless you're unhappy with the product. Unless future releases and updates really muck the system up, I wouldn't change.
I think it's very usable for the employee. I don't think it is as easy for the HR/PR admins - especially if there is an issue. There are so many setup screens that need to be looked at to try to figure out why payroll isn't calculating properly, hours aren't feeding over correctly, or benefits are not calculating properly. For the most part, they can't do their own troubleshooting. The same is true for the managers. Our managers find it cumbersome to go into make any schedule changes after the schedules have been generated.
The dashboard is so confusing, [there are] many clicks to open a task and search by a ticket. The Enterprise customisation [we did] has finished to kill the software and creates a really bad experience on a daily basis. [It is] So slow, and so many clicks to process a ticket. Works only on IE so, that [should] make you realize that [it] is a bad idea.
We have never experienced a total/unplanned outages that effected our ability to process payroll. However, there are times when the application's speed is significantly effected - and processing a payroll may take up to twice as long as normal.
We haven't noticed any slow-down due to the integration of Dayforce WFM with our Ceridian HPL products (HRIS and Payroll). The new HTML view of the timesheets don't load as quickly as the old Silverlight view - however, we have gotten used to the change.
Most of the time the support is great; it's not always super efficient but I always get the help I need. Occasionally it takes a lot longer than we had hoped or get conflicting responses. We had one ticket recently where we were told we would have to pay the service team to support us on the project and then another person called the next day with the solution to our query and was able to find a solution easily. Generally, though, the response is great and they either walk me though how to do something via a Zoom Meeting or they email step-by-step instructions on how to do it and say if I have questions we can set up a meeting to discuss further.
I would give it this rating because we have had no major issues with the support for ServiceNow after we implemented it at our organization. They seem to respond promptly and efficiently if we ever do need to open a support case with them about an issue we are having.
The online training is very good, there is a wide variety of topics offered and several dates and times. The instructors are very knowledgeable about the subjects they are teaching. There are so many ways to program Dayforce that just the basics seem to be covered in the class.
To type in what should be a text box, you have to click an empty cell, a tiny text box pop up opens with a check box and an X. You the. Type in the text box and have to click the check mark. If you have a bunch of fields to fill out, doing this is very annoying. Absolutely know thought went in to this. I'm sure somebody in marketing thought it was a good idea. It wasn't.
Have a strong internal team. Communicate with your implementation team - they are there to make it work for you. Take the time to really think about how you want the system to work for you - in some cases, you may need to rethink your own business practices to see if you are working harder when the system could do it for you
Without exception, every client I have worked with has been very happy with their resulting product. While this is partly due to my work, I must point out that the platform is the winning decision, not the implementer.
All of the info for Payroll, HR updates, employee updates, Time worked and PTO are in a single application, with a single login, updated in every screen or module in real time. There is no lag in data from screen to screen or from user to user, its almost instant.
We used to use Jira to handle service tickets but it's way too robust for something this straightforward. Due to the nature of Jira, you needed to already have a lot of documentation and knowledge about who should be assigned the ticket, so the lift of creating a ticket was time consuming.
Overall, we are extremely happy with the Dayforce WFM module. Our biggest pain point is concerning the twice annual software upgrades - which is the only reason I haven't rated them as a '10'. Because every customer is configured differently, the upgrades can sometimes have adverse effects on our current configured policies/rules. And although they roll-out the upgraded version in a test environment several weeks before go-live, not all testing is accurate in that environment. Some issues do not present themselves until you are working with live punches.
Performance Reviews/Comp used to be handled via paper and tracking/reporting was a nightmare - having all of that in the system is so much more efficient and provides huge ROI
Our organization used to have big problems with hiring managers going rogue and hiring positions that aren't approved by Finance - we built an approval workflow in the system that triggers before any req is approved which has completely solved this problem
Dayforce Wallet has been a huge perk for our employees - it's heavily used and our crew love it
Overall ServiceNow has a positive impact on getting the SLA of tickets down in supporting our customers.
One negative impact has been the amount of time to get the product to produce an ROI, it's almost too big to fail and too big to replace. You almost become committed to the product. Good or bad.
Another negative impact would be if you track metrics of employees and time tracking, there is a lot of scenarios where engineers will track time on tickets but not get credit for closing them as the assignee function of tickets can only be tied to one user and credits only the engineer who closes the ticket.
Another positive impact would be the level of security for permissions and scaling the workloads is robust and you will get out of the system what your team is willing to put in.
