1 / 13

Human Resources Front End

Human Resources Front End. (HRFE). Project Overview. University Implemented Banner ERP in December 2003 Creating increase in data elements Increase in end to end processing time HR/Pay Advisory Group Created in 2004 Analyze usability of ERP system

shiro
Download Presentation

Human Resources Front End

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. Human Resources Front End (HRFE)

  2. Project Overview • University Implemented Banner ERP in December 2003 • Creating increase in data elements • Increase in end to end processing time • HR/Pay Advisory Group Created in 2004 • Analyze usability of ERP system • Recommended an ITPC Project to design a new human resources front end interface

  3. Project Overview (cont.) • Oversight Committee Formed • Composed of university Vice Presidents, Associate Vice Presidents, and campus Provosts • Approved the functional specifications and funding for a new ITPC project (HR Front End, ITPC-0175) to execute the coding, training, and implementation of the HR Front End Application (HRFE).

  4. Key Departments • Project Jointly Managed • Information Technology Prioritization Committee (ITPC) https://www.itpc.uillinois.edu • University Administrative Information Technology Systems (AITS) • University Human Resources (HR)

  5. Project Goals • Reduce unit workload • Improve data integrity • Reduce operating costs • Improve employee satisfaction with the system

  6. Project Timeline • December 2004 – April 2005 • Pre-Design Phase • July 2005 – January 2006 • Functional Design Phase • January 2006 – Present • Technical Design and Implementation • User Acceptance Testing (UAT) – begins October 2008 • User Training – begins January 2009

  7. Pre-Design Findings • Identification of appropriate organization and staffing models • Identification of Campus User Representation Groups • Users sought: • Streamlining of HR transaction processes • Division of roles and responsibilities for data integrity accountability

  8. Functional Design Outcomes • Identified key application functionality • Designed user-focused screens • Developed functional prototype • Produced functional specification document • Complete functional phase on time and within budget

  9. User Input – Functional Phase • 39 sessions with user community • 213 participants in online survey • 17 sessions with business teams • 9 sessions with focus groups (98 participants) • 7 sessions with joint application development • Session with joint campus advisory group

  10. HRFE Benefits • Employee search interface improvement • Ability to attach document to a transaction • Route a transaction through standard, custom, and data-driven routes • Enhanced security profiles allowing security to be based on organization, transaction type, and role

  11. HRFE Benefits (cont.) • Flexible inbox/outbox to help manage workloads • Employee record view that consolidates 11 Banner forms into one view (whole-person view) • Transaction wizards to guide processors through complex transactions (e.g. separations, new hire)

  12. HRFE Benefits (cont.) • Embedded, context-sensitive help within the application including interactive videos based on face-to-face training content • Routing trail and transaction history showing changes to every data element and who changed them

  13. HRFE Benefits (cont.) • Business rules that prevent common data mistakes • Extensive use of default values to speed up data entry

More Related