Skip to content

ITIL 4 Foundation Study Notes

Overview

ITIL is the most widely recognized best practice guidance framework for IT Service Management (ITSM). Rather than a strict, legally binding "law," ITIL provides a set of recommendations that organizations adopt and adapt to their specific needs to plan, implement, support, and improve services.

Core Concept: Value Co-Creation

The fundamental shift in modern ITIL (ITIL 4) is moving away from unilateral "service delivery" to Value Co-Creation.

Value : The perceived benefits, usefulness, and importance of something.

Value is created jointly through active collaboration between service providers and service consumers.

+------------------+                   +------------------+
| Service Provider | <===============> | Service Consumer |
| (Offers resources|   Co-Creation     | (Provides needs  |
|  & expertise)    |     of Value      |  & uses service) |
+------------------+                   +------------------+

Key Service Definitions

Service : A means of enabling value co-creation by facilitating outcomes that customers want to achieve, without the customer having to manage specific costs and risks.

Service Offering (Offre de Service) : A formal description of one or more services designed to address the needs of a target consumer group. It can include goods (transfer of ownership), access to resources (under agreed terms), and service actions (performed by the provider to address consumer needs).

Service Provision (Fourniture de service) : Activities performed by an organization to provide services, including managing resources, provisioning access, executing service actions, managing service levels, and continual improvement.

Outcome (Résultat) : A result for a stakeholder, enabled by one or more outputs.

Outcome vs. Output

An output is a tangible or intangible deliverable of an activity (e.g., a software release, a server deployed). An outcome is the result achieved by using those outputs (e.g., increased sales, improved customer satisfaction).

Consumer Stakeholder Roles

A single consumer organization can have individuals acting in different roles:

  • Client (Customer): Defines the requirements for a service and takes responsibility for the outcomes of service consumption.
  • Utilisateur (User): The role that uses the services.
  • Sponsor: The role that authorizes the budget for service consumption.

The Four Dimensions of Service Management

To ensure a holistic approach, ITIL suggests looking at every service through four dimensions (historically known as the "Four P's"). These dimensions must be balanced for the effective facilitation of value.

       +---------------------------------------------+
       |            Organizations & People           |
       +----------------------+----------------------+
                              |
       +----------------------+----------------------+
       |            Information & Technology         |
       +----------------------+----------------------+
                              |
       +----------------------+----------------------+
       |            Partners & Suppliers             |
       +----------------------+----------------------+
                              |
       +----------------------+----------------------+
       |          Value Streams & Processes          |
       +---------------------------------------------+
  1. Organizations & People: Focuses on roles, responsibilities, reporting lines, communication, collaboration, and organizational culture.
  2. Information & Technology: Covers the information, data, and knowledge needed to manage services, as well as the underlying technologies (databases, networking, software, APIs) required to deliver them.
  3. Partners & Suppliers: Encompasses the organization's relationships with other businesses involved in the design, development, deployment, delivery, support, and improvement of services.
  4. Value Streams & Processes: Focuses on how the different parts of the organization work in an integrated and coordinated way to enable value creation through products and services.

External Factors (PESTLE)

Every dimension is constantly affected by multiple external factors that the organization cannot directly control: P*olitical * Economic Social * Technological Legal * Environmental

The Service Value System (SVS)

The Service Value System (SVS) is the central element and foundation of the ITIL framework. It is a model representing how all the components of an organization work together to facilitate value creation.

At a high level, the flow is: Input ➡️ SVS ➡️ Outcome

+-------------+      +-------------------------------------------+      +---------+
| Opportunity | ===> |  [ SVS: Guiding Principles, Governance,  ] | ===> |  Value  |
|  & Demand   |      |   Value Chain, Practices, Improvement ]   |      |         |
+-------------+      +-------------------------------------------+      +---------+

Components of the SVS

  • ITIL Guiding Principles: Universal recommendations that guide an organization in all circumstances.
  • Governance: The means by which an organization is directed and controlled.
  • ITIL Service Value Chain (SVC): An operating model covering all key activities required to effectively manage products and services.
  • ITIL Practices: Sets of organizational resources designed for performing work.
  • Continual Improvement: The practice of consistently aligning practices and services with changing business needs.

The 7 Guiding Principles

Universal, durable recommendations that guide an organization in all circumstances:

  1. Privilégier la valeur (Focus on value): Everything the organization does must link back, directly or indirectly, to value for stakeholders.
  2. Commencer là où vous en êtes (Start where you are): Do not start from scratch without considering what is already available. Measure and evaluate the current state first.
  3. Procéder par itération avec des retours (Progress iteratively with feedback): Organize work into small, manageable sections (timeboxes) that can be executed and improved iteratively with regular feedback.
  4. Collaborer et promouvoir la visibilité (Collaborate and promote visibility): Work across boundaries to produce results. Visualizing work (e.g., Lean workflows, bottlenecks) is critical.
  5. Penser et travailler de façon holistique (Think and work holistically): No service, process, or department stands alone. Services are delivered through the integration of the four dimensions.
  6. Opter pour la simplicité et rester pratique (Keep it simple and practical): Use the minimum number of steps needed. Eliminate any process, action, or metric that does not create value.
  7. Optimiser et automatiser (Optimize and automate): Optimize workflows before applying automation.

The Service Value Chain (SVC)

The Service Value Chain is an operating model inside the SVS that outlines the six interconnected activities required to respond to demand and facilitate value creation through products and services:

  1. Planifier (Plan): Ensure a shared understanding of the vision, current status, and improvement direction.
  2. Améliorer (Improve): Ensure continual improvement of products, services, and practices across all value chain activities and dimensions.
  3. Impliquer (Engage): Provide a good understanding of stakeholder needs, transparency, and good relationships.
  4. Conception et transition (Design and transition): Ensure that products and services continually meet stakeholder expectations for quality, cost, and time-to-market.
  5. Obtenir et construire (Obtain/build): Ensure that service components are available when and where they are needed, and meet agreed specifications.
  6. Fournir et Soutenir (Deliver & support): Ensure that services are delivered and supported according to agreed specifications.

ITIL Continual Improvement Model

A structured, step-by-step approach to implementing improvements that can be applied to any level of the organization.

The 7 Steps of the Continual Improvement Model
  1. What is the vision? (Quelle est la vision?): Understand business vision, missions, and goals.
  2. Where are we now? (Où en sommes-nous maintenant?): Perform a baseline assessment to understand current performance.
  3. Where do we want to be? (Où voulons-nous être?): Define measurable target states (KPIs, metrics).
  4. How do we get there? (Comment y parvenir?): Define the improvement plan.
  5. Take action (Mise en place des actions): Execute the improvement plan (applying corrective actions as needed).
  6. Did we get there? (Y sommes-nous parvenus?): Measure the results against the baseline.
  7. How do we keep the momentum going? (Comment garder cet élan?): Ensure changes are embedded and plan the next improvement iteration.

The Continual Improvement Register (CIR)

A database or document used to capture, document, evaluate, prioritize, and track improvement opportunities.

  • Continual improvement is the responsibility of everyone in the organization, though a dedicated team is highly recommended to coordinate efforts.
  • Techniques: SWOT analysis (MOFF), Balanced Scorecards, internal/external audits, Lean, Agile iterations, and DevOps.

Key ITIL Practices

A Practice is a set of organizational resources designed for performing work or accomplishing an objective.

1. Incident Management (Gestion des incidents)

The purpose of Incident Management is to reduce the negative impact of incidents by restoring normal service operation as quickly as possible.

  • Incident: An unplanned interruption to a service, or reduction in the quality of a service.
  • Key Incident Handling Steps:
  • Log every incident in a centralized ITSM tool.
  • Categorize and prioritize accurately based on impact × urgency (not based on who reported it).
  • Acknowledge quickly and communicate with the user.
  • Perform initial diagnosis (via Service Desk or self-help).
  • Escalate when needed to support tiers (Tier 2/3) or specialized groups.
  • Resolve and recover service (sometimes using a workaround).
  • Confirm restoration and close the incident.
  • Resolution Channels: Self-help, Service Desk, specialized support teams, suppliers/partners, temporary teams (for major incidents), and disaster recovery plans.

2. Problem Management (Gestion des problèmes)

The purpose of Problem Management is to reduce the likelihood and impact of incidents by identifying actual and potential causes of incidents, and managing workarounds and known errors.

  • Problem vs. Incident:
  • Incident: Restores service as fast as possible.
  • Problem: Finds the root cause and prevents future incidents.
  • Key Definitions:
  • Known Error (Erreur connue): A problem that has been analyzed but has not yet been resolved.
  • Workaround (Solution de contournement): A temporary solution that reduces or eliminates the impact of an incident or problem for which a full resolution is not yet available.
  • Three Phases of Problem Management:
    1. Problem Identification (Identification): Detecting trends, review major incidents.
    2. Problem Control (Contrôle): Analyzing problems, identifying root causes, defining workarounds.
    3. Error Control (Contrôle des erreurs): Managing known errors, evaluating permanent resolutions (which may require initiating a change).

3. Change Enablement (Habilitation des changements)

Ensures that risks are properly assessed, changes are authorized, and a change schedule is managed to maximize the number of successful service and product changes.

  • Change: The addition, modification, or removal of anything that could have a direct or indirect effect on services.
  • Change Authority: The person or group who authorizes a change.
  • Three Types of Changes:
  • Standard Change: Low-risk, pre-authorized, well-understood, and fully documented. Needs no additional authorization.
  • Normal Change: Scheduled, evaluated, and authorized following a formal process (triggered by a Request for Change / RFC).
  • Emergency Change: Must be implemented as soon as possible to resolve major incidents or security threats.
  • Change Schedule: A tool used to plan changes, facilitate communication, avoid conflicts, and allocate resources.

4. Service Level Management (Gestion des niveaux de service)

Defines clear business-based targets for service performance, so that the delivery of a service can be properly assessed, monitored, and managed against these targets.

  • Service Level: One or more metrics defining the expected or achieved quality of service.
  • SLA (Service Level Agreement): A documented agreement between a service provider and a customer that identifies both services required and the expected level of service.
  • SLA Rules: Must be linked to a service in the catalog, report to business outcomes (not just technical metrics), reflect an agreement, and be easy to understand.
  • SLA Inputs: Customer engagement, customer feedback, operational metrics, and business metrics.

5. Service Configuration Management (Gestion des configurations)

Ensures that reliable and accurate information about the configuration of services, and the Configuration Items (CIs) that support them, is available when and where it is needed.

  • Configuration Item (CI): Any component that needs to be managed in order to deliver an IT service.
  • Core Purpose: Maps relationships and dependencies between CIs (e.g., SaaS components, local servers, cloud storage). It provides indirect value by enabling other practices like change and incident management to work effectively.

6. Release Management (Gestion des mises en production)

Makes new and modified services and features available for use.

  • Release: A version of a service or other CI, or collection of CIs, made available for use.
  • Decoupled from Deployment: A service can be deployed to production (e.g., backend servers) days before it is formally released to customers (e.g., via feature flags).

7. Deployment Management (Gestion des déploiements)

Moves new or changed hardware, software, documentation, processes, or any other service component to live environments.

  • Differs from Release in that it focuses on the physical/virtual move of files and configuration to environments, whereas Release focuses on making them available for use.

8. IT Asset Management (Gestion des actifs informatiques)

Plans and manages the full lifecycle of all IT assets to maximize value, control costs, and manage risks.

  • IT Asset: Any financially valuable component that can contribute to the delivery of an IT product or service.
  • Scope: Software, hardware, networks, cloud services, and client devices.

9. Monitoring and Event Management (Surveillance et gestion des événements)

Systematically observes services and service components, and records and reports selected changes of state identified as events.

  • Event: Any change of state that has significance for the management of a service or other CI.
  • Classification:
  • Information: Normal status updates (e.g., backup complete).
  • Warning: Anomalies requiring attention but not yet affecting services (e.g., CPU utilization at 85%).
  • Exception: Failures representing a service degradation or security issue (e.g., server down).

10. Service Desk (Centre de services)

Acts as the single point of communication between the service provider and all of its users.

  • Captures incident resolution requests and service requests.
  • Focuses on customer experience, empathy, prioritization, and business understanding.

References

Disclaimer

This document is a compilation of my personal study notes for the ITIL® 4 Foundation certification and is intended for educational purposes only. It is not an official publication of AXELOS Limited, PeopleCert, or any authorized training provider. All trademarked names and brand names are the property of their respective owners.