ISO 20000 Monitoring and Measurement (Clause 4.5.4.1)

Example Conversation

You: We need to define KPIs for our SMS. We have ISO 20000 certification coming up in four months and the auditor will want to see a measurement framework.

Agent: I’ll help you build the monitoring and measurement framework. Let me load your SMS context first – I can see your service catalog and SLA register. Let me start with the KPIs for each process area.

For Clause 6 (Service Delivery), which is typically the most metric-rich area, what tools do you use for service monitoring and ticketing?

You: ServiceNow for ITSM, Datadog for infrastructure monitoring, and we track SLAs in a spreadsheet right now.

Agent: Good. I’ll use those as data sources. Here are the proposed KPIs for Clause 6:

KPI	Target	Warning	Critical	Data Source
SLA achievement rate	>= 95%	< 95%	< 90%	SLA spreadsheet
Service availability	>= 99.5%	< 99.5%	< 99.0%	Datadog
Capacity utilization	< 80%	>= 80%	>= 90%	Datadog
Incident volume trend	Decreasing	Stable	Increasing > 10%	ServiceNow

Do these targets align with your current service level agreements, or do you need to adjust?

You: The SLA target should be 97% – that’s what we committed to our customers. And we need to add first-call resolution rate for the service desk.

Agent: Updated. I’ll add first-call resolution under Clause 8 (Resolution) with a target of 70%, warning at 60%, and critical at 50%. Now let me define the remaining process areas.

For Clause 9 (Control), I’ll propose: change success rate, CMDB accuracy, release on-time delivery, and unauthorized change count. For Clause 4 (Governance), the key metrics are SMS policy review completion and management review completion.

You: That looks comprehensive. What about the CAPA process?

Agent: For the CAPA register, I’ll define trigger criteria that link to your thresholds:

• Any KPI hitting the critical threshold automatically raises a CAPA
• Audit nonconformities (from internal audits) raise a CAPA
• Recurring incidents (3+ occurrences of the same root cause) raise a CAPA
• Customer complaints raise a CAPA

Each CAPA gets a unique ID (CAPA-001, CAPA-002, etc.), a root cause classification (corrective vs. preventive), an assigned owner, and a target date. Closure requires effectiveness verification – confirming the metric returned to target after the action was implemented.

Let me generate the framework document, CAPA register, and KPI data file, then validate… Running monitoring_framework_validator – all checks passed. KPIs defined for all 6 process areas, measurement methods specified, targets set, and CAPA process documented.

Sample Output Excerpt

The skill produces a framework document, a CAPA register template, and a structured KPI JSON file. Here is a representative excerpt from the KPI data file.

{
  "process_areas": [
    {
      "clause": "6",
      "label": "Service Delivery",
      "kpis": [
        {
          "id": "KPI-6.1",
          "name": "SLA achievement rate",
          "description": "Percentage of SLA targets met across all services",
          "data_source": "SLA tracking spreadsheet",
          "calculation": "(SLA targets met / total SLA targets) * 100",
          "frequency": "monthly",
          "responsible": "Service Delivery Manager",
          "target": ">= 97%",
          "warning_threshold": "< 97%",
          "critical_threshold": "< 90%",
          "baseline": "94%"
        },
        {
          "id": "KPI-6.2",
          "name": "Service availability",
          "description": "Uptime percentage for production services during agreed hours",
          "data_source": "Datadog",
          "calculation": "(total_minutes - downtime_minutes) / total_minutes * 100",
          "frequency": "monthly",
          "responsible": "Infrastructure Lead",
          "target": ">= 99.5%",
          "warning_threshold": "< 99.5%",
          "critical_threshold": "< 99.0%"
        }
      ]
    },
    {
      "clause": "8",
      "label": "Resolution",
      "kpis": [
        {
          "id": "KPI-8.1",
          "name": "Mean time to resolve incidents",
          "description": "Average elapsed time from incident logging to resolution",
          "data_source": "ServiceNow",
          "calculation": "Average of (resolved_at - created_at) for all incidents in period",
          "frequency": "weekly",
          "responsible": "Service Desk Manager",
          "target": "<= 4 hours (P1), <= 8 hours (P2)",
          "warning_threshold": "Target + 25%",
          "critical_threshold": "Target + 50%"
        }
      ]
    }
  ],
  "capa_process": {
    "triggers": [
      "KPI critical threshold breach",
      "Internal audit nonconformity",
      "Recurring incident (3+ same root cause)",
      "Customer complaint"
    ],
    "id_format": "CAPA-NNN",
    "required_fields": ["description", "root_cause", "classification", "owner", "target_date", "status"],
    "closure_requires": "Effectiveness verification confirming metric returned to target"
  }
}

Extension Tools

monitoring_framework_validator

Validates monitoring-kpis.json for ISO/IEC 20000-1:2011 Clause 4.5.4.1 compliance. Run after writing the KPI data file.

Each finding reports ERROR or WARNING severity with a field reference and explanatory message.

Getting Started

Activate the ISO 20000 Monitoring and Measurement skill and describe your current SMS process areas and the tools you use for service management and monitoring. The agent will propose KPIs for each clause area and guide you through setting targets, defining measurement methods, and establishing the CAPA process.

Have this information ready:

• Your ITSM tooling (ticketing system, monitoring platform, CMDB)
• Current SLA targets and any existing metrics you track
• Known problem areas where you want tighter measurement
• Who is responsible for each process area (for assigning metric ownership)

The completed framework provides the measurement inputs for management review and connects threshold breaches to the CAPA register for systematic follow-up.