ITIL Service Operation: Difference between revisions
No edit summary |
|||
(11 intermediate revisions by 2 users not shown) | |||
Line 1: | Line 1: | ||
< | <itpmch><title>ITIL Service Operation | IT Process Wiki</title> | ||
<meta name="keywords" content="service operation, itil service operation, itil service operations, service operations, itil v3 service operation, service operation processes" /> | |||
<meta name="description" content="The objective of ITIL Service Operation is to make sure that IT services are delivered effectively and efficiently. The Service Operation lifecycle stage includes the fulfilling of user requests, resolving service failures, fixing problems, as well as carrying out routine operational tasks." /> | |||
<meta property="og:url" content="https://wiki.en.it-processmaps.com/index.php/ITIL_Service_Operation" /> | |||
<meta property="og:title" content="ITIL Service Operation | IT Process Wiki" /> | |||
<meta property="og:description" content="The objective of ITIL Service Operation is to make sure that IT services are delivered effectively and efficiently. The Service Operation lifecycle stage includes the fulfilling of user requests, resolving service failures, fixing problems, as well as carrying out routine operational tasks." /> | |||
<meta property="og:site_name" content="IT Process Wiki - the ITIL® Wiki"> | |||
<meta property="og:type" content="article" /> | |||
<meta property="article:publisher" content="https://www.facebook.com/itprocessmaps" /> | |||
<meta property="fb:admins" content="100002035253209" /> | |||
<meta property="fb:admins" content="100002592864414" /> | |||
<meta property="og:image" content="https://wiki.en.it-processmaps.com/images/9/96/Service-operation-itil.jpg" /> | |||
<meta property="og:image:width" content="558" /> | |||
<meta property="og:image:height" content="847" /> | |||
<link href="https://plus.google.com/108613479011811316823/posts" rel="publisher" /> | |||
</itpmch> | |||
<imagemap> | <imagemap> | ||
Image:ITIL-Wiki-de-es.jpg|DE - ES - Service Operation| | Image:ITIL-Wiki-de-es.jpg|right|DE - ES - Service Operation|163px | ||
rect 0 | rect 81 0 114 36 [https://wiki.de.it-processmaps.com/index.php/ITIL_Service_Operation_-_Servicebetrieb diese Seite auf Deutsch] | ||
rect | rect 115 0 163 36 [https://wiki.es.it-processmaps.com/index.php/ITIL_Operaci%C3%B3n_del_Servicio esta página en español] | ||
desc none | desc none | ||
</imagemap> | </imagemap> | ||
<br style="clear:both;"/> | <br style="clear:both;"/> | ||
'''<span id="ITIL Service Operation definition">Objective:</span>''' <html><span id="md-webpage-description" itemprop="description">The objective of <i>ITIL Service Operation</i> is to make sure that IT services are delivered effectively and efficiently. The Service Operation lifecycle stage includes the fulfilling of user requests, resolving service failures, fixing problems, as well as carrying out routine operational tasks.</span></p> | |||
<p><b>Part of</b>: <a href="https://wiki.en.it-processmaps.com/index.php/ITIL_Processes#ITIL_Processes_according_to_ITIL_V3" title="ITIL Processes">IT Service Management | ITIL processes</a></html> | |||
The objective of | |||
<p> </p> | <p> </p> | ||
__TOC__ | |||
==Processes: ITIL Service Operation== | |||
Service Operation carries out operational tasks. | |||
[[Image:Service-operation-itil.jpg|right|thumb|458px|alt=ITIL Service Operation|link=https://wiki.en.it-processmaps.com/index.php/File:Service-operation-itil.jpg|Fig. 1: [[#Processes:_ITIL_Service_Operation|ITIL Service Operation]]]] | |||
<html><div itemid="https://wiki.en.it-processmaps.com/index.php/ITIL_Service_Operation#Processes:_ITIL_Service_Operation" itemscope="itemscope" itemtype="https://schema.org/ItemList"><!-- define schema.org/ItemList --> | |||
<meta itemprop="itemListOrder" content="Ascending" /> | |||
<p><span itemprop="name" content="Service Operation main processes">The ITIL service lifecycle stage of <strong class="selflink">Service Operation</strong> (<a href="https://wiki.en.it-processmaps.com/images/9/96/Service-operation-itil.jpg" title="ITIL Service Operation">see fig. 1</a>) includes the following <strong>main processes</strong></span></span>: | |||
</p> | |||
<div itemid="https://wiki.en.it-processmaps.com/index.php/Event_Management" itemprop="itemListElement" itemscope itemtype="http://schema.org/ListItem" > | |||
<meta itemprop="position" content="1" /> | |||
<dl><dt itemprop="name"><a itemprop="url" href="https://wiki.en.it-processmaps.com/index.php/Event_Management" title="Event Management" itemprop="itemListElement">Event Management</a> | |||
</dt><dd itemprop="description">Process Objective: To make sure CIs and services are constantly monitored, and to filter and categorize Events in order to decide on appropriate actions. | |||
</dd></dl></div> | |||
<div itemid="https://wiki.en.it-processmaps.com/index.php/Incident_Management" itemprop="itemListElement" itemscope itemtype="http://schema.org/ListItem" > | |||
<meta itemprop="position" content="2" /> | |||
<dl><dt itemprop="name"><a itemprop="url" href="https://wiki.en.it-processmaps.com/index.php/Incident_Management" title="Incident Management" itemprop="itemListElement">Incident Management</a> | |||
</dt><dd itemprop="description">Process Objective: To manage the lifecycle of all Incidents. The primary objective of Incident Management is to return the IT service to users as quickly as possible. | |||
</dd></dl></div> | |||
<div itemid="https://wiki.en.it-processmaps.com/index.php/Request_Fulfilment" itemprop="itemListElement" itemscope itemtype="http://schema.org/ListItem" > | |||
<meta itemprop="position" content="3" /> | |||
<dl><dt itemprop="name"><a itemprop="url" href="https://wiki.en.it-processmaps.com/index.php/Request_Fulfilment" title="Request Fulfilment" itemprop="itemListElement">Request Fulfilment</a> | |||
</dt><dd itemprop="description">Process Objective: To fulfill Service Requests, which in most cases are minor (standard) Changes (e.g. requests to change a password) or requests for information. | |||
</dd></dl></div> | |||
<div itemid="https://wiki.en.it-processmaps.com/index.php/Access_Management" itemprop="itemListElement" itemscope itemtype="http://schema.org/ListItem" > | |||
<meta itemprop="position" content="4" /> | |||
<dl><dt itemprop="name"><a itemprop="url" href="https://wiki.en.it-processmaps.com/index.php/Access_Management" title="Access Management" itemprop="itemListElement">Access Management</a> | |||
</dt><dd itemprop="description">Process Objective: To grant authorized users the right to use a service, while preventing access to non-authorized users. The Access Management processes essentially execute policies defined in Information Security Management. Access Management is sometimes also referred to as Rights Management or Identity Management. | |||
</dd></dl></div> | |||
<div itemid="https://wiki.en.it-processmaps.com/index.php/Problem_Management" itemprop="itemListElement" itemscope itemtype="http://schema.org/ListItem" > | |||
<meta itemprop="position" content="5" /> | |||
<dl><dt itemprop="name"><a itemprop="url" href="https://wiki.en.it-processmaps.com/index.php/Problem_Management" title="Problem Management" itemprop="itemListElement">Problem Management</a> | |||
</dt><dd itemprop="description">Process Objective: To manage the lifecycle of all Problems. The primary objectives of Problem Management are to prevent Incidents from happening, and to minimize the impact of incidents that cannot be prevented. Proactive Problem Management analyzes Incident Records, and uses data collected by other IT Service Management processes to identify trends or significant Problems. | |||
</dd></dl></div> | |||
<div itemid="https://wiki.en.it-processmaps.com/index.php/IT_Operations_Control" itemprop="itemListElement" itemscope itemtype="http://schema.org/ListItem" > | |||
<meta itemprop="position" content="6" /> | |||
<dl><dt itemprop="name"><a itemprop="url" href="https://wiki.en.it-processmaps.com/index.php/IT_Operations_Control" title="IT Operations Control" itemprop="itemListElement">IT Operations Control</a> | |||
</dt><dd itemprop="description">Process Objective: To monitor and control the IT services and their underlying infrastructure. The process IT Operations Control executes day-to-day routine tasks related to the operation of infrastructure components and applications. This includes job scheduling, backup and restore activities, print and output management, and routine maintenance. | |||
</dd></dl></div> | |||
<div itemid="https://wiki.en.it-processmaps.com/index.php/IT_Facilities_Management" itemprop="itemListElement" itemscope itemtype="http://schema.org/ListItem" > | |||
<meta itemprop="position" content="7" /> | |||
<dl><dt itemprop="name"><a itemprop="url" href="https://wiki.en.it-processmaps.com/index.php/IT_Facilities_Management" title="ITIL Facilities Management" itemprop="itemListElement">Facilities Management</a> | |||
</dt><dd itemprop="description">Process Objective: To manage the physical environment where the IT infrastructure is located. Facilities Management includes all aspects of managing the physical environment, for example power and cooling, building access management, and environmental monitoring. | |||
</dd></dl></div> | |||
<div itemid="https://wiki.en.it-processmaps.com/index.php/ITIL_Application_Management" itemprop="itemListElement" itemscope itemtype="http://schema.org/ListItem" > | |||
<meta itemprop="position" content="8" /> | |||
<dl><dt itemprop="name"><a itemprop="url" href="https://wiki.en.it-processmaps.com/index.php/ITIL_Application_Management" title="ITIL Application Management" itemprop="itemListElement">Application Management</a> | |||
</dt><dd itemprop="description">Process Objective: Application Management is responsible for managing applications throughout their lifecycle. | |||
</dd></dl></div> | |||
<div itemid="https://wiki.en.it-processmaps.com/index.php/ITIL_Technical_Managementt" itemprop="itemListElement" itemscope itemtype="http://schema.org/ListItem" > | |||
<meta itemprop="position" content="9" /> | |||
<dl><dt itemprop="name"><a itemprop="url" href="https://wiki.en.it-processmaps.com/index.php/ITIL_Technical_Management" title="ITIL Technical Management" itemprop="itemListElement">Technical Management</a> | |||
</dt><dd itemprop="description">Process Objective: Technical Management provides technical expertise and support for the management of the IT infrastructure. | |||
</dd></dl></div> | |||
</div><!-- end of schema.org/ItemList --><p></html> | |||
==ITIL 4 Service Operation== | |||
The [[#Processes:_ITIL_Service_Operation|Service Operation processes described here]] ([[Media:Service-operation-itil.jpg|fig. 1]]) follow the specifications of ITIL V3, where Service Operation is the fourth stage in the Service Lifecycle. | |||
: | |||
ITIL V4 has moved from the Service Lifecycle concept to a more holistic approach that includes key concepts, the [[ITIL_4#Four_dimensions_model|Four Dimensions Model]] and the [[ITIL_4#Service_value_system|Service Value System (SVS)]]. | |||
Instead of processes, [[ITIL_4#ITIL_4_management_practices|ITIL 4 describes 34 'practices']], and many of the 26 processes specified in ITIL V3 can be found in ITIL 4 as practices. For example, ITIL 4 refers to Incident Management and Problem Management as practices. | |||
The shift from processes to practices means ITIL V4 is no longer prescriptive about processes and gives organizations more freedom to define tailor-made Service Operation processes. | |||
<html>Since the processes defined in ITIL V3 have not been invalidated with the introduction of ITIL V4, organizations that need to design their Service Operation processes can still use the processes specified in ITIL V3 as templates.</p> | |||
; | <p style="border: 8px solid #cef6e3; padding: 0.5em 1em;"><i><u>Note</u>:</i><br /> In our <i>YaSM Service Management Wiki</i> we describe a <a class="external" href="https://yasm.com/wiki/en/index.php/Service_Management_Processes" title="Service management processes">leaner set of 19 service management processes</a> that are more in tune with ITIL 4 and its focus on simplicity and "just enough process".<br /><br /> The YaSM service management model includes a <a class="external" href="https://yasm.com/wiki/en/index.php/LP4:_Operate_the_services" title="YaSM service operation process">Service Operation process</a> that is a good starting point for organizations that wish to adopt ITIL 4.</html> | ||
: | |||
< | |||
== | ==<span id="Additional_Information_on_Service_Operation">KPIs | Templates | Roles</span>== | ||
* [[ITIL KPIs Service Operation|KPIs for Service Operation]] | * [[ITIL KPIs Service Operation|KPIs for Service Operation]] | ||
* [[ITIL-Checklists# | * [[ITIL-Checklists#ITIL Service Operation Templates|Service Operation templates and checklists]] | ||
* [[Roles | * [[ITIL Roles#ITIL roles and boards - Service Operation|ITIL roles within Service Operation]] | ||
== Downloads == | ==Downloads== | ||
= | [[Image:Service-operation.jpg|thumb|320px|right|none|alt=Service Operation ITIL|link=https://wiki.en.it-processmaps.com/index.php/File:Service-operation.jpg|The ITIL discipline Service Operation at a glance]] | ||
| | |||
Use the following links to open the process overview of Service Operation showing the most important interfaces: | Use the following links to open the process overview of Service Operation showing the most important interfaces: | ||
* [[Media:Service-operation.jpg|Service Operation (.JPG)]] | * [[Media:Service-operation.jpg|Service Operation (.JPG)]] | ||
* [https://wiki.en.it-processmaps.com/images/pdf/service-operation-itil-v3.pdf Service Operation (.PDF)] | * [https://wiki.en.it-processmaps.com/images/pdf/service-operation-itil-v3.pdf Service Operation (.PDF)] | ||
<br style="clear:both;"/> | |||
==Demo Service Operation: ITIL Process Map== | |||
* high-level view of the ITIL | The [https://en.it-processmaps.com/products/demo-itil-process-map.html ITIL Process Map video] shows samples of the ITIL process templates with contents from Service Operation and Incident Management processes, including the | ||
* high-level view of the ITIL Service Lifecycle (Level 0) | |||
* overview of the Service Operation process (Level 1) | * overview of the Service Operation process (Level 1) | ||
* overview of the Incident Management process (Level 2) | * overview of the Incident Management process (Level 2) | ||
* detailed process flow for the process "Incident Resolution by 1st Level Support" (Level 3) | * detailed process flow for the process "Incident Resolution by 1st Level Support" (Level 3) | ||
==Notes== | |||
<html>By:  Stefan Kempter <a rel="author" href="https://www.linkedin.com/in/stefankempter"><img style="margin:0px 0px 0px 0px;" src="/images/bookmarking/linkedin.png" width="16" height="16" title="By: Stefan Kempter | Profile on LinkedIn" alt="Author: Stefan Kempter, IT Process Maps GbR" /></a>, IT Process Maps.</p> | |||
<p> </p> | |||
<p><small> | |||
<span itemprop="breadcrumb" itemscope itemtype="http://schema.org/BreadcrumbList"> | |||
<span itemprop="itemListElement" itemscope itemtype="http://schema.org/ListItem"> | |||
<a itemprop="item" href="https://wiki.en.it-processmaps.com/index.php/ITIL_Service_Operation#ITIL_4_Service_Operation"> | |||
<span itemprop="name">ITIL 4 Service Operation</span></a> | |||
<meta itemprop="position" content="1"></span> › | |||
<span itemprop="itemListElement" itemscope itemtype="http://schema.org/ListItem"> | |||
<a itemprop="item" href="https://wiki.en.it-processmaps.com/index.php/Event_Management"> | |||
<span itemprop="name">Event Management</span></a> | |||
<meta itemprop="position" content="2"></span> › | |||
<span itemprop="itemListElement" itemscope itemtype="http://schema.org/ListItem"> | |||
<a itemprop="item" href="https://wiki.en.it-processmaps.com/index.php/Incident_Management"> | |||
<span itemprop="name">Incident Mgmt.</span></a> | |||
<meta itemprop="position" content="3"></span> › | |||
<span itemprop="itemListElement" itemscope itemtype="http://schema.org/ListItem"> | |||
<a itemprop="item" href="https://wiki.en.it-processmaps.com/index.php/Request_Fulfilment"> | |||
<span itemprop="name">Request Fulfilment</span></a> | |||
<meta itemprop="position" content="4"></span> › | |||
<span itemprop="itemListElement" itemscope itemtype="http://schema.org/ListItem"> | |||
<a itemprop="item" href="https://wiki.en.it-processmaps.com/index.php/Access_Management"> | |||
<span itemprop="name">Access Mgmt.</span></a> | |||
<meta itemprop="position" content="5"></span> › | |||
<span itemprop="itemListElement" itemscope itemtype="http://schema.org/ListItem"> | |||
<a itemprop="item" href="https://wiki.en.it-processmaps.com/index.php/Problem_Management"> | |||
<span itemprop="name">Problem Mgmt.</span></a> | |||
<meta itemprop="position" content="6"></span> › [...] | |||
</span> | |||
</small></p> | |||
<!-- define schema.org/WebPage --> <span itemscope itemtype="https://schema.org/WebPage" itemref="md-webpage-description"> | |||
<meta itemprop="name Headline" content="ITIL Service Operation" /> | |||
<meta itemprop="alternativeHeadline" content="Service Operation" /> | |||
<link itemprop="url" href="https://wiki.en.it-processmaps.com/index.php/ITIL_Service_Operation" /> | |||
<link itemprop="primaryImageOfPage" href="https://wiki.en.it-processmaps.com/images/9/96/Service-operation-itil.jpg" /> | |||
<span itemid="https://wiki.en.it-processmaps.com/images/9/96/Service-operation-itil.jpg" itemprop="image" itemscope itemtype="https://schema.org/ImageObject"> | |||
<meta itemprop="caption" content="ITIL Service Operation main processes."> | |||
<meta itemprop="contentUrl" content="https://wiki.en.it-processmaps.com/images/9/96/Service-operation-itil.jpg" /> | |||
<meta itemprop="width" content="558" /> | |||
<meta itemprop="height" content="847" /> | |||
<meta itemprop="representativeOfPage" content="true"/> | |||
<meta itemprop="dateCreated" content="2011-10-14" /> | |||
<meta itemprop="dateModified" content="2019-09-21" /> | |||
<meta itemprop="keywords" content="Service Operation" /> | |||
</span> | |||
<meta itemprop="mentions" content="https://yasm.com/wiki/en/index.php/LP4:_Operate_the_services" /> | |||
<meta itemprop="inLanguage" content="en" /> | |||
<link itemprop="citation" href="https://wiki.de.it-processmaps.com/index.php/ITIL_Service_Operation_-_Servicebetrieb" /> | |||
<link itemprop="citation" href="https://wiki.es.it-processmaps.com/index.php/ITIL_Operaci%C3%B3n_del_Servicio" /> | |||
<link itemprop="isPartOf" href="https://wiki.en.it-processmaps.com/index.php/ITIL_Processes#ITIL_Processes_according_to_ITIL_V3" /> | |||
<link itemprop="author" href="https://www.linkedin.com/in/stefankempter" /> | |||
<meta itemprop="author" content="Stefan Kempter" /> | |||
<meta itemprop="creator copyrightHolder publisher" content="IT Process Maps" /> | |||
</span><p></html> | |||
<!-- This page is assigned to the following categories: --> | <!-- This page is assigned to the following categories: --> | ||
[[Category:ITIL V3]][[Category:ITIL | [[Category:ITIL V3]][[Category:ITIL 2011]][[Category:ITIL stage]][[Category:ITIL process|4]][[Category:Service Operation|!]] | ||
<!-- --- --> | <!-- --- --> |
Latest revision as of 11:49, 31 December 2023
Objective: The objective of ITIL Service Operation is to make sure that IT services are delivered effectively and efficiently. The Service Operation lifecycle stage includes the fulfilling of user requests, resolving service failures, fixing problems, as well as carrying out routine operational tasks.
Part of: IT Service Management | ITIL processes
Processes: ITIL Service Operation
Service Operation carries out operational tasks.
The ITIL service lifecycle stage of Service Operation (see fig. 1) includes the following main processes:
- Event Management
- Process Objective: To make sure CIs and services are constantly monitored, and to filter and categorize Events in order to decide on appropriate actions.
- Incident Management
- Process Objective: To manage the lifecycle of all Incidents. The primary objective of Incident Management is to return the IT service to users as quickly as possible.
- Request Fulfilment
- Process Objective: To fulfill Service Requests, which in most cases are minor (standard) Changes (e.g. requests to change a password) or requests for information.
- Access Management
- Process Objective: To grant authorized users the right to use a service, while preventing access to non-authorized users. The Access Management processes essentially execute policies defined in Information Security Management. Access Management is sometimes also referred to as Rights Management or Identity Management.
- Problem Management
- Process Objective: To manage the lifecycle of all Problems. The primary objectives of Problem Management are to prevent Incidents from happening, and to minimize the impact of incidents that cannot be prevented. Proactive Problem Management analyzes Incident Records, and uses data collected by other IT Service Management processes to identify trends or significant Problems.
- IT Operations Control
- Process Objective: To monitor and control the IT services and their underlying infrastructure. The process IT Operations Control executes day-to-day routine tasks related to the operation of infrastructure components and applications. This includes job scheduling, backup and restore activities, print and output management, and routine maintenance.
- Facilities Management
- Process Objective: To manage the physical environment where the IT infrastructure is located. Facilities Management includes all aspects of managing the physical environment, for example power and cooling, building access management, and environmental monitoring.
- Application Management
- Process Objective: Application Management is responsible for managing applications throughout their lifecycle.
- Technical Management
- Process Objective: Technical Management provides technical expertise and support for the management of the IT infrastructure.
ITIL 4 Service Operation
The Service Operation processes described here (fig. 1) follow the specifications of ITIL V3, where Service Operation is the fourth stage in the Service Lifecycle.
ITIL V4 has moved from the Service Lifecycle concept to a more holistic approach that includes key concepts, the Four Dimensions Model and the Service Value System (SVS).
Instead of processes, ITIL 4 describes 34 'practices', and many of the 26 processes specified in ITIL V3 can be found in ITIL 4 as practices. For example, ITIL 4 refers to Incident Management and Problem Management as practices.
The shift from processes to practices means ITIL V4 is no longer prescriptive about processes and gives organizations more freedom to define tailor-made Service Operation processes.
Since the processes defined in ITIL V3 have not been invalidated with the introduction of ITIL V4, organizations that need to design their Service Operation processes can still use the processes specified in ITIL V3 as templates.
Note:
In our YaSM Service Management Wiki we describe a leaner set of 19 service management processes that are more in tune with ITIL 4 and its focus on simplicity and "just enough process".
The YaSM service management model includes a Service Operation process that is a good starting point for organizations that wish to adopt ITIL 4.
KPIs | Templates | Roles
- KPIs for Service Operation
- Service Operation templates and checklists
- ITIL roles within Service Operation
Downloads
Use the following links to open the process overview of Service Operation showing the most important interfaces:
Demo Service Operation: ITIL Process Map
The ITIL Process Map video shows samples of the ITIL process templates with contents from Service Operation and Incident Management processes, including the
- high-level view of the ITIL Service Lifecycle (Level 0)
- overview of the Service Operation process (Level 1)
- overview of the Incident Management process (Level 2)
- detailed process flow for the process "Incident Resolution by 1st Level Support" (Level 3)
Notes
By: Stefan Kempter , IT Process Maps.
ITIL 4 Service Operation › Event Management › Incident Mgmt. › Request Fulfilment › Access Mgmt. › Problem Mgmt. › [...]