Page 18 - TNR-V01N1
P. 18

Scenarios                                             Work Instructions
        As part of the Disaster Recovery Framework,           Work Instructions are very detailed instructions on
        scenarios become the structured approach to a         the actual recovery steps for a specific application
        specific Disaster Recovery Plan.                      and/or component. This is the knowledge base to
                                                              recovery from a component element all the way up
        The format of each scenario is consistent to provide   to larger application functions. They may be a small
        for improved success while executing the specific     or a very large document that is to be followed.
        plans.
                                                              The instructions should be very complete and NOT
        The major areas of each scenario are;                 rely on internal undocumented knowledge. These
          • Description – A brief description of the event    Work Instructions are reusable across many Disaster
          • Scope – The definition of what is in and          Recovery Plans for they are specific to applications
            potentially out of scope for the event.   This    and components.  By leveraging a consistent
            allows for containment for the recovery plans.    method for these technical instructions, fewer errors
          • Impacted areas – This is a comprehensive list     are encountered, and a higher level of repeatable
            of all applications and/or components involved    success is observed.
            in the scenario.  Similar to scope but specific to
            applications and components.                      The work instructions are potentially used frequently
          • Impacted clients – Who are the stakeholders,      by operations outside of a recovery process. These
            action item holders, consulted with groups,       instructions need to be complete so the individual
            informed groups both at the business and          using the instructions has all they need to complete
            technical areas.                                  the task.
          • Resources – Who are the resources both
            internal and external required to complete the
            plan.
          • Recovery Overview – This is the high-level        Recovery Flow
            description of the major checkpoints during a     The recovery flow is as follows.
            recovery plan.                                      • BCP deals with the business
          • Major recovery stages (Project Plan) – This is      • DRF is the process to follow
            a breakdown of phases with associated tasks         • DRPs is the actual execution plan to follow
            to be completed by the plan.  It may or may not     • Work Instructions are the actual instructions to
            refer to technical recovery plans.                    be followed
          • Recovery success determination – What is the
            definition of success as it relates to the recovery.
                                                              Conclusion
        Disaster Recovery Plans                               Plan the work and then work the plan.  Your plan
        The Disaster Recovery Plan is the actual plan to      is the guide to follow. The plan will likely need to
        follow wrapped in a specific communications plan.     change during the execution but not the need
                                                              to have one. The Disaster Recovery Framework
        Typically, this is a formal document, but it can      provides a process to follow to ensure all the needs
        also be a digital tool that lays out the plan to be   of the business and its stakeholders are accounted
        executed along with a communication plan to keep      for during a recovery event.                ■
        all stakeholders informed and engaged. I am a firm
        believer the plan should be digital and in the cloud.
        That way it is always current and accessible and
        more importantly, it can be audited.                                                    Tim Lalonde
                                                              Tim Lalonde is the VP of Technical Operations at Mid-
        The contents of a plan may look like the following.      Range. He works with leading-edge companies to
          • Control                                            be more competitive and effective in their industries.
          • Introduction                                          He specializes in developing business roadmaps
          • Systems and applications                                leveraging technology that create and support
          • Execution Plan                                         change from within — with a focus on business
              o Milestones                                        process re-engineering, architecture and design,
              o Work Instruction(s) to be followed                business case development and problem-solving.
          • Contact List                                       With over 30 years of experience in IT, Tim’s guiding
          • Teams                                                   principle remains simple: See a problem, fix a
          • Results and Findings                                                                    problem.


           18
                                                                   True North RESILIENCE magazine - Fall 2022
   13   14   15   16   17   18   19   20   21   22   23