Service Desk and Incident Management: Difference between revisions

From IT Process Wiki
No edit summary
 
No edit summary
 
(2 intermediate revisions by the same user not shown)
Line 1: Line 1:
{|
<itpmch><title>Service Desk and Incident Management | IT Process Wiki</title>
! align="right" width="80%"|
<meta name="keywords" content="Service Desk and Incident Management, incident management itil v2" />
! style="background:#DDDDDD;" align="right" width="20%"| [https://wiki.de.it-processmaps.com/index.php/Service_Desk_and_Incident_Management diese Seite auf Deutsch]
<meta name="description" content="&#8594; See also Incident Management ITIL V3. Process Objective: ... aims to restore IT Services to their defined Service Levels as quickly as possible. ..." />
|}
</itpmch>
<imagemap>
Image:ITIL-Wiki-deutsch.jpg|right|ITIL V2 Service Desk and Incident Management
default [https://wiki.de.it-processmaps.com/index.php/Service_Desk_and_Incident_Management diese Seite auf Deutsch]
desc none
</imagemap>
<br style="clear:both;"/>


'''ITIL Version''': ITIL Version 2 (ITIL V2)
'''ITIL Version''': ITIL V2 '''&#8594;''' see also '''[[Incident Management|Incident Management - ITIL V3]]'''


'''Process Objective:''' The "Service Desk and Incident Management" process aims to restore IT Services to their defined Service Levels as quickly as possible The process is also responsible for receiving and processing Service Requests, for assisting users, and for coordinating the Incident Resolution with Specialist Support Groups. Throughout the process, users are informed at regular intervals about their Incidents' status.
'''Process Objective:''' The "Service Desk and Incident Management" process aims to restore IT Services to their defined Service Levels as quickly as possible The process is also responsible for receiving and processing Service Requests, for assisting users, and for coordinating the Incident Resolution with Specialist Support Groups. Throughout the process, users are informed at regular intervals about their Incidents' status.
Line 10: Line 16:
'''Part of''': [[Service Support]]
'''Part of''': [[Service Support]]


'''Process Owner''': [[Roles_within_ITIL#Incident Manager|Incident Manager]]
'''Process Owner''': [[ITIL Roles#Incident Manager|Incident Manager]]


<p>&nbsp;</p>


==Sub-Processes==
==Sub-Processes==


[[Image:overview_sd_im.jpg|frame|none|Overview of Service Desk and Incident Management]]
[[Image:overview_sd_im.jpg|thumb|739px|none|link=https://wiki.en.it-processmaps.com/index.php/File:Overview_sd_im.jpg|Overview of Service Desk and Incident Management]]


'''Register Incident'''
*Process objective: The Incident shall be recorded and documented in appropriate quality, in order to facilitate a swift and effective solution.


;Register Incident
'''Process Service Request'''
:Process objective: The Incident shall be recorded and documented in appropriate quality, in order to facilitate a swift and effective solution.
*Process objective: An Incident of the type Service Request is to be completely processed within the agreed resolution time.


;Process Service Request
'''Immediate Incident Resolution by 1st Level Support'''
:Process objective: An Incident of the type Service Request is to be completely processed within the agreed resolution time.
*Process objective: An Incident of the type Service interruption is to be solved within the agreed solution period. The aim is the fast recovery of the IT Service, where necessary with the aid of a [[ITIL Glossary#Workaround|Workaround]]. The solution is to take place, where possible, upon the first attempt by 1st Level Support; if this is not possible, the Incident is transfered to a suitable group within 2nd Level Support.


;Immediate Incident Resolution by 1st Level Support
'''Analyse and Resolve Incident in 2nd Level Support'''
:Process objective: An Incident of the type Service interruption is to be solved within the agreed solution period. The aim is the fast recovery of the IT Service, where necessary with the aid of a [[ITIL Glossary#Workaround|Workaround]]. The solution is to take place, where possible, upon the first attempt by 1st Level Support; if this is not possible, the Incident is transfered to a suitable group within 2nd Level Support.
*Process objective: If possible, the root cause of the Service interruption should be corrected, or at least a [[ITIL Glossary#Workaround|Workaround]] applied. If the correction of the root cause is not possible, a Problem Record is created and the error-correction transfered to Problem Management.


;Analyse and Resolve Incident in 2nd Level Support
'''Monitor and Escalate Incidents'''
:Process objective: If possible, the root cause of the Service interruption should be corrected, or at least a [[ITIL Glossary#Workaround|Workaround]] applied. If the correction of the root cause is not possible, a Problem Record is created and the error-correction transfered to Problem Management.
*Process objective: The processing status of outstanding Incidents is to be continuously monitored, so that counter-measures may be introduced as soon as possible if Service Levels are likely to be breached.


;Monitor and Escalate Incidents
'''Pro-Actively Inform Users'''
:Process objective: The processing status of outstanding Incidents is to be continuously monitored, so that counter-measures may be introduced as soon as possible if Service Levels are likely to be breached.
*Process objective: The users are to be informed of detractions to the IT Services as soon as these are known to the Service Desk. The users are then placed in a position to adjust themselves to interruptions, and the number of inquiries by users is reduced.


;Pro-Actively Inform Users
'''Close and Evaluate Incident'''
:Process objective: The users are to be informed of detractions to the IT Services as soon as these are known to the Service Desk. The users are then placed in a position to adjust themselves to interruptions, and the number of inquiries by users is reduced.
*Process objective: Before the final closure of the Incident, it is to be submitted to a quality-control with regards to the resolution. In addition to this, findings from the resolution of the Incident are to be recorded for the future.
 
;Close and Evaluate Incident
:Process objective: Before the final closure of the Incident, it is to be submitted to a quality-control with regards to the resolution. In addition to this, findings from the resolution of the Incident are to be recorded for the future.
 
;Maintenance of Support Knowledge Base
:Process objective: Findings from the processing of Incidents as well as information from other Service Management Processes are to be incorporated into the [[ITIL Glossary#Support Knowledge Base|Support Knowledge Base]] in a structured and quality-assured manner, so that future Incidents can be more efficiently processed.
 
;Carry out [[ITIL Glossary#Incident Management Report|Incident Management Reporting]]
:Process objective: It is to be ensured that (a) improvement potentials are derived from past Incidents, and (b) the other Service Management Processes have the information necessary from Incident Management that are required to fulfill their tasks.
 
 
[https://en.it-processmaps.com/itil-implementation-using-process-templates/best-practice-for-process-modelling.html Click here] to view '''the complete set of process models describing the "Service Desk and Incident Management" process''': An example how process modelling can be used in order to make the process dependencies transparent, while still defining processes in sufficient detail (this is an external link to the IT Process Maps web site).


'''Maintenance of Support Knowledge Base'''
*Process objective: Findings from the processing of Incidents as well as information from other Service Management Processes are to be incorporated into the [[ITIL Glossary#Support Knowledge Base|Support Knowledge Base]] in a structured and quality-assured manner, so that future Incidents can be more efficiently processed.


'''Carry out [[ITIL Glossary#Incident Management Report|Incident Management Reporting]]'''
*Process objective: It is to be ensured that (a) improvement potentials are derived from past Incidents, and (b) the other Service Management Processes have the information necessary from Incident Management that are required to fulfill their tasks.


==Involved Roles==
==Involved Roles==
* [[Roles within ITIL#Incident Manager|Incident Manager]]
*[[ITIL Roles#Incident Manager|Incident Manager]]
* [[Roles within ITIL#1st Level Support|1st Level Support]]
*[[ITIL Roles#1st Level Support|1st Level Support]]
* [[Roles within ITIL#2nd Level Support|2nd Level Support]]
*[[ITIL Roles#2nd Level Support|2nd Level Support]]
* [[Roles within ITIL#3rd Level Support|3rd Level Support]]
*[[ITIL Roles#3rd Level Support|3rd Level Support]]


==Related Checklists and KPIs==
==Related Checklists and KPIs==


==== Checklists ====
==== Checklists ====
*[[Checklist Incident Record]]
*[[ITIL-Checklists#Incident Management / Service Desk|Checklists Service Desk and Incident Management]]
*[[Checklist Initial Analysis of an Incident]]
*[[Checklist Incident Priority]]
*[[Checklist Incident Escalation]]
*[[Checklist Closure of an Incident]]
*[[Checklist Incident Report]]


==== KPIs ====
==== KPIs ====
*[[KPIs Service Desk and Incident Management|Key Performance Indicators "Service Desk and Incident Management" according to ITIL V2]]
*[[KPIs Service Desk and Incident Management|Key Performance Indicators "Service Desk and Incident Management" according to ITIL V2]]


==Related [[ITIL Glossary]] Terms==
*[[ITIL Glossary/_ITIL_Terms_I#Incident Record|Incident Record]]
*[[ITIL Glossary/_ITIL_Terms_W#Workaround|Workaround]]
*[[ITIL Glossary/_ITIL_Terms_K#Known Error|Known Error]]
*[[ITIL Glossary/_ITIL_Terms_S#Support Knowledge Base|Support Knowledge Base]]
*[[ITIL Glossary/_ITIL_Terms_I#Incident Management Report|Incident Management Report]]
<p>&nbsp;</p>
<!-- This page is assigned to the following categories: -->
[[Category:ITIL V2]][[Category:ITIL process]][[Category:Service Support]][[Category:Incident Management]]
<!-- --- -->


==Related ITIL Glossary Terms==
* [[ITIL Glossary#Incident Record|Incident Record]]
* [[ITIL Glossary#Workaround|Workaround]]
* [[ITIL Glossary#Known Error|Known Error]]
* [[ITIL Glossary#Support Knowledge Base|Support Knowledge Base]]
* [[ITIL Glossary#Incident Management Report|Incident Management Report]]

Latest revision as of 18:53, 4 February 2016

ITIL V2 Service Desk and Incident Management
ITIL V2 Service Desk and Incident Management


ITIL Version: ITIL V2 → see also Incident Management - ITIL V3

Process Objective: The "Service Desk and Incident Management" process aims to restore IT Services to their defined Service Levels as quickly as possible The process is also responsible for receiving and processing Service Requests, for assisting users, and for coordinating the Incident Resolution with Specialist Support Groups. Throughout the process, users are informed at regular intervals about their Incidents' status.

Part of: Service Support

Process Owner: Incident Manager

 

Sub-Processes

Overview of Service Desk and Incident Management

Register Incident

  • Process objective: The Incident shall be recorded and documented in appropriate quality, in order to facilitate a swift and effective solution.

Process Service Request

  • Process objective: An Incident of the type Service Request is to be completely processed within the agreed resolution time.

Immediate Incident Resolution by 1st Level Support

  • Process objective: An Incident of the type Service interruption is to be solved within the agreed solution period. The aim is the fast recovery of the IT Service, where necessary with the aid of a Workaround. The solution is to take place, where possible, upon the first attempt by 1st Level Support; if this is not possible, the Incident is transfered to a suitable group within 2nd Level Support.

Analyse and Resolve Incident in 2nd Level Support

  • Process objective: If possible, the root cause of the Service interruption should be corrected, or at least a Workaround applied. If the correction of the root cause is not possible, a Problem Record is created and the error-correction transfered to Problem Management.

Monitor and Escalate Incidents

  • Process objective: The processing status of outstanding Incidents is to be continuously monitored, so that counter-measures may be introduced as soon as possible if Service Levels are likely to be breached.

Pro-Actively Inform Users

  • Process objective: The users are to be informed of detractions to the IT Services as soon as these are known to the Service Desk. The users are then placed in a position to adjust themselves to interruptions, and the number of inquiries by users is reduced.

Close and Evaluate Incident

  • Process objective: Before the final closure of the Incident, it is to be submitted to a quality-control with regards to the resolution. In addition to this, findings from the resolution of the Incident are to be recorded for the future.

Maintenance of Support Knowledge Base

  • Process objective: Findings from the processing of Incidents as well as information from other Service Management Processes are to be incorporated into the Support Knowledge Base in a structured and quality-assured manner, so that future Incidents can be more efficiently processed.

Carry out Incident Management Reporting

  • Process objective: It is to be ensured that (a) improvement potentials are derived from past Incidents, and (b) the other Service Management Processes have the information necessary from Incident Management that are required to fulfill their tasks.

Involved Roles

Related Checklists and KPIs

Checklists

KPIs

Related ITIL Glossary Terms

 

Retrieved from "https://wiki.en.it-processmaps.com/index.php?title=Service_Desk_and_Incident_Management&oldid=8528"