View source for LP4.6: Resolve incidents and service requests

<itpmch><title>LP4.6: Resolve incidents and service requests | YaSM Service Management Wiki</title>
<meta name="keywords" content="how to resolve incidents, how to resolve service requests, yasm incident management, incident management process" />
<meta name="description" content="The incident management process in YaSM is responsible for resolving service incidents (reports of suspected or actual service failures) or requests for service. In the case of service incidents, the primary objective of this process is to return the service to users as quickly as possible." />
<meta property="og:url" content="https://yasm.com/wiki/en/index.php/LP4.6:_Resolve_incidents_and_service_requests" />
<meta property="og:title" content="LP4.6: Resolve incidents and service requests | YaSM Service Management Wiki" />
<meta property="og:description" content="The incident management process in YaSM is responsible for resolving service incidents (reports of suspected or actual service failures) or requests for service. In the case of service incidents, the primary objective of this process is to return the service to users as quickly as possible." />
<meta property="og:site_name" content="YaSM Service Management">
<meta property="og:type" content="article" />
<meta property="og:image" content="https://yasm.com/wiki/en/img/yasm-process/16x9/Resolve-incidents-and-service-requests-yasm-lp4-6.jpg" />
<meta property="og:image:width" content="1200" />
<meta property="og:image:height" content="675" />
<link href="https://plus.google.com/104150539756444616711/posts" rel="publisher" />
</itpmch>
<html><div class="noresize"><a href="https://yasm.com/wiki/de/index.php/LP4.6:_L%C3%B6sen_von_Incidents_und_Service_Requests"><img src="https://yasm.com/wiki/en/img/yasm-wiki/YaSM-Wiki-Deutsch.png" width="140" height="36" style="float:right;" alt="auf Deutsch" title="This page in German" /></a></div><br style="clear:both;"/>
<p>&nbsp;</p>

<p><b>Process name:</b> <a href="#Process_description">Resolve incidents and service requests</a> - <b>Part of:</b> <a href="/wiki/en/index.php/Service_Management_Processes#Service_lifecycle_processes" title="The service lifecycle processes in YaSM service management">Service lifecycle processes</a> - <a href="/wiki/en/index.php/LP4:_Operate_the_services" title="LP4: Operate the services">Operate the services</a>
</p><p><b>Next process:</b> <a href="/wiki/en/index.php/LP4.7:_Resolve_problems" title="LP4.7: Resolve problems">Resolve problems</a></html>
<p>&nbsp;</p>

==Process description==

<html><span id="md-itempage-description" itemprop="description">The incident management process in YaSM (<a href="https://yasm.com/wiki/en/img/yasm-process/Resolve-incidents-and-service-requests-yasm-lp4-6.jpg" title="YaSM incident management (LP4.6)">fig. 1</a>) is responsible for resolving service incidents (reports of suspected or actual service failures) or requests for service. In the case of service incidents, the primary objective of this process is to return the service to users as quickly as possible. In some cases this involves applying a workaround if the root cause cannot be readily identified and/ or resolved.</span></p>

<div style="float:left;">
<div itemid="https://yasm.com/wiki/en/img/yasm-process/Resolve-incidents-and-service-requests-yasm-lp4-6.jpg" itemscope itemtype="https://schema.org/ImageObject">
<a href="https://yasm.com/wiki/en/img/yasm-process/Resolve-incidents-and-service-requests-yasm-lp4-6.jpg" title="Resolve incidents and service requests. - YaSM incident management process LP4.6" itemprop="contentUrl">
<meta itemprop="width" content="1200" />
<meta itemprop="height" content="900" />
<meta itemprop="keywords" content="yasm incident resolution process" />
<meta itemprop="keywords" content="incident management" />
<meta itemprop="keywords" content="request fulfilment" />
<meta itemprop="keywords" content="ITIL 4 incident management" />
<meta itemprop="keywords" content="ITIL 4 service request management" />
<meta itemprop="representativeOfPage" content="true"/>
<meta itemprop="dateCreated" content="2014-05-02" />
<meta itemprop="datePublished" content="2014-05-08" />
<meta itemprop="dateModified" content="2019-11-02" />
<span itemprop="thumbnail" itemscope itemtype="https://schema.org/ImageObject">
  <meta itemprop="url" content="https://yasm.com/wiki/en/img/yasm-process/16x9/Resolve-incidents-and-service-requests-yasm-lp4-6.jpg" />
  <meta itemprop="width" content="1200" />
  <meta itemprop="height" content="675" />
  <meta itemprop="dateCreated" content="2020-06-13" />
  <meta itemprop="datePublished" content="2020-06-14" />
</span>
<img style="margin:20px 0px 10px 0px; float:left;" src="https://yasm.com/wiki/en/img/yasm-process/Resolve-incidents-and-service-requests-yasm-lp4-6.jpg" width="800" height="600" title="Resolve incidents and service requests. - YaSM incident management process LP4.6" alt="Fig. 1: Resolve incidents and service requests. - YaSM incident management process LP4.6. - Related with: Practice of ITIL 4 incident management and ITIL 4 service request management." /></a><br style="clear:both;"/>
<div class="thumbcaption" style="margin:15px 0px 20px 0px"><span itemprop="caption"><span style="font-variant:small-caps;"><b>Fig. 1: '<a href="https://yasm.com/wiki/en/img/yasm-process/Resolve-incidents-and-service-requests-yasm-lp4-6.jpg" title="YaSM incident management LP4.6">Resolve incidents and service requests</a>'</b>:</span><br />YaSM incident management and service request management process LP4.6.</span></div></div></div><br style="clear:both;"/>

<p><i><u>Compatibility</u>: YaSM incident management is <a href="/wiki/en/index.php/YaSM_and_ISO_20000#ISO_20000_requirements_and_related_service_management_processes" title="YaSM und ISO 20000">aligned with ISO 20000</a>, the international standard for service management (see ISO/IEC 20000-1:2018, <a href="/wiki/en/index.php/YaSM_and_ISO_20000#Resolution-and-fulfilment" title="ISO 20000 section 8.6: Resolution and fulfilment">section 8.6</a>), and it corresponds to the ITIL practices of '<a href="/wiki/en/index.php/YaSM_and_ITIL#ITIL-4-Incident-management" title="ITIL 4 practices and YaSM processes: ITIL 4 incident management">ITIL 4 incident management</a>', '<a href="/wiki/en/index.php/YaSM_and_ITIL#ITIL-4-Service-desk" title="ITIL 4 practices and YaSM processes: ITIL 4 service desk">service desk</a>' and '<a href="/wiki/en/index.php/YaSM_and_ITIL#ITIL-4-Service-request-management" title="ITIL 4 practices and YaSM processes: ITIL 4 service request management">ITIL 4 service request management</a>'.</i></html>

==Sub-processes==

<html>YaSM's incident management process has the following sub-processes:</p>

<!-- define schema.org/CreativeWork -->
 <link id="md-type-subProcess" itemprop="additionalType" href="http://www.productontology.org/id/Procedure_(business)" />
<div itemid="https://yasm.com/wiki/en/index.php/LP4.6:_Resolve_incidents_and_service_requests#LP4.6.1" itemscope itemtype="https://schema.org/CreativeWork" itemref="md-type-subProcess">
<meta itemprop="alternateName" content="YaSM incident resolution process LP4.6.1" />
<dl id="LP4.6.1"><dt itemprop="name">LP4.6.1: Support incident and service request resolution</dt>
<dd itemprop="description">Process objective: To provide support for the resolution of incidents and service requests, for example by configuring the systems to manage incidents and service requests, and by maintaining a set of incident and service request models.</dd></dl>
</div>
<div itemid="https://yasm.com/wiki/en/index.php/LP4.6:_Resolve_incidents_and_service_requests#LP4.6.2" itemscope itemtype="https://schema.org/CreativeWork" itemref="md-type-subProcess">
<meta itemprop="alternateName" content="YaSM incident resolution process LP4.6.2" />
<dl id="LP4.6.2"><dt itemprop="name">LP4.6.2: Log incidents and service requests</dt>
<dd itemprop="description">Process objective: To record all relevant details of incidents and service requests, to verify that all required authorizations are given, and to prioritize the incidents or requests.</dd></dl>
</div>
<div itemid="https://yasm.com/wiki/en/index.php/LP4.6:_Resolve_incidents_and_service_requests#LP4.6.3" itemscope itemtype="https://schema.org/CreativeWork" itemref="md-type-subProcess">
<meta itemprop="alternateName" content="YaSM incident resolution process LP4.6.3" />
<dl id="LP4.6.3"><dt itemprop="name">LP4.6.3: Fulfill service requests</dt>
<dd itemprop="description">Process objective: To fulfill service requests, which are typically either requests for information or requests to implement minor (standard) changes like the reset of a password.</dd></dl>
</div>
<div itemid="https://yasm.com/wiki/en/index.php/LP4.6:_Resolve_incidents_and_service_requests#LP4.6.4" itemscope itemtype="https://schema.org/CreativeWork" itemref="md-type-subProcess">
<meta itemprop="alternateName" content="YaSM incident resolution process LP4.6.4" />
<dl id="LP4.6.4"><dt itemprop="name">LP4.6.4: Pro-actively inform users and clients</dt>
<dd itemprop="description">Process objective: To inform users of actual or imminent service failures as soon as these become known to 1st level support, so that users and clients are in a position to adjust themselves to interruptions. This process is also responsible for distributing other important information, like current security alerts.</dd></dl>
</div>
<div itemid="https://yasm.com/wiki/en/index.php/LP4.6:_Resolve_incidents_and_service_requests#LP4.6.5" itemscope itemtype="https://schema.org/CreativeWork" itemref="md-type-subProcess">
<meta itemprop="alternateName" content="YaSM incident resolution process LP4.6.5" />
<dl id="LP4.6.5"><dt itemprop="name">LP4.6.5: Resolve major incidents</dt>
<dd itemprop="description">Process objective: To resolve a major incident. Major incidents cause serious interruptions of business activities and must be resolved with greater urgency. The aim is the fast recovery of the service, possibly by means of a workaround.</dd></dl>
</div>
<div itemid="https://yasm.com/wiki/en/index.php/LP4.6:_Resolve_incidents_and_service_requests#LP4.6.6" itemscope itemtype="https://schema.org/CreativeWork" itemref="md-type-subProcess">
<meta itemprop="alternateName" content="YaSM incident resolution process LP4.6.6" />
<dl id="LP4.6.6"><dt itemprop="name">LP4.6.6: Resolve incidents in 1st level support</dt>
<dd itemprop="description">Process objective: To resolve an incident (service interruption) within the agreed time frame. The aim is the fast recovery of the service, possibly by applying a workaround. As soon as it becomes clear that 1st level support is not able to resolve the incident itself or when target times for 1st level resolution are exceeded, the incident is transferred to 2nd level support.</dd></dl>
</div>
<div itemid="https://yasm.com/wiki/en/index.php/LP4.6:_Resolve_incidents_and_service_requests#LP4.6.7" itemscope itemtype="https://schema.org/CreativeWork" itemref="md-type-subProcess">
<meta itemprop="alternateName" content="YaSM incident resolution process LP4.6.7" />
<dl id="LP4.6.7"><dt itemprop="name">LP4.6.7: Resolve incidents in 2nd level support</dt>
<dd itemprop="description">Process objective: To resolve an Incident (service interruption) within the agreed time frame. The aim is the fast recovery of the service, possibly by means of a workaround. If required, specialist support groups or third-party suppliers (3rd level support) may be involved.</dd></dl>
</div>
<div itemid="https://yasm.com/wiki/en/index.php/LP4.6:_Resolve_incidents_and_service_requests#LP4.6.8" itemscope itemtype="https://schema.org/CreativeWork" itemref="md-type-subProcess">
<meta itemprop="alternateName" content="YaSM incident resolution process LP4.6.8" />
<dl id="LP4.6.8"><dt itemprop="name">LP4.6.8: Monitor incidents and service requests</dt>
<dd itemprop="description">Process objective: To continuously monitor the processing status of outstanding incidents and service requests, so that escalations and counter-measures can be introduced if the agreed resolution times are likely to be breached.</dd></dl>
</div>
<div itemid="https://yasm.com/wiki/en/index.php/LP4.6:_Resolve_incidents_and_service_requests#LP4.6.9" itemscope itemtype="https://schema.org/CreativeWork" itemref="md-type-subProcess">
<meta itemprop="alternateName" content="YaSM incident resolution process LP4.6.9" />
<dl id="LP4.6.9"><dt itemprop="name">LP4.6.9: Close incidents and service requests</dt>
<dd itemprop="description">Process objective: To submit the incident and service request records to a final quality control before formal closure. The aim is to make sure that the incident's or service request's resolution history is described in sufficient detail. In addition, findings from the resolution of the incidents are to be recorded for future use.</dd></dl>
</div><!-- end of schema.org/CreativeWork --><p></html>

==Process outputs==

<html><!-- define schema.org/DefinedTermSet -->
<div itemid="https://yasm.com/wiki/en/index.php/LP4.6:_Resolve_incidents_and_service_requests#process-inputs-outputs" itemscope="itemscope" itemtype="https://schema.org/DefinedTermSet">
<link itemprop="additionalType" href="http://www.productontology.org/id/Input/output" />
<meta itemprop="name" content="YaSM process LP4.6: documents and records" />
<meta itemprop="alternateName" content="Incident resolution process outputs" />
<meta itemprop="alternateName" content="Incident resolution data objects" />
<p><span itemprop="name">This section lists the documents and records produced by the incident 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>

<dl>
<div itemprop="hasDefinedTerm" itemscope itemtype="https://schema.org/DefinedTerm">
<dt itemprop="name">Change record</dt>
<dd itemprop="description" style="margin-bottom: 1em;">A change record contains all details of a change, documenting the lifecycle of a single change. In its initial state, a change record describes a request for change (RFC) which is to be assessed and authorized prior to implementing the change. Further information is added as the change progresses through its lifecycle. <a href="#ydo" title="YaSM data object">[*]</a></dd></div>
<div style="color:#636363" itemprop="hasDefinedTerm" itemscope itemtype="https://schema.org/DefinedTerm">
<dt itemprop="name">Change status information</dt>
<dd itemprop="description" style="margin-bottom: 1em;">Current status information related to the implementation of a change. This information is sent to the change manager from the various processes that implement authorized changes. It is used by the change manager to keep the change records and the change schedule up-to-date.</dd></div>
<div itemprop="hasDefinedTerm" itemscope itemtype="https://schema.org/DefinedTerm">
<dt itemprop="name">CI record</dt>
<dd itemprop="description" style="margin-bottom: 1em;">Configuration information is maintained in CI records for all configuration items (CIs) under the control of the configuration manager. In this context, CIs can be of various types: Applications, systems and other infrastructure components are treated as CIs, but often also services, policies, project documentation, employees, suppliers, etc. Configuration information is stored in the configuration management system (CMS). <a href="#ydo" title="YaSM data object">[*]</a></dd></div>
<div itemprop="hasDefinedTerm" itemscope itemtype="https://schema.org/DefinedTerm">
<dt itemprop="name">Complaint record</dt>
<dd itemprop="description" style="margin-bottom: 1em;">A record containing the details of a customer complaint, including the actions taken to resolve the complaint. <a href="#ydo" title="YaSM data object">[*]</a></dd></div>
<div itemprop="hasDefinedTerm" itemscope itemtype="https://schema.org/DefinedTerm">
<dt itemprop="name">Customer survey questionnaire</dt>
<dd itemprop="description" style="margin-bottom: 1em;">A customer survey is typically based on questionnaires, aimed at getting insight into overall customer satisfaction and customers' views on specific (aspects of) services. In many cases, answers are given using a scale, for example '1: Very dissatisfied', ... , '10: Very satisfied'. <a href="#ydo" title="YaSM data object">[*]</a></dd></div>
<div itemprop="hasDefinedTerm" itemscope itemtype="https://schema.org/DefinedTerm">
<dt itemprop="name" id="Incident-model">Incident model</dt>
<dd itemprop="description" style="margin-bottom: 1em;">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. <a href="#ydo" title="YaSM data object">[*]</a></dd></div>
<div itemprop="hasDefinedTerm" itemscope itemtype="https://schema.org/DefinedTerm">
<dt itemprop="name" id="Incident-record">Incident record</dt>
<dd itemprop="description" style="margin-bottom: 1em;">A set of data with all details of a service incident, documenting the history of the incident from registration to closure. A service incident is defined as an unplanned interruption or reduction in quality of a service. Events that could potentially impair a service in the future are also treated as incidents (e.g. the failure of one hard-drive of a set of mirrored drives). See also: <a href="https://yasm.com/wiki/en/index.php/Incident_Record_-_Template" title="Incident record document template">Incident record checklist</a>. <a href="#ydo" title="YaSM data object">[*]</a></dd></div>
<div style="color:#636363" itemprop="hasDefinedTerm" itemscope itemtype="https://schema.org/DefinedTerm">
<dt itemprop="name" id="Incident-request-status-information">Incident/ request status information</dt>
<dd itemprop="description" style="margin-bottom: 1em;">A message containing the present status of an incident or service request sent to a user who earlier reported a service interruption or submitted a service request. Status information is typically provided to users at various points during an incident's or request's lifecycle. If the resolution time exceeds or is expected to exceed the agreed time frames, status notifications are especially important to keep the user informed.</dd></div>
<div style="color:#636363" itemprop="hasDefinedTerm" itemscope itemtype="https://schema.org/DefinedTerm">
<dt itemprop="name">Pro-active user information</dt>
<dd itemprop="description" style="margin-bottom: 1em;">A notification to users or clients of existing or potential service failures, so that users are in a position to prepare themselves for a period of service unavailability.</dd></div>
<div itemprop="hasDefinedTerm" itemscope itemtype="https://schema.org/DefinedTerm">
<dt itemprop="name">Problem record</dt>
<dd itemprop="description" style="margin-bottom: 1em;">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. See also: <a href="https://yasm.com/wiki/en/index.php/Problem_Record_-_Template" title="Problem record document template">Problem record checklist</a>. <a href="#ydo" title="YaSM data object">[*]</a></dd></div>
<div itemprop="hasDefinedTerm" itemscope itemtype="https://schema.org/DefinedTerm">
<dt itemprop="name">Recovery plan</dt>
<dd itemprop="description" style="margin-bottom: 1em;">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. <a href="#ydo" title="YaSM data object">[*]</a></dd></div>
<div style="color:#636363" itemprop="hasDefinedTerm" itemscope itemtype="https://schema.org/DefinedTerm">
<dt itemprop="name">Self-help information for users</dt>
<dd itemprop="description" style="margin-bottom: 1em;">Self-help information for users supplied by the service provider, for example as part of the support pages on the intranet.</dd></div>
<div itemprop="hasDefinedTerm" itemscope itemtype="https://schema.org/DefinedTerm">
<dt itemprop="name" id="Service-request-model">Service request model</dt>
<dd itemprop="description" style="margin-bottom: 1em;">Service request models contain the pre-defined steps that should be taken for dealing with a particular type of service request. The aim of providing service request models is to ensure that routinely occurring requests are handled efficiently and effectively. <a href="#ydo" title="YaSM data object">[*]</a></dd></div>
<div itemprop="hasDefinedTerm" itemscope itemtype="https://schema.org/DefinedTerm">
<dt itemprop="name" id="Service-request-record">Service request record</dt>
<dd itemprop="description" style="margin-bottom: 1em;">A record containing all details of a service request. Service requests are formal requests from a client or user for something to be provided within the framework of existing service agreements - for example, a request for information or advice; to reset a password; or to install a workstation for a new user. <a href="#ydo" title="YaSM data object">[*]</a></dd></div>
<div style="color:#636363" itemprop="hasDefinedTerm" itemscope itemtype="https://schema.org/DefinedTerm">
<dt itemprop="name">Service usage statistics</dt>
<dd itemprop="description" style="margin-bottom: 1em;">Statistical data on service usage by clients/ users, as a basis for producing client invoices.</dd></div>
<div style="color:#636363" itemprop="hasDefinedTerm" itemscope itemtype="https://schema.org/DefinedTerm">
<dt itemprop="name">Suggested changes to self-help information</dt>
<dd itemprop="description" style="margin-bottom: 1em;">A suggestion to update self-help information for users supplied by the service provider, for example as part of the support pages on the intranet.</dd></div>
<div itemprop="hasDefinedTerm" itemscope itemtype="https://schema.org/DefinedTerm">
<dt itemprop="name">Suggested improvement to continuity arrangements</dt>
<dd itemprop="description" style="margin-bottom: 1em;">A suggestion for improving service security. Suggestions for security improvements may originate from anywhere within the organization. <a href="#ydo" title="YaSM data object">[*]</a></dd></div>
<div style="color:#636363" itemprop="hasDefinedTerm" itemscope itemtype="https://schema.org/DefinedTerm">
<dt itemprop="name">Suggested process modification</dt>
<dd itemprop="description" style="margin-bottom: 1em;">A suggestion for modifying one or several service management processes. Suggestions for process modifications or improvements may originate from anywhere within the organization.</dd></div>
<div style="color:#636363" itemprop="hasDefinedTerm" itemscope itemtype="https://schema.org/DefinedTerm">
<dt itemprop="name">Suggested service modification</dt>
<dd itemprop="description" style="margin-bottom: 1em;">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.</dd></div>
<div style="color:#636363" itemprop="hasDefinedTerm" itemscope itemtype="https://schema.org/DefinedTerm">
<dt itemprop="name">Support request</dt>
<dd itemprop="description" style="margin-bottom: 1em;">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.</dd></div>
</dl>
</div><!-- end of schema.org/DefinedTermSet --><p>

<p>&nbsp;</p>
<hr />
<p><i><u>Notes</u>:</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 href="https://yasm.com/wiki/en/index.php/Incident_Record_-_Template" title="Incident record document template">"Incident record" template</a> and <a href="https://yasm.com/wiki/en/index.php/Service_Management_Checklists#yasm-template-example" title="Examples: YaSM checklists and document templates">more examples</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>

==Process metrics==

Process metrics are used, for example, to assess if the service management processes are running according to expectations.

For suggestions of [[Service Management Metrics|suitable metrics]], please refer to the [[Service_Management_Metrics#Metrics_for_the_incident_resolution_process|list of metrics for the incident resolution process]].

==Roles and responsibilities==

'''<span id="responsible">Process owner: Incident manager</span>'''
*The incident manager is responsible for the effective implementation of the incident resolution process and carries out the corresponding reporting. He represents the first stage of escalation for incidents, should these not be resolvable within the agreed time frames in the relevant service levels.

<p>&nbsp;</p>

{| class="wikitable" style="background: white; text-align:center; vertical-align:top; font-size: 90%; line-height: 1.3em;"
|+<span style="font-size: 120%; line-height: 2.3em;"><span id="raci-matrix-lp4-6">Responsibility matrix: "LP4.6: Resolve incidents and service requests"</span></span>
|- style="vertical-align:top"
! colspan="2"| YaSM role / sub-process
! [[YaSM Roles#1st-level-support|1st level supp.]]
! [[YaSM Roles#2nd-level-support|2nd level supp.]]
! [[YaSM Roles#Configuration-manager|Config. mgr.]]
! [[YaSM Roles#Incident-manager|Incident mgr.]]
! [[YaSM Roles#Major-incident-team|Major incident team]]
! [[YaSM Roles#Service-owner|Serv. owner]]
! [[YaSM Roles#Service-request-fulfillment-group|Serv. requ. fulfill. group]]
! [[YaSM Roles#Technical-domain-expert|Techn. domain expert]]
|- style="text-align:center"
| LP4.6.1
| style="text-align:left"|[[#LP4.6.1|Support incident and service request resolution]]
| -	
| -	
| -	
|AR	
| -	
|R	
| -	
|R
|- style="text-align:center"
|LP4.6.2
| style="text-align:left"|[[#LP4.6.2|Log incidents and service requests]]
|R	
| -	
| -	
|A	
| -	
| -	
| -	
| -
|- style="text-align:center"
|LP4.6.3
| style="text-align:left"|[[#LP4.6.3|Fulfill service requests]]
|R	
| -	
| -	
|A	
| -	
| -	
|R
| -
|- style="text-align:center"
| LP4.6.4
| style="text-align:left"|[[#LP4.6.4|Pro-actively inform users and clients]]
|R	
| -	
| -	
|A	
| -	
| -	
| -
| -
|- style="text-align:center"
| LP4.6.5
| style="text-align:left"|[[#LP4.6.5|Resolve major incidents]]
|R	
| -	
|R	
|AR	
|R	
| -	
| -	
| -
|- style="text-align:center"
| LP4.6.6
| style="text-align:left"|[[#LP4.6.6|Resolve incidents in 1st level support]]
|R	
| -	
| -	
|A	
| -	
| -	
| -
| -
|- style="text-align:center"
| LP4.6.7
| style="text-align:left"|[[#LP4.6.7|Resolve incidents in 2nd level support]]
| -	
|R	
|R	
|A	
| -	
| -	
| -	
|R
|- style="text-align:center"
| LP4.6.8
| style="text-align:left"|[[#LP4.6.8|Monitor incidents and service requests]]
|R	
| -	
| -	
|AR	
| -	
| -	
| - 
| -
|- style="text-align:center"
| LP4.6.9
| style="text-align:left"|[[#LP4.6.9|Close incidents and service requests]]
|R	
| -	
| -	
|A	
| -	
| -	
| - 
| -
|-
|}

<p>&nbsp;</p>

== Notes ==

<html><div itemid="https://yasm.com/wiki/en/img/yasm-process/goal-definition/yasm-incident-management-process.jpg" itemscope itemtype="https://schema.org/ImageObject">
<a href="https://yasm.com/wiki/en/img/yasm-process/goal-definition/yasm-incident-management-process.jpg" title="Incident management: process objectives" itemprop="contentUrl">
<img style="display: block; float: left; margin-left: 10px; margin-right: 20px" src="https://yasm.com/wiki/en/img/yasm-process/goal-definition/yasm-incident-management-process.jpg" width="320" height="167" title="Incident management: process goal" alt="The incident management process in YaSM aims to resolve service incidents or requests for service. In the case of service incidents, the primary objective of this process is to return the service to users as quickly as possible. In some cases this involves applying a workaround." />
<meta itemprop="caption" content="Process objective: YaSM incident management - Resolve incidents and service requests (LP4.6)." />
<meta itemprop="width" content="1200" />
<meta itemprop="height" content="627" />
<meta itemprop="dateCreated" content="2021-09-21" />
<meta itemprop="datePublished" content="2021-09-22" /></a></div>
<div style="margin-left: 5%; color:#636363">
<p style="margin-top: 0; word-wrap:normal;">Is&nbsp;based&nbsp;on: The incident resolution process from the <a href="https://yasm.com/en/products/yasm-process-map" title="YaSM Process Map">YaSM Process Map</a>.</p>

<p>By:&#160;&#160;Stefan Kempter&#160;<a href="https://www.linkedin.com/in/stefankempter"><img style="margin:0px 0px 0px 0px;" src="/wiki/en/img/yasm-wiki/bookmarking/linkedin.jpg" width="16" height="16" title="By: Stefan Kempter | Profile on LinkedIn" alt="Author: Stefan Kempter, IT Process Maps GbR" /></a>&#160;&#160;and&#160;&#160;Andrea Kempter&#160;<a href="https://www.linkedin.com/in/andreakempter"><img style="margin:0px 0px 0px 0px;" src="/wiki/en/img/yasm-wiki/bookmarking/linkedin.jpg" width="16" height="16" title="By: Andrea Kempter | Profile on LinkedIn" alt="Contributor: Andrea Kempter, IT Process Maps GbR" /></a>, IT Process Maps.<br style="clear:both;"/></div><p></html>

==Related articles==

<html><a href="https://yasm.com/wiki/en/index.php/Service_Operation"><img src="https://yasm.com/wiki/en/img/yasm-service-management/service-operation.jpg" title="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-left: 10px; margin-right: 20px" width="320" height="180"/></a>
<div style="margin-left: 5%; color:#636363">
<p style="margin-top: 0; word-wrap:normal;"><a href="https://yasm.com/wiki/en/index.php/Service_Operation" 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>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/wiki/en/index.php/Service_Operation">[...]</a></p></div><p>

<br style="clear:both;"/>
<p>&nbsp;</p>

<p><small>
<span itemprop="breadcrumb" itemscope itemtype="https://schema.org/BreadcrumbList">
<span itemprop="itemListElement" itemscope itemtype="https://schema.org/ListItem">
<a itemprop="item" href="https://yasm.com/wiki/en/index.php/LP4.6:_Resolve_incidents_and_service_requests#Process_description">
<span itemprop="name">Process description</span></a>
<meta itemprop="position" content="1" /></span> ›
<span itemprop="itemListElement" itemscope itemtype="https://schema.org/ListItem">
<a itemprop="item" href="https://yasm.com/wiki/en/index.php/LP4.6:_Resolve_incidents_and_service_requests#Sub-processes">
<span itemprop="name">Sub-processes</span></a>
<meta itemprop="position" content="2" /></span> ›
<span itemprop="itemListElement" itemscope itemtype="https://schema.org/ListItem">
<a itemprop="item" href="https://yasm.com/wiki/en/index.php/LP4.6:_Resolve_incidents_and_service_requests#Process_outputs">
<span itemprop="name">Process outputs</span></a>
<meta itemprop="position" content="3" /></span> ›
<span itemprop="itemListElement" itemscope itemtype="https://schema.org/ListItem">
<a itemprop="item" href="https://yasm.com/wiki/en/index.php/LP4.6:_Resolve_incidents_and_service_requests#Process_metrics">
<span itemprop="name">Metrics</span></a>
<meta itemprop="position" content="4" /></span> ›
<span itemprop="itemListElement" itemscope itemtype="https://schema.org/ListItem">
<a itemprop="item" href="https://yasm.com/wiki/en/index.php/LP4.6:_Resolve_incidents_and_service_requests#Roles_and_responsibilities">
<span itemprop="name">Roles</span></a>
<meta itemprop="position" content="5" /></span>
</span>
</small></p>

<!-- define schema.org/ItemPage --> 
<div itemscope itemtype="https://schema.org/ItemPage">
 <meta itemprop="name Headline" content="LP4.6: Resolve incidents and service requests" />
 <meta itemprop="alternativeHeadline" content="YaSM incident management process" />
 <link itemprop="primaryImageOfPage" href="https://yasm.com/wiki/en/img/yasm-process/Resolve-incidents-and-service-requests-yasm-lp4-6.jpg" />
 <meta itemprop="significantLinks" content="https://yasm.com/wiki/en/index.php/Service_Management_Checklists#yasm-template-example" />
 <meta itemprop="significantLinks" content="https://yasm.com/wiki/en/index.php/Incident_Record_-_Template" />
 <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.6" />
</div>

 <!-- 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" />
 <meta itemscope itemprop="mainEntityOfPage" itemType="https://schema.org/ItemPage"
itemid="https://yasm.com/wiki/en/index.php/LP4.6:_Resolve_incidents_and_service_requests" itemref="md-itempage-description">
 <meta itemprop="name" content="LP4.6: Resolve incidents and service requests" />
 <meta itemprop="alternateName" content="YaSM incident management process" />
 <link itemprop="url" href="https://yasm.com/wiki/en/index.php/LP4.6:_Resolve_incidents_and_service_requests" />
 <link itemprop="hasPart" href="https://yasm.com/wiki/en/index.php/LP4.6:_Resolve_incidents_and_service_requests#LP4.6.1">
 <link itemprop="hasPart" href="https://yasm.com/wiki/en/index.php/LP4.6:_Resolve_incidents_and_service_requests#LP4.6.2">
 <link itemprop="hasPart" href="https://yasm.com/wiki/en/index.php/LP4.6:_Resolve_incidents_and_service_requests#LP4.6.3">
 <link itemprop="hasPart" href="https://yasm.com/wiki/en/index.php/LP4.6:_Resolve_incidents_and_service_requests#LP4.6.4">
 <link itemprop="hasPart" href="https://yasm.com/wiki/en/index.php/LP4.6:_Resolve_incidents_and_service_requests#LP4.6.5">
 <link itemprop="hasPart" href="https://yasm.com/wiki/en/index.php/LP4.6:_Resolve_incidents_and_service_requests#LP4.6.6">
 <link itemprop="hasPart" href="https://yasm.com/wiki/en/index.php/LP4.6:_Resolve_incidents_and_service_requests#LP4.6.7">
 <link itemprop="hasPart" href="https://yasm.com/wiki/en/index.php/LP4.6:_Resolve_incidents_and_service_requests#LP4.6.8">
 <link itemprop="hasPart" href="https://yasm.com/wiki/en/index.php/LP4.6:_Resolve_incidents_and_service_requests#LP4.6.9">
 <link itemprop="hasPart" href="https://yasm.com/wiki/en/index.php/LP4.6:_Resolve_incidents_and_service_requests#process-inputs-outputs">
 <link itemprop="image" href="https://yasm.com/wiki/en/img/yasm-process/Resolve-incidents-and-service-requests-yasm-lp4-6.jpg" />
  <link itemprop="image" href="https://yasm.com/wiki/en/img/yasm-process/goal-definition/yasm-incident-management-process.jpg" />
 <link itemprop="isPartOf" href="https://yasm.com/wiki/en/index.php/LP4:_Operate_the_services" />
  <meta itemprop="mentions" content="ITIL 4 incident management" />
 <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.6:_L%C3%B6sen_von_Incidents_und_Service_Requests" />
 <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>

<!-- This page is assigned to the following categories: -->
[[Category:YaSM process]]
<!-- --- -->