Implement
Document services Estimate service levels
In the first instance we will not implement the full Service Level Management process flow.  Instead we will begin by introducing the first and last steps - that is, the gathering and documenting of service information and the steps towards monitoring and reviewing the service provided.  This will enable you to create a service catalogue that you will use as the basis for service level management and that you can issue to end-users to outline what technical support is responsible for (and, by definition, what it is not responsible for). The preparation of service level agreements, operational level agreements and other underpinning contracts is not necessary at this stage.


Document services
Remember that there is a difference between services and the equipment that enables the services - see example services in toolkit.

In FITS Configuration Management we identify and record all the component parts that make up the infrastructure (the pieces of equipment - hardware, software, documentation and so on). In Service Level Management we take a different view, determining what parts of the infrastructure are required to fulfil each particular service.  This is a key step in improving communication between technical ICT staff and end-users.  If you speak in terms of services and ensure that services are in working order, the end-user is receiving working ICT on their terms.  To try to discuss end-user requirements in terms of the availability of file servers, routers, network cabling and so on would be undesirable, as it is unreasonable to expect end-users to understand the implications.

To document the services, you must then identify each service and the technical components of each service. Gathering service information is harder than doing an audit of physical equipment and is more likely to be in terms of what software is installed on computers and file servers.  You will need to investigate every computer and file server, and talk to at least one representative of each department to make sure that you don't miss anything - see Assigning roles and responsibilities in Service Level Management  for further information on end-user representatives.  Don't assume that if you haven't installed something yourself it doesn't exist!

To help you, we have prepared a service catalogue template outlining the kind of information you should gather.  Complete the section on service details with your service information: service details guidance will help you do this. The section on service details in our service catalogue example  should also help you understand what is required.
If you have implemented FITS Configuration Management, you should store your baseline service catalogue in the configuration management database.  You should then ensure that the list is controlled and maintained so that it is always accurate and up to date (or you will have to do another audit).  FITS Change Management can help you to do this.

Go back to Implement
Service details guidance
Services
Enter every service in this column.
Components
List all the pieces of equipment involved in providing this service.
Component unique ID
Identify each component with its unique ID if it has been assigned - this is dealt with in Configuration Management.  If you have not assigned unique IDs yet, leave this blank until you do.  The information is to help you identify physical pieces of equipment when trying to diagnose a service failure.
End-users
List the end-users of this service (not the components).  List job titles, functions or departments.  Avoid using people's names - if someone leaves and the catalogue is not updated with their replacement's name, you may not know in future to whom it refers.  Be explicit - don't put 'most users' or 'some users in Humanities'.
Date recorded
Enter the date of recording the service in the service catalogue.

Estimate service levels
The purpose of providing an estimate of the service levels currently being provided is to identify what the perceived priorities are in ICT. This is often different from what is in the overall interests of the school - which is what should determine the service levels required. 

By estimating current service levels, you have a baseline  from which to discuss actual requirements and identify changes in priorities.  This helps you to make step- changes to move from current service levels to new ones without having to spend more time starting from a blank sheet of paper.

Before you can estimate the level of service being provided, you must identify what the services are.  See Document services for details. Once you have done that, return to the service catalogue you have started and complete the next section - Service level details.  For assistance in completing this section, see our service level details guidance and the service level details section of service catalogue example.
graphic

Go back to Implement
Service level details guidance
Component availability
Estimate the hours each component is available or is required to be available.
Response time
Estimate the speed of response to an incident relating to each component. Be honest. It may vary between services, depending on the perceived criticality of the service or for other reasons.
Fix time
Estimate the speed of resolution of an incident relating to each component.  Of course, it will vary depending upon the cause. This just needs to be a best-guess average to start with, based on recent experience.
Supported by
Record the function, department or third party responsible for supporting the components of the service.
Hours of support
List the hours of availability of the support service for the components.
Date last updated
Enter the date the service catalogue record was last updated.  It is good practice to indicate when records were changed.