YaSM Concepts: Difference between revisions
No edit summary |
No edit summary |
||
| Line 19: | Line 19: | ||
<p>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.</p> | <p>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.</p> | ||
<p><a itemprop="significantLinks" href="https://yasm.com/wiki/en/index.php/ | <p><a itemprop="significantLinks" href="https://yasm.com/wiki/en/index.php/Service_Portfolio%2C_Service_Definitions_and_Service_Catalogs">→ Details: The service portfolio, service definitions and service catalogs</a></html> | ||
<p> </p> | <p> </p> | ||
| Line 35: | Line 35: | ||
<li>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.</li></ul> | <li>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.</li></ul> | ||
<p><a itemprop="significantLinks" href="https://yasm.com/wiki/en/index.php/ | <p><a itemprop="significantLinks" href="https://yasm.com/wiki/en/index.php/Customer_vs%2E_Operational_Service_Definitions_and_Agreements">→ Details: Customer vs. operational service definitions and agreements</a></html> | ||
<p> </p> | <p> </p> | ||
| Line 45: | Line 45: | ||
<p>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.</p> | <p>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.</p> | ||
<p><a itemprop="significantLinks" href="https://yasm.com/wiki/en/index.php/ | <p><a itemprop="significantLinks" href="https://yasm.com/wiki/en/index.php/Plans_for_organizing_Service_Management_Initiatives">→ Details: Plans for organizing service management initiatives</a></html> | ||
<p> </p> | <p> </p> | ||
| Line 54: | Line 54: | ||
<tr> | <tr> | ||
<td>Link to this page:</td> | <td>Link to this page:</td> | ||
<td><a itemprop="url" href="https://yasm.com/wiki/en/index.php/ | <td><a itemprop="url" href="https://yasm.com/wiki/en/index.php/YaSM_Concepts">https://yasm.com/wiki/en/index.php/YaSM_Concepts</a></td> | ||
</tr> | </tr> | ||
<tr> | <tr> | ||
| Line 72: | Line 72: | ||
<p><small> | <p><small> | ||
<span itemscope="itemscope" itemtype="http://data-vocabulary.org/Breadcrumb"> | <span itemscope="itemscope" itemtype="http://data-vocabulary.org/Breadcrumb"> | ||
<a href="https://yasm.com/wiki/en/index.php/ | <a href="https://yasm.com/wiki/en/index.php/Service_Portfolio%2C_Service_Definitions_and_Service_Catalogs" itemprop="url"><span itemprop="title">Service portfolio, service definitions [...]</span></a> › | ||
</span> | </span> | ||
<span itemscope="itemscope" itemtype="http://data-vocabulary.org/Breadcrumb"> | <span itemscope="itemscope" itemtype="http://data-vocabulary.org/Breadcrumb"> | ||
<a href="https://yasm.com/wiki/en/index.php/ | <a href="https://yasm.com/wiki/en/index.php/Customer_vs%2E_Operational_Service_Definitions_and_Agreements" itemprop="url"><span itemprop="title">Customer vs operational service definitions [...]</span></a> › | ||
</span> | </span> | ||
<span itemscope="itemscope" itemtype="http://data-vocabulary.org/Breadcrumb"> | <span itemscope="itemscope" itemtype="http://data-vocabulary.org/Breadcrumb"> | ||
<a href="https://yasm.com/wiki/en/index.php/ | <a href="https://yasm.com/wiki/en/index.php/Plans_for_organizing_Service_Management_Initiatives" itemprop="url"><span itemprop="title">Plans for organizing intiatives</span></a> | ||
</span> | </span> | ||
</small></p> | </small></p> | ||
Revision as of 16:30, 18 February 2015
This chapter provides detailed information on three important YaSM concepts (or principles) which are used in many YaSM processes. Understanding these concepts will be helpful for understanding how YaSM and the YaSM processes work.
These are the concepts in question:
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
[ Infobox ]
| Link to this page: | https://yasm.com/wiki/en/index.php/YaSM_Concepts |
| Languages: | English | Deutsch |
| Image: | YaSM concepts (.JPG) |
| Author | Contributor: | Andrea Kempter  and Stefan Kempter - IT Process Maps. |
Service portfolio, service definitions [...] › Customer vs operational service definitions [...] › Plans for organizing intiatives
