Fundamental Principles and Concepts of a Service Management System
This domain tests whether you can separate the system from the tools and processes that support it, and whether you know which document in the ISO/IEC 20000 family says what. Expect definitional questions and "which statement is true" items.
Definitions that carry marks
- Service: a means of delivering value to the customer by facilitating outcomes the customer wants to achieve, without the customer having to own specific costs and risks.
- Service management system (SMS): a management system to direct and control the organization's service management activities.
- Management system: a set of interrelated elements - policy, objectives, processes, roles and authorities, documented information - used together to achieve objectives.
The family of standards
ISO/IEC 20000-1 holds the requirements, uses "shall", and is the only certifiable document. ISO/IEC 20000-2 is guidance ("should"). ISO/IEC 20000-3 covers scope and applicability. ISO/IEC 20000-5 describes an implementation plan. ISO/IEC 20000-6 sets requirements for certification bodies. ISO/IEC 20000-10 holds concepts and vocabulary. Quoting 20000-2 as if it were auditable is a classic error.
Principles the exam keeps returning to
- Process approach: each process needs a purpose, inputs, outputs, an owner, measures and defined interfaces with other processes.
- PDCA: Plan (establish), Do (implement and operate), Check (monitor and review), Act (maintain and improve).
- Risk-based thinking and evidence-based decisions: if it is not retained as documented information, it did not happen.
- Continual improvement as a permanent loop, not a one-off project.
Worked example
An organization has a ticketing tool, published SLAs and monthly reports, and claims it has an SMS. Missing: a documented scope, a service management policy, measurable objectives, internal audit, management review and corrective action. Reasoning: the elements that make a system coherent are absent, so conformity fails even though day-to-day operations look healthy. The tool is an enabler, not the system.
Traps
Equating ITIL maturity with ISO/IEC 20000 conformity; assuming guidance documents are auditable; believing that buying a tool creates the SMS; forgetting that the SMS must also cover interfaces and dependencies on suppliers and other parties within the declared scope.