Service Management Checklists: Difference between revisions

From YaSM Service Management Wiki
No edit summary
 
No edit summary
 
(13 intermediate revisions by 2 users not shown)
Line 1: Line 1:
<itpmch><title>YaSM Checklists | YaSM Service Management Wiki</title>
<itpmch><title>Service Management Checklists | YaSM Wiki</title>
<meta name="keywords" content="yasm checklists, yasm document templates, yasm incident record, incident record template" />
<meta name="keywords" content="service management checklists, yasm checklists, service management templates, yasm document templates" />
<meta name="description" content="Checklists ('YaSM document templates') provide detailed explanations of the documents and records which are produced by the YaSM processes." />
<meta name="description" content="These service management templates (checklists and document templates) provide detailed explanations of the documents and records which are produced by the YaSM service management processes." />
<meta property="og:url" content="https://yasm.com/wiki/en/index.php/Service_Management_Checklists" />
<meta property="og:title" content="Service Management Checklists | YaSM Wiki" />
<meta property="og:description" content="These service management templates (checklists and document templates) provide detailed explanations of the documents and records which are produced by the YaSM service management processes." />
<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-templates/16x9/Service-management-templates-index.jpg" />
<meta property="og:image:width" content="1200" />
<meta property="og:image:height" content="675" />
<meta property="og:image" content="https://yasm.com/wiki/en/img/yasm-templates/Service-management-templates-index.jpg" />
<meta property="og:image:width" content="1390" />
<meta property="og:image:height" content="2326" />
<link href="https://plus.google.com/104150539756444616711/posts" rel="publisher" />
</itpmch>
</itpmch>
<html><div itemscope="itemscope" itemtype="https://schema.org/WebPage"><!-- define schema.org/WebPage --><p>
<html><div class="noresize"><a href="https://yasm.com/wiki/de/index.php/Service-Management-Checklisten"><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;"/></html>
<a href="https://yasm.com/wiki/de/index.php/YaSM-Checklisten"><img src="https://yasm.com/wiki/en/img/yasm-wiki/yasm-wiki-deutsch.png" width="48" height="30" style="float:right;" alt="auf Deutsch" title="diese Seite auf Deutsch" /></a><br style="clear:both;"/>
<p>&nbsp;</p>
<p>&nbsp;</p>
<p><span itemprop="description"><span itemprop="name Headline">YaSM checklists</span> ('<span itemprop="alternativeHeadline">YaSM document templates</span>') provide detailed explanations of the various documents and records ('data objects') which are produced by the <a href="https://yasm.com/wiki/en/index.php/YaSM%20Processes" title="YaSM service management processes">YaSM processes</a>.</span>
<p><b>On this page:</b> <a href="#yasm-template-example" title="Example: YaSM document template">Example - Incident record checklist</a><p></html>


<span id="md-webpage-description" itemprop="description">These <b><span style="color:#465674;">service management templates (checklists and document templates)</span></b> provide detailed explanations of the various documents and records ('data objects') which are produced by the [[Service Management Processes|YaSM service management processes]].</span>
<p>&nbsp;</p>
<p>&nbsp;</p>


==<span id="yasm-document-templates">YaSM document templates</span>==
<html><div itemid="https://yasm.com/wiki/en/img/yasm-templates/yasm-document-templates-checklists.jpg" itemscope itemtype="https://schema.org/ImageObject">
<meta itemprop="caption" content="YaSM service management checklist: document template. Example: 'Incident record' template." />
<meta itemprop="width" content="1200" />
<meta itemprop="height" content="900" />
<meta itemprop="dateCreated" content="2023-05-27" />
<meta itemprop="datePublished" content="2023-06-01" />
<span itemprop="thumbnail" itemscope itemtype="https://schema.org/ImageObject">
  <meta itemprop="url" content="https://yasm.com/wiki/en/img/yasm-templates/480px/yasm-document-templates-checklists.jpg" />
  <meta itemprop="width" content="480" />
  <meta itemprop="height" content="360" />
<meta itemprop="dateCreated" content="2023-05-27" />
<meta itemprop="datePublished" content="2023-06-01" />
</span>
<span itemprop="thumbnail" itemscope itemtype="https://schema.org/ImageObject">
  <meta itemprop="url" content="https://yasm.com/wiki/en/img/yasm-templates/400px/yasm-document-templates-checklists.jpg" />
  <meta itemprop="width" content="400" />
  <meta itemprop="height" content="300" />
<meta itemprop="dateCreated" content="2024-03-11" />
<meta itemprop="datePublished" content="2024-03-11" />
</span>
<meta itemprop="keywords" content="yasm checklist" />
<meta itemprop="keywords" content="service management template" />
<meta itemprop="keywords" content="yasm document template" />
<meta itemprop="keywords" content="service management template example" />
<figure class="mw-halign-right" typeof="mw:File/Thumb"><a itemprop="contentUrl" href="https://yasm.com/wiki/en/img/yasm-templates/yasm-document-templates-checklists.jpg" title="YaSM checklist (service management template): Example"><img srcset="https://yasm.com/wiki/en/img/yasm-templates/400px/yasm-document-templates-checklists.jpg 400w, https://yasm.com/wiki/en/img/yasm-templates/480px/yasm-document-templates-checklists.jpg 480w, https://yasm.com/wiki/en/img/yasm-templates/yasm-document-templates-checklists.jpg 1200w" sizes="100vw" src="https://yasm.com/wiki/en/img/yasm-templates/yasm-document-templates-checklists.jpg" decoding="async" width="400" height="300" class="mw-file-element" alt="YaSM service management document templates and checklists. - Example: Incident record." /></a><figcaption><span style="font-variant:small-caps;"><b>Fig. 1: <a href="https://yasm.com/wiki/en/img/yasm-templates/yasm-document-templates-checklists.jpg" title="YaSM checklist (service management template): Example">YaSM service management template</a></b><br />Checklist / document template: example.</span></figcaption></figure></div></html>
 
__TOC__
<br style="clear:both;"/>
 
==<span id="Document_templates">Service management templates and policies==
 
<span style="word-wrap:normal;">Each template describes the typical contents of a YaSM document or record. The service management checklists are generic, and applicable to most organizations; they can be used as templates in many cases when specific service management documents need to be created for a particular organization.</span>
 
<html><div itemid="https://yasm.com/wiki/en/img/yasm-templates/Service-management-templates-index.jpg" itemscope itemtype="https://schema.org/ImageObject">
<meta itemprop="caption" content="Service management templates: Index" />
<meta itemprop="width" content="1390" />
<meta itemprop="height" content="2326" />
<meta itemprop="dateCreated" content="2023-06-01" />
<meta itemprop="datePublished" content="2023-06-01" />
<meta itemprop="representativeOfPage" content="true"/>
<span itemprop="thumbnail" itemscope itemtype="https://schema.org/ImageObject">
  <meta itemprop="url" content="https://yasm.com/wiki/en/img/yasm-templates/16x9/Service-management-templates-index.jpg" />
  <meta itemprop="width" content="1200" />
  <meta itemprop="height" content="675" />
<meta itemprop="dateCreated" content="2023-06-01" />
<meta itemprop="datePublished" content="2023-06-01" />
</span>
<span itemprop="thumbnail" itemscope itemtype="https://schema.org/ImageObject">
  <meta itemprop="url" content="https://yasm.com/wiki/en/img/yasm-templates/400px/Service-management-templates-index.jpg" />
  <meta itemprop="width" content="400" />
  <meta itemprop="height" content="670" />
<meta itemprop="dateCreated" content="2023-06-01" />
<meta itemprop="datePublished" content="2023-06-01" />
</span>
<meta itemprop="keywords" content="service management templates" />
<meta itemprop="keywords" content="service management document templates" />
<meta itemprop="keywords" content="service management checklists" />
<figure class="mw-halign-right" typeof="mw:File/Thumb"><a itemprop="contentUrl" href="https://yasm.com/wiki/en/img/yasm-templates/Service-management-templates-index.jpg" title="Service management templates: Index"><img srcset="https://yasm.com/wiki/en/img/yasm-templates/400px/Service-management-templates-index.jpg 400w, https://yasm.com/wiki/en/img/yasm-templates/Service-management-templates-index.jpg 1390w" sizes="100vw" src="https://yasm.com/wiki/en/img/yasm-templates/Service-management-templates-index.jpg" fetchpriority="high" decoding="async" width="400" height="670" class="mw-file-element" alt="Index of service management templates (checklists, document templates and policies) in the YaSM service management model." /></a><figcaption><span style="font-variant:small-caps;"><b>Fig. 2: <a href="https://yasm.com/wiki/en/img/yasm-templates/Service-management-templates-index.jpg" title="Service management templates: Index">Service management templates: Index</a></b></span></figcaption></figure></div>
 


Each checklist describes the typical contents of a YaSM document or record, as shown in the [[#yasm-template-example|following example]]. Because checklists are Microsoft Word&trade; documents, they can often be used as templates when creating the service management documents for a particular organization.


<html><p>The <a itemprop="significantLinks" href="https://yasm.com/en/products/yasm-process-map" title="YaSM&reg; Process Map">YaSM&reg; Process Map</a> includes 75 checklists, one for every <i>YaSM data object</i>. In addition, there is a set of 19 checklists for the <i>service management policies</i>.</html>
<p>Our <a class="external text" href="https://yasm.com/en/products/yasm-process-map">service management process model (the YaSM&#174; Process Map)</a> contains a total of 95 document templates:</p>
<ul><li>76 checklists (one for every <i>YaSM data object</i> - see fig. 2: "<a href="https://yasm.com/wiki/en/img/yasm-templates/Service-management-templates-index.jpg" title="Service management templates: Index">Index</a>") exemplify what data or information is contained in the different documents and records generated by the YaSM processes.</li>
<li>There is also a set of 19 checklists for the <i>service management policies</i>.</li></ul></html>


<p>&nbsp;</p>
<span id="yasm-template-example">Here in the YaSM Wiki we provide you with the most frequently requested service management templates from the YaSM Process Map free of charge.</span>
 
==<span id="#Checklists_for_the_service_lifecycle_processes">Templates for the service lifecycle processes</span>==
 
====Incident record template====
An incident record is a set of data with all details of a service incident, documenting the history of the incident from registration to closure.


==<span id="yasm-template-example">Example: YaSM checklist "Incident record"</span>==
[[Incident Record - Template|&#8594; Details: Incident record ...]]


<html><p><b>Checklist/ document template:</b> <span id="incident-record-template">Incident record</span></p>
====Problem record template====
<p><b>Related YaSM process</b>: <a itemprop="significantLinks" href="https://yasm.com/wiki/en/index.php/LP4.6:_Resolve_incidents_and_service_requests#Process_description" title="Process description: LP4.6: Resolve incidents and service requests">LP4.6: Resolve incidents and service requests</a></html>
A problem record is a set of data with all details of a problem, documenting the history of the problem from registration to closure.


<p>&nbsp;</p>
[[Problem Record - Template|&#8594; Details: Problem record ...]]


====<span id="incident-record-definition">Incident record: Definition</span>====
====Service quality report====
<hr>
A service quality report gives insight into the service provider's ability to deliver the agreed service quality. Most importantly, it reports on the service levels achieved in relation to the agreed targets, as specified in the [[#Service definition|service definitions]].


<p>&nbsp;</p>
[[Service Quality Report - Template|&#8594; Document template: Service quality report ...]]


<html><div itemscope itemtype="https://schema.org/ImageObject" style="min-width:442px;"><div class="thumb tright" style="width:442px;"><img itemprop="contentUrl" style="margin:0px 0px 10px 0px;" src="https://yasm.com/wiki/en/img/yasm-templates/yasm-document-templates-checklists.jpg" width="442" height="687" title="Fig. 1: YaSM checklist/ document template - Example | Incident record template." alt="YaSM document templates and checklists. - Example: Checklist incident record." /><div class="thumbcaption"><span style="font-variant:small-caps;"><b>Figure 1:</b></span> <small><span itemprop="caption">YaSM checklist/ document template - Example | Incident record template.</span></small></div></div></div>
====Service improvement plan - SIP====
The service improvement plan (SIP) is used to manage service improvement initiatives and report on their status throughout their lifecycle. There may be one service improvement plan for all services or dedicated plans for the various services managed by the service provider.


<p>An <i>incident record</i> is 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).<p></html>
[[Service Improvement Plan - Template|&#8594; Checklist: Service improvement plan ...]]


<p>&nbsp;</p>
==<span id="#Checklists_for_the_supporting_processes">Templates for the supporting processes</span>==


====<span id="contents-incident-record">Typical contents of an incident record</span>====
====Process review report template====
<hr>
A process review report records the details and findings from a process review or process audit. This report is an important input for the definition of process improvement initiatives.
<html><div itemscope="itemscope" itemtype="https://schema.org/ItemList"><!-- define schema.org/ItemList -->
<meta itemprop="itemListOrder" content="Ascending" />
<p><span itemprop="name" content="Incident Record - Typical contents:"><i>An Incident Record</i> typically contains the following information:</span>
</p>
<p>&#160;</p>
<p><b><span itemprop="itemListElement">Unique incident ID</span></b></p>
<ul><li itemprop="description">A unique ID is usually allocated automatically by the application used to manage service incidents.</li></ul>
<p><br></p>
<p><b><span itemprop="itemListElement">Incident status</span></b></p>
<ul><li itemprop="description">Incident status values could be for example "Raised", "Open", "Resolved", "Closed", ...</li></ul>
<p><br></p>
<p><b><span itemprop="itemListElement">Incident recording</span></b></p>
<ul><li itemprop="description">Date and time of incident recording.</li></ul>
<p><br></p>
<p><b><span itemprop="itemListElement">Incident occurrence</span></b></p>
<ul><li itemprop="description">Date and time of incident occurrence.</li></ul>
<p><br></p>
<p><b><span itemprop="itemListElement">Source and method of notification</span></b></p>
<ul><li itemprop="description">E.g. telephone, e-mail, intranet portal, event monitoring system.</li></ul>
<p><br></p>
<p><b><span itemprop="itemListElement">Contact information</span></b></p>
<ul><li itemprop="description">Caller/ user contact information and callback method.</li></ul>
<p><br></p>
<p><b><span itemprop="itemListElement">Authorization information</span></b></p>
<ul><li itemprop="description">If applicable, details on how it has been established that the requester is authorized to raise the incident.</li></ul>
<p><br></p>
<p><b><span itemprop="itemListElement">Incident owner</span></b></p>
<ul><li itemprop="description">The incident owner retains overall responsibility for the resolution of the incident, even if it is assigned during its lifecycle to other support agents or groups to perform specific tasks.</li></ul>
<p><br></p>
<p><b><span itemprop="itemListElement">Assignment</span></b></p>
<ul><li itemprop="description">Agent or support group to which the incident is assigned. This assignment may change during the lifecycle of the incident.</li></ul>
<p><br></p>
<p><b><span itemprop="itemListElement">Incident classification</span></b></p>
<ul><li itemprop="description">Incident classification is a way to add tags to incidents which are instrumental in assigning them to the appropriate support agent or group, as well as in the creation of statistics and the analysis of historical incidents.</li></ul>
<p><br></p>
<p><b><span itemprop="itemListElement">Incident categorization</span></b></p>
<ul><li itemprop="description">Classification schemes may vary between different organizations, but incidents are often classified by<br>&bull; Service(s) affected<br>&bull; Customer(s) affected<br>&bull; Location(s) affected<br>&bull; Infrastructure component(s) and sub-component(s) (i.e. configuration items) affected<br>&bull; Type of symptom (e.g. "Hardware defect", "Software defect", "Slow performance", "Security issue", ...).</li></ul>
<p><br></p>
<p><b><span itemprop="itemListElement">Symptoms</span></b></p>
<ul><li itemprop="description">Description of symptoms.</li></ul>
<p><br></p>
<p><b><span itemprop="itemListElement">Priority</span></b></p>
<ul><li itemprop="description">Priority is often expressed in priority codes like "Critical", "High", "Medium", "Low", "Very low"). Priority is the result from the combination of urgency and impact where<br>&bull; Urgency is a measure of the available time until the resolution of the incident<br>&bull; Impact is a measure of the (potential) damage to the business.<br>For an example for a prioritization scheme, refer to the checklist "Incident and Service Request Policy".<br>For recurring incidents, rules for prioritizing the incidents are typically defined in or coded into the corresponding incident models.</li></ul>
<p><br></p>
<p><b><span itemprop="itemListElement">Major incident flag</span></b></p>
<ul><li itemprop="description">This flag indicates that an incident is treated as a major incident.</li></ul>
<p><br></p>
<p><b><span itemprop="itemListElement">Target time for incident resolution</span></b></p>
<ul><li itemprop="description">This is the target time as committed in the applicable service definitions and agreements. Target resolution times are typically determined based on the incident’s priority.</li></ul>
<p><br></p>
<p><b><span itemprop="itemListElement">Incident model(s)</span></b></p>
<ul><li itemprop="description">Applicable incident model(s).</li></ul>
<p><br></p>
<p><b><span itemprop="itemListElement">Links to related incident records</span></b></p>
<ul><li itemprop="description">If similar outstanding incidents exist to which the new incident can be attributed in this case, one incident is usually declared the "master incident".</li></ul>
<p><br></p>
<p><b><span itemprop="itemListElement">Links to related event records</span></b></p>
<ul><li itemprop="description">If the incident has been raised following an event detected by an event monitoring system.</li></ul>
<p><br></p>
<p><b><span itemprop="itemListElement">Links to related problem records</span></b></p>
<ul><li itemprop="description">If any problems exist which are related to the incident at hand in particular, a problem record can contain a suitable workaround.</li></ul>
<p><br></p>
<p><b><span itemprop="itemListElement">Links to related change records</span></b></p>
<ul><li itemprop="description">If any change requests were submitted during incident resolution.<br>&bull; If the incident is linked to a (recently implemented) change.</li></ul>
<p><br></p>
<p><b><span itemprop="itemListElement">Functional escalations</span></b></p>
<ul><li itemprop="description">Functional escalations (changes in the assignment of the incident to particular support agents or groups) must be recorded.</li></ul>
<p><br></p>
<p><b><span itemprop="itemListElement">Hierarchic escalations</span></b></p>
<ul><li itemprop="description">High-priority or delayed incidents usually trigger hierarchic escalations, for example to top management. Such escalations must be recorded.</li></ul>
<p><br></p>
<p><b><span itemprop="itemListElement">Status changes</span></b></p>
<ul><li itemprop="description">This section records incident status changes (for example from "open" to "resolved").</li></ul>
<p><br></p>
<p><b><span itemprop="itemListElement">Activity log/ tasks assigned to the incident</span></b></p>
<ul><li itemprop="description">Most applications for managing incidents allow maintaining a simple log of steps carried out to resolve the incident. Some systems, however, also provide the means to assign "tasks" to incidents. Akin to the incidents 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.</li></ul>
<p><br></p>
<p><b><span itemprop="itemListElement">Incident closure</span></b></p>
<ul><li itemprop="description">Closure information.</li></ul>
<p><br></p>
<p><b><span itemprop="itemListElement">Resolution type</span></b></p>
<ul><li itemprop="description">Elimination of the underlying cause vs. application of a workaround. If the incident was resolved by applying a workaround: Indication of the applied workaround.</li></ul>
<p><br></p>
<p><b><span itemprop="itemListElement">Problems raised</span></b></p>
<ul><li itemprop="description">A problem record must be raised, for example<br>&bull; If the incident is likely to recur and preventive action is necessary<br>&bull; If the incident has not been completely understood<br>&bull; If a new workaround has been devised during incident resolution.</li></ul>
<p><br></p>
<p><b><span itemprop="itemListElement">Customer feedback</span></b></p>
<ul><li itemprop="description">Confirmation from the customer or user that the incident has been resolved results from a satisfaction survey if one has been conducted.</li></ul>
<p><br></p>
<p><b><span itemprop="itemListElement">Additional information</span></b></p>
<ul><li itemprop="description">Notes and additional information.</li></ul>
</div><!-- end of schema.org/ItemList --><p></html>


<p>&nbsp;</p>
[[Process Review Report - Template|&#8594; Details: Process review report ...]]


====Notes====
====Service portfolio template====
<hr>
The service portfolio represents a complete list of all services managed by the service provider.
*For particular types of recurring incidents, incident models describe how the incidents are to be resolved. In many cases, the handling of such incidents is supported by appropriately configured incident management tools (for example, there may be short-cuts to easily create certain types of incident records).
*The classification of incidents and problems should use the same scheme in order to support matching between incidents and problems - which is important, for example, for the identification of known errors and available workarounds during the resolution of an incident.


<p>&nbsp;</p>
[[Service Portfolio - Template|&#8594; Details: Service portfolio ...]]


<br style="clear:both;"/>
====Service definition====
A service definition specifies the service properties, in particular the offered functionality and the guaranteed service levels. Service definitions also describe how the organization's resources are used in order to provide the service.


==[ Infobox ]==
[[Service Definition - Template|&#8594; Checklist: Service definition ...]]
<p>&nbsp;</p>


<html><table class="wikitable">
==Notes==
<tr>
<html>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.
<td>Link to this page:</td>
<p>&nbsp;</p>
<td><a itemprop="url" href="https://yasm.com/wiki/en/index.php/YaSM%20Checklists">https://yasm.com/wiki/en/index.php/Service_Management_Checklists</a></td>
</tr>
<tr>
<td>Languages:</td>
<td><span itemprop="inLanguage" content="en">English</span> | <span><a itemprop="citation" class="external TEXT" href="https://yasm.com/wiki/de/index.php/YaSM-Checklisten" title="YaSM-Checklisten">Deutsch</a></span></td>
</tr>
<tr>
<td>Image:</td>
<td style="vertical-align:top"><a itemprop="primaryImageOfPage" href="https://yasm.com/wiki/en/img/yasm-templates/yasm-document-templates-checklists.jpg" title="YaSM document templates. - Example: Checklist 'Incident Record'">Example: YaSM checklist 'Incident Record' (.JPG)</a></td>
</tr>
<tr>
<td>Is based on:</td>
<td style="vertical-align:top">YaSM "Incident record" template from the <a itemprop="isBasedOnUrl" href="https://yasm.com/en/products/yasm-process-map" title="Checklist/ template from the YaSM Process Map" class="external text">YaSM Process Map</a></td>
</tr>
<tr>
<td>Author | Contributor:</td>
<td><span itemprop="author">Stefan Kempter</span>&nbsp;<a rel="author" href="https://plus.google.com/111925560448291102517"><img style="margin:0px 0px 0px 0px;" src="/wiki/en/img/yasm-wiki/bookmarking/google.jpg" width="16" height="16" title="By: Stefan Kempter | Profile on Google+" alt="Author: Stefan Kempter, IT Process Maps GbR" /></a> &nbsp; and <span itemprop="contributor">Andrea Kempter</span>&nbsp;<a href="https://plus.google.com/113316270668629760475"><img style="margin:0px 0px 0px 0px;" src="/wiki/en/img/yasm-wiki/bookmarking/google.jpg" width="16" height="16" title="By: Andrea Kempter | Profile on Google+" alt="Contributor: Andrea Kempter, IT Process Maps GbR" /></a> &nbsp; - &nbsp; <span itemprop="creator copyrightHolder publisher">IT Process Maps</span>.</td>
</tr>
</table>


<p><small>
<p><small>
<span itemscope="itemscope" itemtype="http://data-vocabulary.org/Breadcrumb">
<span itemprop="breadcrumb" itemscope itemtype="http://schema.org/BreadcrumbList">
<a href="https://yasm.com/wiki/en/index.php/YaSM%20Checklists" itemprop="url"><span itemprop="title">YaSM checklists</span></a> ›
<span itemprop="itemListElement" itemscope itemtype="http://schema.org/ListItem">
</span>
<a itemprop="item" href="https://yasm.com/wiki/en/index.php/Service_Management_Checklists#Service_management_templates_and_policies">
<span itemscope="itemscope" itemtype="http://data-vocabulary.org/Breadcrumb">
<span itemprop="name">Templates and policies</span></a>
<a href="https://yasm.com/wiki/en/index.php/YaSM%20Checklists#yasm-document-templates" itemprop="url"><span itemprop="title">YaSM document templates</span></a> ›
<meta itemprop="position" content="1" /></span> ›
</span>
<span itemprop="itemListElement" itemscope itemtype="http://schema.org/ListItem">
<span itemscope="itemscope" itemtype="http://data-vocabulary.org/Breadcrumb">
<a itemprop="item" href="https://yasm.com/wiki/en/index.php/Service_Management_Checklists#Templates_for_the_service_lifecycle_processes">
<a href="https://yasm.com/wiki/en/index.php/YaSM%20Checklists#yasm-template-example" itemprop="url"><span itemprop="title">Example: YaSM checklist 'Incident record'</span></a>
<span itemprop="name">Templates for the service lifecycle processes</span></a>
<meta itemprop="position" content="2" /></span> ›
<span itemprop="itemListElement" itemscope itemtype="http://schema.org/ListItem">
<a itemprop="item" href="https://yasm.com/wiki/en/index.php/Service_Management_Checklists#Templates_for_the_supporting_processes">
<span itemprop="name">Templates for the supporting processes</span></a>
<meta itemprop="position" content="3" /></span>
</span>
</span>
</small></p>
</small></p>
</div><!-- end of schema.org/WebPage --><p></html>
 
<!-- define schema.org/WebPage --> <span itemid="https://yasm.com/wiki/en/index.php/Service_Management_Checklists" itemscope itemtype="https://schema.org/WebPage" itemref="md-webpage-description">
  <meta itemprop="name Headline" content="Service management checklists" />
  <meta itemprop="alternativeHeadline" content="Service management templates" />
  <meta itemprop="alternativeHeadline" content="YaSM document templates" />
  <meta itemprop="alternativeHeadline" content="YaSM checklists" />
  <link itemprop="url" href="https://yasm.com/wiki/en/index.php/Service_Management_Checklists" />
  <link itemprop="primaryImageOfPage" href="https://yasm.com/wiki/en/img/yasm-templates/Service-management-templates-index.jpg" />
  <link itemprop="Image" href="https://yasm.com/wiki/en/img/yasm-templates/yasm-document-templates-checklists.jpg" />
  <meta itemprop="significantLinks" content="https://yasm.com/wiki/en/index.php/Incident_Record_-_Template" />
  <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/Service-Management-Checklisten" />
  <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" />
</span><p></html>


<!-- This page is assigned to the following categories: -->
<!-- This page is assigned to the following categories: -->
[[Category:YaSM checklist|!]][[Category:YaSM term (data object)]]
[[Category:YaSM checklist|!]][[Category:YaSM term (data object)]]
<!-- --- -->
<!-- --- -->

Latest revision as of 16:46, 21 September 2024

auf Deutsch


 

These service management templates (checklists and document templates) provide detailed explanations of the various documents and records ('data objects') which are produced by the YaSM service management processes.

 

YaSM service management document templates and checklists. - Example: Incident record.
Fig. 1: YaSM service management template
Checklist / document template: example.


Service management templates and policies

Each template describes the typical contents of a YaSM document or record. The service management checklists are generic, and applicable to most organizations; they can be used as templates in many cases when specific service management documents need to be created for a particular organization.

Our service management process model (the YaSM® Process Map) contains a total of 95 document templates:

  • 76 checklists (one for every YaSM data object - see fig. 2: "Index") exemplify what data or information is contained in the different documents and records generated by the YaSM processes.
  • There is also a set of 19 checklists for the service management policies.

Here in the YaSM Wiki we provide you with the most frequently requested service management templates from the YaSM Process Map free of charge.

Templates for the service lifecycle processes

Incident record template

An incident record is a set of data with all details of a service incident, documenting the history of the incident from registration to closure.

→ Details: Incident record ...

Problem record template

A problem record is a set of data with all details of a problem, documenting the history of the problem from registration to closure.

→ Details: Problem record ...

Service quality report

A service quality report gives insight into the service provider's ability to deliver the agreed service quality. Most importantly, it reports on the service levels achieved in relation to the agreed targets, as specified in the service definitions.

→ Document template: Service quality report ...

Service improvement plan - SIP

The service improvement plan (SIP) is used to manage service improvement initiatives and report on their status throughout their lifecycle. There may be one service improvement plan for all services or dedicated plans for the various services managed by the service provider.

→ Checklist: Service improvement plan ...

Templates for the supporting processes

Process review report template

A process review report records the details and findings from a process review or process audit. This report is an important input for the definition of process improvement initiatives.

→ Details: Process review report ...

Service portfolio template

The service portfolio represents a complete list of all services managed by the service provider.

→ Details: Service portfolio ...

Service definition

A service definition specifies the service properties, in particular the offered functionality and the guaranteed service levels. Service definitions also describe how the organization's resources are used in order to provide the service.

→ Checklist: Service definition ...

 

Notes

By:  Stefan Kempter Author: Stefan Kempter, IT Process Maps GbR  and  Andrea Kempter Contributor: Andrea Kempter, IT Process Maps GbR, IT Process Maps.

 

Templates and policies  › Templates for the service lifecycle processes  › Templates for the supporting processes

Retrieved from "https://yasm.com/wiki/en/index.php?title=Service_Management_Checklists&oldid=1411"