Transcription of ICS Review Document
{{id}} {{{paragraph}}}
ICS Review Document EXTRACTED FROM - E/L/G 0300 INTERMEDIATE incident command system FOR EXPANDING INCIDENTS, ICS 300 March 2018 ICS Review Document EXTRACTED FROM - E/L/G 0300 Intermediate incident command system for Expanding Incidents, ICS 300 2 This page intentionally left blank. March 2018 ICS Review Document EXTRACTED FROM - E/L/G 0300 Intermediate incident command system for Expanding Incidents, ICS 300 3 Table of Contents National incident Management system .. 5 NIMS Management Characteristics .. 5 Common Terminology .. 5 Modular Organization .. 6 Management by Objectives .. 6 incident Action Planning .. 6 Manageable Span of Control .. 7 incident Facilities and Locations .. 7 Comprehensive Resource Management .. 7 Integrated Communications .. 7 Establishment and Transfer of command .. 8 Unified command .. 8 Chain of command and Unity of command .. 8 Accountability .. 8 Dispatch/Deployment .. 8 Information and Intelligence Management .. 10 ICS History and Features.
Intermediate Incident Command System for Expanding Incidents, ICS 300 7 . Every incident should have an action plan; however, not all incidents need written plans. The necessity for written plans depends on incident complexity, command decisions, and legal requirements. Formal IAPs are not always developed for the initial operational
Domain:
Source:
Link to this page:
Please notify us if you found a problem with this document:
{{id}} {{{paragraph}}}