ITIL v3 Definitions
There are 541 entries in this glossary.All
| Term | Definition |
|---|---|
| Acceptance (v3) |
Formal agreement that an IT Service, Process, Plan, or other Deliverable is complete, accurate, Reliable and meets its specified Requirements. Acceptance is usually preceded by Evaluation or Testing and is often required before proceeding to the next stage of a Project or Process. See Service Acceptance Criteria. |
| Access Management (v3) |
(Service Operation) The Process responsible for allowing Users to make use of IT Services, data, or other Assets. Access Management helps to protect the Confidentiality, Integrity and Availability of Assets by ensuring that only authorized Users are able to access or modify the Assets. Access Management is sometimes referred to as Rights Management or Identity Management. |
| Account Manager (v3) |
(Service Strategy) A Role that is very similar to Business Relationship Manager, but includes more commercial aspects. Most commonly used when dealing with External Customers. |
| Accounting (v3) |
(Service Strategy) The Process responsible for identifying actual Costs of delivering IT Services, comparing these with budgeted costs, and managing variance from the Budget. |
| Accredited (v3) |
Officially authorised to carry out a Role. For example an Accredited body may be authorised to provide training or to conduct Audits. |
| Active Monitoring (v3) |
(Service Operation) Monitoring of a Configuration Item or an IT Service that uses automated regular checks to discover the current status. See Passive Monitoring. |
| Activity (v3) |
A set of actions designed to achieve a particular result. Activities are usually defined as part of Processes or Plans, and are documented in Procedures. |
| Agreed Service Time (v3) |
(Service Design) A synonym for Service Hours, commonly used in formal calculations of Availability. See Downtime. |
| Agreement (v3) |
A Document that describes a formal understanding between two or more parties. An Agreement is not legally binding, unless it forms part of a Contract.See Service Level Agreement, Operational Level Agreement. |
| Alert (v3) |
(Service Operation) A warning that a threshold has been reached, something has changed, or a Failure has occurred. Alerts are often created and managed by System Management tools and are managed by the Event Management Process. |
| Analytical Modelling (v3) |
(Service Strategy) (Service Design) (Continual Service Improvement) A technique that uses mathematical Models to predict the behaviour of a Configuration Item or IT Service. Analytical Models are commonly used in Capacity Management and Availability Management.See Modelling. |
| Application (v3) |
Software that provides Functions that are required by an IT Service. Each Application may be part of more than one IT Service. An Application runs on one or more Servers or Clients.See Application Management, Application Portfolio. |
| Application Management (v3) |
(Service Design) (Service Operation) The Function responsible for managing Applications throughout their Lifecycle. |
| Application Portfolio (v3) |
(Service Design) A database or structured Document used to manage Applications throughout their Lifecycle. The Application Portfolio contains key Attributes of all Applications. The Application Portfolio is sometimes implemented as part of the Service Portfolio, or as part of the Configuration Management System. |
| Application Service Provider (ASP) (v3) |
(Service Design) An External Service Provider that provides IT Services using Applications running at the Service Provider's premises. Users access the Applications by network connections to the Service Provider. |
