---
title: Using Business Continuity Management
slug: solutions/using-business-continuity-management
docTags: 
createdAt: 2025-09-15T09:00:41.278Z
---

### Workspaces

**Utilities – BCM**

- Used for importing data records (Resources, BIAs, Solutions, Tasks, Threat Scenarios).

**Business Continuity Management**

- Daily BCM workspace.
- Applications include: Approvals, BIAs, Resources, Threat Scenarios, Incident Repository, Inventory - Solutions, Solutions, Inventory - Tasks, Tasks, Unavailability Scenarios, and Documents.
- Provides dashboards for both program-level and owner-level views.

### Application Records

Application Records are the data structures that power BCM. They establish relationships between business processes, resources, continuity plans, incidents, and approvals.

**Resources**

Represents assets (applications, buildings, suppliers, equipment, infrastructure, etc.).

**Business Impact Assessments (BIAs)**

Determines criticality of processes and defines recovery objectives. Includes **Initial Pre-Screening** and the **full BIA workflow** for Critical processes.

**Inventory – Solutions**

Continuity and contingency plans linked to BIAs and Threat Scenarios.

**Inventory – Tasks**

Step-level actions tied to continuity plans.

**Threat Scenarios**

Risks that may disrupt business operations (for example, cyber, human, natural, technical).

**Incident Repository**

Central record of continuity-related incidents.

**Approvals**

Workflow records for BIA validation.

**Inventory – Documents**

Supporting documentation linked to other records.

**Unavailability Scenarios**

Scenarios describing when critical resources are unavailable.

### How Records Work Together

- **Resources** are mapped to BIAs.
- **BIAs** link to Resources, Solutions, Tasks, and Threat Scenarios.
- **Approvals** validate BIAs.
- **Inventory - Solutions** and **Inventory - Tasks** define how continuity objectives are achieved.
- **Solutions** and **Tasks** are working records where outcomes to continuity tests are recorded.
- **Threat Scenarios** provide risk context.
- **Incidents** consolidate BIAs, resources, and documents during disruptions.

This ensures end-to-end traceability from **process definition → impact assessment → approval → continuity planning → incident response**.