Embedded Files
**Follow along in your Student Manual with the screen cast presentation**
**Follow along in your Student Manual with the screen cast presentation**
UNIT CONTENT (CLICK HERE)
UNIT CONTENT (CLICK HERE)
Unit Terminal Objective
Given a simulated scenario, identify roles and reporting relationships under a Unified Command that involves agencies within the same jurisdiction and under multi-jurisdictional conditions.
Unit Enabling Objectives
1. Explain how ICS fits into the Command and Coordination component of NIMS.
2. Explain reporting relationships and information flow within the organization.
3. Identify ICS supervisory positions and titles.
4. Explain considerations for developing an organizational structure that supports the incident and delegating authority to the lowest practical level.
5. Identify the primary features of Unified Command.
6. Explain how Unified Command functions on a multijurisdictional or multiagency incident.
Methodology
This unit uses lecture, activities, and group discussion to identify roles and reporting relationships under a Unified Command that involves agencies within the same jurisdiction and under multijurisdictional conditions.
ACTIVITY 2.1: FUNDAMENTALS REVIEW INSTRUCTION (CLICK HERE)
ACTIVITY 2.1: FUNDAMENTALS REVIEW INSTRUCTION (CLICK HERE)
Purpose:
Purpose:
The purpose of this activity is to provide you with an opportunity to apply what you have learned about fundamental ICS concepts to an explosion and fire incident at a fixed facility with a large volume of hazardous materials.
Objective:
Objective:
• To apply key Unified Command principles.
Instructions:
Instructions:
Work in teams to complete the following activity:
Review the following:
Scenario
Current Resources
Scenario map
Complete the following steps:
Who has a stake in the incident? What agencies, organizations or groups are impacted by this incident?
Who are the assisting and cooperating agencies? What agencies are providing tactical resources (Assisting) or other types of support (Cooperating)?
Is this a Single or Unified Command managed incident?
If Single Command, who is the Incident Commander and why?
If Unified Command, who are the members and why?
Draw an Organization Chart, using the ICS 207 in your Google Workbook, for your Incident Command or Unified Command to reflect the incident as it currently stands.
Identify any unique management challenges and/or safety issues that this scenario presents.
Record your results in your Google Workbook.
Select a spokesperson and be prepared to present in 45 minutes.
Your spokesperson should be able to explain the rationale for the group’s decisions.
ACTIVITY 2.1: SCENARIO (CLICK HERE)
ACTIVITY 2.1: SCENARIO (CLICK HERE)
At 0730 hours on May 18, 2020 a 2,000 gallon tanker truck carrying waste oil backed into a fixed tank and caused an explosion and subsequent fire. 2 workers were injured and the driver of the truck died from the explosion. The facility collects and processes waste oil, antifreeze and other automotive waste products. Quantities involved ranged from 60,000 – 90,000 gallons of mostly waste motor oil and antifreeze.
Debris from the explosion traveled 2000 feet in all directions impacting a large electrical substation .3 miles to the east. Several power poles were damaged and power outages are reported in the area.
Weather: Current conditions are 50 degree F, light rain with a forecast of ¼ - ½ inch possible today after 5:00PM. Winds are light 3-5 mph with gust of 8 mph from the south.
Commuter traffic is stopped on I-205 and Hwy 212/224 is also stopped in both directions.
A large volume of black smoke is drifting to the north towards Clackamas High School. **School is in session**
Resources Assigned:
Clackamas Fire District #1 Units on Scene
Engine 308 (first due) - 4ppl Battalion Chief 302 – 1ppl
Engine 306 – 4ppl Battalion Chief 301 – 1ppl
Ladder Truck 304 – 4ppl Hazmat 303 – 4ppl
Heavy Rescue 305 – 4ppl Ladder Truck 319 – 4ppl
Engine 307 – 4ppl Engine 301 – 4ppl
Mutual Aid Units On Scene
Gladstone Fire Engine 391 – 3 ppl
Clackamas County’s DTD (Dept. of Transportation and Development)
2 Units – 2ppl
Police Units On Scene
OSP 231 – 1ppl OSP 212 – 1ppl
Clackamas County Sheriff Units On Scene
CSD 121 Deputy CSD 143 Deputy
In addition to the resources on scene, the following resources have been ordered:
OSFM Hazmat Team – 8ppl
ODOT – Traffic Units – 2 Units
Clackamas County’s DTD (Dept. of Transportation and Development) Supervisor
AMR - Medic Unit (Ambulance) – 2ppl
*See Unit 2 Map for more information*
Scenario Maps
Scenario Maps
ICS-300 Carpenter Rd Fire Map Ortho Unit 2.pdfICS-300 Carpenter Rd Fire Map OSM Unit 2.pdfHandout 2-1: Operational Period Planning Cycle (Planning P)
Handout 2-1: Operational Period Planning Cycle (Planning P)
Planning from ICS300_Complete_IG.pdfHandout 2-2: Incident Complexity (CLICK HERE)
Handout 2-2: Incident Complexity (CLICK HERE)
“Incident complexity” is the combination of involved factors that affect the probability of control of an incident. Many factors determine the complexity of an incident, including, but not limited to, area involved, threat to life and property, political sensitivity, organizational complexity, jurisdictional boundaries, values at risk, weather, strategy and tactics, and agency policy.
Incident complexity is considered when making incident management level, staffing, and safety decisions.
Various analysis tools have been developed to assist consideration of important factors involved in incident complexity. Listed below are the factors that may be considered in analyzing incident complexity:
Community and responder safety
Impacts to life, property, environment, and the economy
Potential hazardous materials
Weather and other environmental influences
Likelihood of cascading events
Potential crime scene (including terrorism)
Political sensitivity, external influences, and media relations
Area involved, jurisdictional boundaries
Availability of resources
Potential to extend into multiple Operational Periods
Facilitated Activity: Matching Position Titles
Facilitated Activity: Matching Position Titles
Unit 2 FA from ICS300_Complete_IG (1).pdfICS300_ICS-300 Appendix.pdfPage updated
Google Sites
Report abuse