LP4.7: Resolve problems: Difference between revisions
No edit summary |
No edit summary |
||
Line 1: | Line 1: | ||
<itpmch><title>LP4.7: Resolve problems | YaSM Service Management Wiki</title> | <itpmch><title>LP4.7: Resolve problems | YaSM Service Management Wiki</title> | ||
<meta name="keywords" content="how to resolve problems, yasm problem resolution, yasm problem management, problem management process" /> | <meta name="keywords" content="how to resolve problems, yasm problem resolution, yasm problem management, problem management process" /> | ||
<meta name="description" content=" | <meta name="description" content="The problem management process in YaSM is about managing the lifecycle of all problems, where a problem is the underlying cause of one or several (potential) incidents." /> | ||
<meta property="og:url" content="https://yasm.com/wiki/en/index.php/LP4.7:_Resolve_problems" /> | <meta property="og:url" content="https://yasm.com/wiki/en/index.php/LP4.7:_Resolve_problems" /> | ||
<meta property="og:title" content="LP4.7: Resolve problems | YaSM Service Management Wiki" /> | <meta property="og:title" content="LP4.7: Resolve problems | YaSM Service Management Wiki" /> | ||
<meta property="og:description" content=" | <meta property="og:description" content="The problem management process in YaSM is about managing the lifecycle of all problems, where a problem is the underlying cause of one or several (potential) incidents." /> | ||
<meta property="og:site_name" content="YaSM"> | <meta property="og:site_name" content="YaSM"> | ||
<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://yasm.com/wiki/en/img/yasm-process-definition/what-is-problem-management-process.jpg" /> | |||
<meta property="og:image:width" content="1050" /> | |||
<meta property="og:image:height" content="525" /> | |||
<meta property="og:image" content="https://yasm.com/wiki/en/img/yasm-process/Resolve-problems-yasm-lp4-7.jpg" /> | <meta property="og:image" content="https://yasm.com/wiki/en/img/yasm-process/Resolve-problems-yasm-lp4-7.jpg" /> | ||
<meta property="og:image:width" content="633" /> | <meta property="og:image:width" content="633" /> | ||
Line 20: | Line 23: | ||
<meta name="twitter:creator" content="@yasmcom"> | <meta name="twitter:creator" content="@yasmcom"> | ||
<meta name="twitter:title" content="LP4.7: Resolve problems"> | <meta name="twitter:title" content="LP4.7: Resolve problems"> | ||
<meta name="twitter:description" content=" | <meta name="twitter:description" content="The problem management process in YaSM is about managing the lifecycle of all problems, where a problem is the underlying cause of one or several (potential) incidents."> | ||
<meta name="twitter:image" content="https://yasm.com/wiki/en/img/yasm-process/ | <meta name="twitter:image" content="https://yasm.com/wiki/en/img/yasm-process-definition/what-is-problem-management-process.jpg"> | ||
<meta name="twitter:image:alt" content=" | <meta name="twitter:image:alt" content="The problem management process in YaSM: Definition | To manage the lifecycle of all problems, where a problem is the underlying cause of one or several (potential) incidents. To prevent service incidents from happening, and to minimize the impact of incidents which cannot be prevented."> | ||
<link href="https://plus.google.com/104150539756444616711/posts" rel="publisher" /> | <link href="https://plus.google.com/104150539756444616711/posts" rel="publisher" /> | ||
</itpmch> | </itpmch> | ||
Line 35: | Line 38: | ||
==Process description== | ==Process description== | ||
<html><div itemid="https://yasm.com/wiki/en/img/yasm-process/Resolve-problems-yasm-lp4-7.jpg" itemscope itemtype="https://schema.org/ImageObject"> | <html><p><span id="md-itempage-description" itemprop="description">The problem management process in YaSM is about managing the lifecycle of all problems, where a problem is the underlying cause of one or several (potential) incidents. The primary objective of YaSM's problem resolution process is to prevent service incidents from happening, and to minimize the impact of incidents which cannot be prevented.</span></p> | ||
<div itemid="https://yasm.com/wiki/en/img/yasm-process/Resolve-problems-yasm-lp4-7.jpg" itemscope itemtype="https://schema.org/ImageObject"> | |||
<a href="https://yasm.com/wiki/en/img/yasm-process/Resolve-problems-yasm-lp4-7.jpg" title="Resolve problems. - YaSM process LP4.7" itemprop="contentUrl"> | <a href="https://yasm.com/wiki/en/img/yasm-process/Resolve-problems-yasm-lp4-7.jpg" title="Resolve problems. - YaSM process LP4.7" itemprop="contentUrl"> | ||
<meta itemprop="width" content="633" /> | <meta itemprop="width" content="633" /> | ||
Line 43: | Line 48: | ||
<meta itemprop="keywords" content="Problem management" /> | <meta itemprop="keywords" content="Problem management" /> | ||
<img style="margin:20px 0px 10px 0px; float:left;" src="https://yasm.com/wiki/en/img/yasm-process/Resolve-problems-yasm-lp4-7.jpg" width="633" height="381" title="Resolve problems. - YaSM process LP4.7" alt="Fig. 1: Resolve problems. - YaSM problem resolution process LP4.7" /></a><br style="clear:both;"/> | <img style="margin:20px 0px 10px 0px; float:left;" src="https://yasm.com/wiki/en/img/yasm-process/Resolve-problems-yasm-lp4-7.jpg" width="633" height="381" title="Resolve problems. - YaSM process LP4.7" alt="Fig. 1: Resolve problems. - YaSM problem resolution process LP4.7" /></a><br style="clear:both;"/> | ||
<div class="thumbcaption"><span style="font-variant:small-caps;"><b>Figure 1:</b></span> <small><span itemprop="caption">'Resolve problems'. - YaSM service lifecycle process LP4.7.</span></small></div></div><br style="clear:both;"/> | <div class="thumbcaption"><span style="font-variant:small-caps;"><b>Figure 1:</b></span> <small><span itemprop="caption">'Resolve problems'. - YaSM service lifecycle process LP4.7.</span></small></div></div><br style="clear:both;"/><p></html> | ||
<p | |||
<p> </p> | <p> </p> | ||
Line 51: | Line 54: | ||
==Sub-processes== | ==Sub-processes== | ||
<html>YaSM's problem management process | <html>YaSM's problem management process has the following sub-processes:</p> | ||
<p> </p> | <p> </p> | ||
Line 94: | Line 97: | ||
<meta itemprop="alternateName" content="Problem resolution process outputs" /> | <meta itemprop="alternateName" content="Problem resolution process outputs" /> | ||
<meta itemprop="alternateName" content="Problem resolution data objects" /> | <meta itemprop="alternateName" content="Problem resolution data objects" /> | ||
<p><span itemprop="description">This section lists the documents and records produced by | <p><span itemprop="description">This section lists the documents and records produced by the problem resolution process.</span> YaSM data objects <a href="#ydo" title="YaSM data object">[*]</a> are marked with an asterisk, while other objects are displayed in gray.</p> | ||
<p> </p> | <p> </p> | ||
Line 122: | Line 125: | ||
<hr /> | <hr /> | ||
<p><i><b>Notes:</b></i> | <p><i><b>Notes:</b></i> | ||
</p><p><span id="ydo"><strong>[*]</strong> <i>"YaSM data objects"</i> are those documents or records for which the YaSM model provides detailed recommendations: Every YaSM object has an associated checklist (see <a | </p><p><span id="ydo"><strong>[*]</strong> <i>"YaSM data objects"</i> are those documents or records for which the YaSM model provides detailed recommendations: Every YaSM object has an associated checklist (see <a href="https://yasm.com/wiki/en/index.php/Service_Management_Checklists" title="Example: YaSM checklists and document templates">example</a>) describing its typical contents, and an associated lifecycle diagram depicting how the status of the object changes as it is created, updated, read and archived by various YaSM processes (see <a href="https://yasm.com/wiki/en/img/yasm-project/Yasm-object-lifecycle-diagram.jpg" title="Example: YaSM object lifecycle diagram (.JPG)">example</a>).</span> | ||
</p><p><i>"Other objects"</i> are mostly informal data or information where YaSM has less strong views about their contents. There are no associated lifecycle diagrams or checklists.</html> | </p><p><i>"Other objects"</i> are mostly informal data or information where YaSM has less strong views about their contents. There are no associated lifecycle diagrams or checklists.</html> | ||
Line 185: | Line 188: | ||
== Notes == | == Notes == | ||
<html>< | <html><div itemid="https://yasm.com/wiki/en/img/yasm-process-definition/what-is-problem-management-process.jpg" itemscope itemtype="https://schema.org/ImageObject"> | ||
<a href="https://yasm.com/wiki/en/img/yasm-process-definition/what-is-problem-management-process.jpg" title="Problem management: process definition (.pdf)" itemprop="contentUrl"> | |||
<img style="display: block; float: left; margin-right: 20px" src="https://yasm.com/wiki/en/img/yasm-process-definition/what-is-problem-management-process.jpg" width="320" height="160" title="Problem management: process definition" alt="What is problem management? Definition of the problem resolution process LP4.7 from the YaSM framework." /> | |||
<meta itemprop="caption" content="Definition: problem management" /> | |||
<meta itemprop="width" content="1050" /> | |||
<meta itemprop="height" content="525" /></a></div> | |||
<div style="margin-left: 30%; color:#636363"> | <div style="margin-left: 30%; color:#636363"> | ||
<p style="margin-top: 0;">Is based on: The problem resolution process from the <a href="https://yasm.com/en/products/yasm-process-map" title="YaSM Process Map">YaSM Process Map</a>.</p> | <p style="margin-top: 0;">Is based on: The problem resolution process from the <a href="https://yasm.com/en/products/yasm-process-map" title="YaSM Process Map">YaSM Process Map</a>.</p> | ||
Line 195: | Line 203: | ||
==Related blog posts== | ==Related blog posts== | ||
<html><a href="https://yasm.com/en/blog/service-operation-yasm"><img src="https://yasm.com/en/content/blog/150729-service-operation-yasm/img- | <html><a href="https://yasm.com/en/blog/service-operation-yasm"><img src="https://yasm.com/en/content/blog/150729-service-operation-yasm/img-main.jpg" title="From the YaSM Blog: Service operation according to YaSM" alt="Operational processes, and in particular incident management and problem management, are probably the most widely known (and used) parts of ITSM best practice." style="display: block; float: left; margin-right: 20px" width="320" height="138"/></a> | ||
<div style="margin-left: 30%; color:#636363"> | <div style="margin-left: 30%; color:#636363"> | ||
<p style="margin-top: 0;"><a href="https://yasm.com/en/blog/service-operation-yasm">Service operation according to YaSM</a></p> | <p style="margin-top: 0;"><a href="https://yasm.com/en/blog/service-operation-yasm" title="From the YaSM Blog: Service operation according to YaSM">Service operation according to YaSM</a></p> | ||
<p><small>by: Stefan Kempter</small></p> | <p><small>by: Stefan Kempter</small></p> | ||
<p>Operational processes, and in particular incident management and problem management, are probably the most widely known (and used) parts of IT service management best practice. <a href="https://yasm.com/en/blog/service-operation-yasm">[...]</a></p></div><p> | <p>Operational processes, and in particular incident management and problem management, are probably the most widely known (and used) parts of IT service management best practice. <a href="https://yasm.com/en/blog/service-operation-yasm">[...]</a></p></div><p> | ||
<p> </p> | |||
<p> </p> | <p> </p> | ||
Line 233: | Line 242: | ||
<meta itemprop="alternativeHeadline" content="YaSM problem management process" /> | <meta itemprop="alternativeHeadline" content="YaSM problem management process" /> | ||
<link itemprop="primaryImageOfPage" href="https://yasm.com/wiki/en/img/yasm-process/Resolve-problems-yasm-lp4-7.jpg" /> | <link itemprop="primaryImageOfPage" href="https://yasm.com/wiki/en/img/yasm-process/Resolve-problems-yasm-lp4-7.jpg" /> | ||
<meta itemprop="significantLinks" content="https://yasm.com/wiki/en/index.php/YaSM_Metrics" /> | |||
<meta itemprop="significantLinks" content="https://yasm.com/wiki/en/index.php/YaSM_Metrics/_Service_Lifecycle_Processes#metrics-lp4.7" /> | |||
</div> | </div> | ||
<!-- define schema.org/CreativeWork --> | <!-- define schema.org/CreativeWork --> | ||
<div itemscope itemtype="https://schema.org/CreativeWork" itemref="md-type-subProcess"> | |||
<link id="md-type-process" itemprop="additionalType" href="http://www.productontology.org/id/Business_process" /> | <link id="md-type-process" itemprop="additionalType" href="http://www.productontology.org/id/Business_process" /> | ||
<meta itemscope itemprop="mainEntityOfPage" itemType="https://schema.org/ItemPage" | |||
itemid="https://yasm.com/wiki/en/index.php/LP4.7:_Resolve_problems" itemref="md-itempage-description"> | itemid="https://yasm.com/wiki/en/index.php/LP4.7:_Resolve_problems" itemref="md-itempage-description"> | ||
<meta itemprop="name" content="LP4.7: Resolve problems" /> | |||
<meta itemprop="alternateName" content="YaSM problem management process" /> | |||
<link itemprop="url" href="https://yasm.com/wiki/en/index.php/LP4.7:_Resolve_problems" /> | |||
<link itemprop="hasPart" href="https://yasm.com/wiki/en/index.php/LP4.7:_Resolve_problems#LP4.7.1"> | |||
<link itemprop="hasPart" href="https://yasm.com/wiki/en/index.php/LP4.7:_Resolve_problems#LP4.7.2"> | |||
<link itemprop="hasPart" href="https://yasm.com/wiki/en/index.php/LP4.7:_Resolve_problems#LP4.7.3"> | |||
<link itemprop="hasPart" href="https://yasm.com/wiki/en/index.php/LP4.7:_Resolve_problems#LP4.7.4"> | |||
<link itemprop="hasPart" href="https://yasm.com/wiki/en/index.php/LP4.7:_Resolve_problems#LP4.7.5"> | |||
<link itemprop="hasPart" href="https://yasm.com/wiki/en/index.php/LP4.7:_Resolve_problems#Process_outputs"> | |||
<link itemprop="image" href="https://yasm.com/wiki/en/img/yasm-process/Resolve-problems-yasm-lp4-7.jpg" /> | |||
<link itemprop="image" href="https://yasm.com/wiki/en/img/yasm-process-definition/what-is-problem-management-process.jpg" /> | |||
<link itemprop="isPartOf" href="https://yasm.com/wiki/en/index.php/LP4:_Operate_the_services" /> | |||
<meta itemprop="isBasedOnUrl" content="https://yasm.com/en/products/yasm-process-map" /> | |||
<meta itemprop="inLanguage" content="en" /> | |||
<link itemprop="citation" href="https://yasm.com/wiki/de/index.php/LP4.7:_L%C3%B6sen_von_Problemen" /> | |||
<link itemprop="publisher" href="https://yasm.com/en/#YaSMBrand" /> | |||
<link itemprop="copyrightHolder creator" href="https://yasm.com/en/contact#ITProcessMapsOrg" /> | |||
<link itemprop="author" href="https://yasm.com/en/misc/team#StefanKempter" /> | |||
<link itemprop="contributor" href="https://yasm.com/en/misc/team#AndreaKempter" /> | |||
</div><p></html> | </div><p></html> | ||
Revision as of 16:50, 16 September 2017

Process name: Resolve problems - Part of: Service lifecycle processes - Operate the services
Previous process: Resolve incidents and service requests
Process description
The problem management process in YaSM is about managing the lifecycle of all problems, where a problem is the underlying cause of one or several (potential) incidents. The primary objective of YaSM's problem resolution process is to prevent service incidents from happening, and to minimize the impact of incidents which cannot be prevented.
Sub-processes
YaSM's problem management process has the following sub-processes:
- LP4.7.1: Pro-actively identify problems
- Process objective: To improve overall availability of services by proactively identifying problems. This process aims to identify and solve problems and/ or provide suitable workarounds before (further) service incidents occur.
- LP4.7.2: Categorize and prioritize problems
- Process objective: To record and prioritize the problems with appropriate diligence, in order to facilitate a swift and effective resolution.
- LP4.7.3: Analyze and resolve problems
- Process objective: To identify the underlying causes of problems and to determine the most appropriate and economical problem solution. If possible, a temporary workaround should be supplied while no full solution is available.
- LP4.7.4: Monitor outstanding problems
- Process objective: To constantly monitor outstanding problems with regards to their processing status, and to take corrective action as required.
- LP4.7.5: Close problems
- Process objective: To ensure that the problem resolution has been successful and all related information is up-to-date.
Process outputs
This section lists the documents and records produced by the problem resolution process. YaSM data objects [*] are marked with an asterisk, while other objects are displayed in gray.
- Incident model
- An incident model contains the pre-defined steps that should be taken for dealing with a particular type of incident. The aim of providing incident models is to ensure that recurring incidents are handled efficiently and effectively. [*]
- Problem record
- A set of data with all details of a problem, documenting the history of the problem from registration to closure. A problem is defined as the underlying cause of one or more (potential) incidents, although the cause may not be known at the time a problem record is created. Often, a workaround is provided for a problem while a full resolution is not yet available. [*]
- Recovery plan
- Recovery plans contain detailed instructions for returning specific services and/ or systems to a working state, which often includes recovering data to a defined consistent state. [*]
- Service operation manual
- A service operation manual specifies the activities required for the operation of a service and its underlying infrastructure. The information in the service operation manual is meant to describe the day-to-day tasks in a way that is useful for operational staff. Some instructions related to the operation of particular applications, systems or other infrastructure components may be documented in separate technical manuals or 'standard operating procedures (SOPs)'. [*]
- Suggested process modification
- A suggestion for modifying one or several service management processes. Suggestions for process modifications or improvements may originate from anywhere within the organization.
- Suggested service modification
- A suggestion for modifying a service, for example to improve service quality or economics. Suggestions may originate from anywhere within or outside of the service provider organization.
- Support request
- A request to support the resolution of an incident or problem, usually issued from the incident or problem manager when further assistance is needed from technical experts or external suppliers.
Notes:
[*] "YaSM data objects" are those documents or records for which the YaSM model provides detailed recommendations: Every YaSM object has an associated checklist (see example) describing its typical contents, and an associated lifecycle diagram depicting how the status of the object changes as it is created, updated, read and archived by various YaSM processes (see example).
"Other objects" are mostly informal data or information where YaSM has less strong views about their contents. There are no associated lifecycle diagrams or checklists.
Process metrics
Process metrics are used, for example, to assess if the service management processes are running according to expectations.
For suggestions of suitable metrics, please refer to the list of metrics for the problem resolution process.
Roles and responsibilities
Process owner: Problem manager
- The problem manager is responsible for managing the lifecycle of all problems, where the primary objective is to prevent incidents from happening if possible, and to minimize the impact of incidents that cannot be prevented. Apart from resolving the underlying causes of (potential) incidents, the problem manager often provides workarounds while a full solution is not yet available.
YaSM role / sub-process | Problem manager | Service owner | Technical domain expert | |
---|---|---|---|---|
LP4.7.1 | Pro-actively identify problems | AR | - | - |
LP4.7.2 | Categorize and prioritize problems | AR | - | - |
LP4.7.3 | Analyze and resolve problems | AR | R | R |
LP4.7.4 | Monitor outstanding problems | AR | - | - |
LP4.7.5 | Close problems | AR | - | - |
Notes
Is based on: The problem resolution process from the YaSM Process Map.
Related blog posts
Service operation according to YaSM
by: Stefan Kempter
Operational processes, and in particular incident management and problem management, are probably the most widely known (and used) parts of IT service management best practice. [...]
Process description › Sub-processes › Process outputs › Metrics › Roles