Page History

...

1. Kronos (and remediation)
2. KFS 
3. ELM
4. windstar
5. taleo
6. APDB (to match exactly the current ADABAS ready files so there is no transformation work to do by Cornell)
7. United way (and/or advice to a system to migrate to)
8. Traffic 
9. Statler - tips
10. the set of existing web service calls listed on the integration sheet
11. the set of data extractions that will match the current HR/Payroll extracts for HR/Payroll Dm at Cornell. Refer to the  Datamart list of PS tables.

Cornell's To Dos:

1. HR Core team: Clarify organization representation status, options and intent. This will help Kronos, BI and identity management impact assessments.
2.  
3. Identity Management Team
   1. Clarify Share facts on the use of org data by Active Directory
   2. Clarify Share facts on the use of Reference Groups.
   3. Estimate the impact if the same structures are in place in Workday so that it is mainly a testing and integration effort and not a complete replacement of all tree structures.
4. Project Management and BI Team: 
   1. Define 2 BI Discovery projects
      1. Near term (: 100% oriented towards deliverables on day 1 of Workday go-live)
      2. Long term (term : very strategic and tying into  goals that remediate all warehouses, models, and reports, and provide cross functional and longitudinal reporting and is in alignment with the EDW efforts and Budget office vision for BI)
   2. Provide Workday information to support their estimate work, 
5. #* BI Team: Supply to Workday the sql and tables and any other documentation that are currently used for the HR/Payroll Datamart extractions and for extractions from the PEopleSoft Replication database that supplies other datamarts, per the diagram supplied by Dave during the BI session. (Refer to the attachments from the BI Session.)
6. Applications leads and functional owners: Review Workday's estimates in detail when they come in

...