Plan Development P of Incident Management Framework

(This is Part 3 of a multi-part blog examining the “4Ps” of Incident Management Framework)

The previous blog in this series focused on Planning.  One of Planning’s critical outcomes should be identification of critical products and services – and what strategies are likely to successfully restore or resume each service. In their simplest terms, Plans are the implementation of those strategies.

  • The goal of every plan should be the efficient and predictable resumption of a disrupted service.
  • Plans should be a single source of reference for responders to act upon in response to any business disruption.
  • Plans should be a concise, unambiguous sequence of tasks. During execution, individual tasks can be monitored for status and execution of the plan can be managed.
  • Tasks should be documented, tested and approved.
  • Plans should facilitate collaboration and foster dissemination of vital information to all interested stakeholders: Incident Managers, Recovery Teams, Product/Service owners, Business Process managers, and Executive managers (and anyone else appropriate).
  • Plans should be reviewed & updated periodically to ensure that are both current and viable

Plan completion shouldn’t just be a checkbox on a BCM audit or standards list.  A ‘standardized’ plan outline could make review and audit easier, but a fill-in-the-blanks form – or a checklist – will never be effective enough to assure a successful recovery.

Part 4 of this series will look at Incident Management Framework 3rd P – Preparedness.

SHARE:
Ramesh Warrier

Ramesh Warrier

eBRP Founder and Chief Designer of eBRP Suite, Ramesh is a proponent of constant change, a visionary who believes that the practice of Business Continuity can deliver improved operational efficiency. Ramesh, B.Tech in Electrical Engineering, has nearly 30 years experience in Business & Technology roles. His thoughts are expressed in blogs, white-papers, frequent webcasts and speaking engagements at industry conferences.

Related Posts

Enterprise Resiliency: Navigating Through Disruptions

Enterprise Resiliency: Navigating T...

In today’s threat landscape, the ability of an organization to…
Orchestrating BC/DR Testing: Virtual – Emergency Operations Centers

Orchestrating BC/DR Testing: Virtua...

  Enhancing Planning and Logistics Management  Coordinating BC/DR tests involves…
Insights into creating a successful Disaster Recovery Test – Part 2: Preparation

Insights into creating a successful...

Insights into creating a successful Disaster Recovery exercise – Part 1: Objectives

Insights into creating a successful...

Aligning Cyber Incident Response Planning with Your BC/DR Program

Aligning Cyber Incident Response Pl...

Cyber disruptions – and their impact on both reputations and…
What Can You Do when your BCM software Relationship Falls Apart

What Can You Do when your BCM softw...

“This isn’t working.”  “I’ve changed.”  “I don’t see a future…
Aligning BC/DR to CSIRP Challenges

Aligning BC/DR to CSIRP Challenges

The immediate reaction to a cyber-security incident is the FUD…
Technology Modeling – the eBRP Way

Technology Modeling - the eBRP Way

Definition: Technology modeling is a point-in-time snapshot of an Enterprise’s…
eBIA – The eBRP Way

eBIA - The eBRP Way

Definition: A Business Impact Analysis (BIA) is the cornerstone of…
Threats, Impacts, BCPs

Threats, Impacts, BCPs

Within Business Continuity circles there is ongoing debate about the…