WORST FIVE REASONS TO UPGRADE WORKFORCE TIMEKEEPER (at least right now)

#5:  KRONOS NO LONGER PROVIDES SUPPORT (SERVICE PACKS) FOR MY RELEASE.

Kronos only provides service packs for the current release and two prior releases. This doesn’t really mean they (Kronos Global Support) stops supporting their software after two releases (eg: You are on 6.0 and the latest is 6.3 of workforce timekeeper) but it does mean they are technically off the hook for software defects on your version. (According to their policy, they are free from the defects clause on a previous release the minute they do another release even if it still isn’t fixed in the newest release.) As a practical matter this is rarely an issue if things have been chugging along. Our customers do, however, see varying levels of motivation from KGS depending on the version and the type of problem. Our advice is YOU are the customer and pay for support. 9 times out of 10, polite escalation will get issues with prior releases resolved.

#4: WE ARE UPGRADING OUR PLATFORM TO 64-BIT OPERATING SYSTEM

This would mean you are on Kronos WFC 6.1 or earlier and are considering 6.2 or 6.3 to make your infrastructure guys happy.  Really?  I thought software was intended for the users not the IT folks. This is similar to #5 in that ‘someone said so’ and that is a very limited view of life cycle planning software and change control in an organization. One of the huge risks in this myopic requirements/opportunity stance is that you too often just uplift and not improve or even plan to improve your USERS lives. This almost always sweeps over configuration and business process problems and creates barriers to real improvement down the road.

#3: THERE IS A BUG THAT CAN ONLY BE FIXED IN THE LATEST RELEASE

Check this one out VERY carefully.  First re-read #5 above. Then remember the definition of an upgrade: “Take old bugs out, put new bugs in”. Okay, this is an overstatement of the reality that while an upgrade may in fact fix your problem it would bring forth a whole new set of issues to be dealt with.  These may be bigger, or more than you are prepared to handle under the auspices of ‘patching’.  The cure can often be more painful than the disease. Do a full assessment of all the issues (clock upgrades, user training, interface changes) brought about by going to another full release. Never treat a Kronos release like a service pack.

#2:  IT COSTS MORE TO WAIT TOO MANY VERSIONS TO UPGRADE

Actually it tends to cost less.

#1:  WE WANT THAT NEW FEATURE IN THE LATEST RELEASE

On the face of it, this is the whole reason we upgrade software is to get new features. I could go with this if most of the installations out there were a marriage made in heaven of good pay policies implemented in a maintainable and scalable structure. But there is often sooooo much low hanging fruit in every existing installation that a new car smell just can’t compare to -- from both an immediate ROI as well as a strategic move along a well-planned road-map. Also, double check the pre-requisites to get that new feature to work with your configuration. It may entail a lot more foundational moving that, if looked at in the big picture, should come after some of your other deferred maintenance. You know-- the things you’ve been promising the users, finance, and the department of labor auditor.