How to come up with categories for our service requests
By ITIL® from Experience©
For most tools the category is a key element in the Classification1 of an event. Not only does it describe the type of work that needs to be done, it often determines the group/queue/service department the request is assigned to and it enables reports. It may also select the Service Level Agreement (SLA) and a workflow.
ITIL® Service Operations provides a technique to determine an incidents2 Classification scheme. Unfortunately it does not provide one for Service Requests.
Sources of information to prepare Service Request Categories include:
- Service Catalogue
- Service Desk Reports
- The current ITSM Tool
Categories for service requests should be based on what IT provides. Therefore, they should be available from the Service Catalogue. If the Service Catalogue does not list detailed transaction offered for each service, look at each service from an IMAC perspective. IMAC stands for Install, Move, Add or Change as many service requests will be related to one of those actions.
If the organization does not have a service catalogue, look for SLAs as they may list requests that can be made. In addition, review the Service Desk reports as they usually group service requests into categories for reporting. Moreover, they may be looking to have these reports re-produced by the new ITSM tool thus, this activity would also help identify reporting requirements. In absense of both a Service Catalogue and SLAs ask managers what services they are responsible to provide and the type of requests they are getting.
As a last resort review the categories used in the current tool. Be careful if the tool was not maintained by an ITSM authority and lacked governance. Simply importing the old tool's categories usually brings over problems of the current state and perpetuates difficulties and challenges into the new tool. If this is the only option available, export all the categories and group them by process (e.g. Incident, Problem, Change) and Service Requests.
Before starting this work, ask/demand a list of sample categories from the tool vendor or consultants. They should be able to provide sample lists and templates to capture data in the form of Dictionaries3 , Event Builders4 or CTI5 . Moreover they should be capable of explaining the functionality that categories enable/automate in their tool and what information is required to configure them. It would be unfortunate to discover after the data gathering is done that a mandatory field was required.
Notwithstanding all this work, put in place a process for users to request that a category be added to the tool once it is implemented. However, the list of service request categories should reflect the services offered. Therefore, a new category should not only be added once it is approved by the appropriate governance authority. Without this formal approval, it is the equivalent of offering a new service for which the organization needs to ensure that it is properly funded, resourced and that the service delivery is managed.
Last updated on: 2016-06-13
"The ITSM tool can be many things to many people. It is better to do less very well than a lot poorly."
- How many categories do we need
- Is a How-to an Incident or a Service Request
- We need categories to classify the cause of IT security incidents
- What are good groupings for a Service Catalogue
- Why asking what you want to report on is the wrong way to implement a tool
- Should a service request be reopened or a new one logged
More on Request Fulfillment (Service Requests)
More on Technology - ITSM Tools
ITIL Process > Request Fulfillment
Implementation > Technology (ITSM Tools)
Copyright 2012-2016 - ITIL® from Experience - D.Matte