Problem Management: Difference between revisions
No edit summary |
mNo edit summary |
||
Line 1: | Line 1: | ||
<seo metakeywords="problem management, itil problem management, problem management itil v3, itil v3 problem management, problem management process" metadescription="Problem Management: ITIL process definition - subprocesses - Additional information on Problem Management." /> | |||
<imagemap> | |||
Image:ITIL-Wiki-de-es.jpg|DE - ES - Problem Management|100px | |||
rect 0 0 50 30 [https://wiki.de.it-processmaps.com/index.php/Problem_Management diese Seite auf Deutsch] | |||
rect 50 0 100 30 [https://wiki.es.it-processmaps.com/index.php/ITIL_Gestion_de_Problemas esta página en español] | |||
desc none | |||
</imagemap> | |||
<br style="clear:both;"/> | |||
== ITIL Problem Management: Overview == | |||
'''Process Objective''': To manage the lifecycle of all Problems. The primary objectives of Problem Management are to prevent Incidents from happening, and to minimise the impact of incidents that cannot be prevented. Proactive Problem Management analyses Incident Records, and uses data collected by other IT Service Management processes to identify trends or significant Problems. | '''Process Objective''': To manage the lifecycle of all Problems. The primary objectives of Problem Management are to prevent Incidents from happening, and to minimise the impact of incidents that cannot be prevented. Proactive Problem Management analyses Incident Records, and uses data collected by other IT Service Management processes to identify trends or significant Problems. | ||
Line 10: | Line 14: | ||
'''Part of''': [[ITIL V3 Service Operation|Service Operation]] | '''Part of''': [[ITIL V3 Service Operation|Service Operation]] | ||
'''Process Owner''': [[ | '''Process Owner''': [[Problem Management#ITIL Roles in Problem Management|Problem Manager]] | ||
==ITIL | == ITIL Problem Management: Process Definition == | ||
[[Image:Itil-problem-management.jpg|thumb=overview_problem_management_itilv3_thumb.jpg|left|[https://wiki.en.it-processmaps.com/images/pdf/process_overview_problem_management_itilv3.pdf ITIL Problem Management]]] | |||
Essentially, the activities and process objectives of the Problem Management process are identical in ITIL V3 and ITIL V2. A new sub-process "[[Problem Management#Major Problem Review|Major Problem Review]]" was introduced to review the solution history of major Problems in order to prevent a recurrence and learn lessons for the future. | |||
The following sub-processes are part of [[Problem Management|ITIL Problem Management]]: | |||
<br style="clear:both;"/> | |||
=== Sub-Processes === | |||
;Problem and Error Control | ;Problem and Error Control | ||
:Process Objective: To constantly monitor outstanding Problems with regards to their processing status, so that where necessary corrective measures may be introduced. | :Process Objective: To constantly monitor outstanding [[Problem Management#Problem|Problems]] with regards to their processing status, so that where necessary corrective measures may be introduced. | ||
;Problem Identification and Categorization | ;Problem Identification and Categorization | ||
:Process Objective: To record and prioritize the Problem with appropriate deligence, in order to facilitate a swift and effective resolution. | :Process Objective: To [[Problem Management#Problem Record|record and prioritize the Problem]] with appropriate deligence, in order to facilitate a swift and effective resolution. | ||
;Problem Diagnosis and Resolution | ;Problem Diagnosis and Resolution | ||
:Process Objective: To identify the underlying root cause of a Problem and initiate the most appropriate and economical Problem solution. If possible, a temporary Workaround is supplied. | :Process Objective: To identify the underlying root cause of a Problem and initiate the most appropriate and economical Problem solution. If possible, a temporary [[Problem Management#Workaround|Workaround]] is supplied. | ||
;Problem Closure and Evaluation | ;Problem Closure and Evaluation | ||
:Process Objective: To ensure that - after a successful Problem solution - the Problem Record contains a full historical description, and that related Known Error Records are updated. | :Process Objective: To ensure that - after a successful Problem solution - the [[Problem Management#Problem Record|record and prioritize the Problem]] contains a full historical description, and that related [[Problem Management#Known Error|Known Error]] Records are updated. | ||
;Major Problem Review | ;<span id="Major Problem Review">Major Problem Review</span> | ||
:Process Objective: To review the resolution of a Problem in order to prevent recurrence and learn any lessons for the future. Furthermore it is to be verified whether the | :Process Objective: To review the resolution of a Problem in order to prevent recurrence and learn any lessons for the future. Furthermore it is to be verified whether the Problems marked as closed have actually been eliminated. | ||
;Problem Management Reporting | ;Problem Management Reporting | ||
:Process Objective: To ensure that the other Service Management processes as well as IT Management are informed of outstanding Problems, their processing-status and existing Workarounds. | :Process Objective: To ensure that the other Service Management processes as well as IT Management are informed of outstanding Problems, their processing-status and existing Workarounds (see "[[Problem Management#Problem Management Report|Problem Management Report]]"). | ||
== | ===== Downloads ===== | ||
Use the following links to open the process overview of Problem Management showing the most important interfaces: | |||
* [[Media:Itil-problem-management.jpg|ITIL Problem Management (.JPG)]] | |||
* [https://wiki.en.it-processmaps.com/images/pdf/process_overview_problem_management_itilv3.pdf ITIL Problem Management (.PDF)]'' | |||
* [[Roles | === ITIL Terms: Problem Management === | ||
;<span id="Known Error">Known Error</span> | |||
:A problem that has a documented root cause and a workaround. Known Errors are created and managed throughout their lifecycle by Problem Management. Known Errors may also be identified by development or suppliers. | |||
;<span id="Problem">Problem</span> | |||
:A cause of one or more [[Incident Management#Incident|Incidents]]. The cause is not usually known at the time a Problem Record is created. | |||
;<span id="Problem Management Report">Problem Management Report</span> | |||
:A report supplying Problem-related information to the other Service Management processes. | |||
;<span id="Problem Record">Problem Record</span> | |||
:The Problem Record contains all details of a Problem, documenting the history of the Problem from detection to resolution ([[Checklist Problem Record|ITIL Checklist Problem Record]]). | |||
;<span id="Suggested Known Error">Suggested Known Error</span> | |||
:A suggestion to create a new entry in the Known Error Database, for example raised by the Service Desk or by Release Management. Known Errors are managed throughout their lifecycle by Problem Management. | |||
;<span id="Suggested Problem">Suggested Problem</span> | |||
:A notification about a suspected Problem, handed over to Problem Management for further investigation. | |||
;<span id="Suggested Workaround">Suggested Workaround</span> | |||
:A suggestion to enter a new Workaround in the Known Error Database, for example raised by the Service Desk or by Release Management. Workarounds are managed throughout their lifecycle by Problem Management. | |||
;<span id="Workaround">Workaround</span> | |||
:Reducing or eliminating the impact of an Incident or Problem for which a full resolution is not yet available, for example by restarting a failed Configuration Item. Workarounds for Problems are documented in Known Error records. | |||
== Additional Information on Problem Management == | |||
==== ITIL KPIs and Checklists ==== | |||
* [[ITIL KPIs Service Operation#ITIL KPIs Problem Management|Key Performance Indicators (KPIs) Problem Management]] | |||
* [[Checklist Problem Record|Checklists Problem Management: Checklist Problem Record]] | |||
==== ITIL Roles in Problem Management ==== | |||
;Problem Manager - Process Owner | |||
: The Problem Manager is responsible for managing the lifecycle of all Problems. | |||
: His primary objectives are to prevent Incidents from happening, and to minimise the impact of Incidents that cannot be prevented. | |||
:To this purpose he maintains information about Known Errors and Workarounds. | |||
<i><small>[[Main Page|Home]] > [[ITIL Processes]] > [[ITIL V3 Service Operation|Service Operation]] > [[Problem Management|Problem Management]]</small></i> | |||
<!-- This page is assigned to the following categories: --> | |||
[[Category:ITIL V3]][[Category:ITIL process]][[Category:Service Operation|Problem Management]][[Category:Problem Management|!]] | |||
<!-- --- --> |
Revision as of 10:35, 13 July 2011
<seo metakeywords="problem management, itil problem management, problem management itil v3, itil v3 problem management, problem management process" metadescription="Problem Management: ITIL process definition - subprocesses - Additional information on Problem Management." />
ITIL Problem Management: Overview
Process Objective: To manage the lifecycle of all Problems. The primary objectives of Problem Management are to prevent Incidents from happening, and to minimise the impact of incidents that cannot be prevented. Proactive Problem Management analyses Incident Records, and uses data collected by other IT Service Management processes to identify trends or significant Problems.
Part of: Service Operation
Process Owner: Problem Manager
ITIL Problem Management: Process Definition
Essentially, the activities and process objectives of the Problem Management process are identical in ITIL V3 and ITIL V2. A new sub-process "Major Problem Review" was introduced to review the solution history of major Problems in order to prevent a recurrence and learn lessons for the future.
The following sub-processes are part of ITIL Problem Management:
Sub-Processes
- Problem and Error Control
- Process Objective: To constantly monitor outstanding Problems with regards to their processing status, so that where necessary corrective measures may be introduced.
- Problem Identification and Categorization
- Process Objective: To record and prioritize the Problem with appropriate deligence, in order to facilitate a swift and effective resolution.
- Problem Diagnosis and Resolution
- Process Objective: To identify the underlying root cause of a Problem and initiate the most appropriate and economical Problem solution. If possible, a temporary Workaround is supplied.
- Problem Closure and Evaluation
- Process Objective: To ensure that - after a successful Problem solution - the record and prioritize the Problem contains a full historical description, and that related Known Error Records are updated.
- Major Problem Review
- Process Objective: To review the resolution of a Problem in order to prevent recurrence and learn any lessons for the future. Furthermore it is to be verified whether the Problems marked as closed have actually been eliminated.
- Problem Management Reporting
- Process Objective: To ensure that the other Service Management processes as well as IT Management are informed of outstanding Problems, their processing-status and existing Workarounds (see "Problem Management Report").
Downloads
Use the following links to open the process overview of Problem Management showing the most important interfaces:
ITIL Terms: Problem Management
- Known Error
- A problem that has a documented root cause and a workaround. Known Errors are created and managed throughout their lifecycle by Problem Management. Known Errors may also be identified by development or suppliers.
- Problem
- A cause of one or more Incidents. The cause is not usually known at the time a Problem Record is created.
- Problem Management Report
- A report supplying Problem-related information to the other Service Management processes.
- Problem Record
- The Problem Record contains all details of a Problem, documenting the history of the Problem from detection to resolution (ITIL Checklist Problem Record).
- Suggested Known Error
- A suggestion to create a new entry in the Known Error Database, for example raised by the Service Desk or by Release Management. Known Errors are managed throughout their lifecycle by Problem Management.
- Suggested Problem
- A notification about a suspected Problem, handed over to Problem Management for further investigation.
- Suggested Workaround
- A suggestion to enter a new Workaround in the Known Error Database, for example raised by the Service Desk or by Release Management. Workarounds are managed throughout their lifecycle by Problem Management.
- Workaround
- Reducing or eliminating the impact of an Incident or Problem for which a full resolution is not yet available, for example by restarting a failed Configuration Item. Workarounds for Problems are documented in Known Error records.
Additional Information on Problem Management
ITIL KPIs and Checklists
- Key Performance Indicators (KPIs) Problem Management
- Checklists Problem Management: Checklist Problem Record
ITIL Roles in Problem Management
- Problem Manager - Process Owner
- The Problem Manager is responsible for managing the lifecycle of all Problems.
- His primary objectives are to prevent Incidents from happening, and to minimise the impact of Incidents that cannot be prevented.
- To this purpose he maintains information about Known Errors and Workarounds.
Home > ITIL Processes > Service Operation > Problem Management