| 22 | | == Emergency Management == |
| 23 | | === ICS / NIMS === |
| 24 | | FEMA (US Emergency Response) free online training (exam available only for US citizens) |
| 25 | | * [http://training.fema.gov/EMIWeb/IS/IS100b.asp ICS 100] - Introduction to ICS (Incident Command System) |
| 26 | | * [http://training.fema.gov/emiweb/is/is700a.asp ICS 700] - Introduction to NIMS (National Incident Management System) |
| 27 | | * [http://training.fema.gov/emiweb/is/is800b.asp ICS 800] - Introduction to NRF (National Response Framework) |
| 28 | | * [http://training.fema.gov/EMIWeb/IS/is101a.asp ICS 101] - Deployment Basics (individual preparation) |
| 29 | | * [http://training.fema.gov/emiweb/is/is701a.asp ICS 701] - NIMS Multiagency Coordination System |
| 30 | | * [http://training.fema.gov/emiweb/is/is702a.asp ICS 702] - NIMS Public Information Systems |
| 31 | | * [http://training.fema.gov/emiweb/is/is703a.asp ICS 703] - NIMS Resource Management |
| 32 | | * [http://training.fema.gov/emiweb/is/is704.asp ICS 704] - NIMS Communications and Information Management |
| 33 | | * [http://emilms.fema.gov/IS100b/indexMenu.htm ICS 200] - Single Resources and Initial Action Incidents (for supervisors) |
| 34 | | |
| 35 | | Forms: |
| 36 | | * http://training.fema.gov/EMIWeb/IS/ICSResource/ICSResCntr_Forms.htm |
| 37 | | |
| 38 | | Some brainstorming on a database schema for ICS: IncidentCommandSystem |
| 39 | | |
| 40 | | NB What is called an 'Incident' in ICS is what Sahana calls a 'Project'. |
| 41 | | * How can we have that relabelled for an ICS deployment & not have it confused with 'Incident Reports' from the general public? |
| 42 | | |
| 43 | | ==== Preparedness ==== |
| 44 | | ''Effective emergency management and incident response activities begin with a host of preparedness activities conducted on an ongoing basis, in advance of any potential incident. Preparedness involves an integrated combination of '''assessment'''; '''planning'''; '''procedures and protocols'''; '''training and exercises'''; '''personnel qualifications'''; '''equipment certification'''; and evaluation and revision.'' |
| 45 | | * Protocols are rules for knowing what level of delegated authority a trained person has to operate before referring to a superior. |
| 46 | | * Credentialing involves an objective evaluation and documentation of an individual's: |
| 47 | | * Current certification, license, or degree |
| 48 | | * Training and experience |
| 49 | | * Competence or proficiency |
| 50 | | * Medical Fitness |
| 51 | | * Procedural Documents |
| 52 | | * Standard Operating Procedure or Operations Manual: ''Complete reference document that provides the purpose, authorities, duration, and details for the preferred method of performing a single function or a number of interrelated functions in a uniform manner.'' |
| 53 | | * Field Operations Guide or Incident Management Handbook: ''Durable pocket or desk guide that contains essential information required to perform specific assignments or functions.'' |
| 54 | | * Mobilization Guide: ''Reference document used by agencies/organizations outlining agreements, processes, and procedures used by all participating organizations for activating, assembling, and transporting resources.'' |
| 55 | | * Job Aid: ''Checklist or other visual aid intended to ensure that specific steps for completing a task or assignment are accomplished. Job aids serve as training aids to teach individuals how to complete specific job tasks.'' |
| 56 | | |
| 57 | | We should support Exercises easily (prefix on messages, watermark on records). |
| 58 | | These should be filtered out when not in exercise mode (like deletion_status). |
| 59 | | ==== Communications and Information Management ==== |
| 60 | | ''Emergency management and incident response activities rely on communications and information systems that provide a common operating picture to all command and coordination sites. NIMS describes the requirements necessary for a standardized framework for communications and emphasizes the need for a '''common operating picture'''. This component is based on the concepts of '''interoperability''', '''reliability''', '''scalability''', and '''portability''', as well as the resiliency and '''redundancy''' of communications and information systems.'' |
| 61 | | |
| 62 | | Common operating picture including the '''availability and location of resources''' and the '''status of assistance requests'''. |
| 63 | | |
| 64 | | Standardised Forms: |
| 65 | | * http://training.fema.gov/EMIWeb/IS/ICSResource/ICSResCntr_Forms.htm |
| 66 | | |
| 67 | | ==== Resource Management ==== |
| 68 | | ''Resources (such as '''personnel''', '''equipment''', '''supplies''' and '''facilities''') are needed to support critical incident objectives. The flow of resources must be fluid and adaptable to the requirements of the incident. NIMS defines standardized mechanisms and establishes the resource management process to '''identify requirements''', '''order and acquire''', '''mobilize''', '''track and report''', '''recover and demobilize''', '''reimburse''', and '''inventory''' resources.'' |
| 69 | | |
| 70 | | [[Image(Resource Ordering.png)]] |
| 71 | | |
| 72 | | '''Credentialing''': |
| 73 | | * entails the objective evaluation and documentation of an individual’s current certification, license, or degree; training and experience; and competence or proficiency to meet nationally accepted standards, provide particular services and/or functions, or perform specific tasks under specific conditions during an incident. |
| 74 | | |
| 75 | | Resources are identified by standard: |
| 76 | | * '''Type''' - specifically defines the level of capability a resource has. Type may vary by power, size, or capacity. Therefore, assigning a Type 1 label to a resource implies that it has a greater level of capability than a Type 2 of the same resource. The National Resource Typing definitions are broken into four distinct types. In some cases, a resource may have less than or more than four types. The type assigned to a resource or a component is based on a minimum level of capability described by the identified metric(s) for that resource. |
| 77 | | |
| 78 | | * '''Category''' - describes the function for which a resource would be most useful (list as of June 2007): |
| 79 | | * Transportation |
| 80 | | * Communications |
| 81 | | * Public works and engineering |
| 82 | | * Firefighting |
| 83 | | * Information and planning |
| 84 | | * Law enforcement and security |
| 85 | | * Mass care |
| 86 | | * Resource management |
| 87 | | * Health and medical |
| 88 | | * Search and rescue |
| 89 | | * Hazardous materials response |
| 90 | | * Food and water |
| 91 | | * Energy |
| 92 | | * Public information |
| 93 | | * Animals and agricultural issues |
| 94 | | * Volunteers and donations |
| 95 | | |
| 96 | | * '''Kind''' (broad classes that characterize like resources): |
| 97 | | * teams |
| 98 | | * equipment |
| 99 | | * supplies |
| 100 | | * vehicles |
| 101 | | * aircraft |
| 102 | | |
| 103 | | * '''Tier''': |
| 104 | | * Tier-I (Capable of being requested for National responses) |
| 105 | | * Tier-II (Capable only for Intra-State responses) |
| 106 | | |
| 107 | | |
| 108 | | Although different formats may exist, every '''Resource Order''' should contain the essential elements of information (a good mnemonic is SALTT: Size, Amount, Location, Type, Time): |
| 109 | | * Incident name |
| 110 | | * Order and/or request number (if known or assigned) |
| 111 | | * Date and time of order |
| 112 | | * Quantity, kind, and type or detailed mission description (Resources should be ordered by Task Forces or Strike Teams when appropriate.) Include any special support needs. |
| 113 | | * Reporting location (specific) |
| 114 | | * Requested time of delivery (specific, immediate vs. planned, not ASAP) |
| 115 | | * Radio frequency to be used |
| 116 | | * Person/title placing request |
| 117 | | * Callback phone number or radio designation for clarifications or additional information |
| 118 | | |
| 119 | | Mobilization notifications should include: |
| 120 | | * The date, time, and place of departure. |
| 121 | | * Mode of transportation to the incident. |
| 122 | | * Estimated date and time of arrival. |
| 123 | | * Reporting location (address, contact name, and phone number). |
| 124 | | * Anticipated incident assignment. |
| 125 | | * Anticipated duration of deployment. |
| 126 | | * Resource order number. |
| 127 | | * Incident number. |
| 128 | | * Applicable cost and funding codes. |
| 129 | | |
| 130 | | '''Resource Tracking''': |
| 131 | | * The Planning Section is responsible for tracking all resources assigned to the incident and their status: |
| 132 | | * Assigned – Currently working on an assignment under the direction of a supervisor |
| 133 | | * Available – Ready for immediate assignment and has been issued all required equipment |
| 134 | | * Out of Service – Not available or ready to be assigned (e.g., maintenance issues, rest periods) |
| 135 | | * The Operations Section is responsible for tracking the movement of resources within the Operations Section itself. |
| 136 | | |
| 137 | | ==== Command and Management ==== |
| 138 | | ''The Command and Management component of NIMS is designed to enable effective and efficient incident management and coordination by providing a flexible, standardized incident management structure. The structure is based on three key organizational constructs: the '''Incident Command System''', '''Multiagency Coordination Systems''', and '''Public Information'''.'' |
| 139 | | * Common Language (plain English) |
| 140 | | * Facility types (Office Types? Different Icons): |
| 141 | | * Incident Command Posts, Bases, Camps, Staging Areas, mass casualty triage areas, point-of-distribution sites |
| 142 | | * Manage by Objectives |
| 143 | | * Incident Action Plan (Document Library + Wiki?) |
| 144 | | * Flexible Org charts (predefined optional roles to delegate areas to) |
| 145 | | * each person has only a single superior |
| 146 | | * manageable span of control (3-7 subordinates) |
| 147 | | * Staff need to check-in & check-out (like we do for Shelters) |
| 148 | | * Provide a 'Public Bulletin' area of the site (frontpage?) |
| 149 | | |
| 150 | | '''Incident Action Plan''': |
| 151 | | * Development of incident objectives and strategy. |
| 152 | | * Development of tactics and resource assignments. |
| 153 | | * Detailed incident and resource assessment, including safety concerns. |
| 154 | | * Required logistical support. |
| 155 | | * Consideration of public information and interagency issues. |
| 156 | | * Documentation of assignments and required support on the written IAP. |
| 157 | | * Monitored implementation. |
| 158 | | |
| 159 | | '''Check-In''': |
| 160 | | * Date and time of check-in. |
| 161 | | * Name of resource. |
| 162 | | * Home base. |
| 163 | | * Departure point. |
| 164 | | * Order number and resource filled. |
| 165 | | * Resource Leader name and personnel manifest (if applicable). |
| 166 | | * Other qualifications. |
| 167 | | * Travel method. |
| 168 | | |
| 169 | | '''Demobilization''': |
| 170 | | * Performance Rating by Senior (& signed by Individual) |
| 171 | | |
| 172 | | [[Image(Demobilization Responsibilities.png)]] |
| 173 | | |
| 174 | | '''Requests for assistance''' (outside jurisdiction) should include the following information: |
| 175 | | * The type of incident |
| 176 | | * The time that the incident occurred or is expected to occur |
| 177 | | * The actions already taken |
| 178 | | * The areas and number of people involved |
| 179 | | * Estimates of loss of life, injuries, and extent of damage |
| 180 | | * The type and amount of assistance required |
| 181 | | * A contact for followup questions |
| 182 | | |
| 183 | | '''Public Information''': |
| 184 | | * Gathering information |
| 185 | | * Verifying information |
| 186 | | * Coordinating information (inc key messages, sign-off) |
| 187 | | * Disseminating information |
