School Safety Specialist Day 2 – Incident Management - PowerPoint PPT Presentation

school safety specialist day 2 incident management n.
Download
Skip this Video
Loading SlideShow in 5 Seconds..
School Safety Specialist Day 2 – Incident Management PowerPoint Presentation
Download Presentation
School Safety Specialist Day 2 – Incident Management

play fullscreen
1 / 104
School Safety Specialist Day 2 – Incident Management
147 Views
Download Presentation
hallam
Download Presentation

School Safety Specialist Day 2 – Incident Management

- - - - - - - - - - - - - - - - - - - - - - - - - - - E N D - - - - - - - - - - - - - - - - - - - - - - - - - - -
Presentation Transcript

  1. School Safety Specialist Day 2 – Incident Management

  2. Introduction Compelling Reasons to Care • As schools our main focus is not on the safety of students – it is on student academic achievement. • "What we do in the name of health, safety, and well-being are linked with teaching and learning. Teaching and learning can't take place if students aren't healthy, aren't physically and mentally fit, or aren't safe."William Modzeleski, Director, Safe and Drug-Free School Program, U.S. Department of Education

  3. Introduction Compelling Reasons to Care • There are statutory requirements: • Texas Education Code Chapter 37 • Texas Education Code Chapter 11 • Texas Education Code Chapter 4 • National Incident Management System • Texas and National Response Plans

  4. Introduction Course Benefits • Conforms to intent of SB-11. • NIMS Compliance: IS-800 (Day 1) plus IS 700, ICS 100 and ICS 200 (this course) provides training required for NIMS compliance in 2006. • This training will also prepare you to work with your community in a disaster or emergency.

  5. Introduction Course Content • IS 700 – National Incident Management System, An Introduction • IS 100 - Incident Command System (ICS) • IS 200 – ICS for Single Resources and Initial Action Incidents

  6. NIMS Introduction to NIMS • Comprehensive, national approach to incident management. • Applicable across all jurisdictions and functions • Improve coordination and cooperation between entities.

  7. NIMS NIMS Concepts and Principles • Flexible framework that applies to all phases of incident management. • Standardized organizational structures, processes, procedures and systems to promote interoperability

  8. NIMS NIMS Components • Command and management • ICS • Multi-agency coordination systems • Public information systems • Preparedness • Planning, training, exercises • Personnel qualification and certification standards • Equipment acquisition and certification standards

  9. NIMS NIMS Components • Resource management • Standards for describing, inventorying, tracking resources • Communications and information management • Interoperability

  10. NIMS NIMS Components • Supporting technologies • Voice and data communications • Recordkeeping and resource tracking • Ongoing management and maintenance • NIMS Integration Center provides strategic direction and oversight

  11. ICS Incident Command System • Standard, on-scene, all-hazard incident management system based on best practices • Integrated management structure • Features • Common terminology • Organizational resources • Manageable span of control • Organizational facilities • Position titles • Incident Action Plan • Integrated communications • accountability

  12. ICS ICS Impact on Local Agencies • All response agencies must use ICS. • Personnel will be required to meet national qualification and certification standards to support an incident that transcends interstate jurisdictions. • State and local jurisdictions will be strongly encouraged to implement mutual aid agreements.

  13. ICS ICS Applications • Fires, hazardous materials releases, oil spills, and multi-casualty incidents • Multi-jurisdictional and multi-agency disasters • Search and rescue operations • Law enforcement incidents • Natural disasters • Planned events

  14. ICS ICS Organization • No correlation with the administrative structure of any other agency or jurisdiction. • ICS organization’s uniqueness helps to avoid confusion over different position titles and organizational structures. • Someone who serves as a chief every day may not hold that title when deployed under an ICS structure.

  15. Universal for all Incident Types

  16. ICS Integrated Management Structure

  17. ICS Modular Organization • Develops in a top-down, modular fashion based on: • size and complexity of the incident. • hazard environment created by the incident.

  18. ICS Modular Organization • Incident objectives determine organizational size. • Only fill necessary functions/positions. • Each element must have a person in charge.

  19. ICS Common Terminology • Reduce confusion between day-to-day activities and incident response duties. • Common terminology • Plain English

  20. FormalCommunication ICS Formal Communication Incident Commander Public Information Officer Command Staff Liaison Officer Safety Officer General Staff Operations Section Chief Planning Section Chief Logistics Section Chief Finance/Admin Section Chief Branch Director Air Operations Branch Director Service Branch Director Support Branch Director

  21. ICS When To Use Formal Communication • Use formal communication when: • Receiving and giving work assignments. • Requesting support or additional resources. • Reporting progress of assigned tasks.

  22. ICS Informal Communication • Is used to exchange incident or event information only. • Is NOT used for: • Formal requests for additional resources. • Tasking work assignments. Within the ICS organization, critical information must flow freely!

  23. ICS Chain of Command Authority Chain of command is an orderly line of authority within the ranks of the incident management organization.

  24. ICS Unity of Command • Under unity of command, personnel: • Report to only one supervisor. • Receive work assignments only from their supervisors.

  25. Incident Command Post Agency 1 Agency 2 Agency 3 Agency 1 Incident Commander Agency 2 Incident Commander Agency 3 Incident Commander ICS Unified Command • Enables all responsible agencies to manage an incident together • Establishes common incident objectives and strategies. • Single command structure allows Incident Commanders to analyze intelligence and make joint decisions. • Maintains unity of command. Each employee reports to only one supervisor.

  26. Unified Command (Representatives From Local Jurisdictions) Finance/ Administration Logistics Planning Operations ICS Unified Command Structure Unified Command does not change other features of ICS.

  27. ICS Area Command • Sets overall strategy and priorities • Allocates resources • Ensures proper management • Objectives are met • Strategies are followed • Does not include Operations Section (On-scene) • Examples • Major incident with multiple ICPs • Health emergency that is not site specific

  28. Area Command Area Command Finance/ Administration Planning Logistics ICP 1 ICP 2 ICP 3 ICS Area Command Configuration with multiple ICPs Configuration without ICP

  29. ICS Manageable Span of Control • Span of control: The number of individuals or resources that one supervisor can manage effectively during an incident. • May vary from 3 to 7 subordinates reporting to a supervisor. • Optimum – 5 subordinates to one supervisor. Supervisor Resource 3 Resource 1 Resource 2

  30. ICS Organizational Facilities • Incident Command Post • Tactical level on-scene incident command and management organization • Located at safe distance but close enough to maintain command • Staging Area • Temporary location of available resources not immediately assigned • Base • Location of primary support activities • Location of Logistics Section • Can support multiple incident sites

  31. ICS Organizational Facilities • Camp • Satellite support sites for food, rest, sanitation, maintenance, etc. • Helibase • Main facility to support helicopter operations • Helispot • Satellite facility to support local helicopter operations (i.e., school yard used for med-evac operations)

  32. ICS Position Titles • ICS position titles: • Provide a common standard for performance expectations. • Help to ensure that qualified individuals fill positions. • Standardize communication. • Describe the responsibilities of the position.

  33. ICS Position Titles

  34. ICS Position Titles [Incident Commander] [Officers] [Chiefs]

  35. ICS Position Titles [Chief] Functional or geographical [Directors] [Supervisors] [Leader] Expand organization to maintain workable Span of control

  36. ICS Task Force • Combination of unlike resources • Must have a leader • Must have communications • Must have transportation • Must be within span of control limits

  37. ICS Fire Suppression Task Force

  38. ICS Strike Team • Same type and kind of resources • Must have a leader • Must have communications • Must have transportation (as required) • Must be within span of control limits

  39. ICS Dozer Strike Team

  40. ICS Advantages of Task Forces & Strike Teams • Helps maintain effective span of control • Assists with resource accountability • More effective use of resources • Effective way of ordering resources • Reduces radio traffic

  41. ICS Incident Commander • First responsible person on the scene • Responsible for on-scene incident management until relieved by a more qualified person or authority is delegated to another person. • Only position that is always staffed in ICS applications

  42. ICS Scope of Authority • An Incident Commander's scope of authority is derived: • From existing laws and agency policies and procedures, and/or • Through a delegation of authority from the agency administrator or elected official.

  43. ICS Authority • Authorityis . . . . . . a right or obligation to act on behalf of a department, agency, or jurisdiction.

  44. Superintendent Incident Commander ICS Delegation of Authority • Grants authority to carry out specific functions. • Issued by chief elected official, chief executive officer, or agency administrator in writing or verbally. • Allows the Incident Commander to assume command. • Does NOT relieve the granting authority of the ultimate responsibility for the incident.

  45. ICS Delegation of Authority is Needed • If the incident is outside the Incident Commander’s home jurisdiction. • When the incident scope is complex or beyond existing authorities. • If required by law or procedures.

  46. ICS Delegation of Authority is Not Needed • If the Incident Commander is acting within his or her existing authorities. • An emergency manager may already have the authority to deploy response resources to a small flash flood. • A fire chief probably has the authority (as part of the job description) to serve as an Incident Commander at a structure fire.

  47. Delegation of Authority ICS Delegation of Authority: Elements • Should include: • Legal authorities and restrictions. • Financial authorities and restrictions. • Reporting requirements. • Demographic issues. • Political implications. • Agency or jurisdictional priorities. • Plan for public information management. • Process for communications. • Plan for ongoing incident evaluation.

  48. ICS Incident Commander Role • The Incident Commander: • Provides overall leadership for incident response. • Delegates authority to others. • Takes general direction from agency administrator/official.

  49. ICS Incident Commander Responsibilities • The Incident Commander is specifically responsible for: • Ensuring incident safety. • Providing information services to internal and external stakeholders. • Establishing and maintaining liaison with other agencies participating in the incident.

  50. ICS Incident Commander Responsibilities • Managing Incident Priorities • Life Safety (victims and responders) • Incident Stability • Preservation of property and environment