Etracker Debug:
	et_pagename = "Journal of Homeland Security and Emergency Management|jhsem|C|[EN]"
	
        
Jump to ContentJump to Main Navigation

Journal of Homeland Security and Emergency Management

Editor-in-Chief: Renda-Tanali, Irmak

Managing Editor: McGee, Sibel, Ph.D.

4 Issues per year

IMPACT FACTOR 2013: 0.272
5-year IMPACT FACTOR: 0.489

Engineering the Incident Command and Multiagency Coordination Systems

Kimberly S Stambler1 / Joseph A Barbera2

1George Washington University

2George Washington University

Citation Information: Journal of Homeland Security and Emergency Management. Volume 8, Issue 1, ISSN (Online) 1547-7355, DOI: 10.2202/1547-7355.1838, August 2011

Publication History

Published Online:
2011-08-23

The initial development of the Incident Command System (ICS) and the Multiagency Coordination System (MACS) was conducted through an extensive research, development, and application program initiated by the United States Forest Service in the 1970s and 1980s. Known as FIRESCOPE (Firefighting Resources of California Organized for Potential Emergencies), the complex development process produced these two major management systems that are now central to the Department of Homeland Security’s National Incident Management System (NIMS). Despite the prominence of NIMS, very little information is widely available regarding the original research and development of ICS and MACS. This paper explores the extensive product development and consensus process used to create ICS and MACS, plus the implementation process that propagated these landmark systems that continue to expand in prominence for incident management and coordination during emergencies and disasters. Through analysis of historical documents and interviews with professionals centrally involved in FIRESCOPE, this paper chronicles the evolution of ICS and MACS, including a summary of their varied courses following the end of the original 10-year FIRESCOPE Program initiative.

Keywords: incident command system; multiagency coordination system; incident management

Comments (0)

Please log in or register to comment.
Users without a subscription are not able to see the full content. Please, subscribe or login to access all content.