So why do we test a Workforce Timekeeper configuration?
So why do we test a Workforce Timekeeper configuration?
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?
I recently had the opportunity to work with a client that implemented a new HRPR system. Along with infrastructure changes they also had an interesting structural change that restructured all positions in their existing Kronos system. Those changes needed to be reflected in Kronos Workforce Timekeeper and Scheduler. They needed to expand the existing organizational hierarchy to allow for an additional level at the top of the structure and expand existing levels to allow for more characters. Post the change, scheduling and labor accounting can now be done with the added level. In addition, since there are more digits for level entries, it reduced the amount of level entries to go through for a transfer or employee assignment.
Although change can initially be cumbersome (based on the complexity of the request), some companies find it not only inevitable but beneficial. In my experience, changes can also be time sensitive for "live" systems. If you are already using Kronos, managers need time to continue to pay employees from the existing system; thus changes to production need to be planned well in advance. If you are a new Kronos customer, it can be less of a challenge as you do not have to consider historical information. Change complexity is based on the number of Kronos products, the amount of changes, and if it is made to a new or existing system. The good news is that Improvizations is quite capable of assessing then implementing change for both existing and new Kronos customers.
As an example, let's talk about two components that could require configuration changes: the Organizational Map and Labor Level structure. What could drive structural changes to these components? Although there could be many reasons (including those I mentioned in the second paragraph), the simplest reason is that the existing structure is dated. With the organization restructure, new HRPR software (even possibly a new Kronos Workforce HR Payroll implementation) may also come into play. The challenge presents itself when we consider the dependencies in the Kronos system that may have to be accounted for. When the Labor Level structure is changed, we need to analyze the impact on Labor Level Sets, Interfaces, Hyperfinds, employee assignments, data collection devices, past data, and perhaps custom reports. For Scheduling customers, when the Organizational Map is changed we analyze the impact on many of the same items (Organizational Sets instead of Labor Level Sets) in addition to other items (Schedule Sign-Ups and Time Off Requests). From there we develop a plan to implement change as well as a timeline (when the changes will occur).
How can we at Improvizations help you accommodate the ever changing Workforce? Or perhaps you are not looking at a full restructure for your positions and jobs but your company had some union changes... Let our expertise assist with not only implementing change, but also helping identify requirements for change and assist with adopting Kronos changes in your environment. Maximize the ROI from your Kronos Workforce Central Suite with change today! For more about change, see this article! For more Best Practices on change control, see this article.
A coworker and I decided to reward ourselves after a hard day’s work. You know – look for an oasis away from work where you can forget about everything for at least a little while.
We were in a steak house looking over a really great menu when we came across the 72 oz Steak Challenge. You have probably heard about these contests before, eat the whole thing and it's free. This was one of the most well defined contests I have ever seen. Seriously, just look at these rules:
We recently assisted a customer with a Workforce Central Timekeeper build for an additional server. After completion we wondered; was it really worth the effort? I would have to say a resounding yes. There could be several environments in addition to production. Several examples include training, development, or testing. Also, having a test system allows the entire organization to implement change on the fly while eliminating any risk to production. Sometimes it is also referred to as a sandbox. As we enter autumn, I like to think of having at least one additional Kronos server akin to having the first tree from a certain species available for landscape design. Having seen customers with two or even three Kronos systems beyond production, I’d like to focus on how just having even a single “mirror of production” a.k.a. "test server" could be beneficial.
How many times have we heard the old cliché don’t reinvent the wheel? Under normal circumstances the phrase usually applies as a standard catchphrase for many things in life. Per Wikipedia's definition: "To reinvent the wheel is to duplicate a basic method that has already previously been created or optimized by others". As it is one of the key sayings that have been used lately and one that I have enjoyed over the years, I felt it worthwhile to write about the particular topic when it comes to your Kronos pay or work rule configuration. The catchphrase can also be applied to configuring other areas of Workforce Timekeeper (display profiles, accruals, or <your idea here!>).
A customer of ours has engaged us to help them re-engineer their Kronos timekeeping and scheduling environment. We recently suggested to them that upgrading to the latest version of Kronos from their slightly earlier version might be desirable as part of the project already underway. Although some leeway was granted to do a test upgrade and assess the pros and cons, the idea was nixed before a formal review was completed.
Most companies use less than 50% of Kronos workforce management software functionality. How much utilization do you have?
Would you benefit from a process that helps your organization verify your Kronos configuration and associated processes to ensure you are making the most of your Kronos application?
Learn more or download The Case for Gap Analysis.
Companies invest substantial labor and financial resources to deploy workforce management software Why do so many projects fail?
Do you know the best practices - and the pitfalls to watch for - to deliver a successful project?
Our white paper, Successful WFM Strategies, explores effective steps you can take to deliver a successful project.