ITIL Implementation - IT Service Structure: Difference between revisions

From IT Process Wiki
No edit summary
 
(6 intermediate revisions by the same user not shown)
Line 1: Line 1:
<seo metakeywords="it service structure, it services structure" metadescription="The best way to get a clear picture on IT services is to develop a service structure, comprising both business and supporting services." />
<itpmch><title>ITIL Implementation - IT Service Structure | IT Process Wiki</title>
<meta name="keywords" content="it service structure, it services structure" />
<meta name="description" content="The best way to get a clear picture on IT services is to develop a service structure, comprising both customer services and supporting services." />
<meta property="og:url" content="https://wiki.en.it-processmaps.com/index.php/ITIL_Implementation_-_IT_Service_Structure" />
<meta property="og:title" content="ITIL Implementation - IT Service Structure | IT Process Wiki" />
<meta property="og:description" content="The best way to get a clear picture on IT services is to develop a service structure, comprising both customer services and supporting services." />
<meta property="og:site_name" content="IT Process Wiki - the ITIL&#174; Wiki">
<meta property="og:type" content="article" />
<meta property="fb:admins" content="100002035253209" />
<meta property="fb:admins" content="100002592864414" />
<meta property="og:image" content="https://wiki.en.it-processmaps.com/images/c/cd/2-itil-implementation-IT-service-structure.jpg" />
<meta property="og:image:width" content="1200" />
<meta property="og:image:height" content="600" />
<link href="https://plus.google.com/108613479011811316823/posts" rel="publisher" />
</itpmch>
<imagemap>
<imagemap>
Image:ITIL-Wiki-de-es.jpg|DE - ES - ITIL IT Service Structure|100px
Image:ITIL-Wiki-de-es.jpg|right|DE - ES - ITIL IT Service Structure|163px
rect 0 0 50 30 [https://wiki.de.it-processmaps.com/index.php/ITIL-Implementierung_-_IT-Services diese Seite auf Deutsch]
rect 81 0 114 36 [https://wiki.de.it-processmaps.com/index.php/ITIL-Implementierung_-_IT-Services diese Seite auf Deutsch]
rect 50 0 100 30 [https://wiki.es.it-processmaps.com/index.php/Implementaci%C3%B3n_de_ITIL_-_Estructura_de_servicios esta página en español]
rect 115 0 163 36 [https://wiki.es.it-processmaps.com/index.php/Implementaci%C3%B3n_de_ITIL_-_Estructura_de_servicios esta página en español]
desc none
desc none
</imagemap>
</imagemap>
<br style="clear:both;"/>
<br style="clear:both;"/>
[[image:Defining-the-IT-service-structure-itil-step-2.jpg|thumb|285px|right|alt=Infographic: How to prepare an ITIL project? ITIL implementation, step 2.|link=https://wiki.en.it-processmaps.com/index.php/File:Defining-the-IT-service-structure-itil-step-2.jpg|[[Media:Defining-the-IT-service-structure-itil-step-2.jpg|Infographic: How to define the IT service structure? - ITIL implementation, step 2.]]]]


{|
{|
|-
|-
| style="border-bottom:1px solid grey;" |<big><strong> Step 2: Definition of the IT Service Structure </strong></big>
|style="border-bottom:1px solid grey; font-size:130%"|<strong>Step 2: Definition of the IT Service Structure</strong>
|}
|}


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


Any ITIL initiative should start by looking at services. After all, the whole idea behind introducing ITIL is to achieve a stronger focus on services.
Any ITIL initiative should start by [[#Customer_services_and_supporting_services|looking at services]]. After all, the whole idea behind introducing ITIL best practices is to achieve a better focus on services.


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


==== Objectives of this Project Step ====
===<span id="Objectives of this Project Step">Objectives</span>===


* Identification of business services and supporting services
* Identification of [[#Creating_a_list_of_customer_services|customer services]] and [[#Identifying_supporting_services|supporting services]]
* Creating the service structure by determining the interdependencies between business services and supporting services
* [[#Drawing_up_the_service_structure|Drawing up the service structure]] by determining the interdependencies between customer services and supporting services
 
<br style="clear:both;"/>
<p>&nbsp;</p>
 
==== Description ====
 
===== Business Services and Supporting Services =====


The best way to get a clear picture on services is to develop a service structure, comprising both business services and supporting services. This reflects one of the most important ITIL principles: business services (offered to customers) are built from a set of supporting services (visible only inside the IT organization).
==Description==


There is often confusion in IT organizations about what exactly is considered a business service:
====Customer services and supporting services====


''[[ITIL Implementation - IT Service Structure#Creating a List of Business Services|Business services]]'' are characterized by representing a direct value to customers, like e.g. the provision of e-mailing facilities and internet access.
To get a clear picture of the service provider's range of services, it is advisable to develop a service structure, comprising both customer services and supporting services. This reflects one of the most important principles in ITIL and other service management frameworks: Customer services (services offered to customers) are typically based on a set of supporting services (services visible only inside the service provider organization). Supporting services may be operated with the service provider's own resources or by an external party.


''[[ITIL Implementation - IT Service Structure#Determining Supporting Services|Supporting services]]'', in contrast, are not of direct value to customers but are needed as building blocks for business services. Providing a network infrastructure, for example, would be a supporting service which is required to offer internet access for customers.
There is often confusion about what exactly is considered a customer service:
* [[ITIL Implementation - IT Service Structure#Creating_a_list_of_customer_services|Customer services]] are characterized by providing value to clients, an example would be a service which allows the clients to send and receive emails and to access the internet.
*[[ITIL Implementation - IT Service Structure#Identifying_supporting_services|Supporting services]], in contrast, are not of direct value to clients but are needed as building blocks for customer services. The provision of a suitable network infrastructure, for example, would be a typical supporting service which is required to offer clients an internet access service.


In other words, what the customer wants is reliable internet access, not a specific sort of network infrastructure. (In fact it is irrelevant for the customer that a network infrastructure is needed to provide him with internet access).
In other words, what the customers want is reliable internet access, not a specific sort of network infrastructure (in fact it is irrelevant to the clients that some infrastructure is needed to provide them with internet access).
 
===== Creating a List of Business Services =====
 
<imagemap>
Image:thumb_IT_Services.jpg|right|IT Service Structure - Example [.PDF]|200px|thumb|alt=IT Service Structure
default [https://wiki.en.it-processmaps.com/images/pdf/service_structure.pdf IT Service Structure - Example (.PDF)]
desc bottom-left
</imagemap>


A good way to start is creating a list of existing business services, using – if possible – existing agreements and information. If no service-related information is available, a basic list must be drawn from scratch, including at least short service descriptions and customers using the services.
====Creating a list of customer services====


===== Determining Supporting Services =====
[[Image:thumb_IT_Services.jpg|thumb|200px|right|none|alt=IT Service Structure|link=https://wiki.en.it-processmaps.com/index.php/File:Thumb_IT_Services.jpg|Fig. 1: [https://wiki.en.it-processmaps.com/images/pdf/service_structure.pdf IT Service Structure - Example (.PDF)]]]
A good way to get started is creating a list of existing customer services, using - if possible - existing agreements and other documentation. If no service-related information is available, a basic list must be drawn from scratch, including at least short service descriptions and an overview of which customers use which services.


As soon as it is clear which business services are provided for the customers it becomes possible to identify the required supporting services.
====Identifying supporting services====


The main point of defining supporting services is to assign responsibilities for the delivery of those services. The responsible Service Owners will thus be expected to make sure that their services meet the agreed service level targets.
One it is clear which business services are provided for the customers it becomes possible to identify the required supporting services.


Supporting services are often closely related to certain parts of the IT infrastructure, like e.g. major application systems or infrastructure components: "Providing the SAP environment" would be a typical example.  
A key objective of defining supporting services is to assign responsibilities for the delivery of those services: The [[ITIL Roles#Service Owner|service owners]] are responsible for delivering the services in accordance with the agreed service quality levels.


===== Defining the Service Structure =====
Supporting services are often closely related to certain parts of the technical infrastructure, such as major application systems or infrastructure components: "Providing the SAP environment" would be a typical example.


Having identified business and supporting services, the remaining task is to create the IT service structure by determining their interrelationships ''(see Fig. 1: [https://wiki.en.it-processmaps.com/images/pdf/service_structure.pdf IT Service Structure - Example])''.
====Drawing up the service structure====


It can be seen that supporting services are often layered; for example, a service responsible for running a certain application system may need to rely on another supporting service providing a basic operation system environment.
Having identified customer and supporting services, the remaining task is to draw up the service structure by determining their interdependencies (see fig. 1: [https://wiki.en.it-processmaps.com/images/pdf/service_structure.pdf IT service structure - example (.pdf)]).


This service structure will later also serve as a valuable input to designing the [[Service Catalogue Management#Service Catalogue|Service Catalogue]].
Supporting services may be arranged in several layers; for example, a service responsible for operating a certain application system may rely on another supporting service providing a basic operation system environment.


<p>&nbsp;</p>
The service structure drawn up in this project step will be a valuable input at a later point in time, when the  [[Service Catalogue Management#Service Catalogue|Service Catalogue Management]] process is being implemented.


==== Prerequisites ====  
==Prerequisites==  


* Existing agreements and information
* Existing agreements and information
* Partners on the client-side for the definition of business services
* Partners on the client-side for the definition of customer services
 
<p>&nbsp;</p>
 
==== Results/ Deliverables ====
 
* List of business services, including at least short service descriptions and customers using the services
* List of supporting services, including at least short service descriptions and responsible Service Owners
* Service structure


<p>&nbsp;</p>
==Results/ Deliverables==


==== Success Factors ====
* List of customer services, including at least short service descriptions and an overview of which customers are using which services
* List of supporting services, including at least short service descriptions, responsible service owners and indications of whether the services are operated with internal or external resources
* Service structure, describing the service interdependencies.


* The actual signing of formal [[Service Level Management#SLA|Service Level Agreements (SLAs)]] with the clients is not yet meaningful in this early project phase: SLAs are concluded as part of [[Service Level Management]] – a process which will be implemented later on in the course of the project.
==Success factors==


* For most IT organizations, a number of approx. 5 to 15 business services should be adequate. The service structure will typically combine bundles of related service components into business services, in order to be able to negotiate complete packages with the client and simultaneously spare him from having to consider technical details: in this way for example, a service called "Provision of Client PCs" may contain
* It is not recommended at this stage to ask customers to sign [[Service Level Management#SLA|Service Level Agreements]]: SLAs should be signed at a later point in time, when the services have been formally set up.
* To keep the number of services (and service agreements) manageable, several related service components are often bundled into customer services: A typical customer service offered by IT service providers, "Provision of desktop PCs", may thus include
** Initial installation
** Initial installation
** Troubleshooting
** Troubleshooting
Line 94: Line 95:
** Hardware updates
** Hardware updates
** Etc.
** Etc.
*The IT service structure should be created in close coordination with the IT organization's clients.


* The IT service structure to be defined can only be viable if it is created in close coordination with the IT organization's clients. During the initial talks with the client-side, the IT representatives should emphasize their aim to improve service quality as the motivation for the initiative. The false impression that a possibly disadvantageous contract shall be forced onto the client must be avoided.
==Resources==
[1] IT Process Wiki: [https://wiki.en.it-processmaps.com/images/pdf/service_structure.pdf IT service structure - Template (.pdf)]


* Internal services need to be structured in such a way that it is possible to assign clear responsibilities to [[ITIL Roles#Service Owner|Service Owners]]. [[Service Level Management#OLA|Operational Level Agreements (OLAs)]] are later agreed with these Service Owners.
==Following project activity==


<p>&nbsp;</p>
&#8594; ITIL Implementation - step 3: '''[[ITIL Implementation - ITIL Roles|Selection of ITIL roles and role owners]]'''


==== Resources ====
==Notes==
[1] IT Process Wiki: [https://wiki.en.it-processmaps.com/images/pdf/service_structure.pdf IT Service Structure - Template (.pdf)]


<html>By:&#160;&#160;Andrea Kempter&#160;<a rel="author" href="https://www.linkedin.com/in/andreakempter"><img style="margin:0px 0px 0px 0px;" src="/images/bookmarking/linkedin.png" width="16" height="16" title="By: Andrea Kempter | Profile on LinkedIn" alt="Author: Andrea Kempter, IT Process Maps GbR" /></a>, IT Process Maps.
<p>&nbsp;</p>
<p>&nbsp;</p>


'''Following Project Activity''':
<p><small>
 
<span itemprop="breadcrumb" itemscope itemtype="http://schema.org/BreadcrumbList">
&#8594; ITIL Implementation - Step 3: '''[[ITIL Implementation - ITIL Roles|Selection of ITIL Roles and Role Owners]]'''
<span itemprop="itemListElement" itemscope itemtype="http://schema.org/ListItem">
 
<a itemprop="item" href="https://wiki.en.it-processmaps.com/index.php/ITIL_Implementation_-_IT_Service_Structure#Objectives">
<p>&nbsp;</p>
<span itemprop="name">Objectives</span></a>
<meta itemprop="position" content="1"></span> ›
<span itemprop="itemListElement" itemscope itemtype="http://schema.org/ListItem">
<a itemprop="item" href="https://wiki.en.it-processmaps.com/index.php/ITIL_Implementation_-_IT_Service_Structure#Description">
<span itemprop="name">Description</span></a>
<meta itemprop="position" content="2"></span> ›
<span itemprop="itemListElement" itemscope itemtype="http://schema.org/ListItem">
<a itemprop="item" href="https://wiki.en.it-processmaps.com/index.php/ITIL_Implementation_-_IT_Service_Structure#Prerequisites">
<span itemprop="name">Prerequisites</span></a>
<meta itemprop="position" content="3"></span> ›
<span itemprop="itemListElement" itemscope itemtype="http://schema.org/ListItem">
<a itemprop="item" href="https://wiki.en.it-processmaps.com/index.php/ITIL_Implementation_-_IT_Service_Structure#Results.2F_Deliverables">
<span itemprop="name">Results/ Deliverables</span></a>
<meta itemprop="position" content="4"></span> ›
<span itemprop="itemListElement" itemscope itemtype="http://schema.org/ListItem">
<a itemprop="item" href="https://wiki.en.it-processmaps.com/index.php/ITIL_Implementation_-_IT_Service_Structure#Success_factors">
<span itemprop="name">Success factors</span></a>
<meta itemprop="position" content="5"></span>
</span>
</small></p>


<html><a rel="author" href="https://plus.google.com/113316270668629760475"><img style="margin:0px 0px 0px 0px;" src="/skins/Vector/images/itpm/bookmarking/gplus.png" width="16" height="16" title="By: Andrea Kempter | Profile on Google+" alt="Author: Andrea Kempter, IT Process Maps GbR" /></a></html>
<!-- define schema.org/WebPage --> <span itemscope itemtype="https://schema.org/WebPage">
  <meta itemprop="name" content="ITIL Implementation - IT Service Structure" />
  <meta itemprop="description" content="The best way to get a clear picture on IT services is to develop a service structure, comprising both customer services and supporting services." />
  <link itemprop="url" href="https://wiki.en.it-processmaps.com/index.php/ITIL_Implementation_-_IT_Service_Structure" />
  <meta itemprop="inLanguage" content="en" />
  <link itemprop="citation" href="https://wiki.de.it-processmaps.com/index.php/ITIL-Implementierung_-_IT-Services" />
  <link itemprop="citation" href="https://wiki.es.it-processmaps.com/index.php/Implementaci%C3%B3n_de_ITIL_-_Estructura_de_servicios" />
  <meta itemprop="Headline" content="ITIL Implementation - IT Service Structure" />
  <meta itemprop="alternativeHeadline" content="Step 2: Definition of the IT Service Structure" />
  <link itemprop="primaryImageOfPage" href="https://wiki.en.it-processmaps.com/images/0/05/Thumb_IT_Services.jpg" />
  <link itemprop="author" href="https://www.linkedin.com/in/andreakempter" />
  <meta itemprop="author" content="Andrea Kempter" />
  <meta itemprop="creator copyrightHolder publisher" content="IT Process Maps" />
</span><p></html>


<!-- This page is assigned to the following categories: -->
<!-- This page is assigned to the following categories: -->
[[Category:ITIL V3]][[Category:ITIL 2011]][[Category:ITIL implementation]]
[[Category:ITIL V3]][[Category:ITIL 2011]][[Category:ITIL implementation]]
<!-- --- -->
<!-- --- -->

Latest revision as of 13:36, 5 April 2022

DE - ES - ITIL IT Service Structurediese Seite auf Deutschesta página en español
DE - ES - ITIL IT Service Structure


Infographic: How to prepare an ITIL project? ITIL implementation, step 2.
Infographic: How to define the IT service structure? - ITIL implementation, step 2.
Step 2: Definition of the IT Service Structure

 

Any ITIL initiative should start by looking at services. After all, the whole idea behind introducing ITIL best practices is to achieve a better focus on services.

 

Objectives


Description

Customer services and supporting services

To get a clear picture of the service provider's range of services, it is advisable to develop a service structure, comprising both customer services and supporting services. This reflects one of the most important principles in ITIL and other service management frameworks: Customer services (services offered to customers) are typically based on a set of supporting services (services visible only inside the service provider organization). Supporting services may be operated with the service provider's own resources or by an external party.

There is often confusion about what exactly is considered a customer service:

  • Customer services are characterized by providing value to clients, an example would be a service which allows the clients to send and receive emails and to access the internet.
  • Supporting services, in contrast, are not of direct value to clients but are needed as building blocks for customer services. The provision of a suitable network infrastructure, for example, would be a typical supporting service which is required to offer clients an internet access service.

In other words, what the customers want is reliable internet access, not a specific sort of network infrastructure (in fact it is irrelevant to the clients that some infrastructure is needed to provide them with internet access).

Creating a list of customer services

IT Service Structure
Fig. 1: IT Service Structure - Example (.PDF)

A good way to get started is creating a list of existing customer services, using - if possible - existing agreements and other documentation. If no service-related information is available, a basic list must be drawn from scratch, including at least short service descriptions and an overview of which customers use which services.

Identifying supporting services

One it is clear which business services are provided for the customers it becomes possible to identify the required supporting services.

A key objective of defining supporting services is to assign responsibilities for the delivery of those services: The service owners are responsible for delivering the services in accordance with the agreed service quality levels.

Supporting services are often closely related to certain parts of the technical infrastructure, such as major application systems or infrastructure components: "Providing the SAP environment" would be a typical example.

Drawing up the service structure

Having identified customer and supporting services, the remaining task is to draw up the service structure by determining their interdependencies (see fig. 1: IT service structure - example (.pdf)).

Supporting services may be arranged in several layers; for example, a service responsible for operating a certain application system may rely on another supporting service providing a basic operation system environment.

The service structure drawn up in this project step will be a valuable input at a later point in time, when the Service Catalogue Management process is being implemented.

Prerequisites

  • Existing agreements and information
  • Partners on the client-side for the definition of customer services

Results/ Deliverables

  • List of customer services, including at least short service descriptions and an overview of which customers are using which services
  • List of supporting services, including at least short service descriptions, responsible service owners and indications of whether the services are operated with internal or external resources
  • Service structure, describing the service interdependencies.

Success factors

  • It is not recommended at this stage to ask customers to sign Service Level Agreements: SLAs should be signed at a later point in time, when the services have been formally set up.
  • To keep the number of services (and service agreements) manageable, several related service components are often bundled into customer services: A typical customer service offered by IT service providers, "Provision of desktop PCs", may thus include
    • Initial installation
    • Troubleshooting
    • User assistance
    • Software updates
    • Hardware updates
    • Etc.
  • The IT service structure should be created in close coordination with the IT organization's clients.

Resources

[1] IT Process Wiki: IT service structure - Template (.pdf)

Following project activity

→ ITIL Implementation - step 3: Selection of ITIL roles and role owners

Notes

By:  Andrea Kempter , IT Process Maps.

 

Objectives  › Description  › Prerequisites  › Results/ Deliverables  › Success factors