{"version":"0.2.0","built_at":"2026-10-10T20:58:14.188Z","license":"CC BY 4.0 © Mike Reams","canonical":"https://catalog.mikereams.com","value_stream":{"id":"VS-10","name":"Incident-to-Resolution","industries":["cross-industry"],"description":"From the moment a technology service degrades to the moment the people who depend on it are working again and the cause is understood — the stream that turns noise into a known, closed incident.","outcome":"The affected service is restored, the people affected know it, and the cause is recorded against the right Configuration Item.","trigger":"A monitoring alert, a service desk contact or an automated health check reports degraded service.","aliases":["Detect-to-Restore","Incident Lifecycle"],"stages":[{"id":"VS-10.10","order":1,"name":"Detect & Log","description":"Notice the degradation — from a person or a monitor — and record it once, against the service it affects.","capability_ids":["BC-740.20","BC-740.60","BC-730.60"]},{"id":"VS-10.20","order":2,"name":"Classify & Prioritize","description":"Decide what is affected, how badly and for whom, using the CMDB's picture of what depends on what.","capability_ids":["BC-740.20","BC-740.40"]},{"id":"VS-10.30","order":3,"name":"Diagnose & Restore","description":"Find the fastest safe route back to a working service, which is rarely the same as finding the root cause.","capability_ids":["BC-740.20","BC-720.60","BC-730.10"]},{"id":"VS-10.40","order":4,"name":"Communicate","description":"Keep the people affected and the people accountable informed while the service is down and when it is back.","capability_ids":["BC-740.60","BC-740.50"]},{"id":"VS-10.50","order":5,"name":"Close & Learn","description":"Confirm the restoration with the people affected, record the cause and hand anything structural to problem management.","capability_ids":["BC-740.20","BC-740.40","BC-740.50"]}]}}