ITIL Roles: Difference between revisions

From IT Process Wiki
No edit summary
mNo edit summary
Line 16: Line 16:




== ITIL V3 roles within [[ITIL V3 Service Strategy|Service Strategy]] ==
== <span id="ITIL V3 roles within Service Strategy">ITIL roles - [[ITIL V3 Service Strategy|Service Strategy]]</span> ==


==== Business Relationship Manager ====
==== Business Relationship Manager ====
* The Business Relationship Manager is responsible for maintaining a positive relationship with customers, identifying customer needs and ensuring that the service provider is able to meet these needs with an appropriate catalogue of services.  
* The Business Relationship Manager is responsible for maintaining a positive relationship with customers, identifying customer needs and ensuring that the service provider is able to meet these needs with an appropriate catalogue of services.  
* The Business Relationship Manager works closely with the Service Level Manager.  
* The Business Relationship Manager works closely with the Service Level Manager.  
* The Business Relationship Manager has been introduced as a new role in ITIL 2011.


==== Demand Manager ====
==== Demand Manager ====
* The role Demand Manager has been introduced in ITIL 2011 to perform the activities in the Demand Management process.
* The Demand Manager is responsible for understanding, anticipating and influencing customer demand for services.  
* The Demand Manager is responsible for understanding, anticipating and influencing customer demand for services.  
* The Demand Manager works with capacity management to ensure that the service provider has sufficient capacity to meet the required demand.  
* The Demand Manager works with capacity management to ensure that the service provider has sufficient capacity to meet the required demand.  
Line 40: Line 42:
* The Service Strategy Manager supports the IT Steering Group in producing and maintaining the service provider's strategy.  
* The Service Strategy Manager supports the IT Steering Group in producing and maintaining the service provider's strategy.  
* This role is also responsible for communicating and implementing the service strategy.
* This role is also responsible for communicating and implementing the service strategy.
* The Service Strategy Manager has been introduced as a new role in ITIL 2011.


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


== ITIL V3 roles within [[ITIL V3 Service Design|Service Design]] ==
== <span id="ITIL V3 roles within Service Design">ITIL roles - [[ITIL V3 Service Design|Service Design]]</span> ==
 
==== Service Catalogue Manager ====
* The Service Catalogue Manager is responsible for maintaining the Service Catalogue, ensuring that all information within the Service Catalogue is accurate and up-to-date.
 
==== Service Level Manager ====
* The Service Level Manager is responsible for negotiating Service Level Agreements and ensuring that these are met.
* He makes sure that all IT Service Management processes, Operational Level Agreements and Underpinning Contracts are appropriate for the agreed service level targets.
* The Service Level Manager also monitors and reports on service levels.
 
==== Service Owner ====
* The Service Owner is responsible for delivering a particular service within the agreed service levels.
* Typically, he acts as the counterpart of the Service Level Manager when negotiating Operational Level Agreements (OLAs).
* Often, the Service Owner will lead a team of technical specialists or an internal support unit.
 
==== Service Design Manager ====
* The Service Design Manager is responsible for producing quality, secure and resilient designs for new or improved services.
* This includes producing and maintaining all design documentation.


==== Applications Analyst ====
==== Applications Analyst ====
* The Applications Analyst is responsible for designing applications required to provide a service.  
* The Applications Analyst is an Application Management role which manages applications throughout their lifecycle.
* This includes the detailed specification of technologies, application architectures and data structures as a basis for application development or customization.
* There is typically one Applications Analyst or team of analysts for every key application.  
* This role plays an important part in the application-related aspects of designing, testing, operating and improving IT services.
* It is also responsible for developing the skills required to operate the applications required to deliver IT services.


==== Technical Analyst ====
==== Availability Manager ====
* The Technical Analyst is responsible for designing infrastructure components and systems required to provide a service.
* The Availability Manager is responsible for defining, analyzing, planning, measuring and improving all aspects of the availability of IT services.  
* This includes the detailed specification of technologies and products as a basis for their procurement and customization.
* He is responsible for ensuring that all IT infrastructure, processes, tools, roles etc. are appropriate for the agreed service level targets for availability.
 
==== Risk Manager ====
* The Risk Manager is responsible for identifying, assessing and controlling risks.  
* This includes analyzing the value of assets to the business, identifying threats to those assets, and evaluating how vulnerable each asset is to those threats.


==== Capacity Manager ====
==== Capacity Manager ====
Line 78: Line 62:
* He considers all resources required to deliver the service, and plans for short, medium and long term business requirements.
* He considers all resources required to deliver the service, and plans for short, medium and long term business requirements.


==== Availability Manager ====
==== Compliance Manager ====
* The Availability Manager is responsible for defining, analyzing, planning, measuring and improving all aspects of the availability of IT services.  
* The Compliance Manager's responsibility is to ensure that standards and guidelines is followed, or that proper, consistent accounting or other practices are being employed.
* He is responsible for ensuring that all IT infrastructure, processes, tools, roles etc are appropriate for the agreed service level targets for availability.
* This includes to make sure that external legal requirements are fulfilled.
 
==== Enterprise Architect ====
* The Enterprise Architect is responsible for maintaining the Enterprise Architecture (EA), a description of the essential components of a business, including their interrelationships.
* Bigger organizations may opt to introduce specialist EA roles like Business Architect, Application Architect, Information Architect, or Infrastructure Architect.
 
==== Information Security Manager ====
* The Information Security Manager is responsible for ensuring the confidentiality, integrity and availability of an organization’s assets, information, data and IT services.  
* He is usually involved in an organizational approach to Security Management which has a wider scope than the IT service provider, and includes handling of paper, building access, phone calls etc., for the entire organization.


==== IT Service Continuity Manager ====
==== IT Service Continuity Manager ====
Line 86: Line 78:
* He ensures that the IT service provider can provide minimum agreed service levels in cases of disaster, by reducing the risk to an acceptable level and planning for the recovery of IT services.
* He ensures that the IT service provider can provide minimum agreed service levels in cases of disaster, by reducing the risk to an acceptable level and planning for the recovery of IT services.


==== Information Security Manager ====
==== Risk Manager ====
* The Information Security Manager is responsible for ensuring the confidentiality, integrity and availability of an organization’s assets, information, data and IT services.  
* The Risk Manager is responsible for identifying, assessing and controlling risks.
* He is usually involved in an organizational approach to Security Management which has a wider scope than the IT service provider, and includes handling of paper, building access, phone calls etc., for the entire organization.
* This includes analyzing the value of assets to the business, identifying threats to those assets, and evaluating how vulnerable each asset is to those threats.
 
==== Service Catalogue Manager ====
* The Service Catalogue Manager is responsible for maintaining the Service Catalogue, ensuring that all information within the Service Catalogue is accurate and up-to-date.
 
==== Service Design Manager ====
* The Service Design Manager is responsible for producing quality, secure and resilient designs for new or improved services.
* This includes producing and maintaining all design documentation.


==== Compliance Manager ====
==== Service Level Manager ====
* The Compliance Manager's responsibility is to ensure that standards and guidelines is followed, or that proper, consistent accounting or other practices are being employed.  
* The Service Level Manager is responsible for negotiating Service Level Agreements and ensuring that these are met.  
* This includes to make sure that external legal requirements are fulfilled.
* He makes sure that all IT Service Management processes, Operational Level Agreements and Underpinning Contracts are appropriate for the agreed service level targets.
* The Service Level Manager also monitors and reports on service levels.


==== Enterprise Architect ====
==== Service Owner ====
* The Enterprise Architect defines a blueprint for the future development of the technological landscape, taking into account the service strategy and newly available technologies.
* The Service Owner is responsible for delivering a particular service within the agreed service levels.
* Typically, he acts as the counterpart of the [[#Service Level Manager|Service Level Manager]] when negotiating Operational Level Agreements (OLAs).
* Often, the Service Owner will lead a team of technical specialists or an internal support unit.


==== Supplier Manager ====
==== Supplier Manager ====
* The Supplier Manager is responsible for ensuring that value for money is obtained from all suppliers.  
* The Supplier Manager is responsible for ensuring that value for money is obtained from all suppliers.  
* He makes sure that contracts with suppliers support the needs of the business, and that all suppliers meet their contractual commitments.
* He makes sure that contracts with suppliers support the needs of the business, and that all suppliers meet their contractual commitments.
==== Technical Analyst ====
* The Technical Analyst is a Technical Management role which provides technical expertise and support for the management of the IT infrastructure.
* There is typically one Technical Analyst or team of analysts for every key technology area.
* This role plays an important part in the technical aspects of designing, testing, operating and improving IT services.
* It is also responsible for developing the skills required to operate the IT infrastructure.


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


== ITIL V3 roles and boards within [[ITIL V3 Service Transition|Service Transition]] ==
== <span id="ITIL V3 roles and boards within Service Transition">ITIL roles and boards - [[ITIL V3 Service Transition|Service Transition]]</span> ==
 
==== Application Developer ====
* The Application Developer is responsible for making available applications and systems which provide the required functionality for IT 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|Change Manager]] in the assessment, prioritization and scheduling of Changes.
* This board is usually made up of representatives from all areas within the IT organization, the business, and third parties such as suppliers.


==== Change Manager ====
==== Change Manager ====
* The Change Manager controls the lifecycle of all Changes.  
* The Change Manager controls the lifecycle of all Changes.  
* His primary objective is to enable beneficial Changes to be made, with minimum disruption to IT services.  
* His primary objective is to enable beneficial Changes to be made, with minimum disruption to IT services.  
* For important Changes, the Change Manager will refer the authorization of Changes to the Change Advisory Board (CAB).
* For important Changes, the Change Manager will refer the authorization of Changes to the [[#Change Advisory Board (CAB)|Change Advisory Board (CAB)]].


==== Change Advisory Board (CAB) ====
==== Configuration Manager ====
* A group of people that advises the Change Manager in the assessment, prioritization and scheduling of Changes.  
* The Configuration Manager is responsible for maintaining information about Configuration Items required to deliver IT services.  
* This board is usually made up of representatives from all areas within the IT organization, the business, and third parties such as suppliers.
* To this end he maintains a logical model, containing the components of the IT infrastructure (CIs) and their associations.


==== Emergency Change Advisory Board (ECAB) ====
==== Emergency Change Advisory Board (ECAB) ====
* A sub-set of the Change Advisory Board who makes decisions about high impact Emergency Changes.  
* A sub-set of the [[#Change Advisory Board (CAB)|Change Advisory Board]] who makes decisions about high impact Emergency Changes.  
* Membership of the ECAB may be decided at the time a meeting is called, and depends on the nature of the Emergency Change.
* Membership of the ECAB may be decided at the time a meeting is called, and depends on the nature of the Emergency Change.
==== Knowledge Manager ====
* The Knowledge Manager ensures that the IT organization is able to gather, analyze, store and share knowledge and information.
* His primary goal is to improve efficiency by reducing the need to rediscover knowledge.


==== Project Manager ====
==== Project Manager ====
* The Project Manager is responsible for planning and coordinating the resources to deploy a major Release within the predicted cost, time and quality estimates.
* The Project Manager is responsible for planning and coordinating the resources to deploy a major Release within the predicted cost, time and quality estimates.
==== Application Developer ====
* The Application Developer is responsible for making available applications and systems which provide the required functionality for IT services.
* This includes the development and maintenance of custom applications as well as the customization of products from software vendors.


==== Release Manager ====
==== Release Manager ====
* The Release Manager is responsible for planning and controlling the movement of Releases to test and live environments.  
* The Release Manager is responsible for planning and controlling the movement of Releases to test and live environments.  
* His primary objective is to ensure that the integrity of the live environment is protected and that the correct components are released.
* His primary objective is to ensure that the integrity of the live environment is protected and that the correct components are released.
==== Configuration Manager ====
* The Configuration Manager is responsible for maintaining information about Configuration Items required to deliver IT services.
* To this end he maintains a logical model, containing the components of the IT infrastructure (CIs) and their associations.
==== Knowledge Manager ====
* The Knowledge Manager ensures that the IT organization is able to gather, analyze, store and share knowledge and information.
* His primary goal is to improve efficiency by reducing the need to rediscover knowledge.


==== Test Manager ====
==== Test Manager ====
Line 142: Line 150:
<p>&nbsp;</p>
<p>&nbsp;</p>


== ITIL V3 roles and boards within [[ITIL V3 Service Operation|Service Operation]] ==
== <span id="ITIL V3 roles and boards within Service Operation">ITIL roles and boards - [[ITIL V3 Service Operation|Service Operation]]</span> ==


==== 1st Level Support ====
==== 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 IT service as quickly as possible.  
* 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 IT service as quickly as possible.  
* If no ad-hoc solution can be achieved, 1st Level Support will transfer the Incident to expert technical support groups (2nd Level Support).  
* If no ad-hoc solution can be achieved, 1st Level Support will transfer the Incident to expert technical support groups ([[#2nd Level Support|2nd Level Support]]).  
* 1st Level Support also processes Service Requests and keeps users informed about their Incidents' status at agreed intervals.
* 1st Level Support also processes Service Requests and keeps users informed about their Incidents' status at agreed intervals.


==== 2nd Level Support ====
==== 2nd Level Support ====
* 2nd Level Support takes over Incidents which cannot be solved immediately with the means of 1st Level Support.  
* 2nd Level Support takes over Incidents which cannot be solved immediately with the means of [[#1st Level Support|1st Level Support]].  
* If necessary, it will request external support, e.g. from software or hardware manufacturers.  
* If necessary, it will request external support, e.g. from software or hardware manufacturers.  
* The aim is to restore a failed IT Service as quickly as possible.  
* The aim is to restore a failed IT Service as quickly as possible.  
Line 157: Line 165:
==== 3rd Level Support ====
==== 3rd Level Support ====
* 3rd Level Support is typically located at hardware or software manufacturers (third-party suppliers).  
* 3rd Level Support is typically located at hardware or software manufacturers (third-party suppliers).  
* Its services are requested by 2nd Level Support if required for solving an Incident.  
* Its services are requested by [[#2nd Level Support|2nd Level Support]] if required for solving an Incident.  
* The aim is to restore a failed IT Service as quickly as possible.
* The aim is to restore a failed IT Service as quickly as possible.


==== Major Incident Team ====
==== Access Manager ====
* A dynamically established team of IT managers and technical experts, usually under the leadership of the Incident Manager, formulated to concentrate on the resolution of a Major Incident.
* The Access Manager grants authorized users the right to use a service, while preventing access to non-authorized users.
* The Access Manager essentially executes policies defined in Information Security Management.
 
====<span id="IT Facilities Manager">Facilities Manager</span>====
* The Facilities Manager is responsible for managing the physical environment where the IT infrastructure is located.
* This includes all aspects of managing the physical environment, for example power and cooling, building access management, and environmental monitoring.


==== Incident Manager ====
==== Incident Manager ====
* The Incident Manager is responsible for the effective implementation of the Incident Management process and carries out the corresponding reporting.   
* The Incident Manager is responsible for the effective implementation of the Incident Management process and carries out the corresponding reporting.   
* He represents the first stage of escalation for Incidents, should these not be resolvable within the agreed Service Levels.
* He represents the first stage of escalation for Incidents, should these not be resolvable within the agreed Service Levels.
==== IT Operations Manager ====
* An IT Operations Manager will be needed to take overall responsibility for all of the IT Operations Management activities. He will ensure that all day-to-day operational activities are carried out in a timely and reliable way.
==== IT Operator ====
* IT 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.
==== Major Incident Team ====
* A dynamically established team of IT managers and technical experts, usually under the leadership of the [[#Incident Manager|Incident Manager]], formulated to concentrate on the resolution of a Major Incident.


==== Problem Manager ====
==== Problem Manager ====
Line 174: Line 197:
==== Service Request Fulfilment Group ====
==== Service Request Fulfilment Group ====
* Service Request Fulfilment Groups specialize on the fulfillment of certain types of Service Requests.  
* Service Request Fulfilment Groups specialize on the fulfillment of certain types of Service Requests.  
* Typically, 1st Level Support will process simpler requests, while others are forwarded to the specialized Fulfilment Groups.
* Typically, [[#1st Level Support|1st Level Support]] will process simpler requests, while others are forwarded to the specialized Fulfilment Groups.
 
==== Access Manager ====
* The Access Manager grants authorized users the right to use a service, while preventing access to non-authorized users.
* The Access Manager essentially executes policies defined in Information Security Management.
 
==== IT Operations Manager ====
* An IT Operations Manager will be needed to take overall responsibility for all of the IT Operations Management activities. He will ensure that all day-to-day operational activities are carried out in a timely and reliable way.
 
==== IT Operator ====
* IT 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.
 
====<span id="IT Facilities Manager">Facilities Manager</span>====
* The Facilities Manager is responsible for managing the physical environment where the IT infrastructure is located.
* This includes all aspects of managing the physical environment, for example power and cooling, building access management, and environmental monitoring.


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


== ITIL V3 roles within [[ITIL V3 CSI - Continual Service Improvement|Continual Service Improvement]] ==
== <span id="ITIL V3 roles within Continual Service Improvement">ITIL roles - [[ITIL V3 CSI - Continual Service Improvement|Continual Service Improvement]]</span> ==


==== CSI Manager ====
==== CSI Manager ====
Line 204: Line 212:


==== Process Owner ====
==== Process Owner ====
* A role responsible for ensuring that a process is fit for purpose. The Process Owner’s responsibilities include sponsorship, design, and continual improvement of the process and its metrics.
* A role responsible for ensuring that a process is fit for purpose.  
* The Process Owner’s responsibilities include sponsorship, design, and continual improvement of the process and its metrics.
* 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.
* 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.


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


== ITIL V3 roles outside the IT organization ==
== <span id="ITIL V3 roles outside the IT organization">ITIL roles outside the IT organization</span> ==


==== Customer ====
==== Customer ====
Line 216: Line 225:


==== <span id="User">Service User</span> ====
==== <span id="User">Service User</span> ====
* A person who uses one or several IT services on a day-to-day basis. Service Users are distinct from Customers, as some Customers do not use IT services directly.
* A person who uses one or several IT services on a day-to-day basis. Service Users are distinct from Customers, as some [[#Customer|Customers]] do not use IT services directly.


<p>&nbsp;</p>
<p>&nbsp;</p>
Line 223: Line 232:
Link to the descriptions of the [[Roles within ITIL|roles within ITIL Version 2]].
Link to the descriptions of the [[Roles within ITIL|roles within ITIL Version 2]].


 
<p>&nbsp;</p>


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

Revision as of 12:25, 22 January 2012

<seo metakeywords="itil roles, itil 2011 roles, itil v3 roles" metadescription="ITIL Roles are employed in order to define responsibilities. In particular, they are used to assign Process Owners to the various ITIL 2011 ..." />

DE - ES - ITIL Rolesdiese Seite auf Deutschesta página en español
DE - ES - ITIL Roles


ITIL Roles are employed in order to define responsibilities. In particular, they are used to assign Process Owners to the various ITIL processes, and to illustrate responsibilities for the single activities within the detailed process descriptions.

ITIL Roles
Figure 1: ITIL Roles - Index

The definitions found here (in alphabetical order) are meant to be short, summing up the main characteristics of a specific ITIL role according to ITIL 2011 (ITIL V3 2011 Edition).

When in-depth information on a role's tasks and responsibilities is required this can, in our view, best be obtained from the ITIL process flows.


ITIL roles - Service Strategy

Business Relationship Manager

  • The Business Relationship Manager is responsible for maintaining a positive relationship with customers, identifying customer needs and ensuring that the service provider is able to meet these needs with an appropriate catalogue of services.
  • The Business Relationship Manager works closely with the Service Level Manager.
  • The Business Relationship Manager has been introduced as a new role in ITIL 2011.

Demand Manager

  • The role Demand Manager has been introduced in ITIL 2011 to perform the activities in the Demand Management process.
  • The Demand Manager is responsible for understanding, anticipating and influencing customer demand for services.
  • The Demand Manager works with capacity management to ensure that the service provider has sufficient capacity to meet the required demand.

Financial Manager

  • The Financial Manager is responsible for managing an IT service provider's budgeting, accounting and charging requirements.

IT Steering Group (ISG)

  • The IT Steering Group (ISG) sets the direction and strategy for IT Services. It includes members of senior management from business and IT.
  • The ISG reviews the business and IT strategies in order to make sure that they are aligned.
  • It also sets priorities of service development programs/ projects.

Service Portfolio Manager

  • The Service Portfolio Manager decides on a strategy to serve customers in cooperation with the IT Steering Group, and develops the service provider's offerings and capabilities.

Service Strategy Manager

  • The Service Strategy Manager supports the IT Steering Group in producing and maintaining the service provider's strategy.
  • This role is also responsible for communicating and implementing the service strategy.
  • The Service Strategy Manager has been introduced as a new role in ITIL 2011.

 

ITIL roles - Service Design

Applications Analyst

  • The Applications Analyst is an Application Management role which manages applications throughout their lifecycle.
  • There is typically one Applications Analyst or team of analysts for every key application.
  • This role plays an important part in the application-related aspects of designing, testing, operating and improving IT services.
  • It is also responsible for developing the skills required to operate the applications required to deliver IT services.

Availability Manager

  • The Availability Manager is responsible for defining, analyzing, planning, measuring and improving all aspects of the availability of IT services.
  • He is responsible for ensuring that all IT infrastructure, processes, tools, roles etc. are appropriate for the agreed service level targets for availability.

Capacity Manager

  • The Capacity Manager is responsible for ensuring that services and infrastructure are able to deliver the agreed capacity and performance targets in a cost effective and timely manner.
  • He considers all resources required to deliver the service, and plans for short, medium and long term business requirements.

Compliance Manager

  • The Compliance Manager's responsibility is to ensure that standards and guidelines is followed, or that proper, consistent accounting or other practices are being employed.
  • This includes to make sure that external legal requirements are fulfilled.

Enterprise Architect

  • The Enterprise Architect is responsible for maintaining the Enterprise Architecture (EA), a description of the essential components of a business, including their interrelationships.
  • Bigger organizations may opt to introduce specialist EA roles like Business Architect, Application Architect, Information Architect, or Infrastructure Architect.

Information Security Manager

  • The Information Security Manager is responsible for ensuring the confidentiality, integrity and availability of an organization’s assets, information, data and IT services.
  • He is usually involved in an organizational approach to Security Management which has a wider scope than the IT service provider, and includes handling of paper, building access, phone calls etc., for the entire organization.

IT Service Continuity Manager

  • The IT Service Continuity Manager is responsible for managing risks that could seriously impact IT services.
  • He ensures that the IT service provider can provide minimum agreed service levels in cases of disaster, by reducing the risk to an acceptable level and planning for the recovery of IT services.

Risk Manager

  • The Risk Manager is responsible for identifying, assessing and controlling risks.
  • This includes analyzing the value of assets to the business, identifying threats to those assets, and evaluating how vulnerable each asset is to those threats.

Service Catalogue Manager

  • The Service Catalogue Manager is responsible for maintaining the Service Catalogue, ensuring that all information within the Service Catalogue is accurate and up-to-date.

Service Design Manager

  • The Service Design Manager is responsible for producing quality, secure and resilient designs for new or improved services.
  • This includes producing and maintaining all design documentation.

Service Level Manager

  • The Service Level Manager is responsible for negotiating Service Level Agreements and ensuring that these are met.
  • He makes sure that all IT Service Management processes, Operational Level Agreements and Underpinning Contracts are appropriate for the agreed service level targets.
  • The Service Level Manager also monitors and reports on service levels.

Service Owner

  • The Service Owner is responsible for delivering a particular service within the agreed service levels.
  • Typically, he acts as the counterpart of the Service Level Manager when negotiating Operational Level Agreements (OLAs).
  • Often, the Service Owner will lead a team of technical specialists or an internal support unit.

Supplier Manager

  • The Supplier Manager is responsible for ensuring that value for money is obtained from all suppliers.
  • He makes sure that contracts with suppliers support the needs of the business, and that all suppliers meet their contractual commitments.

Technical Analyst

  • The Technical Analyst is a Technical Management role which provides technical expertise and support for the management of the IT infrastructure.
  • There is typically one Technical Analyst or team of analysts for every key technology area.
  • This role plays an important part in the technical aspects of designing, testing, operating and improving IT services.
  • It is also responsible for developing the skills required to operate the IT infrastructure.

 

ITIL roles and boards - Service Transition

Application Developer

  • The Application Developer is responsible for making available applications and systems which provide the required functionality for IT 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.
  • This board is usually made up of representatives from all areas within the IT organization, the business, and third parties such as suppliers.

Change Manager

  • The Change Manager controls the lifecycle of all Changes.
  • His primary objective is to enable beneficial Changes to be made, with minimum disruption to IT services.
  • For important Changes, the Change Manager will refer the authorization of Changes to the Change Advisory Board (CAB).

Configuration Manager

  • The Configuration Manager is responsible for maintaining information about Configuration Items required to deliver IT services.
  • To this end he maintains a logical model, containing the components of the IT infrastructure (CIs) and their associations.

Emergency Change Advisory Board (ECAB)

  • A sub-set of the Change Advisory Board who makes decisions about high impact Emergency Changes.
  • Membership of the ECAB may be decided at the time a meeting is called, and depends on the nature of the Emergency Change.

Knowledge Manager

  • The Knowledge Manager ensures that the IT organization is able to gather, analyze, store and share knowledge and information.
  • His primary goal is to improve efficiency by reducing the need to rediscover knowledge.

Project Manager

  • The Project Manager is responsible for planning and coordinating the resources to deploy a major Release within the predicted cost, time and quality estimates.

Release Manager

  • The Release Manager is responsible for planning and controlling the movement of Releases to test and live environments.
  • His primary objective is to ensure that the integrity of the live environment is protected and that the correct components are released.

Test Manager

  • The Test Manager ensures that deployed Releases and the resulting services meet customer expectations, and verifies that IT operations is able to support the new service.

 

ITIL roles and boards - Service Operation

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 IT service as quickly as possible.
  • If no ad-hoc solution can be achieved, 1st Level Support will transfer the Incident to expert technical support groups (2nd Level Support).
  • 1st Level Support also processes Service Requests and keeps users informed about their Incidents' status at agreed intervals.

2nd Level Support

  • 2nd Level Support takes over Incidents which cannot be solved immediately with the means of 1st Level Support.
  • If necessary, it will request external support, e.g. from software or hardware manufacturers.
  • The aim is to restore a failed IT Service as quickly as possible.
  • If no solution can be found, the 2nd Level Support passes on the Incident to Problem Management.

3rd Level Support

  • 3rd Level Support is typically located at hardware or software manufacturers (third-party suppliers).
  • Its services are requested by 2nd Level Support if required for solving an Incident.
  • The aim is to restore a failed IT Service as quickly as possible.

Access Manager

  • The Access Manager grants authorized users the right to use a service, while preventing access to non-authorized users.
  • The Access Manager essentially executes policies defined in Information Security Management.

Facilities Manager

  • The Facilities Manager is responsible for managing the physical environment where the IT infrastructure is located.
  • This includes all aspects of managing the physical environment, for example power and cooling, building access management, and environmental monitoring.

Incident Manager

  • The Incident Manager is responsible for the effective implementation of the Incident Management process and carries out the corresponding reporting.
  • He represents the first stage of escalation for Incidents, should these not be resolvable within the agreed Service Levels.

IT Operations Manager

  • An IT Operations Manager will be needed to take overall responsibility for all of the IT Operations Management activities. He will ensure that all day-to-day operational activities are carried out in a timely and reliable way.

IT Operator

  • IT 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.

Major Incident Team

  • A dynamically established team of IT managers and technical experts, usually under the leadership of the Incident Manager, formulated to concentrate on the resolution of a Major Incident.

Problem Manager

  • The Problem Manager is responsible for managing the lifecycle of all Problems.
  • His primary objectives are to prevent Incidents from happening, and to minimize the impact of Incidents that cannot be prevented.
  • To this purpose he maintains information about Known Errors and Workarounds.

Service Request Fulfilment Group

  • Service Request Fulfilment Groups specialize on the fulfillment of certain types of Service Requests.
  • Typically, 1st Level Support will process simpler requests, while others are forwarded to the specialized Fulfilment Groups.

 

ITIL roles - Continual Service Improvement

CSI Manager

  • The Continual Service Improvement (CSI) Manager is responsible for managing improvements to IT Service Management processes and IT services.
  • He will continually measure the performance of the service provider and design improvements to processes, services and infrastructure in order to increase efficiency, effectiveness, and cost effectiveness.

Process Architect

  • The Process Architect is responsible for maintaining the Process Architecture (part of the Enterprise Architecture), coordinating all changes to processes and making sure that all processes cooperate in a seamless way.
  • This role often also supports all parties involved in managing and improving processes, in particular the Process Owners. Some organizations combine this role with the Enterprise Architect role.

Process Owner

  • A role responsible for ensuring that a process is fit for purpose.
  • The Process Owner’s responsibilities include sponsorship, design, and continual improvement of the process and its metrics.
  • 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.

 

ITIL roles outside the IT organization

Customer

  • Someone who buys IT services.
  • The Customer of an IT service provider is the person or group who defines and agrees the service level targets.

Service User

  • A person who uses one or several IT services on a day-to-day basis. Service Users are distinct from Customers, as some Customers do not use IT services directly.

 

Roles and boards according to ITIL Version 2

Link to the descriptions of the roles within ITIL Version 2.