ISO 20000-1 Design and Transition of New or Changed Services (Clause 5)

Example Conversation

You: We need to set up our design and transition process. We’re about to introduce a new cloud-based HR self-service portal for our 2,000 employees.

Agent: I’ll help you establish the design and transition process per ISO 20000-1 Clause 5. Let me start by loading any existing SMS context. I can see your service catalog and organization profile. Now let’s define the lifecycle for this process.

First, let me confirm the stages you want in your service design lifecycle. The standard requires at minimum: requirements gathering, design, testing, and go-live. Do you also want explicit development and transition stages?

You: Yes, we want all six stages. We also need a pilot phase before full rollout since this affects all employees.

Agent: Good. I’ll include a pilot stage between testing and full go-live. Now let’s define the design requirements that must be captured for every new service. For the HR portal specifically:

1. Functional requirements – what capabilities must the portal provide?
2. Non-functional requirements – performance targets (page load time, concurrent users)?
3. Availability – what uptime SLA is required?
4. Continuity – what’s the recovery time objective if the portal goes down?
5. Security – authentication method, data classification, access controls?

You: It needs to handle leave requests, payslips, and personal data updates. Page load under 3 seconds, support 500 concurrent users. 99.5% availability during business hours. RTO of 4 hours. SSO via our corporate Okta, personal data is classified confidential.

Agent: Now let’s establish the service acceptance criteria – the readiness checklist that must be satisfied before go-live. I’ll draft the checklist based on Clause 5 requirements and your context:

• Operational procedures and runbooks complete and tested
• Service desk staff trained on the HR portal
• Monitoring and alerting configured in Datadog
• SLA agreed with HR department as service owner
• CMDB updated with new configuration items
• Approved change request authorizes the go-live
• HR director has formally accepted the service

Does this cover your acceptance criteria, or do you need additional items?

You: Add data migration verification – we need to confirm employee records migrated correctly from the legacy system.

Agent: Added. Now I’ll define the transition planning requirements and document the process integrations with change, configuration, and service level management. Let me generate the process document and structured data file, then validate everything.

I’ll run the design_transition_validator now… All checks passed: lifecycle stages defined (7 stages including pilot), acceptance criteria documented (8 items), transition planning complete, and all three process integrations documented. Your Design and Transition Process is ready.

Sample Output Excerpt

The skill produces a structured JSON process definition and a markdown process document. Here is a representative excerpt from the JSON output.

{
  "lifecycle_stages": [
    "requirements",
    "design",
    "development",
    "testing",
    "pilot",
    "transition",
    "go_live"
  ],
  "triggers": [
    "new_service_request",
    "significant_service_change",
    "service_retirement"
  ],
  "design_requirements": [
    "functional_requirements",
    "non_functional_requirements",
    "capacity_requirements",
    "continuity_requirements",
    "security_controls",
    "sla_targets"
  ],
  "acceptance_criteria": [
    "Operational procedures documented and tested",
    "Service desk staff trained on new service",
    "Monitoring and alerting configured",
    "SLAs agreed with service owner",
    "CMDB updated with new CIs",
    "Approved change request authorizes go-live",
    "Stakeholder formal acceptance obtained",
    "Data migration verified"
  ],
  "transition_planning": {
    "resource_plan": true,
    "communication_plan": true,
    "training_needs": true,
    "support_readiness": true
  },
  "integrations": {
    "change_management": "Go-live requires an approved RFC; emergency changes follow the expedited CAB process",
    "configuration_management": "New CIs registered in CMDB during transition; relationships mapped to existing services",
    "service_level_management": "New or updated SLAs agreed and baselined before go-live"
  }
}

Extension Tools

design_transition_validator

Validates design-transition.json for ISO/IEC 20000-1:2011 Clause 5 completeness. Run after generating the design and transition process.

Each check reports PASS or FAIL with a detail message explaining what was found or what is missing.

Getting Started

Activate the ISO 20000-1 Design and Transition skill and describe the new or changed service you are planning. The agent will walk you through defining lifecycle stages, design requirements, acceptance criteria, transition planning, and process integrations.

Have this information ready:

• The service being introduced or changed and its business justification
• Performance, availability, and capacity requirements
• Security and continuity requirements
• Stakeholders who need to approve the service before go-live
• Integration points with your change, configuration, and service level management processes

The completed design and transition process feeds into change management authorization and provides the acceptance checklist used for every future service introduction.