Enterprise Service Management (ESM) and YaSM: Difference between revisions

From YaSM Service Management Wiki
No edit summary
No edit summary
Line 1: Line 1:
<itpmch><title>Enterprise Service Management | YaSM Service Management Wiki</title>
<itpmch><title>Enterprise Service Management | YaSM Service Management Wiki</title>
<meta name="keywords" content="enterprise service management, esm, what is enterprise service management, enterprise service management framework, enterprise service management processes, enterprise service management vs. IT service management, esm vs. itsm" />
<meta name="keywords" content="enterprise service management, esm, what is enterprise service management, enterprise service management framework, enterprise service management processes, enterprise service management vs. IT service management, esm vs. itsm" />
<meta name="description" content="Enterprise service management (ESM) is an approach for providing value to customers in the form of services. ESM includes capabilities for designing, implementing, operating and improving services." />
<meta name="description" content="Enterprise service management (ESM) is a management discipline aimed at providing value to customers in the form of services. ESM includes capabilities for designing, implementing, operating and improving services." />
<meta property="og:url" content="https://yasm.com/wiki/en/index.php/Enterprise_Service_Management_(ESM)_and_YaSM" />
<meta property="og:url" content="https://yasm.com/wiki/en/index.php/Enterprise_Service_Management_(ESM)_and_YaSM" />
<meta property="og:title" content="Enterprise Service Management | YaSM Service Management Wiki" />
<meta property="og:title" content="Enterprise Service Management | YaSM Service Management Wiki" />
<meta property="og:description" content="Enterprise service management (ESM) is an approach for providing value to customers in the form of services. ESM includes capabilities for designing, implementing, operating and improving services." />
<meta property="og:description" content="Enterprise service management (ESM) is a management discipline aimed at providing value to customers in the form of services. ESM includes capabilities for designing, implementing, operating and improving services." />
<meta property="og:site_name" content="YaSM">
<meta property="og:site_name" content="YaSM">
<meta property="og:type" content="article" />  
<meta property="og:type" content="article" />  
Line 20: Line 20:
<meta name="twitter:creator" content="@yasmcom">
<meta name="twitter:creator" content="@yasmcom">
<meta name="twitter:title" content="Enterprise Service Management (ESM) and YaSM">
<meta name="twitter:title" content="Enterprise Service Management (ESM) and YaSM">
<meta name="twitter:description" content="Enterprise service management (ESM) is an approach for providing value to customers in the form of services. ESM includes capabilities for designing, implementing, operating and improving services.">
<meta name="twitter:description" content="Enterprise service management (ESM) is a management discipline aimed at providing value to customers in the form of services. ESM includes capabilities for designing, implementing, operating and improving services.">
<meta name="twitter:image" content="https://yasm.com/en/content/videos/enterprise-service-management-yasm/yasm-enterprise-service-management-video.jpg">
<meta name="twitter:image" content="https://yasm.com/en/content/videos/enterprise-service-management-yasm/yasm-enterprise-service-management-video.jpg">
<meta name="twitter:image:alt" content="Enterprise service management (ESM) is a management discipline. ESM is about providing value to customers in the form of services. This contrasts with IT service management (ITSM) which is specifically about the management of IT services.">
<meta name="twitter:image:alt" content="Enterprise service management (ESM) is a management discipline. ESM is about providing value to customers in the form of services. This contrasts with IT service management (ITSM) which is specifically about the management of IT services.">
<link href="https://plus.google.com/104150539756444616711/posts" rel="publisher" />
<link href="https://plus.google.com/104150539756444616711/posts" rel="publisher" />
</itpmch>
</itpmch>
<html><div class="floatright"><div class="noresize"><map name="ImageMap_yasm-wiki-share"><area href="https://www.linkedin.com/shareArticle?mini=true&url=https%3A%2F%2Fyasm.com%2Fwiki%2Fen%2Findex.php%2FEnterprise_Service_Management_(ESM)_and_YaSM&hl=en_US&source=YaSM%20Wiki" class="plainlinks" rel="nofollow" shape="rect" coords="55,0,99,36" alt="share this page on LinkedIn" title="share this page on LinkedIn"/><area href="https://twitter.com/intent/tweet?url=https%3A%2F%2Fyasm.com%2Fwiki%2Fen%2Findex.php%2FEnterprise_Service_Management_(ESM)_and_YaSM&text=%23YaSMwiki%20%7C%20Enterprise%20service%20management%20(ESM)%20and%20YaSM%0A%E2%96%BA&lang=en&via=yasmcom" class="plainlinks" rel="nofollow" shape="rect" coords="97,0,140,36" alt="share this page on Twitter" title="share this page on Twitter"/></map><img alt="share this page" src="https://yasm.com/wiki/en/img/yasm-wiki/YaSM-Wiki-share.png" width="140" height="36" usemap="#ImageMap_yasm-wiki-share"/></div></div><div class="noresize"><a href="https://yasm.com/wiki/de/index.php/Enterprise-Service-Management_(ESM)_und_YaSM"><img src="https://yasm.com/wiki/en/img/yasm-wiki/YaSM-Wiki-Deutsch.png" width="140" height="36" style="float:left;" alt="auf Deutsch" title="This page in German" /></a></div><br style="clear:both;"/>
<html><div class="floatright"><div class="noresize"><map name="ImageMap_yasm-wiki-share"><area href="https://www.linkedin.com/shareArticle?mini=true&url=https%3A%2F%2Fyasm.com%2Fwiki%2Fen%2Findex.php%2FEnterprise_Service_Management_(ESM)_and_YaSM&hl=en_US&source=YaSM%20Wiki" class="plainlinks" rel="nofollow" shape="rect" coords="55,0,99,36" alt="share this page on LinkedIn" title="share this page on LinkedIn"/><area href="https://twitter.com/intent/tweet?url=https%3A%2F%2Fyasm.com%2Fwiki%2Fen%2Findex.php%2FEnterprise_Service_Management_(ESM)_and_YaSM&text=%23YaSMwiki%20%7C%20Enterprise%20service%20management%20(ESM)%20and%20YaSM%0A%E2%96%BA&lang=en&via=yasmcom" class="plainlinks" rel="nofollow" shape="rect" coords="97,0,140,36" alt="share this page on Twitter" title="share this page on Twitter"/></map><img alt="share this page" src="https://yasm.com/wiki/en/img/yasm-wiki/YaSM-Wiki-share.png" width="140" height="36" usemap="#ImageMap_yasm-wiki-share"/></div></div><div class="noresize"><a href="https://yasm.com/wiki/de/index.php/Enterprise-Service-Management_(ESM)_und_YaSM"><img src="https://yasm.com/wiki/en/img/yasm-wiki/YaSM-Wiki-Deutsch.png" width="140" height="36" style="float:left;" alt="auf Deutsch" title="This page in German" /></a></div><br style="clear:both;"/></html>
<p>&nbsp;</p>


===What is enterprise service management?===
----
<html><span id="enterprise-service-management"><span id="md-webpage-description" itemprop="description"><i>Enterprise service management (ESM)</i> is a management discipline aimed at providing value to customers in the form of services. ESM includes capabilities for designing, implementing, operating and improving services. <a href="#ITIL-glossary">[1]</a><br /><br />This contrasts with <i>IT service management (ITSM)</i> which is specifically about the management of IT services.</span></span></p>
<p>&nbsp;</p>
<p>&nbsp;</p>
<p id="md-webpage-description" itemprop="description"><i>Enterprise service management (ESM)</i> is an approach for providing value to customers in the form of services. ESM includes capabilities for designing, implementing, operating and improving services.</p>


<div itemid="https://yasm.com/wiki/en/img/enterprise-service-management/696px-what-is-enterprise-service-management.jpg" itemscope itemtype="https://schema.org/ImageObject">
<div itemid="https://yasm.com/wiki/en/img/enterprise-service-management/696px-what-is-enterprise-service-management.jpg" itemscope itemtype="https://schema.org/ImageObject">
Line 37: Line 40:
<meta itemprop="height" content="942" />
<meta itemprop="height" content="942" />
<meta itemprop="keywords" content="Enterprise Service Management" />
<meta itemprop="keywords" content="Enterprise Service Management" />
<img itemprop="thumbnailUrl" style="margin:5px 0px 30px 30px; float:right;" src="https://yasm.com/wiki/en/img/enterprise-service-management/thumbs/348px-what-is-enterprise-service-management.jpg" width="348" height="174" title="Enterprise Service Management (ESM) and YaSM" alt="How enterprise service management evolved out of IT service management." /></a></div>
<img itemprop="thumbnailUrl" style="margin:5px 0px 30px 30px; float:right;" src="https://yasm.com/wiki/en/img/enterprise-service-management/thumbs/348px-what-is-enterprise-service-management.jpg" width="348" height="174" title="Enterprise Service Management (ESM) and YaSM" alt="How enterprise service management evolved out of IT service management." /></a></div></html>


<p>There is no "official" definition of enterprise service management, but some research on the web suggests that most people would agree with the above variation of the definition for 'service management' from the official ITIL&reg; glossary <a href="#ITIL">[1, 2]</a>).</p>
__TOC__


<p>This contrasts with <i>IT service management (ITSM)</i> which is specifically about the management of IT services.</p>
<br style="clear:both;"/>


<p style="clear:both;">As a side note, Wikipedia also offers a definition that refers to enterprise service management as a "category of business management software ... and the use of service processes and technologies across an organization" <a href="#Wikipedia-ESM">[3]</a>. This confuses two concepts which are really different:</html>
<html>Wikipedia also offers a definition that refers to ESM as a "category of business management software ... and the use of service processes and technologies across an organization" <a href="#Wikipedia-ESM">[2]</a>. This confuses two concepts which are really different:</html>


* Enterprise service management as a management discipline, and
* Enterprise service management as a management discipline, and
Line 49: Line 52:


Therefore we do not agree with the definition in Wikipedia.
Therefore we do not agree with the definition in Wikipedia.
<p>&nbsp;</p>
<p>&nbsp;</p>


==<span id="enterprise-service-management">What is enterprise service management? | Video</span>==
==Video: ESM and YaSM==


<html><a href="https://yasm.com/en/videos/enterprise-service-management-yasm" ><img src="https://yasm.com/en/content/videos/enterprise-service-management-yasm/yasm-enterprise-service-management-video.jpg" width="320" height="180" class="thumbimage" alt="Video: Enterprise Service Management (ESM) and YaSM" title="Start video: Enterprise Service Management (ESM) and YaSM" style="display: block; float: right; margin-top: 10px; margin-left: 30px; margin-bottom: 10px; margin-right: 10px" /></a>
<html><a href="https://yasm.com/en/videos/enterprise-service-management-yasm" ><img src="https://yasm.com/en/content/videos/enterprise-service-management-yasm/yasm-enterprise-service-management-video.jpg" width="320" height="180" class="thumbimage" alt="Video: Enterprise Service Management (ESM) and YaSM" title="Start video: Enterprise Service Management (ESM) and YaSM" style="display: block; float: right; margin-top: 10px; margin-left: 30px; margin-bottom: 10px; margin-right: 10px" /></a>
<p style="margin-top: 10px;">If you are new to ESM, start here! In this video Stefan Kempter explores the ideas behind enterprise service management and he shows how the YaSM model helps service providers with introducing ESM.</p>
<p style="margin-top: 10px;">If you are new to ESM, start here! In this video Stefan Kempter explores the ideas behind enterprise service management and he shows how the YaSM model helps service providers with introducing ESM.</p>
<p>Watch the video: "<a href="https://yasm.com/en/videos/enterprise-service-management-yasm">Enterprise service management (ESM) and YaSM</a>" (10:36 min.)
<ul style="list-style-image: URL('/wiki/en/img/yasm-wiki/icon-video-camera.png');padding-left: 18px;">
<li>Watch the video: <a href="https://yasm.com/en/videos/enterprise-service-management-yasm">Enterprise service management (ESM) and YaSM</a> (10:36 min.)</li></ul>
<br style="clear:both;"/><br /></html>
<br style="clear:both;"/><br /></html>


==<span id="history-of-esm">How ESM evolved out of IT service management</span>==
==<span id="history-of-esm">How ESM evolved out of ITSM</span>==


The discipline of service management was pioneered in the field of information technology (IT) services. Back in the 1980's, the British government found that many of the IT services it procured did not meet expectations, and commissioned the development of methods for the provision of IT services with better quality at lower costs.
The discipline of [[Service Management Processes|service management]] was pioneered in the field of information technology (IT) services. Back in the 1980's, the British government found that many of the IT services it procured did not meet expectations, and commissioned the development of methods for the provision of IT services with better quality at lower costs.


This led to the publication of a catalogue of best practices for the IT organization, which today is known as [https://wiki.en.it-processmaps.com/index.php/Main_Page ITIL&reg; (IT Infrastructure Library)]. Over the years, ITIL was updated several times, and it's probably fair to say that the ITIL advice is followed - to varying degrees - by the majority of organizations that provide IT services.
This led to the publication of a catalogue of IT service management (ITSM) best practices for the IT organization, which today is known as [https://wiki.en.it-processmaps.com/index.php/Main_Page ITIL&reg; (IT Infrastructure Library)]. Over the years, ITIL was updated several times, and it's probably fair to say that the ITIL advice is followed - to varying degrees - by the majority of organizations that provide IT services.


So ITIL was developed specifically for the domain of IT services, and therefore many parts of ITIL are about managing the technical infrastructure that underpins the business of IT service providers.
So ITIL was developed specifically for the domain of IT services, and therefore many parts of ITIL are about managing the technical infrastructure that underpins the business of IT service providers.
Line 77: Line 80:
<p>&nbsp;</p>
<p>&nbsp;</p>


==<span id="enterprise-service-management-benefits">Benefits of applying ESM best practice</span>==
==<span id="enterprise-service-management-benefits">Benefits</span>==


Enterprise service management does not have a long history yet, but IT organizations have been following the IT service management guidance for decades and seen many improvements.
So, what are the benefits of applying ESM best practice? Enterprise service management does not have a long history yet, but IT organizations have been following the IT service management guidance for decades and seen many improvements.


Since ESM has its roots in ITSM, both concepts will, by and large, offer the same benefits. In particular, we can expect the following advantages:
Since ESM has its roots in ITSM, both concepts will, by and large, offer the same benefits. In particular, we can expect the following advantages:


* Cost savings through more efficient processes and workflows
* Cost savings through more efficient processes and workflows.
* Improved customer satisfaction through customer focus and seamless support
* Improved customer satisfaction through customer focus and seamless support.
* Long-term success through active management of the service portfolio.
* Long-term success through active management of the service portfolio.


<p>&nbsp;</p>
<p>&nbsp;</p>


==<span id="esm-processes">Enterprise service management processes</span>==
==<span id="esm-processes">ESM processes</span>==


Unlike ITIL, enterprise service management is not a well-defined framework, so we cannot provide a universally accepted list of processes and activities.
Unlike ITIL, enterprise service management is not a well-defined framework, so we cannot provide a universally accepted [[Service Management Processes|list of ESM processes]] and activities.


But since ESM has its roots in IT service management best practice, we can assume that the [https://wiki.en.it-processmaps.com/index.php/ITIL_Processes#ITIL_Processes_according_to_ITIL_2011 service lifecycle concept in ITIL] is a good starting point for all organizations that wish to improve the management of their services. The lifecycle is a variant of the "Plan-Do-Check-Act" or "PDCA" cycle, a well-established management method for continual improvement.
But since ESM has its roots in IT service management best practice, we can assume that the service lifecycle concept in ITIL is a good starting point for all organizations that wish to improve the management of their services. The lifecycle is a variant of the "Plan-Do-Check-Act" or "PDCA" cycle, a well-established management method for [[LP5: Improve the services|continual improvement]].


<p>&nbsp;</p>
<p>&nbsp;</p>


The [[YaSM_Processes#service-lifecycle-processes|service lifecycle]] consists of five processes (or "stages"):
The <i>[[Service_Management_Processes#service-lifecycle-processes|service lifecycle]]</i> consists of five [[Service_Management_Processes|service management processes]] (or "stages"):


* [[LP1: Set the strategic direction|Service strategy]]: The first stage in the service lifecycle is about setting the service strategy. As service providers, we start with an assessment of our current service offerings, the customers' needs and our own weaknesses and strengths. Based on this assessment, we can define a strategy or road-map for developing a portfolio of services to be offered to our customers.
# [[LP1: Set the strategic direction|Service strategy]]:<br />The first stage in the service lifecycle is about setting the service strategy. As service providers, we start with an assessment of our current service offerings, the customers' needs and our own weaknesses and strengths. Based on this assessment, we can define a strategy or road-map for developing a portfolio of services to be offered to our customers.
* [[LP2: Design new or changed services|Service design]]: In the second process, we define the expected outcomes of any new or changed services and specify the approach for their implementation.
# [[LP2: Design new or changed services|Service design]]:<br />In the second process, we define the expected outcomes of any new or changed services and specify the approach for their implementation.
* [[LP3: Build new or changed services|Service implementation/ service build]]: In the third lifecycle stage, we take care of implementing new services (or changes to existing services). This includes acquiring, developing and testing of all required service components, such as the technical infrastructure and supporting services provided by external parties.
# [[LP3: Build new or changed services|Service implementation/ service build]]:<br />In the third lifecycle stage, we take care of implementing new services (or changes to existing services). This includes acquiring, developing and testing of all required service components, such as the technical infrastructure and supporting services provided by external parties.
* [[LP4: Operate the services|Service operation]]: Once the services are operational, we need to ensure they are provided efficiently and effectively. This includes handling issues and service requests, performing maintenance tasks, and producing reports on the achieved service quality.
# [[LP4: Operate the services|Service operation]]:<br />Once the services are operational, we need to ensure they are provided efficiently and effectively. This includes handling issues and service requests, performing maintenance tasks, and producing reports on the achieved service quality.
* [[LP5: Improve the services|Service improvement]]: The final stage is about continual improvement. Within this process, we assess if the services are delivered as promised and try to identify potentials for improvement. This will often lead to the specification and implementation of service improvements.
# [[LP5: Improve the services|Service improvement]]:<br />The final stage is about continual improvement. Within this process, we assess if the services are delivered as promised and try to identify potentials for improvement. This will often lead to the specification and implementation of service improvements.


<p>&nbsp;</p>
<p>&nbsp;</p>
Line 113: Line 116:
For instance, a business installing equipment in clients' homes will need robust processes for managing configuration information and dealing with failures of these devices, while this may not be so much of a concern for a restaurant chain.
For instance, a business installing equipment in clients' homes will need robust processes for managing configuration information and dealing with failures of these devices, while this may not be so much of a concern for a restaurant chain.


Apart from the service lifecycle processes, most organizations will need a number of [[YaSM_Processes#supporting-service-management-processes|additional, supporting processes]], as recommended in service management best practice. Among these are customer relationship management, financial management, project management, etc. Again, this list of processes is not prescriptive and which ones are needed will depend on the type of business.
Apart from the service lifecycle processes, most organizations will need a number of <i>[[Service_Management_Processes#supporting-processes|additional, supporting processes]]</i>, as recommended in service management best practice. Among these are [[SP3: Manage customer relationships|customer relationship management]], [[SP6: Manage projects|project management]], [[SP12: Manage service financials|financial management]], etc. Again, this list of processes is not prescriptive and which ones are needed will depend on the type of business.
 
<p>&nbsp;</p>
<p>&nbsp;</p>


==<span id="enterprise-service-management-framework">YaSM - a process model for enterprise service management</span>==
==<span id="enterprise-service-management-framework">YaSM: The ESM process model</span>==


ITIL was developed specifically for the domain of IT services, and what's more, it has grown rather complex over the years.
ITIL was developed specifically for the domain of IT services, and what's more, it has grown rather complex over the years.
Line 125: Line 127:
And here YaSM comes into the picture:
And here YaSM comes into the picture:


When creating [[What is YaSM|YaSM]], our aim was to build a streamlined process model that is not too hard to understand. YaSM, with its simple [[YaSM_Processes#yasm-process-structure|process structure]] and complete set of [[YaSM Implementation with Process Templates|process and document templates]], is thus a very good choice for organizations that want to get started with enterprise service management.
When creating [[What is YaSM|YaSM]], our aim was to build a streamlined process model that is not too hard to understand. YaSM, with its simple [[Service_Management_Processes#yasm-process-structure|process structure]] and complete set of [[YaSM Implementation with Process Templates|process and document templates]], is thus a very good choice for organizations that want to get started with enterprise service management.
 
<html><ul style="list-style-image: URL('/wiki/en/img/yasm-wiki/icon-video-camera.png');padding-left: 18px;">
<li>Start the video: <a href="https://yasm.com/en/videos/enterprise-service-management-yasm">Enterprise service management (ESM) and YaSM</a></li></ul></html>


&#8594; Watch the video: [https://yasm.com/en/videos/enterprise-service-management-yasm Enterprise service management (ESM) and YaSM]
<p>&nbsp;</p>
<p>&nbsp;</p>


==Notes==
==Notes==


[1] <span id="ITIL">ITIL<sup><small>&#174;</small></sup> is a registered trade mark of AXELOS Limited. - IT Infrastructure Library<sup><small>&#174;</small></sup> is a registered trade mark of AXELOS Limited.</span><br />
[1] <span id="ITIL-glossary">This description is a variant of the term "service management" in the official ITIL&reg; glossary. The complete [https://www.itsmf.de/community/itsm-querschnitts-fachforen/ak-publikationen.html#c1077 ITIL glossary] (in English and German) is available for download at the itSMF Germany website.</span><br />
[2] <span id="ITIL-glossary">The complete [http://www.best-management-practice.com/bookstore.asp?DI=575004&amp;FO=1230366 ITIL Glossary compiled by APMG in conjunction with the Cabinet Office and TSO] is available for download from the Internet.</span><br />
[2] <span id="Wikipedia-ESM">[https://en.wikipedia.org/wiki/Enterprise_service_management Enterprise service management]. -- Wikipedia. Retrieved September 29, 2018.</span>
[3] <span id="Wikipedia-ESM">[https://en.wikipedia.org/wiki/Enterprise_service_management Enterprise service management]. -- Wikipedia. Retrieved November 25, 2016.</span>


<html>By:&#160;&#160;Stefan Kempter&#160;<a rel="author" href="https://plus.google.com/111925560448291102517/about"><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>&#160;&#160;and&#160;&#160;Andrea Kempter&#160;<a href="https://plus.google.com/113316270668629760475/about"><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>, IT Process Maps.</html>
<html>By:&#160;&#160;Stefan Kempter&#160;<a rel="author" href="https://plus.google.com/111925560448291102517/about"><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>&#160;&#160;and&#160;&#160;Andrea Kempter&#160;<a href="https://plus.google.com/113316270668629760475/about"><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>, IT Process Maps.</html>
Line 152: Line 155:
<span itemscope itemtype="http://schema.org/BreadcrumbList">
<span itemscope itemtype="http://schema.org/BreadcrumbList">
<span itemprop="itemListElement" itemscope itemtype="http://schema.org/ListItem">
<span itemprop="itemListElement" itemscope itemtype="http://schema.org/ListItem">
<a itemprop="item" href="https://yasm.com/wiki/en/index.php/Enterprise_Service_Management_(ESM)_and_YaSM#enterprise-service-management">
<a itemprop="item" href="https://yasm.com/wiki/en/index.php/Enterprise_Service_Management_(ESM)_and_YaSM#What_is_enterprise_service_management.3F">
<span itemprop="name">What is ESM?</span></a>
<span itemprop="name">What is ESM?</span></a>
<meta itemprop="position" content="1" /></span> ›
<meta itemprop="position" content="1" /></span> ›
<span itemprop="itemListElement" itemscope itemtype="http://schema.org/ListItem">
<span itemprop="itemListElement" itemscope itemtype="http://schema.org/ListItem">
<a itemprop="item" href="https://yasm.com/wiki/en/index.php/Enterprise_Service_Management_(ESM)_and_YaSM#history-of-esm">
<a itemprop="item" href="https://yasm.com/wiki/en/index.php/Enterprise_Service_Management_(ESM)_and_YaSM#Video:_ESM_and_YaSM">
<span itemprop="name">How ESM evolved out of IT service management</span></a>
<span itemprop="name">Video: ESM and YaSM</span></a>
<meta itemprop="position" content="2" /></span> ›
<meta itemprop="position" content="2" /></span> ›
<span itemprop="itemListElement" itemscope itemtype="http://schema.org/ListItem">
<span itemprop="itemListElement" itemscope itemtype="http://schema.org/ListItem">
<a itemprop="item" href="https://yasm.com/wiki/en/index.php/Enterprise_Service_Management_(ESM)_and_YaSM#enterprise-service-management-benefits">
<a itemprop="item" href="https://yasm.com/wiki/en/index.php/Enterprise_Service_Management_(ESM)_and_YaSM#How_ESM_evolved_out_of_ITSM">
<span itemprop="name">Benefits of applying ESM best practice</span></a>
<span itemprop="name">How ESM evolved out of ITSM</span></a>
<meta itemprop="position" content="3" /></span> ›
<meta itemprop="position" content="3" /></span> ›
<span itemprop="itemListElement" itemscope itemtype="http://schema.org/ListItem">
<span itemprop="itemListElement" itemscope itemtype="http://schema.org/ListItem">
<a itemprop="item" href="https://yasm.com/wiki/en/index.php/Enterprise_Service_Management_(ESM)_and_YaSM#esm-processes">
<a itemprop="item" href="https://yasm.com/wiki/en/index.php/Enterprise_Service_Management_(ESM)_and_YaSM#Benefits">
<span itemprop="name">Benefits</span></a>
<meta itemprop="position" content="4" /></span> ›
<span itemprop="itemListElement" itemscope itemtype="http://schema.org/ListItem">
<a itemprop="item" href="https://yasm.com/wiki/en/index.php/Enterprise_Service_Management_(ESM)_and_YaSM#ESM_processes">
<span itemprop="name">ESM processes</span></a>
<span itemprop="name">ESM processes</span></a>
<meta itemprop="position" content="4" /></span> ›
<meta itemprop="position" content="5" /></span> ›
<span itemprop="itemListElement" itemscope itemtype="http://schema.org/ListItem">
<span itemprop="itemListElement" itemscope itemtype="http://schema.org/ListItem">
<a itemprop="item" href="https://yasm.com/wiki/en/index.php/Enterprise_Service_Management_(ESM)_and_YaSM#enterprise-service-management-framework">
<a itemprop="item" href="https://yasm.com/wiki/en/index.php/Enterprise_Service_Management_(ESM)_and_YaSM#YaSM:_The_ESM_process_model">
<span itemprop="name">ESM process model</span></a>
<span itemprop="name">ESM process model</span></a>
<meta itemprop="position" content="5" /></span>
<meta itemprop="position" content="6" /></span>
</span>
</span>
</small></p>
</small></p>
Line 179: Line 186:
   <link itemprop="url" href="https://yasm.com/wiki/en/index.php/Enterprise_Service_Management_(ESM)_and_YaSM" />
   <link itemprop="url" href="https://yasm.com/wiki/en/index.php/Enterprise_Service_Management_(ESM)_and_YaSM" />
   <link itemprop="primaryImageOfPage" href="https://yasm.com/wiki/en/img/enterprise-service-management/696px-what-is-enterprise-service-management.jpg" />
   <link itemprop="primaryImageOfPage" href="https://yasm.com/wiki/en/img/enterprise-service-management/696px-what-is-enterprise-service-management.jpg" />
   <meta itemprop="significantLinks" content="https://yasm.com/wiki/en/index.php/YaSM_Processes" />
   <meta itemprop="significantLinks" content="https://yasm.com/wiki/en/index.php/Service_Management_Processes" />
   <meta itemprop="significantLinks" content="https://yasm.com/wiki/en/index.php/What_is_YaSM" />
   <meta itemprop="significantLinks" content="https://yasm.com/wiki/en/index.php/What_is_YaSM" />
   <meta itemprop="significantLinks" content="https://yasm.com/wiki/en/index.php/YaSM_Implementation_with_Process_Templates" />
   <meta itemprop="significantLinks" content="https://yasm.com/wiki/en/index.php/YaSM_Implementation_with_Process_Templates" />

Revision as of 12:33, 12 October 2018

share this page on LinkedInshare this page on Twittershare this page
auf Deutsch


 

What is enterprise service management?


Enterprise service management (ESM) is a management discipline aimed at providing value to customers in the form of services. ESM includes capabilities for designing, implementing, operating and improving services. [1]

This contrasts with IT service management (ITSM) which is specifically about the management of IT services.

 


Wikipedia also offers a definition that refers to ESM as a "category of business management software ... and the use of service processes and technologies across an organization" [2]. This confuses two concepts which are really different:

  • Enterprise service management as a management discipline, and
  • ESM tools or software that are used by organizations to support their ESM processes

Therefore we do not agree with the definition in Wikipedia.

 

Video: ESM and YaSM

Video: Enterprise Service Management (ESM) and YaSM

If you are new to ESM, start here! In this video Stefan Kempter explores the ideas behind enterprise service management and he shows how the YaSM model helps service providers with introducing ESM.



How ESM evolved out of ITSM

The discipline of service management was pioneered in the field of information technology (IT) services. Back in the 1980's, the British government found that many of the IT services it procured did not meet expectations, and commissioned the development of methods for the provision of IT services with better quality at lower costs.

This led to the publication of a catalogue of IT service management (ITSM) best practices for the IT organization, which today is known as ITIL® (IT Infrastructure Library). Over the years, ITIL was updated several times, and it's probably fair to say that the ITIL advice is followed - to varying degrees - by the majority of organizations that provide IT services.

So ITIL was developed specifically for the domain of IT services, and therefore many parts of ITIL are about managing the technical infrastructure that underpins the business of IT service providers.

But it was always obvious that there are many similarities between providers of IT and non-IT services. Everyone in the business of providing services should, for instance, know the needs of their customers and have methods in place for offering and managing a range of services that fulfill those needs.

What happened is that, as ITIL grew popular, more and more people realized that ITIL and ITSM best practice can be put to good use in all organizations or business functions that provide services, for example in the fields of healthcare, banking, human resources, legal services, etc.

The spread of ITIL beyond the framework's traditional use in IT was certainly driven by the many "ITIL-compatible" tools that are readily available on the market: Service providers of all sorts discovered that their operations can benefit from tools such as help-desk software or self-service portals.

Still, we are at the beginning and the idea that ITIL principles can be applied outside IT organizations is only now gaining traction. In this context, "enterprise service management" has emerged as a new catchphrase. It is often used when people speak or write about "applying ITIL and ITSM best practice in areas beyond IT".

 

Benefits

So, what are the benefits of applying ESM best practice? Enterprise service management does not have a long history yet, but IT organizations have been following the IT service management guidance for decades and seen many improvements.

Since ESM has its roots in ITSM, both concepts will, by and large, offer the same benefits. In particular, we can expect the following advantages:

  • Cost savings through more efficient processes and workflows.
  • Improved customer satisfaction through customer focus and seamless support.
  • Long-term success through active management of the service portfolio.

 

ESM processes

Unlike ITIL, enterprise service management is not a well-defined framework, so we cannot provide a universally accepted list of ESM processes and activities.

But since ESM has its roots in IT service management best practice, we can assume that the service lifecycle concept in ITIL is a good starting point for all organizations that wish to improve the management of their services. The lifecycle is a variant of the "Plan-Do-Check-Act" or "PDCA" cycle, a well-established management method for continual improvement.

 

The service lifecycle consists of five service management processes (or "stages"):

  1. Service strategy:
    The first stage in the service lifecycle is about setting the service strategy. As service providers, we start with an assessment of our current service offerings, the customers' needs and our own weaknesses and strengths. Based on this assessment, we can define a strategy or road-map for developing a portfolio of services to be offered to our customers.
  2. Service design:
    In the second process, we define the expected outcomes of any new or changed services and specify the approach for their implementation.
  3. Service implementation/ service build:
    In the third lifecycle stage, we take care of implementing new services (or changes to existing services). This includes acquiring, developing and testing of all required service components, such as the technical infrastructure and supporting services provided by external parties.
  4. Service operation:
    Once the services are operational, we need to ensure they are provided efficiently and effectively. This includes handling issues and service requests, performing maintenance tasks, and producing reports on the achieved service quality.
  5. Service improvement:
    The final stage is about continual improvement. Within this process, we assess if the services are delivered as promised and try to identify potentials for improvement. This will often lead to the specification and implementation of service improvements.

 

Of course, this list of processes is not prescriptive, but for most service providers it will be appropriate to introduce at least a basic set of service lifecycle processes, for the lifecycle concept ensures that we never stop learning from past successes and failures - and stay on track in the longer term.

The degree of sophistication required for each process will depend on the nature of the business:

For instance, a business installing equipment in clients' homes will need robust processes for managing configuration information and dealing with failures of these devices, while this may not be so much of a concern for a restaurant chain.

Apart from the service lifecycle processes, most organizations will need a number of additional, supporting processes, as recommended in service management best practice. Among these are customer relationship management, project management, financial management, etc. Again, this list of processes is not prescriptive and which ones are needed will depend on the type of business.

 

YaSM: The ESM process model

ITIL was developed specifically for the domain of IT services, and what's more, it has grown rather complex over the years.

From numerous conversations with our customers we know that, in order to become attractive to providers of non-IT services, the service management guidance has to be easier to understand and less biased towards the management of IT infrastructure.

And here YaSM comes into the picture:

When creating YaSM, our aim was to build a streamlined process model that is not too hard to understand. YaSM, with its simple process structure and complete set of process and document templates, is thus a very good choice for organizations that want to get started with enterprise service management.

 

Notes

[1] This description is a variant of the term "service management" in the official ITIL® glossary. The complete ITIL glossary (in English and German) is available for download at the itSMF Germany website.
[2] Enterprise service management. -- Wikipedia. Retrieved September 29, 2018.

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

 

Related articles

Enterprise service management is a growing trend. What are the key success factors in ESM?

Enterprise service management is gaining traction

by: Stefan Kempter

Enterprise service management is a growing trend. What are the key success factors in ESM? [...]


 

What is ESM?  › Video: ESM and YaSM  › How ESM evolved out of ITSM  › Benefits  › ESM processes  › ESM process model