Open main menu
Home
Random
Recent changes
Special pages
Community portal
Preferences
About Wikipedia
Disclaimers
Incubator escapee wiki
Search
User menu
Talk
Dark mode
Contributions
Create account
Log in
Editing
Incident Command System
(section)
Warning:
You are not logged in. Your IP address will be publicly visible if you make any edits. If you
log in
or
create an account
, your edits will be attributed to your username, along with other benefits.
Anti-spam check. Do
not
fill this in!
==Composition== === Incident commander === * Single incident commander β Most incidents involve a single [[incident commander]]. In these incidents, a single person commands the incident response and is the decision-making final authority. * Unified command β A [[Unified command (ICS)|unified command]] involves two or more individuals sharing the authority normally held by a single incident commander. Unified command is used on larger incidents usually when multiple agencies or multiple jurisdictions are involved. A Unified command typically includes a command representative from major involved agencies and/or jurisdictions with one from that group to act as the spokesman, though not designated as an Incident Commander. A Unified Command acts as a single entity. It is important to note, that in Unified Command the command representatives will appoint a single operations section chief.<ref>[http://www.fema.gov/pdf/emergency/nims/NIMS_core.pdf National Incident Management System] {{Webarchive|url=https://web.archive.org/web/20120404024237/http://www.fema.gov/pdf/emergency/nims/NIMS_core.pdf |date=4 April 2012 }} β December 2008 Page 51</ref> {{Anchor|Area Command}} * Area command β During multiple-incident situations, an area command may be established to provide for incident commanders at separate locations. Generally, an area commander will be assigned β a single person β and the area command will operate as a logistical and administrative support. Area commands usually do not include an operations function. ===Command staff=== * Safety officer β The safety officer monitors safety conditions and develops measures for assuring the safety of all assigned personnel.<ref>Federal Emergency Management Agency [http://training.fema.gov/position%20specific%20taskbooks/#safety "FEMA Taskbooks"] {{Webarchive|url=https://web.archive.org/web/20110716153908/http://training.fema.gov/position%20specific%20taskbooks/#safety |date=16 July 2011 }}, ''FEMA'', 28 October 2010, accessed 11 December 2010.</ref> * Public information officer β The public information officer (PIO or IO) serves as the conduit for information to and from internal and external stakeholders, including the media or other organizations seeking information directly from the incident or event. While less often discussed, the public information officer is also responsible for ensuring that an incident's command staff are kept apprised as to what is being said or reported about an incident. This allows public questions to be addressed, rumors to be managed, and ensures that other such public relations issues are not overlooked.<ref>Federal Emergency Management Agency [http://training.fema.gov/EMIWeb/IS/ICSResource/Glossary.htm#P "FEMA Glossary"], ''FEMA'', 28 October 2010, accessed 11 December 2010.</ref> * Liaison officer β A liaison serves as the primary contact for supporting agencies assisting at an incident.<ref>Federal Emergency Management Agency [http://training.fema.gov/EMIWEB/IS/ICSResource/ICSResCntr_Glossary.htm#L "FEMA Glossary"] {{Webarchive|url=https://web.archive.org/web/20110116193922/http://www.training.fema.gov/EMIWEB/IS/ICSResource/ICSResCntr_Glossary.htm#L |date=16 January 2011 }}, ''FEMA'', 28 October 2010, accessed 11 December 2010.</ref> ===General staff=== * Operations section chief: Tasked with directing all actions to meet the incident objectives. * Planning section chief: Tasked with the collection and display of incident information, primarily consisting of the status of all resources and overall status of the incident. * Finance/administration section chief: Tasked with tracking incident-related costs, personnel records, requisitions, and administrating procurement contracts required by Logistics. * Logistics section chief: Tasked with providing all resources, services, and support required by the incident. ===200-Level ICS=== At the ICS 200 level, the function of Information and Intelligence is added to the standard ICS staff as an option. This role is unique in ICS as it can be arranged in multiple ways based on the judgement of the Incident Commander and needs of the incident. The three possible arrangements are: * Information & intelligence officer, a position on the command staff. * Information & intelligence section, a section headed by an information & intelligence section chief, a general staff position. * Information & intelligence branch, headed by an information & intelligence branch director, this branch is a part of the planning section. ===300-Level ICS=== At the ICS 300 level, the focus is on entry-level management of small-scale, all-hazards incidents with emphasis on the scalability of ICS. It acts as an introduction to the utilization of more than one agency and the possibility of numerous operational periods. It also involves an introduction to the emergency operations center.<ref>{{cite journal |last = Decker |first = Russell |date = 1 October 2011 |title = Acceptance and utilisation of the Incident Command System in first response and allied disciplines: An Ohio study |url = http://www.ingentaconnect.com/content/hsp/jbcep |journal = Journal of Business Continuity & Emergency Planning |publisher = Henry Stewart Publications |volume = 5 |issue = 3 |pages = 224β230 |doi = 10.69554/GYIW3654 |pmid = 22130340 |access-date = 25 September 2015 |archive-date = 11 February 2016 |archive-url = https://web.archive.org/web/20160211144014/http://www.ingentaconnect.com/content/hsp/jbcep |url-status = live |url-access= subscription }}</ref> ===400-Level ICS=== At the ICS 400 level, the focus is on large, complex incidents.{{Citation needed|date=April 2025}} Topics covered include the characteristics of incident complexity, the approaches to dividing an incident into manageable components, the establishment of an "area command", and the multi-agency coordination system (MACS).{{Citation needed|date=April 2025}}
Edit summary
(Briefly describe your changes)
By publishing changes, you agree to the
Terms of Use
, and you irrevocably agree to release your contribution under the
CC BY-SA 4.0 License
and the
GFDL
. You agree that a hyperlink or URL is sufficient attribution under the Creative Commons license.
Cancel
Editing help
(opens in new window)