1 / 31

CIO Council Meeting HRS Project Update

CIO Council Meeting HRS Project Update. 10/21/2010. Agenda. Project Overview Testing Data Collection / Conversion Reporting November Road Shows Project Concerns. Plan. Build. Test. Deploy. Support. HRS Project Phase Descriptions.

irina
Download Presentation

CIO Council Meeting HRS Project Update

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. CIO Council Meeting HRS Project Update 10/21/2010

  2. Agenda • Project Overview • Testing • Data Collection / Conversion • Reporting • November Road Shows • Project Concerns

  3. Plan Build Test Deploy Support HRS Project Phase Descriptions Each release will follow a proven approach for implementing PeopleSoft functionality as outlined below and includes a list of key deliverables for each phase. • Project Plan & Timeline • Resource Estimates • Budget • Requirements List • Fit/Gap Decisions • Campus Coordination Plan • Communications Strategy • Training & Support Approach • Development Infrastructure & Database • Configured System • Modifications , Interfaces, Workflows • Reports & Views • Conversion Programs • Cleansed Data for Mock Conversions • User Procedures • Training Content • Work Process Analysis • Test Scripts • Security Configuration • Cutover Schedule • Trained Users • Converted Data • Code Migration • Deployed Procedures • Readiness Assessment • Secured Production Database • Help Desk Support Procedures • Redesigned Processes • Configuration Documentation • Functional Specifications • Technical Specifications • Revised Role Descriptions • Security Specifications • Training Infrastructure & Database • Integration Test Results • Systems Test Results • Performance Test Results • Parallel Test Results • Mock Conversion Results • Acceptance Test Results • Production Infrastructure & Database • Help Desk Issues List • Post Production Review Results • Follow up Training & Coaching NOW

  4. Testing

  5. Testing Scope

  6. Testing Scope continued

  7. System Test Closure Report

  8. System Testing – Lessons Learned • The exit criteria for System Test were developed in July and at the time seemed rational and reasonable • In early September when we met the exit criteria we lacked confidence as a team in our true readiness to call this testing complete • We had several meetings with subset of the Decision Council for guidance and determined: • Extend System Test by one week (end date 10/8) • Start Integration Test – Iteration 2A on 10/11 • Continue to evaluate and track Test Faults needed for Iteration 2A

  9. Testing Timeline

  10. Other Testing Phases • Performance Testing • Performance testing tool installed and configured • Test scenarios / scripts being developed • Targeting testing of online, batch, reports, interfaces • Parallel Testing • Team identified and approach drafted • Campuses identifying data for comparative analysis • User Acceptance Test (UAT) • Approach defined, tentative dates established with campuses

  11. Data Collection / Conversion

  12. Mock Conversion 3 Results • Completed on 9/24 • Data used for Integration Testing – Iteration #2 in HRWORK1 • Conversion Scorecard: • Document success rates for conversion using multiple methods in a variety of breakdowns by campus and functionality. • Available on the Intranet: • Log-In to the Intranet • Click on Data Conversion and Cleanup News • Click on the “Open the Validation Scorecard” at the bottom right-hand part of the window Mock Conversion 3 Scorecard

  13. Mock 3 Scorecard - Summary

  14. Conversion Current Phase • Currently in the middle of Mock 4 • Converted Data will be used for • Integration Testing – Iteration 3 (in HRTST) • Parallel Testing • Performance Testing • Start Date:10/4 • End Date: 10/18 • Longer Conversion window compared to previous mocks to ensure better quality of converted data.

  15. Data Cleanup

  16. Data Cleanup – Priority 1 Errors • As you can see there was a recent spike in Priority 1 Errors: • Decreased from 82% to 62% between August/September • Main Causes: New Hires and the HR Org. Department Reorganization • But over all percentage is back up to 84% and continues to go up!

  17. Data Collection: Schedule • Expected time-line for completion • Total percent of data collected (as of 10/1)

  18. Clean-Up & Collection Update • Login to the HRS-IntraNet to check on progress with Data C&C tasks on your campus. • https://intranet.hrs.wisc.edu/Content/hrs_conversion.aspx • Select Priority and Campus from the drop down menus

  19. Reporting

  20. Reporting Sources • HCM = "live data" - HCM (Human Capital Management) is the live production system that contains the live transactional data. HCM is the data source for reports delivered with the PeopleSoft system (referred to as "delivered reports“ • EPM = "day-old data" - The EPM (Enterprise Performance Management) Data Warehouse will extract data from HCM on a nightly basis. EPM will be the source for most custom reporting needs, since most reports do not require "up to the minute" data.

  21. EPM – The Data Warehouse • The EPM Data Warehouse simplifies the difficult tasks of finding, consolidating, and preparing information for distribution. • The EPM data warehouse serves as a platform for basic queries and reports, and also as a data feed for supplemental systems. • Access to EPM is provided through EPM Data Views

  22. EPM – Data Views • For Release 1, the HRS Data Warehouse team is developing between 60-70 data views that will simplify your ability to access HRS data. The data views offer a number of advantages over querying the database table structures directly: • EPM (and HCM) contain very complex relational database structures • EPM data views simplify data access by performing complex joins and supplying code/description data pairs from lookup tables • EPM data views will be available for HRS "current data" PLUS "historical data" • There are separate EPM data views for secure vs. non-secure data

  23. EPM – Data Dictionary • The EPM Data Dictionary is a document that details the EPM Data Views and the data that they contain. • It will be invaluable for understanding the EPM Data Views and how to utilize them in queries and reports

  24. R1 Reporting Development Status As of 10/11: • Development of all 79 R1 custom or modified reports is complete

  25. R1 EPM Development Status As of 10/11: • Development of all 47 EPM requirements is complete • EPM Data Dictionary published on the HRS Intranet website:https://intranet.hrs.wisc.edu/Content/hrs_reporting.aspx • Two student helpers will aid in enhancing the Data Dictionary documentation • Data Dictionary updates to be published on a monthly basis, targeting completion in 2/11

  26. Reporting/EPM - Next Steps • Reporting – Release 1: • Identify and document R1 custom/delivered reports for Cypress distribution • Address Test Faults • Reporting - Deployments 2-13: • 77 custom/revised reports identified for Phases D2 - D13 • For the 42 reports targeted for D2 - D4, development to be complete by the end of February • 13 reports have business requirements completed, and 20 others are in process

  27. Reporting/EPM - Next Steps • EPM: • Continue development of Data Dictionary & sample EPM queries • Develop & deliver Training for EPM / Data Dictionary / PSQuery • Develop & test Batch Scheduling for EPM ETL (Extract/Translate/Load) programs • Prepare EPM environments for Integration Testing & Supplemental Systems testing

  28. November Road Shows

  29. Road Show – Purpose and Dates • The purpose of the road shows is to get the HRS Project team in front of the campus staff to demonstrate the modifications made to the system and to communicate to the campus staff critical information to help them prepare for implementation • November 9-10 in Oshkosh • November 16-17 in Eau Claire

  30. Road Show Agenda Day 1 8:30 – 4:30 • Welcome • State of the Project • My UW Portal and Employee Self Service • HRS User Support • Security and Data Governance • HRS Communication • Human Resource System View • Each functional area lead will review the modifications and business processes for that area • Overview of HRS Timeline Day 2 8:30 – 4:30 • Human Resource System View • Each functional area lead will review the modifications and business processes for that area • EMP/Reporting Overview • Data Collection, Conversion, and Cleanup • Workshops • Query writing • Benefits enrollment forms • Communication strategies • PAGs

  31. Project Concerns • Retention of key staff members • Uncertainty of future roles • Attrition of key staff members will require re-staffing to meet deliverables

More Related