| Term |
Meaning |
| Ability |
The power or aptitude to perform physical or mental activities related to a profession or trade. |
| Action Plan |
See Mitigation Plan. |
| Active monitoring |
The pro-active polling of individual configuration items (CIs).
For example, pinging a CI on a network in order to determine the state of that CI. |
| Asset management |
The acquisition, operation, care and disposal of organisational assets, particularly critical infrastructure. |
| Assign |
To transfer an item (or in ITIL terminology to escalate an item functionally). |
| Attitude |
A set of emotions, beliefs and behaviours towards a particular object, person, thing or event. |
| Authentication |
Confirming someone is who they claim to be. |
| Availability |
The ability of a service or other configuration item to perform its agreed function when required. |
| Availability |
The percentage of service hours during which the functionality of a service was accessible to its customers over a period of time.
Also, in ISO/IEC 20000 terms, the ability of a component or service to perform its required function at a stated instant or over a period of time. |
| Availability Plan |
A documented plan detailing actual and agreed levels of availability, and planned availability improvement and review activities. |
| Baseline |
A configuration baseline is the configuration of a product or system established at a specific point in time, which captures both the structure and details of a configuration. It serves as reference for further activities. An application or software baseline provides the ability to change or to rebuild a specific version at a later date.
Also, in ISO/IEC 20000 terms, a snapshot of a service or individual configuration items at a point in time. |
| Business analyst (BA) |
The role primarily responsible for performing business analysis. |
| Business Case |
A document providing justification for committing substantial financial resources, such as supporting a proposal to deliver a new service. It will include data such as a cost benefit analysis, delivery options, risks and issues, etc. |
| Business Consequence |
The impact on the business due to the operational consequences of the risk occurring. |
| Business impact analysis (BIA) |
A mechanism for identifying vital business functions (VBFs) and their dependencies (such as suppliers, people, business processes, etc.).
A BIA also defines the recovery requirements for services, including RTOs, RPOs and the minimum service levels to be attained (during disaster scenarios). |
| Business Impact Analysis (BIA) |
The gathering and assessment of information regarding the potential impacts on the business due to particular scenarios. |
| Capacity Management Information System (CMIS) |
The Capacity Management Information System (CMIS) is a repository (or multiple repositories), that contains a collation of previous, present and future capacity-related information.
This information could include current capacity and performance data and reports, forecasts of future capacity, and current and previous capacity plans. |
| Change |
The addition, modification or removal of anything that could have a direct or indirect effect on services. |
| Change (or change record) |
A change is any modification to or deletion of an existing item or creation of a new item under the control of Service Asset and Configuration Management. It is handled by the Change Management process; click here to see more details about the scope and aim of this process. |
| Change Advisory Board (CAB) |
The group of people who review requests for change. This can be a meeting which is held on a regular basis but a virtual CAB is also possible.
A virtual CAB can be used typically for small, low impact standard changes where the notification and voting can be done via email. |
| Change authority |
The person or group that authorises a change. |
| Change schedule |
Used for planning changes, avoiding scheduling conflicts, assigning resources, communicating to stakeholders when changes will take place. |
| Cloud computing |
An operating model for providing on-demand network access to a shared pool of configurable resources that can be swiftly provided with minimal management effort or service provider interaction. |
| Competencies |
Observable and memorable knowledge, skills, abilities and attitudes that when combined contribute to higher levels of employee performance. |
| Competencies |
The abilities of an individual to perform the given activities to which they have been assigned. |
| Compliant |
A process or an activity that is performed to the standard as dictated by ISO/IEC 20000. |
| Condition |
The event that could potentially occur so as to trigger the consequences of the risk. |
| Configuration item (CI) |
Any component that needs to be managed in order to deliver an IT service. |
| Configuration Item (CI) |
A configuration item is any item held in the CMDB and typically includes components of the IT infrastructure (hardware and software) together with other related items such as documentation. Click here for more details about CI’s.
Also, in ISO/IEC 20000 terms, a component of an infrastructure or an item which is, or will be, under the control of Configuration Management. |
| Configuration management system (CMS) |
A set of tools, data and information that is used to support service configuration management. |
| Configuration Management System (CMS) / Configuration Management Database (CMDB) |
Configuration Management System: a set of tools and databases that are used to manage configuration data. A database, such as the CMDB contains records of CI’s and their inter-relationships. Typically the level of CI’s in the CMDB is set at the lowest level of independent change.
Also in ISO/IEC 20000 terms, a database containing all of the relevant details of each configuration item and details of the important relationships between them. |
| Consequences |
The potential affects of the risk should it occur.
These are normally considered in terms of operational consequences and business consequences. |
| Contingency Plan |
A pre-determined and agreed plan that will be invoked should a particular situation arise.
The plan should allow the situation to be contained and recovered from, in a controlled manner, minimising the impacts where possible. |
| Continual Service Improvement Programme (CSIP) |
An ongoing project to monitor, review and improve the effectiveness of services and the processes in use. |
| Controls |
A mechanism, such as a tool or procedure, which is put in place to help mitigate a security risk. |
| Corporate Governance |
The ongoing activity of monitoring on a sound system of internal control to safeguard investment and the organisation’s assets. |
| Critical success factor (CSF) |
A necessary precondition for the achievement of intended results. |
| Customer |
A person or organisation which receives a service. |
| Customer experience (CX) |
Design activities focused on time, quality, cost, reliability and effectiveness. |
| Design thinking |
A practical, human-centred and highly integrative approach based on the key activities of: inspiration and empathy, ideation, prototyping, implementation and evaluation. |
| Disaster recovery plans |
Clearly defined plans that set out how an organisation will recover from a disaster, including returning the affected services to a pre-disaster condition. |
| Document |
A physical paper or electronic item such as a policy, a service level agreement or a set of operating procedures, etc. |
| Emergency Change |
A change that follows the emergency change procedure (which allows for a fast track). |
| Emergency Change Advisory Board (ECAB) |
The group of people who have responsibility for authorising (or rejecting) an emergency change |
| Enterprise Risk Management |
The Corporate Risk Management function, responsible for reporting the status of generic risks and providing assurance to the Board. |
| Escalation |
The process of alerting various levels of management to the possibility of SLA breaches; typically using email and automatic business logic within a service management tool. |
| Event |
Any change of state that has significance for the management of a service or other configuration item. |
| Evidence |
The proof that an activity is being performed as per the agreed process and procedures. |
| Exception |
An abnormal event, usually involving the near or actual breaching of an SLA target. |
| Forward schedule of change (FSC) |
See change schedule. |
| Functional escalation |
Escalation to a support team (either internal or external). |
| Functional Escalation |
The official ITIL term for assignment: see Assign above. |
| Generic Risks |
High level risk categories such as “hardware failure” and “lack of key skills”. |
| Hierarchical escalation |
Escalation to management (including senior management). |
| Hierarchical Escalation |
The official ITIL term for escalation. |
| Impact |
An indication of the amount of disruption to a service. This rises as more users become affected or the available functionality of the service becomes less. |
| Incident |
An unplanned interruption to a service or a reduction in the quality of a service. |
| Incident |
Any event which is not part of the standard operation of a service and which causes, or may cause, an interruption to, or reduction in, the quality of that service. |
| Information Security Policy (ISP) |
This document should be the driving force behind all of the information security activities, and should be supported where necessary by a sub-set of supporting policies. The ISP should have the support of senior management from both the business and IT, and should include the following (amongst others):
- Use and misuse of IT assets policy
- Policies on access and password controls
- Policies on email, the internet and viruses
- Remote access policy
- Etc.
All policies must be widely available to all of those people that are affected by them, including customers, users and third parties. Where relevant, the requirements to adhere to the appropriate policies should be included in agreements such as SLAs and third-party contracts. Once developed and signed-off by management, they will need to be reviewed and revised when necessary – normally on an annual basis as a minimum. |
| Infrastructure as a code |
Configuration information utilised in the creation of configuration items. |
| IT asset |
Any valuable component that can contribute to the delivery of an IT product or service. |
| IT asset management (ITAM) |
A sub-practice of asset management, with a focus of managing the lifecycles and total cost of IT equipment and infrastructure. |
| IT infrastructure |
Physical and/or virtual technology resources that provide the necessary environments needed to deliver IT services; e.g. servers, storage, networks, client hardware, middleware, operating systems, etc.
Also includes any configuration item (CI) used by a customer to access a service or consume a product. |
| IT Forensics |
The highly specialised task of capturing and preserving evidence of a security breach, for purposes of future disciplinary action or prosecution. |
| IT Service |
See service. |
| Key performance indicator (KPI) |
An important metric used to evaluate the success in meeting an objective. |
| Key Performance Indicator (KPI) |
A regular metric/report which shows how well each process is working in your organisation. |
| Knowledge |
A person’s understanding of facts or information that is obtained through experience or education; the theoretical or practical understanding of a subject. |
| Known error |
A problem that has been analysed but has not yet been resolved. |
| Known Error |
An incident or problem for which the root cause is known and for which a temporary workaround or a permanent alternative has been identified. |
| Lean user experience (Lean UX) |
Design activities with a focus on Lean-Agile methods. |
| Managed objects |
e.g. products and services, practices and value chain activities, teams and individuals, suppliers and partners, etc. |
| Mandatory |
An activity or process that must be performed in order to satisfy the requirements of the ISO/IEC 20000 standard. |
| Mean time between failures (MTBF) |
How frequently a service fails. |
| Mean time to restore service (MTRS) |
How quickly a service is restored after a failure. |
| Mitigation Actions |
Actions taken to alleviate a risk often by reducing either the likelihood of occurrence or the potential impacts. |
| Mitigation Plan |
A plan documenting actions that will be taken to alleviate a particular risk. The actions may include the development of a contingency plan and the monitoring of identified triggers. |
| Non-compliance |
A process or an activity that is not being performed to the standard as dictated by ISO/IEC 20000. |
| Non-repudiation |
Ensuring that someone cannot deny that they performed an action. |
| Operational Consequence |
The impact on normal operations if a risk occurs, for example, one or more IT services being unavailable. |
| Operational Level Agreement (OLA) |
A documented internal agreement covering the delivery of services that support IT teams in their delivery of services. |
| Operational Risk |
Risks that are primarily related to the day-to-day operation of business processes. |
| Organisational velocity |
The speed, effectiveness and efficiency with which an organisation operates.
It influences time to market, quality, safety, costs and risks. |
| Passive monitoring |
Where monitoring tools identify alerts that have been automatically generated by individual configuration items. |
| Patch |
An amendment to existing software or firmware to correct a deficiency or to add functionality. |
| Performance |
A measure of what is achieved or delivered by a system, person, team, practice, process or service. |
| Performance |
An indication of how well/fast a service handles its transactions.
The ideal measure of performance is the time from the moment a customer starts a transaction until the response that the action has been completed is received. |
| Post-implementation review (PIR) |
This happens once a release has been fully implemented and takes a look at the entire lifecycle of the release, including whether it has delivered the intended requirements.
It is an opportunity to learn from mistakes, highlight opportunities for improvement, and assess customer satisfaction. |
| Practice |
A practice is a set of organisational resources designed for performing work or accomplishing an objective.
These resources are grouped into the four dimensions of service management: organisations and people; information and technology; partners and suppliers; value streams and processes. |
| Priority |
An indication of how quickly the item is to be dealt with. |
| Problem |
A cause, or potential cause, of one or more incidents. |
| Problem |
The unknown underlying cause of one or more related incidents. |
| Process |
A set of inter-related or interfacing activities that transform inputs into outputs.
A process defines a sequence of actions (i.e. the activities) and their dependencies (e.g. with other processes). |
| PSA |
Projected Service Availability. |
| Record |
A document (physical or electronic) stating the results achieved or providing evidence of activities performed. |
| Recovery point objective (RPO) |
The point in time to which information used by an activity must be restored to enable the activity to operate on service resumption. |
| Recovery time objective (RTO) |
The maximum permissible time period following a service disruption that can lapse before the lack of business functionality severely impacts the organisation. |
| Release |
A version of a configuration item (e.g. a service), or a collection of configuration items, that is made available for use. |
| Release |
A collection of new or amended configuration items that have been packaged together and are tested and implemented together.
Also, in ISO/IEC 20000 terms, a collection of new and/or changed configuration items which are tested and introduced into the live environment together. |
| Release plan |
Specifies the blend of new or changed components that form the release, and the timing for their release into the live environment. |
| Release schedule |
Specifies the timing for all releases and is usually negotiated with interested parties (e.g. customers, key stakeholders, etc.). |
| Request catalogue |
A view of the service catalogue that focuses on providing customers with a set of service requests that are available (relevant to the services and products being provided). |
| Residual Risk |
The degree of risk remaining after mitigation actions have occurred. |
| Request for Change (RFC) |
A request for a change to be made (see Change above).
A form or screen is used to record details of a request for a change to any configuration item within the service or infrastructure. |
| Risk |
Uncertainty of outcome. The possibility of an event occurring and its potential consequences.
Can be either an opportunity (positive) or a threat (negative). |
| Risk Appetite |
The amount of risk that the Organisation or Risk Owner is prepared to tolerate at a specific point in time. |
| Risk Exposure |
The degree of vulnerability to a particular risk, taking into account the likelihood of the risk occurring, the potential impacts if the risk does occur and the controls in place to mitigate the risk. |
| Risk Owner |
The individual who has been given responsibility for a particular risk. |
| Risk Record |
The documented description of a particular risk, including condition, consequences, categorisation, risk analysis findings, past occurrences and current status. |
| Risk Register |
A repository containing information on identified risks and is used to record and track risks. |
| Risk Treatment |
The application of mitigation actions in order to alleviate a risk. |
| Screening |
The vetting of new joiners and contractors in accordance with security guidelines. |
| Security Classification |
The grading of information assets based on the potential impacts from their loss, disclosure or corruption, according to a pre-defined scale.
The classification provides information on how that asset should be treated for purposes of security. |
| Security Incident |
An incident specifically related to the security of the organisation’s assets. |
| Security Patch |
An amendment to existing software or firmware to correct a security vulnerability. |
| Security Plan |
A plan describing the existing and planned controls required in order to meet the organisation’s requirements with regard to security. |
| Security Policy |
High-level plan describing the goals, scope, approach and responsibilities for security management within the organisation. |
| Security Vulnerability |
A deficiency in security controls which may be either accidentally or deliberately exploited. |
| Service |
A set of CIs providing certain functionality. |
| Service capacity |
The maximum throughput that a configuration item or service can deliver. |
| Service catalogue |
A list of currently available services and which is a subset of all the services contained within the service portfolio. |
| Service Desk |
A customer-facing support group who do a high proportion of the total support work. |
| Service hours |
The period of time during which the functionality of a service should be accessible to its customers. |
| Service Knowledge Management System (SKMS) |
A set of tools and databases that are used to manage knowledge and information data. |
| Service level |
Elements of a service that enable it to be measured (and those measures to be compared against required service level targets). |
| Service level agreement (SLA) |
A documented agreement between a service provider and a customer that identifies the services required together with the associated levels of service that are expected to be delivered. |
| Service Level Agreement (SLA) |
An agreement between the service owner and the customer of the service including details of who receives the service and the level of service to which they are entitled.
Also, in ISO/IEC 20000 terms, a written agreement between a service provider and a customer that documents services and agreed service levels. |
| Service Management |
The management of services in order to meet the stated business requirements. |
| Service Management Policy |
A document that contains the objectives and plans for the implementation and running of service management processes and activities within the organisation. |
| Service map/service model |
A high-level view of a service and its component configuration items and their relationships and inter-dependencies. |
| Service Provider |
In ISO/IEC 20000 terms, the organisation aiming to achieve ISO/IEC 20000 certification. |
| Service Report Catalogue |
The catalogue which defines the following details for all required reports:
- Report name
- Report owner
- Report approver(s)
- Report scope
- Report purpose
- Data required, its sources
- KPI’s and metrics the report is covering
- Frequency of delivery
- Target audience
- Electronic location
|
| Service request |
A request from a user (or their authorised representative) that triggers a service action which has been previously agreed as part of the normal delivery activity for a service. |
| Service validation |
Determining release management and deployment management acceptance criteria that can be verified via testing activities. |
| Skills |
A developed proficiency or dexterity of thought, verbal communication or physical action. |
| Software |
A programme or suite of programmes, operating systems/environments, databases, etc. upon which smaller application programmes, processes and workflows can run.
Includes: desktop applications, mobile apps, embedded software, websites, etc. |
| Software asset management (SAM) |
An element of IT asset management aimed at managing the acquisition, development, release, deployment, maintenance and retirement of software assets. |
| Specific Risks |
Detailed risks that refer to particular instances of a generic risk, such as the risk of hardware failure on a specific legacy system which is now out of support. |
| Testing |
Activities undertaken to verify that a new or changed product or service has satisfied stated acceptance criteria. |
| Thresholds |
Values set for specific monitored metrics which if met will result in an automated action.
May be aligned with agreed service level targets. |
| Trigger |
Anything that will give warning that a risk is either occurring or is about to occur.
Triggers should be identified as part of the Risk Action Plan and then monitored, preferably using automated tools where possible. |
| Trusted Source |
A reputable and/or official source of security notifications or patches, information from which the organisation will take to be genuine without requiring independent verification from alternative sources. |
| User experience (UX) |
Design activities that focus on ease of use of the product or service, and how the customer interacts with it. |
| Utility requirements |
Functional requirements defined by a customer and are unique to a specific product. |
| Value stream |
A series of steps undertaken by an organisation to create and deliver products and services to consumers. |
| Warranty requirement |
Non-functional requirements that are gathered from key stakeholders and via other related practices. |
| Workaround |
A solution that reduces or eliminates the impact of an incident or problem for which a full resolution is not yet available.
Some workarounds may reduce the likelihood of incidents from occurring. |
| Workaround |
Means of resolving or avoiding a particular incident without fixing the underlying problem. |