Loading

Subscribe to this Blog

Your email:

Are you preparing for an implementation or upgrade?

Kronos Implementation Strategy

Download the WFM Implementation Strategy White Paper

About Bryan

Resume Pic of Bryan deSilvaMusician & Yin Style Bagua practitioner. Over twenty years of software implementations and upgrades, project management, systems and applications development experience with a current focus on ADP eTime & Kronos Timekeeper/HR systems implementation. 

The "Kronos Guy" Blog

Current Articles | RSS Feed RSS Feed

A New Kronos Version That Demands An Answer

  
  
  
  

Kronos has released a major upgrade. The features look exciting, the new reporting functions are enticing and - ah...the dilemma.  To upgrade or not to upgrade? There seems to be an even divide on the reasons whether a company chooses to upgrade or not.

Two weeks ago I got a call from a company with a version of Kronos that was so old (how old was it?) that we could only find one person who had actually worked with this version. It was from 1999. It had never been upgraded.

Clearly then, some companies go with the "if it ain't broke, don't fix it" methodology.

Is this an overall good business strategy?

It can be. If you have a good, solid product like Kronos Workforce Central, just use the bare minimum basic functionality, and don't need to take advantage of the additional functionality that has been added over the years and don't need to change your infrastructure...then this might work for you.

However, this can also result in your HR and Payroll Manager not being able to sleep at night. Tell me, what happens when the system goes ‘clunk in the night'?

There are solid reasons why our clients should upgrade. Although every client is different, there are some universal reasons to consider upgrading your version of Kronos. Each day this week, we'll discuss one reason to consider upgrading.

Keeping Current

When a software company upgrades a product as complex as the Kronos suite of products, you can bet your bottom dollar that they have involved many of their users. They also have access to every technical support call reporting bugs or other deficiencies in the system. A new release will have bug fixes and additional features that may benefit your organization. For example, it might eliminate manual processes, reduce processing times, or improve interfaces and workflow for your users.

Coming in June of 2009, Improvizations is launching the Upgrade Studio, a process that your company can use to determine if and when you are ready to upgrade to Kronos 6.1. We will work with you to create a comprehensive upgrade plan so you have ALL the variables in place to plan for your next upgrade. Want to know more?

Comments

Well, If Kronos software is not upgraded, you lose kronos support after certain time. In that sense it is kind of mandatory. 
 
Again if you upgrade to DCM 6.1, I am not sure if old clocks (480F)are compatible with it.
Posted @ Wednesday, April 29, 2009 7:09 AM by Gajanan Nadkarni
Thank you! I agree - Kronos kind of has a "hafta upgrade" built-in. You are right; compatibility issues and infrastructure are areas that can be completely overlooked and derail an upgrade process. Appreciate your input.
Posted @ Wednesday, April 29, 2009 1:35 PM by Amy Doughten
Post Comment
Name
 *
Email
 *
Website (optional)
Comment
 *

Allowed tags: <a> link, <b> bold, <i> italics