{"version":"0.2.0","built_at":"2026-10-10T20:58:14.188Z","license":"CC BY 4.0 © Mike Reams","canonical":"https://catalog.mikereams.com","capability":{"id":"BC-830","name":"Business Continuity & Crisis","level":1,"parent_id":null,"l1_id":"BC-830","industry":"cross-industry","macro_id":"MC-80","path":["Business Continuity & Crisis"],"description":"Keep the operations that matter running, or bring them back fast, when a site, a system, a supplier or a region fails, and lead the organization through the event with one voice.","aliases":["Business Continuity Management","BCM","Crisis Management","Resilience"],"in_scope":["Business impact analysis and recovery priorities","Continuity plans for sites, processes, people and suppliers","Crisis leadership, communication and emergency response coordination","Exercises, testing and the lessons they produce"],"out_of_scope":["Technology disaster recovery execution itself (see BC-730)","Enterprise risk framework and appetite (see BC-130)","Cyber incident response (see BC-760)"],"csdm_note":"Lands as one Business Capability record; recovery priorities should be carried as criticality on Business Services and the Business Applications beneath them, so the continuity plan and the CMDB agree on what matters.","status":"active","successor_id":null,"child_ids":["BC-830.10","BC-830.20","BC-830.30","BC-830.40","BC-830.50"]},"crosswalk":{"realized_by":[],"used_in":[],"patterns":[],"stacks":[],"books":[{"id":"BK-chaos-engineering","title":"Chaos Engineering","topic":"Delivery & DevOps","via":"BC-830.50"}]},"ancestors":[],"children":[{"id":"BC-830.10","name":"Business Impact Analysis","level":2,"child_count":3},{"id":"BC-830.20","name":"Continuity Planning","level":2,"child_count":4},{"id":"BC-830.30","name":"Emergency Response","level":2,"child_count":4},{"id":"BC-830.40","name":"Crisis Management","level":2,"child_count":4},{"id":"BC-830.50","name":"Exercising & Continuous Improvement","level":2,"child_count":4}]}