FY 2009 NIMS Implementation Objectives The chart below depicts the 28 NIMS Implementation Objectives prescribed by National Integration Center’s Incident Management Systems Integration (IMSI) Division for Federal Fiscal Year (FY) 2009. State, territorial, tribal, and local jurisdictions must ensure all NIMS objectives have been initiated and/or are in progress toward completion. NIMS Component NIMS Implementation Objective Federal FY Prescribed to: State/ Territory Tribal Local AADDOOPPTTIIOONN 1. Adopt NIMS for all Departments/Agencies; as well as promote and encourage NIMS adoption by associations, utilities, nongovernmental organizations (NGOs) and private sector emergency management and incident response organizations. 2005 2. Establish and maintain a planning process to communicate, monitor, and implement all NIMS compliance objectives across the State/Territory/Tribal Nation (including Departments/Agencies), to include local governments. This process must provide a means for measuring progress and facilitate reporting. 2006 2008 N/A 3. Designate and maintain a single point of contact within government to serve as principal coordinator for NIMS implementation jurisdiction-wide (to include a principal coordinator for NIMS implementation within each Department/Agency). 2006 2007 4. Ensure that Federal Preparedness Awards [to include, but not limited to, DHS Homeland Security Grant Program and Urban Area Security Initiative Funds] to State/Territorial/Tribal Departments/Agencies, as well as local governments, support all required NIMS Compliance Objectives (requirements). 2005 2008 5. Audit agencies and review organizations should routinely include NIMS Compliance Objectives (requirements) in all audits associated with Federal Preparedness Awards. 2006 2008 6. Assist Tribal Nations with formal adoption and implementation of NIMS. 2007 N/A PPRREEPPAARREEDDNNEESSSS Planning 7. Revise and update emergency operations plans (EOPs), standard operating procedures (SOPs), and standard operating guidelines (SOGs) to incorporate NIMS and National Response Framework (NRF) components, principles and policies, to include planning, training, response, exercises, equipment, evaluation, and corrective actions. 2005 8. Promote and/or develop intrastate and interagency mutual aid agreements and assistance agreements (to include agreements with the private sector and NGOs). 2005 Training 9. Use existing resources such as programs, personnel and training facilities to coordinate and deliver NIMS training requirements. 2006 2008 10. Implement IS-700 NIMS: An Introduction training to include appropriate personnel (as identified in the Five-Year NIMS Training Plan, February 2008). 2006 11. Implement IS-800 National Response Framework (NRF): An Introduction training to include appropriate personnel (as identified in the Five-Year NIMS Training Plan, February 2008). 2006 12. Implement ICS-100 Introduction to ICS training to include appropriate personnel (as identified in the Five-Year NIMS Training Plan, February 2008). 2006 13. Implement ICS-200 ICS for Single Resources and Initial Action Incidents training to include appropriate personnel (as identified in the Five-Year NIMS Training Plan, February 2008). 2006 14. Implement ICS-300 Intermediate ICS training to include appropriate personnel (as identified in the Five-Year NIMS Training Plan, February 2008). 2007 15. Implement ICS-400 Advanced ICS training to include appropriate personnel (as identified in the Five-Year NIMS Training Plan, February 2008). 2009 Exercises 16. Incorporate NIMS concepts and principles into all appropriate State/Territorial/Tribal training and exercises. 2005 17. Plan for and/or participate in an all-hazards exercise program [for example, Homeland Security Exercise and Evaluation Program] that involves emergency management/response personnel from multiple disciplines and/or multiple jurisdictions. 2006 18. Incorporate corrective actions into preparedness and response plans and procedures. 2006 CCOOMMMMUUNNIICCAATTIIOONN AANNDD IINNFFOORRMMAATTIIOONN MMAANNAAGGEEMMEENNTT 19. Apply common and consistent terminology as used in NIMS, including the establishment of plain language (clear text) communications standards. 2006 20. Utilize systems, tools, and processes to present consistent and accurate information (e.g., common operating picture) during an incident/planned event. 2007 RREESSOOUURRCCEE MMAANNAAGGEEMMEENNTT 21. Inventory response assets to conform to NIMS National Resource Typing Definitions, as defined by FEMA Incident Management Systems Integration Division. 2006 22. Ensure that equipment, communications and data systems acquired through State/Territorial and local acquisition programs are interoperable. 2006 23. Utilize response asset inventory for intrastate/interstate mutual aid requests [such as Emergency Management Assistance Compact (EMAC)], training, exercises, and incidents/planned events. 2007 24. Initiate development of a State/Territory/Tribal-wide system (that incorporates local jurisdictions) to credential emergency management/response personnel to ensure proper authorization and access to an incident including those involving mutual aid agreements and/or assistance agreements. 2008 CCOOMMMMAANNDD AANNDD MMAANNAAGGEEMMEENNTT Incident Command System 25. Manage all incidents/ planned events in accordance with ICS organizational structures, doctrine and procedures. ICS implementation must include the consistent application of Incident Action Planning (IAP), common communications plans, implementation of Area Command to oversee multiple incidents that are handled by separate ICS organizations or to oversee the management of a very large or evolving incident that has multiple incident management teams engaged, and implementation of unified command (UC) in multi-jurisdictional or multi-agency incident management, as appropriate. 2006 MultiAgency Coordination Systems 26. Coordinate and support emergency management and incident response objectives through the development and use of integrated MACS, [i.e. develop/maintain connectivity capability between local Incident Command Posts (ICPs), local 911 Centers, local/regional/State/territorial/tribal/Federal Emergency Operations Centers (EOCs), as well as NRF organizational elements.] 2006 Public Information 27. Institutionalize, within the framework of ICS, Public Information, [e.g., Joint Information System (JIS) and a Joint Information Center (JIC)] during an incident/planned event. 2006 28. Ensure that Public Information procedures and processes can gather, verify, coordinate, and disseminate information during an incident/planned event. 2007