ID
8-508-1266
Name
Urban Search and Rescue Incident Support Team
Status
Published
Version
1.0
Updated
6/8/2021 10:08:42 AM
Original Release
06/08/2021
Last Major Release
06/08/2021
Description
The Urban Search and Rescue (US&R) Incident Support Team (IST) augments incident management efforts by providing subject matter expertise to existing command and control operations during incidents or events that could require large-scale search and rescue resources
Resource Category
Search and Rescue
Primary Core Capability
Mass Search and Rescue Operations
Secondary Core Capability
 
Resource Kind
Team
Overall Function
The US&R IST: 1. Deploys to supplement the management and application of search and rescue resources in emergency response operations, incidents, or planned events requiring large-scale search and rescue operations 2. Supports a local Incident Commander (IC), Unified Command, Incident Management Team (IMT), or Emergency Operations Center (EOC) in managing an incident or event 3. Plans for, manages, and tracks tactical resources that the Authority Having Jurisdiction (AHJ) and other supporting organizations provide 4. Performs Command, Operations, Planning, Logistics, Finance/Administration, Safety, Public Information, and Liaison functions as the incident requires, in support of the AHJ’s existing response enterprise 5. Coordinates with IMT(s), EOC personnel, AHJ, and agency administrators regarding incident management objectives and support 6. Has short-team and long-team configurations; long-team configurations incorporate additional positions and capabilities to meet incident needs based on the results of a complexity analysis that includes such factors as number of resources, area of operations, and complexity of operations
Composition and Ordering Specifications
1. Discuss logistics for deploying this team, such as working conditions, communications, length of deployment, security, lodging, transportation, and meals, prior to deployment 2. Discuss team relief/replacement and team member overlap to ensure smooth operational transitions 3. Discuss staffing and equipment needs based on incident complexity, such as the need for deputies and assistants or the need to provide 24-hour coverage 4. Discuss team responsibilities and authority throughout the incident 5. Discuss existing incident command structures and other coordinating entities—such as Federal, state, local, tribal, and territorial governments, IMTs, EOCs, Multiagency Coordination Groups (MAC Groups), and Joint Information Systems (JIS)—that this team will support 6. Discuss the need to include trainees on this team 7. Discuss the process and expectations for documentation; ordering, tracking, and managing resources; tracking and managing personnel hours; ensuring adequate personnel accountability; ensuring personnel safety and welfare; managing contracts and Memorandums of Understanding (MOU); and managing communications processes and equipment
Supporting Core Capabilities
None
Components
Component Notes  
MINIMUM PERSONNEL PER TEAMNot Specified
Component Types
Type Attribute
Type 130
Type 215
Type 312
Type 48
MANAGEMENT AND OVERSIGHT PERSONNEL PER TEAMAn additional IC (Type 1, 2, or 3) can fill the role of deputy IC if the IC or requesting jurisdiction/entity specifies.
Component Types
Type Attribute
Type 1Same as Type 2, PLUS: 1 – National Incident Management System (NIMS) Type 1 Incident Commander
Type 21 – NIMS Type 2 Incident Commander
Type 3Same as Type 4
Type 41 – NIMS Type 3 Incident Commander
SUPPORT PERSONNEL PER TEAM1. An IST of a different complexity type may manage or support the incident until an appropriately typed IST can deploy. 2. For Types 1–3, Command and General Staff type should match the IST type, though subordinate positions, such as Unit Leaders, are not tied to incident complexity and may be of a single type. 3. Personnel meet the minimum qualifications indicated in the relevant position qualification system, such as the National Qualification System (NQS). Position typing schemes may vary depending on the qualification system the AHJ uses. 4. For Types 1–3, teams include two or more Operations Section Chiefs, who may serve as deputy, as Operations Section Chief for different operational periods, or as a planning assistant. 5. Teams may include additional positions, such as US&R Technical Specialist or other IMT unit-level or specialist positions. 6. The computer technical specialist is not a NIMS typed position.
Component Types
Type Attribute
Type 1Same as Type 2, PLUS: 1 – NIMS Type 1 Public Information Officer 1 – NIMS Type 1 Safety Officer 1 – NIMS Type 1 Liaison Officer 2 – NIMS Type 1 Operations Section Chief 1 – NIMS Type 1 Planning Section Chief 1 – NIMS Type 1 Logistics Section Chief 1 – NIMS Type 1 Finance/Administration Section Chief 1 – NIMS Type 1 Air Operations Branch Director 1 – NIMS Type 1 Communications Unit Leader 1 – NIMS Type 1 Situation Unit Leader 1 – NIMS Type 1 Resources Unit Leader 1 – NIMS Type 1 Geographic Information Systems Specialist 1 – Computer technical specialist
Type 21 – NIMS Type 2 Public Information Officer 1 – NIMS Type 2 Safety Officer 1 – NIMS Type 2 Liaison Officer 2 – NIMS Type 2 Operations Section Chief 1 – NIMS Type 2 Planning Section Chief 1 – NIMS Type 2 Logistics Section Chief 1 – NIMS Type 2 Finance/Administration Section Chief 1 – NIMS Type 1 Air Operations Branch Director 1 – NIMS Type 2 Communications Unit Leader 1 – NIMS Type 1 Situation Unit Leader 1 – NIMS Type 1 Resources Unit Leader 1 – NIMS Type 1 Geographic Information Systems Specialist 1 – Computer technical specialist
Type 3Same as Type 4, PLUS: 1 – NIMS Type 3 Communications Unit Leader 1 – NIMS Type 1 Situation Unit Leader 1 – NIMS Type 1 Resources Unit Leader
Type 41 – NIMS Type 3 Public Information Officer 1 – NIMS Type 3 Safety Officer 1 – NIMS Type 3 Liaison Officer 1 – NIMS Type 3 Operations Section Chief 1 – NIMS Type 3 Planning Section Chief 1 – NIMS Type 3 Logistics Section Chief 1 – NIMS Type 3 Finance/Administration Section Chief
Personnel Management Capabilities Per TeamPersonnel criteria are flexible parameters for identifying the necessary incident management capabilities.
Component Types
Type Attribute
Type 1Typically manages more than 500 personnel
Type 2Typically manages up to 500 personnel
Type 3Typically manages up to 200 personnel
Type 4Typically manages up to 80 personnel
Electronics and Office Equipment Per TeamRefer to FEMA US&R/State Urban Search and Rescue (SUSAR) cache lists for detailed equipment guidelines.
Component Types
Type Attribute
Type 1Same as Type 2
Type 2Same as Type 3
Type 3Same as Type 4
Type 4Electronic and office equipment commensurate with the mission assignment
PERSONAL PROTECTIVE EQUIPMENT (PPE) PER TEAM MEMBER1. PPE requirements depend on the position, the nature of the incident, and the environmental conditions experienced or expected. Not all positions require PPE. 2. PPE is mission specific and may vary by work environment; it includes protective footwear, protective clothing for skin exposure, eye and ear protection, respirators, gloves, and masks.
Component Types
Type Attribute
Type 1Same as Type 2
Type 2Same as Type 3
Type 3Same as Type 4
Type 4Appropriate PPE, if necessary
COMMUNICATIONS EQUIPMENT PER TEAM1. Refer to FEMA US&R/SUSAR cache lists for detailed equipment guidelines. 2. The team arrives with or can order portable radios, repeaters, portable cellular towers, mobile communications units, mobile command posts, and other communications support equipment as necessary to provide communications for the incident.
Component Types
Type Attribute
Type 1Same as Type 2
Type 2Same as Type 3
Type 3Same as Type 4
Type 4Communications equipment commensurate with the mission assignment
Administrative Support Supplies Per Team1. Refer to FEMA US&R/SUSAR cache lists for detailed equipment guidelines.
Component Types
Type Attribute
Type 1Same as Type 2
Type 2Same as Type 3
Type 3Same as Type 4
Type 4Basic office supplies and electronics equipment necessary to support development and distribution of plans, maps, and other mission needs for 72 hours of continuous operations
878878
Notes
References
Reference
FEMA, NIMS 509: Air Operations Branch Director
FEMA, NIMS 509: Air Support Group Supervisor
FEMA, NIMS 509: Air Tactical Group Supervisor
FEMA, NIMS 509: Communications Technician
FEMA, NIMS 509: Communications Unit Leader
FEMA, NIMS 509: Compensation/Claims Unit Leader
FEMA, NIMS 509: Cost Unit Leader
FEMA, NIMS 509: Demobilization Unit Leader
FEMA, NIMS 509: Documentation Unit Leader
FEMA, NIMS 509: Facilities Unit Leader
FEMA, NIMS 509: Finance/Administration Section Chief
FEMA, NIMS 509: Food Unit Leader
FEMA, NIMS 509: Geographic Information Systems Analyst
FEMA, NIMS 509: Geographic Information Systems Specialist
FEMA, NIMS 509: Ground Support Unit Leader
FEMA, NIMS 509: Incident Commander
FEMA, NIMS 509: Liaison Officer
FEMA, NIMS 509: Logistics Section Chief
FEMA, NIMS 509: Medical Unit Leader
FEMA, NIMS 509: Operations Section Chief
FEMA, NIMS 509: Ordering Team Leader
FEMA, NIMS 509: Planning Section Chief
FEMA, NIMS 509: Procurement Unit Leader
FEMA, NIMS 509: Public Information Officer
FEMA, NIMS 509: Resources Unit Leader
FEMA, NIMS 509: Safety Officer