Checklist Problem Record: Difference between revisions

From IT Process Wiki
mNo edit summary
mNo edit summary
Line 8: Line 8:
<br style="clear:both;"/>
<br style="clear:both;"/>


'''ITIL Process''': [[ITIL V3 Service Operation]] - [[Problem Management]]
'''ITIL Process''': [[ITIL V3 Service Operation|ITIL 2011 Service Operation]] - [[Problem Management]]


'''Checklist Category:''' [[ITIL-Checklists#Checklists ITIL V3 Service Operation|Checklists ITIL V3 Service Operation]]
'''Checklist Category:''' [[ITIL-Checklists#Checklists ITIL V3 Service Operation|Checklists ITIL Service Operation]]


'''Source''': Checklist "Problem Record" from the [https://en.it-processmaps.com/products/itil-process-map.html ITIL Process Map V3]
'''Source''': Checklist "Problem Record" from the [https://en.it-processmaps.com/products/itil-process-map.html ITIL Process Map]


<p>&nbsp;</p>
<p>&nbsp;</p>
Line 41: Line 41:
## Priority (for example in stages 1, 2 and 3): The result from the combination of urgency and the degree of severity
## Priority (for example in stages 1, 2 and 3): The result from the combination of urgency and the degree of severity
# Relationships to [[Service Asset and Configuration Management#CI|CIs]]
# Relationships to [[Service Asset and Configuration Management#CI|CIs]]
# Product category, usually selected from a category-tree according to the following example:
# Problem category, usually selected from a category-tree according to the following example (Problem categories should be harmonized with CI and Incident categories to support matching between Incidents, Problems and CIs):
## Client PC
### Standard configuration 1
### ...
## Printer
### Manufacturer 1
### ...
# Problem category, usually selected from a category-tree according to the following example:  
## Hardware error
## Hardware error
### Server A
#### Component x
##### Symptom a
##### Symptom b
#### Component y
#### …
### Server B
### …
## Software error
## Software error
### System A
### System B
### …
## Network error
## ...
## ...
# Links to related Problem Records (if there are other outstanding Problems related to this one)
# Links to related Problem Records (if there are other outstanding Problems related to this one)
# Links to related [[Incident Management#Incident Record|Incident Records]] (if outstanding Incidents exist, whose solution depends on the solution of this Problem)
# Links to related [[Incident Management#Incident Record|Incident Records]] (if outstanding Incidents exist, whose solution depends on the solution of this Problem)
# Links to [[Problem Management#Known Error|Known Errors]] and [[Problem Management#Workaround|Workarounds]] (if Known Errors and Workarounds related to the Problem have been identified)
# Links to [[Problem Management#Known Error|Known Errors]] and [[Problem Management#Workaround|Workarounds]] (if Known Errors and Workarounds related to the Problem have been identified)
# Problem Recovery Procedures: Any procedures that are required to be performed to eliminate the Problem. These procedures may need to be performed as part of removing Workarounds that have been applied while solving related Incidents.
# Activity log/ resolution history
# Activity log/ resolution history
## Date and time
## Date and time
Line 65: Line 71:
<!-- This page is assigned to the following categories: -->
<!-- This page is assigned to the following categories: -->
[[Category:ITIL V3|Problem Record]]
[[Category:ITIL V3|Problem Record]]
[[Category:ITIL 2011|Problem Record]]
[[Category:Checklist (ITIL)|Problem Record]]
[[Category:Checklist (ITIL)|Problem Record]]
[[Category:Service Operation|Problem Record]]
[[Category:Service Operation|Problem Record]]
[[Category:Incident Management|Problem Record]]
[[Category:Incident Management|Problem Record]]
<!-- --- -->
<!-- --- -->

Revision as of 16:05, 30 December 2011

<seo metakeywords="problem record, problem record template, problem record checklist" metadescription="The Problem Record contains all details of a Problem, documenting the history of the Problem from detection to resolution. ..." />

DE - ES - Checklist Problem Record - Template Problem Recorddiese Seite auf Deutschesta página en español
DE - ES - Checklist Problem Record - Template Problem Record


ITIL Process: ITIL 2011 Service Operation - Problem Management

Checklist Category: Checklists ITIL Service Operation

Source: Checklist "Problem Record" from the ITIL Process Map

 

The Problem Record contains all details of a Problem, documenting the history of the Problem from detection to resolution.

 

A Problem Record typically contains the following information:

 

  1. Unique ID of the Problem (usually allocated automatically by the system)
  2. Date and time of detection
  3. Problem owner
  4. Description of symptoms
  5. Affected users/ business areas
  6. Affected service(s)
  7. Prioritization, a function of the following components:
    1. Urgency (available time until the resolution of the Problem), e.g.
      1. Up to 5 working days
      2. Up to 2 weeks
      3. Up to 4 weeks
    2. Degree of severity (damage caused to the business), e.g.
      1. "High" (interruption to critical business processes)
      2. "Normal" (interruption to the work of individual employees)
      3. "Low" (hindrance to the work of individual employees, continuation of work possible by means of a circumventive solution)
    3. Priority (for example in stages 1, 2 and 3): The result from the combination of urgency and the degree of severity
  8. Relationships to CIs
  9. Problem category, usually selected from a category-tree according to the following example (Problem categories should be harmonized with CI and Incident categories to support matching between Incidents, Problems and CIs):
    1. Hardware error
      1. Server A
        1. Component x
          1. Symptom a
          2. Symptom b
        2. Component y
      2. Server B
    2. Software error
      1. System A
      2. System B
    3. Network error
    4. ...
  10. Links to related Problem Records (if there are other outstanding Problems related to this one)
  11. Links to related Incident Records (if outstanding Incidents exist, whose solution depends on the solution of this Problem)
  12. Links to Known Errors and Workarounds (if Known Errors and Workarounds related to the Problem have been identified)
  13. Problem Recovery Procedures: Any procedures that are required to be performed to eliminate the Problem. These procedures may need to be performed as part of removing Workarounds that have been applied while solving related Incidents.
  14. Activity log/ resolution history
    1. Date and time
    2. Person in charge
    3. Description of activities
    4. New Problem status (if the activity results in a change of status)