Service management system planning and implementing
This domain addresses how the SMS is planned and put into operation, mainly Clause 6 (planning) with the implementation expectations of Clause 4.4. The exam tests risk-based planning, measurable objectives and controlled change, rather than a one-time project plan.
Risk, objectives and change
Planning must address risks and opportunities arising from context and interested-party requirements. The organization decides actions needed so the SMS achieves intended outcomes, prevents undesired effects and improves; it integrates actions into SMS processes and evaluates their effectiveness. Service management objectives are set at relevant functions and levels, consistent with policy, measurable where practicable, monitored, communicated and updated. Each objective needs a plan: what will be done, resources, owner, timeframe and how results are evaluated. Changes to the SMS are planned, considering purpose, consequences, SMS integrity, resources and responsibilities.
Implementation
Implementation means establishing, implementing, maintaining and continually improving the SMS and its processes. It depends on support elements: resources, competence, awareness, communication and documented information. A plan that stops at launch is incomplete; operation and review must be resourced.
Worked example
An objective says 'improve availability'. It cannot be evaluated. A better objective is 'raise availability of Service A from 99.5% to 99.8% over the next two quarters, measured monthly by the service desk tool'. The plan names the service owner, engineering resources, actions, milestones, reporting and evaluation. The first version is a slogan; the second is auditable.
Traps
Do not keep a risk register that never changes decisions. Do not set objectives without baselines or owners. Do not make changes without impact assessment. Do not plan only for initial certification.