It takes guts to lead. It takes guts to follow. Remember when reviewing your Kronos Timekeeper or Scheduling implementation to give the team members with the seemingly crazy ideas a chance. They might just have the idea that saves the company $10M.
The US unemployment rate continues its downward trend, and while that's good news for our slowly growing economy, that collective groan you hear just might be from people like me who are responsible for finding good talent.
So why do we test a Workforce Timekeeper configuration?
Ever just need a quick answer to a Kronos-related dilemma? How do you assign a default accrual code to a new employee? What happens when you get an error reading badge data? Need a script to get firmware versions for each device in a report?
So you are implementing your Kronos application. You've spent a lot of time working with your organization to ensure you have captured all the necessary information. Your configuration is moving along swimmingly! Your system getting ready to use and your change management and training plans are moving along. What did you forget? Do you know your system will work as designed? Did your configuration hit the mark?
As a reminder, Kronos released a technical advisory on 6/24/14 for Workforce Central® Suite v7.0. It's not a huge change; it simply changes the name of Workforce Operations Planner to Workforce Budgeting. This does NOT affect product functionality, but does change the user interface, and user documentation. The name change will be updated in the online help for Workforce Central beginning with version 8. If you can't find your Operations Planner - try changing your search to Workforce Budgeting.
Over the last few blog entries, we introduced the schedule group and pattern template. Hopefully these tools will be useful as you build schedules in Kronos Basic Scheduler.
When we last met, we discussed how to build schedule groups, and how to assign employees to them.
© 2014 www.improvizations.com