Shopping Cart

No products in the cart.

BS ISO/IEC 20000-2:2019+A1:2020

$215.11

Information technology. Service management – Guidance on the application of service management systems

Published By Publication Date Number of Pages
BSI 2020 74
Guaranteed Safe Checkout
Categories: ,

If you have any questions, feel free to reach out to our online customer service team by clicking on the bottom right corner. We’re here to assist you 24/7.
Email:[email protected]

1.1 General

This document provides guidance on the application of a service management system (SMS) based on ISO/IEC 20000‑1. It provides examples and recommendations to enable organizations to interpret and apply ISO/IEC 20000‑1, including references to other parts of ISO/IEC 20000 and other relevant standards.

Figure 1 illustrates an SMS with the clause content of ISO/IEC 20000‑1. It does not represent a structural hierarchy, sequence, or authority levels.

Figure 1 Service management system

The structure of clauses is intended to provide a coherent presentation of requirements, rather than a model for documenting an organization’s policies, objectives, and processes. Each organization can choose how to combine the requirements into processes. The relationship between each organization and its customers, users, and other interested parties influences how the processes are implemented. However, an SMS as designed by an organization cannot exclude any of the requirements specified in ISO/IEC 20000‑1.

The term ‘service’ as used in this document refers to the services in the scope of the SMS. The term ‘organization’ as used in this document refers to the organization in the scope of the SMS. The organization in the scope of the SMS can be part of a larger organization, for example an IT department of a large corporation. The organization manages and delivers services to customers and can also be referred to as a service provider. Any use of the terms ‘service’ or ’organization’ with a different intent is distinguished clearly in this document. The term ‘delivered’, as used in this document, can be interpreted as all of the service lifecycle activities that are performed in addition to daily operational activities. Service lifecycle activities include planning, design, transition, delivery, and improvement.

1.2 Application

The guidance in this document is generic and is intended to be applicable to any organization applying an SMS, regardless of the organization’s type or size, or the nature of the services delivered. While it can be used ‘regardless of the organization’s type or size, or the nature of the services delivered’, ISO/IEC 20000‑1 has its roots in IT. It is intended for service management of services using technology and digital information. The examples given in this document illustrate a variety of uses of ISO/IEC 20000‑1.

The service provider is accountable for the SMS and therefore cannot ask another party to fulfil the requirements of ISO/IEC 20000‑1:2018, Clauses 4 and 5. For example, the organization cannot ask another party to provide the top management and demonstrate top management commitment or to demonstrate the control of parties involved in the service lifecycle.

Some activities in ISO/IEC 20000‑1:2018, Clauses 4 and 5 can be performed by another party under the management of the organization. For example, an organization can ask another party to create the initial service management plan as a key document for the SMS. The plan, once created and agreed, is the direct responsibility of and is maintained by the organization. In these examples, the organization is using other parties for specific short-term activities. The organization has accountability, authorities, and responsibility for the SMS. The organization can therefore demonstrate evidence of fulfilling all of the requirements of ISO/IEC 20000‑1:2018, Clauses 4 and 5.

For ISO/IEC 20000‑1:2018, Clauses 6 to 10, an organization can show evidence of meeting all of the requirements itself. Alternatively, an organization can show evidence of retaining accountability for the requirements when other parties are involved in meeting the requirements in ISO/IEC 20000‑1:2018, Clauses 6 to 10. Control of other parties involved in the service lifecycle can be demonstrated by the organization (see 8.2.3). For example, the organization can demonstrate evidence of controls for another party who is providing infrastructure service components or operating the service desk including the incident management process.

The organization cannot demonstrate conformity to the requirements in ISO/IEC 20000‑1 if other parties are used to provide or operate all services, service components, or processes within the scope of the SMS. However, if other parties provide or operate only some of the services, service components, or processes, the organization can normally demonstrate evidence of meeting the requirements specified in ISO/IEC 20000‑1.

The scope of this document excludes the specification of products or tools. However, ISO/IEC 20000‑1 and this document can be used to help with the development or acquisition of products or tools that support the operation of an SMS.

1.3 Structure

This document follows the clauses in ISO/IEC 20000‑1 and, from Clause 4 onwards, provides three sections per clause or sub-clause:

  1. Required activities: a summary of the activities required by this clause in ISO/IEC 20000‑1 Note that this summary does not replicate the requirement statements in ISO/IEC 20000‑1 or add new requirements, but simply describes the activities;

  2. Explanation: an explanation of the purpose of the clause and practical guidance on clause contents, including examples and recommendations on how to implement the requirements of ISO/IEC 20000‑1. When relevant, it refers to other parts of ISO/IEC 20000 and other relevant standards;

  3. Other information: guidance on roles and responsibilities and on documented information supporting the implementation of an SMS. Further relevant information can also be included.

PDF Catalog

PDF Pages PDF Title
2 National foreword
8 Foreword
9 Introduction
11 1 Scope
1.1 General
12 1.2 Application
13 1.3 Structure
2 Normative references
3 Terms and definitions
4 Context of the organization
4.1 Understanding the organization and its context
4.1.1 Required activities
4.1.2 Explanation
14 4.1.3 Other information
4.2 Understanding the needs and expectations of interested parties
4.2.1 Required activities
4.2.2 Explanation
4.2.3 Other information
15 4.3 Determining the scope of the service management system
4.3.1 Required activities
4.3.2 Explanation
4.3.3 Other information
4.4 Service management system
4.4.1 Required activities
16 4.4.2 Explanation
4.4.3 Other information
5 Leadership
5.1 Leadership and commitment
5.1.1 Required activities
5.1.2 Explanation
17 5.1.3 Other information
18 5.2 Policy
5.2.1 Required activities
5.2.2 Explanation
19 5.2.3 Other information
5.3 Organizational roles, responsibilities, and authorities
5.3.1 Required activities
5.3.2 Explanation
5.3.3 Other information
20 6 Planning
6.1 Actions to address risks and opportunities
6.1.1 Required activities
6.1.2 Explanation
21 6.1.3 Other information
6.2 Service management objectives and planning to achieve them
6.2.1 Required activities
6.2.2 Explanation
22 6.2.3 Other information
6.3 Plan the service management system
6.3.1 Required activities
6.3.2 Explanation
23 6.3.3 Other information
7 Support of the service management system
7.1 Resources
7.1.1 Required activities
7.1.2 Explanation
24 7.1.3 Other information
7.2 Competence
7.2.1 Required activities
7.2.2 Explanation
25 7.2.3 Other information
7.3 Awareness
7.3.1 Required activities
7.3.2 Explanation
26 7.3.3 Other information
7.4 Communication
7.4.1 Required activities
7.4.2 Explanation
27 7.4.3 Other information
7.5 Documented information
7.5.1 General
28 7.5.2 Creating and updating documented information
7.5.3 Control of documented information
29 7.5.4 Service management system documented information
30 7.6 Knowledge
7.6.1 Required activities
7.6.2 Explanation
31 7.6.3 Other information
8 Operation of the service management system
8.1 Operational planning and control
8.1.1 Required activities
8.1.2 Explanation
32 8.1.3 Other information
8.2 Service portfolio
8.2.1 Service delivery
33 8.2.2 Plan the services
34 8.2.3 Control of parties involved in the service lifecycle
35 8.2.4 Service catalogue management
37 8.2.5 Asset management
38 8.2.6 Configuration management
39 8.3 Relationship and agreement
8.3.1 General
40 8.3.2 Business relationship management
42 8.3.3 Service level management
43 8.3.4 Supplier management
45 8.4 Supply and demand
8.4.1 Budgeting and accounting for services
46 8.4.2 Demand management
47 8.4.3 Capacity management
48 8.5 Service design, build and transition
8.5.1 Change management
52 8.5.2 Service design and transition
54 8.5.3 Release and deployment management
56 8.6 Resolution and fulfilment
8.6.1 Incident management
57 8.6.2 Service request management
58 8.6.3 Problem management
59 8.7 Service assurance
8.7.1 Service availability management
60 8.7.2 Service continuity management
61 8.7.3 Information security management
63 9 Performance evaluation
9.1 Monitoring, measurement, analysis, and evaluation
9.1.1 Required activities
9.1.2 Explanation
9.1.3 Other information
9.2 Internal audit
9.2.1 Required activities
9.2.2 Explanation
64 9.2.3 Other information
9.3 Management review
9.3.1 Required activities
9.3.2 Explanation
65 9.3.3 Other information
9.4 Service reporting
9.4.1 Required activities
9.4.2 Explanation
9.4.3 Other information
66 10 Improvement
10.1 Nonconformity and corrective action
10.1.1 Required activities
10.1.2 Explanation
10.1.3 Other information
67 10.2 Continual improvement
10.2.1 Required activities
10.2.2 Explanation
10.2.3 Other information
68 Annex A (informative) Mandatory documented information in ISO/IEC 20000‑1:2018
73 Bibliography
BS ISO/IEC 20000-2:2019+A1:2020
$215.11