ITIL Glossary

From IT Process Wiki

Jump to: navigation, search
diese Seite auf Deutschesta página en español
ITIL Glossary - ITIL V3 Glossary



The ITIL Glossary provides you with definitions for the most important ITIL V3 and V2 Glossary Terms in alphabetical order.

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


[edit] 1-9

[edit] 1st Level Support

[edit] 2nd Level Support

[edit] 3rd Level Support

[edit] A

[edit] Access Management

[edit] 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

[edit] Application Development and Customization

[edit] Application Developer

[edit] Application Manager

[edit] Applications Analyst/ Architect

[edit] 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

[edit] Availability Guidelines for the Service Desk

[edit] 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

[edit] Availability/ ITSCM/ Security Testing Schedule

[edit] Availability Management

[edit] Availability Management Information System

[edit] Availability Manager

[edit] Availability Plan

[edit] 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

[edit] B

[edit] 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.

[edit] Budget Allocation

[edit] Business Planning Data

[edit] Budget Request

[edit] Business Continuity Strategy

[edit] 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

[edit] Business Strategy

[edit] C

[edit] Capacity Management

[edit] Capacity Management Information System

[edit] Capacity Manager

[edit] 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

[edit] Capacity Report

[edit] Change Advisory Board (CAB)

[edit] Change Authorization Hierarchy

[edit] Change Management

[edit] Change Manager

[edit] Change Model

[edit] Change Owner

[edit] Change Record

The Change Record contains all the details of a Change, documenting the lifecycle of a single Change, where a Change is defined as the addition, changing or removal of any object with an influence upon the IT services.

[edit] Change Request to CMS Structure

[edit] Change Request to IT Architecture

[edit] Change Request to Process Architecture

[edit] Change Schedule

[edit] CI Status Monitoring Report

[edit] Client (Contract Partner)

[edit] CMS/ CMDB

[edit] CMS Change Policy

[edit] Complaints Log

[edit] Compliance Management

[edit] Compliance Manager

[edit] Compliance Register

[edit] 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

[edit] 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

[edit] Configuration Audit Protocol

[edit] Configuration Management

[edit] Configuration Manager

[edit] Continual Service Improvement (CSI)

[edit] Cost Data for Service Provisioning

[edit] CSI

[edit] CSI Metric (KPI)

[edit] CSI Monitoring

[edit] Customer

[edit] Customer Survey Evaluation

[edit] Customer Survey Response

[edit] D

[edit] Data for Project Plan Update

[edit] Definition of Improvement Initiatives

[edit] Definitive Media Library (DML)

[edit] 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

[edit] 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

[edit] Development Work Order

[edit] Disaster Invocation Guideline

[edit] E

[edit] Emergency Change Advisory Board (ECAB)

[edit] Emergency Committee (EC)

[edit] End-User Documentation

[edit] Enterprise Policies and Regulations

[edit] Event Categories and Correlation Rules

  • Rules and criteria used to decide upon an appropriate response to an Event.
  • Categorization and Correlation Rules are typically used by Event Monitoring systems.
  • → ITIL Processes, ITIL Service Operation > Event Management

[edit] Event Management

[edit] Event Record

  • 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

[edit] 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

[edit] F

[edit] Financial Analysis

[edit] 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

[edit] Financial Management

[edit] Financial Management for IT Services

[edit] Financial Manager

[edit] Forward Schedule of Changes (FSC)

[edit] G

[edit] H

[edit] I

[edit] Improvement Initiatives

[edit] Incident

[edit] 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

[edit] Incident Management

[edit] 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

[edit] Incident Manager

[edit] 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

[edit] 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

[edit] Incident Status Information

[edit] Incident Status Inquiry

[edit] Index of Disaster-Relevant Information

[edit] 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

[edit] Installation Work Order

[edit] Invoice

[edit] IT Architecture

  • A request to change or extend the IT 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 > IT Architecture Management

[edit] IT Architecture Management

[edit] IT Architect

[edit] IT Budget

[edit] ITC Infrastructure Manager

[edit] IT Facilities Management

[edit] IT Facilities Manager

[edit] IT Operations Management

[edit] IT Operations Manager

[edit] IT Operator

[edit] IT Security Management

[edit] IT Security Manager

[edit] IT Security Policy

[edit] IT Security Report

[edit] IT Security Strategy

  • The IT Security Strategy contains an outline of the approach to ensure the security of IT services and systems.
  • It includes a list of security-related risks and existing or planned Security Controls to address those risks.
  • → ITIL Processes, ITIL Service Design > IT Security Management

[edit] IT Service Continuity Management

[edit] IT Service Continuity Manager

[edit] 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

[edit] 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

[edit] IT Service Continuity Strategy

  • The IT Service Continuity Strategy contains an outline of the approach to ensure the continuity of 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.
  • → ITIL Processes, ITIL Service Design > IT Service Continuity Management

[edit] IT Service Management

[edit] IT Steering Group (ISG)

[edit] J

[edit] K

[edit] 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.

[edit] Knowledge Management

[edit] Knowledge Manager

[edit] Known Error

[edit] KPI Target Value

[edit] L

[edit] M

[edit] Maintenance Plan/ SOP

[edit] Major Incident Team

[edit] N

[edit] Notification of Service Failure

[edit] O

[edit] Operational Documentation

[edit] 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

[edit] P

[edit] 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

[edit] 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

[edit] Problem

[edit] Problem Management

[edit] Problem Management Report

[edit] Problem Manager

[edit] Problem Record

[edit] Process and Asset Valuation

[edit] Process Architecture

[edit] Process Design

[edit] Process Evaluation

[edit] Process Evaluation Report

[edit] Project Charter

[edit] Projected Service Availability (PSA)

[edit] Projected Service Outage (PSO)

[edit] Project History Log

[edit] Project Management (Transition Planning and Support)

[edit] Project Manager

[edit] Project Plan

[edit] Purchase Order

[edit] 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

[edit] Q

[edit] R

[edit] Recovery Plan

[edit] 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

[edit] Release and Deployment Management

[edit] Release Management

[edit] Release Manager

[edit] 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

[edit] Release Policy

[edit] Release Record

[edit] Request for Access Rights

  • A request to grant, change or revoke the right to use a particular service or access certain assets.

[edit] Request for Change (RFC)

[edit] Request Fulfilment

[edit] Required Modifications to Service Catalogue

[edit] Required Modifications to UCs

[edit] Risk Management

[edit] Risk Manager

[edit] 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

[edit] S

[edit] 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 > IT Security Management

[edit] Security Alert

  • A warning produced by IT 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 > IT Security Management

[edit] Security Management Information System

[edit] 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

[edit] Service Asset and Configuration Management

[edit] 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

[edit] Service Catalogue Management

[edit] Service Catalogue Manager

[edit] Service Delivery

[edit] Service Design

[edit] Service Design Manager

[edit] Service Design Package (SDP)

[edit] Service Design Validation Report

[edit] Service Desk

[edit] Service Evaluation

[edit] Service Evaluation Report

[edit] Service Improvement Plan (SIP)

[edit] 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

[edit] Service Knowledge Management System (SKMS)

[edit] 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

[edit] Service Level Management

[edit] Service Level Manager

[edit] 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

[edit] 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

[edit] Service Operation

[edit] Service Owner

[edit] 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

[edit] Service Portfolio Management

[edit] Service Portfolio Manager

[edit] 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.

[edit] Service Request

  • A request from a user for information, or advice, or for a standard change or for access to an IT service.
  • For example to reset a password, or to provide standard IT services for a new user.
  • Service Requests are usually handled by a service desk or a request fulfilment group, and do not require an RFC to be submitted.
  • → ITIL Processes, ITIL Service Operation > Request Fulfilment

[edit] Service Request Fulfilment Group

[edit] Service Request Status Information

[edit] Service Requirements

[edit] 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

[edit] Service Strategy

[edit] Service Strategy

[edit] Service Strategy Plan

[edit] Service Support

[edit] Service Transition

[edit] Service Transition Report

[edit] Service Validation and Testing

[edit] SLA/ OLA/ UC Catalogue and Structure

[edit] SLM Document Templates

[edit] Standard Terms and Conditions

[edit] Strategic Service Assessment

[edit] 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

[edit] Suggested Known Error

[edit] Suggested Problem

[edit] 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

[edit] Suggested Workaround

[edit] Suggestions and Complaints

[edit] Suggestion to Influence Service Demand

[edit] Supplier and Contract Database (SCD)

[edit] 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

[edit] 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

[edit] Supplier Management

[edit] Supplier Manager

[edit] 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

[edit] 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

[edit] Support Request

[edit] Survey Questionnaire

[edit] T

[edit] Technical Analyst/ Architect

[edit] Test and QS Manager

[edit] Testing Script

  • A detailed set of instructions for testing certain aspects of an application or infrastructure item.
  • The Testing Script essentially defines the activities to be carried out and the expected outcomes.
  • → ITIL Processes, ITIL Service Transition > Service Validation and Testing

[edit] Test Manager

[edit] 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.
  • → ITIL Processes, ITIL Service Transition > Service Validation and Testing

[edit] Test Protocol

[edit] Test Report

[edit] Transition Planning and Support

[edit] U

[edit] 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

[edit] User

  • → Roles within ITIL, User

[edit] User Escalation

[edit] User FAQs

[edit] User Identity Record

[edit] User Identity Request

[edit] 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

[edit] 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

[edit] 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

[edit] V

[edit] W

[edit] Workaround

  • Reducing or eliminating the impact of an Incident or Problem for which a full resolution is not yet available, for example by restarting a failed Configuration Item.
  • Workarounds for Problems are documented in Known Error records.
  • → ITIL Processes, ITIL Service Operation > Problem Management

[edit] X

[edit] Y

[edit] Z

Personal tools
ITIL Process Map V3
Demo ITIL Process Map V3
Product Demo:
A complete set of
ITIL Process Templates
in Visio, ARIS, iGrafx
Flowcharter and QMAP