FitSM and YaSM - Revision history

Andrea at 10:43, 22 January 2025

2025-01-22T10:43:29Z

← Older revision		Revision as of 12:43, 22 January 2025
Line 1:		Line 1:
	<itpmch><title>FitSM and YaSM \| YaSM Service Management Wiki</title>		<itpmch><title>FitSM and YaSM \| YaSM Service Management Wiki</title>
	<meta name="keywords" content="fitsm processes, fitsm templates, fitsm process model" />		<meta name="keywords" content="fitsm processes, fitsm templates, fitsm process model" />
	<meta name="description" content="While FitSM includes documents with requirements and supporting guidance, YaSM provides a ready-to-use process model for service management in popular formats, such as Visio and ARIS." />		<meta name="description" content="While FitSM includes documents with requirements and supporting guidance, YaSM provides a ready-to-use process model for service management in popular formats, such as Visio, BIC Process Design, and ARIS." />
			<meta name="thumbnail" content="https://yasm.com/wiki/en/img/yasm-frameworks/fitsm/thumbnail/fitsm-process-templates-yasm.jpg" />
	<meta property="og:url" content="https://yasm.com/wiki/en/index.php/FitSM_and_YaSM" />		<meta property="og:url" content="https://yasm.com/wiki/en/index.php/FitSM_and_YaSM" />
	<meta property="og:title" content="FitSM and YaSM \| YaSM Service Management Wiki" />		<meta property="og:title" content="FitSM and YaSM \| YaSM Service Management Wiki" />
	<meta property="og:description" content="While FitSM includes documents with requirements and supporting guidance, YaSM provides a ready-to-use process model for service management in popular formats, such as Visio and ARIS." />		<meta property="og:description" content="While FitSM includes documents with requirements and supporting guidance, YaSM provides a ready-to-use process model for service management in popular formats, such as Visio, BIC Process Design, and ARIS." />
	<meta property="og:site_name" content="YaSM Service Management">		<meta property="og:site_name" content="YaSM Service Management">
	<meta property="og:type" content="article" />		<meta property="og:type" content="article" />
Line 14:		Line 15:
	</itpmch>		</itpmch>
	<html><div class="noresize"><a href="https://yasm.com/wiki/de/index.php/FitSM_und_YaSM"><img src="https://yasm.com/wiki/en/img/yasm-wiki/YaSM-Wiki-Deutsch.png" width="210" height="54" style="float:right;" alt="auf Deutsch" title="This page in German" /></a></div><br style="clear:both;"/>		<html><div class="noresize"><a href="https://yasm.com/wiki/de/index.php/FitSM_und_YaSM"><img src="https://yasm.com/wiki/en/img/yasm-wiki/YaSM-Wiki-Deutsch.png" width="210" height="54" style="float:right;" alt="auf Deutsch" title="This page in German" /></a></div><br style="clear:both;"/>
	~~<p> </p>~~
	<p><b>Comparison:</b> YaSM and FitSM</p>		<p><b>Comparison:</b> YaSM and FitSM</p>
	<p><b>Part of</b>: <a href="https://yasm.com/wiki/en/index.php/What_is_YaSM#yasm-other-service-management-frameworks" title="YaSM and other service management frameworks and standards">YaSM vs. other service management frameworks and standards</a></html>		<p><b>Part of</b>: <a href="https://yasm.com/wiki/en/index.php/What_is_YaSM#yasm-other-service-management-frameworks" title="YaSM and other service management frameworks and standards">YaSM vs. other service management frameworks and standards</a></html>
Line 27:		Line 28:
	<meta itemprop="height" content="900" />		<meta itemprop="height" content="900" />
	<meta itemprop="representativeOfPage" content="true"/>		<meta itemprop="representativeOfPage" content="true"/>
			<meta itemprop="dateCreated" content="2021-12-14" />
			<meta itemprop="datePublished" content="2021-12-25" />
	<span itemprop="thumbnail" itemscope itemtype="https://schema.org/ImageObject">		<span itemprop="thumbnail" itemscope itemtype="https://schema.org/ImageObject">
	<meta itemprop="url" content="https://yasm.com/wiki/en/img/yasm-frameworks/fitsm/480px/fitsm-process-templates-yasm.jpg" />		<meta itemprop="url" content="https://yasm.com/wiki/en/img/yasm-frameworks/fitsm/480px/fitsm-process-templates-yasm.jpg" />
Line 34:		Line 37:
	<meta itemprop="datePublished" content="2022-10-02" />		<meta itemprop="datePublished" content="2022-10-02" />
	</span>		</span>
	<meta itemprop="dateCreated" content="~~2021~~-12-14" />		<span itemprop="thumbnail" itemscope itemtype="https://schema.org/ImageObject">
	<meta itemprop="datePublished" content="~~2021~~-12-25" />		<meta itemprop="url" content="https://yasm.com/wiki/en/img/yasm-frameworks/fitsm/thumbnail/fitsm-process-templates-yasm.jpg" />
			<meta itemprop="width" content="1200" />
			<meta itemprop="height" content="1200" />
			<meta itemprop="dateCreated" content="2025-01-22" />
			<meta itemprop="datePublished" content="2025-01-22" />
			</span>
	<meta itemprop="keywords" content="FitSM process templates" />		<meta itemprop="keywords" content="FitSM process templates" />
	<meta itemprop="keywords" content="FitSM process model" />		<meta itemprop="keywords" content="FitSM process model" />
	<figure class="mw-halign-right" typeof="mw:File/Thumb"><a itemprop="contentUrl" href="https://yasm.com/wiki/en/img/yasm-frameworks/fitsm/fitsm-process-templates-yasm.jpg" title="Comparison: FitSM and YaSM service management templates"><img srcset="https://yasm.com/wiki/en/img/yasm-frameworks/fitsm/480px/fitsm-process-templates-yasm.jpg 480w, https://yasm.com/wiki/en/img/yasm-frameworks/fitsm/fitsm-process-templates-yasm.jpg 1200w" sizes="100vw" src="https://yasm.com/wiki/en/img/yasm-frameworks/fitsm/fitsm-process-templates-yasm.jpg" fetchpriority="high" decoding="async" width="480" height="360" class="mw-file-element" alt="While FitSM includes documents with requirements and supporting guidance, YaSM provides a ready-to-use process model for service management in popular formats, such as Visio and ARIS." /></a><figcaption><span style="font-variant:small-caps;"><b>Fig. 1: <a href="https://yasm.com/wiki/en/img/yasm-frameworks/fitsm/fitsm-process-templates-yasm.jpg" title="FitSM and YaSM service management templates">FitSM requirements vs. YaSM process templates</a></b></span></figcaption></figure></div></html>		<figure class="mw-halign-right" typeof="mw:File/Thumb"><a itemprop="contentUrl" href="https://yasm.com/wiki/en/img/yasm-frameworks/fitsm/fitsm-process-templates-yasm.jpg" title="Comparison: FitSM and YaSM service management templates"><img srcset="https://yasm.com/wiki/en/img/yasm-frameworks/fitsm/480px/fitsm-process-templates-yasm.jpg 480w, https://yasm.com/wiki/en/img/yasm-frameworks/fitsm/fitsm-process-templates-yasm.jpg 1200w" sizes="100vw" src="https://yasm.com/wiki/en/img/yasm-frameworks/fitsm/fitsm-process-templates-yasm.jpg" fetchpriority="high" decoding="async" width="480" height="360" class="mw-file-element" alt="While FitSM includes documents with requirements and supporting guidance, YaSM provides a ready-to-use process model for service management in popular formats, such as Visio, BIC Process Design, and ARIS." /></a><figcaption><span style="font-variant:small-caps;"><b>Fig. 1: <a href="https://yasm.com/wiki/en/img/yasm-frameworks/fitsm/fitsm-process-templates-yasm.jpg" title="FitSM and YaSM service management templates">FitSM requirements vs. YaSM process templates</a></b></span></figcaption></figure></div></html>

	__TOC__		__TOC__
Line 55:		Line 63:
	<li><a href="https://yasm.com/en/products/yasm-process-map-bic" title="YaSM Process Map for the BIC Platform">a process model for BIC / BIC Process Design</a>®,</li>		<li><a href="https://yasm.com/en/products/yasm-process-map-bic" title="YaSM Process Map for the BIC Platform">a process model for BIC / BIC Process Design</a>®,</li>
	<li>as a <a href="https://yasm.com/en/products/yasm-process-map-aris" title="YaSM Process Map for ARIS">reference model for the ARIS Process Platform</a>™.</li>		<li>as a <a href="https://yasm.com/en/products/yasm-process-map-aris" title="YaSM Process Map for ARIS">reference model for the ARIS Process Platform</a>™.</li>
	<li>and also as <a href="https://yasm.com/en/products/service-management-templates-bpmn-xml" title="Service management templates in BPMN XML">BPMN XML ~~documents~~</a>.</li></ul><li>		<li>and also as <a href="https://yasm.com/en/products/service-management-templates-bpmn-xml" title="Service management templates in BPMN XML">BPMN-DI compatible XML templates</a> for popular BPM tools like Signavio®, Adonis®, iGrafx® etc.</li></ul><li>
	<li>The templates are fully editable, allowing organizations to design tailor-made processes without having to start from nothing.</li></ul></html>		<li>The templates are fully editable, allowing organizations to design tailor-made processes without having to start from nothing.</li></ul></html>

Line 65:		Line 73:

	For example, FitSM requires that		For example, FitSM requires that
	* top management is committed to planning, implementing and operating a service management system		* top management is committed to planning, implementing and operating a service management system
	* service management scope, goals and policies are documented and communicated		* service management scope, goals and policies are documented and communicated
	* service management processes are defined and documented, including inputs, activities, outputs and responsibilities		* service management processes are defined and documented, including inputs, activities, outputs and responsibilities

Andrea at 11:26, 9 August 2024

2024-08-09T11:26:18Z

Show changes

Andrea at 16:04, 30 December 2023

2023-12-30T16:04:00Z

← Older revision		Revision as of 18:04, 30 December 2023
Line 6:		Line 6:
	<meta property="og:description" content="While FitSM includes documents with requirements and supporting guidance, YaSM provides a ready-to-use process model for service management in popular formats, such as Visio and ARIS." />		<meta property="og:description" content="While FitSM includes documents with requirements and supporting guidance, YaSM provides a ready-to-use process model for service management in popular formats, such as Visio and ARIS." />
	<meta property="og:site_name" content="YaSM Service Management">		<meta property="og:site_name" content="YaSM Service Management">
	<meta property="og:type" content="article~~" />~~		<meta property="og:type" content="article" />
	~~<meta property="article:publisher" content="https://www.facebook.com/yasmcom" />~~
	~~<meta property="fb:admins" content="100002035253209" />~~
	~~<meta property="fb:admins" content="100002592864414~~" />
	<meta property="og:image" content="https://yasm.com/wiki/en/img/yasm-frameworks/fitsm/fitsm-process-templates-yasm.jpg" />		<meta property="og:image" content="https://yasm.com/wiki/en/img/yasm-frameworks/fitsm/fitsm-process-templates-yasm.jpg" />
	<meta property="og:image:width" content="1200" />		<meta property="og:image:width" content="1200" />
	<meta property="og:image:height" content="900" />		<meta property="og:image:height" content="900" />
	~~<meta name="twitter:card" content="summary_large_image">~~
	~~<meta name="twitter:site" content="@yasmcom">~~
	~~<meta name="twitter:creator" content="@yasmcom">~~
	~~<meta name="twitter:title" content="FitSM und YaSM">~~
	<meta name="twitter:description" content="While FitSM includes documents with requirements and supporting guidance, YaSM provides a ready-to-use process model for service management in popular formats, such as Visio and ARIS.">
	~~<meta name="twitter:image" content="https://yasm.com/wiki/en/img/yasm-frameworks/fitsm/fitsm-process-templates-yasm.jpg">~~
	<meta name="twitter:image:alt" content="The differences between FitSM and YaSM service management: FitSM processes / process-specific requirements and corresponding processes and templates from the YaSM process model.">
	<link href="https://plus.google.com/104150539756444616711/posts" rel="publisher" />		<link href="https://plus.google.com/104150539756444616711/posts" rel="publisher" />
	<meta name="pinterest-rich-pin" content="false" />		<meta name="pinterest-rich-pin" content="false" />

Stefan: Renamed process: SP8: Ensure continuity.

2023-11-12T15:12:08Z

Renamed process: SP8: Ensure continuity.

← Older revision		Revision as of 17:12, 12 November 2023
Line 151:		Line 151:
	* [[LP4: Operate the services]]		* [[LP4: Operate the services]]
	* [[LP5: Improve the services]]		* [[LP5: Improve the services]]
	* [[SP8: ~~Prepare for disaster events~~]]		* [[SP8: Ensure continuity]]
	YaSM document templates:		YaSM document templates:
	* Service definition		* Service definition
	* Service quality report		* Service quality report
	* Service improvement plan		* Service improvement plan
	* Register of managed ~~disaster~~ events		* Register of managed critical events
	* Service continuity plan		* Service continuity plan
	\|		\|
Line 163:		Line 163:
	* The service operation process performs routine operational tasks to ensure service availability and monitors actual availability levels.		* The service operation process performs routine operational tasks to ensure service availability and monitors actual availability levels.
	* This allows the service improvement process to initiate corrective action if availability must be enhanced.		* This allows the service improvement process to initiate corrective action if availability must be enhanced.
	* YaSM includes a specific supporting process to ensure service continuity in the case of ~~disaster~~ events. This process includes activities to identify continuity risks and create continuity plans.		* YaSM includes a specific supporting process to ensure service continuity in the case of critical, disruptive events. This process includes activities to identify continuity risks and create continuity plans.
	* See also: [[Availability Management\|Availability management]] in YaSM		* See also: [[Availability Management\|Availability management]] in YaSM
	\|-style="vertical-align:top"		\|-style="vertical-align:top"

Andrea at 10:26, 30 September 2023

2023-09-30T10:26:55Z

← Older revision		Revision as of 12:26, 30 September 2023
Line 49:		Line 49:
	<meta itemprop="keywords" content="FitSM process templates" />		<meta itemprop="keywords" content="FitSM process templates" />
	<meta itemprop="keywords" content="FitSM process model" />		<meta itemprop="keywords" content="FitSM process model" />
	<img style="margin:0px ~~0px 20px~~ 20px; float:right;" srcset="https://yasm.com/wiki/en/img/yasm-frameworks/fitsm/480px/fitsm-process-templates-yasm.jpg 480w, https://yasm.com/wiki/en/img/yasm-frameworks/fitsm/fitsm-process-templates-yasm.jpg 1200w" sizes="100vw" src="https://yasm.com/wiki/en/img/yasm-frameworks/fitsm/fitsm-process-templates-yasm.jpg" width="480" height="360" title="Comparison: FitSM and YaSM service management templates" alt="While FitSM includes documents with requirements and supporting guidance, YaSM provides a ready-to-use process model for service management in popular formats, such as Visio and ARIS." /></a>		<img style="margin:5px 0px 15px 20px; float:right;" srcset="https://yasm.com/wiki/en/img/yasm-frameworks/fitsm/480px/fitsm-process-templates-yasm.jpg 480w, https://yasm.com/wiki/en/img/yasm-frameworks/fitsm/fitsm-process-templates-yasm.jpg 1200w" sizes="100vw" src="https://yasm.com/wiki/en/img/yasm-frameworks/fitsm/fitsm-process-templates-yasm.jpg" width="480" height="360" title="Comparison: FitSM and YaSM service management templates" alt="While FitSM includes documents with requirements and supporting guidance, YaSM provides a ready-to-use process model for service management in popular formats, such as Visio and ARIS." /></a>
	<div class="thumbcaption" style="margin:0px 0px 20px 20px"><span style="font-variant:small-caps;"><b>Fig. 1: FitSM requirements vs. YaSM process templates</b></span></div></div></div></html>		<div class="thumbcaption" style="margin:0px 0px 20px 20px"><span style="font-variant:small-caps;"><b>Fig. 1: FitSM requirements vs. YaSM process templates</b></span></div></div></div></html>

Line 57:		Line 57:
	==The difference between FitSM and YaSM==		==The difference between FitSM and YaSM==

	While FitSM defines requirements for 14 core ITSM processes, the YaSM model includes 19 processes that are fully aligned with [[ISO 20000]], the international standard for service management. So in comparison, there is a very good match between the FitSM processes and the YaSM service management model, and YaSM covers some additional topics.		While FitSM defines requirements for 14 core ITSM processes, the YaSM model includes [[Service Management Processes\|19 processes]] that are fully aligned with [[ISO 20000]], the international standard for service management. So in comparison, there is a very good match between the FitSM processes and the YaSM service management model, and YaSM covers some additional topics.

	A key difference between FitSM and YaSM is the type of content provided:		A key difference between FitSM and YaSM is the type of content provided:
Line 63:		Line 63:
	<li>FitSM includes documents with requirements for a service management system (SMS) and additional guidance, such as process objectives and recommended high-level activities.</li>		<li>FitSM includes documents with requirements for a service management system (SMS) and additional guidance, such as process objectives and recommended high-level activities.</li>
	<li>YaSM makes such high-level content available in the free YaSM Service Management Wiki.</li>		<li>YaSM makes such high-level content available in the free YaSM Service Management Wiki.</li>
	<li>But YaSM also offers the <a href="https://yasm.com/en/products/yasm-process-map" title="YaSM Process Map - the service management process modell">YaSM Process Map</a>, a complete and detailed set of process and document templates. <a href="https://yasm.com/en/products/yasm-process-map-visio" title="YaSM Process Map for Visio"> These service management templates are available in popular formats, such as Visio</a><sup><small>®</small></sup>, Word™, Excel<sup><small>®</small></sup>, ~~and also~~ as a <a href="https://yasm.com/en/products/yasm-process-map-aris" title="YaSM Process Map for ARIS">reference model for the ARIS Process Platform</a>™. The templates are fully editable, allowing organizations to design tailor-made processes without having to start from nothing.</li></ul></html>		<li>But YaSM also offers the <a href="https://yasm.com/en/products/yasm-process-map" title="YaSM Process Map - the service management process modell">YaSM Process Map</a>, a complete and detailed set of process and document templates.
			<ul><li><a href="https://yasm.com/en/products/yasm-process-map-visio" title="YaSM Process Map for Visio"> These service management templates are available in popular formats, such as Visio</a><sup><small>®</small></sup>, Word™, Excel<sup><small>®</small></sup>,</li>
			<li><a href="https://yasm.com/en/products/yasm-process-map-bic" title="YaSM Process Map for the BIC Platform">a process model for BIC / BIC Process Design</a>®,</li>
			<li>as a <a href="https://yasm.com/en/products/yasm-process-map-aris" title="YaSM Process Map for ARIS">reference model for the ARIS Process Platform</a>™.</li>
			<li>and also as <a href="https://yasm.com/en/products/service-management-templates-bpmn-xml" title="Service management templates in BPMN XML">BPMN XML documents</a>.</li></ul><li>
			<li>The templates are fully editable, allowing organizations to design tailor-made processes without having to start from nothing.</li></ul></html>

	==FitSM requirements and YaSM==		==FitSM requirements and YaSM==
Line 80:		Line 85:

	Organizations are also required to implement a PDCA (Plan-Do-Check-Act) cycle, an iterative, four-stage approach for continually improving processes, products or services that is also known as the Deming cycle. This concept is well aligned with the service lifecycle that is a key feature of the YaSM process model.		Organizations are also required to implement a PDCA (Plan-Do-Check-Act) cycle, an iterative, four-stage approach for continually improving processes, products or services that is also known as the Deming cycle. This concept is well aligned with the service lifecycle that is a key feature of the YaSM process model.
			<p> </p>

	====Process-specific FitSM requirements====		====Process-specific FitSM requirements====
Line 86:		Line 92:
	<p> </p>		<p> </p>

	In the table below, we use the list of FitSM processes and related YaSM process and document templates to illustrate how the YaSM process model is a good starting point for all organizations that seek to introduce the FitSM processes:		In the table below, we use the list of FitSM processes and related YaSM process templates and [[Service Management Checklists\|document templates]] to illustrate how the YaSM process model is a good starting point for all organizations that seek to introduce the FitSM processes:
	<p> </p>		<p> </p>

	{\| class="wikitable" style="background: white;"		{\| class="wikitable" style="background: white;"
	\|+style="background:#~~379988~~; color:#ffffff;" colspan="3"\|<h4>FitSM requirements and related YaSM processes and templates</h4>		\|+style="background:#465674; color:#ffffff;" colspan="3"\|<h4>FitSM requirements and related YaSM processes and templates</h4>
	\|-		\|-style="vertical-align:top"
	!style="background:#eeeeee;"\|FitSM processes and related process-specific requirements		!style="background:#eeeeee; text-align:left;"\|FitSM processes and related process-specific requirements
	!style="background:#eeeeee;"\|Related YaSM processes and templates		!style="background:#eeeeee; text-align:left;"\|Related YaSM processes and templates
	!style="background:#eeeeee;"\|Comparison: YaSM service management and FitSM		!style="background:#eeeeee; text-align:left;"\|Comparison: YaSM service management and FitSM
	\|-style="vertical-align:top"		\|-style="vertical-align:top"
	\|PR1: Service portfolio management		\|PR1: Service portfolio management
Line 334:		Line 340:
	#Specific roles are generic roles interpreted in the context of a particular service management process. For example, in the context of incident and service request management (ISRM), the generic role of process manager becomes the "ISRM process manager", who ensures that all incidents are recorded and resolved within target resolution times.		#Specific roles are generic roles interpreted in the context of a particular service management process. For example, in the context of incident and service request management (ISRM), the generic role of process manager becomes the "ISRM process manager", who ensures that all incidents are recorded and resolved within target resolution times.

	The YaSM model does not distinguish between generic and specific roles, but describes a streamlined set of [[YaSM Roles\|service management roles]] that is aligned with the popular frameworks like ITIL. In the context of incident and service request management, for example, YaSM uses the roles of incident manager, 1st level support, 2nd level support, etc.		The YaSM model does not distinguish between generic and specific roles, but describes a streamlined set of [[YaSM Roles\|service management roles]] that is aligned with the popular frameworks like ITIL. In the context of incident and service request management, for example, YaSM uses the roles of [[YaSM_Roles#Incident-manager\|incident manager]], [[YaSM_Roles#1st-level-support\|1st level support]], [[YaSM_Roles#2nd-level-support\|2nd level support]], etc.

	So the role names in FitSM and YaSM are not exactly the same. A closer look at the role definitions, however, suggests that FitSM and YaSM have the same idea of which roles are needed to perform ITSM effectively.		So the role names in FitSM and YaSM are not exactly the same. A closer look at the role definitions, however, suggests that FitSM and YaSM have the same idea of which roles are needed to perform ITSM effectively.
Line 350:		Line 356:
	* Process definition.		* Process definition.

	The YaSM model includes Word™ documents that are similar to the FitSM templates, and many more: There are some 90 YaSM document templates for all documents created in the service management processes.		The YaSM model includes Word™ documents (see examples: '[[Service Management Checklists\|service management checklists]]') that are similar to the FitSM templates, and many more: There are some 90 YaSM document templates for all documents created in the service management processes.

	or a complete list of YaSM templates, please refer to the [[YaSM Glossary]] und im [[YaSM_Data_Model\|YaSM data object model]].		For a complete list of YaSM templates, please refer to the [[YaSM Glossary]] und im [[YaSM_Data_Model\|YaSM data object model]].
	<p> </p>		<p> </p>

Andrea at 14:03, 25 December 2022

2022-12-25T14:03:01Z

← Older revision		Revision as of 16:03, 25 December 2022
Line 5:		Line 5:
	<meta property="og:title" content="FitSM and YaSM \| YaSM Service Management Wiki" />		<meta property="og:title" content="FitSM and YaSM \| YaSM Service Management Wiki" />
	<meta property="og:description" content="While FitSM includes documents with requirements and supporting guidance, YaSM provides a ready-to-use process model for service management in popular formats, such as Visio and ARIS." />		<meta property="og:description" content="While FitSM includes documents with requirements and supporting guidance, YaSM provides a ready-to-use process model for service management in popular formats, such as Visio and ARIS." />
	<meta property="og:site_name" content="YaSM">		<meta property="og:site_name" content="YaSM Service Management">
	<meta property="og:type" content="article" />		<meta property="og:type" content="article" />
	<meta property="article:publisher" content="https://www.facebook.com/yasmcom" />		<meta property="article:publisher" content="https://www.facebook.com/yasmcom" />
Line 63:		Line 63:
	<li>FitSM includes documents with requirements for a service management system (SMS) and additional guidance, such as process objectives and recommended high-level activities.</li>		<li>FitSM includes documents with requirements for a service management system (SMS) and additional guidance, such as process objectives and recommended high-level activities.</li>
	<li>YaSM makes such high-level content available in the free YaSM Service Management Wiki.</li>		<li>YaSM makes such high-level content available in the free YaSM Service Management Wiki.</li>
	<li>But YaSM also offers the <a href="https://yasm.com/en/products/yasm-process-map" title="YaSM Process Map - the service management process modell">YaSM Process Map</a>, a complete and detailed set of process and document templates. <a href="https://yasm.com/en/products/yasm-process-map-visio" title="YaSM Process Map for Visio"> These service management templates are available in popular formats, such as Visio</a><sup><small>®</small></sup>, Word™, Excel<sup><small>®</small></sup>, and also as a <a href="https://yasm.com/de/~~produkte~~/yasm-~~prozesslandkarte~~-aris" title="YaSM~~-Prozesslandkarte für~~ ARIS">reference model for the ARIS Process Platform</a>™. The templates are fully editable, allowing organizations to design tailor-made processes without having to start from nothing.</li></ul></html>		<li>But YaSM also offers the <a href="https://yasm.com/en/products/yasm-process-map" title="YaSM Process Map - the service management process modell">YaSM Process Map</a>, a complete and detailed set of process and document templates. <a href="https://yasm.com/en/products/yasm-process-map-visio" title="YaSM Process Map for Visio"> These service management templates are available in popular formats, such as Visio</a><sup><small>®</small></sup>, Word™, Excel<sup><small>®</small></sup>, and also as a <a href="https://yasm.com/en/products/yasm-process-map-aris" title="YaSM Process Map for ARIS">reference model for the ARIS Process Platform</a>™. The templates are fully editable, allowing organizations to design tailor-made processes without having to start from nothing.</li></ul></html>

	==FitSM requirements and YaSM==		==FitSM requirements and YaSM==
Line 356:		Line 356:

	==Related articles==		==Related articles==

	<html><a href="https://yasm.com/wiki/en/index.php/FitSM"><img src="https://yasm.com/wiki/en/img/yasm-frameworks/fitsm/480px/fitsm-parts-documents-core-standard-implementation.jpg" title="What is FitSM?" alt="The FitSM components (FitSM parts): Core standard and implementation aids." style="display: block; float: left; margin-right: 15px" width="320" height="240"/></a>		<html><a href="https://yasm.com/wiki/en/index.php/FitSM"><img src="https://yasm.com/wiki/en/img/yasm-frameworks/fitsm/480px/fitsm-parts-documents-core-standard-implementation.jpg" title="What is FitSM?" alt="The FitSM components (FitSM parts): Core standard and implementation aids." style="display: block; float: left; margin-right: 15px" width="320" height="240"/></a>
	<div style="margin-left: 5%; color:#636363">		<div style="margin-left: 5%; color:#636363">
	<p style="margin-top: 0; word-wrap:normal;"><a href="https://yasm.com/wiki/en/index.php/FitSM">A short introduction to FitSM</a></p>		<p style="margin-top: 0; word-wrap:normal;"><a href="https://yasm.com/wiki/en/index.php/FitSM">A short introduction to FitSM</a></p>
	<p>What is FitSM (Federated IT Service Management), and what components and documents are included in this lightweight family of standards for implementing IT service management (ITSM)? <a href="https://yasm.com/wiki/en/index.php/FitSM">[...]</a></p></div></html>		<p>What is FitSM (Federated IT Service Management), and what components and documents are included in this lightweight family of standards for implementing IT service management (ITSM)? <a href="https://yasm.com/wiki/en/index.php/FitSM">[...]</a></p></div></html>
			<br style="clear:both;"/>

			==Video==
			<html><a href="https://yasm.com/en/videos/fitsm-lightweight-process-model-yasm"><img src="https://yasm.com/en/content/videos/fitsm-lightweight-process-model-yasm/480px/fitsm-lightweight-service-management-yasm-video.jpg" title="Video: What is FitSM?" alt="What is FitSM (Federated IT Service Management), the lightweight standard for ITSM? How does FitSM help organizations improve their service management practices?" style="display: block; float: left; margin-right: 15px" width="320" height="240"/></a>
			<div style="margin-left: 5%; color:#636363">
			<p style="margin-top: 0; word-wrap:normal;"><a href="https://yasm.com/de/videos/fitsm-lightweight-prozessmodell-yasm">FitSM - Lightweight service management</a></p>
			<p>What components and documents does FitSM include? What are the similarities and differences between FitSM and YaSM service management?</p>
			<p>Start the video: <a href="https://yasm.com/en/videos/fitsm-lightweight-process-model-yasm" title="Start video: What is FitSM?">Introduction to FitSM</a> (8:20 Min.)</p></div></html>
	<br style="clear:both;"/>		<br style="clear:both;"/>
	<p> </p>		<p> </p>
Line 396:		Line 403:
	<meta itemprop="alternativeHeadline" content="FitSM processes and YaSM processes" />		<meta itemprop="alternativeHeadline" content="FitSM processes and YaSM processes" />
	<link itemprop="url" href="https://yasm.com/wiki/en/index.php/FitSM_and_YaSM" />		<link itemprop="url" href="https://yasm.com/wiki/en/index.php/FitSM_and_YaSM" />
	~~<time itemprop="dateModified" datetime="2022-11-22"></time>~~
	<link itemprop="primaryImageOfPage" href="https://yasm.com/wiki/en/img/yasm-frameworks/fitsm/fitsm-process-templates-yasm.jpg" />		<link itemprop="primaryImageOfPage" href="https://yasm.com/wiki/en/img/yasm-frameworks/fitsm/fitsm-process-templates-yasm.jpg" />
	<meta itemprop="inLanguage" content="en" />		<meta itemprop="inLanguage" content="en" />

Andrea at 10:26, 3 October 2022

2022-10-03T10:26:36Z

← Older revision		Revision as of 12:26, 3 October 2022
Line 32:		Line 32:
	<p> </p>		<p> </p>

	<html><div itemid="https://yasm.com/wiki/en/img/yasm-frameworks/fitsm/fitsm-process-templates-yasm.jpg" itemscope itemtype="https://schema.org/ImageObject">		<html><div style="float:right;"><div itemid="https://yasm.com/wiki/en/img/yasm-frameworks/fitsm/fitsm-process-templates-yasm.jpg" itemscope itemtype="https://schema.org/ImageObject">
	<a href="https://yasm.com/wiki/en/img/yasm-frameworks/fitsm/fitsm-process-templates-yasm.jpg" title="Comparison: FitSM and YaSM service management templates" itemprop="contentUrl">		<a href="https://yasm.com/wiki/en/img/yasm-frameworks/fitsm/fitsm-process-templates-yasm.jpg" title="Comparison: FitSM and YaSM service management templates" itemprop="contentUrl">
	<meta itemprop="caption" content="FitSM requirements vs. YaSM process templates" />		<meta itemprop="caption" content="FitSM requirements vs. YaSM process templates" />
	<meta itemprop="width" content="1200" />		<meta itemprop="width" content="1200" />
	<meta itemprop="height" content="900" />		<meta itemprop="height" content="900" />
			<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-frameworks/fitsm/480px/fitsm-process-templates-yasm.jpg" />
			<meta itemprop="width" content="480" />
			<meta itemprop="height" content="360" />
			<meta itemprop="dateCreated" content="2022-10-02" />
			<meta itemprop="datePublished" content="2022-10-02" />
			</span>
	<meta itemprop="dateCreated" content="2021-12-14" />		<meta itemprop="dateCreated" content="2021-12-14" />
	<meta itemprop="datePublished" content="2021-12-25" />		<meta itemprop="datePublished" content="2021-12-25" />
	<meta itemprop="keywords" content="FitSM process templates" />		<meta itemprop="keywords" content="FitSM process templates" />
	<meta itemprop="keywords" content="FitSM process model" />		<meta itemprop="keywords" content="FitSM process model" />
	<img style="margin:0px 0px ~~30px 30px~~; float:right;" src="https://yasm.com/wiki/en/img/yasm-frameworks/fitsm/fitsm-process-templates-yasm.jpg" width="480" height="360" title="Comparison: FitSM and YaSM service management templates" alt="While FitSM includes documents with requirements and supporting guidance, YaSM provides a ready-to-use process model for service management in popular formats, such as Visio and ARIS." /></a></div></html>		<img style="margin:0px 0px 20px 20px; float:right;" srcset="https://yasm.com/wiki/en/img/yasm-frameworks/fitsm/480px/fitsm-process-templates-yasm.jpg 480w, https://yasm.com/wiki/en/img/yasm-frameworks/fitsm/fitsm-process-templates-yasm.jpg 1200w" sizes="100vw" src="https://yasm.com/wiki/en/img/yasm-frameworks/fitsm/fitsm-process-templates-yasm.jpg" width="480" height="360" title="Comparison: FitSM and YaSM service management templates" alt="While FitSM includes documents with requirements and supporting guidance, YaSM provides a ready-to-use process model for service management in popular formats, such as Visio and ARIS." /></a>
			<div class="thumbcaption" style="margin:0px 0px 20px 20px"><span style="font-variant:small-caps;"><b>Fig. 1: FitSM requirements vs. YaSM process templates</b></span></div></div></div></html>

	__TOC__		__TOC__
Line 68:		Line 77:
	* the outputs of all service management processes are documented.		* the outputs of all service management processes are documented.

	Many of these requirements are addressed in the YaSM process [[SP1:~~_Set_up_and_maintain_the_service_management_system~~]].		Many of these requirements are addressed in the YaSM process [[SP1: Set up and maintain the service management system]].

	Organizations are also required to implement a PDCA (Plan-Do-Check-Act) cycle, an iterative, four-stage approach for continually improving processes, products or services that is also known as the Deming cycle. This concept is well aligned with the service lifecycle that is a key feature of the YaSM process model.		Organizations are also required to implement a PDCA (Plan-Do-Check-Act) cycle, an iterative, four-stage approach for continually improving processes, products or services that is also known as the Deming cycle. This concept is well aligned with the service lifecycle that is a key feature of the YaSM process model.
Line 325:		Line 334:
	#Specific roles are generic roles interpreted in the context of a particular service management process. For example, in the context of incident and service request management (ISRM), the generic role of process manager becomes the "ISRM process manager", who ensures that all incidents are recorded and resolved within target resolution times.		#Specific roles are generic roles interpreted in the context of a particular service management process. For example, in the context of incident and service request management (ISRM), the generic role of process manager becomes the "ISRM process manager", who ensures that all incidents are recorded and resolved within target resolution times.

	The YaSM model does not distinguish between generic and specific roles, but describes a [[YaSM Roles\|~~streamlined set of~~ roles]] that is aligned with the popular ~~service management~~ frameworks like ITIL. In the context of incident and service request management, for example, YaSM uses the roles of incident manager, 1st level support, 2nd level support, etc.		The YaSM model does not distinguish between generic and specific roles, but describes a streamlined set of [[YaSM Roles\|service management roles]] that is aligned with the popular frameworks like ITIL. In the context of incident and service request management, for example, YaSM uses the roles of incident manager, 1st level support, 2nd level support, etc.

	So the role names in FitSM and YaSM are not exactly the same. A closer look at the role definitions, however, suggests that FitSM and YaSM have the same idea of which roles are needed to perform ITSM effectively.		So the role names in FitSM and YaSM are not exactly the same. A closer look at the role definitions, however, suggests that FitSM and YaSM have the same idea of which roles are needed to perform ITSM effectively.
Line 348:		Line 357:
	==Related articles==		==Related articles==

	<html><a href="https://yasm.com/wiki/en/index.php/FitSM"><img src="https://yasm.com/wiki/en/img/yasm-frameworks/fitsm/~~16x9~~/fitsm-parts-documents-core-standard-implementation.jpg" title="What is FitSM?" alt="The FitSM components (FitSM parts): Core standard and implementation ~~aides~~." style="display: block; float: left~~; margin-left: 10px~~; margin-right: ~~20px~~" width="320" height="~~180~~"/></a>		<html><a href="https://yasm.com/wiki/en/index.php/FitSM"><img src="https://yasm.com/wiki/en/img/yasm-frameworks/fitsm/480px/fitsm-parts-documents-core-standard-implementation.jpg" title="What is FitSM?" alt="The FitSM components (FitSM parts): Core standard and implementation aids." style="display: block; float: left; margin-right: 15px" width="320" height="240"/></a>
	<div style="margin-left: 5%; color:#636363">		<div style="margin-left: 5%; color:#636363">
	<p style="margin-top: 0; word-wrap:normal;"><a href="https://yasm.com/wiki/en/index.php/FitSM">A short introduction to FitSM</a></p>		<p style="margin-top: 0; word-wrap:normal;"><a href="https://yasm.com/wiki/en/index.php/FitSM">A short introduction to FitSM</a></p>
	<p>What is FitSM, and what components and documents are included in this lightweight family of standards for implementing IT service management (ITSM)? <a href="https://yasm.com/wiki/en/index.php/FitSM">[...]</a></p></div></html>		<p>What is FitSM (Federated IT Service Management), and what components and documents are included in this lightweight family of standards for implementing IT service management (ITSM)? <a href="https://yasm.com/wiki/en/index.php/FitSM">[...]</a></p></div></html>
	<br style="clear:both;"/>		<br style="clear:both;"/>
	<p> </p>		<p> </p>
Line 387:		Line 396:
	<meta itemprop="alternativeHeadline" content="FitSM processes and YaSM processes" />		<meta itemprop="alternativeHeadline" content="FitSM processes and YaSM processes" />
	<link itemprop="url" href="https://yasm.com/wiki/en/index.php/FitSM_and_YaSM" />		<link itemprop="url" href="https://yasm.com/wiki/en/index.php/FitSM_and_YaSM" />
			<time itemprop="dateModified" datetime="2022-11-22"></time>
	<link itemprop="primaryImageOfPage" href="https://yasm.com/wiki/en/img/yasm-frameworks/fitsm/fitsm-process-templates-yasm.jpg" />		<link itemprop="primaryImageOfPage" href="https://yasm.com/wiki/en/img/yasm-frameworks/fitsm/fitsm-process-templates-yasm.jpg" />
	<meta itemprop="inLanguage" content="en" />		<meta itemprop="inLanguage" content="en" />

Andrea: Created page with "FitSM and YaSM | YaSM Service Management Wiki
2021-12-26T12:31:23Z

Created page with "<itpmch><title>FitSM and YaSM | YaSM Service Management Wiki</title> <meta name="keywords" content="fitsm processes, fitsm templates, fitsm process model" /> <meta name="descr..."

New page
<itpmch><title>FitSM and YaSM | YaSM Service Management Wiki</title>
<meta name="keywords" content="fitsm processes, fitsm templates, fitsm process model" />
<meta name="description" content="While FitSM includes documents with requirements and supporting guidance, YaSM provides a ready-to-use process model for service management in popular formats, such as Visio and ARIS." />
<meta property="og:url" content="https://yasm.com/wiki/en/index.php/FitSM_and_YaSM" />
<meta property="og:title" content="FitSM and YaSM | YaSM Service Management Wiki" />
<meta property="og:description" content="While FitSM includes documents with requirements and supporting guidance, YaSM provides a ready-to-use process model for service management in popular formats, such as Visio and ARIS." />
<meta property="og:site_name" content="YaSM">
<meta property="og:type" content="article" />
<meta property="article:publisher" content="https://www.facebook.com/yasmcom" />
<meta property="fb:admins" content="100002035253209" />
<meta property="fb:admins" content="100002592864414" />
<meta property="og:image" content="https://yasm.com/wiki/en/img/yasm-frameworks/fitsm/fitsm-process-templates-yasm.jpg" />
<meta property="og:image:width" content="1200" />
<meta property="og:image:height" content="900" />
<meta name="twitter:card" content="summary_large_image">
<meta name="twitter:site" content="@yasmcom">
<meta name="twitter:creator" content="@yasmcom">
<meta name="twitter:title" content="FitSM und YaSM">
<meta name="twitter:description" content="While FitSM includes documents with requirements and supporting guidance, YaSM provides a ready-to-use process model for service management in popular formats, such as Visio and ARIS.">
<meta name="twitter:image" content="https://yasm.com/wiki/en/img/yasm-frameworks/fitsm/fitsm-process-templates-yasm.jpg">
<meta name="twitter:image:alt" content="The differences between FitSM and YaSM service management: FitSM processes / process-specific requirements and corresponding processes and templates from the YaSM process model.">
<link href="https://plus.google.com/104150539756444616711/posts" rel="publisher" />
<meta name="pinterest-rich-pin" content="false" />
</itpmch>
<html><div class="noresize"><a href="https://yasm.com/wiki/de/index.php/FitSM_und_YaSM"><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> 
 
Comparison: YaSM and FitSM
Part of: <a href="https://yasm.com/wiki/en/index.php/What_is_YaSM#yasm-other-service-management-frameworks" title="YaSM and other service management frameworks and standards">YaSM vs. other service management frameworks and standards</a></html>
 

Both [[FitSM]] and [[What is YaSM|YaSM]] have their roots in the popular and time-tested service management frameworks such as [[ITIL]]®, and aim to provide clear and pragmatic advice for organizations that wish to improve the [[Service Management|management of their services]].
 

<html><div itemid="https://yasm.com/wiki/en/img/yasm-frameworks/fitsm/fitsm-process-templates-yasm.jpg" itemscope itemtype="https://schema.org/ImageObject">
<a href="https://yasm.com/wiki/en/img/yasm-frameworks/fitsm/fitsm-process-templates-yasm.jpg" title="Comparison: FitSM and YaSM service management templates" itemprop="contentUrl">
<meta itemprop="caption" content="FitSM requirements vs. YaSM process templates" />
<meta itemprop="width" content="1200" />
<meta itemprop="height" content="900" />
<meta itemprop="dateCreated" content="2021-12-14" />
<meta itemprop="datePublished" content="2021-12-25" />
<meta itemprop="keywords" content="FitSM process templates" />
<meta itemprop="keywords" content="FitSM process model" />
<img style="margin:0px 0px 30px 30px; float:right;" src="https://yasm.com/wiki/en/img/yasm-frameworks/fitsm/fitsm-process-templates-yasm.jpg" width="480" height="360" title="Comparison: FitSM and YaSM service management templates" alt="While FitSM includes documents with requirements and supporting guidance, YaSM provides a ready-to-use process model for service management in popular formats, such as Visio and ARIS." /></a></div></html>

TOC
 

==The difference between FitSM and YaSM==

While FitSM defines requirements for 14 core ITSM processes, the YaSM model includes 19 processes that are fully aligned with [[ISO 20000]], the international standard for service management. So in comparison, there is a very good match between the FitSM processes and the YaSM service management model, and YaSM covers some additional topics.

A key difference between FitSM and YaSM is the type of content provided:
<html><ul>
<li>FitSM includes documents with requirements for a service management system (SMS) and additional guidance, such as process objectives and recommended high-level activities.</li>
<li>YaSM makes such high-level content available in the free YaSM Service Management Wiki.</li>
<li>But YaSM also offers the <a href="https://yasm.com/en/products/yasm-process-map" title="YaSM Process Map - the service management process modell">YaSM Process Map</a>, a complete and detailed set of process and document templates. <a href="https://yasm.com/en/products/yasm-process-map-visio" title="YaSM Process Map for Visio"> These service management templates are available in popular formats, such as Visio</a>®, Word™, Excel®, and also as a <a href="https://yasm.com/de/produkte/yasm-prozesslandkarte-aris" title="YaSM-Prozesslandkarte für ARIS">reference model for the ARIS Process Platform</a>™. The templates are fully editable, allowing organizations to design tailor-made processes without having to start from nothing.</li></ul></html>

==FitSM requirements and YaSM==

====General FitSM requirements for a service management system (SMS)====

The first set of FitSM requirements focuses on the general aspects of planning and implementing an effective service management system (see FitSM-1: Requirements / Section 5: General requirements for a service management system).

For example, FitSM requires that
* top management is committed to planning, implementing and operating a service management system
* service management scope, goals and policies are documented and communicated
* service management processes are defined and documented, including inputs, activities, outputs and responsibilities
* the outputs of all service management processes are documented.

Many of these requirements are addressed in the YaSM process [[SP1:_Set_up_and_maintain_the_service_management_system]].

Organizations are also required to implement a PDCA (Plan-Do-Check-Act) cycle, an iterative, four-stage approach for continually improving processes, products or services that is also known as the Deming cycle. This concept is well aligned with the service lifecycle that is a key feature of the YaSM process model.

====Process-specific FitSM requirements====

The second set of FitSM requirements defines specific requirements for each of the 14 FitSM processes (see FitSM-1: Requirements / Section 6: Process-specific requirements).
 

In the table below, we use the list of FitSM processes and related YaSM process and document templates to illustrate how the YaSM process model is a good starting point for all organizations that seek to introduce the FitSM processes:
 

{| class="wikitable" style="background: white;"
|+style="background:#379988; color:#ffffff;" colspan="3"|<h4>FitSM requirements and related YaSM processes and templates</h4>
|-
!style="background:#eeeeee;"|FitSM processes and related process-specific requirements
!style="background:#eeeeee;"|Related YaSM processes and templates
!style="background:#eeeeee;"|Comparison: YaSM service management and FitSM
|-style="vertical-align:top"
|PR1: Service portfolio management
|
YaSM process templates:
* [[SP2: Maintain the service portfolio]]
* [[LP2: Design new or changed services]]
YaSM document templates:
* Service portfolio
* Service definition
* Service implementation blueprint
|
* The YaSM model includes a process for maintaining the service portfolio. This process ensures the information in the service portfolio and the related service definitions are an accurate representation of the services managed by the service provider.
* Detailed service specifications are created in the YaSM process for service design. This process also includes activities for planning the transition of new or changed services.
|-style="vertical-align:top"
|PR2: Service level management
|
YaSM process templates:
* [[LP2: Design new or changed services]]
* [[LP5: Improve the services]]
* [[SP2: Maintain the service portfolio]]
* [[SP3: Manage customer relationships|SP3: Manage customer relationships]]
YaSM document templates:
* Service portfolio
* Service definition
* Customer service agreement
* Service improvement plan
|
* While FitSM defines service level management as a process of its own, YaSM takes the view that service levels are one aspect of the services that needs to be considered in the service lifecycle processes and several supporting processes.
* For example, the YaSM process for maintaining the service portfolio is tasked with publishing service catalogs.
* The required service levels are defined during the service design stage.
* Customer relationship management ensures formal agreements are in place with customers.
* Regular service reviews are performed as part of YaSM's service improvement process. Where required service levels are not met, the necessary service improvements are managed and implemented through the service improvement plan.
* See also: [[Service Level Management|Service level management]] in YaSM
|-style="vertical-align:top"
|PR3: Service reporting management
|
YaSM process templates:
* [[LP4:_Operate_the_services#LP4.4|LP4.4: Produce service quality reports]]
YaSM document templates:
* Service quality report
|
* Service quality reports are produced on a regular basis as part of YaSM's service operation process. These reports identify areas where service quality does not meet the agreed service requirements.
|-style="vertical-align:top"
|PR4: Service availability and continuity management
|
YaSM process templates:
* [[LP2: Design new or changed services]]
* [[LP3: Build new or changed services]]
* [[LP4: Operate the services]]
* [[LP5: Improve the services]]
* [[SP8: Prepare for disaster events]]
YaSM document templates:
* Service definition
* Service quality report
* Service improvement plan
* Register of managed disaster events
* Service continuity plan
|
* The YaSM process model deals with service availability as an aspect of services that is to be managed through the service lifecycle processes:
* Availability requirements are defined during the service design stage.
* The service operation process performs routine operational tasks to ensure service availability and monitors actual availability levels.
* This allows the service improvement process to initiate corrective action if availability must be enhanced.
* YaSM includes a specific supporting process to ensure service continuity in the case of disaster events. This process includes activities to identify continuity risks and create continuity plans.
* See also: [[Availability Management|Availability management]] in YaSM
|-style="vertical-align:top"
|PR5: Capacity management
|
YaSM process templates:
* [[LP2: Design new or changed services]]
* [[LP3: Build new or changed services]]
* [[LP4: Operate the services]]
* [[LP5: Improve the services]]
YaSM document templates:
* Service definition
* Service quality report
* Service improvement plan
|
* The YaSM model deals with service capacity as an aspect of services that is to be managed through the service lifecycle processes:
* Capacity and performance requirements are defined during the service design stage.
* The service operation process performs routine operational tasks to ensure service capacity and performance and monitors actual capacity and performance levels.
* This allows the service improvement process to initiate corrective action if capacity or performance must be enhanced.
* See also: [Capacity Managemen|Capacity management]] in YaSM
|-style="vertical-align:top"
|PR6: Information security management
|
YaSM process templates:
* [[SP7: Ensure security]]
YaSM document templates:
* Register of security risks
* Security operation manual
* Test report
* Security review report
* Security improvement plan
|
* The security management process in YaSM develops and implements policies and procedures for protecting the service provider's assets.
Key activities in the process include identifying assets, vulnerabilities and threats, as well as setting up security controls to mitigate or eliminate those threats.
|-style="vertical-align:top"
|PR7: Customer relationship management
|
YaSM process templates:
* [[SP3: Manage customer relationships|SP3: Manage customer relationships]]
YaSM document templates:
* Customer portfolio
* Customer service agreement
* Service definition
* Complaint record
* Customer survey evaluation
* Customer meeting minutes
|
* YaSM's customer relationship management process is responsible for building and maintaining strong relationships between the service provider and its customers.
* This includes obtaining regular feedback from customers through customer meetings and surveys.
|-style="vertical-align:top"
|PR8: Supplier relationship management
|
YaSM process templates:
* [[SP11: Manage suppliers]]
YaSM document templates:
* Supplier portfolio
* External service agreement
* Service definition
* Supplier dispute record
* Supplier review report
|
* The supplier management process manages supplier performance and takes corrective action of contractual commitments are not fulfilled.
* This includes negotiating contracts with service providers, managing disputes and reviewing contracts on a regular basis.
|-style="vertical-align:top"
|PR9: Incident and service request management
|
YaSM process templates:
* [[LP4.6: Resolve incidents and service requests]]
YaSM document templates:
* Incident model
* Incident record
* Problem record
* Recovery plan
|
* The YaSM process for resolving incidents and service requests described in YaSM meets the requirements of the equivalent process in FitSM.
* Incidents and service requests are managed through the incident and service request resolution process, where incidents and service requests are registered, classified and prioritized.
* Actions taken to resolve incidents and service requests are documented in incident / service request records.
* Several other YaSM processes provide personnel involved in the incident and service request management with relevant information including known errors, workarounds, recovery plans and configuration information.
|-style="vertical-align:top"
|PR10: Problem management
|
YaSM process templates:
* [[LP4.7: Resolve problems]]
YaSM document templates:
* Problem record
* Incident model
* Recovery plan
|
* Problem management aims to identify, investigate and resolve problems, where a problem is the underlying cause of one or several (potential) incidents.
* Reactive problem management is concerned with solving problems in response to one or more incidents that have occurred in the past.
* Proactive problem management tries to prevent incidents from occurring in the first place.
|-style="vertical-align:top"
|PR11: Configuration management
|
YaSM process templates:
* [[SP4: Manage configuration information]]
YaSM document templates:
* CI record
* Configuration model
* Configuration audit report
|
* Configuration management in the YaSM model ensures configuration items (CIs) are identified, recorded, controlled and changes to CIs tracked in the CMDB.
* To this end, the process maintains a configuration model, which defines the types of CIs to be managed in the CMDB.
|-style="vertical-align:top"
|PR12: Change management
|
YaSM process templates:
* [[SP5: Assess and coordinate changes]]
YaSM document templates:
* Change record
* Change model
* Change assessment report
* Change schedule
* Post-implementation review report
|
* The YaSM process model includes a change assessment process to make sure modifications to the services and their underlying components are made only after careful consideration of risks and potential side-effects.
* This process includes activities for the registration, classification, assessment and approval of changes.
|-style="vertical-align:top"
|PR13: Release and deployment management
|
YaSM process templates:
* [[LP3: Build new or changed services]]
* [[LP5: Improve the services]]
YaSM document templates:
* Change schedule
* Service implementation blueprint
* Test script
* Test report
* Post-implementation review report
|
* YaSM provides several ways for the deployment of changes and releases:
* Changes required for new or substantially changed services are typically tested and deployed through the service build process.
* Changes on a minor scale, required for example to improve a service or resolve a problem, may be implemented through the service improvement process.
* This ensures the deployment of new or changed services and service components to the live environment is planned with all relevant parties, including affected customers.
* All new releases are built and tested prior to being deployed.
|-style="vertical-align:top"
|PR14: Continual service improvement management
|
YaSM process templates:
* [[LP5: Improve the services]]
* [[SP1: Set up and maintain the service management system|SP1: Set up and maintain the service mgmt. system]]
YaSM document templates:
* Service review report
* Service improvement plan
* Process model
* Process metric
* Process review report
* Process improvement plan
|
* YaSM's process for continual service improvement is in charge of identifying potentials for service improvement and managing service improvement initiatives.
* A consistent approach to improvement should also be applied to the service provider's processes. These activities are included in the process for maintaining the service management system.
|}
 

==FitSM process objectives and recommended activities vs. YaSM processes==

The FitSM process model includes 14 core processes for IT service management. For each process, FitSM describes, typically in the form of a one-page table:
* the process objectives
* activities for process setup
* process inputs
* activities during ongoing process execution
* process outputs.

(See FitSM-3: Objectives and activities).

<html>Users of the YaSM service management model will find this content in the YaSM process and document templates. For example, <a href="https://yasm.com/en/products/yasm-process-map-visio#Visio_diagrams" title="Diagrams as part of the YaSM Process Map for Visio">swim lane diagrams</a> show the inputs and outputs for each process. In addition, these diagrams illustrate which roles are responsible for the various process activities.</html>

As for the recommended process activities, where FitSM specifies some high-level activities, the YaSM process flows provide more detail and describe whole sequences of activities, including decisions to be made within the processes.

==FitSM role model vs. YaSM roles==

FitSM includes a model of roles that describes typical roles, their responsibilities and relationships (see FitSM-3: Recommended role model). For each role, FitSM provides a description and a list of typical tasks.

FitSM distinguishes between two types of roles: generic and specific roles:
#Generic roles generally exist in all service provider organizations. Examples of generic FitSM roles are SMS owner, service owner, process owner, process manager or case owner.
#Specific roles are generic roles interpreted in the context of a particular service management process. For example, in the context of incident and service request management (ISRM), the generic role of process manager becomes the "ISRM process manager", who ensures that all incidents are recorded and resolved within target resolution times.

The YaSM model does not distinguish between generic and specific roles, but describes a [[YaSM Roles|streamlined set of roles]] that is aligned with the popular service management frameworks like ITIL. In the context of incident and service request management, for example, YaSM uses the roles of incident manager, 1st level support, 2nd level support, etc.

So the role names in FitSM and YaSM are not exactly the same. A closer look at the role definitions, however, suggests that FitSM and YaSM have the same idea of which roles are needed to perform ITSM effectively.

In addition, the YaSM model includes a complete [[YaSM_RACI_Matrix|RACI matrix]] as a visual representation of all YaSM roles and their responsibilities in the [[Service Management Processes|YaSM service management processes]].

==FitSM templates and samples vs. YaSM process and document templates==

FitSM seeks to support organizations that wish to adopt the standard with ready-to-use templates and samples for important pieces of documentation. FitSM templates for processes and documents currently include:
* Service management policy
* Service portfolio / catalogue
* Service level agreement (SLA)
* Basic service report
* Service transition package
* Process definition.

The YaSM model includes Word™ documents that are similar to the FitSM templates, and many more: There are some 90 YaSM document templates for all documents created in the service management processes.

or a complete list of YaSM templates, please refer to the [[YaSM Glossary]] und im [[YaSM_Data_Model|YaSM data object model]].
 

==Related articles==

<html><a href="https://yasm.com/wiki/en/index.php/FitSM"><img src="https://yasm.com/wiki/en/img/yasm-frameworks/fitsm/16x9/fitsm-parts-documents-core-standard-implementation.jpg" title="What is FitSM?" alt="The FitSM components (FitSM parts): Core standard and implementation aides." style="display: block; float: left; margin-left: 10px; margin-right: 20px" width="320" height="180"/></a>
<div style="margin-left: 5%; color:#636363">
<a href="https://yasm.com/wiki/en/index.php/FitSM">A short introduction to FitSM</a>
What is FitSM, and what components and documents are included in this lightweight family of standards for implementing IT service management (ITSM)? <a href="https://yasm.com/wiki/en/index.php/FitSM">[...]</a></div></html>
 
 

==Notes and references==

This page features content from the [https://www.fitsm.eu/ FitSM website] published under a Creative Commons Attribution 4.0 International ([https://creativecommons.org/licenses/by/4.0/ CC BY 4.0]) license.
 

<html>By:  Stefan Kempter <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>  and  Andrea Kempter <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.
 




<a itemprop="item" href="https://yasm.com/wiki/en/index.php/FitSM_and_YaSM#The_difference_between_FitSM_and_YaSM"> The difference between FitSM and YaSM</a>
<meta itemprop="position" content="1" /> ›

<a itemprop="item" href="https://yasm.com/wiki/en/index.php/FitSM_and_YaSM#FitSM_requirements_and_YaSM"> FitSM requirements and YaSM</a>
<meta itemprop="position" content="2" /> ›

<a itemprop="item" href="https://yasm.com/wiki/en/index.php/FitSM_and_YaSM#FitSM_process_objectives_and_recommended_activities_vs._YaSM_processes"> FitSM process objectives and recommended activities vs. YaSM processes</a>
<meta itemprop="position" content="3" /> ›

<a itemprop="item" href="https://yasm.com/wiki/en/index.php/FitSM_and_YaSM#FitSM_role_model_vs._YaSM_roles"> FitSM role model vs. YaSM roles</a>
<meta itemprop="position" content="4" /> ›

<a itemprop="item" href="https://yasm.com/wiki/en/index.php/FitSM_and_YaSM#FitSM_templates_and_samples_vs._YaSM_process_and_document_templates"> FitSM templates and samples vs. YaSM process and document templates</a>
<meta itemprop="position" content="5" />



 
<meta itemprop="name Headline" content="FitSM and YaSM" />
<meta itemprop="alternativeHeadline" content="FitSM processes and YaSM processes" />
<link itemprop="url" href="https://yasm.com/wiki/en/index.php/FitSM_and_YaSM" />
<link itemprop="primaryImageOfPage" href="https://yasm.com/wiki/en/img/yasm-frameworks/fitsm/fitsm-process-templates-yasm.jpg" />
<meta itemprop="inLanguage" content="en" />
<link itemprop="citation" href="https://yasm.com/wiki/de/index.php/FitSM" />
<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" />
</html>


[[Category:Service management frameworks and standards]][[Category:FitSM]]