|
PLANNING SUPPORT (FEMA/ESF-5) Mission: To analyze information and intelligence, identify and anticipate problems, project future requirements, and manage ERT operational objectives.. Note: Navy color "Hot" buttons in tables are FEMA/DFO intranets and cannot be accessed from the internet. All other linked information is in the public domain on the Internet. |
|
ESF-5 Planning Organization, Definitions and Plan Outlines |
|
ORGANIZATION: The Planning Support Branch consists of three designated functional positions, led by a branch chief (Branch Chief, Planning Coordinator and Planning Specialist . In some cases, a fourth position (Clerical Specialist) may be required to provide dedicated Administrative support. FUNCTIONAL AND ACTION PLANNING: Outlines the major actions and activities of the ERT in the next operational period. Establishes the FCO priorities, development of supporting objectives and supporting tasks of ERT functional elements. KEY ACTION PLANNING ELEMENTS: FCO Priority - provides a general direction, but not a specific destination (e.g. Identify critical unmet needs in impacted area). ERT Objective - provides a specific destination but not a route. (e.g. Deploy Rapid Needs Assessment (RNA) Team to impacted area. ERT Element Task - Identifies how to get to a specific destination (e.g. Arrange air transportation to MOB Center for RNA Team). OPERIOD ACTION PLANING CYCLE: This cycle is essentially a four-stage process: (1)Identify FCO Priorities, (2) ERT Elements develop and refine objectives, (3) ERT Elements identify and unify objectives for next OPeriod, and (4) ESF5 assembles Action Plan for next OPeriod. An OPeriod is a specific time period that serves as the baseline for planning, coordinating and accomplishing ERT Operations and activities. It is established by the FCO based on recommendations from the Operations Section Chief and the Information and Planning Chief. At the outset of the disaster the Operiod may be set at 12 hours. Normally, the OPeriod is initially set at 24 hours and then lengthened to 48 hours once the response operation enters the recovery phase. CONTINGENCY PLANNING: Developed to address one or more specific threats to provide a basis for decision making and a course of action. Identifies requirements and resources to satisfy those requirements. Contains action timelines and checklists to support operations and to task ERT components. It's purpose is to prepare for events and threats which would, if they were to occur, would adversely impact ERT or response operations. ERT MANAGEMENT PLANNING: Long range management planning. (See ERT Strategic Planning). ERT STRATEGIC PLANING: (Ref: Interim Guidance, Apr 24, 2000) Strategic Planning is the forecasting of future goals by the Federal Coordinating Officer, and the associated development of goal-supporting objectives through unified Emergency Response Team Planning processess. The new Strategic Planning Guide is an interim publication designed to help standardize the strategic planning process during disaster response operations. Final and more refined guidance is planned for publication later in 2000, in the form of an ERT Planning Job Aid, which will be a companion document to the new ERT Information and Planning Section Operations Manual. SPECIAL FUNCTIONAL PLANS: e.g. Debris Management Plans, Temporary Housing Plans, Public Assistance Management Plans. Keep these plans as streamlined and simple as possible. Critical components include: Specific Objectives, method(s) of achieving the objective(s), list of milestones, and a timeline. TRANSITION PLAN: Components - Staff positions changing, prioritize changes, operational transition briefings, overview of key decisions and events, current response and situation (from SITSTAT Branch), and ERT organizational overview (FCO priorities, Operational Period, transition timeline) DEMOBILIZATION PLAN: Components - timeline, phased functional staffing pattern, key demobilization action, key DFO closure actions and After Action Reporting. |
|
ERT Action Planning Instructions:
The top
portion through Section One of the Worksheet is filled out by the planning coordinator (ESF5). Section 2 to the bottom is filled out by the ERT Section or Element. The Action Planning meeting ideally takes place in the afternoon, following the development of the priority-supporting objectives by the functional areas. Attendance at the OPeriod Planning Meeting is locally determined. The Planning Coordinator or Planning Support Branch Chief will facilitate all OPeriod Planning Meetings. Meeting should be 30 minutes or less and conducted in a SIT Room with Maps, Displays and other references. Following the meeting an Action Plan for the next Operiod should be completed and distributed (See Format below). |
|||
|
ERT OPERATIONAL PLANNING WORK SHEET |
|||
| Disaster Number: | |||
| ERT Element: | |||
|
Operiod |
Beginning: Ending: | ||
| 1. Specific FCO Priority this Operational Planning Worksheet Supports: | |||
| a. FCO Priority | |||
| b. Lead Element | c. Supporting Elements | ||
| 2. Operational Objectives that Support Accomplishments of the Above Priority | |||
| a. Operational Objective: | |||
| (1) Time Required to Complete Objective: | (2) Lead POC: | Name: Number: |
|
| (3) Support Required from other ERT Elements: | |||
| (4) Factors that may impact success: | |||
| b. Operational Objective | |||
| (1) Time Required to Complete Objective: | (2) Lead POC: | Name: Number: |
|
| (3) Support Required from other ERT Elements: | |||
| (4) Factors that may impact success: | |||
| c. Operational Objective | |||
| (1) Time Required to Complete Objective: | (2) Lead POC: | Name: Number: |
|
| (3) Support Required from other ERT Elements: | |||
| (4) Factors that may impact success: | |||
| APPROVED BY: | Typed
and Signed Name of Approving Official: |
||
|
ERT OPERATIONAL PERIOD ACTION PLAN |
||
| Disaster Number: | ||
| OPeriod: | Beginning: Ending: | |
| a. FCO Priority: | ||
| (1) Operational Objective: | Lead ERT Element | |
| (2) Operational Objective: | Lead ERT Element | |
| (3) Operational Objective: | Lead ERT Element | |
| b. FCO Priority: | ||
| (1) Operational Objective: | Lead ERT Element | |
| (2) Operational Objective: | Lead ERT Element | |
| (3) Operational Objective: | Lead ERT Element | |
| c. FCO Priority: | ||
| (1) Operational Objective: | Lead ERT Element | |
| (2) Operational Objective: | Lead ERT Element | |
| (3) Operational Objective: | Lead ERT Element | |
| d. FCO Priority: | ||
| (1) Operational Objective: | Lead ERT Element | |
| (2) Operational Objective: | Lead ERT Element | |
| (3) Operational Objective: | Lead ERT Element | |
| Attachments | Functional Plan(s) Other:_______________ | |
| SCO
Approval:*
FCO Approval: |
SCO Name and Signature: | |
| FCO Name and Signature: | ||
| *Note: The SCO Approval is required when preparing a joint State/Federal Action Plan. | ||
Alternate Action Plan Format
|
ACTION
PLAN For the Operational Period FEMA-XXXX-DR-XX |
MASTER |
|||||
|
DATE:
5/18/00
|
POC/Ext:
|
|||||
|
Personnel
Assigned |
DFO: |
Field:
|
Total: |
|||
|
Instructions: Open FCO Priorities that are supported by the Staff
functions will appear under the Section I and given a Priority Number by
ESF-5. Completed FCO priorities will be removed from Section 1 by ESF-5
and placed on a Closed Priority Form.
Critical issues for FCO Priorities will be entered by the Staff
Functions in Section II. Staff
functions should number and publish their daily priorities in Section
III in order to facilitate DFO inter- coordination. Internal Staff
accomplishments for the current operational period should be entered in
Section IV. Staff SITREP inputs should be submitted in the Section V. |
||||||
|
Section
I:
FCO PRIORITIES (Current Operational Period) |
||||||
Priority Number |
Description |
Activities/Objectives |
||||
|
|
|
|
||||
|
|
|
|
||||
|
|
|
|
||||
|
Section
II: RECOMMENDED
ISSUES FOR FCO PRIORITIES (Next Operational Period) |
||||||
|
Priority
|
Description |
Activities/Objectives |
||||
|
|
|
|
||||
|
|
|
|
||||
|
|
|
|
||||
Section III: STAFF FUNCTION PRIORITIES (Internal) |
||||||
|
Priority
Number |
Description |
Activities/Objectives |
||||
|
|
|
|
||||
|
|
|
|
||||
|
|
|
|
||||
|
|
|
|
||||
|
Section
IV: STAFF
ACCOMPLISHMENTS (Internal – Previous Operational Period) |
||||||
|
Priority Number |
Description |
Activities/Objectives Completed |
||||
|
|
|
|
||||
|
|
|
|
||||
|
Section V:
SITREP
INPUT |
|
Instructions:
Type all new inputs in italics and take italics off items that have been
published once. Sections should try to have at least 80 percent or more
new inputs each time. Items that have been published twice should be
considered for removal. 6.
STATUS
OF FEDERAL OPERATIONS: A.
|
|
ERT STRATEGIC PLANNING (Interim Guidance Apr 14, 2000) |
||||||||||||||||||
Suggested FCO Goals:
|
STRATEGIC PLAN GUIDANCE
TABLE
OF CONTENTS
SECTION
PAGE
TABLE OF CONTENTS...........................................................................................
INTRODUCTION.....................................................................................................
ERT STRATEGIC PLANNING OVERVIEW........................................................
·
TIMELINES..............................................................................................
·
MILESTONES..........................................................................................
·
STRATEGIC
SUB-OBJECTIVES...........................................................
·
SPECIAL
FUNCTION PLANS..........................................................
STRATEGIC
PLANNING CHECKLIST..........................................................
STRATEGIC
PLAN TEMPLATE (Instructions)...............................................
STRATEGIC
PLAN TEMPLATES (Format)....................................................
ERT
STRATEGIC PLANNING OVERVIEW
TIMELINES
A
key component of strategic planning is the timeline.
A timeline provides a universal basis for planning, progress evaluation,
and analysis. It also provides a
visual overview of long-range strategic planning goals and associated
milestones.
NOTE: A number of software
programs designed to support project management requirements (e.g., MS Project)
are capable of producing timelines. The
timeline example at Figure 2 was created using the table function in Microsoft
Word.
Timeline Planning Worksheet Format