Text only | Skip links
Skip to Navigation

ICT Development Team: OUCS Service Response Levels


1. Service Response Levels for OUCS Services

1.1. Description

This document describes the response times that service users can generally expect for services currently provided by the ICT Team within OUCS. The primary mechanism for reporting problems and requesting assistance within OUCS is via the Request Tracker (RT) system. Major problems are best reported by phone or in person. Requests are assessed and prioritised according to importance and urgency and will be prioritised accordingly.

1.2. Response Times

Problems will initially be assessed according to the number of people affected, the impact or severity of the problem and the security implications of the problem. The problem will then be assigned a priority accordingly. Change requests will not generally be categorised but will always be assigned a priority of 5.

Response times will be determined by the final assigned priority according to the following table. Normally the time quoted will be the time to resolve 95% of problems. In the case of priority 5 items (requests for change) the time quoted will be the time for a plan of action to be agreed with the customer, rather than resolution of the problem. Times quoted only apply during working hours.

Note that these response times are very new, and will be reviewed and if necessary revised once a month for the next three months (until February 2006).

Priority Response from Notification Time to Resolve/Agreed plan of action Preferred Contact Mechanism
1 Immediate 2 hours In person/phone
2 30 minutes 3 hours In person/phone
3 4 hours 7 hours RT
4 1 working day 5 working days RT
5 2 working days 5 working days RT

1.3. Mechanism

The following tables give more detail as to the criteria used to assess problems. Note that without going into minute detail, staff judgement will necessarily be part of the assessment process, and adjustment of priorities by staff according to individual circumstances is expected to form part of the process (although we expect this generally only to change a priority by ±1. Change requests will not generally be categorised but will always be assigned a priority of 5.

Number Affected Priority
Whole University A
Large group of users (e.g. Lecture Rooms) B
Small group or Individual C
Impact or severity Priority
Little or no work possible A
Workaround available B
Inconvenience C
Security Implications Priority
Major threat A
Minor threat B
No threat C

The combined priorities of any request will be translated into a numerical priority as follows, where 1 is the highest priority and 5 the lowest.

Combination Priority
AAA 1
AAB 1
AAC 1
ABB 2
ABC 2
ACC 3
BBB 2
BBC 3
BCC 4
CCC 4
Change Request 5

Up: Contents


Style: Simple text | Single file | Normal

Maintained by: OUCS Webmaster (webmaster@rt.oucs.ox.ac.uk) 28 October 2005 . Bridget Lewis .
University of Oxford. Back to top
Skip to search