Event Management: Difference between revisions
No edit summary |
No edit summary |
||
(6 intermediate revisions by the same user not shown) | |||
Line 1: | Line 1: | ||
< | <itpmch><title>Event Management | IT Process Wiki</title> | ||
<meta name="keywords" content="itil event management, event management itil, event management process, itil v3 event management, event management itil" /> | |||
<meta name="description" content="The objective of ITIL Event Management is to make sure Configuration Items (CIs) and services are constantly monitored. The Event Management process aims to filter and categorize Events in order to decide on appropriate actions if required." /> | |||
<meta property="og:url" content="https://wiki.en.it-processmaps.com/index.php/Event_Management" /> | |||
<meta property="og:title" content="Event Management | IT Process Wiki" /> | |||
<meta property="og:description" content="The objective of ITIL Event Management is to make sure Configuration Items (CIs) and services are constantly monitored. The Event Management process aims to filter and categorize Events in order to decide on appropriate actions if required." /> | |||
<meta property="og:site_name" content="IT Process Wiki - the ITIL® Wiki"> | |||
<meta property="og:type" content="article" /> | |||
<meta property="article:publisher" content="https://www.facebook.com/itprocessmaps" /> | |||
<meta property="fb:admins" content="100002035253209" /> | |||
<meta property="fb:admins" content="100002592864414" /> | |||
<meta property="og:image" content="https://wiki.en.it-processmaps.com/images/1/13/Event-management-itil.jpg" /> | |||
<meta property="og:image:width" content="1200" /> | |||
<meta property="og:image:height" content="900" /> | |||
<link href="https://plus.google.com/108613479011811316823/posts" rel="publisher" /> | |||
</itpmch> | |||
<imagemap> | <imagemap> | ||
Image:ITIL-Wiki-de-es.jpg|DE - ES - Event Management| | Image:ITIL-Wiki-de-es.jpg|right|DE - ES - Event Management|163px | ||
rect 0 | rect 81 0 114 36 [https://wiki.de.it-processmaps.com/index.php/Event_Management diese Seite auf Deutsch] | ||
rect | rect 115 0 163 36 [https://wiki.es.it-processmaps.com/index.php/ITIL_Gestion_de_Eventos esta página en español] | ||
desc none | desc none | ||
</imagemap> | </imagemap> | ||
<br style="clear:both;"/> | <br style="clear:both;"/> | ||
'''<span id="Overview">Objective:</span>''' <html><span id="md-webpage-description" itemprop="description">The objective of <i>ITIL Event Management</i> is to make sure Configuration Items (CIs) and services are constantly monitored. The Event Management process aims to filter and categorize Events in order to decide on appropriate actions if required.</span></p> | |||
<p><b>Part of</b>: <a href="https://wiki.en.it-processmaps.com/index.php/ITIL_Service_Operation" title="ITIL Service Operation">Service Operation</a></html> | |||
'''<span id="Overview">Objective:</span>''' <html><span itemprop="description">The objective of <i | |||
<p><b>Part of</b>: <a | |||
'''Process Owner''': [[Event Management#IT Operations Manager|IT Operations Manager]] | '''Process Owner''': [[Event Management#IT Operations Manager|IT Operations Manager]] | ||
Line 20: | Line 32: | ||
==Process Description== | ==Process Description== | ||
The activities and process objectives of the Event Management process are mostly identical in ITIL V3 and V2 (Event Management was part of ICT Infrastructure Management). | |||
[[Image:Event-management-itil.jpg|right|thumb| | [[Image:Event-management-itil.jpg|right|thumb|500px|alt=Event Management ITIL|link=https://wiki.en.it-processmaps.com/index.php/File:Event-management-itil.jpg|[https://wiki.en.it-processmaps.com/images/pdf/process_overview_event_management_itilv3.pdf ITIL Event Management (.pdf)]]] | ||
Interfaces between Event Management and the other ITIL processes were adjusted in order to reflect the new ITIL process structure in ITIL V3. | Interfaces between Event Management and the other ITIL processes were adjusted in order to reflect the new ITIL process structure in ITIL V3. | ||
In ITIL 2011 Event Management has been updated to reflect the concept of [[Event Management#ITIL Event 1st Level Correlation|1st Level Correlation]] and [[Event Management#Event Management 2nd Level Correlation|2nd Level Correlation]]. | |||
In | |||
The process flows | The process flows reflect the more detailed guidance in the ITIL 2011 books. The process overview of [[Media:Event-management-itil.jpg|ITIL Event Management]] shows the key information flows (see fig. 1). | ||
<p> </p> | [[ITIL 4]] refers to Event Management as a [[ITIL_4#Service_management_practices|service management practice]], and has renamed the practice to "Monitoring and event management". | ||
<p style="clear:both;"> </p> | |||
==Sub-Processes== | ==Sub-Processes== | ||
Line 39: | Line 50: | ||
<p><span itemprop="name" content="Event Management sub-processes:">These are the <strong class="selflink">ITIL Event Management</strong> sub-processes and their process objectives:</span> | <p><span itemprop="name" content="Event Management sub-processes:">These are the <strong class="selflink">ITIL Event Management</strong> sub-processes and their process objectives:</span> | ||
</p> | </p> | ||
<p><b><span id="ITIL_Event_Management_Maintenance" itemprop="itemListElement">Maintenance of Event Monitoring Mechanisms and Rules</span></b> | <p><b><span id="ITIL_Event_Management_Maintenance" itemprop="itemListElement">Maintenance of Event Monitoring Mechanisms and Rules</span></b> | ||
</p> | </p> | ||
<ul><li itemprop="description">Process Objective: To set up and maintain the mechanisms for generating meaningful <a href="/index.php/Event_Management#Event_Record" title="Event Management">Events</a> and effective rules for their filtering and <a href="/index.php/Event_Management#Event_Filtering_and_Correlation_Rules" title="Event Management">correlating</a>. | <ul><li itemprop="description">Process Objective: To set up and maintain the mechanisms for generating meaningful <a href="/index.php/Event_Management#Event_Record" title="Event Management">Events</a> and effective rules for their filtering and <a href="/index.php/Event_Management#Event_Filtering_and_Correlation_Rules" title="Event Management">correlating</a>. | ||
</li></ul> | </li></ul> | ||
<p><b><span id="ITIL_Event_1st_Level_Correlation" itemprop="itemListElement">Event Filtering and 1st Level Correlation</span></b> | |||
</p> | </p> | ||
<ul><li itemprop="description">Process Objective: To <a href="/index.php/Event_Management#Event_Filtering_and_Correlation_Rules" title="Event Management">filter out</a> Events which are merely informational and can be ignored, and to communicate any Warning and Exception <a href="/index.php/Event_Management#Event_Record" title="Event Management">Events</a>. | <ul><li itemprop="description">Process Objective: To <a href="/index.php/Event_Management#Event_Filtering_and_Correlation_Rules" title="Event Management">filter out</a> Events which are merely informational and can be ignored, and to communicate any Warning and Exception <a href="/index.php/Event_Management#Event_Record" title="Event Management">Events</a>. | ||
</li></ul> | </li></ul> | ||
<p><b><span id="Event_Management_2nd_Level_Correlation" itemprop="itemListElement">2nd Level Correlation and Response Selection</span></b> | |||
</p> | </p> | ||
<ul><li itemprop="description">Process Objective: To interpret the meaning of an <a href="/index.php/Event_Management#Event_Record" title="Event Management">Event</a> and select a suitable response if required. | <ul><li itemprop="description">Process Objective: To interpret the meaning of an <a href="/index.php/Event_Management#Event_Record" title="Event Management">Event</a> and select a suitable response if required. | ||
</li></ul> | </li></ul> | ||
<p><b><span id="ITIL_Event_Management_Review" itemprop="itemListElement">Event Review and Closure</span></b> | |||
</p> | </p> | ||
<ul><li itemprop="description">Process Objective: To check if <a href="/index.php/Event_Management#Event_Record" title="Event Management">Events</a> have been handled appropriately and may be closed. This process also makes sure that Event logs are analyzed in order to identify <a href="/index.php/Event_Management#Event_Trends_and_Patterns" title="Event Management">trends or patterns</a> which suggest corrective action must be taken. | <ul><li itemprop="description">Process Objective: To check if <a href="/index.php/Event_Management#Event_Record" title="Event Management">Events</a> have been handled appropriately and may be closed. This process also makes sure that Event logs are analyzed in order to identify <a href="/index.php/Event_Management#Event_Trends_and_Patterns" title="Event Management">trends or patterns</a> which suggest corrective action must be taken. | ||
</li></ul> | </li></ul> | ||
</div><!-- end of schema.org/ItemList --><p></html> | </div><!-- end of schema.org/ItemList --><p></html> | ||
==Definitions== | ==Definitions== | ||
Line 66: | Line 72: | ||
<html><div itemscope="itemscope" itemtype="https://schema.org/ItemList"><!-- define schema.org/ItemList --> | <html><div itemscope="itemscope" itemtype="https://schema.org/ItemList"><!-- define schema.org/ItemList --> | ||
<meta itemprop="itemListOrder" content="Ascending" /> | <meta itemprop="itemListOrder" content="Ascending" /> | ||
<p><span itemprop="name">The following <a href="/index.php/ | <p><span itemprop="name">The following <a href="/index.php/ITIL_Glossary#ITIL_Glossary_A-Z" title="ITIL Glossary">ITIL terms and acronyms</a> (<i>information objects</i>) are used in the ITIL Event Management process to represent process outputs and inputs:</span> | ||
</p> | </p> | ||
<p><b><span id="Event" itemprop="itemListElement">Event</span></b> | <p><b><span id="Event" itemprop="itemListElement">Event</span></b> | ||
</p> | </p> | ||
<ul><li itemprop="description">see <a href="/index.php/Event_Management#Event_Record" title="Event Management">Event Record</a> | <ul><li itemprop="description">see <a href="/index.php/Event_Management#Event_Record" title="Event Management">Event Record</a> | ||
</li></ul> | </li></ul> | ||
<p><b><span id="Event_Categorization_Scheme" itemprop="itemListElement">Event Categorization Scheme</span></b> | |||
</p> | </p> | ||
<ul><li itemprop="description">The Categorization Scheme for Events supports a consistent approach to dealing with specific types of Events. Ideally, this scheme should be harmonized with the schemes to categorize CIs, Incidents and Problems. | <ul><li itemprop="description">The Categorization Scheme for Events supports a consistent approach to dealing with specific types of Events. Ideally, this scheme should be harmonized with the schemes to categorize CIs, Incidents and Problems. | ||
</li></ul> | </li></ul> | ||
<p><b><span id="Event_Filtering_and_Correlation_Rules" itemprop="itemListElement">Event Filtering and Correlation Rules</span></b> | |||
</p> | </p> | ||
<ul><li itemprop="description">Rules and criteria used to determine if an Event is significant and to decide upon an appropriate response. <a href="/index.php/Event_Management#ITIL_Event_1st_Level_Correlation" title="Event Management">Event Filtering and Correlation</a> Rules are typically used by Event Monitoring systems. Some of those rules are defined during the Service Design stage, for example to ensure that Events are triggered when the required service availability is endangered. | <ul><li itemprop="description">Rules and criteria used to determine if an Event is significant and to decide upon an appropriate response. <a href="/index.php/Event_Management#ITIL_Event_1st_Level_Correlation" title="Event Management">Event Filtering and Correlation</a> Rules are typically used by Event Monitoring systems. Some of those rules are defined during the Service Design stage, for example to ensure that Events are triggered when the required service availability is endangered. | ||
</li></ul> | </li></ul> | ||
<p><b><span id="Event_Record" itemprop="itemListElement">Event Record</span></b> | |||
</p> | </p> | ||
<ul><li itemprop="description">A record describing a change of state which has significance for the management of a Configuration Item or service. The term <i>Event</i> is also used to mean an alert or notification created by any IT service, Configuration Item or monitoring tool. Events often require IT operations personnel to take actions, and may lead to Incidents being logged. | <ul><li itemprop="description">A record describing a change of state which has significance for the management of a Configuration Item or service. The term <i>Event</i> is also used to mean an alert or notification created by any IT service, Configuration Item or monitoring tool. Events often require IT operations personnel to take actions, and may lead to Incidents being logged. | ||
</li></ul> | </li></ul> | ||
<p><b><span id="Event_Trends_and_Patterns" itemprop="itemListElement">Event Trends and Patterns</span></b> | |||
</p> | </p> | ||
<ul><li itemprop="description">Any trends and patterns identified during analysis of significant Events, which suggest that improvements to the infrastructure are needed. | <ul><li itemprop="description">Any trends and patterns identified during analysis of significant Events, which suggest that improvements to the infrastructure are needed. | ||
</li></ul> | </li></ul> | ||
</div><!-- end of schema.org/ItemList --><p></html> | </div><!-- end of schema.org/ItemList --><p></html> | ||
==Roles | Responsibilities== | ==Roles | Responsibilities== | ||
Line 100: | Line 100: | ||
'''<span id="IT Operations Manager">IT Operations Manager - Process Owner</span>''' | '''<span id="IT Operations Manager">IT Operations Manager - Process Owner</span>''' | ||
*An IT Operations Manager will be needed to take overall responsibility for a number of Service Operation activities. For instance, this role will ensure that all day-to-day operational activities are carried out in a timely and reliable way. | *An IT Operations Manager will be needed to take overall responsibility for a number of Service Operation activities. For instance, this role will ensure that all day-to-day operational activities are carried out in a timely and reliable way. | ||
'''<span id="IT Operator">IT Operator</span>''' | '''<span id="IT Operator">IT Operator</span>''' | ||
Line 108: | Line 107: | ||
<p> </p> | <p> </p> | ||
{| | {| class="wikitable" style="background: white;" | ||
|- | |- | ||
|style=" | |+ style="background:#013b5e; color:#ffffff; font-size: 120%" colspan="5"| '''Responsibility Matrix: ITIL Event Management''' | ||
|- | |- | ||
! style="background:#ffffee; width: 40%; text-align:center"| ITIL Role / Sub-Process | ! style="background:#ffffee; width: 40%; text-align:center"| ITIL Role / Sub-Process | ||
! style="background:# | ! style="background:#eeeeee" | [[Event Management#IT Operations Manager|IT Operations Manager]] | ||
! style="background:# | ! style="background:#eeeeee" | [[Event Management#IT Operator|IT Operator]] | ||
! style="background:# | ! style="background:#eeeeee" | (Event Monitoring System) | ||
! style="background:# | ! style="background:#eeeeee" | Other roles involved [[Event Management#Team|<small>[3]</small>]] | ||
|- | |- | ||
|style="text-align:left;" |[[#ITIL Event Management Maintenance|Maintenance of Event Monitoring Mechanisms and Rules]] | |style="text-align:left;" |[[#ITIL Event Management Maintenance|Maintenance of Event Monitoring Mechanisms and Rules]] | ||
Line 143: | Line 142: | ||
|- | |- | ||
|} | |} | ||
'''Remarks''' | '''Remarks''' | ||
Line 154: | Line 151: | ||
<span id="Team">[3] In cooperation, as appropriate: IT Operations Manager, Access Manager, Capacity Manager, Availability Manager, IT Service Continuity Manager, Information Security Manager, Applications Analyst and/ or technical Analyst. [[ITIL Roles| → Role descriptions...]]</span> | <span id="Team">[3] In cooperation, as appropriate: IT Operations Manager, Access Manager, Capacity Manager, Availability Manager, IT Service Continuity Manager, Information Security Manager, Applications Analyst and/ or technical Analyst. [[ITIL Roles| → Role descriptions...]]</span> | ||
==Notes== | |||
== | <html>By:  Stefan Kempter <a rel="author" href="https://www.linkedin.com/in/stefankempter"><img style="margin:0px 0px 0px 0px;" src="/images/bookmarking/linkedin.png" width="16" height="16" title="By: Stefan Kempter | Profile on LinkedIn" alt="Author: Stefan Kempter, IT Process Maps GbR" /></a>, IT Process Maps.</p> | ||
< | <p> </p> | ||
</ | |||
<p><small> | <p><small> | ||
<span itemscope="itemscope | <span itemprop="breadcrumb" itemscope itemtype="http://schema.org/BreadcrumbList"> | ||
<a href="https://wiki.en.it-processmaps.com/index.php/Event_Management#Process_Description | <span itemprop="itemListElement" itemscope itemtype="http://schema.org/ListItem"> | ||
</span> | <a itemprop="item" href="https://wiki.en.it-processmaps.com/index.php/Event_Management#Process_Description"> | ||
<span | <span itemprop="name">Process Description</span></a> | ||
<a href="https://wiki.en.it-processmaps.com/index.php/Event_Management#Sub-Processes | <meta itemprop="position" content="1"></span> › | ||
</span> | <span itemprop="itemListElement" itemscope itemtype="http://schema.org/ListItem"> | ||
<span | <a itemprop="item" href="https://wiki.en.it-processmaps.com/index.php/Event_Management#Sub-Processes"> | ||
<a href="https://wiki.en.it-processmaps.com/index.php/Event_Management#Definitions | <span itemprop="name">Sub-Processes</span></a> | ||
</span> | <meta itemprop="position" content="2"></span> › | ||
<span | <span itemprop="itemListElement" itemscope itemtype="http://schema.org/ListItem"> | ||
<a href="https://wiki.en.it-processmaps.com/index.php/Event_Management#Roles_.7C_Responsibilities | <a itemprop="item" href="https://wiki.en.it-processmaps.com/index.php/Event_Management#Definitions"> | ||
<span itemprop="name">Definitions</span></a> | |||
<meta itemprop="position" content="3"></span> › | |||
<span itemprop="itemListElement" itemscope itemtype="http://schema.org/ListItem"> | |||
<a itemprop="item" href="https://wiki.en.it-processmaps.com/index.php/Event_Management#Roles_.7C_Responsibilities"> | |||
<span itemprop="name">Roles</span></a> | |||
<meta itemprop="position" content="4"></span> | |||
</span> | </span> | ||
</small></p> | </small></p> | ||
</ | |||
<!-- define schema.org/WebPage --> <span itemscope itemtype="https://schema.org/WebPage" itemref="md-webpage-description"> | |||
<meta itemprop="alternativeHeadline" content="ITIL Event Management" /> | |||
<meta itemprop="alternativeHeadline" content="Monitoring and Event Management" /> | |||
<meta itemprop="name" content="Event Management" /> | |||
<link itemprop="url" href="https://wiki.en.it-processmaps.com/index.php/Event_Management" /> | |||
<meta itemprop="inLanguage" content="en" /> | |||
<link itemprop="citation" href="https://wiki.de.it-processmaps.com/index.php/Event_Management" /> | |||
<link itemprop="citation" href="https://wiki.es.it-processmaps.com/index.php/ITIL_Gestion_de_Eventos" /> | |||
<meta itemprop="Headline" content="Event Management" /> | |||
<link itemprop="isPartOf" href="https://wiki.en.it-processmaps.com/index.php/ITIL_Service_Operation" /> | |||
<link itemprop="primaryImageOfPage" href="https://wiki.en.it-processmaps.com/images/1/13/Event-management-itil.jpg" /> | |||
<span id="https://wiki.en.it-processmaps.com/images/1/13/Event-management-itil.jpg" itemprop="image" itemscope itemtype="https://schema.org/ImageObject"> | |||
<meta itemprop="caption" content="ITIL Event Management"> | |||
<meta itemprop="contentUrl" content="https://wiki.en.it-processmaps.com/images/1/13/Event-management-itil.jpg" /> | |||
<meta itemprop="width" content="1200" /> | |||
<meta itemprop="height" content="900" /> | |||
<meta itemprop="representativeOfPage" content="true"/> | |||
<meta itemprop="dateCreated" content="2011-10-02" /> | |||
<meta itemprop="dateModified" content="2020-06-20" /> | |||
<span itemprop="thumbnail" itemscope itemtype="https://schema.org/ImageObject"> | |||
<meta itemprop="url" content="https://wiki.en.it-processmaps.com/images/thumb/1/13/Event-management-itil.jpg/800px-Event-management-itil.jpg" /> | |||
<meta itemprop="width" content="800" /> | |||
<meta itemprop="height" content="600" /> | |||
</span> | |||
<meta itemprop="keywords" content="Event Management" /> | |||
<meta itemprop="keywords" content="ITIL Event Management" /> | |||
<meta itemprop="keywords" content="Event Monitoring" /> | |||
</span> | |||
<link itemprop="author" href="https://www.linkedin.com/in/stefankempter" /> | |||
<meta itemprop="author" content="Stefan Kempter" /> | |||
<meta itemprop="creator copyrightHolder publisher" content="IT Process Maps" /> | |||
</span><p></html> | |||
<!-- This page is assigned to the following categories: --> | <!-- This page is assigned to the following categories: --> | ||
[[Category:ITIL V3]][[Category:ITIL | [[Category:ITIL 4]][[Category:ITIL 2011]][[Category:ITIL V3]][[Category:ITIL practice]][[Category:ITIL process]][[Category:Service Operation|Event Management]][[Category:Event Management|!]] | ||
<!-- --- --> | <!-- --- --> |
Latest revision as of 11:56, 31 December 2023
Objective: The objective of ITIL Event Management is to make sure Configuration Items (CIs) and services are constantly monitored. The Event Management process aims to filter and categorize Events in order to decide on appropriate actions if required.
Part of: Service Operation
Process Owner: IT Operations Manager
Process Description
The activities and process objectives of the Event Management process are mostly identical in ITIL V3 and V2 (Event Management was part of ICT Infrastructure Management).
Interfaces between Event Management and the other ITIL processes were adjusted in order to reflect the new ITIL process structure in ITIL V3.
In ITIL 2011 Event Management has been updated to reflect the concept of 1st Level Correlation and 2nd Level Correlation.
The process flows reflect the more detailed guidance in the ITIL 2011 books. The process overview of ITIL Event Management shows the key information flows (see fig. 1).
ITIL 4 refers to Event Management as a service management practice, and has renamed the practice to "Monitoring and event management".
Sub-Processes
These are the ITIL Event Management sub-processes and their process objectives:
Maintenance of Event Monitoring Mechanisms and Rules
- Process Objective: To set up and maintain the mechanisms for generating meaningful Events and effective rules for their filtering and correlating.
Event Filtering and 1st Level Correlation
- Process Objective: To filter out Events which are merely informational and can be ignored, and to communicate any Warning and Exception Events.
2nd Level Correlation and Response Selection
- Process Objective: To interpret the meaning of an Event and select a suitable response if required.
Event Review and Closure
- Process Objective: To check if Events have been handled appropriately and may be closed. This process also makes sure that Event logs are analyzed in order to identify trends or patterns which suggest corrective action must be taken.
Definitions
The following ITIL terms and acronyms (information objects) are used in the ITIL Event Management process to represent process outputs and inputs:
Event
- see Event Record
Event Categorization Scheme
- The Categorization Scheme for Events supports a consistent approach to dealing with specific types of Events. Ideally, this scheme should be harmonized with the schemes to categorize CIs, Incidents and Problems.
Event Filtering and Correlation Rules
- Rules and criteria used to determine if an Event is significant and to decide upon an appropriate response. Event Filtering and Correlation Rules are typically used by Event Monitoring systems. Some of those rules are defined during the Service Design stage, for example to ensure that Events are triggered when the required service availability is endangered.
Event Record
- A record describing a change of state which has significance for the management of a Configuration Item or service. The term Event is also used to mean an alert or notification created by any IT service, Configuration Item or monitoring tool. Events often require IT operations personnel to take actions, and may lead to Incidents being logged.
Event Trends and Patterns
- Any trends and patterns identified during analysis of significant Events, which suggest that improvements to the infrastructure are needed.
Roles | Responsibilities
IT Operations Manager - Process Owner
- An IT Operations Manager will be needed to take overall responsibility for a number of Service Operation activities. For instance, this role 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.
ITIL Role / Sub-Process | IT Operations Manager | IT Operator | (Event Monitoring System) | Other roles involved [3] |
---|---|---|---|---|
Maintenance of Event Monitoring Mechanisms and Rules | A[1]R[2] | R | - | R |
Event Filtering and 1st Level Correlation | A | - | R | - |
2nd Level Correlation and Response Selection | A | R | R | - |
Event Review and Closure | AR | - | - | - |
Remarks
[1] A: Accountable according to the RACI Model: Those who are ultimately accountable for the correct and thorough completion of the Event Management process.
[2] R: Responsible according to the RACI Model: Those who do the work to achieve a task within Event Management.
[3] In cooperation, as appropriate: IT Operations Manager, Access Manager, Capacity Manager, Availability Manager, IT Service Continuity Manager, Information Security Manager, Applications Analyst and/ or technical Analyst. → Role descriptions...
Notes
By: Stefan Kempter , IT Process Maps.
Process Description › Sub-Processes › Definitions › Roles