The Backbone of Hourly HR Payroll
Overall Satisfaction
My former employer had Kronos devices deployed for hourly employees to clock in/out of their shifts. The product was used by managers of those employees across the organization to review and approve time entered by the employees. The HR team and my former team would ensure that the data entered was pulled from Kronos and loaded to Oracle for our Payroll process. This provided accurate time recording for our hourly employees and saved the company money resolving disputes on time entered.
Pros
- Kronos is the market leader when it comes to timekeeping and the devices used to support it. There is a reason for that: They work as designed, and they work well.
- Once configured properly, the stability of a WFC server is admirable, considering that the majority of deployments are on Windows Server
- The layout of WFC is very well thought out. It is easy for non-technical personnel to navigate with minor training
Cons
- Product Support can be difficult from a back end perspective. Questions regarding database and network infrastructure (network load balancers/VIPs) can drag as it is hard to get their L2 Support team to engage them
- Although this is true of any application that requires a JRE installed to use from the desktop, Kronos is very sensitive to what version of Java you use. Be warned: delay or cancel any updates until they have been vetted on Kronos
- The Kronos devices are great. However, the Workforce Device Manager module is not as hardy and foolproof as the clocks. Good idea, but still needs work.
- increased payroll accuracy
- increased employee efficiency
- improved resource reporting
I've worked with this when it was called e-time. Nowhere near as good as Kronos.
Comments
Please log in to join the conversation