ITIL Glossary: Difference between revisions
No edit summary |
mNo edit summary |
||
Line 56: | Line 56: | ||
* → ITIL Processes, [[ITIL V3 Service Operation|ITIL Service Operation]] > [[Access Management]] | * → ITIL Processes, [[ITIL V3 Service Operation|ITIL Service Operation]] > [[Access Management]] | ||
====Application Development | ====Application Development==== | ||
* → ITIL Processes, [[ITIL V3 Service Transition|ITIL Service Transition]] > [[Application Development and Customization]] | * → ITIL Processes, [[ITIL V3 Service Transition|ITIL Service Transition]] > [[Application Development and Customization|Application Development]] | ||
====Application Developer==== | ====Application Developer==== | ||
Line 175: | Line 175: | ||
* The Capacity Report provides other [[ITIL Processes|Service Management processes]] and IT Management with information related to service and resource utilization and performance. | * The Capacity Report provides other [[ITIL Processes|Service Management processes]] and IT Management with information related to service and resource utilization and performance. | ||
* → ITIL Processes, [[ITIL V3 Service Design|ITIL Service Design]] > [[Capacity Management]] | * → ITIL Processes, [[ITIL V3 Service Design|ITIL Service Design]] > [[Capacity Management]] | ||
==== Change ==== | |||
* The addition, modification or removal of anything that could have an effect on IT services. | |||
* The scope should include changes to all architectures, processes, tools, metrics and documentation, as well as changes to IT services and other configuration items. | |||
* → ITIL Processes, [[ITIL V3 Service Transition|ITIL Service Transition]] > [[Change Management]] | |||
==== Change Advisory Board (CAB) ==== | ==== Change Advisory Board (CAB) ==== | ||
* → Roles within ITIL, [[Roles within ITIL V3#Change Advisory Board (CAB)|Change Advisory Board (CAB)]] | * → Roles within ITIL, [[Roles within ITIL V3#Change Advisory Board (CAB)|Change Advisory Board (CAB)]] | ||
==== Change | ==== Change Evaluation ==== | ||
* The Change | * → ITIL Processes, [[ITIL V3 Service Transition|ITIL Service Transition]] > [[ITIL Change Evaluation]] | ||
==== Change Evaluation Report ==== | |||
* Certain types of major Changes, like the introduction of a new service or a substantial change to an existing service, require formal Change evaluations before being authorized. | |||
* The results of a formal Change evaluation are documented in a Change Evaluation Report. | |||
* Change evaluations may be used at different points in a Change’s lifecycle, for example before authorizing the Change/ Release build or during the Post Implementation Review. | |||
* → ITIL Processes, [[ITIL V3 Service Transition|ITIL Service Transition]] > [[ITIL Change Evaluation]] | |||
==== Change Management ==== | |||
* → ITIL Processes, [[ITIL V3 Service Transition|ITIL Service Transition]] > [[Change Management]] | * → ITIL Processes, [[ITIL V3 Service Transition|ITIL Service Transition]] > [[Change Management]] | ||
==== Change Management ==== | ==== Change Management Policy ==== | ||
* The decision to authorize or reject a proposed Change is based on the completed Change Assessment. | |||
* In particular, the assessment is about properly understanding the risks associated with the implementation of a Change. | |||
* In this context, the Change Management Policy specifies the levels of authorization required to authorize different types of Changes and other rules for assessing Changes. | |||
* → ITIL Processes, [[ITIL V3 Service Transition|ITIL Service Transition]] > [[Change Management]] | * → ITIL Processes, [[ITIL V3 Service Transition|ITIL Service Transition]] > [[Change Management]] | ||
Line 191: | Line 207: | ||
==== Change Model ==== | ==== Change Model ==== | ||
* Change Models describe procedures for the handling of recurring Changes. | * Change Models describe procedures for the handling of recurring Changes. | ||
* | * While Change Models can be created for Changes of any scale, they are often used to define Standard Changes (low-risk, pre-authorized Changes like installing additional hardware on a client PC). | ||
* → ITIL Processes, [[ITIL V3 Service Transition|ITIL Service Transition]] > [[Change Management]] | * → ITIL Processes, [[ITIL V3 Service Transition|ITIL Service Transition]] > [[Change Management]] | ||
Line 198: | Line 214: | ||
* In most cases the Change Owner is identical with the RFC initiator. | * In most cases the Change Owner is identical with the RFC initiator. | ||
* Typically Changes are owned by Service Management roles (e.g. the Problem or Capacity Manager) or members of IT management. | * Typically Changes are owned by Service Management roles (e.g. the Problem or Capacity Manager) or members of IT management. | ||
====Change Proposal==== | |||
* A Change Proposal describes a proposed major Change, like the introduction of a new service or a substantial change to an existing service. | |||
* The purpose of Change Proposals is to communicate a proposed major Change and assess its risk, impact and feasibility before design activities begin. | |||
* Change Proposals are typically created in Service Portfolio Management. | |||
* → ITIL Processes, [[ITIL V3 Service Transition|ITIL Service Transition]] > [[Change Management]] | |||
====Change Record==== | ====Change Record==== | ||
The Change Record contains all the details of a Change, documenting the lifecycle of a single Change | * The Change Record contains all the details of a Change, documenting the lifecycle of a single Change. | ||
* It is usually created on the basis of a preceding Request for Change (RFC). | |||
* → ITIL Processes, [[ITIL V3 Service Transition|ITIL Service Transition]] > [[Change Management]] | * → ITIL Processes, [[ITIL V3 Service Transition|ITIL Service Transition]] > [[Change Management]] | ||
Line 284: | Line 307: | ||
==== Continual Service Improvement (CSI) ==== | ==== Continual Service Improvement (CSI) ==== | ||
* → ITIL Core Discipline, [[ITIL V3 CSI - Continual Service Improvement]] | * → ITIL Core Discipline, [[ITIL V3 CSI - Continual Service Improvement]] | ||
==== Cost Data for Service Provisioning ==== | ==== Cost Data for Service Provisioning ==== | ||
Line 305: | Line 324: | ||
==== Customer ==== | ==== Customer ==== | ||
* → Roles within ITIL, [[Roles within ITIL V3#Customer|Customer]] | * → Roles within ITIL, [[Roles within ITIL V3#Customer|Customer]] | ||
==== Customer Agreement Portfolio ==== | |||
* While the Service Catalogue holds a complete list of the services managed by the service provider, the Customer Agreement Portfolio contains all Service Agreements which provide the framework for delivering services to specific customers. | |||
* → ITIL Processes, [[ITIL V3 Service Design|ITIL Service Design]] > [[Service Level Management]] | |||
==== Customer Survey Evaluation ==== | ==== Customer Survey Evaluation ==== | ||
Line 320: | Line 343: | ||
== <span id="ITIL Glossary D">D</span> == | == <span id="ITIL Glossary D">D</span> == | ||
==== Data for | ==== Data for Project Plan Update ==== | ||
* Actual data related to project progress and resource consumption. | * Actual data related to project progress and resource consumption. | ||
* This information is sent from [[Release and Deployment Management|Release Management]] to [[Project Management - Transition Planning and Support|Project Management]] as input for Project Control and Reporting. | * This information is sent from [[Release and Deployment Management|Release Management]] to [[Project Management - Transition Planning and Support|Project Management]] as input for Project Control and Reporting. | ||
Line 344: | Line 367: | ||
* → [[ITIL Glossary#Definitive Media Library (DML)|Definitive Media Library (DML) - ITIL V3]] | * → [[ITIL Glossary#Definitive Media Library (DML)|Definitive Media Library (DML) - ITIL V3]] | ||
* → ITIL Processes, [[Configuration Management|Configuration Management - ITIL V2]] | * → ITIL Processes, [[Configuration Management|Configuration Management - ITIL V2]] | ||
==== Design Coordination ==== | |||
* → ITIL Processes, [[ITIL V3 Service Design|ITIL Service Design]] > [[ITIL Design Coordination|Design Coordination]] | |||
==== Development/ Installation QA Documentation ==== | ==== Development/ Installation QA Documentation ==== | ||
Line 360: | Line 386: | ||
== <span id="ITIL Glossary E">E</span> == | == <span id="ITIL Glossary E">E</span> == | ||
==== Emergency Change ==== | |||
* A Change that must be introduced as soon as possible – for example, to resolve a major incident or implement a security patch. | |||
* → ITIL Processes, [[ITIL V3 Service Transition|ITIL Service Transition]] > [[Change Management]] | |||
====Emergency Change Advisory Board (ECAB)==== | ====Emergency Change Advisory Board (ECAB)==== | ||
Line 368: | Line 398: | ||
** ITIL V2: [[Roles within ITIL#ITIL Bodies|Emergency Committee (EC)]] | ** ITIL V2: [[Roles within ITIL#ITIL Bodies|Emergency Committee (EC)]] | ||
** ITIL V3: [[Roles within ITIL V3#Emergency Change Advisory Board (ECAB)|Emergency Change Advisory Board (ECAB)]] | ** ITIL V3: [[Roles within ITIL V3#Emergency Change Advisory Board (ECAB)|Emergency Change Advisory Board (ECAB)]] | ||
==== Enterprise Architect ==== | ==== Enterprise Architect ==== | ||
Line 385: | Line 411: | ||
* → ITIL Processes, [[ITIL V3 Service Design|ITIL Service Design]] > [[Compliance Management]] | * → ITIL Processes, [[ITIL V3 Service Design|ITIL Service Design]] > [[Compliance Management]] | ||
==== Event | ==== Event Categorization Scheme ==== | ||
* Rules and criteria used to decide upon an appropriate response | * 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. | ||
* → ITIL Processes, [[ITIL V3 Service Operation|ITIL Service Operation]] > | * → ITIL Processes, [[ITIL V3 Service Operation|ITIL Service Operation]] > [[Event Management]] | ||
==== Event Filtering and Correlation Rules ==== | |||
* Rules and criteria used to determine if an Event is significant and to decide upon an appropriate response. | |||
* 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. | |||
* → ITIL Processes, [[ITIL V3 Service Operation|ITIL Service Operation]] > [[Event Management]] | |||
==== Event Management ==== | ==== Event Management ==== | ||
Line 404: | Line 436: | ||
== <span id="ITIL Glossary F">F</span> == | == <span id="ITIL Glossary F">F</span> == | ||
==== Facilities Management ==== | |||
* → ITIL Processes, [[ITIL V3 Service Operation|ITIL Service Operation]] > [[IT Facilities Management|Facilities Management]] | |||
==== Facilities Manager ==== | |||
* → Roles within ITIL, [[Roles within ITIL V3#Facilities Manager|Facilities Manager]] | |||
==== Financial Analysis ==== | ==== Financial Analysis ==== | ||
Line 479: | Line 517: | ||
==== Incident Status Information ==== | ==== Incident Status Information ==== | ||
* A message containing the present status of an Incident, usually sent to a user who earlier reported that Incident. | * A message containing the present status of an Incident, usually sent to a user who earlier reported that Incident. | ||
* → ITIL Processes, [[ITIL V3 Service Operation|ITIL Service Operation]] > [[Incident Management]] | * → ITIL Processes, [[ITIL V3 Service Operation|ITIL Service Operation]] > [[Incident Management]] | ||
Line 525: | Line 559: | ||
==== IT Facilities Management ==== | ==== IT Facilities Management ==== | ||
* → ITIL Processes, [[ITIL V3 Service Operation|ITIL Service Operation]] > [[IT Facilities Management | * → ITIL Processes, [[ITIL V3 Service Operation|ITIL Service Operation]] > [[IT Facilities Management|Facilities Management]] | ||
==== IT Operations Control ==== | ==== IT Operations Control ==== | ||
Line 600: | Line 631: | ||
====Known Error==== | ====Known Error==== | ||
* A problem that has a documented root cause and a | * A Known Error is a problem that has a documented root cause and (if possible) a Workaround. | ||
* Known Errors are | * Known Errors are managed throughout their lifecycle by the Problem Management Process. | ||
* Known Errors may also be | * The details of each Known Error are recorded in a Known Error Record stored in the [[ITIL Glossary#Known Error Database|Known Error Database (KEDB)]]. | ||
* As a rule, Known Errors are identified by Problem Management, but Known Errors may also be suggested by other Service Management disciplines, e.g. Incident Management, or by suppliers. | |||
* → ITIL Processes, [[ITIL V3 Service Operation|ITIL Service Operation]] > [[Problem Management]] | |||
====Known Error Database==== | |||
* The Known Error Database (KEDB) is created by Problem Management and used by Incident and Problem Management to manage all Known Error Records. | |||
* → ITIL Processes, [[ITIL V3 Service Operation|ITIL Service Operation]] > [[Problem Management]] | * → ITIL Processes, [[ITIL V3 Service Operation|ITIL Service Operation]] > [[Problem Management]] | ||
Line 640: | Line 676: | ||
==== OLA ==== | ==== OLA ==== | ||
* → [[ITIL Glossary#Operational Level Agreement (OLA)|Operational Level Agreement]] | * → [[ITIL Glossary#Operational Level Agreement (OLA)|Operational Level Agreement]] | ||
====Operational Level Agreement (OLA)==== | ====Operational Level Agreement (OLA)==== | ||
Line 651: | Line 683: | ||
* For example there could be an OLA - between the IT service provider and a procurement department to obtain hardware in agreed times - between the [[ITIL Glossary#Srvice Desk|Service Desk]] and a support group to provide Incident resolution in agreed times. | * For example there could be an OLA - between the IT service provider and a procurement department to obtain hardware in agreed times - between the [[ITIL Glossary#Srvice Desk|Service Desk]] and a support group to provide Incident resolution in agreed times. | ||
* → [[Checklist SLA OLA UC|ITIL Checklist SLA - OLA - UC]] | * → [[Checklist SLA OLA UC|ITIL Checklist SLA - OLA - UC]] | ||
* → ITIL Processes, [[ITIL V3 Service Design|ITIL Service Design]] > [[Service Level Management]] | |||
==== Outline of Service Requirements ==== | |||
* The desired outcome of a service, stated in terms of required service functionality (utility) and service levels (warranty). | |||
* Based on this information, detailed service requirements are specified during the Service Design stage. | |||
* → ITIL Processes, [[ITIL V3 Service Design|ITIL Service Design]] > [[Service Level Management]] | * → ITIL Processes, [[ITIL V3 Service Design|ITIL Service Design]] > [[Service Level Management]] | ||
Line 918: | Line 955: | ||
* The ITILv3 definition for the Service Design Package for an IT Service states: [The Service Design Package is one or more] “Service Design Documents defining all aspects of an IT Service and its Requirements through each stage of its Lifecycle. A Service Design Package is produced for each new IT Service, major Change, or IT Service Retirement”. | * The ITILv3 definition for the Service Design Package for an IT Service states: [The Service Design Package is one or more] “Service Design Documents defining all aspects of an IT Service and its Requirements through each stage of its Lifecycle. A Service Design Package is produced for each new IT Service, major Change, or IT Service Retirement”. | ||
* → [[Checklist Service Design Package SDP|ITIL Checklist Service Design Package - SDP]] | * → [[Checklist Service Design Package SDP|ITIL Checklist Service Design Package - SDP]] | ||
* → ITIL Processes, [[ITIL V3 Service Design|ITIL Service Design]] > [[Service | * → ITIL Processes, [[ITIL V3 Service Design|ITIL Service Design]] > [[ITIL Design Coordination]] | ||
==== Service Design Policy ==== | |||
* The Service Design Policy provides guidance on how to ensure that a consistent approach is applied to all design activity. | |||
* In particular, the Service Design Policy specifies which projects or Changes are required to undergo the formal Service Design stage, and who needs to be involved in Service Design to ensure that all relevant aspects are considered. | |||
* → ITIL Processes, [[ITIL V3 Service Design|ITIL Service Design]] > [[ITIL Design Coordination]] | |||
==== Service Design Validation Report ==== | ==== Service Design Validation Report ==== | ||
Line 1,013: | Line 1,055: | ||
==== Service Request Fulfilment Group ==== | ==== Service Request Fulfilment Group ==== | ||
* → Roles within ITIL, [[Roles within ITIL V3#Service Request Fulfilment Group|Service Request Fulfilment Group]] | * → Roles within ITIL, [[Roles within ITIL V3#Service Request Fulfilment Group|Service Request Fulfilment Group]] | ||
==== Service Request Model ==== | |||
* A (Service) Request Model defines specific agreed steps that will be followed for a Service Request of a particular type (or category). | |||
* → ITIL Processes, [[ITIL V3 Service Operation|ITIL Service Operation]] > [[Request Fulfilment]] | |||
==== Service Request Record ==== | |||
* A record containing all details of a Service Request. Service Requests are formal requests from a user for something to be provided – for example, a request for information or advice; to reset a password; or to install a workstation for a new user. | |||
* → ITIL Processes, [[ITIL V3 Service Operation|ITIL Service Operation]] > [[Request Fulfilment]] | |||
==== Service Request Status Information ==== | ==== Service Request Status Information ==== | ||
Line 1,057: | Line 1,107: | ||
==== Seven-Step Improvement Guideline ==== | ==== Seven-Step Improvement Guideline ==== | ||
* The Seven-Step Improvement Method is presented in the ITIL | * The Seven-Step Improvement Method is presented in the ITIL books as the Seven-step Improvement Process. | ||
* Rather than a process it is in fact the description of a methodology which can be universally applied to identify shortcomings in services and processes and to implement improvements. | * Rather than a process it is in fact the description of a methodology which can be universally applied to identify shortcomings in services and processes and to implement improvements. | ||
* → ITIL Processes, [[ITIL V3 CSI - Continual Service Improvement|ITIL Continual Service Improvement (CSI)]] > [[Process Evaluation]] | * → ITIL Processes, [[ITIL V3 CSI - Continual Service Improvement|ITIL Continual Service Improvement (CSI)]] > [[Process Evaluation]] | ||
Line 1,071: | Line 1,121: | ||
* A set of terms and conditions which are routinely attached to contracts and orders when procuring services or products. | * A set of terms and conditions which are routinely attached to contracts and orders when procuring services or products. | ||
* → ITIL Processes, [[ITIL V3 Service Design|ITIL Service Design]] > [[Supplier Management]] | * → ITIL Processes, [[ITIL V3 Service Design|ITIL Service Design]] > [[Supplier Management]] | ||
==== Status Inquiry ==== | |||
* An inquiry regarding the present status of an Incident or Service Request, usually from a user who earlier reported an Incident or submitted a request. | |||
* → ITIL Processes, [[ITIL V3 Service Operation|ITIL Service Operation]] > [[Incident Management]] | |||
==== Strategic Plan ==== | ==== Strategic Plan ==== | ||
Line 1,090: | Line 1,144: | ||
* → ITIL Processes, [[ITIL V3 Service Operation|ITIL Service Operation]] > [[Problem Management]] | * → ITIL Processes, [[ITIL V3 Service Operation|ITIL Service Operation]] > [[Problem Management]] | ||
==== Suggested Problem ==== | ==== Suggested new Problem ==== | ||
* A notification about a suspected Problem, handed over to [[Problem Management]] for further investigation. | * A notification about a suspected Problem, handed over to [[Problem Management]] for further investigation, possibly leading to the formal logging of a Problem. | ||
* → ITIL Processes, [[ITIL V3 Service Operation|ITIL Service Operation]] > [[Problem Management]] | |||
==== Suggested new Workaround ==== | |||
* A suggestion to enter a new [[ITIL Glossary#Workaround|Workaround]] in the Known Error Database, for example raised by the [[ITIL Glossary#Service Desk|Service Desk]] or by [[Release and Deployment Management|Release Management]]. Workarounds are managed throughout their lifecycle by [[Problem Management]]. | |||
* → ITIL Processes, [[ITIL V3 Service Operation|ITIL Service Operation]] > [[Problem Management]] | * → ITIL Processes, [[ITIL V3 Service Operation|ITIL Service Operation]] > [[Problem Management]] | ||
Line 1,098: | Line 1,156: | ||
* Suggestions for process improvements may originate from anywhere within the IT organization. | * Suggestions for process improvements may originate from anywhere within the IT organization. | ||
* → ITIL Processes, [[ITIL V3 CSI - Continual Service Improvement|ITIL Continual Service Improvement (CSI)]] > [[Process Evaluation]] | * → ITIL Processes, [[ITIL V3 CSI - Continual Service Improvement|ITIL Continual Service Improvement (CSI)]] > [[Process Evaluation]] | ||
==== Suggestions and Complaints ==== | ==== Suggestions and Complaints ==== | ||
* Suggestions and complaints from the customer side which are addressed in the Continual Service Improvement process. | * Suggestions and complaints from the customer side which are addressed in the Continual Service Improvement process. | ||
* → ITIL Processes, [[ITIL V3 CSI - Continual Service Improvement|ITIL Continual Service Improvement (CSI)]] > [[Service Evaluation]] | * → ITIL Processes, [[ITIL V3 CSI - Continual Service Improvement|ITIL Continual Service Improvement (CSI)]] > [[Service Evaluation]] | ||
==== Supplier and Contract Database (SCD) ==== | ==== Supplier and Contract Database (SCD) ==== | ||
Line 1,151: | Line 1,201: | ||
== <span id="ITIL Glossary T">T</span> == | == <span id="ITIL Glossary T">T</span> == | ||
==== Technical/ Administration Manual ==== | |||
* A document describing the procedures required to run and maintain an application or infrastructure component. | |||
* → ITIL Processes, [[ITIL V3 Service Transition|ITIL Service Transition]] > [[Application Development and Customization|Application Development]] | |||
==== Technical Analyst ==== | ==== Technical Analyst ==== | ||
Line 1,199: | Line 1,253: | ||
==== User Escalation ==== | ==== User Escalation ==== | ||
* Escalation regarding the processing of an Incident, initiated by a user experiencing delays or a failure to restore their services. | * Escalation regarding the processing of an Incident or Service Request, initiated by a user experiencing delays or a failure to restore their services. | ||
* → ITIL Processes, [[ITIL V3 Service Operation|ITIL Service Operation]] > [[Incident Management]] | * → ITIL Processes, [[ITIL V3 Service Operation|ITIL Service Operation]] > [[Incident Management]] | ||
Line 1,214: | Line 1,268: | ||
* A request to create, modify or delete a User Identity. | * A request to create, modify or delete a User Identity. | ||
* → ITIL Processes, [[ITIL V3 Service Operation|ITIL Service Operation]] > [[Access Management]] | * → ITIL Processes, [[ITIL V3 Service Operation|ITIL Service Operation]] > [[Access Management]] | ||
==== User Manual ==== | |||
* A document for end-users, describing how to use an application or system. | |||
* → ITIL Processes, [[ITIL V3 Service Transition|ITIL Service Transition]] > [[Application Development and Customization|Application Development]] | |||
==== User Role ==== | ==== User Role ==== | ||
Line 1,239: | Line 1,297: | ||
====Workaround==== | ====Workaround==== | ||
* | * Workarounds are temporary solutions aimed at reducing or eliminating the impact of Known Errors (and thus Problems) for which a full resolution is not yet available. | ||
* Workarounds | * As such, Workarounds are often applied to reduce the impact of Incidents or Problems if their underlying causes cannot be readily identified or removed. Workarounds are typically either documented as part of Known Error Records or in records of their own, linked to Known Error and Problem Records. | ||
* → ITIL Processes, [[ITIL V3 Service Operation|ITIL Service Operation]] > [[Problem Management]] | * → ITIL Processes, [[ITIL V3 Service Operation|ITIL Service Operation]] > [[Problem Management]] | ||
Revision as of 19:25, 28 November 2011
<seo metakeywords="itil definitions, itil glossary" metadescription="The ITIL Glossary provides you with definitions for the most important ITIL Glossary Terms. You are able to navigate the ITIL Glossary: ... " />
The ITIL Glossary provides you with definitions for the most important ITIL V3 and V2 Glossary Terms in alphabetical order.[1]
You are able to navigate the ITIL Glossary: Related contents of this ITIL Wiki, like ITIL process descriptions and role definitions can be reached via links.
Remark: Source (partially): ITIL Glossaries/ Acronyms © Crown Copyright Office of Government Commerce. Reproduced with the permission of the Controller of HMSO and the Office of Government Commerce.
The complete ITIL Glossary compiled by the OGC is available for download from the Internet.
1 | ... | 9 | ||||||||||
A | B | C | D | E | F | G | H | I | J | K | L | M |
N | O | P | Q | R | S | T | U | V | W | X | Y | Z |
1-9
1st Level Support
- → Roles within ITIL, 1st Level Support
2nd Level Support
- → Roles within ITIL, 2nd Level Support
3rd Level Support
- → Roles within ITIL, 3rd Level Support
7-Step Improvement Guideline
A
Access Management
- → ITIL Processes, ITIL Service Operation > Access Management
Access Manager
- → Roles within ITIL, Access Manager
Access Rights
- A set of data defining what services a user is allowed to access.
- This definition is achieved by assigning the user, identified by his User Identity, to one or more User Roles.
- → ITIL Processes, ITIL Service Operation > Access Management
Application Development
- → ITIL Processes, ITIL Service Transition > Application Development
Application Developer
- → Roles within ITIL, Application Developer
Application Framework
- Application Frameworks aim to promote the re-use of components and the standardizing of technologies on which applications are based.
- For this reason, they have to be planned and managed separately from software development projects – but must be carefully aligned with the needs of software developers.
- Application Frameworks define classes of applications, typically with common non-functional requirements.
- → ITIL Processes, ITIL Service Design > Architecture Management
Application Management
- → ITIL Processes, ITIL Service Operation > Application Management
Application Manager
- → Roles within ITIL, Application Manager
Applications Analyst
- → Roles within ITIL, Applications Analyst
Architecture Management
- → ITIL Processes, ITIL Service Design > Architecture Management
Availability Design Guidelines
- The Availability Design Guidelines define from a technical point of view how the required availability levels can be achieved, including specific instructions for application development and for externally sourced infrastructure components.
- → ITIL Processes, ITIL Service Design > Availability Management
Availability Guidelines for the Service Desk
- Rules produced by Availability Management on how to manage Incidents causing unavailability, to prevent minor Incidents from becoming major Incidents.
- → ITIL Processes, ITIL Service Design > Availability Management
Availability Improvement Plan
- A Plan to ensure that existing and future Availability requirements for IT Services can be fulfilled cost-effectively.
- It embraces a description of the current situation, improvement measures and planned new guidelines.
- → ITIL Processes, Availability Management - ITIL V2
Availability/ ITSCM/ Security Testing Schedule
- A schedule for the regular testing of all availability, continuity and security mechanisms, jointly maintained by Availability, IT Service Continuity and Information Security Management.
- → ITIL Processes,
Availability Management
- → ITIL Processes, ITIL Service Design > Availability Management
Availability Management Information System
- A virtual repository of all Availability Management data, usually stored in multiple physical locations.
- → ITIL Processes, ITIL Service Design > Availability Management
Availability Manager
- → Roles within ITIL, Availability Manager
Availability Plan
- The Availability Plan contains detailed information about initiatives aimed at improving service and/ or component availability.
- → ITIL Processes, ITIL Service Design > Availability Management
Availability Report
- The Availability Report provides other Service Management processes and IT Management with information related to service and infrastructure component availability.
- → ITIL Processes, ITIL Service Design > Availability Management
B
Baseline
- An ITSM can be used as a starting point to measure the effectiveness of a Service Improvement Plan
- A Performance Baseline can be used to measure changes in Performance over the lifetime of an IT Service
- A Configuration Management Baseline can be used to enable the IT Infrastructure to be restored to a known Configuration if a Change or Release fails.
Budget Allocation
- A budget allocated by the Financial Manager to implement a Change. Budget Allocations are issued in response to Budget Requests originating from any Service Management process in conjunction with Requests for Change.
- → ITIL Processes, ITIL Service Strategy > Financial Management
Budget Request
- A request for a budget, typically issued from any of the Service Management processes at the same time when compiling a Request for Change.
- An approved Budget Request means that the required financial resources for implementing a Change are approved by Financial Management.
- → ITIL Processes, ITIL Service Strategy > Financial Management
Business Continuity Strategy
- An outline of the approach to ensure the continuity of Vital Business Functions in the case of disaster events.
- The Business Continuity Strategy is prepared by the business and serves as a starting point for producing the IT Service Continuity Strategy.
- → ITIL Processes, ITIL Service Design > IT Service Continuity Management
Business Impact and Risk Analysis
- The Business Impact Analysis (BIA) identifies Vital Business Functions (VBFs) and their dependencies.
- These dependencies may include suppliers, people, other business processes, services etc..
- The Risk Analysis identifies threats and vulnerabilities to business assets, and indicates how vulnerable each asset is to those threats.
- → ITIL Processes, ITIL Service Design > Risk Management
Business Planning Information
- Business Planning Information includes important input from clients and external service providers, especially for devising the Service Strategy and looking for ways to improve services.
- This input will highlight, for example, planned business initiatives like the introduction of new product/ service offerings or the expansion into new markets, as well as information on the future development of business activity, especially expected increases in business transaction volumes.
- This information helps the service organization understand the businesses it serves and their plans for the future, allowing it to offer and develop the right set of services.
- → ITIL Processes, ITIL Service Strategy > Service Portfolio Management
C
CAB Agenda Template
- The CAB Agenda lists the topics for discussion in a CAB meeting.
- → ITIL Processes, ITIL Service Transition > Change Management
Capacity Management
- → ITIL Processes, ITIL Service Design > Capacity Management
Capacity Management Information System
- A virtual repository of all Capacity Management data, usually stored in multiple physical locations.
- → ITIL Processes, ITIL Service Design > Capacity Management
Capacity Manager
- → Roles within ITIL, Capacity Manager
Capacity Plan
- A Capacity Plan is used to manage the resources required to deliver IT services.
- The plan contains scenarios for different predictions of business demand, and costed options to deliver the agreed service level targets.
- → ITIL Processes, ITIL Service Design > Capacity Management
Capacity Report
- The Capacity Report provides other Service Management processes and IT Management with information related to service and resource utilization and performance.
- → ITIL Processes, ITIL Service Design > Capacity Management
Change
- The addition, modification or removal of anything that could have an effect on IT services.
- The scope should include changes to all architectures, processes, tools, metrics and documentation, as well as changes to IT services and other configuration items.
- → ITIL Processes, ITIL Service Transition > Change Management
Change Advisory Board (CAB)
- → Roles within ITIL, Change Advisory Board (CAB)
Change Evaluation
- → ITIL Processes, ITIL Service Transition > ITIL Change Evaluation
Change Evaluation Report
- Certain types of major Changes, like the introduction of a new service or a substantial change to an existing service, require formal Change evaluations before being authorized.
- The results of a formal Change evaluation are documented in a Change Evaluation Report.
- Change evaluations may be used at different points in a Change’s lifecycle, for example before authorizing the Change/ Release build or during the Post Implementation Review.
- → ITIL Processes, ITIL Service Transition > ITIL Change Evaluation
Change Management
- → ITIL Processes, ITIL Service Transition > Change Management
Change Management Policy
- The decision to authorize or reject a proposed Change is based on the completed Change Assessment.
- In particular, the assessment is about properly understanding the risks associated with the implementation of a Change.
- In this context, the Change Management Policy specifies the levels of authorization required to authorize different types of Changes and other rules for assessing Changes.
- → ITIL Processes, ITIL Service Transition > Change Management
Change Manager
- → Roles within ITIL, Change Manager
Change Model
- Change Models describe procedures for the handling of recurring Changes.
- While Change Models can be created for Changes of any scale, they are often used to define Standard Changes (low-risk, pre-authorized Changes like installing additional hardware on a client PC).
- → ITIL Processes, ITIL Service Transition > Change Management
Change Owner
- The person backing a Change and holding a budget for its implementation.
- In most cases the Change Owner is identical with the RFC initiator.
- Typically Changes are owned by Service Management roles (e.g. the Problem or Capacity Manager) or members of IT management.
Change Proposal
- A Change Proposal describes a proposed major Change, like the introduction of a new service or a substantial change to an existing service.
- The purpose of Change Proposals is to communicate a proposed major Change and assess its risk, impact and feasibility before design activities begin.
- Change Proposals are typically created in Service Portfolio Management.
- → ITIL Processes, ITIL Service Transition > Change Management
Change Record
- The Change Record contains all the details of a Change, documenting the lifecycle of a single Change.
- It is usually created on the basis of a preceding Request for Change (RFC).
- → ITIL Processes, ITIL Service Transition > Change Management
Change Request to CMS Structure
- A request from a Service Management process to change the CMS structure.
- This request is sent to Configuration Management if new CIs or attributes must be recorded but the CMS's structure is not adequate for holding the new data.
- → ITIL Processes, ITIL Service Transition > Service Asset and Configuration Management
Change Request to Enterprise Architecture
- A request to change or extend the Enterprise Architecture, usually issued from the Service Design process when the introduction or modification of a service is not possible within the constraints of the existing application, infrastructure and information/ data architectures.
- → ITIL Processes, ITIL Service Design > Architecture Management
Change Request to Process Architecture
- A request to change or extend the Process Architecture, usually issued from the Service Design process when the introduction or modification of a service is not possible within the constraints of the existing process framework.
- → ITIL Processes, ITIL Continual Service Improvement (CSI) > Process Evaluation
Change Schedule
- A Document that lists all approved Changes and their planned implementation dates.
- A Change Schedule is sometimes called a Forward Schedule of Changes (FSC).
- → ITIL Processes, ITIL Service Transition > Change Management
CI (Configuration Item)
- CIs (Configuration Items) are mainly hardware or software items and are characterized by their attributes (recorded in the CI’s Configuration Record) and their relationships to other CIs.
- → ITIL Checklist CMS - CMDB
- → ITIL Processes, ITIL Service Transition > Service Asset and Configuration Management
CI Status Monitoring Report
- A report from Configuration Management covering the lifecycle of each Configuration Item, stating important CI status changes like addition, removal, responsibility change, or Downtimes (especially important for Availability Management).
- → ITIL Processes, Configuration Management - ITIL V2
Client (Contract Partner)
- → Roles within ITIL, Client (Contract Partner)
CMS/ CMDB
- The Configuration Management System (CMS) is a coherent logical model of the IT organization’s infrastructure, typically made up of several Configuration Management Databases (CMDBs) as physical sub-systems.
- It is used to store information on all Configuration Items (CIs) under the control of Configuration Management.
- → ITIL Checklist CMS - CMDB
- → ITIL Processes, ITIL Service Transition > Service Asset and Configuration Management
CMS Change Policy
- A set of rules defining who is authorized to modify the structure and contents of the CMS.
- → ITIL Processes, ITIL Service Transition > Service Asset and Configuration Management
Complaints Log
- The Complaints Log contains the full history of all received customer complaints, complete with activities triggered by those complaints.
- → ITIL Processes, ITIL Continual Service Improvement (CSI) > Service Evaluation
Compliance Management
- → ITIL Processes, ITIL Service Design > Compliance Management
Compliance Manager
- → Roles within ITIL, Compliance Manager
Compliance Register
- The Compliance Register is a tool used by the Compliance Management process to keep an overview of all compliance requirements and the measures applied to ensure their enforcement.
- → ITIL Processes, ITIL Service Design > Compliance Management
Compliance Review
- The Compliance Review documents the results of regular process and system compliance assessments.
- In particular, it contains any identified deviations from compliance requirements, as well as measures to correct the situation.
- → ITIL Processes, ITIL Service Design > Compliance Management
Config Management Database (CMDB)
- A Database used to manage Configuration Records throughout their Lifecycle.
- The CMDB records the attributes of each CI, and relationships with other CIs.
- A CMDB may also contain other information refering to CIs, for example Incident, Problem and Change Records.
- The CMDB is maintained by Configuration Management and is used by all IT Service Management Processes.
- → ITIL Checklist CMS - CMDB
- → ITIL Processes, Configuration Management - ITIL V2
Configuration Audit Report
- A report summarizing the results of a CMS audit, highlighting revealed differences between CMS records and actually installed CIs.
- → ITIL Processes, ITIL Service Transition > Service Asset and Configuration Management
Configuration Management
- → ITIL Processes,
Configuration Manager
- → Roles within ITIL, Configuration Manager
Continual Service Improvement (CSI)
- → ITIL Core Discipline, ITIL V3 CSI - Continual Service Improvement
Cost Data for Service Provisioning
- The cost for providing a service, calculated by Financial Management as a basis for calculating the price a customer is expected to pay for a service.
- → ITIL Processes, ITIL Service Strategy > Financial Management
CSI
- → ITIL Core Discipline, ITIL V3 CSI - Continual Service Improvement
CSI Initiative
- → ITIL Processes, ITIL Continual Service Improvement (CSI) > Definition of CSI Initiatives
- → ITIL Processes, ITIL Continual Service Improvement (CSI) > Monitoring of CSI Initiatives
CSI Monitoring
- → ITIL Processes, ITIL Continual Service Improvement (CSI) > Monitoring of CSI Initiatives
Customer
- → Roles within ITIL, Customer
Customer Agreement Portfolio
- While the Service Catalogue holds a complete list of the services managed by the service provider, the Customer Agreement Portfolio contains all Service Agreements which provide the framework for delivering services to specific customers.
- → ITIL Processes, ITIL Service Design > Service Level Management
Customer Survey Evaluation
- The evaluation of a Customer Satisfaction Survey, presenting the results and findings in a condensed way.
- → ITIL Processes, ITIL Continual Service Improvement (CSI) > Service Evaluation
Customer Survey Questionnaire
- A questionnaire for surveying customer satisfaction, aimed at getting insight into overall customer satisfaction and customers' views on specific (aspects of) services.
- → ITIL Processes, ITIL Continual Service Improvement (CSI) > Service Evaluation
Customer Survey Response
- The response to a service provider's customer survey, typically a completed questionnaire.
- → ITIL Processes, ITIL Continual Service Improvement (CSI) > Service Evaluation
D
Data for Project Plan Update
- Actual data related to project progress and resource consumption.
- This information is sent from Release Management to Project Management as input for Project Control and Reporting.
- → ITIL Processes, ITIL Service Transition > Project Management - Transition Planning and Support
Definition of Improvement Initiatives
- → ITIL Processes, ITIL Continual Service Improvement (CSI) > Definition of Improvement Initiatives
Definitive Media Library (DML)
- One or more locations in which the definitive and approved versions of all software Configuration Items are securely stored.
- The DML may also contain associated CIs such as licenses and documentation.
- The DML is a single logical storage area even if there are multiple locations.
- All software in the DML is under the control of Change and Release Management and is recorded in the Configuration Management System.
- Only software from the DML is acceptable for use in a Release.
- → ITIL Processes, ITIL Service Transition > Service Asset and Configuration Management
Definitive Software Library (DSL)
- One or more locations in which the definitive and approved versions of all software Configuration Items are securely stored.
- The DSL may also contain associated CIs such as licenses and documentation.
- The DSL is a single logical storage area even if there are multiple locations.
- All software in the DSL is under the control of Change and Release Management and is recorded in the CMDB.
- Only software from the DSL is acceptable for use in a Release.
- → Definitive Media Library (DML) - ITIL V3
- → ITIL Processes, Configuration Management - ITIL V2
Design Coordination
- → ITIL Processes, ITIL Service Design > Design Coordination
Development/ Installation QA Documentation
- A documentation of tests and quality assurance measures applied during the development or installation of applications, systems and other infrastructure components (e.g. component tests, code walk-throughs, ...).
- A complete Development/ Installation QA Documentation testifies that the required QA measures were applied prior to handing a Release component over to Release Management.
- → ITIL Processes, ITIL Service Transition > Service Validation and Testing
Development Work Order
- A Work Order for the development or customization of an application or system, typically issued from Release Management.
- → ITIL Processes, ITIL Service Transition > Release and Deployment Management
Disaster Recovery Invocation Guideline
- A document produced by IT Service Continuity Management with detailed instructions on when and how to invoke the procedure for fighting a disaster.
- Most importantly, the guideline defines the first steps to be taken by 1st Level Support after learning that a (suspected) disaster has occurred.
- → ITIL Processes, ITIL Service Design > IT Service Continuity Management
E
Emergency Change
- A Change that must be introduced as soon as possible – for example, to resolve a major incident or implement a security patch.
- → ITIL Processes, ITIL Service Transition > Change Management
Emergency Change Advisory Board (ECAB)
- → Roles within ITIL, Emergency Change Advisory Board (ECAB)
Emergency Committee (EC)
- → Roles within ITIL,
- ITIL V2: Emergency Committee (EC)
- ITIL V3: Emergency Change Advisory Board (ECAB)
Enterprise Architect
- → Roles within ITIL, Enterprise Architect
Enterprise Architecture (EA)
- An Enterprise Architecture (EA) is a description of the essential components of a business, including their interrelationships.
- In most cases, an EA covers the following domains: Business, Information, Applications and Technology.
- → ITIL Processes, ITIL Service Design > Architecture Management
Enterprise Policies and Regulations
- A set of binding enterprise policies and regulations which are an important input for the Compliance Management process.
- → ITIL Processes, ITIL Service Design > Compliance Management
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.
- → ITIL Processes, ITIL Service Operation > Event Management
Event Filtering and Correlation Rules
- Rules and criteria used to determine if an Event is significant and to decide upon an appropriate response.
- 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.
- → ITIL Processes, ITIL Service Operation > Event Management
Event Management
- → ITIL Processes, ITIL Service Operation > Event Management
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 typically require IT operations personnel to take actions, and often lead to Incidents being logged.
- → ITIL Processes, ITIL Service Operation > Event Management
Event Trends and Patterns
- Any trends and patterns identified during analysis of significant Events, which suggest that improvements to the infrastructure are needed.
- → ITIL Processes, ITIL Service Operation > Event Management
F
Facilities Management
- → ITIL Processes, ITIL Service Operation > Facilities Management
Facilities Manager
- → Roles within ITIL, Facilities Manager
Financial Analysis
- The Financial Analysis is an important input to the Portfolio Management process.
- It contains information on the costs for providing services and provides insight into the profitability of services and customers.
- → ITIL Checklist Financial Analysis
- → ITIL Processes, ITIL Service Strategy > Financial Management
Financial Data Categories
- Various categories are used to structure financial data, as a means to gain insight into the underlying costs of service provisioning and service profitability.
- → ITIL Processes, ITIL Service Strategy > Financial Management
Financial Management
- → ITIL Processes, ITIL Service Strategy > Financial Management
Financial Management for IT Services
- → ITIL Processes,
- ITIL V2: Financial Management for IT Services
- ITIL V3: ITIL Service Strategy > Financial Management
Financial Manager
- → Roles within ITIL, Financial Manager
Forward Schedule of Changes (FSC)
- A Document that lists all approved Changes and their planned implementation dates.
- A Forward Schedule of Changes is sometimes also known as a Change Schedule.
- → ITIL Processes, ITIL Service Transition > Change Management
G
H
I
Improvement Initiative
- → ITIL Processes, ITIL Continual Service Improvement (CSI) > Definition of CSI Initiatives
- → ITIL Processes, ITIL Continual Service Improvement (CSI) > Monitoring of CSI Initiatives
Incident
- An Incident is defined as an unplanned interruption or reduction in quality of an IT service (a Service Interruption).
- → ITIL Processes, ITIL Service Operation > Incident Management
Incident Escalation Rules
- A set of rules defining a hierarchy for escalating Incidents, and triggers which lead to escalations. Triggers are usually based on Incident severity and resolution times.
- → ITIL Processes, ITIL Service Operation > Incident Management
Incident Management
- → ITIL Processes, ITIL Service Operation > Incident Management
Incident Management Report
- A series of reports produced by the Incident Manager for various target groups (IT Management, Service Level Management, other Service Management processes, or Incident Management itself).
- Depending on the target group, the Report will focus upon process quality, volume of enquiries, service quality, itemization of Incidents by category, ...
- → ITIL Processes, ITIL Service Operation > Incident Management
Incident Manager
- → Roles within ITIL, Incident Manager
Incident Model
- An Incident Model contains the pre-defined steps that should be taken for dealing with a particular type of Incident.
- This is a way to ensure that routinely occurring Incidents are handled efficiently and effectively.
- → ITIL Processes, ITIL Service Operation > Incident Management
Incident Prioritization Guideline
- The Incident Prioritization Guideline describes the rules for assigning priorities to Incidents, including the definition of what constitutes a Major Incident.
- Since Incident Management escalation rules are usually based on priorities, assigning the correct priority to an Incident is essential for triggering appropriate escalations.
- → ITIL Processes, ITIL Service Operation > Incident Management
Incident Record
- A set of data with all details of an Incident, documenting the history of the Incident from registration to resolution.
- An Incident is defined as an unplanned interruption or reduction in quality of an IT service.
- Every event that could potentially impair an IT service in the future is also an Incident (e.g. the failure of one hard-drive of a set of mirrored drives).
- → ITIL Checklist Incident Record
- → ITIL Processes, ITIL Service Operation > Incident Management
Incident Status Information
- A message containing the present status of an Incident, usually sent to a user who earlier reported that Incident.
- → ITIL Processes, ITIL Service Operation > Incident Management
Index of Disaster-Relevant Information
- A catalogue of all information that is relevant in the event of disasters. This document is maintained and circulated by IT Service Continuity Management to all members of IT staff with responsibilities for fighting disasters.
- → ITIL Processes, ITIL Service Design > IT Service Continuity Management
Indirect Cost Allocation Table
- A table used to allocate indirect costs that are shared among multiple services, defining the rules how those costs are spread among the services.
- → ITIL Processes, ITIL Service Strategy > Financial Management
Information Security Management
- → ITIL Processes, ITIL Service Design > Information Security Management
Information Security Manager
- → Roles within ITIL, Information Security Manager
Information Security Policy
- The main Information Security Policy contains an outline of the approach to ensure the security of IT services and systems.
- It is typically complemented by a set of more specific underpinning policies, e.g. policies on e-mail usage or remote system access.
- The Information Security Policy includes a list of security-related risks and existing or planned Security Controls to address those risks.
- → ITIL Processes, ITIL Service Design > Information Security Management
Information Security Report
- The Information Security Report provides other Service Management processes and IT Management with information related to Information Security issues.
- → ITIL Processes, ITIL Service Design > Information Security Management
Installation Work Order
- A Work Order for the installation of an application, system or infrastructure component, typically issued from Release Management.
- → ITIL Processes, ITIL Service Transition > Release and Deployment Management
Invoice
- The invoice for the delivery of a service or product.
- → ITIL Processes, ITIL Service Strategy > Financial Management
IT Budget
- The IT Budget is an annual financial plan that provides a forecast of expected expenditures and allocates financial resources to the various service management processes and organizational units within the IT organization.
- → ITIL Processes, ITIL Service Strategy > Financial Management
ITC Infrastructure Manager
- → Roles within ITIL, ITC Infrastructure Manager
IT Facilities Management
- → ITIL Processes, ITIL Service Operation > Facilities Management
IT Operations Control
- → ITIL Processes, ITIL Service Operation > IT Operations Control
IT Operations Management
- → ITIL Processes, ITIL Service Operation, ITIL 2007 > IT Operations Management
IT Operations Manager
- → Roles within ITIL, IT Operations Manager
IT Operator
- → Roles within ITIL, IT Operator
IT Service Continuity Management
- → ITIL Processes, ITIL Service Design > IT Service Continuity Management
IT Service Continuity Manager
- → Roles within ITIL, IT Service Continuity Manager
IT Service Continuity Plan
- A plan containing the steps required to recover one or more IT Services in the event of a desaster.
- The plan also defines the basic conditions under which it applies, as well as communication mechanisms.
- The IT Service Continuity Plan should be part of a desaster plan for the whole business.
- → ITIL Processes, IT Service Continuity Management - ITIL V2
IT Service Continuity Report
- The IT Service Continuity Report is created at regular intervals and provides other Service Management processes and IT Management with information related to disaster prevention.
- → ITIL Processes, ITIL Service Design > IT Service Continuity Management
IT Service Continuity Plan
IT Service Continuity Plans underpin the ITSCM Strategy, describing how continuity is ensured for specific disaster events and services.
- It specifies the measures to enhance the resilience of services and describes how to effectively respond to a disaster event.
- ITSCM Plans usually include references to more detailed Recovery Plans with specific instructions for returning systems to a working state.
- → ITIL Processes, ITIL Service Design > IT Service Continuity Management
IT Service Continuity Strategy
- The IT Service Continuity Strategy contains an outline of the approach to ensure the continuity of vital services in the case of disaster events.
- It includes a list of Vital Business Functions and applied risk reduction or recovery options.
- The IT Service Continuity Strategy should be based on a Business Continuity Strategy.
- The ITSCM Strategy is underpinned by more detailed ITSCM Plans, describing how continuity is ensured for specific disaster events and services.
- → ITIL Processes, ITIL Service Design > IT Service Continuity Management
IT Service Management
- The processes within IT Service Management ensure that IT Services are provided in a focused, client-friendly and cost-optimised manner.
- With their help, IT Services are clearly defined, success can be measured with regards to the service provision, and targeted improvement measures can be introduced where necessary.
- IT Service Management according to ITIL Version 3 (ITIL V3) encompasses the following core disciplines:
IT Steering Group (ISG)
- → Roles within ITIL, IT Steering Group (ISG)
J
K
Key Performance Indicator (KPI)
- A Metric that is used to help manage a process, service or activity.
- Many Metrics may be measured, but only the most important of these are defined as KPIs and used to actively manage and report on the process, service or activity.
- KPIs should be selected to ensure that efficiency, effectiveness, and cost effectiveness are all managed.
Knowledge Management
- → ITIL Processes, ITIL Service Transition > Knowledge Management
Knowledge Manager
- → Roles within ITIL, Knowledge Manager
Known Error
- A Known Error is a problem that has a documented root cause and (if possible) a Workaround.
- Known Errors are managed throughout their lifecycle by the Problem Management Process.
- The details of each Known Error are recorded in a Known Error Record stored in the Known Error Database (KEDB).
- As a rule, Known Errors are identified by Problem Management, but Known Errors may also be suggested by other Service Management disciplines, e.g. Incident Management, or by suppliers.
- → ITIL Processes, ITIL Service Operation > Problem Management
Known Error Database
- The Known Error Database (KEDB) is created by Problem Management and used by Incident and Problem Management to manage all Known Error Records.
- → ITIL Processes, ITIL Service Operation > Problem Management
KPI Target Value
- The to-be value of a Key Performance Indicator (KPI).
- It is the responsibility of the Process Owners to manage and optimize processes so that KPI targets are achieved.
- → ITIL Processes, ITIL Continual Service Improvement (CSI) > Process Evaluation
L
M
Maintenance Plan/ SOP
- A plan produced by Availability Management to define frequency and scope of preventative maintenance for service-critical applications and infrastructure components under control of Availability Management.
- Maintenance Plans are sometimes known as Standard Operating Procedures.
- → ITIL Processes, ITIL Service Design > Availability Management
Major Incident Review
- A Major Incident Review takes place after a Major Incident has occurred.
- The review documents the Incident's underlying causes (if known) and the complete resolution history, and identifies opportunities for improving the handling of future Major Incidents.
- → ITIL Processes, ITIL Service Operation > Incident Management
Major Incident Team
- → Roles within ITIL, Major Incident Team
Monitoring of CSI Initiatives
- → ITIL Processes, ITIL Continual Service Improvement (CSI) > Monitoring of CSI Initiatives
N
Notification of Service Failure
- The reporting of a service failure to the Service Desk, for example by a user via telephone or e-mail, or by a system monitoring tool.
- → ITIL Processes, ITIL Service Operation > Incident Management
O
OLA
Operational Level Agreement (OLA)
- An agreement between an IT service provider and another part of the same organization.
- An OLA supports the IT service provider's delivery of services to customers.
- The OLA defines the goods or services to be provided and the responsibilities of both parties.
- For example there could be an OLA - between the IT service provider and a procurement department to obtain hardware in agreed times - between the Service Desk and a support group to provide Incident resolution in agreed times.
- → ITIL Checklist SLA - OLA - UC
- → ITIL Processes, ITIL Service Design > Service Level Management
Outline of Service Requirements
- The desired outcome of a service, stated in terms of required service functionality (utility) and service levels (warranty).
- Based on this information, detailed service requirements are specified during the Service Design stage.
- → ITIL Processes, ITIL Service Design > Service Level Management
P
Post Implementation Review (PIR)
- The Post Implementation Review takes place after a Change has been implemented.
- It determines if the Change and its implementation Project were successful, and identifies opportunities for improvement.
- → ITIL Processes, ITIL Service Transition > Change Management
Pro-Active User Information
- A notification to users of existing or imminent service failures even if the users are not yet aware of the interruptions, so that users are in a position to prepare themselves for a period of service unavailability.
- → ITIL Processes, ITIL Service Operation > Incident Management
Problem
- A cause of one or more Incidents. The cause is not usually known at the time a Problem Record is created.
- → ITIL Processes, ITIL Service Operation > Problem Management
Problem Management
- → ITIL Processes, ITIL Service Operation > Problem Management
Problem Management Report
- A report supplying Problem-related information to the other Service Management processes.
- → ITIL Processes, ITIL Service Operation > Problem Management
Problem Manager
- → Roles within ITIL, Problem Manager
Problem Record
- The Problem Record contains all details of a Problem, documenting the history of the Problem from detection to resolution.
- → ITIL Checklist Problem Record
- → ITIL Processes, ITIL Service Operation > Problem Management
Process and Asset Valuation
- An estimate of the value a process or other asset represents for the business.
- This value is an important input for Risk Analysis.
- → ITIL Processes, ITIL Service Design > Risk Management
Process Architect
- → Roles within ITIL, Process Architect
Process Architecture
- An overview of all processes and process interfaces, used as a tool to make sure that all processes within an organization cooperate in a seamless way.
- The Process Architecture is part the Enterprise Architecture.
- → ITIL Processes, ITIL Continual Service Improvement (CSI) > Process Evaluation
Process Area
- Process Area is a CMMI® [2] term with the following (CMMI) definition: “A cluster of related practices in an area that, when implemented collectively, satisfy a set of goals considered important for making significant improvement in that area”.
- In the context of ITIL this would mean that the top level processes such as (for example) Incident Management would be a Process Area. The Logging and Categorization of an Incident would constitute a Process within that Process Area.
Process Assessment Guideline
- A guideline describing the four most-often used approaches to evaluate the underlying service management processes: Process Maturity Assessments, Benchmarks, Audits and Process Reviews.
- → ITIL Processes, ITIL Continual Service Improvement (CSI) > Process Evaluation
Process Design
- The description of a process including its in- and outputs, activities, and responsibilities.
- Process Designs are under the control of Process Management.
- → ITIL Processes, ITIL Continual Service Improvement (CSI) > Process Evaluation
Process Evaluation
- → ITIL Processes, ITIL Continual Service Improvement (CSI) > Process Evaluation
Process Evaluation Report
- The results from a Process Maturity Assessment, Benchmarking, Audit, or Process Review, including identified shortcomings and areas which must be addressed by improvement initiatives.
- → ITIL Processes, ITIL Continual Service Improvement (CSI) > Process Evaluation
Process Metric (KPI)
- Process Metrics (Key Performance Indicators – KPIs) define what is to be measured and reported to help manage a process.
- → ITIL Processes, ITIL Continual Service Improvement (CSI) > Process Evaluation
Process Owner
- → Roles within ITIL, Process Owner
Project Charter
- The Project Charter is a statement of the scope, objectives and participants in a project.
- It outlines the project objectives, identifies the main stakeholders, defines the authority of the project manager and the resources at his disposal, and lists any constraints and assumptions affecting the project.
- → ITIL Processes, ITIL Service Transition > Project Management - Transition Planning and Support
Projected Service Availability (PSA)
- A Document that identifies the effect of planned Changes on agreed Service Levels, based on the Forward Schedule of Change (FSC).
- → ITIL Processes, Change Management - ITIL V2
Projected Service Outage (PSO)
- The Projected Service Outage (PSO) document lists any expected deviations from the service availability agreed in SLAs.
- → ITIL Processes, ITIL Service Transition > Change Management
Project History Log
- A document recording important events during the course of the project, e.g. decisions, escalations and changes to the project scope.
- → ITIL Processes, ITIL Service Transition > Project Management - Transition Planning and Support
Project Management (Transition Planning and Support)
- → ITIL Processes, ITIL Service Transition > Project Management - Transition Planning and Support
Project Manager
- → Roles within ITIL, Project Manager
Project Plan (Service Transition Plan)
- A Project Plan (in ITIL also referred to as Service Transition Plan) is a formal, approved document showing the major deliverables, milestones, activities and resources for a Service Transition project, used to guide both project execution and project control.
- → ITIL Processes, ITIL Service Transition > Project Management - Transition Planning and Support
Project Portfolio Status Report
- The Project Portfolio Status Report is an overall summary of all planned or ongoing Service Transition projects for deploying major Releases, listing key project data like milestones and current project status.
- → ITIL Processes, ITIL Service Transition > Project Management - Transition Planning and Support
Purchase Order
- An order for purchasing items from a supplier.
- If the order is for an externally supplied Supporting Service it is accompanied by an Underpinning Contract defining service level targets.
- → ITIL Processes, ITIL Service Design > Supplier Management
Purchase Request
- A request to purchase a service or a product from an external supplier, issued for example from Release Management during Service Build.
- Processing of a Purchase Request will generally proceed only if the requester also holds an approved budget for the purchase.
- → ITIL Processes, ITIL Service Design > Supplier Management
Q
R
Recovery Plan
- Recovery Plans are created mainly by Availability and IT Service Continuity Management.
- The plans contain detailed instructions for returning specific services and/or systems to a working state, which often includes recovering data to a known consistent state.
- → ITIL Processes,
RFC Template
- A template to be used when formally requesting a Change.
- An RFC includes details of the proposed Change, and may be recorded on paper or electronically.
- → ITIL Processes, ITIL Service Transition > Change Management
Release
- A Release (also referred to as a “Release Package”) consists of a single Release Unit or a structured set of Release Units.
Release and Deployment Management
- → ITIL Processes, ITIL Service Transition > Release and Deployment Management
Release Management
- → ITIL Processes,
- ITIL V3: ITIL Service Transition > Release and Deployment Management
- ITIL V2: Release Management
Release Manager
- → Roles within ITIL, Release Manager
Release Package
- → Release
Release Plan
- A Document that embraces all Releases in line for rollout and their planned implementation dates.
- A Release is defined as a collection of hardware, software, documentation, processes or other components required to implement one or more approved Changes to IT Services. The contents of each Release are managed and tested as a unit, and deployed as a single entity.
- → ITIL Processes, Release Management - ITIL V2
Release Policy
- A set of rules for deploying releases into the live operational environment, defining different approaches for releases depending on their urgency and impact.
- → ITIL Processes, ITIL Service Transition > Release and Deployment Management
Release Record
- Release Record contains all details of a Release, documenting the history of the Release from the first planning stages to closure.
- → ITIL Processes, ITIL Service Transition > Release and Deployment Management
Release Unit
- A Release Unit is a set of new, changed and/or unchanged Configuration Items, which are tested and introduced into the live environment together to implement one or several approved Changes.
Request for Access Rights
- A request to grant, change or revoke the right to use a particular service or access certain assets.
Request for Change (RFC)
- A formal request for a Change to be implemented.
- An RFC includes details of the proposed Change, and may be recorded on paper or electronically.
- The term RFC is often misused to mean a Change Record, or the Change in itself.
- → ITIL Checklist Checklist Request for Change - RFC
- → ITIL Processes, ITIL Service Transition > Change Management
Request Fulfilment
- → ITIL Processes, ITIL Service Operation > Request Fulfilment
Required Modifications to Service Catalogue
- A request from a Service Management process to change the Service Catalogue.
- This request is sent to Service Catalogue Management if new services or service attributes must be recorded.
- → ITIL Processes, ITIL Service Design > Service Catalogue Management
Required Modifications to UCs
- A request from a Service Management process to change an Underpinning Contract.
- This request is most often sent from Service Level Management to Supplier Management if a new service requires a new or modified external Supporting Service.
RFC
RFC Assessment Guideline
- A guideline describing the aspects to be considered when assessing a proposed change.
- → ITIL Processes, ITIL Service Transition > Change Management
RFC Template
- A template to be used when formally requesting a Change. An RFC includes details of the proposed Change, and may be recorded on paper or electronically.
- → ITIL Processes, ITIL Service Transition > Change Management
Risk Management
- → ITIL Processes, ITIL Service Design > Risk Management
Risk Management Policy
- The Risk Management Policy describes and communicates the organization’s approach to managing risk.
- Most importantly, it defines how risk is quantified and who is in charge of specific risk management duties.
- The Risk Management Policy is maintained by the Risk Manager role, but to be effective it needs the backing of senior management.
- → ITIL Processes, ITIL Service Design > Risk Management
Risk Manager
- → Roles within ITIL, Risk Manager
Risk Register
- The Risk Register is a tool used by the Risk Management process to keep an overview of identified risks and corresponding counter measures.
- The Risk Register is sometimes referred to as the Risk Log.
- → ITIL Processes, ITIL Service Design > Risk Management
S
Security Advisories
- A list of known security vulnerabilities compiled from input by third-party product suppliers.
- The list contains instructions for preventive measures and for the handling of security breaches once they occur.
- → ITIL Processes, ITIL Service Design > Information Security Management
Security Alert
- A warning produced by Information Security Management, typically released when outbreaks of security threats are foreseeable or already under way.
- The aim is to make sure that users and IT staff are able to identify any attacks and take appropriate precautions.
- → ITIL Processes, ITIL Service Design > Information Security Management
Security Management Information System
- A virtual repository of all Information Security Management data, usually stored in multiple physical locations.
- → ITIL Processes, ITIL Service Design > Information Security Management
Service Acceptance Criteria (SAC)
- A set of criteria used to ensure that an IT service meets its functionality and quality requirements and that the service provider is ready to operate the new service when it has been deployed.
- → ITIL Processes, ITIL Service Design > Service Level Management
Service Architecture
- The Service Architecture for a specific Service identifies all the components of a Service and their structure, including all the corresponding designs for the Service and its components in the Service Design Package.
- However an important part of a Service Architecture is the organization-level standards and templates that are required for developing and maintaining a consistent and integrated set of Services for the organization. These standards and templates are usually embedded in an appropriate architecture management system.
Service Asset and Configuration Management
- → ITIL Processes, ITIL Service Transition > Service Asset and Configuration Management
Service Catalogue
- A database or structured document with information about all live services, including those available for deployment.
- The Service Catalogue is the only part of the Service Portfolio published to Customers, and is used to support the sale and delivery of IT Services.
- The Service Catalogue includes information about deliverables, prices, contact points, ordering and request processes.
- → ITIL Processes, ITIL Service Design > Service Catalogue Management
Service Catalogue Management
- → ITIL Processes, ITIL Service Design > Service Catalogue Management
Service Catalogue Manager
- → Roles within ITIL, Service Catalogue Manager
Service Delivery
- → ITIL Discipline, Service Delivery - ITIL V2
Service Design
- → ITIL Core Discipline, ITIL V3 Service Design
Service Design Manager
- → Roles within ITIL, Service Design Manager
Service Design Package (SDP)
- The Service Design Package builds upon the Service Level Requirements.
- It further specifies the requirements from the viewpoint of the client and defines how these are actually fulfilled from a technical and organizational point of view.
- The ITILv3 definition for the Service Design Package for an IT Service states: [The Service Design Package is one or more] “Service Design Documents defining all aspects of an IT Service and its Requirements through each stage of its Lifecycle. A Service Design Package is produced for each new IT Service, major Change, or IT Service Retirement”.
- → ITIL Checklist Service Design Package - SDP
- → ITIL Processes, ITIL Service Design > ITIL Design Coordination
Service Design Policy
- The Service Design Policy provides guidance on how to ensure that a consistent approach is applied to all design activity.
- In particular, the Service Design Policy specifies which projects or Changes are required to undergo the formal Service Design stage, and who needs to be involved in Service Design to ensure that all relevant aspects are considered.
- → ITIL Processes, ITIL Service Design > ITIL Design Coordination
Service Design Validation Report
- A report summarizing the results of the Service Design Validation testing activities, documenting that the Service Design Package correctly matches the Service Requirements.
- → ITIL Processes, ITIL Service Transition > Service Validation and Testing
Service Desk
- → ITIL Processes,
- ITIL V3: ITIL Service Operation > Incident Management
- ITIL V2: Service Desk and Incident Management - ITIL V2
Service Evaluation
- → ITIL Processes, ITIL Continual Service Improvement (CSI) > Service Evaluation
Service Improvement Plan (SIP)
- The Service Improvement Plan is a formal plan to implement improvements to services and IT processes. The SIP is used to manage and log improvement initiatives triggered by Continual Service Improvement.
- → ITIL Checklist Service Improvement Plan - SIP
- → ITIL Processes, ITIL Continual Service Improvement (CSI) > Definition of Improvement Initiatives
Service Improvement Program (SIP)
- A formal Plan to provide guidelines as to when and in which form improvements to a Process or IT Service are to be implemented.
- An SIP is maintained within the framework of a continuous optimisation process.
- → ITIL V3 - Service Improvement Plan
- → ITIL Processes, Service Level Management - ITIL V2
Service Knowledge Management System (SKMS)
- The Service Knowledge Management System is the central repository of the IT organization’s data, information and knowledge.
- It extends the concept of the infrastructure-focused Configuration Management System to include further information on services, capabilities, and initiatives.
- → ITIL Processes, ITIL Service Transition > Knowledge Management
Service Level Agreement (SLA)
- An agreement between an IT service provider and a customer.
- The SLA describes the IT service, documents service level targets, and specifies the responsibilities of the IT service provider and the customer.
- A single SLA may cover multiple services or multiple customers.
- → ITIL Checklist SLA - OLA - UC
- → ITIL Processes, ITIL Service Design > Service Level Management
Service Level Management
- → ITIL Processes, ITIL Service Design > Service Level Management
Service Level Manager
- → Roles within ITIL, Service Level Manager
Service Level Report
- The Service Level Report gives insight into a service provider's ability to deliver the agreed service quality.
- To this purpose, it compares the agreed and actually achieved service levels, and also includes information on the usage of services, ongoing measures for service improvement, and any exceptional events.
- A Service Level Report is issued by the service provider for its customers, IT management and other Service Management processes.
- A similar report is also created by an external service supplier to document its achieved service performance.
- → ITIL Processes, ITIL Service Design > Service Level Management
Service Level Requirements (SLR)
- The Service Level Requirements document contains the requirements for a service from the client viewpoint, defining detailed service level targets, mutual responsibilities, and other requirements specific to a certain (group of) customers.
- → ITIL Processes, ITIL Service Design > Service Level Management
Service Management System
- The standard, BS ISO/IEC 20000-1:2005 introduced the concept of a "Service Management System". This is usually a complex "system" of manual and automated processes that are used to manage a Service over its lifetime; in particular, its planning, development, implementation, operation and improvement.
- ITIL V3 provides a set of best practice guidelines for Service Management. It addresses those Process Areas that are required for a comprehensive Service Management System.
- It is difficult to introduce all the ITIL V3 Process Areas into a Service Management System in one project or program, especially in their mature form. As a result, those organization that have done this, focus on a subset of the ITIL V3 Process Areas to create an initial Service Management System, often using BS ISO/IEC 20000-1:2005 as the standard followed to do this. The initial Service Management System is then subsequently enhanced and improved in later Service Management programs and projects.
- What is important is that the initial Service Management System contains the minimum set of processes from ITIL V3 that enable an organization to manage a Service across its whole lifecycle.
- The Service Management (System) Architecture is a vital component of this to ensure the quality and consistency of the Service Management System, especially as it develops over time. Furthermore, an holistic view of the ITIL V3 architecture enables a Service Management or Business Architect to design an initial Service Management System that is consistent with the expected form of the future Service Management System.
Service Operation
- → ITIL Core Discipline, ITIL V3 Service Operation
Service Owner
- → Roles within ITIL, Service Owner
Service Portfolio
- The Service Portfolio represents a complete list of the services managed by a service provider; some of these services are visible to the customers, while others are not.
- It contains present contractual commitments, new service development, and ongoing service improvement plans initiated by Continual Service Improvement.
- It also includes third-party services which are an integral part of service offerings to customers.
- The Service Portfolio is divided into three phases: Service Pipeline, Service Catalogue, and Retired Services.
- → ITIL Checklist Service Portfolio
- → ITIL Processes, ITIL Service Strategy > Service Portfolio Management
Service Portfolio Management
- → ITIL Processes, ITIL Service Strategy > Service Portfolio Management
Service Portfolio Manager
- → Roles within ITIL, Service Portfolio Manager
Service Quality Plan (SQP)
- A document containing all management information on the measurement of Service Quality and the contributions made to the IT Services by internal and external Suppliers, upon the basis of KPIs.
Service Request
- Service Requests are formal requests from a user for something to be provided – for example, a request for information or advice; to reset a password; or to install a workstation for a new user.
- → ITIL Processes, ITIL Service Operation > Request Fulfilment
Service Request Fulfilment Group
- → Roles within ITIL, Service Request Fulfilment Group
Service Request Model
- A (Service) Request Model defines specific agreed steps that will be followed for a Service Request of a particular type (or category).
- → ITIL Processes, ITIL Service Operation > Request Fulfilment
Service Request Record
- A record containing all details of a Service Request. Service Requests are formal requests from a user for something to be provided – for example, a request for information or advice; to reset a password; or to install a workstation for a new user.
- → ITIL Processes, ITIL Service Operation > Request Fulfilment
Service Request Status Information
- A message containing the present status of a Service Request, usually sent to a user who earlier requested a service.
- → ITIL Processes, ITIL Service Operation > Request Fulfilment
Service Requirements
- The desired outcome of a service, stated in terms of required service functionality and service levels.
- → ITIL Processes, ITIL Service Design > Service Level Management
Service Review Report
- A document containing the results and findings from a Service Review.
- This report is an important input for the definition of improvement initiatives.
- → ITIL Checklist Service Review Report
- → ITIL Processes, ITIL Continual Service Improvement (CSI) > Service Evaluation
Service Specification Sheet
- The Service Specification Sheets lays out in detail how the customer requirements can be fulfilled from the viewpoint of the IT Organisation.
- In particular, it references the internal IT Service components used to build the new or changed Service required by the customer (i.e. the necessary services provided from within the IT Organisation or from external Service Suppliers).
- This document may also list further consequences related to the provision of the IT Service, such as required resources and skills.
- → ITIL Processes, Service Level Management - ITIL V2
Service Strategy
- A systematic long-term plan of action, designed by the IT Service Organization to achieve defined objectives.
- → ITIL Processes, ITIL Service Strategy > Service Portfolio Management
Service Strategy
- → ITIL Core Discipline, ITIL V3 Service Strategy
Service Support
- → ITIL Discipline, Service Support - ITIL V2
Service Transition
- → ITIL Core Discipline, ITIL V3 Service Transition
Service Transition Plan
Service User
- → Roles within ITIL, Service User
Service Validation and Testing
- → ITIL Processes, ITIL Service Transition > Service Validation and Testing
Seven-Step Improvement Guideline
- The Seven-Step Improvement Method is presented in the ITIL books as the Seven-step Improvement Process.
- Rather than a process it is in fact the description of a methodology which can be universally applied to identify shortcomings in services and processes and to implement improvements.
- → ITIL Processes, ITIL Continual Service Improvement (CSI) > Process Evaluation
SLA
SLM Document Templates
- Templates for the various documents used within Service Level Management, e.g. Service Level Requirements, Service Level Agreements, Operational Level Agreements, Underpinning Contracts, Service Acceptance Criteria, ...
- → ITIL Processes, ITIL Service Design > Service Level Management
Standard Terms and Conditions
- A set of terms and conditions which are routinely attached to contracts and orders when procuring services or products.
- → ITIL Processes, ITIL Service Design > Supplier Management
Status Inquiry
- An inquiry regarding the present status of an Incident or Service Request, usually from a user who earlier reported an Incident or submitted a request.
- → ITIL Processes, ITIL Service Operation > Incident Management
Strategic Plan
- A plan for implementing the Service Strategy, containing specific objectives, activities and responsibilities.
- → ITIL Processes, ITIL Service Strategy > Service Portfolio Management
Strategic Service Assessment
- The Strategic Service Assessment is used to gain insight into a service provider’s weaknesses and strengths prior to developing a Service Strategy.
- → ITIL Processes, ITIL Service Strategy > Service Portfolio Management
Suggested Changes to SLAs, OLAs and UCs
- Suggestions for improving service quality or economics, handed over from other Service Management processes to the Continual Service Improvement process.
- Suggestions to improve services may originate from anywhere within or outside of the IT organization.
- → ITIL Processes, ITIL Continual Service Improvement (CSI) > Service Evaluation
Suggested new Known Error
- A suggestion to create a new entry in the Known Error Database, for example raised by the Service Desk or by Release Management.
- Known Errors are managed throughout their lifecycle by Problem Management.
- → ITIL Processes, ITIL Service Operation > Problem Management
Suggested new Problem
- A notification about a suspected Problem, handed over to Problem Management for further investigation, possibly leading to the formal logging of a Problem.
- → ITIL Processes, ITIL Service Operation > Problem Management
Suggested new Workaround
- A suggestion to enter a new Workaround in the Known Error Database, for example raised by the Service Desk or by Release Management. Workarounds are managed throughout their lifecycle by Problem Management.
- → ITIL Processes, ITIL Service Operation > Problem Management
Suggested Process Improvement
- Suggestions for improving Service Management processes, handed over to the Continual Service Improvement process.
- Suggestions for process improvements may originate from anywhere within the IT organization.
- → ITIL Processes, ITIL Continual Service Improvement (CSI) > Process Evaluation
Suggestions and Complaints
- Suggestions and complaints from the customer side which are addressed in the Continual Service Improvement process.
- → ITIL Processes, ITIL Continual Service Improvement (CSI) > Service Evaluation
Supplier and Contract Database (SCD)
- A database or structured document used to manage supplier contracts throughout their lifecycle.
- The SCD contains key attributes of all contracts and suppliers, and should be part of the Service Knowledge Management System.
- → ITIL Processes, ITIL Service Design > Supplier Management
Supplier and Contract Review
- The Supplier and Contract Review documents achieved vs. agreed supplier performance.
- It also contains any identified supplier weaknesses and problems, as well as suggestions on how the situation could be improved.
- → ITIL Processes, ITIL Service Design > Supplier Management
Supplier Evaluation
- The resulting document from the Supplier Evaluation process, describing in detail the criteria used for evaluating and selecting a suitable supplier.
- → ITIL Processes, ITIL Service Design > Supplier Management
Supplier Management
- → ITIL Processes, ITIL Service Design > Supplier Management
Supplier Manager
- → Roles within ITIL, Supplier Manager
Supplier Service Level Report
- The Supplier Service Level Report gives insight into a service provider's external supplier's ability to deliver the agreed service quality.
- To this purpose, it compares the agreed and actually achieved service levels, and also includes information on the usage of services, ongoing measures for service improvement, and any exceptional events.
- → ITIL Processes, ITIL Service Design > Supplier Management
Supplier Strategy
- The Supplier Strategy sets guidelines for the procurement of services and goods.
- It typically includes criteria for the selection of suitable suppliers and a list of preferred suppliers.
- → ITIL Processes, ITIL Service Design > Supplier Management
Support Knowledge Base
- A Database containing information about Incidents, Problems and Known Errors.
- The Knowledge Base is used to match new Incidents with historical information, with the objective of improving resolution times and First Time Fix Rates.
- → ITIL Processes, Service Desk and Incident Management - ITIL V2
Support Request
- A request to support the resolution of an Incident or Problem, usually issued from the Incident or Problem Management processes when further assistance is needed from technical experts.
- → ITIL Processes, ITIL Service Operation > Incident Management
T
Technical/ Administration Manual
- A document describing the procedures required to run and maintain an application or infrastructure component.
- → ITIL Processes, ITIL Service Transition > Application Development
Technical Analyst
- → Roles within ITIL, Technical Analyst
Technical Management
- → ITIL Processes, ITIL Service Operation > Technical Management
Test and QS Manager
- → Roles within ITIL, Test and QS Manager
Test Manager
- → Roles within ITIL, Test Manager
Test Model
- A Test Model is created during the Release planning phase to specify in detail the testing approach used for deploying a Release into the productive environment. It is an important input for the Project Plan.
- Most importantly, this document defines the required quality assurance checkpoints during the Release deployment, as well as the required test scripts.
- → ITIL Processes, ITIL Service Transition > Service Validation and Testing
Transition Planning and Support
- → ITIL Processes, ITIL Service Transition > Project Management - Transition Planning and Support
Test Report
- A report of the preparation, progress and evaluation of a test, created for example during the various tests carried out by Availability, IT Service Continuity or Information Security Management.
- → ITIL Processes,
U
UC
Underpinning Contract (UC)
- A contract between an IT service provider and a third party.
- The third party provides services that support the delivery of a service to a customer.
- The Underpinning Contract defines targets and responsibilities that are required to meet agreed Service Level targets in an SLA.
- → ITIL Checklist SLA - OLA - UC
- → ITIL Processes, ITIL Service Design > Supplier Management
Underpinning Information Security Policy
- Underpinning Information Security Policies are specific policies complementing the main Information Security Policy by setting binding rules for the use of systems and information as well as for the use and delivery of services, with the aim of improving information security.
- → ITIL Processes, ITIL Service Design > Information Security Management
User
- → Roles within ITIL, Service User
User Escalation
- Escalation regarding the processing of an Incident or Service Request, initiated by a user experiencing delays or a failure to restore their services.
- → ITIL Processes, ITIL Service Operation > Incident Management
User FAQs
- Self-help information for users supplied by the Service Desk, usually as part of the Support Pages on the intranet.
- → ITIL Processes, ITIL Service Operation > Incident Management
User Identity Record
- A set of data with all the details identifying a user or person.
- It is used to grant rights to that user or person.
- → ITIL Processes, ITIL Service Operation > Access Management
User Identity Request
- A request to create, modify or delete a User Identity.
- → ITIL Processes, ITIL Service Operation > Access Management
User Manual
- A document for end-users, describing how to use an application or system.
- → ITIL Processes, ITIL Service Transition > Application Development
User Role
- A role as part of a catalogue or hierarchy of all the roles (types of users) in the organization.
- Access rights are based on the roles that individual users have as part of an organization.
- → ITIL Processes, ITIL Service Operation > Access Management
User Role Access Profile
- A set of data defining the level of access to a service or group of services for a certain type of user ("User Role").
- User Role Access Profiles help to protect the confidentiality, integrity and availability of assets by defining what information computer users can utilize, the programs that they can run, and the modifications that they can make.
- → ITIL Processes, ITIL Service Operation > Access Management
User Role Requirements
- Requirements from the business side for the catalogue or hierarchy of user roles (types of users) in the organization.
- Access rights are based on the roles that individual users have as part of an organization.
- → ITIL Processes, ITIL Service Operation > Access Management
V
Validation Test Report
- A Validation Test Report summarizes the results of testing and assessment activities, documenting that the assessed Release components successfully passed a validation stage.
- → ITIL Processes, ITIL Service Transition > Service Validation and Testing
W
Workaround
- Workarounds are temporary solutions aimed at reducing or eliminating the impact of Known Errors (and thus Problems) for which a full resolution is not yet available.
- As such, Workarounds are often applied to reduce the impact of Incidents or Problems if their underlying causes cannot be readily identified or removed. Workarounds are typically either documented as part of Known Error Records or in records of their own, linked to Known Error and Problem Records.
- → ITIL Processes, ITIL Service Operation > Problem Management
X
Y
Z
Notes
[1] ITIL® is a Registered Trade Mark of the Office of Government Commerce in the United Kingdom and other countries. — IT Infrastructure Library® is a Registered Trade Mark of the Office of Government Commerce in the United Kingdom and other countries.
[2] CMMI® (Capability Maturity Model Integrated) is a registered trade mark of the Software Engineering Institute, Carnegie Mellon University.