The ITIL 4 Service Value System (SVS)
The Service Value System (SVS) is the central model of ITIL 4. It describes how all the components and activities in an organisation work together to enable value creation. The SVS has five components: Guiding Principles (seven principles that guide decisions and actions), Governance (the means by which an organisation is directed and controlled), Service Value Chain (the operating model for creating, delivering, and continually improving services), Practices (34 management practices that support activities in the SVS), and Continual Improvement (an ongoing organisational activity to ensure services meet evolving business needs). The SVS inputs are Opportunity (potential for adding value) and Demand (need for products and services from internal or external customers). The output is Value — the outcomes, benefits, and cost reductions delivered to stakeholders. The SVS is deliberately flexible — it recognises that organisations work in an ecosystem with other entities and must adapt to the environment.
The Seven Guiding Principles
ITIL 4's seven guiding principles are universal recommendations that guide organisations in all circumstances. Focus on Value: every activity should link back to value for stakeholders — ask 'who benefits from this?' and 'how?'. Start Where You Are: do not start from scratch — assess what currently exists before building something new, preserve what works. Progress Iteratively with Feedback: work in small increments, gather feedback, adjust — do not design the perfect solution before delivering any value. Collaborate and Promote Visibility: involve stakeholders, share information, break silos — poor communication is the most common cause of project failure. Think and Work Holistically: understand how all parts of the system interact — optimising one part in isolation often degrades the whole. Keep It Simple and Practical: eliminate waste, do not add complexity without clear benefit. Optimise and Automate: remove manual steps where technology can do it better — but optimise the process first, then automate, not the other way around. The exam tests which principle applies to a given scenario — all seven are equally important.
The Service Value Chain and Four Dimensions
The Service Value Chain is the operating model for delivering value. Six activities in the chain: Plan (ensure a shared understanding of direction and improvement), Improve (ensure continual improvement of products, services, and practices), Engage (understand stakeholder needs, maintain transparency), Design and Transition (ensure services meet stakeholder expectations for quality, costs, and time), Obtain/Build (ensure service components are available), Deliver and Support (deliver services per agreed specifications). The four dimensions model defines four perspectives that must be balanced to provide a holistic view of service management: Organisations and People (culture, skills, roles — everyone must understand their role in value delivery), Information and Technology (knowledge, data, tools needed), Partners and Suppliers (relationships with third parties), Value Streams and Processes (how activities create value — workflows, procedures). The PESTLE factors (Political, Economic, Social, Technological, Legal, Environmental) represent external forces that affect all four dimensions.
Key ITIL 4 Practices
ITIL 4 replaced ITIL v3's 26 processes with 34 practices grouped in three categories. General Management Practices (applicable beyond IT): Continual Improvement, Information Security Management, Relationship Management, Supplier Management, Knowledge Management. Service Management Practices (core IT SM): Incident Management (restore normal service operation as quickly as possible — reactive), Problem Management (identify root cause of incidents to prevent recurrence — reactive and proactive), Change Enablement (maximise changes while minimising disruption — change types: standard, normal, emergency), Service Desk (the entry point for users — single point of contact), Service Level Management (agree, monitor, and report on SLAs), Monitoring and Event Management, Service Request Management (fulfil standard requests — pre-approved, low risk). Technical Management Practices: Deployment Management (moving changes to the live environment), Infrastructure and Platform Management, Software Development and Management. High-priority exam topics: know the purpose of Incident, Problem, Change Enablement, Service Desk, and SLM practices cold.
Incident, Problem, and Change Management Deep Dive
Three practices are central to ITIL 4 Foundation exam questions. Incident Management: restore service as quickly as possible — an incident is an unplanned interruption or quality reduction. Classify by urgency and impact (priority matrix). Escalation: functional (transfer to team with skill), hierarchical (escalate to management). Major incident: defined threshold of impact — separate major incident process with dedicated coordinator. Problem Management: investigate root cause of incidents — a problem is the cause of one or more incidents. Problem record: documents investigation status. Known error: problem with identified root cause but no permanent fix yet — workaround documented. Problem closure: permanent fix implemented, known error removed. Change Enablement: ensure changes are beneficial, assessed, authorised, and managed. Change types: Standard change (pre-approved, low risk, well-understood — e.g., password reset), Normal change (assessed and authorised by Change Authority — follows change schedule, CAB), Emergency change (needed to resolve major incident or urgent security issue — faster approval path, can be authorised post-implementation). CAB (Change Advisory Board) advises the Change Authority on normal changes.