|
Top 5 FAQs
Q: I still have not received my training certificate for a course I took on the EMI Web site. What should I do?
A: Contact the Emergency Management Institute's Independent Study Office at 301-447-1200 or independent.study@dhs.gov.
Q: Who has to take NIMS and ICS training?
A: Stakeholders will define the emergency management/response personnel within their jurisdiction, agency, or organization who require ongoing training. This includes all emergency services-related disciplines such as EMS, hospitals, public health, fire service, law enforcement, public works/utilities, skilled support personnel, and other emergency management response, support, and volunteer personnel, as follows:
Entry Level:
- FEMA IS-700: NIMS, An Introduction
- ICS-100: Introduction to ICS or equivalent
First Line, Single Resource, Field Supervisors:
- IS-700.A, ICS-100, and ICS-200: Basic ICS or its equivalent
Middle Management: Strike Team Leaders, Division Supervisors, EOC Staff, etc.:
- IS-700.A, IS-800.B NRF, ICS-100, ICS-200, and ICS-300
Command and General Staff; Area, Emergency, and EOC Managers:
- IS-700.A, IS-800.B NRF, ICS-100, ICS-200, ICS-300, and ICS-400
Q: What about elected and appointed officials?
A: The National Integration Center strongly recommends that all elected officials who will be interacting with multiple jurisdictions and agencies during an emergency incident at the minimum complete IS-700: NIMS, An Introduction and ICS-100: Introduction to ICS. These courses provide a basic understanding of the National Incident Management System and the Incident Command System. Everyone directly involved in managing an emergency should understand the command reporting structures, common terminology, and roles and responsibilities inherent in a response operation.
- Fact Sheet 01-07-NIMS Elected Officials [3/07] (PDF 26KB, TXT 3KB)
Q: What training do I need to be an ICS instructor?
A:
ICS-100: Instructor Qualifications
- Successful completion of accredited ICS-100, ICS-200, and IS-700.A.
- Service in a mid-level emergency management and incident response position within five years in real-world incidents, planned events, or accredited exercises.
- Recognized qualifications in techniques of instruction and adult education methodologies.
ICS-200: Instructor Qualifications
- Successful completion of accredited ICS-100, ICS-200, IS-700.A, and IS-800.B.
- Service in a mid-level emergency management and incident response position within five years in real-world incidents, planned events, or accredited exercises.
- Recognized qualifications in techniques of instruction and adult education methodologies.
ICS-300: Instructor Qualifications
- Successful completion of accredited ICS-100, ICS-200, ICS-300, ICS-400, IS-700.A, and IS-800.B.
- Service in a mid-level incident management position within five years in real-world incidents, planned events, or accredited exercises.
- Recognized qualifications in techniques of instruction and adult education methodologies.
ICS 400: Instructor Qualifications
- Successful completion of accredited ICS-100, ICS-200, ICS-300, ICS-400, IS-700.A, and IS-800.B.
- Service in a mid-level emergency management and incident response position within five years in real-world incidents, planned events, or accredited exercises.
- Recognized qualifications in techniques of instruction and adult education methodologies.
For additional information, refer to the Five-Year NIMS Training Plan.
An instructor's qualifications must be verified by the agency sponsoring the training.
Q: I've tried logging on NIMSCAST and my password doesn't work. What can I do?
A: If you have received a temporary password, you will need to log into your account within 24 hours and change your password. If it has been more than 24 hours since you received your password, you can have a new password e-mailed to you by clicking on the "lost or forgotten password" option on the NIMSCAST login page. Remember, new passwords must be at least eight characters long and must contain at least one of each of the following: lowercase character (a-z); uppercase character (A-Z); special character (!, @, #, $, %, etc ...); and a digit (0-9). Be sure to input your password exactly - it is case sensitive.
Back To Top
General Questions
Q. What is the National Incident Management System (NIMS)?
A: NIMS is a comprehensive, national approach to incident management that is applicable at all jurisdictional levels and across functional disciplines. It is intended to:
- Be applicable across a full spectrum of potential incidents, hazards, and impacts, regardless of size, location or complexity.
- Improve coordination and cooperation between public and private entities in a variety of incident management activities.
- Provide a common standard for overall incident management.
Q. Why do we need NIMS?
A: NIMS provides a consistent nationwide framework and approach to enable government at all levels (Federal, State, tribal, and local), the private sector, and nongovernmental organizations (NGOs) to work together to prepare for, prevent, respond to, recover from, and mitigate the effects of incidents regardless of the incident’s cause, size, location, or complexity.
Consistent application of NIMS lays the groundwork for efficient and effective responses, from a single agency fire response to a multiagency, multijurisdictional natural disaster or terrorism response. Entities that have integrated NIMS into their planning and incident management structure can arrive at an incident with little notice and still understand the procedures and protocols governing the response, as well as the expectations for equipment and personnel. NIMS provides commonality in preparedness and response efforts that allow diverse entities to readily integrate and, if necessary, establish unified command during an incident.
Q. What are the Components of NIMS?
A: NIMS Components link together and work in unison to form a comprehensive incident management system. NIMS Components include:
- Preparedness
- Communications and Information Management
- Resource Management
- Command and Management
- Ongoing Management and Maintenance
Q. To whom does NIMS apply?
A: NIMS is applicable to State, tribal and local governments, private sector organizations, critical infrastructure owners and operators, nongovernmental organizations and other organizations with an active role in emergency management and incident response. Elected and appointed officials, who are responsible for jurisdictional policy decisions, must also have a clear understanding of their emergency management roles and responsibilities to better serve their constituency.
Q. How does NIMS relate to the National Response Framework (NRF)?
A: The NIMS and NRF are companion documents and are designed to improve the Nation’s incident management and response capabilities. While NIMS provides the template for the management of incidents regardless of size, scope or cause, the NRF provides the structure and mechanisms for national level policy of incident response. Together, the NIMS and the NRF integrate the capabilities and resources of various governmental jurisdictions, incident management and emergency response disciplines, non-governmental organizations, and the private-sector into a cohesive, coordinated, and seamless national framework for domestic incident response.
Q. How does NIMS relate to local incident command?
A: A basic premise of NIMS is that all incidents begin and end locally. NIMS does not take command away from State and local authorities. NIMS simply provides the framework to enhance the ability of responders, including the private sector and NGOs, to work together more effectively. The Federal Government supports State and local authorities when their resources are overwhelmed or anticipated to be overwhelmed. Federal departments and agencies respect the sovereignty and responsibilities of local, tribal, and State governments while rendering assistance. The intention of the Federal Government in these situations is not to command the response, but rather to support the affected local, tribal, and/or State governments.
Q. What is the role of Elected and Appointed Officials during an incident?
A: Elected and appointed officials are responsible for ensuring the public safety and welfare of the people of that jurisdiction. Specifically, these officials provide strategic guidance and resources during preparedness, response, and recovery efforts. Elected or appointed officials must have a clear understanding of their roles and responsibilities for successful emergency management and response. At times, these roles may require providing direction and guidance to constituents during an incident, but their day-to-day activities do not focus on emergency management and response. Their awareness of NIMS is critical to ensuring cooperative response efforts and minimizing the incident impacts.
Q. What role does Preparedness have in NIMS?
A: Preparedness is essential for effective incident and emergency management and involves engaging in a continuous cycle of planning, organizing, training, equipping, exercising, evaluating, and taking corrective action to achieve and maintain readiness to respond to emergencies. As such, the NIMS Preparedness Component serves as a baseline concept that links all the NIMS Components. Preparedness spans jurisdictions, governments, agencies and organizations. Though individuals certainly play a critical role in preparedness and are expected to prepare themselves and their families for all types of potential incidents, they are not directly included in NIMS preparedness. NIMS primarily discusses the preparedness role for governments, organizations geared specifically toward preparedness, elected and appointed officials, nongovernmental organizations, and the private sector.
Q. What is a Common Operating Picture?
A: A common operating picture (COP) offers a standard overview of an incident, thereby providing incident information that enables the Incident Commander/Unified Command and any supporting agencies and organizations to make effective, consistent, and timely decisions. Compiling data from multiple sources and disseminating the collaborative information COP ensures that all responding entities have the same understanding and awareness of incident status and information when conducting operations.
Q. What is Interoperability?
A: Interoperability allows emergency management/response personnel and their affiliated organizations to communicate within and across agencies and jurisdictions via voice, data, or video-on-demand, in real-time, when needed, and when authorized - this includes equipment and the ability to communicate. If entities have physical communications systems that are able to directly communicate, those systems are considered to be interoperable. This can be a function of the actual system or the frequency on which the system operates.
Q. What is Resource Management?
A: Resource management involves the coordination, oversight, and processes necessary to provide timely and appropriate resources during an incident. Utilization of the standardized resource management concepts such as the typing, inventorying, ordering, and tracking of resources will facilitate their dispatch, deployment, and recovery before, during, and after an incident.
Q. What is Command and Management?
A: The Command and Management component within NIMS is designed to enable effective and efficient incident management and coordination by providing a flexible, standardized incident management structure. To institutionalize these activities within a formal structure, command and management includes three fundamental elements: the Incident Command System (ICS), Multiagency Coordination Systems (MACS), and Public Information. These fundamental elements provide standardization through consistent terminology and established organizational structures.
Q. Why is ICS needed?
A: When an incident requires response from multiple local emergency management and response agencies, effective cross-jurisdictional coordination using common processes and systems is critical. The Incident Command System (ICS) provides a flexible, yet standardized core mechanism for coordinated and collaborative incident management, whether for incidents where additional resources are required or are provided from different organizations within a single jurisdiction or outside the jurisdiction, or for complex incidents with national implications.
Q. What is ICS Designed To Do?
A: The ICS is a widely applicable management system designed to enable effective, efficient incident management by integrating a combination of facilities, equipment, personnel, procedures, and communications operating within a common organizational structure. ICS is a fundamental form of management established in a standard format, with the purpose of enabling incident managers to identify the key concerns associated with the incident—often under urgent conditions—without sacrificing attention to any component of the command system. It represents organizational "best practices" and, as an element of the Command and Management Component of NIMS, has become the standard for emergency management across the country. Designers of the system recognized early that ICS must be interdisciplinary and organizationally flexible to meet the following management challenges:
- Meet the needs of incidents of any kind or size.
- Allow personnel from a variety of agencies to meld rapidly into a common management structure.
- Provide logistical and administrative support to operational staff.
- Be cost effective by avoiding duplication of efforts.
ICS consists of procedures for controlling personnel, facilities, equipment, and communications. It is a system designed to be used or applied from the time an incident occurs until the requirement for management and operations no longer exists.
Q. How does an EOC relate to MACS?
A: MACS is designed to facilitate the process of multiagency coordination, which allows all levels of government and all disciplines to work together more efficiently and effectively. Multiagency coordination can and does occur on a regular basis whenever personnel from different agencies interact in such activities as preparedness, prevention, response, recovery, and mitigation. More specifically, the primary function of MACS is to coordinate activities above the field level and to prioritize the incident demands for critical or competing resources, thereby assisting the coordination of the operations in the field. MACS consists of a combination of elements: personnel, procedures, protocols, business practices, and communications integrated into a common system.
Emergency Operations Centers (EOCs) are one of several system elements included within the Multiagency Coordination System(MACS). EOCs are intended to facilitate MACS functions, and may provide support to Area Command, Incident Command, or Unified Command when resource needs exceed local capabilities.
Q. What is the relationship between an Incident Command Post and an EOC/MAC Group?
A: The Incident Command Post is a physical location that administers the on-scene incident command and the other major incident management functions. An EOC is a physical location that is located separately from the on-scene Incident Command Post and supports the on-scene response by providing external coordination and securing of additional resources. A MAC Group does not have any direct incident command involvement and will often be located some distance from the incident site(s). EOC/MAC Groups do not command the on-scene level of the incident, but rather supports the Incident Command Post’s command and management efforts.
Q. What is the difference between Area Command and MACS?
A: Area Command is an organization that oversees the management of multiple incidents handled individually by separate incident command organizations or to oversee the management of a very large or evolving incident engaging multiple incident management teams. Area Command should not be confused with the functions performed by MACS as Area Command oversees management coordination of the incident(s), while a MACS element (such as a communications/dispatch center, EOC, or MAC Group) coordinates support.
Q. What does Public Information, within NIMS, include?
A: Public Information consists of the processes, procedures, and systems to communicate timely, accurate, and accessible information on the incident’s cause, size, and current situation to the public, responders, and additional stakeholders (both directly and indirectly affected). Public information must be coordinated and integrated across jurisdictions and organizations involved in the incident to include, Federal, State, tribal, and local governments, private sector entities and NGOs. In order to facilitate that process, Public Information includes three major systems/components - Public Information Officers (PIOs), the Joint Information System (JIS), and the Joint Information Center (JIC).
Back To Top
Preparedness
Q: NIMS promotes the use of State and local mutual aid to help local jurisdictions better handle large-scale disasters. Where can I find information on how to write a mutual aid agreement?
A: The National Emergency Management Association (NEMA), in coordination with DHS/FEMA and a cross-section of emergency responders, has developed a tool to assist State and local governments in the preparation of model legislation designed to streamline the sharing of assistance and resources between communities during a disaster. The model is available for download at www.emacweb.org. Additionally, many States, such as North Carolina, have developed statewide mutual aid systems. We are also working with the International Association of Fire Chiefs (IAFC) on developing better firefighting mutual aid systems with States to make filling EMAC requests faster (Intrastate Mutual Aid Systems), as well as developing a national firefighting coordination system (Emergency Management Committee). Information on these can be found on the IAFC Web site.
Q: How does the NIC view its role in the management of mutual aid resources? Is there potential for conflict between the NIC and EMAC?
A: The NIC does not manage resources - the NIC facilitates resource management by providing resource typing definitions for nationally important resources. All the work we have been engaged with is in support of EMAC and for the purpose of making EMAC more efficient.
Back To Top
Communications and Information Management
Q: What is the National Emergency Communications Plan?
A: National studies, assessments, and after-action reports from September 11, 2001, Hurricane Katrina, and other natural and manmade disasters in the last decade have underscored the critical need for improved emergency communications nationwide. These documents show that the lack of emergency communications interoperability across disciplines and jurisdictions hinders situational awareness, command and control, and the overall management of response and recovery efforts.
In 2006, Congress enacted provisions under the Fiscal Year 2007 Department of Homeland Security Appropriations Act requiring the Department of Homeland Security (DHS) Office of Emergency Communications (OEC) to develop a National Emergency Communications Plan (NECP) to provide a roadmap to improve the Nation’s emergency communications capabilities. The NECP is a strategic plan that sets goals and identifies key national priorities to enhance governance, planning, technology, training and exercises, and disaster communications capabilities. The NECP provides recommendations, including milestones, to help emergency response providers and relevant government officials make measurable improvements in emergency communications over the next 3 years.
Q: What does NIMS mean for Information Technology (IT) managers?
A: IT managers can play an important support role in the implementation of NIMS. NIMS is our Nation's incident management system. NIMS integrates best emergency management practices, procedures, and systems utilized by emergency management professionals across the Nation into a national framework for incident response. Information technology can provide important supporting capabilities essential to implementing and continuously refining NIMS.
Information technology systems must be able to work together and should not interfere with one another when multiple jurisdictions, organizations, and functions come together to respond to an incident. Effective emergency management and incident response activities rely on flexible communications and information systems that provide a common operating picture to emergency management/response personnel and their affiliated organizations. Systems should support the following Communications and Information Management concepts and principles: interoperability; reliability, scalability, and portability; and resiliency and redundancy of any system and its components.
Q: What steps are important for IT managers to establish information systems?
A: It is important that IT managers work with department heads, local emergency management, and State emergency management to determine technology support requirements prior to an event. IT managers should reach out to emergency management personnel in the community to formulate information technology requirements. Such requirements could include:
- Establishing information systems to inform, coordinate, and execute operational decisions and requests during an incident.
- Establishing information systems to support the establishment of a common operating picture during an incident.
- Establishing information management policies prior to an event to integrate information needs during an event into a common operating picture.
- Establishing information systems that tie together all command, tactical, and support units involved in incident management. This system must enable all entities to share critical information.
Back To Top
Mutual Aid Agreements and Assistance Agreements
Q: NIMS promotes the use of State and local mutual aid to help local jurisdictions better handle large-scale disasters. Where can I find information on how to write a mutual aid agreement?
A: The National Emergency Management Association (NEMA), in coordination with DHS/FEMA and a cross-section of emergency responders, has developed a tool to assist State and local governments in the preparation of model legislation designed to streamline the sharing of assistance and resources between communities during a disaster. The model is available for download at www.emacweb.org. Additionally, many States, such as North Carolina, have developed statewide mutual aid systems. We are also working with the International Association of Fire Chiefs (IAFC) on developing better firefighting mutual aid systems with States to make filling EMAC requests faster (Intrastate Mutual Aid Systems), as well as developing a national firefighting coordination system (Emergency Management Committee). Information on these can be found on the IAFC Web site.
Q: How do we better partner in the development of mutual aid resources built to a national standard?
A: The NIC is working with other elements of the National Preparedness Directorate and the Grants Management Directorate of FEMA on resource typing/credentialing for the resources identified in the Target Capabilities List. The NIC also is working with Citizen Corps, the Telecommunicator Emergency Response Taskforce (TERT), and the National Humane Society to develop additional national-level resource typing.
The NIC developed a policy on resource typing to define what resources require a national definition. This policy is contained in NIMS Guide 0001, National Resource Typing Criteria, dated March 27, 2008. The policy allows State, regional, and local efforts to type resources that are important locally and regionally but do not need a national consensus definition.
Q: How does this mutual aid developmental effort fit into the overall strategic plan? Do we have a clear vision of what we want to build, how many of each package is needed, and where all of these resources should be strategically located?
A: The role of the NIC is establishment of interoperability of resources through consensus definition for teams and equipment, and Knowledge, Skills, and Abilities for individuals and members of teams. The NIC is collaborating with the DHS Science and Technology Directorate in the development of a data model for resource management that can be incorporated into any system selected by States, to ensure the information will be interoperable when interjurisdictional mutual aid is needed. The data model will also incorporate existing technology standards, such as EDXL and the National Information Exchange Model, to further the interoperability of all resource management systems.
The determination of how many of any given resource are needed in each community is not a function of NIMS, but is a function of the FEMA Grants and Assistance Program and their work on the National Preparedness Goal (HSPD-8). While the Grants Management Directorate and National Preparedness Directorate determine needed resources, the NIC ensures consistent definition of resources so they can be ordered and will arrive fully able to perform the function requested for.
Q: How does the NIC view its role in the management of mutual aid resources? Is there potential for conflict between the NIC and EMAC?
A: The NIC does not manage resources - the NIC facilitates resource management by providing resource typing definitions for nationally important resources. All the work we have been engaged with is in support of EMAC and for the purpose of making EMAC more efficient.
Back To Top
Resource Typing
Q: What is resource typing?
A: Resource typing is the categorization and description of response resources that are commonly exchanged in disasters through mutual aid agreements. The National Integration Center (NIC) Incident Management Systems Integration (IMSI) Division has developed and published over 120 resource typing definitions. The NIC is continuing resource typing work and has established new working groups for the ongoing initiative. Resource typing definitions can give emergency responders the information they need to make sure they request and receive the appropriate resources during an emergency or disaster. Ordering resources that have been typed using these definitions makes the resource request and dispatch process more accurate and efficient. In FY 2006, State, territorial, tribal, and local jurisdictions were required to inventory response assets that conform to NIMS resource typing standards.
Q: What is the purpose of resource typing?
A: Resource typing enhances emergency readiness and response at all levels of government through a system that allows an already overwhelmed jurisdiction to augment its response resources during an incident. Standard resource typing definitions help responders request and deploy the resources they need through the use of common terminology. They allow emergency management personnel to identify, locate, request, order, and track outside resources quickly and effectively and facilitate the movement of these resources to the jurisdiction that needs them.
Q: Is resource typing part of NIMS?
A: Yes. Resource typing is an important part of resource management, which is one of the five components of the National Incident Management System. The only standard for resource typing is contained in Appendix B to the NIMS. However, the appendix does not provide the detailed guidance for someone to produce nationally consistent resource definitions. To better explain NIMS resource typing, the NIC published NIMS Guide 0001, National Resource Typing Criteria, dated March 27, 2008. The NIC is continuing to develop resource typing definitions, which are then offered for national comment. The role of the NIC is to establish interoperability of resources through consensus definition for teams and equipment, and Knowledge, Skills, and Abilities for individuals and team members.
Q: Has the National Integration Center developed a list of typed resources?
A: FEMA and the National Integration Center (NIC) Incident Management Systems Integration (IMSI) Division recently released the National Mutual Aid Glossary of Terms and Definitions and the resource typing definitions for over 120 different kinds of resources. The resources were identified by groups of Federal, State, and local representatives as the most commonly requested and exchanged resources during significant disasters and emergencies. These products provide a foundation for facilitating the use of common terminology while enhancing mutual aid across the country.
Q: Are the resource typing groups still working on defining critical response assets?
A: Yes. Nine working groups have been formed by the National Integration Center (NIC) Incident Management Systems Integration (IMSI) Division to develop and refine definitions for critical response assets. The working groups include Animal Health, Emergency Management, Emergency Medical Services, Fire & Hazmat, Public Health & Medical, Mass Care, Law Enforcement, Public Works, and Search and Rescue. The initiative will expand to include additional discipline groups if the need arises. Resources are being revised on an as-needed basis as errors or updates are recognized by the NIC and stakeholders. Adjustments will be made to the current 120 typed definitions as capabilities and capacities improve and additional resources will be typed as they are identified by stakeholders.
Q: I read with interest your statement that independently developed typing systems are not compliant with NIMS. What about DHS's Pre-Positioned Equipment Program, ODP's Authorized Equipment List (AEL), and the Standardized Equipment List (SEL), which use nomenclatures not common with resource typing.
A: The National Integration Center (NIC) Incident Management Systems Integration (IMSI) Division has been leading a national resource typing effort for several years to identify resources that are especially valuable for mutual aid in disasters. However, with the focus on NIMS compliance, many State and local governments are revisiting the resource typing definitions. In some cases, when it seems that the existing definitions don't fit their resources, they are initiating new resource typing efforts. This really defeats the purpose of common resource typing definitions that are essential in mutual aid operations in disasters. The current NIMS resource typing definitions were created to reflect the resources that are most commonly exchanged via mutual aid during a disaster, and are referred to as Tier I in accordance with NIMS Guide 0001. The NIMS typed resources are not resources for routine day-to-day emergency response operations. IMSI recognizes that States and jurisdictions may want to extend resource typing to more than the NIMS for their own purposes, and under NIMS Guide 0001 these are referred to as Tier II resources. For example, resources that never leave a State do not belong in Tier I but can be added to the State inventory as Tier II.
The NIC is working with the National Preparedness Directorate and the Grants Management Directorate to review the efforts of the Target Capabilities Working Groups to determine which resources they want to add to the list of NIMS Tier I resources typed by the NIC. The NIC will continue to work with the DHS Office of Grants and Training to refine these definitions, create new definitions, and look at what changes may need to be made to other documents (such as the equipment lists). The NIC will meet with the Resource Typing Working Groups on a quarterly basis to review and address the suggestions and issues that are raised through this process.
Q: Who certifies that a resource meets the national standard and that personnel are credentialed to fill a role?
A: The State or local agency conducting the inventory uses the NIMS Tier I typed resources issued by the NIC and compares the definitions with the equipment/teams that exist in the jurisdiction. If a resource matches a definition on the list of the NIMS Tier I typed resources, then that resource must be included in the State or local inventory. Since there are currently no position-specific credentialing definitions, the jurisdiction must ensure that the training, etc., specified in the typing definition is met by all personnel attached to a team. In general, the typing lists training and education qualifications that are routinely required throughout the country.
Q: Who maintains the inventory, the State or the NIC or both?
A: Inventories are maintained by State and local governments. The NIC is not operational and does not intend to be a resource ordering point for the Nation.
Q: We know that NIMS emphasizes resource management and resource typing. Does that mean we are supposed to do our own resource typing, or what?
A: The only resource typing States should pursue is for those resources that fall into Tier II as detailed in NIMS Guide 0001. Communities and jurisdictions should begin to use the NIMS Tier I resource typing definitions to describe and inventory their resources. State and local jurisdictions may use DHS Homeland Security grant funds to create or update an inventory of their resources in accordance with the NIMS Tier I resource typing definitions.
Back To Top
Resource Credentialing
Q: The NIMS document mentions a credentialing system tied to training and certification standards. Is there a national credentialing system in place that we need to follow?
A: The development of a nationwide credentialing system is a fundamental component of NIMS. However, this system is fundamental doctrine and business rules, and is not a single information technology system. A national credentialing system can document minimum professional qualifications, certifications, training, and education requirements that define baseline criteria expected of emergency response professionals and volunteers for deployment as mutual aid to disasters. While such a system is meant to verify the identity and qualifications of emergency responders, it does not provide automatic access to an incident site. The credentialing system can help prevent unauthorized (i.e., self-dispatched or unqualified personnel) access to an incident site. To support this credentialing initiative, the National Integration Center (NIC) uses working groups to identify positions that should be credentialed and the minimum qualification, certification, training, and education requirements for each position. The groups represent the following disciplines:
- Incident Management
- Emergency Medical Services
- Fire Fighting and Hazardous Materials Response
- Law Enforcement
- Public Health/Medical
- Public Works
- Search & Rescue
- Animal Control/Veterinary
- Mass Care
In addition to these NIC discipline groups, the NIC is working with other organizations to assist their development of credentialing for their disciplines, such as the APCO/NENA Telecommunicator Emergency Response Taskforce (TERT) and the Citizen Corps initiative for credentialing volunteers.
Although the NIC Incident Management Systems Integration (IMSI) Division has identified subject-matter experts for its working groups, the Center requests notification of all existing credentialing efforts, regardless of discipline. The NIC welcomes your participation into our stakeholder review group. As a stakeholder, you will receive updates concerning the working group process and be able to review and provide feedback on the draft products that are developed. If you are interested in participating as a stakeholder, please send an e-mail to: FEMA-NIMS@dhs.gov.
Back To Top
Incident Command System
Q: In order to meet NIMS compliance, does it matter which brand of ICS is used (i.e., NIIMS, FIRESCOPE, NWCG)?
A: To be NIMS compliant, you need to use the Incident Command System (ICS) structure described in the current version of NIMS. The foundation for ICS principles embedded in NIMS is derived from the National Interagency Incident Management System (NIIMS), Firefighting Resources of California Organized for Potential Emergencies (FIRESCOPE), and National Wildfire Coordinating Group (NWCG).
Q: Our 911 center, which receives and dispatches emergency and nonemergency calls, has told us that we may not use 10-codes at all. I gather we must use plain language when using NIMS ICS. Is that correct?
A: Yes. When engaged in a multiagency/multijurisdictional incident using ICS, plain language is required. The value of using 10-codes for simplicity and speed is lost when members of the response team are unaware of their meanings, as may occur in a multiagency/multijurisdiction response event. As 10-codes used in one jurisdiction or agency are not the same as those used in another, it is important that responders and incident managers use common terminology to prevent misunderstanding in an emergency situation. While plain language is not required for internal operations, it is encouraged over 10-codes to promote familiarity within operational procedures used in emergencies.
NIMS Alert: NIMS and Use of Plain Language [12/06] (PDF 26KB, TXT 3KB)
Back To Top
Multiagency Coordination Systems
Q: Can you provide additional guidance regarding NIMS and the Emergency Operations Center?
A: NIMS characterizes Emergency Operations Centers (EOCs) as an element of a Multiagency Coordination System. EOCs do not have to be organized around ICS. The NIMS states in the Command and Management chapter that "EOCs may be organized by major discipline (e.g., fire, law enforcement, or emergency medical services); by emergency support function (e.g., transportation, communications, public works and engineering, or resource support); by jurisdiction (e.g., city, county, or region); or, more likely, by some combination thereof. Incident Command Posts need reliable communication links to EOCs to ensure effective and efficient incident management. EOCs may be staffed by personnel representing multiple jurisdictions and functional disciplines and a wide variety of resources. For example, a local EOC established in response to a bioterrorism incident would likely include a mix of law enforcement, emergency management, public health, and medical personnel (local, State, or Federal public health officials and possibly representatives of health care facilities, emergency medical services, etc.). The physical size, staffing, and equipping of an EOC will depend on the size of the jurisdiction, resources available, and anticipated incident management workload. EOCs may be organized and staffed in a variety of ways. Regardless of its specific organizational structure, an EOC should include the following core functions: coordination; communications; resource allocation and tracking; and information collection, analysis, and dissemination.”
Q: In addition to Emergency Operations Plans (EOPs), which subordinate documents must also be NIMS compliant?
A: Any plan, procedure, field guide, or standard operating procedure (SOP) must support the State, territory, tribal, or local EOP and NIMS. SOPs that are not NIMS compliant will only serve to undermine the EOP's compliance with NIMS. While no schedule is proposed for EOP elements, they should be reviewed and revised for NIMS compliance as soon as it is practicable to do so.
Back To Top
Public Information
Q: What is a Joint Information System?
A: A Joint Information System (JIS) provides the mechanism to organize, integrate, and coordinate information to ensure timely, accurate, accessible, and consistent messaging across multiple jurisdictions and/or disciplines with nongovernmental organizations and the private sector. A JIS includes the plans, protocols, procedures, and structures used to provide public information. Federal, State, tribal, territorial, regional, or local Public Information Officers and established Joint Information Centers (JICs) are critical supporting elements of the JIS.
Q: What is a Joint Information Center?
A: A Joint Information Center (JIC) is a central location that facilitates operation of the Joint Information System. The JIC is a location where personnel with public information responsibilities perform critical emergency information functions, crisis communications, and public affairs functions. JICs may be established at various levels of government or at incident sites, or can be components of Multiagency Coordination Systems. A single JIC location is preferable, but the system is flexible and adaptable enough to accommodate virtual or multiple JIC locations, as required.
Back To Top
NIMS Compliance
Q: I still do not understand what NIMS is. Could you explain to me what benefit our small fire department will gain from using NIMS?
A: While most emergency situations are handled locally, when there's a major incident help may be needed from other jurisdictions, the State, and the Federal Government. The National Incident Management System (NIMS) provides a consistent nationwide template to enable Federal, State, tribal, and local governments, the private sector, and nongovernmental organizations to work together effectively and efficiently to prepare for, prevent, respond to, and recover from domestic incidents, regardless of cause, size, or complexity, including acts of catastrophic terrorism. NIMS benefits include a unified approach to incident management; standard command and management structures; and emphasis on preparedness, mutual aid, and resource management. The bottom line is that every community in America is a potential recipient of mutual aid, and having a common incident management system allows the arriving mutual aid to be seamlessly integrated into your operations.
Q: What does it mean for State, territorial, tribal, and local governments to implement the National Incident Management System (NIMS)?
A: In order to implement NIMS, State, territorial, tribal, and local governments must follow the compliance activities for the current fiscal year. The current NIMS Implementation Compliance Objectives can be found here. Requirements will be added/updated based on lessons learned during disasters, exercises, and other events.
Q: In order to meet NIMS compliance, does it matter which brand of ICS is used (i.e. NIIMS, FIRESCOPE, NWCG)?
A: Yes. NIMS compliance is based on the Incident Command System (ICS) structure described in the current version of NIMS. The foundation for ICS principles embedded in NIMS is derived from the National Interagency Incident Management System (NIIMS), Firefighting Resources of California Organized for Potential Emergencies (FIRESCOPE), and National Wildfire Coordinating Group (NWCG).
Q: If a jurisdiction is compliant with the NIIMS (National Interagency Incident Management System), does this mean that we're compliant with NIMS?
A: No. Compliance with NIIMS does not constitute compliance with NIMS. NIIMS, adopted by several Federal, State, and local agencies in 1982, served as the basis for today's National Incident Management System. Although there are many similarities between NIIMS and NIMS; there are some key differences. NIIMS was designed to meet the challenges of wildland fire. NIMS was designed to address all-hazards challenges. In addition, NIMS possesses an increased emphasis on prevention and preparedness measures.
The principles and concepts of NIMS ICS are the same as the NIIMS ICS, with the exception of the means in which the Intelligence/Investigations function is handled. Under NIMS ICS, the Incident Commander has flexibility in where to assign the Intelligence/Investigations function (e.g., Command Staff or Operations).
Q: Our 911 center, which receives and dispatches emergency and nonemergency calls, has told us that we may not use 10-codes at all. I gather we must use plain language when using NIMS ICS. Is that correct?
A: Yes. When engaged in a multiagency/multijurisdictional incident using ICS, plain language is required. The value of using 10-codes for simplicity and speed is lost when members of the response team are unaware of their meanings, as may occur in a multiagency/multijurisdiction response event. As 10-codes used in one jurisdiction or agency are not the same as those used in another, it is important that responders and incident managers use common terminology to prevent misunderstanding in an emergency situation. While plain language is not required for internal operations, it is encouraged over 10-codes to promote familiarity within operational procedures used in emergencies.
NIMS Alert: NIMS and Use of Plain Language [12/06] (PDF 26KB, TXT 3KB)
Q: What is the relationship between NIMS, the NRF, and COOP?
A:
-
The National Incident Management System (NIMS) provides a consistent framework for incident management at all jurisdictional levels regardless of the cause, size, or complexity of the incident. Building upon the Incident Command System (ICS), NIMS provides the Nation's first responders and authorities with the same foundation for incident management for terrorist attacks, natural disasters, and other emergencies.
-
The National Response Framework (NRF) is an all-discipline, all-hazards plan for the management of domestic incidents. Using the template established by NIMS, the NRF provides the structure and mechanisms to coordinate and integrate incident management activities and emergency support functions across Federal, State, tribal, and local government entities, the private sector, and nongovernmental organizations.
-
Continuity of Operations (COOP) planning is simply a "good business practice"—part of the fundamental mission of agencies as responsible and reliable public institutions. Today's changing threat environment and the potential for no-notice emergencies, including localized acts of nature, accidents, technological emergencies, and military or terrorist attack-related incidents, have increased the need for COOP capabilities and plans that enable agencies to continue their essential functions across a broad spectrum of emergencies. This, coupled with the potential for terrorist use of weapons of mass destruction, has emphasized the importance of COOP programs that ensure continuity of essential government functions across the Federal executive branch.
To provide oversight and coordination of this effort, Presidential Decision Directive (PDD) 67 established the Federal Emergency Management Agency (FEMA) as the lead agency for Federal executive branch COOP. This authority was transferred to the Department of Homeland Security (DHS) on March 1, 2003, and then delegated to the Emergency Preparedness and Response Directorate (FEMA). FEMA's Office of National Security Coordination has been designated as DHS's lead agent for the Federal executive branch COOP program. Included in this responsibility is the requirement to formulate guidance and establish common standards for agencies to use in developing viable, executable COOP plans; facilitate interagency coordination as appropriate; and oversee and assess the status of COOP capabilities of Federal executive branch agencies. Additionally, each Federal executive branch agency is responsible for appointing a senior Federal Government executive as an emergency coordinator to serve as program manager and agency point of contact for coordinating agency COOP activities, to include planning, programming, and budgeting for a viable and executable COOP program.
Back To Top
NIMS Training
Q: I still have not received my training certificate for a course I took on the EMI Web site. What should I do?
A: If you have inquiries regarding certificates or EMI online courses, please contact the Emergency Management Institute's Independent Study Office at: (301) 447-1200 or e-mail them at: Independent.Study@dhs.gov.
Q: Who has to take NIMS and ICS training?
A: Stakeholders will define the emergency management/response personnel within their jurisdiction, agency, or organization who require ongoing training. This includes all emergency services related disciplines such as EMS, hospitals, public health, fire service, law enforcement, public works/utilities, skilled support personnel, and other emergency management response, support and volunteer personnel, as follows:
Entry Level:
- FEMA IS-700: NIMS, An Introduction
- ICS-100: Introduction to ICS or equivalent
First Line, Single Resource, Field Supervisors:
- IS-700.A, ICS-100, and ICS-200: Basic ICS or its equivalent
Middle Management: Strike Team Leaders, Division Supervisors, EOC Staff, etc.:
- IS-700.A, IS-800.B NRF, ICS-100, ICS-200, and ICS-300
Command and General Staff; Area, Emergency, and EOC Managers:
- IS-700.A, IS-800.B NRF, ICS-100, ICS-200, ICS-300, and ICS-400
Q: What level of NIMS training is required for elected officials?
A: The National Integration Center (NIC) Incident Management Systems Integration (IMSI) Division strongly recommends that all elected officials who will be interacting with multiple jurisdictions and agencies during an incident at the minimum complete IS-700: NIMS, An Introduction and ICS-100: Introduction to ICS. These courses provide a basic understanding of the National Incident Management System and the Incident Command System. Everyone directly involved in managing an emergency should understand the command reporting structures, common terminology, and roles and responsibilities inherent in a response operation.
Q: What training do I need to be an ICS instructor?
A:
ICS-100: Instructor Qualifications
- Successful completion of accredited ICS-100, ICS-200, and IS-700.A.
- Service in a mid-level emergency management and incident response position within five years in real-world incidents, planned events, or accredited exercises.
- Recognized qualifications in techniques of instruction and adult education methodologies.
ICS-200: Instructor Qualifications
- Successful completion of accredited ICS-100, ICS-200, IS-700.A, and IS-800.B.
- Service in a mid-level emergency management and incident response position within five years in real-world incidents, planned events, or accredited exercises.
- Recognized qualifications in techniques of instruction and adult education methodologies.
ICS-300: Instructor Qualifications
- Successful completion of accredited ICS-100, ICS-200, ICS-300, ICS-400, IS-700.A, and IS-800.B.
- Service in a mid-level incident management position within five years in real-world incidents, planned events, or accredited exercises.
- Recognized qualifications in techniques of instruction and adult education methodologies.
ICS 400: Instructor Qualifications
- Successful completion of accredited ICS-100, ICS-200, ICS-300, ICS-400, IS-700.A, and IS-800.B.
- Service in a mid-level emergency management and incident response position within five years in real-world incidents, planned events, or accredited exercises.
- Recognized qualifications in techniques of instruction and adult education methodologies.
For additional information, refer to the Five-Year NIMS Training Plan.
An instructor's qualifications must be verified by the agency sponsoring the training.
Q: I've tried logging on NIMSCAST and my password doesn't work. What can I do?
A: If you have received a temporary password, you will need to log into your account within 24 hours and change your password. If it has been more than 24 hours since you received your password, you can have a new password e-mailed to you by clicking on the "lost or forgotten password" option on the NIMSCAST login page. Remember, new passwords must be at least eight characters long and must contain at least one of each of the following: lowercase character (a-z); uppercase character (A-Z); special character (!, @, #, $, %, etc ...); and a digit (0-9). Be sure to input your password exactly - it is case sensitive.
For additional information, refer to the Five-Year NIMS Training Plan.
An instructor's qualifications must be verified by the agency sponsoring the training.
Back To Top |
|
Email Updates
