* Kronos** daily interface into Kronos*** create a staging table in kronos;
all staff, new hires, changed hires, changes...are included
reference tables kept by payroll staff used for the feeds from the staging areas into Kronos**** leave status -> drive licenses
which payroll to apply -> 100s of payroll by union, students, temps, non CU people...***** data elements are changing because data coming in is different from Workday and because we want that to use the new ones. = remediation work.
record number is needed in Kronos - drives how people are paid and differentiate between different jobs. Position numbers are not a one-to-one match to WD numbers. No field for record number is additional job numbers.
The logic for employee record number and primary job NEEDS TO BE CONSISTENT LOGIC ACROSS ALL INTEGRATIONS.
Integrations Today:**** Employee Data Feed:***** From Workday: Extracts employee demographic data from PeopleSoft and passes it to Kronos
Into Kronos: Reads employee extract and populates Kronos import tables
Labor Level Feed***** From Workday: Extracts Department data from PeopleSoft and passes it to Kronos
Into Kronos: Reads labor level extract and populates Kronos import tables
New Enhancement to include supervisor to employee association (see below)
FLSA Validation***** From Workday: Process Overtime for Kronos Employees
FLSA Report***** From Workday: Report by employee id and employee rcd number all earnings affected and not affected by FLSA.
Summarize Time***** From Workday: Summarize time for Colts/Kronos employees
Big business decisions to be made:**** payrep group - drives security and access, exists in workday but we have to decide of we want / can use it.
empl record: for uniquely identifying jobs (The Multiple Job issue) in Kronos and for Kronos to be able to send updates to Workday. Rules on primary job have to understood and used by Kronos.
cost center field: definition and use: Kronos and Workday both have this field and the definitions are different and have to be reconciled. Could kronos cost center be in Workday? ***** Statler example: need to know WHERE the job was worked and where the costing went on the same job.
Supervisor to employee association : are defined in Workday and not in the existing feed from PS, and new logic is need to present it and put it on the employee record. This would be an extension of the labor level interface.
role on org in Workday: can you have a payrep and a supervisor both defined in Workday? yes. knonos needs the payrep and the supervisor. Supervisor is adefaultrole by virtue of the WD application everyone gets one. Payrep is a role that can be assigned. Today in Kronos, hand entering payreps. When they move or change not keeping up with the changes.
assumptions:**** workday calculated FLSA with Release 15 (Nov 2011)
colts tables are left alone (and their use by PS) until workday is deployed;
Kronos will integrate directly to WD with no intermediary staging tables in PS or other systems.
some CIT talent is required for Kronos/Workday subproject***** DBAs, sys admins... to set up
Analysis for the Remediation of Kronos for Workday**** Answer the above questions
Determine what enhancements, changes, etc are needed
Kronos Corp to assess if the WD configured integration as delivered could be used with the CU installation of Kronos.
minimum: ***** 120 hours and time data back in on workday side