Sunday, December 14, 2008

BUSINESS CONTINUITY PLAN COMPONENTS DOC

BUSINESS CONTINUITY PLAN COMPONENTS

DOC

Date Filed:
Contact Name:
Phone:
E-Mail:
Fax:

  1. Business continuity Planning Outline
  2. Business continuity Plan Template
  3. Business continuity Plan Worksheets

  • Checklist
  • Business Action Template
  • Recovery Procedures Template
  • Accident Assessment Worksheets

Written by:________________Date:___________________

Written by:________________Date:___________________


I. Business continuity Planning Outline

Phase One

• Analyze Current Mission-Critical Business Processes (See Operations Plan for starting

point)

• Appraise Appulse or Importance of Business Processes, considering:

  1. Health and Public Safety
  2. Revenue or Cash Flow
  3. Number of Citizens, Businesses, or Employees Impacted
  4. Federal Reporting Requirements
  5. Public Perception

• Analyze Assets and Dependencies

• Evaluate Accident or Likelihood of Failure

Application Systems and Interfaces

IT Infrastructure

Third Party Products

Embedded Chips

Supply continuity

Infrastructure (Facilities, Telecom, Utilities)

• Authorize Antecedence Based aloft Appulse and Risk

Phase Two

• Develop Business continuity Plan Based aloft Available Assets and Time

• Make Assumptions to Focus Plan

• Devise Alternatives to Complete Core Business Processes, considering:

Roles & Responsibilities

Communication Channels

Manual Workarounds

Triggering Events

Who Invokes the Plan

Required Training & Preparation

How & Who Maintains the Plan

Needed Food & Equipment

Additional Staffing Needs

What Ends the Plan

Clean-Up

• Analysis for Completeness

Phase Three

• Exercise the Plan

• Make Modifications as Needed



II.Business continuity Plan Template

The afterward sections are included in a Accident Plan Template. It is a sample template, therefore,

sections may be added or deleted as appropriate.


PROCESS:

• Accommodate the name and a abrupt overview of the analytical business action as it currently exists.

PRIORITY:

• Actuate the antecedence of this accident plan about to the added accident plans, if multiple

failures action aural an organization. Use this breadth if applicable.

RISK DESCRIPTION:

• Describe in simple agreement the accident affair and the appulse to the organization. Cover the nature

and likelihood of accepted disruptions or impacts.

For example:

-

Electrical ability is unavailable. If processing cannot be resumed aural 3 days, client

checks will be late.

• Describe briefly any cogent dependencies or linkages of the business action with programs

within the organization, with added organizations, or with added parties either central or alfresco of

state government.

• State absolutely any assumptions, which your alignment is authoritative in this accident plan.

MITIGATING STRATEGIES:

• Accommodate a abrupt conceptual description of how the accident plan for the business action is

intended to work.

For example:

-Conduct added superior affirmation analysis of abstracts above-mentioned to mailing.

-Set up annual in beforehand with alternating supplier(s) and authorize procedures for using

the alternating supplier.

-Investigate achievability and amount of an uninterruptible ability supply.

• Describe the akin of casework to be provided during the disruption.

For example:

-

Provide assiduity of accustomed operations.

- Provide assiduity of account in a base mode.

- Provide complete abandonment from accustomed functions as bound and cautiously as possible.

ACTIVATION TRIGGER(S):

• Describe the specific contest or altitude that will activate or adjure the plan.

For example:

- Employees can’t admission architecture admission via cyberbanking admission cards.

RECOVERY PROCEDURES:

• Describe the accepted activity or continuance of the accident plan.

For example:

- How continued it ability be all-important to accomplish beneath the plan.

- Any adapted timing-related constraints, e.g., aback batteries charge re-charging afterwards 10

hours.

• Accommodate detailed, step-by-step procedures for initiating and active accident operations,

and for transitioning aback to accustomed (non-contingency) operations with the names of the persons

who are to serve specific roles apropos the plan.

For example:

- Initiate centralized and bell-ringer account notification procedures – Responsibility: Ms. X

- Get advancement listings from off-site accumulator – Responsibility: Mr. Y

- Contact alternating supplier to accommodate bare food – Responsibility: Ms. Z

IMPLEMENTATION:

• Name BCP Coordinator and Team

• Accommodate the name and acquaintance advice of the being who will accord the adjustment to adjure the

plan.

• Accommodate the name of the being who will accord the adjustment to acknowledgment to accustomed operations.

• Accommodate a abrupt description of cogent assets bare to implement, execute, and transition

out of accident operation. Also analyze the being who is amenable for accepting these

resources, as contest may warrant.

For example:

- Staffing and scheduling of personnel.

- Equipment, acting accouterments and software, forms and supplies, etc.

-Possible acting alive facilities.

Communications, both exact and data.


• Accommodate a abrupt description of any training or appliance of the plan that will be necessary.

For example:

- Perform a structured walk-through to ensure that all the processes will plan as expected.

- Perform an exercise or “dry-run” to ensure that all the processes work.

-Perform a “mock” exercise with adapted agents and vendors on a non-work day.

• In continuity planning, the aliment action ensures that humans and action aspects of the plan

which charge added plan are appropriately addressed and corrected.

• The afterward types of aliment should be conducted for every business continuity plan in your

organization:

  • o Scheduled
  • o Unscheduled
  • o Post exercised



III. BUSINESS CONTINUITY PLANNING WORKSHEETS

A. Checklist

B. Business Action Template

C. Recovery Procedures Template

D. Accident Assessment Worksheets

Page 7

Page 7 of 11

COMPONENTS OF A CONTINGENCY PLAN

CHECKLIST

Checklist

Components

ORGANIZATION:

Organization Name *

PROCESS:

Business Action Name *

Business Action Overview

PRIORITY:

Priority aural organization

RISK DESCRIPTION:

Risk Description

Impact of Accident on Organization

Nature and likelihood of disruptions

Dependencies aloft business process

Assumptions

MITIGATING STRATEGIES:

Mitigating Strategies description

Level of account to be provided

ACTIVATION TRIGGER(S):

Activation Trigger(s) *

RECOVERY PROCEDURES:

Duration of accident plan

Recovery Procedures/Work-Around *

Responsible being for anniversary action

IMPLEMENTATION:

Person invoking plan

Person acclimation acknowledgment to accustomed operations

Resources Adapted *

MAINTAINING/EXERCISING PLAN

  • Training Required
  • Exercising Required
  • Person amenable to access resources
  • Maintenance Required



Business Action XYZ CONTINGENCY PLAN

Process:

Priority:

Risk Description:

Mitigating Strategies:


RECOVERY PROCEDURE ACTION PLAN


Recovery Procedures (Action Plan):

Duration:



Procedures

Responsibility


  1. Implementation:
  2. Person Responsible:
  3. Invokes Plan:
  4. Return to Accustomed Operations:
  5. Resources Required:

(Staff, supplies, etc.)

Training Required: Completed: ___ / ___ / ________

Sample Accident Assessment Worksheet

Purpose and Directions

Purpose:

This worksheet is advised to accommodate a framework for answering the afterward questions for a particular

business process:

1. Where could a abeyant abortion occur?

2. Does it appulse this business process? If so, how much?

3. What has been done or is in advance to abate the blackmail of a failure?

Based on the answers to the aloft questions:

4. What is the actual risk?

By answering the endure question, you should be in a bigger position to focus your accident planning

efforts, decidedly which business processes are a lot of in charge of accident planning and what specific

failures do the accident affairs charge to abode and at what akin of detail.

Directions:

1. Accept a accurate business process.

2. Analysis the areas of affair to actuate if any charge to be added or broadcast aloft that are specific

to the business process. Modify spreadsheet as appropriate. Note: the Remediation or Mitigation

Status Values are stored in columns E-I, which are hidden.

3. For anniversary breadth of concern, accredit a akin of annex of High, Medium, Low, or Not Applicative (or

blank).

4. Accept from the drop-down account of choices for the Remediation or Acknowledgment Status. This information

will a lot of acceptable appear from the individuals aural your alignment that are amenable for status

reports. If the choices do not appropriately reflect your status, blazon in your own cachet description.

5. Based on the akin of annex and the remediation or acknowledgment status, appraise the actual risk

and accredit a amount of High, Medium, or Low. Alternatively, you may accept to animadversion on your

analysis rather than accredit a specific akin of risk.

6. Once you accept bent the accomplished actual accident areas, focus your Accident Planning initiative

to abode the accident areas. This would cover which business processes charge accident plans, how

detailed the affairs should be, and which areas should be addressed a lot of fully.



RISK ASSESSMENT WORKSHEET

Department/Division:

Business Process:

Areas of Concern*

Level of

Dependency

(H/M/L or N/A)

Remediation or

Mitigation Status

Risk Assessment

(H/M/L or Other

Analysis)

APPLICATION SYSTEMS


Hardware

Operating System

Third Party Software

Utilities/Macros

Date-Impacted Custom Source Code/JCL

Internal Interfaces

External Interfaces (Banks, Feds, Added NC)

Shared Data

Data Communications/Network

PC/LAN

Hardware

Operating System

Third Party Software

COMMUNICATIONS

Telephone Switches

Voice Mail

Voice Response Units

Automatic Call Distributors

Cell Phones

Pagers

Fax

FACILITIES

Power

Water/Sewer

Fire Alarm Systems

Security Systems

HVAC Control Systems

Parking Control Systems

DEPENDENCIES

Application Interfaces

Hardware Infrastructure

Vendor Support

No comments: