YaSM Concepts: Difference between revisions
From YaSM Service Management Wiki
No edit summary |
No edit summary |
||
| Line 1: | Line 1: | ||
<itpmch><title>YaSM Concepts | YaSM Service Management Wiki</title> | <itpmch><title>YaSM Concepts | YaSM Service Management Wiki</title> | ||
<meta name="keywords" content="yasm concepts, service management concepts, understanding yasm" /> | <meta name="keywords" content="yasm concepts, service management concepts, understanding yasm" /> | ||
<meta name="description" content="This chapter provides detailed information on 3 important | <meta name="description" content="This chapter provides detailed information on 3 important service management concepts which are used in many YaSM processes." /> | ||
<meta property="og:url" content="https://yasm.com/wiki/en/index.php/YaSM_Concepts" /> | <meta property="og:url" content="https://yasm.com/wiki/en/index.php/YaSM_Concepts" /> | ||
<meta property="og:title" content="YaSM Concepts | YaSM Service Management Wiki" /> | <meta property="og:title" content="YaSM Concepts | YaSM Service Management Wiki" /> | ||
<meta property="og:description" content="This chapter provides detailed information on 3 important | <meta property="og:description" content="This chapter provides detailed information on 3 important service management concepts which are used in many YaSM processes." /> | ||
<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" /> | ||
<meta property="fb:admins" content="100002035253209" /> | <meta property="fb:admins" content="100002035253209" /> | ||
<meta property="fb:admins" content="100002592864414" /> | <meta property="fb:admins" content="100002592864414" /> | ||
<meta property="og:image" content="https://yasm.com/wiki/en/img/yasm-concept/Yasm-concepts.jpg" /> | <meta property="og:image" content="https://yasm.com/wiki/en/img/yasm-concept/16x9/Yasm-concepts.jpg" /> | ||
<meta property="og:image:width" content=" | <meta property="og:image:width" content="1200" /> | ||
<meta property="og:image:height" content=" | <meta property="og:image:height" content="675" /> | ||
<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="YaSM Concepts"> | |||
<meta name="twitter:description" content="3 important service management concepts which are used in many YaSM processes."> | |||
<meta name="twitter:image" content="https://yasm.com/wiki/en/img/yasm-concept/16x9/Yasm-concepts.jpg"> | |||
<meta name="twitter:image:alt" content="Service management key concepts: 3 important concepts ('principles') which are used in many YaSM service management processes."> | |||
<link href="https://plus.google.com/104150539756444616711/posts" rel="publisher" /> | <link href="https://plus.google.com/104150539756444616711/posts" rel="publisher" /> | ||
</itpmch> | </itpmch> | ||
| Line 17: | Line 24: | ||
<p> </p> | <p> </p> | ||
<div itemscope itemtype="https://schema.org/ImageObject"> | <div itemid="https://yasm.com/wiki/en/img/yasm-concept/Yasm-concepts.jpg" itemscope itemtype="https://schema.org/ImageObject"> | ||
<a href="https://yasm.com/wiki/en/img/yasm-concept/Yasm-concepts.jpg" title=" | <a href="https://yasm.com/wiki/en/img/yasm-concept/Yasm-concepts.jpg" title="3 important service management key concepts" itemprop="contentUrl"> | ||
< | <meta itemprop="caption" content="The 3 most important service management key concepts in YaSM." /> | ||
<meta itemprop=" | <meta itemprop="width" content="1200" /> | ||
<meta itemprop=" | <meta itemprop="height" content="900" /> | ||
<meta itemprop=" | <meta itemprop="dateCreated" content="2014-06-25" /> | ||
<meta itemprop="datePublished" content="2014-06-25" /> | |||
<meta itemprop="dateModified" content="2020-04-27" /> | |||
<span itemprop="thumbnail" itemscope itemtype="https://schema.org/ImageObject"> | |||
<meta itemprop="url" content="https://yasm.com/wiki/en/img/yasm-concept/16x9/Yasm-concepts.jpg" /> | |||
<meta itemprop="width" content="1200" /> | |||
<meta itemprop="height" content="675" /> | |||
<meta itemprop="dateCreated" content="2020-04-27" /> | |||
<meta itemprop="datePublished" content="2020-04-28" /> | |||
</span> | |||
<meta itemprop="keywords" content="service management concepts" /> | |||
<meta itemprop="keywords" content="service management key concepts" /> | |||
<meta itemprop="keywords" content="yasm concepts" /> | <meta itemprop="keywords" content="yasm concepts" /> | ||
< | <img style="margin:5px 0px 30px 30px; float:right;" src="https://yasm.com/wiki/en/img/yasm-concept/Yasm-concepts.jpg" width="480" height="360" title="3 important service management key concepts" alt="Service management key concepts: 3 important concepts ('principles') which are used in many YaSM service management processes." /></a></div></html> | ||
<span id="md-webpage-description" itemprop="description">This chapter provides detailed information on three important [[YaSM Concepts|service management concepts]] (or principles) which are used in many [[Service Management Processes|YaSM processes]]. Understanding these key concepts will be helpful for understanding how YaSM and the YaSM processes work.</span> | |||
<p> | <p> </p> | ||
< | __TOC__ | ||
<br style="clear:both;"/> | |||
==<span id="yasm-concept-1">The service portfolio, service definitions and service catalogs</span>== | ==<span id="yasm-concept-1">The service portfolio, service definitions and service catalogs</span>== | ||
Every service provider needs a precise understanding of the services it provides and the interdependencies between those services - otherwise it will be very difficult to manage those services. | Every service provider needs a precise understanding of the [[Service|services]] it provides and the interdependencies between those services - otherwise it will be very difficult to manage those services. | ||
In this respect, YaSM is aligned with the most widely used service management frameworks and recommends maintaining a service portfolio that provides a complete overview of all services, and possibly one or several service catalogs for the customers. The detailed service properties are documented in service definitions. | In this respect, YaSM is aligned with the most widely used [[Service_Management#What_service_management_frameworks_are_available.3F|service management frameworks]] and recommends maintaining a service portfolio that provides a complete overview of all services, and possibly one or several service catalogs for the customers. The detailed service properties are documented in service definitions. | ||
&# | ▶ Details: [[Service Portfolio, Service Definitions and Service Catalogs|The service portfolio, service definitions and service catalogs]] | ||
<p> </p> | <p> </p> | ||
| Line 44: | Line 63: | ||
==<span id="yasm-concept-2">Customer vs. operational service definitions and agreements</span>== | ==<span id="yasm-concept-2">Customer vs. operational service definitions and agreements</span>== | ||
Services in the service portfolio may be "customer services" (services offered to customers) or "supporting services" (services visible only inside the service provider organization which are used as building blocks for the customer services). | Services in the service portfolio may be "[[Service#Customer-facing_services|customer services]]" (services offered to customers) or "[[Service#Internal_services_and_shared_services|supporting services]]" (services visible only inside the service provider organization which are used as building blocks for the customer services). | ||
For example, if a service provider offers a "web site hosting" service to its clients, this customer service will often be based on a number of internal supporting services, such as "network infrastructure management service", "server management service", etc. | For example, if a service provider offers a "web site hosting" service to its clients, this customer service will often be based on a number of internal supporting services, such as "network infrastructure management service", "server management service", etc. | ||
| Line 54: | Line 73: | ||
*Define and agree with the owners of the internal supporting services what is to be delivered; this includes specifying the properties of the supporting services in the form of service definitions, and signing operational service agreements with the internal service owners. | *Define and agree with the owners of the internal supporting services what is to be delivered; this includes specifying the properties of the supporting services in the form of service definitions, and signing operational service agreements with the internal service owners. | ||
&# | ▶ Details: [[Customer vs. Operational Service Definitions and Agreements|Customer vs. operational service definitions and agreements]] | ||
<p> </p> | <p> </p> | ||
| Line 60: | Line 79: | ||
==<span id="yasm-concept-3">Plans for organizing service management initiatives</span>== | ==<span id="yasm-concept-3">Plans for organizing service management initiatives</span>== | ||
Readers familiar with ITIL will know the service improvement plan (SIP). | Readers familiar with [[ITIL]]® will know the service improvement plan (SIP). | ||
There is also a service improvement plan in YaSM, but YaSM extends the concept and recommends to maintain similar plans for organizing other kinds of work and initiatives, e.g. a process improvement plan to manage process improvement initiatives, a security improvement plan to manage security improvement initiatives, etc. | There is also a service improvement plan in YaSM, but YaSM extends the concept and recommends to maintain similar plans for organizing other kinds of work and initiatives, e.g. a process improvement plan to manage process improvement initiatives, a security improvement plan to manage security improvement initiatives, etc. | ||
&# | ▶ Details: [[Plans for organizing Service Management Initiatives|Plans for organizing service management initiatives]] | ||
<p> </p> | <p> </p> | ||
| Line 77: | Line 96: | ||
<span itemprop="breadcrumb" itemscope itemtype="http://schema.org/BreadcrumbList"> | <span itemprop="breadcrumb" 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/ | <a itemprop="item" href="https://yasm.com/wiki/en/index.php/YaSM_Concepts#The_service_portfolio.2C_service_definitions_and_service_catalogs"> | ||
<span itemprop="name">Service portfolio, service definitions [...]</span></a> | <span itemprop="name">Service portfolio, service definitions [...]</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/Customer_vs | <a itemprop="item" href="https://yasm.com/wiki/en/index.php/YaSM_Concepts#Customer_vs._operational_service_definitions_and_agreements"> | ||
<span itemprop="name">Customer vs operational service definitions [...]</span></a> | <span itemprop="name">Customer vs operational service definitions [...]</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/ | <a itemprop="item" href="https://yasm.com/wiki/en/index.php/YaSM_Concepts#Plans_for_organizing_service_management_initiatives"> | ||
<span itemprop="name">Plans for organizing intiatives</span></a> | <span itemprop="name">Plans for organizing intiatives</span></a> | ||
<meta itemprop="position" content="3" /></span> | <meta itemprop="position" content="3" /></span> | ||
Revision as of 16:15, 28 April 2020
This chapter provides detailed information on three important service management concepts (or principles) which are used in many YaSM processes. Understanding these key concepts will be helpful for understanding how YaSM and the YaSM processes work.
The service portfolio, service definitions and service catalogs
Every service provider needs a precise understanding of the services it provides and the interdependencies between those services - otherwise it will be very difficult to manage those services.
In this respect, YaSM is aligned with the most widely used service management frameworks and recommends maintaining a service portfolio that provides a complete overview of all services, and possibly one or several service catalogs for the customers. The detailed service properties are documented in service definitions.
▶ Details: The service portfolio, service definitions and service catalogs
Customer vs. operational service definitions and agreements
Services in the service portfolio may be "customer services" (services offered to customers) or "supporting services" (services visible only inside the service provider organization which are used as building blocks for the customer services).
For example, if a service provider offers a "web site hosting" service to its clients, this customer service will often be based on a number of internal supporting services, such as "network infrastructure management service", "server management service", etc.
Ultimately, the service provider must deliver the customer services as agreed with the customers. Since the customer services are based on supporting services, this can only work if the supporting services are aligned with the requirements of the customer services and delivered as specified.
This means the service provider will need to
- Define and agree with the customers what is to be delivered, in the form of service definitions and customer service agreements
- Define and agree with the owners of the internal supporting services what is to be delivered; this includes specifying the properties of the supporting services in the form of service definitions, and signing operational service agreements with the internal service owners.
▶ Details: Customer vs. operational service definitions and agreements
Plans for organizing service management initiatives
Readers familiar with ITIL® will know the service improvement plan (SIP).
There is also a service improvement plan in YaSM, but YaSM extends the concept and recommends to maintain similar plans for organizing other kinds of work and initiatives, e.g. a process improvement plan to manage process improvement initiatives, a security improvement plan to manage security improvement initiatives, etc.
▶ Details: Plans for organizing service management initiatives
Notes
By: Andrea Kempter 
and Stefan Kempter , IT Process Maps.
Service portfolio, service definitions [...] › Customer vs operational service definitions [...] › Plans for organizing intiatives
