{"revision":"c10276e953456835cdbb1f3a60d58ae1980be353","document":{"id":16484,"path":"governance-risk-compliance/bcp-use-cases.md","title":"Use cases for business continuity planning","bundle":null,"doc_type":null,"release":"australia","body":"\n# Use cases for business continuity planning\n\nThis section describes the common use cases that are used for business continuity planning in the Business Continuity Management application. You can deploy these use cases individually or you can combine them to meet your specific needs.\n\nYou can build your business continuity plan based on your recovery strategy, partners, teams, tools, and processes that are needed to implement the plan.\n\nConsider an example of a malware attack on a corporation. The attack may disrupt critical services such as utilities, transportation, payments, and so on. If a business continuity plan is in place, the emergency IT consultants and professionals can implement preventive actions:\n\n-   Shut down the IT services.\n-   Restore the services from the disaster data recovery component in the plan.\n-   Control the damage by moving the essential data servers to an off-site location.\n\n## Use cases for planning\n\n<table id=\"table_agg_gq5_bcc\"><thead><tr><th>\n\nUse case name\n\n</th><th>\n\nDescription\n\n</th><th>\n\nRoles\n\n</th><th>\n\nActions for the use case\n\n</th></tr></thead><tbody><tr><td>\n\nCreate a standardized recovery plan\n\n</td><td>\n\nBCP helps you enact and mitigate risk at the time of an event by addressing action items such as plan assets, activities, recovery teams, documentation, policies, and procedures.\n\n The plan record goes through a cycle of states before:\n\n -   Draft -&gt; In review -&gt; Pending approval -&gt; Approved -&gt; Archived\n-   In the **Pending approval** state, plan can be rejected back to **Returned** state.\n\n</td><td>\n\nBCM planner, BCM manager, BCM administrator\n\n</td><td>\n\nUser creates a plan.\n\n</td></tr><tr><td>\n\nUpdate dependencies in the plan\n\n</td><td>\n\nUpdate dependencies in the plan: 1. Enables users to view and configure the assets that are affected within the plan.\n\n2. Monitor the RTO, RPO, and Recovery Tier of each asset and identify any gaps/risks when the asset is down.\n\n3. View the relationship of the primary assets and related assets.\n\n</td><td>\n\nBCM planner, BCM manager, BCM administrator\n\n</td><td>\n\nUser selects Update dependencies button.\n\n The Update BCP dependencies snapshot scheduled job is executed.\n\n</td></tr><tr><td>\n\nConfigure the dependencies for plan\n\n</td><td>\n\nProvide configurations for users to configure what dependencies they want for plans including:\n\n 1.  Configure the sources that they want to pull in from their dependencies including CMDB, BIA downstream, BIA upstream.\n2.  Choose whether they want to pull the last updated record or all records from the source.\n3.  Configure the users and groups that they want to notify via emails.\n4.  Configure the fields that are updated when dependencies are updated.\n5.  Configure what type of plans the configurations should be applied to.\n\n</td><td>\n\nBCM administrator\n\n</td><td>\n\nUser creates or updates records by navigating to\n\n All -&gt; Planning dependency update configuration.\n\n</td></tr><tr><td>\n\nCreate documentations\n\n</td><td>\n\nProvides a section and templates for the user to document the goals, objectives, and scopes that are required within the context of the plan.\n\n</td><td>\n\nBCM planner, BCM manager, BCM administrator\n\n</td><td>\n\nUser creates a plan using a plan template with document sections defined.\n\n User creates a section in the Documentation tab.\n\n</td></tr><tr><td>\n\nCreate recovery teams\n\n</td><td>\n\nDefines the teams responsible for executing the plans during the recovery process. It is used in recovery tasks.\n\n</td><td>\n\nBCM planner, BCM manager, BCM administrator\n\n</td><td>\n\nUser selects New button in the Recovery teams related list.\n\n</td></tr><tr><td>\n\nMonitor the loss scenarios of the plan\n\n</td><td>\n\nCreate crisis scenarios that can be included in your plan \\(for example, Loss of Datacenters or Vendor disruption\\). Then add assets dependencies or recovery strategies to the loss scenarios.\n\n</td><td>\n\nBCM planner, BCM manager, BCM administrator\n\n</td><td>\n\nUser creates a plan using a plan template with loss scenarios defined.\n\n User adds the loss scenarios.\n\n</td></tr><tr><td>\n\nSubmit for approval\n\n</td><td>\n\nCreate approval configurations including groups, users, or rules to standardize the approval process.\n\n</td><td>\n\nBCM planner, BCM manager, BCM administrator\n\n</td><td>\n\nUser submits the plan for approval.\n\n</td></tr><tr><td>\n\nGenerate PDF\n\n</td><td>\n\nSummarize the details of the plan \\(scopes, asset dependencies, related plans, recovery teams, recovery tasks\\) in a PDF format.\n\n 2. Enables users to write scripts and format the PDF through document templates, and document scripts.\n\n</td><td>\n\nBCM planner, BCM manager, BCM administrator\n\n</td><td>\n\nUser generates PDF of the plan.\n\n</td></tr><tr><td>\n\nCopy plan\n\n</td><td>\n\nCopy existing plans including their details and related lists.\n\n</td><td>\n\nBCM planner, BCM manager, BCM administrator\n\n</td><td>\n\nUser copies the plan.\n\n</td></tr><tr><td>\n\nAdd related plan\n\n</td><td>\n\nAdd the related plan to the related list.\n\n</td><td>\n\nBCM planner, BCM manager, BCM administrator\n\n</td><td>\n\nUser adds a related plan.\n\n</td></tr><tr><td>\n\nAvoid creating cyclic tasks for the same plan while adding plan dependencies.\n\n</td><td>\n\nStop processing same plan if it's already part of the hierarchy. Avoid creation such plan dependencies during planning phase. Verify that plan dependency in recovery task doesn’t create a cycle.\n\n</td><td>\n\nBCM planner, BCM manager, BCM administrator\n\n</td><td>\n\nUser adds an activated plan to the plan recovery task.\n\n</td></tr><tr><td>\n\nTask execution order\n\n</td><td>\n\nTasks under a plan can be parallel and sequential based on the task dependencies. Therefore, the tasks in a plan should be ordered.\n\n</td><td>\n\nBCM planner, BCM manager, BCM administrator\n\n</td><td>\n\nUser adds recovery tasks.\n\n</td></tr></tbody>\n</table>"}}