Service management system general requirements
This domain covers the foundation of an ISO/IEC 20000-1 service management system (SMS), mainly Clause 4 (context) and Clause 5 (leadership) in the 2018 structure. The exam tests whether you can tell a management system from a service catalogue or a set of practices: the SMS governs how services and processes are directed, controlled and improved.
Context, scope and system
The organization determines external and internal issues relevant to its purpose and strategic direction, plus interested parties and their requirements. The SMS scope is a boundary decision based on those issues, applicable requirements, and the services and service components delivered. The scope must be documented and available. Certification is against that scope, so it cannot be drawn to hide awkward dependencies.
Leadership and roles
Top management must lead, not merely approve. It sets a service management policy compatible with strategy, ensures objectives, integrates SMS requirements into business processes, provides resources, communicates importance and promotes improvement. The policy commits to satisfying applicable requirements and to continual improvement. Responsibilities and authorities are assigned, and people need authority to act, not just titles.
Worked example
A provider proposes a scope of 'service desk and incident management only', although its service depends on an outsourced data centre. The scope is probably inadequate: the service and its components include that dependency. Include and govern the dependency, or explicitly justify and control the boundary. Narrowing scope to avoid requirements does not remove the need to manage the service.
Traps
Do not reduce context to a one-off SWOT. Do not treat leadership as sign-off. Do not omit service components or third parties from scope. Do not write a policy without compliance and continual improvement commitments. Roles without authority are a frequent finding.