EX0-115 and EXIN IT Service Management Foundation

EX0-115 is an older Exam-Labs code label associated with EXIN's IT Service Management Foundation based on ISO/IEC 20000. The credential itself remains current, but EXIN now presents it as EXIN IT Service Management Foundation based on ISO/IEC 20000:2018 rather than centering the old EX0-115 identifier. That distinction matters in 2026: candidates can still study the service-management body of knowledge represented by this page, but they should verify registration, language availability, and preparation materials through EXIN's current certification system rather than assuming the historical code is the booking reference.

The current EXIN foundation exam is a one-hour, 40-question, closed-book multiple-choice assessment with a 65 percent pass mark. Its official subject structure is deliberately compact: introduction to IT service management, the service management system, and operation of that system. The most productive preparation therefore focuses on how an organization establishes, operates, evaluates, and continually improves a coherent service management system rather than memorizing a long catalog of isolated process names.

Within the broader EXIN certification portfolio, this credential is useful for service managers, operations staff, support professionals, process owners, auditors, suppliers, and anyone who needs a common vocabulary for managing services. It can also help candidates distinguish an ISO/IEC 20000 management-system perspective from frameworks such as ITIL 4 Foundation, which overlaps in service-management thinking but has a different structure and certification owner.

ISO/IEC 20000 treats service management as a system, not a collection of disconnected processes

The central idea is the service management system, usually abbreviated SMS. An SMS brings together policies, objectives, responsibilities, documented information, resources, controls, measurement, and improvement activities so that services can be planned and managed consistently. This system view prevents a common study mistake: learning incident management, change control, service levels, or supplier activities as separate checklists without understanding how leadership, planning, governance, and evidence connect them.

A candidate should be able to explain why an organization defines the scope of its SMS and why that scope affects every later decision. The scope identifies which services, organizational units, locations, customers, and supporting capabilities are governed by the system. If the scope is vague, it becomes difficult to decide which objectives apply, which suppliers are relevant, what evidence must be retained, and how performance should be measured. Exam scenarios often become easier when the candidate first asks, “What part of the service-management system is being controlled or improved here?”

Leadership and planning establish the conditions for reliable service delivery

Service management cannot be delegated entirely to a service desk or process office. Leadership must set direction, provide resources, assign accountability, and make sure service-management objectives support business needs. Candidates should understand the difference between approving a policy and actually creating conditions in which that policy can be followed. Roles, competence, communication, resources, and decision rights are practical parts of governance, not administrative decoration.

Planning also requires organizations to consider risks and opportunities. A service can meet yesterday's targets yet still be exposed to a capacity constraint, supplier dependency, security weakness, skills shortage, or continuity risk. Foundation-level reasoning is less about sophisticated quantitative modeling and more about recognizing that risks should influence priorities and controls. An organization should be able to explain what it is trying to achieve, what might prevent that outcome, how it will respond, and how it will know whether the response is working.

Service design and transition connect customer expectations with operational capability

Before a new or changed service enters live use, the organization needs a clear understanding of requirements, service levels, dependencies, capacity, availability, continuity, information security, and support arrangements. Good service management asks whether the complete operating model is ready, not merely whether a technical component has passed a test. A release that is technically functional can still fail if monitoring is missing, support teams are unprepared, supplier obligations are unclear, or recovery procedures have never been exercised.

Change control should therefore be understood as risk-informed governance rather than bureaucracy. Different changes carry different levels of uncertainty and potential impact. The organization needs an approach for evaluating, authorizing, scheduling, communicating, and reviewing changes in a way that protects service outcomes without making routine work unnecessarily slow. Candidates should be able to distinguish an emergency response from normal planning and recognize why post-implementation evidence can improve future decisions.

Incident and problem management answer different operational questions

An incident interrupts or reduces the quality of a service, so incident management prioritizes restoration. The immediate question is how to return users to acceptable service as efficiently as possible while maintaining communication and escalation. Problem management asks a different question: why did one or more incidents occur, and what can be done to reduce recurrence or impact? Conflating the two leads to poor exam reasoning and poor operations.

A temporary workaround may be entirely appropriate during an incident even though it does not remove the underlying cause. Later analysis can examine patterns, known errors, technical evidence, supplier behavior, configuration information, or process weaknesses. Candidates should understand that incident records are not just tickets to close; they create operational data that can reveal recurring failure modes, ineffective controls, and opportunities for automation or prevention.

Service levels, suppliers, and relationships make performance visible across organizational boundaries

Service management depends on expectations that can be understood and measured. Service-level management translates customer requirements into agreed targets and review mechanisms. Strong measures describe outcomes that matter to customers rather than simply counting internal activity. A support team might close many tickets quickly while customers still experience recurring interruptions, poor communication, or slow recovery from high-impact failures.

Supplier relationships add another layer because an organization can outsource an activity without outsourcing accountability for the service experience. Contracts and agreements should support the required service outcomes, and supplier performance should be monitored in context. When several providers contribute to one service, the organization needs an integrated view of dependencies, escalation, data exchange, security responsibilities, and changes. That broader relationship perspective also explains why ITSM knowledge remains useful alongside more specialized supplier-integration approaches.

Measurement and continual improvement turn the SMS into a learning system

Measurement is useful only when it supports decisions. Candidates should distinguish raw metrics from meaningful evaluation: ticket counts, response times, failed changes, availability percentages, customer feedback, audit findings, and supplier measures all require interpretation. Trends and context matter. A single month can look excellent while masking deteriorating resilience or growing technical debt, while a short-term metric can worsen because the organization is finally exposing previously hidden work.

Continual improvement uses evidence to select, prioritize, implement, and review changes to services and the management system. The objective is not constant change for its own sake. Improvement should be tied to business value, risk, customer outcomes, and measurable gaps. Small, well-evidenced improvements can be more valuable than an ambitious transformation with unclear ownership. Candidates who learn to ask what evidence triggered an improvement and how success will be assessed usually handle scenario questions more reliably.

ISO/IEC 20000 and ITIL are related but should not be treated as interchangeable

ITIL is widely used as a body of service-management guidance, while ISO/IEC 20000 specifies requirements for a service management system. Organizations can use ITIL practices to help implement or improve parts of an ISO/IEC 20000-aligned system, but the two are not the same certification scheme and one does not automatically prove conformance with the other. The distinction is important when a question asks about organizational requirements, evidence, governance, or certification rather than general service-management guidance.

Candidates who already know ITIL should use that knowledge as context rather than forcing every EXIN question into ITIL terminology. The approved Exam-Labs article on ITIL certification can help clarify the separate credential path, while this page should remain focused on ISO/IEC 20000:2018 and EXIN's service-management-system perspective.

Preparation should follow the current EXIN specification rather than the old code label

The safest preparation method is to use EXIN's current preparation guide as the syllabus boundary, then connect each learning objective to practical examples. Build a simple mental model of the SMS first; then place service requirements, design, transition, operations, relationships, measurement, audits, and improvement within that model. When reviewing a scenario, identify the objective, affected role, required evidence, and stage of the management cycle before selecting an answer.

EX0-115 remains a useful historical locator because many training archives and search results use it, but the learning decision in 2026 should be based on the current EXIN IT Service Management Foundation based on ISO/IEC 20000:2018. Candidates pursuing deeper ISO/IEC 20000 implementation responsibility can also examine the approved ISO/IEC 20000 Lead Implementer destination, while broader management responsibility may make Certified Information Technology Manager relevant. The important point is progression by job need, not collecting adjacent credentials mechanically.

One useful final exercise is to trace a single business service across the SMS. Start with the customer requirement, identify the service owner and supporting suppliers, describe the relevant service level, then follow a normal change, an incident, and a review of performance. That exercise exposes the relationships among planning, operation, measurement, and improvement far better than learning definitions independently. It also helps candidates recognize which evidence would demonstrate that the system is working as intended.