YaSM Roles: Difference between revisions

From YaSM Service Management Wiki
No edit summary
No edit summary
Line 1: Line 1:
<itpmch><title>YaSM Roles | YaSM Service Management Wiki</title>
<itpmch><title>Service Management Roles | YaSM Service Management Wiki</title>
<meta name="keywords" content="yasm roles, yasm responsibilities, yasm service management roles, yasm roles and responsibilities, yasm boards" />
<meta name="keywords" content="yasm roles, service management roles, yasm responsibilities, yasm roles and responsibilities, service management responsibilities, service management boards" />
<meta name="description" content="Role objects are used in the YaSM process model and the RACI matrix to illustrate the responsibilities for whole processes or single process activities." />
<meta name="description" content="Roles are used in YaSM service management to illustrate the responsibilities for whole YaSM processes or single process activities." />
<meta property="og:url" content="https://yasm.com/wiki/en/index.php/YaSM_Roles" />
<meta property="og:title" content="Service Management Roles | YaSM Service Management Wiki" />
<meta property="og:description" content="Roles are used in YaSM service management to illustrate the responsibilities for whole YaSM processes or single process activities." />
<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-roles/Yasm-roles.jpg" />
<meta property="og:image:width" content="629" />
<meta property="og:image:height" content="455" />
<link href="https://plus.google.com/104150539756444616711/posts" rel="publisher" />
</itpmch>
</itpmch>
<html><div itemscope="itemscope" itemtype="https://schema.org/WebPage"><!-- define schema.org/WebPage --><p>
<html><a href="https://yasm.com/wiki/de/index.php/YaSM-Rollen"><img src="https://yasm.com/wiki/en/img/yasm-wiki/yasm-wiki-deutsch.png" width="48" height="30" style="float:right;" alt="auf Deutsch" title="diese Seite auf Deutsch" /></a><br style="clear:both;"/>
<a href="https://yasm.com/wiki/de/index.php/YaSM-Rollen"><img src="https://yasm.com/wiki/en/img/yasm-wiki/yasm-wiki-deutsch.png" width="48" height="30" style="float:right;" alt="auf Deutsch" title="diese Seite auf Deutsch" /></a><br style="clear:both;"/>


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


<p><span itemprop="description">Roles are used in YaSM to illustrate the responsibilities for whole YaSM service management processes or single process activities.</span>
<p><span id="md-webpage-description" itemprop="description">Roles are used in service management to illustrate the responsibilities for whole processes or single process activities. This page contains the complete list of YaSM roles and boards.</span></p>
 
<p>This page contains the complete list of <span itemprop="name Headline" content="YaSM Roles">YaSM roles</span>.</p>


<p>There's another page on the <a href="https://yasm.com/wiki/en/index.php/YaSM_RACI_Matrix" title="YaSM RACI responsibility matrix">YaSM RACI matrix</a> where you can download the complete responsibility matrix in PDF format.</html>
<p>There's another page on the <a href="https://yasm.com/wiki/en/index.php/YaSM_RACI_Matrix" title="YaSM RACI responsibility matrix">YaSM RACI matrix</a> where you can download the complete responsibility matrix in PDF format.</html>
Line 16: Line 25:
<p>&nbsp;</p>
<p>&nbsp;</p>


==Index of <span id="yasm-service-management-roles">YaSM service management roles</span>==
==Index of <span id="yasm-service-management-roles">the service management roles</span>==


<html><div itemscope itemtype="https://schema.org/ImageObject"><a href="https://yasm.com/wiki/en/img/yasm-roles/Yasm-roles.jpg" title="YaSM roles and responsibilities" itemprop="contentUrl"><img itemprop="thumbnailUrl" style="margin:5px 0px 30px 30px; float:right;" src="https://yasm.com/wiki/en/img/yasm-roles/Yasm-roles-thumb.jpg" width="396" height="294" title="Fig. 1: YaSM roles and responsibilities." alt="YaSM service management roles and responsibilities." /></a><meta itemprop="caption" content="YaSM service management roles and responsibilities."></div>
<html><div itemscope itemtype="https://schema.org/ImageObject">
<a href="https://yasm.com/wiki/en/img/yasm-roles/Yasm-roles.jpg" title="YaSM service management roles" itemprop="contentUrl">
<meta itemprop="caption" content="YaSM service management roles and responsibilities." />
<meta itemprop="width" content="629" />
<meta itemprop="height" content="455" />
<meta itemprop="keywords" content="service management roles" />
<meta itemprop="keywords" content="yasm roles" />
<img itemprop="thumbnailUrl" style="margin:5px 0px 30px 30px; float:right;" src="https://yasm.com/wiki/en/img/yasm-roles/Yasm-roles-thumb.jpg" width="396" height="294" title="YaSM service management roles" alt="Descriptions of the YaSM service management roles and responsibilities." /></a></div>


<div itemscope="itemscope" itemtype="https://schema.org/ItemList"><!-- define schema.org/ItemList -->
<p>The following table contains short descriptions or definitions of the <i>YaSM service management roles</i> in alphabetical order.</p><p>&#160;</p>
<meta itemprop="itemListOrder" content="Ascending" />
<p><span itemprop="name" content="YaSM roles: short descriptions or definitions of the YaSM service management roles">The following table contains short descriptions or definitions of the <i>YaSM service management roles</i> in alphabetical order.</span></p><p>&#160;</p>
<p><i>Note: Throughout this wiki, &quot;he&quot; is used as a reference to an indefinite person, meaning &quot;she&quot; or &quot;he&quot;.</i></p><br style="clear:both;"/>
<p><i>Note: Throughout this wiki, &quot;he&quot; is used as a reference to an indefinite person, meaning &quot;she&quot; or &quot;he&quot;.</i></p><br style="clear:both;"/>
<p><b><span id="1st-level-support" itemprop="itemListElement">1st level support</span></b></p>
 
<ul><li itemprop="description">The responsibility of 1st level support is to register and classify received incidents and to undertake an immediate effort in order to restore a failed service as quickly as possible or to fulfill a service request. If no immediate solution can be achieved, 1st level support will transfer the incident to expert technical support agents or groups (2nd level support). 1st level support also keeps users informed about their incidents' status at agreed intervals. In some organizations, 1st level support is referred to as "help desk" or "service desk".</li></ul>
<div itemid="https://yasm.com/wiki/en/index.php/YaSM_Roles#1st-level-support" itemscope itemtype="https://schema.org/OrganizationRole">
<dl id="1st-level-support"><dt itemprop="name">1st level support</dt>
<dd itemprop="description">The responsibility of 1st level support is to register and classify received incidents and to undertake an immediate effort in order to restore a failed service as quickly as possible or to fulfill a service request. If no immediate solution can be achieved, 1st level support will transfer the incident to expert technical support agents or groups (2nd level support). 1st level support also keeps users informed about their incidents' status at agreed intervals. In some organizations, 1st level support is referred to as 'help desk' or 'service desk'.</dd></dl></div>
<p><br /></p>
<p><br /></p>
<p><b><span id="2nd-level-support" itemprop="itemListElement">2nd level support</span></b></p>
<div itemid="https://yasm.com/wiki/en/index.php/YaSM_Roles#2nd-level-support" itemscope itemtype="https://schema.org/OrganizationRole">
<ul><li itemprop="description">2nd Level Support takes over incidents which cannot be resolved immediately with the means of 1st level support. If necessary, it will request external support, e.g. from software or hardware manufacturers (often referred to as 3rd level support). The aim is to restore a failed service as quickly as possible.</li></ul>
<dl id="2nd-level-support"><dt itemprop="name">2nd level support</dt>
<dd itemprop="description">2nd Level Support takes over incidents which cannot be resolved immediately with the means of 1st level support. If necessary, it will request external support, e.g. from software or hardware manufacturers (often referred to as 3rd level support). The aim is to restore a failed service as quickly as possible.</dd></dl></div>
<p><br /></p>
<p><br /></p>
<p><b><span id="Application-System-developer" itemprop="itemListElement">Application/ System developer</span></b></p>
<div itemid="https://yasm.com/wiki/en/index.php/YaSM_Roles#Application-System-developer" itemscope itemtype="https://schema.org/OrganizationRole">
<ul><li itemprop="description">Developers are responsible for creating the applications and systems which support the service provider's range of services. This includes the development and maintenance of custom applications as well as the customization of products from software vendors.
<meta itemprop="alternateName" content="Application developer" />
</li></ul>
<meta itemprop="alternateName" content="System developer" />
<dl id="Application-System-developer" itemprop="name" content="Developer"><dt>Application/ System developer</dt>
<dd itemprop="description">Developers are responsible for creating the applications and systems which support the service provider's range of services. This includes the development and maintenance of custom applications as well as the customization of products from software vendors.
</dd></dl></div>
<p><br /></p>
<p><br /></p>
<p><b><span id="CAB" itemprop="itemListElement">Change advisory board (CAB)</span></b></p>
<div itemid="https://yasm.com/wiki/en/index.php/YaSM_Roles#CAB" itemscope itemtype="https://schema.org/OrganizationRole">
<ul><li itemprop="description">A group of people that advises the change manager in the assessment, prioritization and scheduling of changes. The composition of this will vary depending on the nature of the changes to be assessed. It is usually made up of representatives from all areas within the service provider organization, the business, and third parties such as suppliers.</li></ul>
<meta itemprop="alternateName" content="CAB" />
<dl id="CAB" itemprop="name" content="Change advisory board"><dt>Change advisory board (CAB)</dt>
<dd itemprop="description">A group of people that advises the change manager in the assessment, prioritization and scheduling of changes. The composition of this will vary depending on the nature of the changes to be assessed. It is usually made up of representatives from all areas within the service provider organization, the business, and third parties such as suppliers.</dd></dl></div>
<p><br /></p>
<p><br /></p>
<p><b><span id="Change-manager" itemprop="itemListElement">Change manager</span></b></p>
<div itemid="https://yasm.com/wiki/en/index.php/YaSM_Roles#Change-manager" itemscope itemtype="https://schema.org/OrganizationRole">
<ul><li itemprop="description">The Change manager controls all changes across their lifecycle. His primary objective is to enable beneficial changes to be made, with minimum disruption to services. For important changes, the change manager will refer the authorization of changes to the change advisory board (CAB).</li></ul>
<dl id="Change-manager"><dt itemprop="name">Change manager</dt>
<dd itemprop="description">The Change manager controls all changes across their lifecycle. His primary objective is to enable beneficial changes to be made, with minimum disruption to services. For important changes, the change manager will refer the authorization of changes to the change advisory board (CAB).</dd></dl></div>
<p><br /></p>
<p><br /></p>
<p><b><span id="Change-owner" itemprop="itemListElement">Change owner</span></b></p>
<div itemid="https://yasm.com/wiki/en/index.php/YaSM_Roles#Change-owner" itemscope itemtype="https://schema.org/OrganizationRole">
<ul><li itemprop="description">Every change has a responsible change owner, holding the budget for its implementation. In many cases the change owner is identical with the individual submitting a request for change. Many changes are owned by service management roles (e.g. 1st or 2nd level support or a service owner).</li></ul>
<dl id="Change-owner"><dt itemprop="name">Change owner</dt>
<dd itemprop="description">Every change has a responsible change owner, holding the budget for its implementation. In many cases the change owner is identical with the individual submitting a request for change. Many changes are owned by service management roles (e.g. 1st or 2nd level support or a service owner).</dd></dl></div>
<p><br /></p>
<p><br /></p>
<p><b><span id="Compliance-manager" itemprop="itemListElement">Compliance manager</span></b></p>
<div itemid="https://yasm.com/wiki/en/index.php/YaSM_Roles#Compliance-manager" itemscope itemtype="https://schema.org/OrganizationRole">
<ul><li itemprop="description">The compliance manager's responsibility is to ensure that standards and guidelines are followed. In particular, this role ensures compliance with internal policies and external legal requirements.</li></ul>
<dl id="Compliance-manager"><dt itemprop="name">Compliance manager</dt>
<dd itemprop="description">The compliance manager's responsibility is to ensure that standards and guidelines are followed. In particular, this role ensures compliance with internal policies and external legal requirements.</dd></dl></div>
<p><br /></p>
<p><br /></p>
<p><b><span id="Configuration-manager" itemprop="itemListElement">Configuration manager</span></b></p>
<div itemid="https://yasm.com/wiki/en/index.php/YaSM_Roles#Configuration-manager" itemscope itemtype="https://schema.org/OrganizationRole">
<ul><li itemprop="description">The configuration manager is responsible for maintaining information about the infrastructure required to deliver the services. To this end he/ she maintains a logical model describing the components of the infrastructure and their associations.</li></ul>
<dl id="Configuration-manager"><dt itemprop="name">Configuration manager</dt>
<dd itemprop="description">The configuration manager is responsible for maintaining information about the infrastructure required to deliver the services. To this end he/ she maintains a logical model describing the components of the infrastructure and their associations.</dd></dl></div>
<p><br /></p>
<p><br /></p>
<p><b><span id="Customer" itemprop="itemListElement">Customer</span></b></p>
<div itemid="https://yasm.com/wiki/en/index.php/YaSM_Roles#Customer" itemscope itemtype="https://schema.org/OrganizationRole">
<ul><li itemprop="description">Someone who buys services. The customer of a service provider is the person or party who agrees to use a service with specified service properties at a defined price.</li></ul>
<dl id="Customer"><dt itemprop="name">Customer</dt>
<dd itemprop="description">Someone who buys services. The customer of a service provider is the person or party who agrees to use a service with specified service properties at a defined price.</dd></dl></div>
<p><br /></p>
<p><br /></p>
<p><b><span id="Customer-relationship-manager" itemprop="itemListElement">Customer relationship manager</span></b></p>
<div itemid="https://yasm.com/wiki/en/index.php/YaSM_Roles#Customer-relationship-manager" itemscope itemtype="https://schema.org/OrganizationRole">
<ul><li itemprop="description">The customer relationship manager is responsible for maintaining a positive relationship with customers. This role identifies customer needs and makes this information available to the service provider organization, so that the service provider is able to offer an appropriate range of services.</li></ul>
<dl id="Customer-relationship-manager"><dt itemprop="name">Customer relationship manager</dt>
<dd itemprop="description">The customer relationship manager is responsible for maintaining a positive relationship with customers. This role identifies customer needs and makes this information available to the service provider organization, so that the service provider is able to offer an appropriate range of services.</dd></dl></div>
<p><br /></p>
<p><br /></p>
<p><b><span id="ECAB" itemprop="itemListElement">Emergency change advisory board (ECAB)</span></b></p>
<div itemid="https://yasm.com/wiki/en/index.php/YaSM_Roles#ECAB" itemscope itemtype="https://schema.org/OrganizationRole">
<ul><li itemprop="description">A sub-set of the change advisory board that makes decisions about high-impact emergency changes. Membership of the ECAB is typically decided at the time an emergency change must be assessed and depends on the nature of the change.</li></ul>
<meta itemprop="alternateName" content="ECAB" />
<dl id="ECAB" itemprop="name" content="Emergency change advisory board"><dt>Emergency change advisory board (ECAB)</dt>
<dd itemprop="description">A sub-set of the change advisory board that makes decisions about high-impact emergency changes. Membership of the ECAB is typically decided at the time an emergency change must be assessed and depends on the nature of the change.</dd></dl></div>
<p><br /></p>
<p><br /></p>
<p><b><span id="Financial-manager" itemprop="itemListElement">Financial manager</span></b></p>
<div itemid="https://yasm.com/wiki/en/index.php/YaSM_Roles#Financial-manager" itemscope itemtype="https://schema.org/OrganizationRole">
<ul><li itemprop="description">The financial manager is responsible for managing the service provider's budgeting, accounting and charging requirements.</li></ul>
<dl id="Financial-manager"><dt itemprop="name">Financial manager</dt>
<dd itemprop="description">The financial manager is responsible for managing the service provider's budgeting, accounting and charging requirements.</dd></dl></div>
<p><br /></p>
<p><br /></p>
<p><b><span id="Human-resources-manager" itemprop="itemListElement">Human resources manager</span></b></p>
<div itemid="https://yasm.com/wiki/en/index.php/YaSM_Roles#Human-resources-manager" itemscope itemtype="https://schema.org/OrganizationRole">
<ul><li itemprop="description">This role ensures that the service provider employs the right balance of staff in terms of skills and experience. The human resources (HR) manager is also responsible for identifying gaps in the organization's current set of skills and for organizing any required skill development initiatives, in line with the service provider's objectives.</li></ul>
<meta itemprop="alternateName" content="HR manager" />
<dl id="Human-resources-manager"><dt itemprop="name">Human resources manager</dt>
<dd itemprop="description">This role ensures that the service provider employs the right balance of staff in terms of skills and experience. The human resources (HR) manager is also responsible for identifying gaps in the organization's current set of skills and for organizing any required skill development initiatives, in line with the service provider's objectives.</dd></dl></div>
<p><br /></p>
<p><br /></p>
<p><b><span id="Incident-manager" itemprop="itemListElement">Incident manager</span></b></p>
<div itemid="https://yasm.com/wiki/en/index.php/YaSM_Roles#Incident-manager" itemscope itemtype="https://schema.org/OrganizationRole">
<ul><li itemprop="description">The incident manager is responsible for the effective implementation of the incident resolution process and carries out the corresponding reporting. He represents the first stage of escalation for incidents, should these not be resolvable within the agreed time frames in the relevant service levels.</li></ul>
<dl id="Incident-manager"><dt itemprop="name">Incident manager</dt>
<dd itemprop="description">The incident manager is responsible for the effective implementation of the incident resolution process and carries out the corresponding reporting. He represents the first stage of escalation for incidents, should these not be resolvable within the agreed time frames in the relevant service levels.</dd></dl></div>
<p><br /></p>
<p><br /></p>
<p><b><span id="Major-incident-team" itemprop="itemListElement">Major incident team</span></b></p>
<div itemid="https://yasm.com/wiki/en/index.php/YaSM_Roles#Major-incident-team" itemscope itemtype="https://schema.org/OrganizationRole">
<ul><li itemprop="description">A dynamically established team of managers and technical experts, usually under the leadership of the incident manager, set up to concentrate on the resolution of a major incident.</li></ul>
<dl id="Major-incident-team"><dt itemprop="name">Major incident team</dt>
<dd itemprop="description">A dynamically established team of managers and technical experts, usually under the leadership of the incident manager, set up to concentrate on the resolution of a major incident.</dd></dl></div>
<p><br /></p>
<p><br /></p>
<p><b><span id="Operations-manager" itemprop="itemListElement">Operations manager</span></b></p>
<div itemid="https://yasm.com/wiki/en/index.php/YaSM_Roles#Operations-manager" itemscope itemtype="https://schema.org/OrganizationRole">
<ul><li itemprop="description">An operations manager will be needed to take overall responsibility for operating a service. For instance, this role will ensure that all day-to-day operational activities are carried out in a timely and reliable way.</li></ul>
<dl id="Operations-manager"><dt itemprop="name">Operations manager</dt>
<dd itemprop="description">An operations manager will be needed to take overall responsibility for operating a service. For instance, this role will ensure that all day-to-day operational activities are carried out in a timely and reliable way.</dd></dl></div>
<p><br /></p>
<p><br /></p>
<p><b><span id="Operator" itemprop="itemListElement">Operator</span></b></p>
<div itemid="https://yasm.com/wiki/en/index.php/YaSM_Roles#Operator" itemscope itemtype="https://schema.org/OrganizationRole">
<ul><li itemprop="description">Operators are the staff who perform the day-to-day operational activities. Typical responsibilities include: Performing backups, ensuring that scheduled jobs are performed, installing standard equipment in the data center.</li></ul>
<dl id="Operator"><dt itemprop="name">Operator</dt>
<dd itemprop="description">Operators are the staff who perform the day-to-day operational activities. Typical responsibilities include: Performing backups, ensuring that scheduled jobs are performed, installing standard equipment in the data center.</dd></dl></div>
<p><br /></p>
<p><br /></p>
<p><b><span id="Problem-manager" itemprop="itemListElement">Problem manager</span></b></p>
<div itemid="https://yasm.com/wiki/en/index.php/YaSM_Roles#Problem-manager" itemscope itemtype="https://schema.org/OrganizationRole">
<ul><li itemprop="description">The problem manager is responsible for managing the lifecycle of all problems, where the primary objective is to prevent incidents from happening if possible, and to minimize the impact of incidents that cannot be prevented. Apart from resolving the underlying causes of (potential) incidents, the problem manager often provides workarounds while a full solution is not yet available.</li></ul>
<dl id="Problem-manager"><dt itemprop="name">Problem manager</dt>
<dd itemprop="description">The problem manager is responsible for managing the lifecycle of all problems, where the primary objective is to prevent incidents from happening if possible, and to minimize the impact of incidents that cannot be prevented. Apart from resolving the underlying causes of (potential) incidents, the problem manager often provides workarounds while a full solution is not yet available.</dd></dl></div>
<p><br /></p>
<p><br /></p>
<p><b><span id="Process-owner" itemprop="itemListElement">Process owner</span></b></p>
<div itemid="https://yasm.com/wiki/en/index.php/YaSM_Roles#Process-owner" itemscope itemtype="https://schema.org/OrganizationRole">
<ul><li itemprop="description">This role ensures that the processes it owns are fit for purpose. The process owner’s responsibilities include the design and continual improvement of the process. In larger organizations there might be separate process owner and process manager roles, where the process manager has responsibility for the operational management of a process.</li></ul>
<dl id="Process-owner"><dt itemprop="name">Process owner</dt>
<dd itemprop="description">This role ensures that the processes it owns are fit for purpose. The process owner’s responsibilities include the design and continual improvement of the process. In larger organizations there might be separate process owner and process manager roles, where the process manager has responsibility for the operational management of a process.</dd></dl></div>
<p><br /></p>
<p><br /></p>
<p><b><span id="Project-board" itemprop="itemListElement">Project board</span></b></p>
<div itemid="https://yasm.com/wiki/en/index.php/YaSM_Roles#Project-board" itemscope itemtype="https://schema.org/OrganizationRole">
<ul><li itemprop="description">The project board is the decision-making body of the project. The project board typically consists of members of the management board and representatives of the different project stakeholders. It is important that the project board has real authority to take decisions.</li></ul>
<dl id="Project-board"><dt itemprop="name">Project board</dt>
<dd itemprop="description">The project board is the decision-making body of the project. The project board typically consists of members of the management board and representatives of the different project stakeholders. It is important that the project board has real authority to take decisions.</dd></dl></div>
<p><br /></p>
<p><br /></p>
<p><b><span id="Project-manager" itemprop="itemListElement">Project manager</span></b></p>
<div itemid="https://yasm.com/wiki/en/index.php/YaSM_Roles#Project-manager" itemscope itemtype="https://schema.org/OrganizationRole">
<ul><li itemprop="description">The project manager is responsible for directing a project, which includes responsibility for delivering the agreed project deliverables within the agreed time and budget.</li></ul>
<dl id="Project-manager"><dt itemprop="name">Project manager</dt>
<dd itemprop="description">The project manager is responsible for directing a project, which includes responsibility for delivering the agreed project deliverables within the agreed time and budget.</dd></dl></div>
<p><br /></p>
<p><br /></p>
<p><b><span id="Project-owner" itemprop="itemListElement">Project owner</span></b></p>
<div itemid="https://yasm.com/wiki/en/index.php/YaSM_Roles#Project-owner" itemscope itemtype="https://schema.org/OrganizationRole">
<ul><li itemprop="description">The project owner is the driving force behind a project. Typically, this role will prepare a business case and apply for a budget before a project is set up. As many projects are related to improving services, service owners will often act as project owners.</li></ul>
<dl id="Project-owner"><dt itemprop="name">Project owner</dt>
<dd itemprop="description">The project owner is the driving force behind a project. Typically, this role will prepare a business case and apply for a budget before a project is set up. As many projects are related to improving services, service owners will often act as project owners.</dd></dl></div>
<p><br /></p>
<p><br /></p>
<p><b><span id="Security-manager" itemprop="itemListElement">Security manager</span></b></p>
<div itemid="https://yasm.com/wiki/en/index.php/YaSM_Roles#Security-manager" itemscope itemtype="https://schema.org/OrganizationRole">
<ul><li itemprop="description">The security manager is responsible for the service provider's and its customers' security. This includes responsibility for the security of information and data being processed by the service provider.</li></ul>
<dl id="Security-manager"><dt itemprop="name">Security manager</dt>
<dd itemprop="description">The security manager is responsible for the service provider's and its customers' security. This includes responsibility for the security of information and data being processed by the service provider.</dd></dl></div>
<p><br /></p>
<p><br /></p>
<p><b><span id="Service-continuity-manager" itemprop="itemListElement">Service continuity manager</span></b></p>
<div itemid="https://yasm.com/wiki/en/index.php/YaSM_Roles#Service-continuity-manage" itemscope itemtype="https://schema.org/OrganizationRole">
<ul><li itemprop="description">The service continuity manager is responsible for managing risks that could seriously impact the service provider's services. In particular, this role ensures that the service provider can provide minimum agreed service levels in cases of disaster.</li></ul>
<dl id="Service-continuity-manager"><dt itemprop="name">Service continuity manager</dt>
<dd itemprop="description">The service continuity manager is responsible for managing risks that could seriously impact the service provider's services. In particular, this role ensures that the service provider can provide minimum agreed service levels in cases of disaster.</dd></dl></div>
<p><br /></p>
<p><br /></p>
<p><b><span id="Service-design-manager" itemprop="itemListElement">Service design manager</span></b></p>
<div itemid="https://yasm.com/wiki/en/index.php/YaSM_Roles#Service-design-manager" itemscope itemtype="https://schema.org/OrganizationRole">
<ul><li itemprop="description">The service design manager is responsible for the detailed specification of the requirements for new or changed services, as well as identifying a suitable approach for their implementation.</li></ul>
<dl id="Service-design-manager"><dt itemprop="name">Service design manager</dt>
<dd itemprop="description">The service design manager is responsible for the detailed specification of the requirements for new or changed services, as well as identifying a suitable approach for their implementation.</dd></dl></div>
<p><br /></p>
<p><br /></p>
<p><b><span id="Service-implementation-manager" itemprop="itemListElement">Service implementation manager</span></b></p>
<div itemid="https://yasm.com/wiki/en/index.php/YaSM_Roles#Service-implementation-manager" itemscope itemtype="https://schema.org/OrganizationRole">
<ul><li itemprop="description">The service implementation manager is responsible for coordinating the implementation of new or significantly changed services. In particular, the service implementation manager ensures that all service infrastructure and other required capabilities are properly tested and deployed.</li></ul>
<dl id="Service-implementation-manager"><dt itemprop="name">Service implementation manager</dt>
<dd itemprop="description">The service implementation manager is responsible for coordinating the implementation of new or significantly changed services. In particular, the service implementation manager ensures that all service infrastructure and other required capabilities are properly tested and deployed.</dd></dl></div>
<p><br /></p>
<p><br /></p>
<p><b><span id="Service-improvement-manager" itemprop="itemListElement">Service improvement manager</span></b></p>
<div itemid="https://yasm.com/wiki/en/index.php/YaSM_Roles#Service-improvement-manager" itemscope itemtype="https://schema.org/OrganizationRole">
<ul><li itemprop="description">The service improvement manager is responsible for managing improvements to the service provider's range of services. In particular, this role will identify improvement potentials by analyzing service quality reports and performing service reviews.</li></ul>
<dl id="Service-improvement-manager"><dt itemprop="name">Service improvement manager</dt>
<dd itemprop="description">The service improvement manager is responsible for managing improvements to the service provider's range of services. In particular, this role will identify improvement potentials by analyzing service quality reports and performing service reviews.</dd></dl></div>
<p><br /></p>
<p><br /></p>
<p><b><span id="Service-owner" itemprop="itemListElement">Service owner</span></b></p>
<div itemid="https://yasm.com/wiki/en/index.php/YaSM_Roles#Service-owner" itemscope itemtype="https://schema.org/OrganizationRole">
<ul><li itemprop="description">The service owner holds responsibility for delivering a particular service. In the case of a customer-facing business service, the service owner is responsible for delivering the service as specified in the customer agreement. In the case of supporting services, the service owner will often lead a team of technical specialists or an internal support unit.</li></ul>
<dl id="Service-owner"><dt itemprop="name">Service owner</dt>
<dd itemprop="description">The service owner holds responsibility for delivering a particular service. In the case of a customer-facing business service, the service owner is responsible for delivering the service as specified in the customer agreement. In the case of supporting services, the service owner will often lead a team of technical specialists or an internal support unit.</dd></dl></div>
<p><br /></p>
<p><br /></p>
<p><b><span id="Service-portfolio-manager" itemprop="itemListElement">Service portfolio manager</span></b></p>
<div itemid="https://yasm.com/wiki/en/index.php/YaSM_Roles#Service-portfolio-manager" itemscope itemtype="https://schema.org/OrganizationRole">
<ul><li itemprop="description">The service portfolio manager is responsible for managing the service provider's range of services. This includes making sure that the information in the service portfolio and any service definitions are accurate and up-to-date. The service portfolio manager will also support the steering group during strategic assessments of the service portfolio.</li></ul>
<dl id="Service-portfolio-manager"><dt itemprop="name">Service portfolio manager</dt>
<dd itemprop="description">The service portfolio manager is responsible for managing the service provider's range of services. This includes making sure that the information in the service portfolio and any service definitions are accurate and up-to-date. The service portfolio manager will also support the steering group during strategic assessments of the service portfolio.</dd></dl></div>
<p><br /></p>
<p><br /></p>
<p><b><span id="Service-request-fulfillment-group" itemprop="itemListElement">Service request fulfillment group</span></b></p>
<div itemid="https://yasm.com/wiki/en/index.php/YaSM_Roles#Service-request-fulfillment-group" itemscope itemtype="https://schema.org/OrganizationRole">
<ul><li itemprop="description">Service request fulfillment groups specialize in the fulfillment of certain types of service requests. Typically, 1st level support will process simpler requests, while others are forwarded to the specialized fulfillment groups.</li></ul>
<dl id="Service-request-fulfillment-group"><dt itemprop="name">Service request fulfillment group</dt>
<dd itemprop="description">Service request fulfillment groups specialize in the fulfillment of certain types of service requests. Typically, 1st level support will process simpler requests, while others are forwarded to the specialized fulfillment groups.</dd></dl></div>
<p><br /></p>
<p><br /></p>
<p><b><span id="Service-strategy-manager" itemprop="itemListElement">Service strategy manager</span></b></p>
<div itemid="https://yasm.com/wiki/en/index.php/YaSM_Roles#Service-strategy-manager" itemscope itemtype="https://schema.org/OrganizationRole">
<ul><li itemprop="description">The service strategy manager supports the steering group in producing and maintaining the service provider's strategy. This role is also responsible for communicating and implementing the service strategy.</li></ul>
<dl id="Service-strategy-manager"><dt itemprop="name">Service strategy manager</dt>
<dd itemprop="description">The service strategy manager supports the steering group in producing and maintaining the service provider's strategy. This role is also responsible for communicating and implementing the service strategy.</dd></dl></div>
<p><br /></p>
<p><br /></p>
<p><b><span id="SMS-manager" itemprop="itemListElement">SMS manager</span></b></p>
<div itemid="https://yasm.com/wiki/en/index.php/YaSM_Roles#SMS-manager" itemscope itemtype="https://schema.org/OrganizationRole">
<ul><li itemprop="description">The SMS manager is responsible for setting up and maintaining the service management system. This role plays a key part in managing the service management processes and policies, ensuring that all elements of the SMS cooperate in a seamless way to achieve the service provider's objectives.</li></ul>
<dl id="SMS-manager"><dt itemprop="name">SMS manager</dt>
<dd itemprop="description">The SMS manager is responsible for setting up and maintaining the service management system. This role plays a key part in managing the service management processes and policies, ensuring that all elements of the SMS cooperate in a seamless way to achieve the service provider's objectives.</dd></dl></div>
<p><br /></p>
<p><br /></p>
<p><b><span id="Steering-group" itemprop="itemListElement">Steering group</span></b></p>
<div itemid="https://yasm.com/wiki/en/index.php/YaSM_Roles#Steering-group" itemscope itemtype="https://schema.org/OrganizationRole">
<ul><li itemprop="description">The steering group sets the direction and strategy for the service provider. It typically consists of members of top and middle-level management. The steering group has ultimate responsibility for the range of services offered by the service provider. As such, it also authorizes initiatives for the introduction of new or the enhancement of existing services. It is important that the steering group has real authority to take decisions.</li></ul>
<dl id="Steering-group"><dt itemprop="name">Steering group</dt>
<dd itemprop="description">The steering group sets the direction and strategy for the service provider. It typically consists of members of top and middle-level management. The steering group has ultimate responsibility for the range of services offered by the service provider. As such, it also authorizes initiatives for the introduction of new or the enhancement of existing services. It is important that the steering group has real authority to take decisions.</dd></dl></div>
<p><br /></p>
<p><br /></p>
<p><b><span id="Supplier-manager" itemprop="itemListElement">Supplier manager</span></b></p>
<div itemid="https://yasm.com/wiki/en/index.php/YaSM_Roles#Supplier-manager" itemscope itemtype="https://schema.org/OrganizationRole">
<ul><li itemprop="description">The supplier manager is responsible for ensuring that value for money is obtained from all suppliers. This role makes sure that the contracts with external suppliers support the service provider's needs, and that all suppliers meet their contractual commitments.</li></ul>
<dl id="Supplier-manager"><dt itemprop="name">Supplier manager</dt>
<dd itemprop="description">The supplier manager is responsible for ensuring that value for money is obtained from all suppliers. This role makes sure that the contracts with external suppliers support the service provider's needs, and that all suppliers meet their contractual commitments.</dd></dl></div>
<p><br /></p>
<p><br /></p>
<p><b><span id="Technical-domain-expert" itemprop="itemListElement">Technical domain expert</span></b></p>
<div itemid="https://yasm.com/wiki/en/index.php/YaSM_Roles#Technical-domain-expert" itemscope itemtype="https://schema.org/OrganizationRole">
<ul><li itemprop="description">The technical domain expert provides technical expertise and support in various service management processes. There is typically one expert or team of experts for every key technology area or type of application or system. This role plays an important part in the technical aspects of designing, testing, operating and improving services.</li></ul>
<dl id="Technical-domain-expert"><dt itemprop="name">Technical domain expert</dt>
<dd itemprop="description">The technical domain expert provides technical expertise and support in various service management processes. There is typically one expert or team of experts for every key technology area or type of application or system. This role plays an important part in the technical aspects of designing, testing, operating and improving services.</dd></dl></div>
<p><br /></p>
<p><br /></p>
<p><b><span id="Test-manager" itemprop="itemListElement">Test manager</span></b></p>
<div itemid="https://yasm.com/wiki/en/index.php/YaSM_Roles#Test-manager" itemscope itemtype="https://schema.org/OrganizationRole">
<ul><li itemprop="description">The test manager ensures that newly implemented services deliver the required outcomes, and verifies that all preconditions for operating a new service have been created.</li></ul>
<dl id="Test-manager"><dt itemprop="name">Test manager</dt>
</div><!-- end of schema.org/ItemList --><p></html>
<dd itemprop="description">The test manager ensures that newly implemented services deliver the required outcomes, and verifies that all preconditions for operating a new service have been created.</dd></dl></div>
<p></html>


<p>&nbsp;</p>
<p>&nbsp;</p>
Line 142: Line 198:
<p>&nbsp;</p>
<p>&nbsp;</p>


==[ Infobox ]==
== Notes ==
Is based on: YaSM service management role definitions from the from the [https://yasm.com/en/products/yasm-process-map YaSM Process Map].


<html><table class="wikitable">
<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.
<tr>
 
<td>Link to this page:</td>
<p>&nbsp;</p>
<td><a itemprop="url" href="https://yasm.com/wiki/en/index.php/YaSM_Roles">https://yasm.com/wiki/en/index.php/YaSM_Roles</a></td>
</tr>
<tr>
<td>Languages:</td>
<td><span itemprop="inLanguage" content="en">English</span> | <span><a itemprop="citation" class="external TEXT" href="https://yasm.com/wiki/de/index.php/YaSM-Rollen" title="YaSM-Rollen">Deutsch</a></span></td>
</tr>
<tr>
<td>Image:</td>
<td style="vertical-align:top"><a itemprop="primaryImageOfPage" href="https://yasm.com/wiki/en/img/yasm-roles/Yasm-roles.jpg" title="YaSM service management roles.">YaSM roles and responsibilities (.JPG)</a></td>
</tr>
<tr>
<td>Is based on:</td>
<td style="vertical-align:top">YaSM role definitions from the <a itemprop="isBasedOnUrl" href="https://yasm.com/en/products/yasm-process-map" title="Role definitions from the YaSM Process Map" class="external text">YaSM Process Map</a></td>
</tr>
<tr>
<td>Author | Contributor:</td>
<td><span itemprop="author">Stefan Kempter</span>&nbsp;<a rel="author" href="https://plus.google.com/111925560448291102517"><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> &nbsp; and <span itemprop="contributor">Andrea Kempter</span>&nbsp;<a href="https://plus.google.com/113316270668629760475"><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> &nbsp; - &nbsp; <span itemprop="creator copyrightHolder publisher">IT Process Maps</span>.</td>
</tr>
</table>


<p><small>
<p><small>
Line 181: Line 219:
</span>
</span>
</small></p>
</small></p>
</div><!-- end of schema.org/WebPage --><p></html>
 
<!-- define schema.org/WebPage --> <span itemid="https://yasm.com/wiki/en/index.php/YaSM_Roles" itemscope itemtype="https://schema.org/WebPage" itemref="md-webpage-description">
  <meta itemprop="name Headline" content="YaSM Roles" />
  <meta itemprop="alternativeHeadline" content="Service Management Roles" />
  <link itemprop="url" href="https://yasm.com/wiki/en/index.php/YaSM_Roles" />
  <link itemprop="primaryImageOfPage" href="https://yasm.com/wiki/en/img/yasm-roles/Yasm-roles.jpg" />
  <span itemprop="image" itemscope itemtype="https://schema.org/ImageObject" >
    <meta itemprop="url" content="https://yasm.com/wiki/en/img/yasm-roles/Yasm-roles.jpg" />
    <meta itemprop="width" content="629" />
    <meta itemprop="height" content="455" />
  </span> 
  <meta itemprop="significantLinks" content="https://yasm.com/wiki/en/index.php/YaSM_RACI_Matrix" />
  <meta itemprop="isBasedOnUrl" content="https://yasm.com/en/products/yasm-process-map" />
  <meta itemprop="inLanguage" content="en" />
  <link  itemprop="citation" href="https://yasm.com/wiki/de/index.php/YaSM-Rollen" />
  <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" />
</span><p></html>


<!-- This page is assigned to the following categories: -->
<!-- This page is assigned to the following categories: -->
[[Category:YaSM role|!]]
[[Category:YaSM role|!]]
<!-- --- -->
<!-- --- -->

Revision as of 13:59, 15 November 2016

auf Deutsch

 

Roles are used in service management to illustrate the responsibilities for whole processes or single process activities. This page contains the complete list of YaSM roles and boards.

There's another page on the YaSM RACI matrix where you can download the complete responsibility matrix in PDF format.

 

Index of the service management roles

The following table contains short descriptions or definitions of the YaSM service management roles in alphabetical order.

 

Note: Throughout this wiki, "he" is used as a reference to an indefinite person, meaning "she" or "he".


1st level support
The responsibility of 1st level support is to register and classify received incidents and to undertake an immediate effort in order to restore a failed service as quickly as possible or to fulfill a service request. If no immediate solution can be achieved, 1st level support will transfer the incident to expert technical support agents or groups (2nd level support). 1st level support also keeps users informed about their incidents' status at agreed intervals. In some organizations, 1st level support is referred to as 'help desk' or 'service desk'.


2nd level support
2nd Level Support takes over incidents which cannot be resolved immediately with the means of 1st level support. If necessary, it will request external support, e.g. from software or hardware manufacturers (often referred to as 3rd level support). The aim is to restore a failed service as quickly as possible.


Application/ System developer
Developers are responsible for creating the applications and systems which support the service provider's range of services. This includes the development and maintenance of custom applications as well as the customization of products from software vendors.


Change advisory board (CAB)
A group of people that advises the change manager in the assessment, prioritization and scheduling of changes. The composition of this will vary depending on the nature of the changes to be assessed. It is usually made up of representatives from all areas within the service provider organization, the business, and third parties such as suppliers.


Change manager
The Change manager controls all changes across their lifecycle. His primary objective is to enable beneficial changes to be made, with minimum disruption to services. For important changes, the change manager will refer the authorization of changes to the change advisory board (CAB).


Change owner
Every change has a responsible change owner, holding the budget for its implementation. In many cases the change owner is identical with the individual submitting a request for change. Many changes are owned by service management roles (e.g. 1st or 2nd level support or a service owner).


Compliance manager
The compliance manager's responsibility is to ensure that standards and guidelines are followed. In particular, this role ensures compliance with internal policies and external legal requirements.


Configuration manager
The configuration manager is responsible for maintaining information about the infrastructure required to deliver the services. To this end he/ she maintains a logical model describing the components of the infrastructure and their associations.


Customer
Someone who buys services. The customer of a service provider is the person or party who agrees to use a service with specified service properties at a defined price.


Customer relationship manager
The customer relationship manager is responsible for maintaining a positive relationship with customers. This role identifies customer needs and makes this information available to the service provider organization, so that the service provider is able to offer an appropriate range of services.


Emergency change advisory board (ECAB)
A sub-set of the change advisory board that makes decisions about high-impact emergency changes. Membership of the ECAB is typically decided at the time an emergency change must be assessed and depends on the nature of the change.


Financial manager
The financial manager is responsible for managing the service provider's budgeting, accounting and charging requirements.


Human resources manager
This role ensures that the service provider employs the right balance of staff in terms of skills and experience. The human resources (HR) manager is also responsible for identifying gaps in the organization's current set of skills and for organizing any required skill development initiatives, in line with the service provider's objectives.


Incident manager
The incident manager is responsible for the effective implementation of the incident resolution process and carries out the corresponding reporting. He represents the first stage of escalation for incidents, should these not be resolvable within the agreed time frames in the relevant service levels.


Major incident team
A dynamically established team of managers and technical experts, usually under the leadership of the incident manager, set up to concentrate on the resolution of a major incident.


Operations manager
An operations manager will be needed to take overall responsibility for operating a service. For instance, this role will ensure that all day-to-day operational activities are carried out in a timely and reliable way.


Operator
Operators are the staff who perform the day-to-day operational activities. Typical responsibilities include: Performing backups, ensuring that scheduled jobs are performed, installing standard equipment in the data center.


Problem manager
The problem manager is responsible for managing the lifecycle of all problems, where the primary objective is to prevent incidents from happening if possible, and to minimize the impact of incidents that cannot be prevented. Apart from resolving the underlying causes of (potential) incidents, the problem manager often provides workarounds while a full solution is not yet available.


Process owner
This role ensures that the processes it owns are fit for purpose. The process owner’s responsibilities include the design and continual improvement of the process. In larger organizations there might be separate process owner and process manager roles, where the process manager has responsibility for the operational management of a process.


Project board
The project board is the decision-making body of the project. The project board typically consists of members of the management board and representatives of the different project stakeholders. It is important that the project board has real authority to take decisions.


Project manager
The project manager is responsible for directing a project, which includes responsibility for delivering the agreed project deliverables within the agreed time and budget.


Project owner
The project owner is the driving force behind a project. Typically, this role will prepare a business case and apply for a budget before a project is set up. As many projects are related to improving services, service owners will often act as project owners.


Security manager
The security manager is responsible for the service provider's and its customers' security. This includes responsibility for the security of information and data being processed by the service provider.


Service continuity manager
The service continuity manager is responsible for managing risks that could seriously impact the service provider's services. In particular, this role ensures that the service provider can provide minimum agreed service levels in cases of disaster.


Service design manager
The service design manager is responsible for the detailed specification of the requirements for new or changed services, as well as identifying a suitable approach for their implementation.


Service implementation manager
The service implementation manager is responsible for coordinating the implementation of new or significantly changed services. In particular, the service implementation manager ensures that all service infrastructure and other required capabilities are properly tested and deployed.


Service improvement manager
The service improvement manager is responsible for managing improvements to the service provider's range of services. In particular, this role will identify improvement potentials by analyzing service quality reports and performing service reviews.


Service owner
The service owner holds responsibility for delivering a particular service. In the case of a customer-facing business service, the service owner is responsible for delivering the service as specified in the customer agreement. In the case of supporting services, the service owner will often lead a team of technical specialists or an internal support unit.


Service portfolio manager
The service portfolio manager is responsible for managing the service provider's range of services. This includes making sure that the information in the service portfolio and any service definitions are accurate and up-to-date. The service portfolio manager will also support the steering group during strategic assessments of the service portfolio.


Service request fulfillment group
Service request fulfillment groups specialize in the fulfillment of certain types of service requests. Typically, 1st level support will process simpler requests, while others are forwarded to the specialized fulfillment groups.


Service strategy manager
The service strategy manager supports the steering group in producing and maintaining the service provider's strategy. This role is also responsible for communicating and implementing the service strategy.


SMS manager
The SMS manager is responsible for setting up and maintaining the service management system. This role plays a key part in managing the service management processes and policies, ensuring that all elements of the SMS cooperate in a seamless way to achieve the service provider's objectives.


Steering group
The steering group sets the direction and strategy for the service provider. It typically consists of members of top and middle-level management. The steering group has ultimate responsibility for the range of services offered by the service provider. As such, it also authorizes initiatives for the introduction of new or the enhancement of existing services. It is important that the steering group has real authority to take decisions.


Supplier manager
The supplier manager is responsible for ensuring that value for money is obtained from all suppliers. This role makes sure that the contracts with external suppliers support the service provider's needs, and that all suppliers meet their contractual commitments.


Technical domain expert
The technical domain expert provides technical expertise and support in various service management processes. There is typically one expert or team of experts for every key technology area or type of application or system. This role plays an important part in the technical aspects of designing, testing, operating and improving services.


Test manager
The test manager ensures that newly implemented services deliver the required outcomes, and verifies that all preconditions for operating a new service have been created.

 

YaSM RACI matrix

The YaSM RACI matrix ("responsibility matrix") provides a summary of the YaSM roles' responsibilities for whole processes or single process activities.

 

Notes

Is based on: YaSM service management role definitions from the from the YaSM Process Map.

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

 

 ›  ›  ›