Current Kronos users with an issue should contact their department leave clerk. Leave clerks may escalate issue to the ITCS Help Desk.
When submitting a help ticket, select “Administrative Systems” from the ticket menu on the main Help Desk Web page, then select “Kronos” under “Category.” Please provide any relevant information about the problem.
For general Kronos Project questions or information, please email the ECU Kronos Team at email@example.com.
All employees who track hours worked, leave taken, or both, will use Kronos.
With an increase in state and federal legislation and compliance concerns related to wage and hour rules, it is in the best interest of the university to standardize and automate time and leave-keeping functions. To assist in this standardization and automation, ECU purchased Workforce Timekeeper from Kronos Incorporated, a proven leader in workforce management. This software package has been adopted by the university as the time, attendance and leave keeping system of record for employees who track time, as well as employees who are granted or earn leave. Kronos is expected to provide university employees an efficient, effective tool for tracking, paying and reporting these key employee data values.
Kronos will allow reduction in costs, improvement in technology, utilization of employee self-service tools, real-time flow of information, and support of the university’s paperless initiatives.
The Kronos project is sponsored by Dr. Rick Niswander, Vice Chancellor for Administration and Finance and supported by an Executive Steering Committee. Steering Committee membership includes representation from across campus and incorporates employees at a variety of levels within the university.
Ownership of the system resides in the Department of Human Resources under Melissa Bard, Associate Vice Chancellor for Human Resources, with ownership for pay-related system components belonging to Payroll under Letty Lalu, Payroll Director. Payroll resides within Financial Services under Ann Jenkins, Associate Vice Chancellor for Financial Services.
A Core Project Team and content-specific specialty teams have been established to work on various aspects of the system’s design, configuration, implementation and application at ECU. Questions, challenges and decisions derived in these groups are presented to the Steering Committee for feedback and resolution.
To learn more about the organization of the Kronos project team, please see the organization chart at: www.ecu.edu/cs-itcs/kronos/upload/KronosOrgChart.pdf.
Upcoming phases of the implementation are contacted individually and provided available information regarding timelines for “going live.”
The current Kronos timeline is posted on the Kronos Project website here: www.ecu.edu/itcs/kronos/.
Specific employee groups have been identified for inclusion in Kronos. To determine if you will be using Kronos, determine your employee type. One way to find this is by logging onto OneStop at: http://onestop.ecu.edu. At the top of the page, select“Profile,” then “Employee Profile” in the left navigation bar. Find your employee type under “Employment Information” next to “empl class.”
To view employee types that will be using Kronos, please view the Project Scope document.
Banner passes information to Kronos for each employee. Banner will remain the system of record for employee and job information. Kronos will use information from the employee and job records in Banner (Employee Class, FTE, Leave Category, Years of Service, and Effective Dates) to determine the appropriate Pay Rules and Accrual Profiles in Kronos. An interface runs each day from Banner to Kronos to add and update employee information. Employees maintain their Kronos Timecard by recording time and/or requesting leave to reach expected weekly hours. Managers evaluate and resolve any “exceptions” or timecard problems each day. Managers approve Requests for Time-Off as needed. At the end of the Pay Period, both the employee and manager approve the timecard. The Departmental Super User must Sign-off the card to close the period. Payroll will collect data for the closed pay period and use it when processing payroll.
Nonexempt employees may access punch recording features via Kronos time clocks and Kronos Timestamp (see images below). All employees may access timecards and leave balances (if applicable) via a workstation with ECU network access.
The login for Kronos is kronos.ecu.edu. Use your PirateID and passphrase to log in.
Permanent nonexempt employees will log time in and out at the start of each day’s shift and at lunch using a timeclock or workstation with Kronos Timestamp. In addition, permanent nonexempt employees may record non-regular hours or premium pay types, request time off, track leave, and will approve and submit timecards each semi-monthly pay period.
Exempt employees will populate their regular schedule, request time off, track leave, record certain non-regular hours, approve and submit timecards each semi-monthly pay period.
SPA/CSS temporary employees will log time in and out at the start of each day’s shift and at lunch using a timeclock or workstation with Kronos Timestamp. In addition, employees will approve and submit timecards each semi-monthly pay period.
Student employees will log time in and out at the start of each day’s shift and at lunch using a timeclock or workstation with Kronos Timestamp. In addition, employees will approve and submit timecards each semi-monthly pay period.
12-month faculty members will track leave, approve and submit timecards each semi- monthly pay period.
Kronos training will be offered! Training will be scheduled around each department’s “Go Live” date.
Visit the Human Resources website for online training materials.
Kronos requires a browser and workstation Java installation. The browser and Java version must be certified as compatible with the production version of Kronos. Kronos is highly flexible with Java and browser versions and generally workstation users experience limited technical issues accessing the system. Departments with specific Browser or Java version issues related to other software packages should bring those particular needs to the attention of the Implementation Team during a department’s “Go Live.”