ISO/IEC 20000 (ITSM) Lead Implementer Training — Lesson 4: Availability, Continuity, Security, Reporting, Audit, and Improvement

Learning Objectives

• Interpret the principles, requirements, roles, and dependencies shaping availability, continuity, security, reporting, audit, and improvement.
• Apply the workflow and produce SMS readiness report that can withstand review.
• Analyze “targets pass while users face disruption” and recommend a proportionate evidence-based response.

Detailed Topics

• availability
• service continuity
• information security
• service reporting
• performance measurement
• internal audit
• management review
• continual improvement
• Competence, communication, governance, documented information, risk, and follow-up

Instructor Demonstration

The instructor demonstrates the availability, continuity, security, reporting, audit, and improvement workflow, identifies applicable inputs and responsibilities, records checkpoints in SMS readiness report, and contrasts the accepted state with a condition where targets pass while users face disruption.

Hands-On Exercise

Complete a controlled implementation, audit, analysis, or foundation exercise for Availability, Continuity, Security, Reporting, Audit, and Improvement. Establish scope and criteria, collect or create evidence, examine “targets pass while users face disruption,” reach a supported conclusion, and preserve the result in SMS readiness report.

1. Confirm objectives, scope, roles, criteria, stakeholders, and expected outputs.
2. Perform planned activities while recording assumptions, evidence, and decisions.
3. Test a normal case, an exception, and a follow-up or improvement condition.
4. Document conclusions, owners, due dates, escalation, and verification requirements.

Scenario Analysis

• Identify the requirement or principle with the strongest influence on availability, continuity, security, reporting, audit, and improvement.
• Compare two defensible responses and explain governance, risk, and evidence trade-offs.
• Determine how SMS readiness report should be approved, retained, reviewed, and updated.

Troubleshooting Guidance

Separate missing evidence from ineffective practice, and distinguish a documentation issue from a control, process, governance, or competence failure. Use SMS readiness report to trace the earliest divergence. Treat “targets pass while users face disruption” as a hypothesis until the response is validated against the relevant requirement and intended outcome.

Validation Checklist

• The scope, criteria, stakeholders, and intended outcome for availability, continuity, security, reporting, audit, and improvement are explicit.
• The SMS readiness report links statements and decisions to objective, reviewable support.
• Responsibilities, competence, communication, risk, legal duties, and change impact were considered.
• Findings, corrective actions, monitoring, review triggers, and improvement ownership are clear.

Lesson Outcome

Learners can apply Availability, Continuity, Security, Reporting, Audit, and Improvement, explain the reasoning, and defend the result through SMS readiness report.