STEN – Strike Team Leader Policy & Guidelines Area C - XLC Don Wise – Verdugo Fire – Executive Administrator –

Slides:



Advertisements
Similar presentations
Review of the Incident Command System
Advertisements

WASHINGTON FIRE SERVICES RESOURCE MOBILIZATION PLAN 2013 VERSION
Incident Command System
Public Health Seattle & King County Incident Command System Overview May 2004.
THE INTERNATIONAL SOCIETY OF FIRE SERVICE INSTRUCTORS Electronic INSTRUCT-O-GRAM Program The “Safety Engine” Concept – Part 1.
Fire District Strike Teams STATE FIRE MOBILIZATION TASK FORCES &
Visual 3.1 Unified Command Unit 3: Unified Command.
Missouri Systems Concept of Operational Planning for Emergencies Missouri Systems Concept of Operational Planning for Emergencies (MoSCOPE) Includes: Missouri.
Visual 3.1 Unified Command Unit 3: Unified Command.
OSHA Respiratory Protection Standard – 29 CFR Prepared by Daniel Gearhart, Division Chief, Retired.
Troy Fire Department Incident Command System
1. 2 Mutual Aid Among Local Entities Occurs Somewhere In Missouri On A Daily Basis 3.
Department of Transportation Support Services Branch ODOT Procurement Office Intergovernmental Agreements 455 Airport Rd. SE, Bldg K Salem, OR
Law Enforcement Mutual Aid Quick Reference Guide Mutual Aid Defined Authorities Mutual Aid Process Mutual Aid Considerations Mutual aid is the voluntary.
Emergency Transportation Operations (ETO) Plan Wisconsin Department of Transportation.
Training On Demand. Purpose To provide fire fighters at an emergency incident a team with pre-assigned duties aimed at rescuing downed, lost or trapped.
Ohio Hazardous Materials Technical Advisory Committee (TAC) Notification SOP.
I-295 / I-76 / NJ 42 Incident Management Task Force in New Jersey
Incident Command System Basic Course
FIRE DEPARTMENT ORGANIZATION State of Georgia BASIC FIRE FIGHTER TRAINING COURSE.
What Is It And How Will We Measure It?
4 Incident Management System. 2 Objectives (1 of 2) Describe the characteristics of the incident management system. Explain the organization of the incident.
4 Incident Command System. 4 Objectives (1 of 2) Describe the characteristics of the incident command system (ICS). Explain the organization of the ICS.
Rapid Intervention Team & MAYDAY Procedures
DMC Incident Command System Page 1 of 31 DMC Corporate Audit and Compliance Department Detroit Medical Center© Revised: January, 2010 Incident Command.
Questions & Answers Missing Documents and Incorrect Notification.
Last Updated May 24,  Incident Management Overview  AQM Incident Support Roles  Guiding Documents  Procurement Unit Leader (PROC)  Buying Team.
Incident Command and Unified Command 1293 Airport Road Beaver, WV Phone: (304) Fax: (304)
District Planning Council Program Overview. District Planning Concept Local Elected Officials Emergency Managers Emergency Responders Local Business Community.
Visual 7.1 Common Responsibilities Version 2.0 Unit 7: Common Responsibilities.
Part of a Broader Strategy
Chapter 8 Support Functions
Introduction to Incident Command System (IS 100b)
United States Fire Administration Chief Officer Training Curriculum Operations Module 1: Application of the ICS.
IS-700.A: National Incident Management System, An Introduction
Mutual Aid Box Alarm System. MABAS Communications Committee  Charged with the task of improving fire service communications interoperability to assist.
Nursing Home Incident Command System
Page 1 of 32 DMC Incident Command System Incident Command System for Hospitals Emergency Management Department Emergency Management Leadership Task Force.
Division of Forestry Incident Management Teams John Nielsen WDNR, Division of Forestry Regional Forestry Leader-SOR.
Slide 4-1 Unit 4 Slide 4-1. Slide 4-2 Unit 4 Objectives 1.Mobilize, reassign and demobilize overhead resources in a safe and cost effective manner. 2.Describe.
Visual 6.1 Incident Resource Management Unit 5: Incident Resource Management.
Intro: On a day to day basis when new incidents arise, we generally have the capability to handle them with resources within our unit. We trust when.
Visual 2.1 G191: ICS/EOC Interface Workshop Unit 2: Incident Command System (ICS) Review.
State of Florida Emergency Support Function 6 1 EMERGENCY SUPPORT FUNCTION 6 - MASS CARE & EMERGENCY ASSISTANCE “Training for incoming EMAC personnel”
Return to Work 101 Injury Reporting May 14th, 2009 Presented by: Cathy Stein-Romo Chief Executive Office Risk Management/WC Unit (213)
Washington State Patrol Office of the State Fire Marshal Unit 5: Command and Support Structure of a State Mobilization.
Disaster Planning Workshop Hosted By: Pleasantview Fire Protection District.
What Is an Incident? An incident is an occurrence, caused by either human or natural phenomena, that requires response actions to prevent or minimize.
INITIAL APPARATUS PLACEMENT and STAGING OPERATIONAL GUIDELINE SALT LAKE VALLEY FIRE ALLIANCE.
Incident Command System Nevada Department of Corrections.
California Fire Service and Rescue Emergency Mutual Aid System Mutual Aid Plan Steve Prziborowski.
State of Florida Emergency Support Function 6 1 EMERGENCY SUPPORT FUNCTION 6 - MASS CARE & EMERGENCY ASSISTANCE “Your Role at the State Emergency Operations.
Illinois Mobile Support Teams Incident Management Team and the Emergency Management Assistance Team.
RAPID INTERVENTION TEAMS This presentation is a work in progress and has not yet been adopted as policy. It is meant as a training guide to better.
Finance and Administration Developed Using The CAP-USAF Pamphlet 12 and CAP ES materials 6/7/2016NESA 2012 phm1.
ACS ACTIVATION. The first section of this presentation describes the initial activities of the ACS Staff. The second section describes the initial activities.
Foothill Mutual Threat Zone (MTZ) Communications Plan.
Introduction to the Emergency Operations Center City of Santa Cruz 2011 EOC Training and Exercise.
Mutual Aid 1 Created by: Mike Fennell. CALIFORNIA MASTER MUTUAL AID AGREEMENT n State of California, all State agencies, all political subdivisions and.
Module 3 Organization Overview Module 3 Organization Overview Subjects to be covered in this module include: Terminology Terminology Organizational structure.
Fireground Operations: Staging Union County SOG 3.24.
Developing Local and Regional Incident Management Teams Bob Koenig Incident Management Team Coordinator Texas Forest Service.
CAP Communications Equipment Management – Squadron Level CAP Communications Equipment Management Developed by: Capt Karl Falken SWR-TX
MULTI- CASUALTY INCIDENTS GLENDALE FIRE DEPARTMENT ANNUAL TRAINING MARIANNE NEWBY.
Module 3 Organization Overview
IS-700.A: National Incident Management System, An Introduction
Delegation of Authority & Management by Objectives
Review of the Incident Command System
Organizational Flexibility
Presentation transcript:

STEN – Strike Team Leader Policy & Guidelines Area C - XLC Don Wise – Verdugo Fire – Executive Administrator –

Strike Team Leader Refresher Or Publications Strike Team

Strike Team Leader Refresher Area C Coordination Area C Strike Team Policy Strike Team Formation / Rotation Daily Sign-Up Strike Team Numbering CALOES Type III Resources, Water Tenders / Use INC-209 / FMAG ROSS CICCS Single Resource Ordering TICP Standing Orders Area C Activity Agreements

Area C - Coordination Verdugo Fire is the coordination point for 12 cities for Fire / EMS in Area C, within REGION-1 Verdugo has the best overview of available resources systemwide for the area Generally, for PLANNED need, a minimum of two Type I Strike Teams can be dispatched and on the road within 30 minutes; for IMMEDIATE need, in 10 minutes.

Area C - Coordination A third team can be formed up and dispatched within 4 hours; still allowing for key stations to be covered in the area Regardless of team formation, authorization to deploy is required from the Area C Coordinator or their designee Or when a team is relocated to another incident other than the initial dispatch Region I understands there are two teams available at any given time, but authorization to dispatch is still needed prior to any launch

Area C – Strike Team Policy Current policy can be found at: or Under: Publications and then Strike Team Last revised: March 20, 2013 and adopted by Area C Fire Chief’s Under revision with latest changes for “SSS” and inclusion of MTB to Area C

Area C – Strike Team Policy Distance Any location within Region I (Los Angeles County), and; Up to a 250 mile maximum beyond Area C ○ Beyond 250 miles, dispatch of resources within a team requires Agency-by-Agency Fire Chief approval; ○ A lack of response from the agency Fire Chief is indicative that they decline to allow their resources beyond the limit

Area C – Strike Team Policy Polling Requests Verdugo will perform a Systemwide Notification indicating that Region I is polling only for available resources from Area C; it is not a dispatch and serves only as an advisory situation: All available information from the incident is also sent Unless you’re an STL (STEN) or Trainee, there’s no need to contact dispatch Sent via Systemwide Notification – Page Gate

Area C – Strike Team Policy Polling Requests Initiate a Systemwide Notification via Page Gate: Advise that the notification is polling activity only and give all available detail: E.g., - SYSTEMWIDE NOTICE – Region I is polling only for strike team availability for the Old Road incident in Santa Clarita. Team 1202A GLN Leader & 1204A SGB Leader are next up. Polling only – not a request. FCO [Name]

Area C – Strike Team Policy Polling Requests Verdugo Staff notifies Area C Coordinator (or designee) for authorization to deploy up to two (2) teams Notify by phone, page, and until contact is made! Advise of current Area C conditions – i.e., system activity, weather, resource availability Verdugo obtains and provides the incident location, nature of incident, details, etc., and a callback number to REGION 1; it may be different from one that Verdugo normally uses

Area C – Strike Team Policy Responses – Immediate Need – Outside of Verdugo System Dispatch verbiage shall include “This is an immediate need response – people/structures threatened – respond directly to the incident” Units are dispatched immediately, using closest available resources to the location of the incident, regardless of sign-up or configuration. Resources must be Enroute within 10 minutes of dispatch; there is no form up! However, if the location is well outside of the area, take the time to form up if needed… STL coordinates the arrival (formation) point with all incoming units just outside the incident location. Resources assigned will be to the extent that no single agency is depleted of their key stations and that key stations remain filled.

Area C – Strike Team Policy Responses – Immediate Need – Within Verdugo System Unified Response applies – closest and available apparatus I.C. requests additional alarm levels until Verdugo advises the system has been maximized (On a perfect day, Verdugo can handle a 5 th alarm BRUSH and still maintain 20+ engines for key station coverage) All first alarms and subsequent alarms, up to when system is depleted, are Initial Attack (IA) and request numbers are not issued! Exceptions: If needed for span of control, Team Numbering can be issued (but not using existing numbers of ); request numbers (E-#’s) are not issued! If incident is expected to involve a State of Emergency declaration (FMAG situation) Initial Attack always remains on the incident until released by the I.C.

Area C – Strike Team Policy Responses – Planned Need ○ Units shall be Enroute within 30 minutes immediately following dispatch notice. ○ Safety briefings are conducted at the pre-designated form-up locations found in the policy. ○ Staging/form-up is designated by Verdugo; generally at a station closest to the fire. ○ STEN Leader and Trainees shall communicate daily as to where both shall meet in event of a dispatch.

Station 11 Station 21 Station 33 Station 71 Station 105

Area C – Strike Team Policy Responses – Planned Need STEN (Leader or Trainee) shall supply Verdugo by or fax with all contact phone numbers for each resource and a list of personnel for each. Agency Personnel Names/CAD-IDs must be correct! Verdugo shall supply all necessary information as available; there are times when a team is launched and information will follow – i.e., E #

Strike Team Composition A Type I Strike Team shall be composed of five (5) triple combination pumpers and one (1) qualified Strike Team Leader. One (1) Trainee is also authorized. A limit of five (5) engines and one (1) command vehicle; support vehicles and utility vehicles are strictly prohibited Enclosed cabs only! Able to pump 1,000 gallons per minute; 500 gallons per minute “heavy stream” 400-gallon tank 1,200 feet of 2 ½” hose – or larger 400 feet of 1 ½” hose or 1 ¾” hose 200 feet of 1” hose 20 – 24 foot extension ladder 4 Personnel – Captain, Engineer, Firefighter, Firefighter

Strike Team Formation 1201-A (BRK-GLN-GLN-PAS-PAS) – BRK Leader 1202-A (BRK-BRK-GLN-PAS-PAS) – GLN Leader 1203-A (BRK-BRK-GLN-GLN-PAS) – PAS Leader 1204-A (ALH-ARC-MPK-MTB-SSS) – Rotational 1205-A (ALH-ARC-MPK-MRV-SSS) – Rotational ALH may be recommended but not dispatched on two teams at the same time

Strike Team Rotation / / /5

Strike Team Rotation Verdugo Staff refer to Strike Team Worksheets and Guidelines for determining next-up STL Leaders and team rotation Please refer to the ST policy for substitution scenarios Strike Team Leader/Trainee Rotation Please refer to the policy for substitution scenarios. Verdugo staff have latitude and authorization to substitute as necessary based on situational necessity and availability of resources = “Big picture”

Daily Signup Go to Click on Daily Sign-up Username / Password Enter in appropriate information; be sure to use drop-down box to denote proper agency name! If updated later, advise Verdugo by phone Complete no later than 08:30 each day; regardless of whether you have resources or not…

Strike Team Numbering Verdugo maintains Team Numbering What do they mean?XLC-1201-A XLC = Area or Agency ○ X = A team comprised of a number of agencies (mixed grouping) within one (1) team ○ L = The team is from Los Angeles County ○ C = The team is from Area C 1 = Region I ○ 2 = Area or Agency ○ 01 = Grouped resource number ○ 201 = Represents the team number (202, 203, 204, 205) A = Kind and Type [Type I Engines]

Strike Team – CALOES Resources Team numbering is assigned by Region I E.g., 1801-C, 1860-C, 1812-C At minimum, a CALOES Team is comprised of five (5) Type III fire engines Verdugo normally serves as coordination point for these resources The CALOES Strike Team from Area C will utilize four (4) engines, if available; the balance coming from Areas B, E, G, or F

Strike Team – CALOES Resources Area C has resources strategically placed and owned by CALOES (California Office of Emergency Services) Engine 341 (Type II) - Stationed at MRV 101 Engine 343 (Type I) - Stationed at ARC 105 Engine 281 (Type I) - Stationed at SMD 41 Engine 285 (Type I) – Stationed at MTB 56 Water Tender 11 (Type III) - Stationed at GLN 21 ○ Note that E281 & E285 are not SPS engines! ○ Note that WT11 is not a BRK water tender!

Region I Coordination/Identifiers Area IdentifiersCounty/Agency Coordinator Area A – XLALos Angeles City Fire Comm. Area B – XLBLos Angeles County Fire Comm. Area C – XLCVerdugo Fire Communications Area E – XLEDowney Fire Communications Area F – XLFLong Beach Fire Communications Area G – XLGTorrance Fire Communications XOR – Orange CountyOrange County Fire Department XSL – San Luis ObispoSan Luis Obispo County Fire Dept. XSB – Santa BarbaraSanta Barbara County Fire Dept. XVE – VenturaVentura County Fire Department

INC-209 What is it? An incident summary for Wildland fires and large scale incidents. When is it triggered? Any working or significant incidents or when resource requests exceed that of Area C. Who maintains it? Verdugo initiates up until a management team is in place and takes over. Updated twice a day in conjunction with I.C. It is expected, that the agency will take over the INC-209 after Verdugo Staff have initiated the form.

INC-209

FMAG What is it? Is the Fire Management Assistance Grant process for requesting Federal financial aid to a local government incident for control of a fire or large-scale incident. Requested through local government to CALOES; then from CALOES to FEMA. When is it triggered? Working and significant incidents. CA State thresholds for 2014 are currently: $2.59M – Individual Fire $7.76M – Cumulative Fire Statewide the thresholds have already been met for Who initiates it? Verdugo/Agency initiation in conjunction with I.C. and Fire Chief. Watchouts! FMAG A-B-C form must match INC-209 information. INC-209 is no longer required at time of submittal. All conversations must match any follow-up phone calls. Ensure phone number and any related individuals for contact are aware of the FMAG/INC-209 information. I.e., Finance, Business Executives for Fire Admin. Ensure it actually is delivered and within reasonable timeframe!

FMAG

CICCS California Incident Command and Certification System Area C Policy – anyone responding out of the Verdugo System, is required to be vetted through the CICCS-300 Level Committee and have agency Fire Chief approval. Agency Training Chief Officer sits on 300-Level Committee Only qualified/vetted staff are entered into ROSS by Verdugo, upon committee approval. Field personnel requesting to be dispatched and not currently in ROSS will not be dispatched nor entered into ROSS unless vetted by the Committee.

ROSS - Resource Ordering & Status System National Database for ordering of Equipment (E#), Aircraft (A#), Supplies (S#), Overhead (O#) Only certified staff in Verdugo can enter data or make requests via ROSS. Verdugo serves as “gatekeeper” to all entries and data. Complicated database; used 90% of time by CA agencies. Verdugo can only see own incidents and resources; if incident is outside the system, can only see those resources assigned – not the incident details… Two Verdugo Staff members are required to have ROSS open and operating at ALL times.

ROSS - Resource Ordering & Status System Verdugo maintains a separate mirrored “CICCS” database in the event that ROSS is not available. Verdugo is “Ordering Point” for incidents and any needed resources within Area C. Incoming Orders for resources outside or Area C comes from: ANF – Incident Management Team Staff REGION I (LAC) – Single Resource (Named Requests / Shopping List), Strike Teams In the Verdugo “catalog” – 1,227 qualified personnel or trainees, for up to 55 “positions”. Ordering within Verdugo System: (818) or RED8 when following FOOTHILL VHF Communications Plan

ROSS - Resource Ordering & Status System Single Resource (Overhead = O#) Requests “Named Request” or “Fill by Position Code Request” Verdugo workflow process: Request received from ANF or REGION I Resource must already be in ROSS! Finance code necessary prior to anyone being contacted. Approval to send is needed by agency Line Operations B.C. Agency must know/understand their own contracts Operations B.C. given information for resource. Resource then contacts Verdugo with travel information. This closes loop. Verdugo enters/updates data into ROSS. Single Resource should only initiate contact with Verdugo after approval process and only then with travel information. Please do not contact Verdugo with a “pre-alert” of a possible incoming request; Verdugo cannot act on any information until a formal request is received and subsequently approved.

ROSS - Resource Ordering & Status System Request is received via FAX or or ROSS REGION I ANF Verdugo processes request Obtains: Order #, Request #, Type of Assistance, FINANCE CODE Faxes / s all pertinent information to Line B.C. for APPROVAL Did Verdugo Receive Line B.C. Approval? No? ANF: Notify via Phone REGION I: Notify via ROSS as Unable to Fill (UTF) Yes? Verdugo creates CAD Incident and logs data into CICCS database and ROSS ANF: Notify via Phone once Travel Info. is received from resource REGION I: Notify via ROSS upon receipt of Travel Info. It is the Operations B.C. responsibility to make contact with the Resource or vice-versa for approval to go. In turn, the resource notifies Verdugo they are enroute and provides Travel Information for ROSS

TICP – Tactical Interoperable Communications Plan Most recent communications plans are: UHF plan adopted in May 2014 VHF plan adopted in May 2014 FOOTHILL Comm. Plan – ZONE 7 VHF ALL VHF, 1 st alarm onwards – BRUSH Fires in Area C Admin. Channel will be RED-8 to Verdugo Review the VHF communications plan! Always, know who is working around or with you at the incident and how to communicate with them either by radio or by cell!

TICP – Tactical Interoperable Communications Plan Mobile/Portables At minimum programmed with VHF ZONES 1, 2, 3 and FOOTHILL Plan (ZONE 7) Frequency Assignments Immediate – Assigned a Travel Channel CESRS Direct ( ) until going on-scene/staging [BIG TICP ZONE 14 (34), ZONE 15 (46)] FDUMA Direct ( , used only within LAC) STL monitor/remains on RED1 as long as possible. Report time of departure/onscene to Verdugo Form-up prior to onscene at incident/staging Planned – Assigned a Travel Channel CESRS Direct ( ) until going on-scene/staging [BIG TICP ZONE 14 (34), ZONE 15 (46)] FDUMA Direct ( , used only within LAC) STL monitor/remains on RED1 as long as possible. Report time of departure/onscene to Verdugo At incident make contact with agency on their assigned channel.

Standing Orders STEN Leaders or Single Resource Check-in twice per day at minimum directly with Verdugo at (818) Preferably every six hours. Updates shall consist of team status, conditions of incident, and team activity within the incident. Information is critical to Stakeholders (City Managers, Fire Chief’s, City Council, etc.) Control the flow of information… Single Resource at least once per day to the extent possible. Whether STEN or Single Resource: If re-dispatched to a new/different location, you MUST contact Verdugo Fire prior to changing assignments! Coordinate your “meet points” with Trainees. Not all Trainees will be immediately adjacent to the STEN Leader location. This is especially critical when Immediate Need is launched!

Activity

Review Agreements CA Master Mutual Aid Agreement, CMA ANF Agreement LFD Agreement LAC Agreements 7-Points of Light Agreement CICCS – STEN Refresher PPT’s at Unified Response website

Did you know? Did you know, because Verdugo “touches” Area A and Area B that each Operational Area can be contacted on a one time basis for up to five (5) closest STRIKE TEAMS (25 Engines) or TASK FORCES from each area under Mutual Aid for a Verdugo incident? And, vice-versa… Mutual Aid means = “non-reimbursable” Local AREA Coordinators XLA, XLB, etc., can refuse request; no obligation. CFAA = “Assistance by Hire (ABH) First 12 hours are “free”; if resources are committed beyond 12 hours, costs are associated from time of their dispatch SO! What question will be asked when an I.C. requests outside agency resources into the Verdugo System?

Voluntary Mutual Aid Voluntary Mutual Aid Agreement – generally a local, formal and standing agreement for cooperative emergency management on a continuing basis, regardless of jurisdictional boundary. Automatic Aid Agreement – e.g., Unified Response (Fire Category), dispatch of the closest engine to an incident regardless of jurisdiction, simultaneously dispatched with the jurisdictional agency Initial Action Agreement – e.g., Use of the closest available unit until the jurisdictional agency arrives. The first-in unit is only in charge until the primary agency arrives on-scene Ad Hoc Mutual Aid – requested only when an emergency occurs, where no other pre-existing agreement covers a situation, and used as needed; generally referred to as Mutual Aid Voluntary and non-reimbursable!

Voluntary Mutual Aid CA Master Mutual Aid Agreement An agreement made and entered into by and between the State of California and various political subdivisions, municipal corporations, and other public agencies under the California Emergency Services Act Requests made by another agency for Verdugo resources or by a Verdugo agency for outside system resources under Master Mutual Aid = “voluntary and not reimbursable” Reimbursement may be provided pursuant to a Governor’s or Presidential disaster proclamation or when certain other conditions exist.

Voluntary Mutual Aid CA Master Mutual Aid Agreement (CMA) Seven Points of Light Agreement – utilizes provisions of the agreement to apply state resources to a local incident (i.e., CDF resources to BRK) prior to a declaration of “local emergency”. It is applicable to certain guidelines: From the time of initial attack to the point of determination that an incident is likely to exceed the ability of a local government entity to control, state resources can be made available to local fire agencies through a variety of agreements (e.g., automatic aid, wildland protection, mutual threat zone, etc.) In the absence of an emergency that is beyond the ability of a local government entity to control, mutual aid shall not be used to shift the costs of fire suppression to another political entity. Mutual aid fire suppression resources committed to an incident, under the provisions of the California Fire Service and Rescue Emergency Mutual Aid System's Mutual Aid Plan, should only be used during the period of the emergency. The period of emergency constitutes the time during which mutual aid resources are necessary to prevent imminent or perceived imminent threat to life and property. As the emergency condition de-escalates, the mutual aid resources should be released, based on a preplanned demobilization process.

Voluntary Mutual Aid Entities should make maximum use of locally available facilities, equipment and services. Requests for firefighting resources, for response to an emergency that is beyond the ability of a local government entity to control, are to be based on the "closest resources" concept and initiated through proper mutual aid channels. Federal fire suppression resources, which may be the “closest resources”, are not part of the California Fire Service and Rescue Emergency Mutual Aid System. Assistance provided by these resources will be on an assistance-by- hire arrangement, unless obtained through other preexisting agreements. Local government agencies receiving mutual aid are responsible for providing logistical support to the mutual aid personnel and equipment.

Obligatory Mutual Aid Mutual Aid under a “State of War Emergency” is deemed obligatory Mutual Aid under a declared local governmental agency “State of Emergency” may be obligatory.

Reimbursable Aid California Fire Assistance Agreement (CFAA) – An agreement made and entered into by and between the State of California, CALOES, and the five forest agencies (CDF, USDA Forest Service, USDI National Park Services, BLM, and Fish and Wildlife Service) for purpose of coordinating use and reimbursement for use of local government Fire and Rescue resources as wildfire incidents. First 12 hours are “free”; thereafter, costs are from time of their dispatch Assistance by Hire (ABH) Assistance by hire resources are those elements of personnel and equipment which are provided by cooperating agencies through specific arrangements. Where such arrangements exist, parties should be thoroughly familiar with, and aware of, provisions (contracts) at time of request and response. Fire Management Assistance Grant (FMAG) – to fund fire suppression activities by state agencies and local governments for wildfires that threaten to become major disasters; an incident must be declared eligible by FEMA during the incident period of the fire for up to 75% reimbursement of costs associated with the incident.

Questions?