Resource Deployment - No Notice Event

OVERVIEW

There are times when local, mutual aid, and regional resources are quickly overwhelmed and there is a need for immediate assistance through the FFCA SERP. Such requests require an immediate deployment of on duty resources that would not be expected to remain on location past their normal work schedule without relief. In other words, a No Notice Deployment is like any other mutual aid request, just from a greater distance. Examples of a No Notice event include wildfires, weather-related events, and terrorism. A goal is to provide assistance as quickly as possible and either demobilize or transition resources to that of a sustained emergency, i.e., Planned Deployment. Additionally, a goal should be to fill the request as expeditiously as possible utilizing resources from as close as possible to the incident location first. Often, resources may be “rolling” prior to all the required documentation is complete.

Requesting Assistance

When a fire department has exhausted all its traditional resources, local, mutual aid, and regional, a request should be made for FFCA SERP resources. To expedite the process the Regional SERP Coordinator for the affected area should contact the SEOC ESF 4/9 Representative and the State SERP Coordinator. Requests may come through the FDEM State Watch Office from the impacted County or municipality. DSFM ESF 4&9 on call will notify the State SERP Coordinator and will jointly follow through with the resource process.

Confirming And Providing Assistance

Once a request for assistance is received a ESF 4/9 Representative or the State SERP Coordinator will contact the requesting agency to:

• Verify the request

• Obtain the name/number of a local Point of Contact (POC)

• Obtain the location of the where the resource(s) is/are expected to report

The State SERP Coordinator or designee will identify the appropriate resource(s) working with the Regional SERP Coordinator(s) who in turn work with their County SERP Coordinator(s). Once the resource(s) is/are confirmed the ESF 4/9 Representative will coordinate the completion of Section 2 (all tabs) Cost Estimate, of the SMAA Form B.

Absent a State or Federal disaster declaration, the Requesting Agency must understand they are responsible for the costs associated with the resource(s) deployment to include personnel salary, backfill costs, lodging, food, mileage, and other allowable expense

Documentation

All resources deployed must be documented PRIOR TO leaving their POA and any changes updated during the mission. Regional SERP Coordinators must ensure that at a minimum, the following documentation is completed and forwarded to the ESF 4/9 Section at the SEOC PRIOR TO any resources departing. A link to all forms can be found in Appendix J- List of Forms:

• FFCA Form 2 - Team Roster

• FFCA Form 3 – Emergency Agency POC

• ICS 218 Form - Support Vehicle/Equipment Inventory

Completed forms must be e-mailed to ESF49@myfloridacfo.com.

ICS 214 Activity Log

An ICS 214 Activity Log must be completed by each Leader, Unit Supervisor, and/or Single Resource for each operational period while assigned to a Mission. These logs will be required to be submitted as part of the agencies reimbursement package to document each operational period hours worked

READY-RESOURCE LIST

To help facilitate a rapid deployment for a No Notice event, Regional SERP Coordinators are encouraged to pre-identify resources that may be assembled quickly for immediate deployment. Examples include.

• Engine Strike Teams (Type I or II)

• Ambulance Strike Teams (Type I)

• Technical Rescue

• Structural Protection Task Forces

• Brush Truck Strike Team

• Tender Strike Team

Reimbursement

It is expected that agencies providing resources for a No Notice Deployment will not seek reimbursement from the requesting agency as this should be considered a type of mutual aid response with on duty resources. If, however, later a formal disaster declaration is issued and the agency is eligible for reimbursement, this does not preclude that request. Therefore, documentation is critical as if it were a Planned Deployment.