The following short Q&A session was conducted with Ray Ney, Workforce Solutions Engineer at Improvizations. He responds to five common questions regarding the Java update for Workforce Central. This is a continuation of the previous article dealing with the Java Update and how it affects WFC users. The "summary" Ray mentions below is a Kronos Super Search article called "Java JRE Security Issues Q&A" (Kronos Doc ID: KB45534) published on 8/20/13. It was updated on 12/10/13.
So 2013 is gone... (and may I be the first to say how weird it is? I mean, when I was a kid I thought it would be cool to live to the year 2000!) What do we have that we can be grateful for? Or should I say, thankful for? I know I missed the Thanksgiving holiday for this post, so hopefully this image will tie that and Christmas together nicely. So let's look at some of the things to be thankful for this year:1. Leadership - Kronos continues to push forward in the field of workforce management. Ten years ago we were happy with Workforce Central. Time and attendance with a dash of scheduling. That's all we really needed. Right? Wrong. Kronos has greatly expanded their suite of products to include HR/Payroll, changing the frame of reference from merely Kronos Attendance and Kronos Leave Management to Workforce Absence Management, and improving from the simplicity of Data Collection Manager to the more robust Workforce Device Manager for the newest terminals we use today. Some of these changes have been simple, some more challenging, but Kronos has worked to keep with changing technology (and in some cases, ahead of it) to provide for the needs of their customers. 2. Commitment - Kronos has shown a high level of commitment to both the products they produce and their customers. It is impossible to do business today without creating some frustrations with your customer base, but by and large, Kronos has striven to provide solutions that meet the demands of their customers in many markets. Kronos is committed to their products, working to fix what is wrong and to provide new features and functionality. 3. Advancement - I am providing a couple of questions to describe the idea of advancement. Is your organization better for having Kronos? Can you do more with less? Can you do it with a higher level of efficiency with fewer mistakes? Most commonly the answers to these questions are a resounding "Yes!" Kronos has taken an industry and developed it, helped it grow, and thereby forced their competitors to improve their product as well. The industry of Workforce Management (even if Kronos created the name!) is better because Kronos is there. By providing leadership, commitment, and technological advancement, Kronos works hard to improve the workforce management space, and we appreciate it. Now, how can we work together with you to successfully improve your Kronos ROI?
Oracle released Security Alert CVE-2012-0422 to address two vulnerabilities affecting Java in web browsers. The security vulnerabilities only affect Oracle Java 7 versions. Oracle is recommending that the updates in this Security Alert be applied as soon as possible. This to avoid the possibility of unknown attackers entry into your computer systems through malicious browser applets. In response to this upcoming update, Kronos issued a technical advisory titled: "Workforce Central and JRE 1.7 – Mandatory Action Required." What does this mean for Kronos users and your Java Runtime Environment?
So many risks in the Kronos™ implementation project -- so little time. Wikipedia identifies project risk as something that "can be defined as an unforeseen event or activity that can impact the project's progress, result or outcome in a positive or negative way." The question I have for you is:
There have been two or three Kronos Timekeeper customers that I have had the opportunity to work with this year that were suffering from the same challenge. See if you can pick it out:
One of the big, big pushes from KronosWorks this year was Kronos Workforce Social. It was mentioned heavily during Aron Ain's welcome announcement, and several sessions were also dedicated to the topic. The guest speaker was the "Award winning expert of chaos and change" Jeremy Gutsche. Jeremy's high energy oratory was well matched to this new Kronos offering.
I'm often asked when a team should move new features into Production. Or, how do you know that a Kronos configuration is "good enough"? This is a simple question that deserves a simple answer. I answer the question with a question. "Is it right?"
Customers spend a lot of money implementing and/or upgrading Kronos, so it only makes sense to get as much out of it as possible. So, what else can we do with it? Do we total the data and put it in a spreadsheet? Is it better presented as on a Report, in a Genie, or as a CSV file? What information is going to be beneficial to extract; what’s better to put in an email? What else can we do with Genies?
Skills and certifications are a useful Kronos feature that allows organizations to schedule employees more effectively. By using skills and certification, a business can better serve its customers or a hospital can ensure that departments have nurses with specific certifications. Let’s start by defining skills and certifications, and then talk about where Kronos stores this information, and finally, how it is used.
Change is constant. Right, we all know that. So what's the big deal? Firstly let's get some definitions down for this series as these topics cross one another all over the place.
© 2014 www.improvizations.com