ITIL 4 MSF key terms

The single point of contact between the service provider and users, handling incidents, service requests, and communication, and acting as the entry point to all other support and delivery teams.

An unplanned interruption to a service or a reduction in its quality that has not yet been diagnosed and resolved through normal request handling.

The practice that minimizes the negative impact of incidents by restoring normal service operation as quickly as possible, prioritizing speed of recovery over root-cause analysis.

An incident with significant business impact that demands a coordinated, high-priority response, often with a dedicated team, defined escalation path, and frequent stakeholder communication.

A cause, or potential cause, of one or more incidents. Problems are investigated to remove underlying causes and reduce the likelihood and impact of future incidents.

The practice of reducing the likelihood and impact of incidents by identifying actual and potential causes of incidents and managing workarounds and known errors.

A problem that has been analyzed and has a documented root cause or a documented workaround, allowing faster diagnosis and consistent handling of related incidents.

A temporary solution that reduces or eliminates the impact of an incident or problem for which a full resolution is not yet available, restoring service without removing the cause.

A structured investigation technique used to identify the underlying reason an incident or problem occurred, so that permanent corrective action can be taken.

The act of transferring an incident, request, or task to a more specialized or higher-authority level when it cannot be resolved at the current level or when impact demands it.

Escalation based on the need for greater technical skill or knowledge, moving work from first-line staff to more specialized support groups or subject-matter experts.

Escalation based on authority, urgency, or business impact, involving managers or senior stakeholders who can make decisions, allocate resources, or authorize action.

A collaborative working style in which a group of people with relevant skills is brought together to resolve a work item, rather than passing it between tiers sequentially.

A request from a user for something new or a change to an existing service, such as information, access, a standard change, or a pre-approved catalog item.

The practice that supports the agreed quality of a service by handling all pre-defined, user-initiated service requests in an effective and user-friendly manner.

A structured, published list of available services and service offerings, including descriptions, prices, and ordering details, used by users to request what they need.

A documented agreement between a service provider and a customer that identifies required services and the expected level of service, typically expressed as measurable targets.

A measurable target for a specific aspect of service performance, such as response time or availability, used to track whether agreed service levels are being met.

The practice of setting clear business-based targets for service levels, ensuring delivery against them, and managing customer expectations through measurement and reporting.

A categorization of the relative importance of an incident or request, usually derived from impact and urgency, that determines the order and speed of handling.

A measure of the effect of an incident, problem, or change on business processes and services, often judged by the number of users or criticality of the affected component.

A measure of how quickly an incident or request requires attention, based on the potential damage or business consequence of delay rather than on the size of the effect.

Any change of state that has significance for the management of a service or other configuration item, detected by monitoring tools or reported by people.

The practice of systematically observing services and components, recording and reporting selected state changes, and identifying their significance so action can be taken.

A notification generated when a monitored condition crosses a defined threshold or matches a rule, prompting someone or an automated tool to investigate or act.

Any component that needs to be managed in order to deliver an IT service, including hardware, software, networks, documentation, and people, recorded in the configuration management system.

A database that stores records of configuration items and the relationships between them, supporting impact assessment, incident diagnosis, and change planning.

Any financially valuable component that can contribute to the delivery of an IT product or service, tracked for cost, ownership, and lifecycle purposes.

The addition, modification, or removal of anything that could have a direct or indirect effect on services, ranging from small fixes to large releases.

The practice of ensuring that risks are properly assessed, authorizing changes to proceed, and managing the change schedule to maximize successful service and product changes.

A low-risk, pre-authorized change that is well understood, repeatable, and follows a documented procedure, so it does not require individual approval each time.

A group that supports change assessment and authorization by evaluating proposed changes for risk, impact, and readiness, and advising the change authority.

A calendar or plan showing planned changes and their scheduled implementation windows, used to coordinate work, avoid conflicts, and communicate downtime to users.

A version of a service or other configuration item, or a collection of configuration items, made available for use, often deployed together as a coordinated unit.

The practice of moving new or changed hardware, software, documentation, processes, or other components to live environments in a controlled and repeatable way.

The practice of ensuring that new or changed products and services meet defined requirements, both in terms of utility and warranty, before they are released into live use.

The functionality offered by a product or service to meet a particular need, describing what the service does and whether it is fit for purpose.

The assurance that a product or service will meet agreed requirements, covering availability, capacity, security, and continuity, and describing whether it is fit for use.

The practice of aligning an organization's practices and services with changing business needs through the ongoing identification and improvement of services, components, and practices.

A series of steps an organization undertakes to create and deliver products and services to consumers, mapped to reveal waste and opportunities for improvement.

An operating model of six interconnected activities, plan, improve, engage, design and transition, obtain and build, and deliver and support, that converts demand into value.

A model showing how the components and activities of an organization work together as a whole to enable value creation, including guiding principles, governance, and practices.