Notes: 

• There are 160 tables from Peoplesoft; deltas go daily to replicator
• There are a number of impacted dms / mini marts stewarded by CIT that haven't surfaced as impacted by HR/Payroll until we saw Dave's daigram
• Some have extensive impact and other have minor impact
• In all cases shown in the diagrams data is moved/copied, transformed and inserted into those tables
• There is no clarity (written, definitive statements) from the Workday project on the representation of level 9s org data
• All users of the marts will have to be the ones to explain how the various org roll ups work and why they are needed.
• There are various possibilities of getting the representation done in Workday:
  • custom  fields
  • 'containers'
• IN any case, the department tree is used broadly in the feeds from PS HR/Payroll

Big questions:

• what are the data conversion implications of org data?
• what are the implications of various Workday org representations and transformations from that to the pre-Workday org structures and representation?

Things to do:

• In an approved and scheduled BI for Workday Discovery project:
  • categorize the impact in terms of size and complexity and impact/risk
    • feeds/transformations
    • reports
    • models
  • decide who owns talking to campus about downstream impacts / campus extracts and uses and their own reports

• • make sure time collection is included in reporting needs (it's not just HR)

• • elaborate on the diagram with...
    • the basic purpose and use of each DM
    • owners and users of each DM
    • data extracts, transformations, and extracts for each DM
• For Workday to do:
  • estimate the work to extract the same data now taken out of PeopleSoft (the 160 tables' worth of data)
  • map out the canned Workday jobs extract with the PS jobs table used for 80% of the right hand side of the diagram
  • supply a meta data model (fields definitions,types, uses, examples of fields)
• For analytical work in the discovery project:
• define minimal functionality
• define historical longitudinal reporting
• simple ad hoc access to an extract and PAIDS data
• updated APDB reporting solution
• align efforts in HR with efforts in other topics -> keep enterprise warehousing in mind.
• workday: delivers exports in a 'flat manner'
• In WD everything is position based.  Vicky, Patrick and Tim roll up to Steve.  Put a supervisor container in front of Steve and then CIT Applications can roll up to CIT Applications.  The supervisor container is not included in the roll up. And, then use multiple containers for CIT and also for dual appointments.
• GET ETAs on all Workday numbers
• Notes:
• Workday Project Deliverable
• research outside solutions
• gaps
• longitudial
• compliance
• Enterprise model - for new work
• acceptable day 1, day n
• remediation - see picture
• Need overall BI strategy for project
• 2 discovery projects
• day 1 discovery project
• end goal discovery project
• each would have subsequent implementation work
• Need data model from Workday
• Need sponsor approval of what is needed day 1 (dodds, opperman, elmira, destefano)