Checklist Problem Record: Difference between revisions
No edit summary |
No edit summary |
||
| Line 1: | Line 1: | ||
<itpmch><title>Checklist Problem Record | IT Process Wiki</title> | <itpmch><title>Checklist Problem Record | IT Process Wiki</title> | ||
<meta name="keywords" content="problem record, itil problem record, problem record itil, problem record template, problem record checklist" /> | <meta name="keywords" content="problem record, itil problem record, problem record itil, problem record template, problem record checklist" /> | ||
<meta name="description" content="The 'Problem Record' contains all details of a Problem, documenting the history of the Problem from detection to closure." /> | <meta name="description" content="The 'Problem Record' contains all details of a Problem, documenting the history of the Problem from detection to closure. A 'Problem' is defined as a cause of one or more incidents; the cause is not usually known at the time a Problem Record is created." /> | ||
<meta property="og:url" content="https://wiki.en.it-processmaps.com/index.php/Checklist_Problem_Record" /> | <meta property="og:url" content="https://wiki.en.it-processmaps.com/index.php/Checklist_Problem_Record" /> | ||
<meta property="og:title" content="Checklist Problem Record | IT Process Wiki" /> | <meta property="og:title" content="Checklist Problem Record | IT Process Wiki" /> | ||
<meta property="og:description" content="The | <meta property="og:description" content="The Problem Record contains all details of a Problem, documenting the history of the Problem from detection to closure." /> | ||
<meta property="og:site_name" content="IT Process Wiki - the ITIL® Wiki"> | <meta property="og:site_name" content="IT Process Wiki - the ITIL® Wiki"> | ||
<meta property="og:type" content="article" /> | <meta property="og:type" content="article" /> | ||
| Line 10: | Line 10: | ||
<meta property="fb:admins" content="100002035253209" /> | <meta property="fb:admins" content="100002035253209" /> | ||
<meta property="fb:admins" content="100002592864414" /> | <meta property="fb:admins" content="100002592864414" /> | ||
<meta property="og:image" content="https://wiki.en.it-processmaps.com/images/c/c2/Problem-record-itil.jpg" /> | |||
<meta property="og:image:width" content="1200" /> | |||
<meta property="og:image:height" content="600" /> | |||
<meta property="og:image" content="https://wiki.en.it-processmaps.com/images/7/77/Problem-record.jpg" /> | <meta property="og:image" content="https://wiki.en.it-processmaps.com/images/7/77/Problem-record.jpg" /> | ||
<meta property="og:image:width" content="620" /> | <meta property="og:image:width" content="620" /> | ||
<meta property="og:image:height" content="848" /> | <meta property="og:image:height" content="848" /> | ||
<meta name="twitter:card" content="summary_large_image"> | |||
<meta name="twitter:site" content="@itprocessmaps"> | |||
<meta name="twitter:creator" content="@itprocessmaps"> | |||
<meta name="twitter:title" content="Checklist Problem Record | IT Process Wiki"> | |||
<meta name="twitter:description" content="The Problem Record contains all details of a Problem, documenting the history of the Problem from detection to closure. - Free template."> | |||
<meta name="twitter:image" content="https://wiki.en.it-processmaps.com/images/c/c2/Problem-record-itil.jpg"> | |||
<meta name="twitter:image:alt" content="Problem Record - ITIL template: The 'Problem Record' contains all details of a Problem, documenting the history of the Problem from detection to closure. A 'Problem' is defined as a cause of one or more incidents; the cause is not usually known at the time a Problem Record is created."> | |||
<link href="https://plus.google.com/108613479011811316823/posts" rel="publisher" /> | <link href="https://plus.google.com/108613479011811316823/posts" rel="publisher" /> | ||
</itpmch> | </itpmch> | ||
| Line 41: | Line 51: | ||
==Problem Record - Contents== | ==Problem Record - Contents== | ||
[[image:Problem-record.jpg|link=https://wiki.en.it-processmaps.com/index.php/File:Problem-record.jpg|thumb| | [[image:Problem-record.jpg|link=https://wiki.en.it-processmaps.com/index.php/File:Problem-record.jpg|thumb|438px|right|alt=ITIL Problem Record|Fig. 1: [[media:Problem-record.jpg|ITIL Problem Record: Definition and information flow (view full size)]]]] | ||
''A Problem Record typically contains the following information:'' | ''A Problem Record typically contains the following information:'' | ||
| Line 150: | Line 160: | ||
<!-- This page is assigned to the following categories: --> | <!-- This page is assigned to the following categories: --> | ||
[[Category:Checklist (ITIL)|Problem Record]] | [[Category:Checklist (ITIL)|Problem Record]] | ||
[[Category:Template (ITIL)|Problem Record]] | |||
[[Category:Service Operation|Problem Record]] | [[Category:Service Operation|Problem Record]] | ||
[[Category:Problem Management|Problem Record]] | [[Category:Problem Management|Problem Record]] | ||
<!-- --- --> | <!-- --- --> | ||
Revision as of 12:28, 24 May 2020
Definition: The Problem Record contains all details of a Problem, documenting the history of the Problem from detection to closure. A 'Problem' is defined as a cause of one or more incidents; the cause is not usually known at the time a Problem Record is created.
ITIL Process: ITIL Service Operation - Problem Management
Checklist Category: ITIL Templates
Problem Record - Contents
A Problem Record typically contains the following information:
Unique ID
(Unique ID of the Problem - usually allocated automatically by the system)
Date and time of detection
Problem owner
Description of symptoms
Affected users/ business areas
Affected service(s)
Problem priority
Priority, a function of the following components:
- Urgency (available time until the resolution of the Problem)
- Impact (damage caused or potential damage to the business or IT infrastructure)
- Priority (for example expressed in codes like "Critical", "High", "Medium", "Low", "Very Low"): The result from the combination of urgency and impact
(Note: Prioritization of Problems should follow the same rules as the prioritization of Incidents; for further information, refer to the checklist Incident Prioritization Guideline)
Relationships to CIs
(Relationships to Configuration Items (CIs))
Problem category
Problem category, usually selected from a category-tree according to the following example:
- Hardware error
- Server A
- Component x
- Symptom a
- Symptom b
- Component y
- …
- Component x
- Server B
- …
- Server A
- Software error
- System A
- System B
- …
- Network error
- ...
(Note: Problem categories should be harmonized with Incident categories to support matching between Incidents and Problems)
(Links to related Problem Records - if there are other outstanding Problems related to this one)
(Links to related Incident Records - if outstanding Incidents exist, whose solution depends on the solution of this Problem)
(Links to Known Errors and Workarounds - if Known Errors and Workarounds related to the Problem have been identified)
Links to RFCs/ Change Records
(Links to RFCs/ Change Records associated with the solution of the Problem)
Problem status change history
- Date and time
- Person in charge
- Reason for status change
- New Problem status
Activity log
Activity log/ Tasks assigned to the Problem: Most service desk systems allow maintaining a simple log of steps carried out to resolve the Problem. Some systems, however, also provide the means to assign "Tasks" to Problems. Akin to the Problems they are assigned to, Tasks are typically characterized by properties like name, description, owner, priority, etc. and contain a status history and activity log of their own.
Notes
Is based on: Checklist 'Problem Record' from the ITIL Process Map
By: Stefan Kempter 
, IT Process Maps.
Definition › Problem Record: Contents › Priority › Category
