ISO 20000-1 IT Service Management – clause 8.2 break down
This is the second of a series of blogs, relating to Clause 8 of the new ISO 20000-1:2018, designed to unpack the requirements of the standard and remove that air of mystery that can so often form around standards. This week we’ll continue to look at clause 8.2 of the standard.
Service catalogue management
The Service Catalogue is often undervalued in service management systems, but it has a critical part to play in communicating to customers exactly what you can provide, and, above all, it should be used by Sales when selling services to a customer. If anyone sells anything that is not in the catalogue it is not the responsibility of your organisation to bend your processes to meet that service agreement. First, Sales should go back to the customer and advise them that the service cannot be delivered and second, the proposal put forward by Sales could be passed through the Design, Build and Transition process to produce a new service.
Sometimes it helps to see that Service Catalogue as something like an ‘Argos’ catalogue where all the wares for sale are recorded, but the customer doesn’t have to buy everything; they may choose to just by Incident Management or Service Request Management, but the catalogue will show them clearly how they might develop that service in the future.
The catalogue does not have to have the service prices printed in it as this will be part of the Sales discussion. One way of making the catalogue available to all interested parties is to put in on the company website or in a ‘customers only’ area of the website.
Don’t look at Asset Management as purely being related to customer assets as the standard clearly states that ‘the organization shall ensure that assets used to deliver services are managed…’ So, a good asset management system can help here (if you are certified to ISO55001, much of the work will have been completed). What are the assets that should be considered?
– Service Desk tools (Service Now etc)
– Vehicles to get engineers and equipment to a customer site
– IT equipment
This isn’t by any means an exhaustive list but just listing 4 items can show how broad this small clause can be. But don’t run away with the idea that you need to create a new job role to manage assets, instead look for where these are managed naturally in the business; staff by HR; Vehicles by facilities; Service Desk tools and IT equipment by the IT department; Spares by Procurement and Logistics. All these teams might be providing reports to the Service Delivery Manager/Director about the availability of the assets in their control.
Focus on Customer Assets takes place here. First, we need to understand what is meant by a Configuration Item (CI) – a CI is an asset that makes up part of the service.
The service itself could be a Configuration Item and all the assets used to deliver that service could all be classed as configuration items; but the main point of configuration management is to ensure that your organisation only services equipment under contract.
For every service established it is key to understand the exact equipment to be serviced; this can be determined through Model Numbers, Serial Numbers and or Asset Numbers (see below). This will enable the Service Desk staff to know what equipment is under contract and which equipment should be subject to a Service Charge. Without this you will end up servicing equipment that is not under contract
The standard is quite specific about what information should be recorded for each Configuration Item:
– Unique identification (serial number, asset number)
– Type of CI (the item or model number)
– Description of the CI (detailed description of the item)
– Relationship with other CIs (does this CI have any dependencies on or for other items; if changes are made will other CIs be affected?)
– Status (is the CI still live or obsoleted in the service contract).
A configuration management list will be produced for each customer, but it is important that the list is reviewed at planned intervals (add this to the audit schedule) and audited to ensure that changes to the configuration estate have been captured. It is useful to ensure that a step in the Change Management process includes a review of the customer’s configuration list.