Excerpt |
---|
Notes concerning the integration with Kronos. |
Kronos Integration as is
...
- Basics as is:
- today there is
...
- a staging table in kronos;
- all staff, new hires, changed hires, changes...are included
- reference tables are kept by payroll staff and used for the feeds from the staging areas into Kronos
- a staging table in kronos;
...
- leave status drives Kronos
...
- 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
...
- a position record number is needed in Kronos
...
- as it drives how people are paid and differentiate between different jobs. Position numbers are not a one-to-one match to WD numbers.
...
- The logic for employee record number and primary job NEEDS TO BE CONSISTENT LOGIC ACROSS ALL INTEGRATIONS.
- Purposes of Integrations Today:
- Employee Data Feed
...
- From
...
- peopleSoft:
...
- Now Extracts employee demographic data from PeopleSoft and passes it to Krono
- Into Kronos: Reads employee extract and populates Kronos import
...
- table
- Labor Level Feed
...
- From PeopleSoft: 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: We might be able to use Summarized time for Kronos employees
- Big business decisions to be made
...
- Payrep groups - these groups drive
...
- security and access
...
- . They exist in workday but we have to decide
...
- if we want / can use it.
...
- empl record: these are used 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: we need the understand the definition and use
...
- in both systems as Kronos and Workday both have this field and the definitions are different and have to be reconciled. Could kronos cost center be in Workday?
...
- Maybe.
- Statler example:
...
- Management needs to know WHERE the job was worked and where the costing went on the same job.
- Supervisor to employee association : these are defined in Workday and are not in the existing feed from PS
...
- so new logic
...
- may be needed 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:
...
- knonos needs the payrep and the supervisor. Apparently we can we have a payrep and a supervisor both defined in Workday
...
- . Supervisor is a default role by virtue of the WD application everyone gets one. Payrep is a role that can be assigned. Today in Kronos
...
- we are hand entering payreps. When they move or change there is always an issue of 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
...
- , such as DBAs and sys admins, to set up environments
- Analysis for the Remediation of Kronos for Workday
...
- is required to answer the above questions
...
- , and determine what enhancements
...
- and changes
- Kronos Corp
...
- should assess if the
...
- Workday configured integration as delivered could be used with the CU installation of Kronos.
...