Problem Management - ITIL V2: 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>Problem Management - ITIL V2 | IT Process Wiki</title>
! align="right" width="80%"|
<meta name="keywords" content="problem management itil v2" />
! style="background:#DDDDDD;" align="right" width="20%"| [https://wiki.de.it-processmaps.com/index.php/Problem_Management_-_ITIL_V2 diese Seite auf Deutsch]
<meta name="description" content="&#8594; See also Problem Management ITIL V3. Process Objective: ... resolve the root cause of Incidents, and to prevent the recurrence of Incidents ..." />
|}
</itpmch>
<imagemap>
Image:ITIL-Wiki-deutsch.jpg|right|ITIL V2 Problem Management
default [https://wiki.de.it-processmaps.com/index.php/Problem_Management_-_ITIL_V2 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 '''[[Problem Management|Problem Management - ITIL V3]]'''


'''Process-Objective:''' The objective of Problem Management is to resolve the root cause of Incidents, and to prevent the recurrence of Incidents related to these errors. It provides Incident Management with Temporary Fixes ([[ITIL Glossary#Workaround|Workarounds]]) and Permanent Solutions to [[ITIL Glossary#Known Error|Known Errors]]. Proactive Problem Management identifies and resolves Problems before Incidents occur, for example by analysing trends in IT Service Usage or by investigating historic Incidents.
'''Process-Objective:''' The objective of Problem Management is to resolve the root cause of Incidents, and to prevent the recurrence of Incidents related to these errors. It provides Incident Management with Temporary Fixes ([[ITIL Glossary#Workaround|Workarounds]]) and Permanent Solutions to [[ITIL Glossary#Known Error|Known Errors]]. Proactive Problem Management identifies and resolves Problems before Incidents occur, for example by analysing trends in IT Service Usage or by investigating historic Incidents.
Line 10: Line 16:
'''Part of''': [[Service Support]]
'''Part of''': [[Service Support]]


'''Process Owner''': [[Roles_within_ITIL#Problem Manager|Problem Manager]]
'''Process Owner''': [[#Problem Manager ITIL V2|Problem Manager]]


<p>&nbsp;</p>


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


[[Image:overview_pm.jpg|frame|none|Overview of Problem Management]]
[[Image:overview_pm.jpg|thumb|728px|none|link=https://wiki.en.it-processmaps.com/index.php/File:Overview_pm.jpg|Overview of Problem Management]]


'''Identify and Analyse Problem'''
*Process objective: Past Incidents and other indications of problems in the IT infrastructure are to be analysed, in order to find the root causes of repeatedly occurring IT Service interruptions.


;Identify and Analyse Problem
'''Identify Problem Solution'''
:Process objective: Past Incidents and other indications of problems in the IT infrastructure are to be analysed, in order to find the root causes of repeatedly occurring IT Service interruptions.
*Process objective: A resolution is to be found for identified Problems and a corresponding RFC, initiating the implementation of the resolution, is to be compiled.


;Identify Problem Solution
'''Monitor Problems and Errors'''
:Process objective: A resolution is to be found for identified Problems and a corresponding RFC, initiating the implementation of the resolution, is to be compiled.
*Process objective: Outstanding Problems are to be continuously monitored with regards to their processing status, so that where necessary corrective measures may be introduced. Furthermore it is to be verified whether the Problems marked as Closed have actually been eliminated.


;Monitor Problems and Errors
'''Develop Problem Solution'''
:Process objective: Outstanding Problems are to be continuously monitored with regards to their processing status, so that where necessary corrective measures may be introduced. Furthermore it is to be verified whether the Problems marked as Closed have actually been eliminated.
*Process objective: After the clearance of the Change the actual error-correction is to be developed and subsequently transfered to Release Management for Rollout.


;Develop Problem Solution
'''Close Problem'''
:Process objective: After the clearance of the Change the actual error-correction is to be developed and subsequently transfered to Release Management for Rollout.
*Process objective: After a successful problem solution it is to be ensured that the knowledge gained is made available to the other IT Service Management processes, in order to be used for the handling of future Problems or Incidents.
 
;Close Problem
:Process objective: After a successful problem solution it is to be ensured that the knowledge gained is made available to the other IT Service Management processes, in order to be used for the handling of future Problems or Incidents.
 
;Compile [[ITIL Glossary#Problem Management Report|Problem Management Reporting]]
:Process objective: It is to be ensured that the other IT Service Management processes as well as IT Management are informed of outstanding Problems, their processing-status and existing Workarounds.


'''Compile [[ITIL Glossary#Problem Management Report|Problem Management Reporting]]'''
*Process objective: It is to be ensured that the other IT Service Management processes as well as IT Management are informed of outstanding Problems, their processing-status and existing Workarounds.


==Involved Roles==
==Involved Roles==
* [[Roles within ITIL#Application Manager|Application Manager]]
*[[ITIL Roles#Application-Manager|Application Manager]]
* [[Roles within ITIL#ITC Infrastructure Manager|ITC Infrastructure Manager]]
*[[ITIL Roles#ITC-Infrastructure-Manager|ITC Infrastructure Manager]]
* [[Roles within ITIL#Problem Manager|Problem Manager]]
*'''<span id="Problem Manager ITIL V2">Problem Manager</span>''': According to ITIL V2 the Problem Manager undertakes research for the root-causes of Incidents and thus ensures the enduring elimination of interruptions. If possible, he makes temporary solutions (Workarounds) available to Incident Management. He develops final solutions for Known Errors. In addition to this he engages in the avoidance of interruptions (Pro-active Problem Management), i.e via a trend-analysis of important services or historical Incidents.
 


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


==== Checklists ====
==== Checklists ====
*[[Checklist Problem Record]]
*[[ITIL-Checklists#Problem Management|Checklists Problem Management]]
*[[Checklist Problem Priority]]
*[[Checklist Closure of a Problem]]
*[[Checklist Problem Report]]


==== KPIs ====
==== KPIs ====
*[[KPIs Problem Management|Key Performance Indicators "Problem Management" according to ITIL V2]]
*[[KPIs Problem Management|Key Performance Indicators "Problem Management" according to ITIL V2]]


==Related [[ITIL Glossary]] Terms==
*[[ITIL Glossary/_ITIL_Terms_P#Problem Record|Problem Record]]
*[[ITIL Glossary/_ITIL_Terms_P#Problem Management Report|Problem Management Report]]


==Related ITIL Glossary Terms==
<!-- This page is assigned to the following categories: -->
* [[ITIL Glossary#Problem Record|Problem Record]]
[[Category:ITIL V2]][[Category:ITIL process]][[Category:Service Support]][[Category:Problem Management]]
* [[ITIL Glossary#Problem Management Report|Problem Management Report]]
<!-- --- -->

Latest revision as of 17:53, 4 February 2016

ITIL V2 Problem Management
ITIL V2 Problem Management


ITIL Version: ITIL V2 see also Problem Management - ITIL V3

Process-Objective: The objective of Problem Management is to resolve the root cause of Incidents, and to prevent the recurrence of Incidents related to these errors. It provides Incident Management with Temporary Fixes (Workarounds) and Permanent Solutions to Known Errors. Proactive Problem Management identifies and resolves Problems before Incidents occur, for example by analysing trends in IT Service Usage or by investigating historic Incidents.

Part of: Service Support

Process Owner: Problem Manager

 

Sub-Processes

Overview of Problem Management

Identify and Analyse Problem

  • Process objective: Past Incidents and other indications of problems in the IT infrastructure are to be analysed, in order to find the root causes of repeatedly occurring IT Service interruptions.

Identify Problem Solution

  • Process objective: A resolution is to be found for identified Problems and a corresponding RFC, initiating the implementation of the resolution, is to be compiled.

Monitor Problems and Errors

  • Process objective: Outstanding Problems are to be continuously monitored with regards to their processing status, so that where necessary corrective measures may be introduced. Furthermore it is to be verified whether the Problems marked as Closed have actually been eliminated.

Develop Problem Solution

  • Process objective: After the clearance of the Change the actual error-correction is to be developed and subsequently transfered to Release Management for Rollout.

Close Problem

  • Process objective: After a successful problem solution it is to be ensured that the knowledge gained is made available to the other IT Service Management processes, in order to be used for the handling of future Problems or Incidents.

Compile Problem Management Reporting

  • Process objective: It is to be ensured that the other IT Service Management processes as well as IT Management are informed of outstanding Problems, their processing-status and existing Workarounds.

Involved Roles

  • Application Manager
  • ITC Infrastructure Manager
  • Problem Manager: According to ITIL V2 the Problem Manager undertakes research for the root-causes of Incidents and thus ensures the enduring elimination of interruptions. If possible, he makes temporary solutions (Workarounds) available to Incident Management. He develops final solutions for Known Errors. In addition to this he engages in the avoidance of interruptions (Pro-active Problem Management), i.e via a trend-analysis of important services or historical Incidents.

Related Checklists and KPIs

Checklists

KPIs

Related ITIL Glossary Terms