Skip to content

Do You Have Kronos Ingenuity?

July 21, 2014
ISEE-3 Reboot Project

ISEE-3 Reboot Project

Yesterday I read a fascinating New York Times article about how a small team of volunteers and aerospace engineers have crowd-sourced nearly $160,000 in financing to rescue a spacecraft launched from earth in 1978, but since abandoned by NASA. The bootstrapping team signed an agreement with NASA to take over the International Sun-Earth Explorer-3, or ISEE-3, and so far have been able to: contact and control the spacecraft, obtain telemetry data on things like position and speed, and fire up the ISEE-3’s engines. The team wrote software to replace the functionality of old ground control hardware, long lost to time. They’re still trying to attain consistent control of the engines, and when they hit problem solving obstacles, they use their Twitter account to ask for help. Then they get inundated with responses from thousands of fans and supporters. I found it an inspiring story. The scope of human ingenuity is limited only by our imagination.

The tale got me thinking about our thousands of customers and millions of users. I wonder how they’re extending the utility of our solutions… If you’re supporting/using a Kronos system, please comment on:

  • What unique interfaces to other systems have you created?
  • Have you written any interesting custom code as “bolt-ons” to Kronos?
  • What unique reports have you designed?
  • Have you used the broad configuration options in Workforce Central to track things other than time?
  • What else have you done with Kronos that you consider unique or cool?

Also, if you’ve worked with customers creating these unique solutions, let us know in the comments what you’ve seen/done. I’m sure there are some amazing customer built solutions out there. I’m just not sure my SETI signal is strong enough to reach them.


2 Comments leave one →
  1. July 25, 2014 9:46 am

    Living in Orlando usually hurricanes don’t do much damage since Orlando in the middle between the Gulf Of Mexico and the Atlantic Ocean. But back in 2004 we had 3 that traveled right through Orlando. After those storms a need came up about finding a better way of reporting to FEMA for reimbursement. Kronos databases table are very complex but Kronos creates views for it’s customers to work with. We devised a system to use those view to pull data out of Kronos. Because FEMA would only reimburse for overtime our budget department developed project numbers for the categories of work done in recovery from a storm. In Kronos we used a labor level called project to track to assign the hours to the specific category. The employees time was entered in the normal way the do it daily either through manual time card edits or timeclocks. The manager assigned the project and out IT staff created queries inside a FEMA application to forms that were approved by FEMA. The FEMA application also linked to another system that equipment used for disaster recovery cost for equipment rental could be reimbursed by FEMA. The equipment data was linked to a specific employee and then the linked to Kronos to verifiy the employees was actually working at the time the other system reported they were using the equipment. One good thing is we haven’t had to use this app since 2004 (No storm with damage). Although one year we did have a storm that caused a bit of flood damage but we didn’t have enough damage to qualify for FEMA reimbursement so we use it for a test.

    • July 25, 2014 9:52 am

      Jake, thank you! That’s what I’m talking about! I’ll keep on this so Kronos customers like you can share their ingenuity!

Leave a Reply

%d bloggers like this: