KRONOS 3 Project

1
KRONOS 3 Project

• Sherri Hayes
• Tyler Stott

2
Background

• Kronos is a time clock software. Perdue uses it
  to track employee time at work.
• The Kronos 3 project is a software upgrade Perdue
  started in early 2006.
• The upgrade will track the absence occurrences of
  employees a process currently done by hand.
• The project ended up being delayed by 18 months
  due to a snag in the software.

3
Background Continued

• Kronos is used in 60 locations including 18 large
  plants.
• 22,000 employees rely on the Kronos software to
  ensure they get paid.

4
The Problem

• Plants running Kronos have Human Resource staff
  manually entering absence information into
  Peoplesoft to track absence history and then
  prepare the appropriate coaching forms. Absence
  information is not readily available for all
  shifts. There is no standardized absence or
  manpower reporting.

5
Stakeholders

• Executive Sponsor
• Business Sponsor
• Business Lead
• IT Project Manager
• Customers Plant Kronos locations
• End Users Kronos Users and HR
• Additional support required from Kronos

6
Scope What needs to be done

• Replace current time clocks with the new 4500
  model.
• Current time clocks are no longer manufactured
  and incompatible with the new software.
• Upgrade current Kronos software to the Timekeeper
  5.1 version.

7
Project Plan
Baseline
Clocks
V5
Kronos 3
8
Hardware Replacement

• The clock replacement was successful and was
  completed ahead of schedule.

9
Software Upgrade

• The software was completed but Perdue soon
  realized that the vendor removed group scheduling
  functionality in the new version.
• The upgrade was forced to be put on hold until
  Kronos resolved the issue.
• Kronos agreed to release a new version
• Perdue agreed to be apart of the Beta program to
  be released April 2007.

10
Cost to the Company

• The project was delayed 18 months.
• The company lost 200,000 dollars on licenses they
  purchased for version 5.1.

11
Result

• The beta was tested through May 2007 and the new
  version 6 is currently being implemented and is
  scheduled to be completed by September 2008.
• The project as a whole helped to strengthen
  vendor relations between Perdue and Kronos.

12
Lessons Learned

• Critical to have committed business resources for
  a project.
• Project team members ended up creating a work
  around for the version 5.1 software until the
  version 6 was released.
• Develop a strong relationship with vendors.
• If the vendor knew what Perdue needed maybe the
  delay would have been avoided.

13
Lessons Learned Continued

• Importance of escalating an issue to all the
  stakeholders so they understand an issue that
  could delay a project.

14
References

• Stacey Norton Perdue Farms project manager.
• Kronos www.kronos.com