Overview

Background

 

Following the Simitive Workload Allocation Management System (WAMS) implementation (HSS022) and to support wider adoption of the system across CAHSS,  the College is completing this business embedding project . It also aims to address the issues that have emerged during the initial implementation project, which broadly follow the deliverable themes detailed below.  

Without this embedding phase, the College will be failing to properly realise the benefits the system drives for the College that were established in the original business case and in the system procurement.  

 A revised governance structure led by a senior academic is being implemented, including a new project board with appropriate representation from across the College to influence and drive academic involvement with the culture, system and processes of WAM. The project board will report to College Staffing Management Committee. 

The primary purpose is not a technology or systems project, rather a business process and change project that is facilitated and enabled by the IT system we have procured and adopted (Simitive). 

The project will take until end of March 2020 to deliver, followed by a 3 month period to ensure sustainment in the use of WAM. If adopted the College will be planning academic workload using the new business process for the 2020 – 2021 session.

It is estimated to take 85 days effort from Information Services and at the least, where workload planning is performed in schools, an equivalent collective amount of time from DoPS teams and HoSA’s.

In addition, the project will investigate the introduction of an Application Programming Interface (API) or HR information to Simitive to improve the frequency and efficiency of updating this information in Simitive.

Scope

As outlined in the Objectives and Deliverables, this project has the following in scope:

1. Embedding adoption of WAMs - This is essential to deliver the benefits of consistency, transparency and fairness

2. Data management - improving efficiency of data feeds to WAM; managing cutover to new Core System

3. Embedding Business-As-Usual governance for sustained use and future improvements

 

Objectives & Deliverables

WAMS Business Embedding

Priority   Owner
     

O1        Communication & Culture

   
O1.D1. Communication Plan Development   MUST Project Manager

O1.D2. Project Board Establishment

  MUST Sponsor
O1.D3. Engaging and influencing key stakeholder community   MUST Sponsor/Board
O1.D4. Cultural workshops to address wider understanding of WAM   MUST Academic WAM Champion
O1.D5. Simitive Head of Subject Area Training   MUST Vendor/Project Manager
O1.D6. WAM Co-ordinators forum organisation   MUST Sponsor
O1.D7. Documented future recommendations for service improvements at Closure   MUST Project Manager/Business Analyst
O1.D8. Data/Reporting to be standardised and curated with exceptions when required   MUST Project Manager/Business Analyst/Vendor
     
O2        Business Analysis    
O2.D1. Review of the current business processes across all Schools   MUST Business Analyst
O2.D2. Document embed and agree new common business process in line with best practice   MUST Business Analyst/Project Manager
O2.D3. Existing WAM Analysis   MUST Business Analyst
O2.D4. Collate current reporting and future reporting needs for College/Schools   MUST Business Analyst
O2.D5. Deploy the updated College WAM to the system   SHOULD  Vendor
O2.D6 School resource requirements - to complete project and ongoing running of WAM   MUST Project Manager
      
O3       Data Management    
O3.D1. WAM Calendar development - Documenting the business calendar required   MUST Project Manager/Business Analyst
O3.D2. Documentation of WAM/Simitive dataflows   MUST Business Analyst/College BI team
O3.D3. Documentation of WAM business processes including roles and responsibilities   MUST Business Analyst
O3.D4. Automation feed of data (using an API) for HR data   SHOULD Service Management API lead
O3.D5 Cutover plan in place with Core Systems Implementation   MUST Project Manager/Core Systems solutions architect
O3.D6. TRAC Code Review   COULD Project Manager/Vendor
O3.D7. Governance established for Business as usual data and reporting for Schools/College   MUST Sponsor

 

Out of Scope

Automation of data feeds (APIs) other than HR, eg EUCLID

Forward Scenario planning of school/college work

Benefits

Academic staff time is the College's most important resource. The purpose of workload management is to ensure adequate, appropriate and equitable resourcing of the College's strategic plans. 

By the end of this project the College is expected to be able to realise the following benefits:  

  • Academic staff will be able to engage with their own workload information at any time in a modern, online, secure and self-service manner
  • The end to end process of workload allocation will be streamlined through the use of a workflow in the system avoiding the use of email or shared files
  • A significant increase in consistency, transparency and perceived fairness of workload allocation across the College
  • Workload allocation process should enable improved conversations with staff about their balance of work across various academic activities, as well as their work/life balance and wellbeing
  • Heads of College, School and Subject Area and DoPs are able to perform academic workload forecasting, modelling, planning and prediction
  • A reduction in the cost and effort associated with academic workload planning, staff development and succession planning
  • Enable analysis and understanding of cross-College workload (and if the system is adopted more widely as expected, cross-University)
  • A fully allocated cross-College WAM will support development of a course costing model with accurate academic staff costs 

Success Criteria

  • WAMs in use across CAHSS for academic workload planning for 2020/21 session
  • Measurable increase in usage of Simitive (with baseline being taken on approval of Project Brief)

  • Increased consistency in WAM implemented across College through deployment of a revised approved CAHSS WAM

  • Established and active WAM co-ordinators forum

  • Governance change control process to ensure WAMs use is sustained and continuously improved in a consistent manner across the College

  • No unplanned interruption to service with cutover to revised College WAM model
  • No data loss with cutover to revised College WAM model
  • No unplanned interruption to service with cutover to new Core System
  • No data loss with cutover to new Core System

Project Milestones

The Board acknowledge that these milestones are based on the assumption that the analysis will not surface large gaps between current College WAM and those in operation in Schools. On completion of the WAM analysis a review of the milestones should be undertaken to test whether they remain achievable.

 

Stage Milestone Due Date
Plan Project brief approval 10-Oct-2019
Execute Project Board approval of Communications Plan and engagement strategy to delivery 18-Nov-2019
Analyse Completion of API analysis and estimation to current Oracle HR 22-Nov-2019
Analyse Completion of Business Analysis - updated College WAM 29-Nov-2019
Execute Project Board approval of updated College WAM 16-Dec-2019
Execute WAM Co-ordinators forum organisation established 31-Jan-2020
Deliver Approved revised College WAM implemented in Simitive 31-Jan-2020
Execute Head of Subject Area Simitive training completed 28-Feb-2020
Deliver API established with current HR system 28-Feb-2020
Deliver Project Delivery 31-Mar-2020
Deliver Cutover plan in place with Core Systems Implementation project 30-Apr-2020
Deliver Sustainment of WAMS use checkpoint pre-closure 29-May-2020
Deliver Completion of cutover to new Core System 08-Jun-2020
Deliver Completion of enagagment work to ensure sustainment of WAMs use 10-Jul-2020
Close Project Closure approved 31-Jul-2020

Project Info

Not available.

Documentation

Not available.