Need help with Disaster Recovery homework

User Generated

zrrrm

Computer Science

Description

Hello, 

I need some help with my assignment, but please, a few sentences each is not going to work!

"Enter and surf the term “Disaster Recovery Testing Services” in search and find 3 companies that provide those services/tools, then answer/evaluate 

(A) what are some of the tools/services being offered?

(B) what are the benefits of using these outside services versus in-house, how effectively can they be?

(C) after reviewing these templates (Business Continuity Test Template, BCP-template, T-BC8000-exercise-template, DR7000-test-lessons-learned & F-DR7000-test-objectoves-by-team) what are the key components, what’s their value, usefulness for the organization?

BCP-template.docx 

Business Continuity Test Template.doc 

DR7000-test-lessons-learned.docx 

F-DR7000-test-objectoves-by-team.docx 

T-BC8000-exercise-template.docx 

 "

Thanks!



Unformatted Attachment Preview

M-Pathways Business Continuity Plan Sunday, May 05, 2019 2 Business Continuity Plan Save Date: May 5, 2019 Application System: Plan Description Process Name(s) 1. 2. Process Description(s): 1. (Describe the Business Process for which this plan is developed.) Plan Locations: 1. (Describe the location where the plan document is physically kept; and the location from which the plan will be executed. Include backup locations where necessary.) Statement of Impact(s): 1. (Enter descriptions of effects this process has on University concerns, such as finances, regulatory requirements and U-M reputation or image.) Summary of “Input” Dependencies: 1. (List other business processes, offices and/or functions on which each process relies.) Summary of “Output” Dependencies: 1. (List other business processes, offices and/or functions that rely on the results of each process.) C:\Users\cloudconvert\server\files\119\125\9\520b8713-c135-4431-bfa5-3832c92353fe\20151026222739bcp_template.docx Page 2 of 6 3 Business Continuity Plan Save Date: May 5, 2019 Advance Planning Readiness Checklist Tasks Responsible Role How often 1 2 3 4 5 6 7 8 9 10 C:\Users\cloudconvert\server\files\119\125\9\520b8713-c135-4431-bfa5-3832c92353fe\20151026222739bcp_template.docx Page 3 of 6 How When Last Done 4 Business Continuity Plan Save Date: May 5, 2019 Contingency Plan: Conditions and Assumptions (Describe the situation and circumstances of the scenario(s) for which this contingency plan applies. Create multiple plans for varying conditions as needed. Add to or change the prompts listed as needed.) Outage Duration Personnel Availability Business Cycle Worksite Facility Condition Equipment Availability Telecommunications Availability Task / Process Step Responsible Role (Describe manual work around processes and other contingencies step-by-step to be followed in the event ITS systems are unavailable. Include: customer support options, printing options, reports needed, hard copy reports, any special reports, agreement with vendors: banks, suppliers of checks etc., extra equipment/supplies, special forms, saving information, offsite storage) Time to Execute (Estimated time to execute the step from start to finish) 1 2 3 4 5 6 What to do when the outage is over 1 2 3 4 5 6 C:\Users\cloudconvert\server\files\119\125\9\520b8713-c135-4431-bfa5-3832c92353fe\20151026222739bcp_template.docx Page 4 of 6 Responsible Role Time to Execute 5 Business Continuity Plan Save Date: May 5, 2019 Appendix A: Contact List Name Role Work Phone Number Home Phone Number Email C:\Users\cloudconvert\server\files\119\125\9\520b8713-c135-4431-bfa5-3832c92353fe\20151026222739bcp_template.docx Page 5 of 6 Work Unit / Department Home Address 6 Business Continuity Plan Save Date: May 5, 2019 Appendix B: Revision History and Signoff This version approved by: Printed Name: ___________________________________ Title ___________________________________________ Signature _______________________________________ Approved on: Date ___________________ Revision History Document / Version Revision Description C:\Users\cloudconvert\server\files\119\125\9\520b8713-c135-4431-bfa5-3832c92353fe\20151026222739bcp_template.docx Page 6 of 6 Approval Source Approval Date M-Pathways Business Continuity Plan Sunday, May 05, 2019 2 Business Continuity Plan Save Date: May 5, 2019 Application System: Plan Description Process Name(s) 1. 2. Process Description(s): 1. (Describe the Business Process for which this plan is developed.) Plan Locations: 1. (Describe the location where the plan document is physically kept; and the location from which the plan will be executed. Include backup locations where necessary.) Statement of Impact(s): 1. (Enter descriptions of effects this process has on University concerns, such as finances, regulatory requirements and U-M reputation or image.) Summary of “Input” Dependencies: 1. (List other business processes, offices and/or functions on which each process relies.) Summary of “Output” Dependencies: 1. (List other business processes, offices and/or functions that rely on the results of each process.) C:\Users\cloudconvert\server\files\119\125\9\7f40bbc6-d7d5-4f95-ba57-a39e5e8bcb97\20151026222814bcp_template.docx Page 2 of 6 3 Business Continuity Plan Save Date: May 5, 2019 Advance Planning Readiness Checklist Tasks Responsible Role How often 1 2 3 4 5 6 7 8 9 10 C:\Users\cloudconvert\server\files\119\125\9\7f40bbc6-d7d5-4f95-ba57-a39e5e8bcb97\20151026222814bcp_template.docx Page 3 of 6 How When Last Done 4 Business Continuity Plan Save Date: May 5, 2019 Contingency Plan: Conditions and Assumptions (Describe the situation and circumstances of the scenario(s) for which this contingency plan applies. Create multiple plans for varying conditions as needed. Add to or change the prompts listed as needed.) Outage Duration Personnel Availability Business Cycle Worksite Facility Condition Equipment Availability Telecommunications Availability Task / Process Step Responsible Role (Describe manual work around processes and other contingencies step-by-step to be followed in the event ITS systems are unavailable. Include: customer support options, printing options, reports needed, hard copy reports, any special reports, agreement with vendors: banks, suppliers of checks etc., extra equipment/supplies, special forms, saving information, offsite storage) Time to Execute (Estimated time to execute the step from start to finish) 1 2 3 4 5 6 What to do when the outage is over 1 2 3 4 5 6 C:\Users\cloudconvert\server\files\119\125\9\7f40bbc6-d7d5-4f95-ba57-a39e5e8bcb97\20151026222814bcp_template.docx Page 4 of 6 Responsible Role Time to Execute 5 Business Continuity Plan Save Date: May 5, 2019 Appendix A: Contact List Name Role Work Phone Number Home Phone Number Email C:\Users\cloudconvert\server\files\119\125\9\7f40bbc6-d7d5-4f95-ba57-a39e5e8bcb97\20151026222814bcp_template.docx Page 5 of 6 Work Unit / Department Home Address 6 Business Continuity Plan Save Date: May 5, 2019 Appendix B: Revision History and Signoff This version approved by: Printed Name: ___________________________________ Title ___________________________________________ Signature _______________________________________ Approved on: Date ___________________ Revision History Document / Version Revision Description C:\Users\cloudconvert\server\files\119\125\9\7f40bbc6-d7d5-4f95-ba57-a39e5e8bcb97\20151026222814bcp_template.docx Page 6 of 6 Approval Source Approval Date – Document Name BUSINESS CONTINUITY TEST TEMPLATE By Paul Kirvan, FBCI, CBCP, CISSP BUSINESS CONTINUITY TEST TEMPLATE Date ________ Revision __ Revision History REVISION DATE NAME Confidential – Property of All Rights Reserved, 2009, TechTarget DESCRIPTION 1 – Document Name TABLE OF CONTENTS 1 PURPOSE OF THIS DOCUMENT 3 2 DOCUMENT CHANGE CONTROL HISTORY 3 3 PRE-TEST 3 3.1 3.2 4 4 SCOPE OF TEST EXECUTION SCENARIO: INSTRUCTIONS TO PARTICIPANTS COMMUNICATIONS DIRECTORY MESSAGES 4 5 7 8 8 PARTICIPANTS 5.1 5.2 5.3 5.4 5.5 5.6 5.7 5.8 5.9 5.10 5.11 5.12 6 3 3 TEST 4.1 4.2 4.3 4.4 4.5 5 TEST PLANNING BACKGROUND PRE-TEST PLANNING MEETING(S) 10 TEST FACILITATOR TEST ASSISTANT TEST DESIGN TEAM SIMULATION TEAM MEMBERS TEST EVALUATORS TEST PARTICIPANTS THE TEST BRIEFING THE TEST DEBRIEFING WRITTEN EVALUATIONS WRITTEN REPORT KEYS TO A SUCCESSFUL TEST SUGGESTED TEST SCHEDULE 10 10 11 11 12 13 14 14 14 14 15 15 TEST/DEBRIEF SUMMARY 6.1 6.2 6.3 15 WRITTEN EVALUATION RESPONSES VERBAL EVALUATION RECOMMENDATIONS FOR IMPROVEMENT 15 16 16 7 APPENDIX A – GLOSSARY 18 8 APPENDIX B – RECORD OF TEST PLANNING MEETING(S) 20 Confidential – Property of All Rights Reserved, 2009, TechTarget 2 – Document Name 1 Purpose of this Document The purpose of this test document is to facilitate test planning, test execution, test review, and corrective action to plans developed for location(s). This document can be considered a “baseline” throughout the phases of the exercising process, independent of the type of exercising being performed. 2 Document Change Control History This document will be updated as necessary throughout the course of pre-test planning, test execution, and post-test review. Enter the version, issue, date issued and description of the document. The version number (left-most digit) indicates the phase of the test report document (1=Pre-Test 2=Test, 3=Post-Test, 4=Final-Report). The issue number (right-most digit) will be incremented by one whole digit if there is a need to re-issue this document due to a major change or update within a phase. Version and Issue Date Issued (MM/DD/YYYY) Phase and Version Description 1-1 Pre-test version of this document, for use during pre-test planning meeting(s) 2-1 Test version of this document, for use during exercising 3-1 Post-test version of this document, for use at the post-test review meeting(s) 4-1 Final version of this document, with a completed corrective action plan 3 Pre-Test 3.1 Test Planning Background This test is in support of the test program for 2009. 3.2 Pre-Test Planning Meeting(s) Pre-test planning meeting(s) must be scheduled sufficiently in advance of the desired exercising date for the specific BC plan(s) of interest. Confidential – Property of All Rights Reserved, 2009, TechTarget 3 – Document Name The business continuity professional with overall responsibility for the content of the given plan should chair the pre-test planning meeting(s). Select planners (e.g., the Test Planning Team) and any other parties deemed necessary for the construction of the desired type and scope of BCP test should attend pre-test planning meetings. The meeting(s) may be conducted face-to-face, by teleconference, or by other electronic means (e.g., e-mail, net meeting). 4 Test 4.1 4.1.1 Scope of Test Scheduled Date and Time of Test Start Date/Time 4.1.2 Finish Date / Time Type of Test Highlight Box Indicating Test Being Conducted Orientation Test Drill Tabletop Test Functional Test Full Scale Test 4.1.3 Plans to be tested BC Plan Name(s) 4.1.4 Scope of Execution Test Goals Enter a brief and clearly stated goal of what you want the test to accomplish. Test goals and objectives drive the test and keep the process on track. Goal(s) Confidential – Property of All Rights Reserved, 2009, TechTarget 4 – Document Name 4.1.5 Test Objectives Clear, measurable objectives should be defined here. Write at least 3-5 overall objectives. There may be additional objectives for a specific function of the Local Incident Response Team, a department or location. 4.1.5.1 Objectives Defined • Establish the direction of the test • Control the direction of the messages • Narrow the scope of the test plan • Keep the test and participants on track • Are used to evaluate the test • Help to identify follow-up needs, improvements and to-do lists 4.1.5.2 Writing Objectives • Simple • Concise • Measurable • Achievable • Realistic and challenging • Task-oriented (oriented to specific business functions) Objectives 4.2 Execution Scenario 4.2.1 Test Basic Premises Equipment, procedures, standard operating procedures or conditions needed to conduct the test but exist only for the purpose of the test need to be defined here. Examples: • The weather is hot and humid and temperatures will exceed 100 degrees. • Change the date, the time, and put people on vacation and make them not available. • The only valid phone numbers are those listed in the communications directory. No. Test Basic Premises 1 2 3 4 Confidential – Property of All Rights Reserved, 2009, TechTarget 5 – Document Name 4.2.2 Test Execution Assumptions Design criteria that further define the scope of the test by placing assumed limits on the participants are described here. These answers address questions that often hold up the test. Examples: • The city will be isolated for 24 hours. • The telephone systems are operating normally. • All employees who are “supposed to come to work” show up. No. Assumptions 1 2 3 4 4.2.3 Test Scenario The event or incident scenario for this test can be as simple as a basic technology disruption or as complex as a simulated, major crisis event. • • • • • • • • • • • • • • • This section prepares participants for the test This is the overview of the event, the beginning of the process Describe the environment at the time of the test Provide necessary background information Launch the event – is it realistic? Discovery – how do you find out? Details: time, location, extent of damage Sequence of events Initial damage report, if possible Weather conditions Where are we in the timeline of response and recovery? Who is missing? Who is there? Are there injuries? Fatalities? What communication has taken place? Leave nothing to assume – this just creates chaos with the participants Example: “A major earthquake struck at 9am. The epicenter has not yet been determined. Electrical power and phones are out. Your emergency generator did not turn on. The shaking was severe, causing glass breakage and furniture to topple. You hear moans and screams of fellow employees. You do not know the status of your building or the city.” Confidential – Property of All Rights Reserved, 2009, TechTarget 6 – Document Name Planned Date & Time Seg Actual Date & Time Message Content Delivery Method Delivered By A B C D E F G H I J K L M N O P Q R S T U V W X Y Z 4.3 Instructions to Participants Describe here what you expect of the test participants. Explain decisions and actions to simulators as if they were the “real” people. Simulators are reality (e.g., Imagine if you will…). Explain that the test is not a “fault-finding” activity. Explain time outs – and how that would work. Also discuss the fact that there will be mistakes. Be sure to note that the more mistakes, the better, as learning comes from making mistakes. Example: • This is a training test designed to assess existing plans and procedures as a tool to manage a corporate headquarters response. It is understood that plans are always evolving and are not “perfect”. Questions regarding the test should be directed to the test facilitator. • The test design team has designed the situations to be as realistic as possible. If we have missed the mark, work through the problem to the best of your ability. The value is in the process, the dialogue, and the experience. • Actions and decisions should be consistent with your existing plans. • Stay in the role the entire time. Don’t get into the future; stay in the moment. Confidential – Property of All Rights Reserved, 2009, TechTarget 7 – Document Name 4.4 Communications Directory The directory should be published separately, and included here. It should contain the phone numbers, fax numbers, and/or email addresses of those with whom the participants are likely to have to call. These numbers, of course, will be for phones in the Simulation Room. This closes the communication loop. Don’t forget to assign the Jack and Jill of all trades. The directory is the last piece to be done prior to the test. Name Cell Phone Number Team members Call Trees Vendors Others 4.5 4.5.1 Messages Messages drive the test, expose unresolved issues, and address the objectives. They add information to describe the disaster environment and/or situation. Messages stimulate action by the participants. Messages can escalate an initial (primary) problem and create secondary or tertiary problems. Example: • Primary event – earthquake • Second event – building collapse • Tertiary event – building fire Messages should influence action at least one of four ways • Verification – information gathering • Consideration – discussion, consultation • Deferral – place on a priority list • Decision – deploy or deny resources Confidential – Property of All Rights Reserved, 2009, TechTarget 8 – Document Name 4.5.2 Message component examples • Time – what time is it to be delivered within the test? • Who – who is the source of the message? • Mode – how was the message transmitted? • To Whom – who is the recipient? • What – is the content of the message? • Acting tips – helpful to note expected action/reaction and acting tips 4.5.3 Message sources • Pre-scripted messages provide the story line of the test; they also deliver or announce important information • Incident response team members • Simulators in an effort to stress a particular issue 4.5.4 Message delivery • Phone • Two-way radio • Fax • Email • Radio broadcast • Video • Runner • Actor playing a role 4.5.5 Message examples • “This is the security guard at the main desk. There is a strong smell of gas in the lobby. What should I do? • “This is the floor warden on the 22nd floor. Employees are asking if they should go home or stay. Is there any food or water here at work if we have to spend the night? 4.5.6 Message tracking • Keep messages and related test information on a spreadsheet so that you can sort them by location, date, time, or type of event • Have 4-5 key messages that speak directly to the objectives that you will have passed by the evaluators and simulation room for resolution • If messages are not adequately or properly resolved, keep the message alive • Note key messages on the spreadsheet by using bold font. Confidential – Property of All Rights Reserved, 2009, TechTarget 9 – Document Name 5 Participants 5.1 Test facilitator The test facilitator must be familiar with the BC plan being tested, ideally independent of both the BC plan developers and standing team members. The facilitator coordinates the test’s execution scenario and provides spontaneous input to the test. This helps plan execution throughout the test scope. The facilitator is in charge of all test elements, provides oversight to the process, and is the final arbiter. Test Facilitator Name 5.1.1 5.2 On Test Day • Review all the major points – timelines, key messages, contact information at all facilities • Have an assistant if possible • Cell, pager and landline numbers should be available to reach you • Facilitators should not get into active problem solving; their job is to delegate and encourage the participants Test Assistant A test assistant supports the facilitator, especially during large and complex tests. Test Assistant Name 5.2.1 On Test Day • Name cards need to be distributed to those who cannot participate until later • Radio announcements (and other audio/video media) need to be planned and recorded in advance and cued for playback • Have lunch available at 11:30 am and brought into the room before 11:45 • Check in with the facilitator frequently • Play any media as required in the test plan, e.g., video, radio broadcast. • Hand out the participant evaluations • Assist with the debriefing Confidential – Property of All Rights Reserved, 2009, TechTarget 10 – Document Name 5.3 Test Design Team The following individuals are involved in designing and planning the test: Design Team Members 5.4 Simulation Team Members Design team members make great simulation team members. In-depth knowledge of the organization and departments being tested is a key requirement. STMs should have a positive good attitude and good acting skills. They need to be able to produce “credible scenarios” and yet stay on course with the test plan. Most of all they need to be team players. Simulation Team Members 5.4.1 Simulation Team Guidelines • Know the test plan and the messages • Know where the test is going • Know your resources • Know your messages • Follow instructions from the simulation coordinator • Provide realistic time frames to callers • Use spontaneous yet realistic messages • Deliver messages at the stated time • React convincingly to the message recipient’s comments • Ensure that key messages are kept active until they have been addressed • The simulation coordinator monitors messages and keeps the simulation team on track • Respond to participants’ requests and actions • Repeat information if asked • Stay on track with the script and objectives • Keep the simulation room scribe informed on impromptu stories • Report issues to the simulation room coordinator • If a phone is used, answer it with, “May I help you?” Confidential – Property of All Rights Reserved, 2009, TechTarget 11 – Document Name • 5.4.2 5.4.3 5.4.4 5.5 Keep the test plan and messages in a binder, and highlight your assigned messages • Keep notes on what you said to everyone • Be at the test early • Don’t offer to call anyone back; place the responsibility on test participants. You will be too busy with other calls to keep calling them back. • Remember you are in control of calls. Don’t let the caller determine how it is handled. • Try and avoid delivering something in writing • When following up on a message the team did not complete, and they state it was fixed, challenge them to validate their claims • When callers into the simulation room demand more information than is necessary or available, state that you don’t have any more information Simulation Room • The simulation room should be located near the test room, but far enough away where occupants cannot be heard • Have a sufficient number of phones • Have white boards or flip charts for scribes to note the current status • Key messages need to be noted for tracking • The room needs to have adequate room and wall space Simulation Team Orientation • Review test plan and key messages • Plot the strategy for escalation • Provide any necessary background information that the players will need • Provide a names list • Facilitate roles such as scribes and message runners On Test Day • Once the test is underway, stay in your assigned role as much as possible • Check with the simulation team coordinator if you have any questions Test Evaluators Evaluators need to understand the plan and test. They must understand the business and processes being tested, and be observant and objective. They should attend pretest briefing, test and post-test review meetings. Test Evaluator Name 5.5.1 Test Evaluator Role • Monitor test play • Evaluate actions, not players • Determine if the objectives and related actions are being met Confidential – Property of All Rights Reserved, 2009, TechTarget 12 – Document Name 5.5.2 5.5.3 5.5.4 5.6 • Identify problems to the facilitator • Track key messages and report findings to facilitator What to Evaluate • Test objectives – the evaluation form should have each objective written on one page with the evaluator commenting on his/her observations related to that objective. • Evaluate expected player outcomes • Track key messages • Provide objective comments and recommendations Evaluator Activities • Attend the pre-test briefing • Assist in the development of evaluation form • Review and know the test plan • Know the objectives, narrative and messages • Know the test organization • Report early to the test • Be positioned near intake phones so you will see where messages go and how they are handled • If messages are not addressed, notify the simulation team so they can remind the test team. • If key messages are lost, advise the simulation team coordinator so the message can be resent • Assign certain messages to specific evaluators so they can track their progress. • Note message processing on evaluator forms • Evaluators should be assessing command, control, coordination, and communication activities On Test Day • Observe participants in key roles (chairs and directors) • Examine situation boards and forms • Examine reports • Discuss issues with participants • Attend briefings • Follow key messages into crisis command center for handling Test Participants Test participants must be familiar with the BC plan being tested, and should specifically be named team members of the BC program. Individuals involved in executing plan sections and procedures are the following: Test Participant Name Confidential – Property of All Rights Reserved, 2009, TechTarget Comments 13 – Document Name Test Participant Name Comments 5.7 The Test Briefing • Following completion of the test, the facilitator reviews the test plan with the participants and answers questions • If possible, use audio-visuals to add realism • At the briefing conclusion, give participants a few minutes to get ready 5.8 The Test Debriefing • The purpose of the debriefing is: o To review and evaluate the test o To provide feedback o To review lessons learned from the test • Obtain feedback from all participants on what worked and what didn’t work • Note issues of command, control, coordination, and communication • Have each function chair report on their group • Evaluators and simulation team members share their observations • Test facilitator facilitates the session • The best time for a debriefing is immediately after the test • Ask two key questions: What worked? What didn’t work? • Simulation team members and evaluators should also debrief to capture their observations and lessons learned for sharing with the test team 5.9 Written Evaluations • Test participants should evaluate the perceived value of the test and their overall reaction to the experience • They should evaluate the existing plan • They should evaluate the test • They should identify the need for further training and tests • They should make suggestions for improvement 5.10 Written Report • The test facilitator should incorporate debriefing comments, evaluator observations and participant evaluations into a concise report of the event Confidential – Property of All Rights Reserved, 2009, TechTarget 14 – Document Name • including lessons learned, issues that need correction, next steps and additional training needed Complete the report within five working days of the test and distribute it to all participants 5.11 Keys to a Successful Test • Top level support and involvement • Test design team and volunteers • Realistic test plan • Thorough preparation and attention to detail • Clear introduction and instructions • Participant feedback at debriefing • Follow-up 5.12 Suggested Test Schedule Consider the following schedule if two tests are conducted on the same day: 4 weeks prior to test: Design team meets one hour per week 1 day prior to test: 1 hour meeting – Simulation team orientation 1 hour meeting – Assistant orientation 1 hour meeting – Evaluator orientation Day of test: 9:00 am Test participant orientation 9:30 am Conduct test 10:30 am Break (as needed) 11:45 am Lunch and debriefing 1:00 pm Test complete 6 Test/Debrief Summary The test took place on . A total of participants took part in the test. Out of participants, people responded to the written evaluation. Out of participants, people gave verbal feedback. 6.1 Written Evaluation Responses 6.1.1 Do you feel the test goal was achieved? Yes – No – Comments: 6.1.2 Do you feel that you had the opportunity during the test to participate in at least one of the objectives? Yes – No – No response – Confidential – Property of All Rights Reserved, 2009, TechTarget 15 – Document Name 6.1.3 If you answered YES, then which objective(s) did you participate in? Objective 1 – Objective 2 – Objective 3 – Objective 4 – None – 6.1.4 What did you like best about participating in this test? • 6.1.5 When did you feel most uncomfortable and why? • 6.1.6 Please reflect on the test and provide an honest opinion about what you have learned today. • 6.1.7 If you have a written departmental or facility plan, do you feel your plan, as written today, will be adequate to recover your business functions? Yes – No – No response – 6.1.8 Additional comments • 6.1.9 What worked properly? • 6.1.10 What didn’t work properly? • 6.2 Verbal Evaluation 6.2.1 What worked? • 6.2.2 What didn’t work? • 6.3 Recommendations for Improvement Assistance for all the following items is provided through the business continuity program office. Examples, samples and other documentation that other business units have produced will be shared upon request. Confidential – Property of All Rights Reserved, 2009, TechTarget 16 – Document Name No. Description of Improvement Responsible Party Due Date Completion Date 1 2 3 4 5 6 7 8 9 10 11 12 Confidential – Property of All Rights Reserved, 2009, TechTarget 17 – Document Name 7 Appendix A – Glossary Term Design Team Test Orientation Test Drill Table Top Test Definition The design team develops the test from start to finish. Members should have strong knowledge of the overall business. They should also have detailed knowledge in their area or department. The team usually has 3-7 members, more if needed. The design team is: • Creative • Functional under pressure • Able to stay on schedule • Detail-oriented • Willing to challenge • Good at keeping secrets • Not participating in the test An activity designed to promote emergency preparedness. The test examines the performance of duties, tasks and operations in a way similar to the way they would be performed in a real emergency. • Introduces participants to the plans and procedures • Introduce new plans or revise old plans • Requires no previous experience • Helps orient new staff or leadership • Planning cycle: one month • Test time: 60-90 minutes • Test of individual emergency response functions • Involves actual field response • Practice or test under realistic conditions • Involve all levels of responders • Planning cycle: one month • Test time: 10-60 minutes • Examples: o Fire drill o Radio test o Tornado test o Earthquake test • The basic version seeks to solve problems in a group setting via brainstorming • Advanced table tops will introduce messages and test assistants who can answer questions • A more “reality-based” experience • Planning cycle: 2-3 months • Test time: 90-120 minutes Confidential – Property of All Rights Reserved, 2009, TechTarget 18 – Document Name Term Functional Test Definition • • • • • • • Full-Scale Test • • • • • • • • Debriefing time: 30 minutes Assesses the allocation of resources and manpower Evaluates communication across the different groups Assesses the adequacy of current procedures and policies Participants perform actual activities Involves more participants: simulators, evaluators, larger design team Introduces more advanced messages and other media Test time: 90 min – 4 hours Planning cycle: 3-6 months Evaluates the operational capability of systems in an interactive manner over a substantial period of time Presents complex and detailed events in real-time Mobilizes personnel and resources and movement of emergency response teams, equipment and resources Can be expensive; may be disruptive to normal operations Test time: 2-8 hours Planning cycle: 4 months minimum Confidential – Property of All Rights Reserved, 2009, TechTarget 19 – Document Name 8 Appendix B – Record of Test Planning Meetings Date of Meeting Meeting Summary (Attach meeting minutes here) Confidential – Property of All Rights Reserved, 2009, TechTarget 20 Information and Technology Services (ITS) DISASTER RECOVERY / BUSINESS CONTINUITY DR TESTING LESSONS LEARNED Purpose The purpose of this document is to document the process issues in the DR Testing effort and apply any process improvements to the rest of the project. Please identify what you think went well, what can be improved, and recommendations for improvement in the table below. Please focus on process, and, as you think of issues, consider “why” certain things went wrong, so that we try to fix the root problem, rather than the symptoms. 1. + WHAT WENT WELL + 1. WHAT CAN BE IMPROVED 9. ∆ RECOMMENDATIONS FOR IMPROVEMENT ∆ Recovery Test Lessons Learned - 1 of 1 updated/saved 5/5/19 Information and Technology Services (ITS) DISASTER RECOVERY / BUSINESS CONTINUITY Disaster Recovery Test Objectives - Date: Time: Locations: Primary Objectives Objective 1: Result:  Did not meet objective. ❑ Met objective. ❑ Exceeded objective. Description: Issue: To-Do: Recovery Test Objectves - 1 of 2 updated/saved 5/5/19 Information and Technology Services (ITS) DISASTER RECOVERY TEST FOUR Secondary Objectives Objective 1: Result:  Did not meet objective. ❑ Met objective. ❑ Exceeded objective. Description: Issue: To-Do: Exercise page 2 of 2 updated/saved 5/5/19 Information and Technology Services (ITS) DISASTER RECOVERY / BUSINESS CONTINUITY Exercise Definition Exercise Session Primary Objectives This lists general objectives sketched out by the DR/BC office, which are used by CPU representatives to outline business specific objectives. Secondary Objectives This lists general ‘stretch’ objectives sketched out by the DR/BC office, which are used by CPU representatives to outline business specific ‘stretch’ objectives. Conditions   All key personnel are available.  Only M-pathways is impacted.  Outage duration expected to last 2 – 5 days. Limits Exercise – Session - 1 of 8 updated/saved 5/5/19 Information and Technology Services (ITS) DISASTER RECOVERY / BUSINESS CONTINUITY Exercise Outline Exercise Session Primary Objectives 1. This lists the specific business process objectives, which were developed using the general objectives in the Exercise Definition. Secondary Objectives 1. This lists the specific business process ‘stretch’ objectives, which were developed using the general stretch objectives in the Exercise Definition. Conditions 1. This lists specific business process scenario circumstances developed by CPU representatives, which were developed using the general conditions in the Exercise Definition. 2. Limits Roles 1. Facilitator – 2. Players – 3. Evaluator – Resource Listing   Exercise – Session - 2 of 8 updated/saved 5/5/19 Information and Technology Services (ITS) DISASTER RECOVERY / BUSINESS CONTINUITY Checklist Exercise The Checklist is provided by the DR/BC office for guidance during exercise. Can be used as-is or slightly altered to meet specific business process goals. Delete the italic writings before distribution.> Session  Personnel Contact Information — Review names and numbers. Send a copy of it to each team member to review and update, if needed.  Critical Processes Listed — Team leaders must review critical functions to determine that they are relevant and complete.  Action Plan Steps – Ensure steps are written clearly, in logical order, comprehensive and concrete. o Recovery Steps — Ensure action plan includes steps for recovery of critical functions after the outage; validate that strategies are meeting current business objectives and reflect the best possible solutions. o Recover Lost Data – Ensure action plan includes processes to recover lost data. o Dependencies – Ensure dependencies on other processes or business areas are identified. o Staffing – Plan should state whether or not additional staffing is needed during or after the outage. o Communication – Determine the dependence on phone and email; consider alternative communication methods. o Escalation – Include escalation procedures under particular circumstances.  Advance Planning Readiness Checklist — Critical resources required to support manual processes and recovery; must be reviewed to determine list accuracy and completeness.  Off-Site Storage Inventory — Critical records or resources stored off site; must be reviewed to determine accuracy and completeness.  Vendor and Customer List — Contact information for critical vendors and customers; must be reviewed to determine list accuracy and completeness.  Initial Responders, Essential & Alternate Essential Personnel — Awareness and preparedness of personnel acting as first or second… alternates must be exercised and validated at least annually. Exercise – Session - 3 of 8 updated/saved 5/5/19 Information and Technology Services (ITS) DISASTER RECOVERY / BUSINESS CONTINUITY checklist Exercise Session  Personnel Contact Information — Review names and numbers. Send a copy of it to each team member to review and update, if needed.  Critical Processes Listed — Team leaders must review critical functions to determine that they are relevant and complete.  Action Plan Steps – Ensure steps are written clearly, in logical order, comprehensive and concrete. o Recovery Steps — Ensure action plan includes steps for recovery of critical functions after the outage; validate that strategies are meeting current business objectives and reflect the best possible solutions. o Recover Lost Data – Ensure action plan includes processes to recover lost data. o Dependencies – Ensure dependencies on other processes or business areas are identified. o Staffing – Plan should state whether or not additional staffing is needed during or after the outage. o Communication – Determine the dependence on phone and email; consider alternative communication methods. o Escalation – Include escalation procedures under particular circumstances.  Advance Planning Readiness Checklist — Critical resources required to support manual processes and recovery; must be reviewed to determine list accuracy and completeness.  Off-Site Storage Inventory — Critical records or resources stored off site; must be reviewed to determine accuracy and completeness.  Vendor and Customer List — Contact information for critical vendors and customers; must be reviewed to determine list accuracy and completeness.  Initial Responders, Essential & Alternate Essential Personnel — Awareness and preparedness of personnel acting as first or second… alternates must be exercised and validated at least annually. Exercise – Session - 4 of 8 updated/saved 5/5/19 Information and Technology Services (ITS) DISASTER RECOVERY / BUSINESS CONTINUITY Cool Down Evaluation Exercise Session Strengths Areas for Improvement Issues Assignments Task Exercise – Session - Assigned 5 of 8 Target Date updated/saved 5/5/19 Information and Technology Services (ITS) DISASTER RECOVERY / BUSINESS CONTINUITY Program Evaluation Exercise Session Strongly Disagree Moderately Disagree Moderately Agree Strongly Agree N/A 1. The materials provided were complete. 2. The materials provided were well written. 3. The situation (conditions, limits, etc) was plausible. 4. The situation was of the right complexity. 5. The exercise was conducted in a logical order. 6. The time allowed for exercise was just right. 7. This exercise was progressive, not a repetition of previous exercises. 8. Exercises should be run more often. 9. This exercise offered valuable DR/BC training opportunities. 10. I feel my work area is ready for lengthy systems outages. 11. Overall, this session was effective. COMMENTS: Exercise – Session - 6 of 8 updated/saved 5/5/19 Information and Technology Services (ITS) DISASTER RECOVERY / BUSINESS CONTINUITY Brief for Facilitator Exercise Session 1. Review test objectives 2. Review BCP and evaluation a. High light areas for improvement b. Discuss highlights with Evaluator 3. Conduct Initial Briefing a. Review exercise format b. Review Exercise Definition (general exercise situation including conditions, limits, etc.) c. Review Exercise Outline. 4. Discuss assumptions of BCP and how those assumptions may impact exercise results. (For example, a plan may have been written assuming phones are available or that all personnel are available.) 5. Discuss exercise attendance, roles and responsibilities and any possible impact on exercise. 6. Review exercise expectations – a successful exercise finds omissions, inaccuracies, constrictions, etc. 7. Suggest players move away from scripted situation if it delivers added value. 8. Feed exercise scenario information to players where they need information outside the written conditions or scenario. Provide details that are plausible, realistic and consistent with the conditions or scenario. 9. Avoid interfering or disrupting the flow of activity, except to get things moving if they have stalled. 10. Report observations during cool down. 11. Gain player agreement on action items and assignments. 12. Track action items until completed. 13. Submit materials to DR/BC Office. Exercise – Session - 7 of 8 updated/saved 5/5/19 Information and Technology Services (ITS) DISASTER RECOVERY / BUSINESS CONTINUITY Brief for Evaluator Exercise Session 1. Review test objectives 2. Review BCP and evaluation a. High light areas for improvement 3. Observe and record: b. Actions taken during the exercise, which were not, but should be, incorporated in the plan. c. Omissions from the plan (contact information, dependent processes…) d. Inaccuracies and inconsistencies e. Areas too detailed or restrictive f. Note assumptions that were challenged g. Any other aspects and observations either on the effectiveness of the plan or effectiveness of the test. 4. Suggest players to move away from scripted situation if it delivers added value. 5. Feed exercise scenario information to players where they need information outside the written conditions or scenario. Provide details that are plausible, realistic and consistent with the conditions or scenario. 6. Avoid interfering or disrupting the flow of activity, except to get things moving if they have stalled. In the event of difficulty, contact the facilitator. 7. Report observations during cool down. 8. Submit written notes to facilitator. Exercise – Session - 8 of 8 updated/saved 5/5/19
Purchase answer to see full attachment
User generated content is uploaded by users for the purposes of learning and should be used following Studypool's honor code & terms of service.

Explanation & Answer


Anonymous
Really great stuff, couldn't ask for more.

Studypool
4.7
Indeed
4.5
Sitejabber
4.4

Related Tags