Timescales

2011 New system selection

The product evaluation and procurement process was completed in July 2011. Two of the five end-to-end student system suppliers - Unit4 and Tribal - were identified as offering solutions most appropriate for Oxford. Demonstration workshops were carried out involving staff from across the collegiate University to evaluate the two proposed solutions. The Student Systems Programme Business Case, detailing the recommended solution, was presented to the UAS Information Systems Board, Education Committee, Budget Sub-Committee, Planning & Resource Allocation Committee and Council. Tribal was selected as the supplier of the new system, SITS:Vision.

2012-14 Replacing OSS with SITS:Vision

eVision, the web view access to the SITS:Vision student records system, went live during Michaelmas Term 2012 for degree ceremonies administration. Students are using eVision to book to attend their degree ceremony from July 2013 onwards and colleges are using eVision to manage information about degree ceremony requirements for graduands and their guests.

A detailed assessment of the Student Systems Programme has been undertaken to ascertain what is both practical and achievable during 2013/14 for the continued roll-out of eVision. The current aim is to deliver the following elements between April 2013 and December 2014:

  • April 2013: Degree ceremonies updates;
  • September 2013: Delivery of the new replacement ADSS (Admissions Decision Support System) service to set-up for the 2013-14 undergraduate admissions cycle;
  • From September 2014: Roll-out of eVision for the management of the main student record, to replace the Oracle Student System (OSS);
  • From Autumn 2014: Roll-out of admissions.

2013-15 Enhancements and continued development

It is anticipated that the next phase of the programme will begin during 2014, alongside the final delivery of the first phase of the Programme. An overlap between the delivery of the current work and the start of the next phase of work will enable continued use of the expertise the programme team has built up, and engagement with stakeholders across the collegiate University to be maintained effectively.

Views were gathered from across the collegiate University during Michaelmas Term 2012 as to the possible priorities for which developments to student systems should be delivered. The paper which sought input is available to read at: https://sharepoint.nexus.ox.ac.uk/sites/SSP/SitePages/Priorities.aspx.

Several key points stand out from a consideration of the responses:

  • There is a broad consensus on the top priorities for the next phase of work;
  • Considerable overlap exists between a set of priorities which had been stated separately but which all cover matters related to the delivery of the academic curriculum. The first step will be to assess the various activities within this area, in consultation with representatives from across the collegiate University, to determine the main priorities alongside consideration of the most logical sequence for delivering these requirements;
  • Improving links between the collegiate University’s various systems should form a common thread of all future work, rather than a stand-alone priority. Even where developments do not specifically relate to integration, they should be undertaken in such a way that integration in the future is eased rather than hampered;
  • Some resource should be allocated for statutory requirements (e.g. UKBA compliance) and enhancements to functionality being delivered in the first phase of work.

Alongside delivering the current phase of work, the Programme will be considering how developments of the proposed priorities can best be structured during 2014. A business case for the next phase of work on the Student Systems Programme will be presented through IT Committee to Council during Trinity Term 2013.