department of homeland security (dhs) geospatial...

39
Department of Homeland Security (DHS) Geospatial Management Office (GMO) Common Geospatial Operating Data COMMON OPERATING DATA (COD) REQUIREMENTS FOR THE NATIONAL RESPONSE PLAN (NRP) July 11, 2007

Upload: others

Post on 24-Jul-2020

1 views

Category:

Documents


0 download

TRANSCRIPT

Page 1: Department of Homeland Security (DHS) Geospatial ...files.ctctcdn.com/39123c2e001/66faab8f-f335-448b-b... · management, procurement, and licensing of geospatial data. Furthermore,

Department of Homeland Security (DHS) Geospatial Management Office (GMO) Common Geospatial Operating Data

COMMON OPERATING DATA (COD) REQUIREMENTS FOR THE NATIONAL RESPONSE PLAN (NRP)

July 11, 2007

Page 2: Department of Homeland Security (DHS) Geospatial ...files.ctctcdn.com/39123c2e001/66faab8f-f335-448b-b... · management, procurement, and licensing of geospatial data. Furthermore,

DHS Geospatial Management Office Common Operating Data Requirements

July 11, 2007 Page 2 of 39

TABLE OF CONTENTS 1 INTRODUCTION ................................................................................................................3

1.1 Common Operating Data Initiative .................................................................................3 1.2 Task Two Approach ........................................................................................................3 1.3 Task 2 Schedule...............................................................................................................4

2 COMMON OPERATING DATA REQUIREMENTS SUMMARY...................................5 2.1 Requirements Gathering Synopsis...................................................................................5 2.2 Recommendations............................................................................................................6 2.3 Categorized Geospatial Data Requirements ....................................................................7

3 GEOSPATIAL DATA REQUIREMENTS ANALYSIS RESULTS.................................11 3.1 Participation Summary ..................................................................................................11 3.2 Survey Results ...............................................................................................................11

ESF #1 – Transportation ................................................................................................12 ESF #2 – Communications.............................................................................................14 ESF #3 – Public Works and Engineering.......................................................................16 ESF #4 – Firefighting.....................................................................................................18 ESF #5 – Emergency Management................................................................................20 ESF #6 – Mass Care, Emergency Assistance, Housing, and Human Services ..............22 ESF #7 – Resource Support ...........................................................................................24 ESF #8 – Public Health and Medical Services...............................................................25 ESF #9 – Urban Search and Rescue...............................................................................27 ESF #10 – Oil and Hazardous Materials Response .......................................................29 ESF #11 – Agriculture and Natural Resources ..............................................................31 ESF #12 – Energy ..........................................................................................................33 ESF #13 – Public Safety and Security ...........................................................................35 ESF #14 – Long-Term Community Recovery ...............................................................36 ESF #15 – External Affairs ............................................................................................38

Appendix A. List of Acronyms...................................................................................................39

Page 3: Department of Homeland Security (DHS) Geospatial ...files.ctctcdn.com/39123c2e001/66faab8f-f335-448b-b... · management, procurement, and licensing of geospatial data. Furthermore,

DHS Geospatial Management Office Common Operating Data Requirements

July 11, 2007 Page 3 of 39

1 INTRODUCTION 1.1 Common Operating Data Initiative The Department of Homeland Security, Geospatial Management Office (DHS/GMO) has undertaken an initiative to identify and validate the geospatial data requirements of the DHS components and other Federal Departments and agencies supporting the National Response Plan (NRP). This geospatial Common Operating Data (COD) initiative aims to identify the common geospatial data needed to support each Emergency Support Function (ESF), Incident Annex, and Supporting Annex of the NRP. The initiative will also identify the authoritative government or available commercial data sources to fulfill these requirements and provide the basis for the management, procurement, and licensing of geospatial data. Furthermore, it will support efforts to develop a geospatial Concept of Operations and implementation of the DHS Geospatial Data Warehousing Strategy. This initiative consists of five major tasks, to include:

• Task One: Review and verification of current known geospatial data needs of the DHS

components • Task Two: Establishment of geospatial Common Operating Data needs of the NRP • Task Three: Coordination with the Homeland Infrastructure Foundation-Level Data

Working Group (HIFLD) to identify authoritative data sources to fulfill the identified geospatial data needs

• Task Four: Integration of Tasks One through Three into an overarching, comprehensive analysis to include the mapping of the types of geospatial data requirements to DHS Components and NRP ESFs and Annex activities

• Task Five: Ongoing coordination support and maintenance of COD requirements to include attendance of the bi-monthly HIFLD meetings and the DHS Geospatial Working Group meetings and the continued refinement of resulting COD requirements analysis documentation

This report summarizes the results of Task Two, establishment of geospatial Common Operating Data needs of the NRP. 1.2 Task Two Approach Two survey strategies were used to collect information from the participating ESF leadership. In both survey efforts, the participants answered questions designed to explore their mission objectives and overall information requirements. The first effort focused at the national ESF leadership. Each ESF was offered the opportunity to participate in a face-to-face interview with the Task Two interview team. This team consisted of staff from Booz Allen Hamilton (BAH) and representation from the DHS GMO, Federal Emergency Management Agency (FEMA) and the United States Geological Survey (USGS). The interviews were conducted over two one-week periods spaced approximately 30 days apart to facilitate scheduling. The second effort was an internet-based survey derived from the original questionnaire. This was delivered to the regional ESF leadership through the 10 FEMA Regional Interagency Steering Committee meeting coordinators.

Page 4: Department of Homeland Security (DHS) Geospatial ...files.ctctcdn.com/39123c2e001/66faab8f-f335-448b-b... · management, procurement, and licensing of geospatial data. Furthermore,

DHS Geospatial Management Office Common Operating Data Requirements

July 11, 2007 Page 4 of 39

In addition to the questionnaire, participants were asked to provide sample products (reports, SOPs, maps, etc.). The combination of survey approaches and sample product collection was designed to obtain input from both headquarters and field ESF leadership across the nation. An analysis of the collected information discovered many commonalities across the ESFs as well as the unique requirements each face in performing their missions. The array of geospatial data requirements were organized according to the data categorization initially defined in Task One and enhanced as a result of this Task (see section 2.3 Categorized Geospatial Data Requirements). This report documents the analysis results and the information collected in Task Two. Its major components are:

• an overall summary of findings • a matrix characterizing the information requirements of the ESFs • a set of ESF-specific reports

This report underwent a series of reviews:

• internal GMO • survey participants • selected subset of the HIFLD group representing the Federal entities supporting the NRP

All collected comments were assessed, and incorporated into the final report. 1.3 Task 2 Schedule

• First series of Team* interviews with ESF Leads, week of January 8-12, 2007 • Second series of Team* interviews with ESF Leads, February 5-9, 2007 • Interview notes compiled following interviews • Web survey deployed to Regional ESF Representatives, February 2, 2007 • Web survey closed, February 21, 2007 • Notes compiled • Draft report review by Interview Team and GMO, March 20, 2007 • Draft report participant review, April 2, 2007 to April 13, 2007 • Draft report HIFLD (ESF Support only) review, April 11, 2007 to April 17, 2007 • Review input compiled • Final draft report GMO review, April 24, 2007 to July 10, 2007 • Final report delivered to GMO, July 11, 2007

Page 5: Department of Homeland Security (DHS) Geospatial ...files.ctctcdn.com/39123c2e001/66faab8f-f335-448b-b... · management, procurement, and licensing of geospatial data. Furthermore,

DHS Geospatial Management Office Common Operating Data Requirements

July 11, 2007 Page 5 of 39

2 COMMON OPERATING DATA REQUIREMENTS SUMMARY 2.1 Requirements Gathering Synopsis Geospatial maps and products are utilized extensively within the ESFs for exercises, National Special Security Events, and activities related to actual events. With geospatial tools the status of ESF-specific resources and infrastructure can be easily visualized, providing clarity and additional content to briefing and report products. Across the ESFs, the leadership is identifying a multitude of geospatial requirements with minimal understanding of actions necessary to fully support them. The information requirements of the ESFs share many themes. All participants commented on their requirements for providing impact assessments specific to their individual missions and the difficulties they have in obtaining big-picture impact data for their early analysis. As the ESFs have evolved they have created supporting data-stores and developed in-house tools to simplify their processes. In many cases these data sets and tools cannot be linked to other systems. The issues of system-to-system limitations and lack of interconnectivity have continually created problems. The reasons for this include misunderstandings of technology, limited views on the value of internal information to external partners, and issues with privacy act, network security, and many others. The result of these limitations is that critical information is not available to the ESFs leadership, putting individuals in the situation of making crucial decisions with sub-standard and incomplete information. In terms of the collection and movement of information, there is a relatively thorough understanding of how general information is acquired, exploited, disseminated and reported. When the conversation focuses on the use of geospatial data, there is minimal understanding of what is available and how it is acquired and/or shared. The informal human-to-human network is critical to ensuring that the information flow is maintained regardless of the type. The relationships built through past opportunities are critical to future successes. One interviewee commented that “you need to make a friend before you need a friend.” Across all ESFs, the frequently-raised topics of internal collaboration, meetings, conference calls, the sharing of current critical documents, and re-directions based on past experiences and lessons learned bring to light the multitude of efforts required to maintain a current mission scope and ensure that the correct information is used to support it. The topic of information security (classification) was addressed for both data intake and distribution. While the major priorities revolved around unclassified information, there were constant comments made in reference to the low frequency but high-value requirements of sensitive and secure information. All ESFs that identified specific requirements to access secure information also noted they have personnel with the required credentials to support their needs. However, their analysts may not have direct access to the raw data and therefore may be operating with generalized information which they in turn provided through others. With the high-visibility of the recent Hurricane Katrina response and recovery efforts came an unusually large amount of imagery data. Imagery datasets were shared through many sources and generally available to everyone involved in the recovery efforts, many of the recipients had minimal exposure to imagery prior to this. Of the imagery users, the majority acknowledged that

Page 6: Department of Homeland Security (DHS) Geospatial ...files.ctctcdn.com/39123c2e001/66faab8f-f335-448b-b... · management, procurement, and licensing of geospatial data. Furthermore,

DHS Geospatial Management Office Common Operating Data Requirements

July 11, 2007 Page 6 of 39

they did not purchase imagery for the Hurricane Katrina operations but would expect to rely on high-resolution imagery in future events. In addition, they did not have a budget for post-event imagery or the expertise to pursue it and would rely on others to acquire and share imagery data. Interviewees felt that imagery provided the best big-picture solution for visualization and had the potential to support post-event assessments from a distance with high-resolution products. 2.2 Recommendations Several initial recommendations have been identified to support the overall geospatial requirements of the ESFs:

• Define the Big-Picture The issue of generating an all-inclusive and credible data source for the big-picture impact (e.g. wind damage, rainfall, storm surge, modeled/actual plumes, ground shaking) needs to be resolved in order to assist the ESFs in making accurate decisions in everything from initial damage estimates, strategies for asset deployments, ingress/egress efforts, media reporting, and access control following an event. Capitalizing on two complimentary solutions, imagery derived polygons and a system for compiling field collected information with citizen-based reports (e.g. intelligence derived from 911 calls), could provide a near real-time dataset to fill this critical information gap.

• Promote cross-training of the ESFs In many cases, the ESFs have a very limited understanding of the missions and objectives of their fellow ESFs. Promoting the cross-education of the ESF missions and responsibilities can compliment future activities with the sharing of information from a conscious vision of the multi-purpose relationships of data and other types of information to meet multiple objectives. With this understanding, individuals within the ESF structure may be more interested in posting their products to the Homeland Security Information Network (HSIN) for use by other groups in support of their missions.

• Maximize the use of secure and sensitive data

The use of secure and sensitive information should be explored in detail to ensure that geospatial analysts supporting Incidents of National Significance have direct access to all information available for any event. There is a general feeling that the current situation is fully capable of meeting any perceived requirements. However, most ESFs agree that this has not been fully tested in a domestic event and the consequences could be severe.

• Ensure the availability of post-event imagery and derived products The development of a national strategy for the consistent collection and dissemination of imagery and imagery derived products (damage estimates that serve the broader community as well as large scale damage estimates) needs to be explored. A solution of this type has the potential to meet 80% of the imagery requirements for the ESFs with minimal effort. It would provide crucial information to immediately support the saving of lives and property immediately following an event. To accomplish this, the general terms of “high-resolution” and “low-resolution” need to be formally defined as they relate to imagery. Collection plans must also be developed to ensure that the required

Page 7: Department of Homeland Security (DHS) Geospatial ...files.ctctcdn.com/39123c2e001/66faab8f-f335-448b-b... · management, procurement, and licensing of geospatial data. Furthermore,

DHS Geospatial Management Office Common Operating Data Requirements

July 11, 2007 Page 7 of 39

imagery is acquired effectively and the analysis is performed in an expedited manner.

• Develop a standard socio-economic model Economic impact analysis can provide major benefits in both short and long term recovery, enabling citizens to sustain their livelihoods, ensuring continuity of services, and maintaining social and economic health for an impacted area. Currently, individual groups are performing socio-economic analysis to meet their internal requirements and/or specific objectives. With multiple entities generating products and reports with their in-house models, conflicting results are shared across the disaster response community. Providing a standardized socio-economic model would assist all ESFs in their missions by providing a consistent vision of both the pre-event and post-event environments.

• Reassess ESFs per changes to the NRP

There is currently a major rewrite of the NRP and many of the supporting documents being undertaken. The outcome of this effort may necessitate reassessment of several ESFs as their missions and objectives may change significantly.

• Develop a Geospatial Concept of Operations for Disaster Response/Recovery Geospatial technology has played a significant role in disaster response for well over 15 years. In this time, individuals have been operating with minimal formal guidance and little documentation on how to conduct their business. Developing a Geospatial Concept of Operations for Disaster Response and Recovery would ensure that key information collected in the field would be transferable across the event and that all geospatial support providers would maintain a minimum continuity and level of service.

2.3 Categorized Geospatial Data Requirements To enable the identification of common data requirements, the information collected through the surveys and sample products was organized to highlight similarities and differences and analyzed to assess importance. Two additional data categories were required to fill gaps in the list of data themes: Cadastre and Event Impact. The categories were then assigned a rating for each ESF to quantify the level of need: partial (0-25%), required (25-90%), or fully required (90-100%). This analysis was compiled and summarized in Table 1: ESF Geospatial Data Requirements. The requirement ratings were reviewed by the survey participants and adjusted per their feedback. Table 2: Data Category Definitions presents for reference the data categories and definitions utilized in Table 1.

Page 8: Department of Homeland Security (DHS) Geospatial ...files.ctctcdn.com/39123c2e001/66faab8f-f335-448b-b... · management, procurement, and licensing of geospatial data. Furthermore,

DHS Geospatial Management Office Common Operating Data Requirements

July 11, 2007 Page 8 of 39

Table 1: ESF Geospatial Data Requirements

ESF Vector Data Requirements

0 Partially requires dataset (Utilized primarily for display purposes, 0%-25%

requirement)

2 Requires dataset (Key data component to support ESF analysis and decision

support, 25%-90% requirement)

Data Categories listed below are in reference to the DHS GMO COD Task1 Recommendations

4 Fully requires dataset (Essential to ESF mission, mandatory for direct decision

support, 90%-100% requirement) HSPD-7

Categories ESF

1 ESF

2 ESF

3 ESF

4 ESF

5 ESF

6 ESF

7 ESF

8 ESF

9 ESF 10

ESF 11

ESF 12

ESF 13

ESF 14

ESF 15

Agriculture / Food 0 0 2 2 4 0 0 4 0 2 4 0 0 2 4

Banking / Finance 0 0 0 0 4 2 0 0 0 0 0 0 2 2 4

Chemicals and Hazardous Materials Industry

2 0 4 4 4 0 0 4 4 4 2 2 0 2 4

Commercial Assets 2 2 4 2 4 2 2 2 4 4 2 2 0 4 4

Dams 0 2 2 2 4 0 0 2 4 2 0 4 0 0 4

Defense Industrial Base

2 4 4 0 4 0 2 2 4 2 2 2 2 0 4

Emergency Services 2 4 4 4 4 2 0 4 4 2 2 0 4 0 4

Energy 0 2 4 2 4 0 2 2 4 4 0 4 4 2 4

Government Facilities

2 2 4 2 4 2 4 4 4 2 2 2 4 2 4

Healthcare and Public Health

2 2 2 4 4 2 0 4 4 4 2 0 2 4 4

National Monuments & Icons

0 0 2 4 4 0 0 0 0 0 0 0 0 2 4

Nuclear Facilities 0 4 4 2 4 0 0 2 4 4 2 4 2 2 4

Postal / Shipping 2 0 2 0 4 2 2 2 2 2 0 0 2 0 4

Tele-communications 0 4 2 2 4 0 0 2 4 2 0 2 2 2 4

Transportation 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4

Water 0 2 4 4 4 2 0 2 4 4 4 0 2 4 4

Additional Categories

Base Map 4 4 4 4 4 4 2 4 4 4 4 4 4 4 4

Cadastre 0 4 4 4 4 4 0 2 4 4 2 0 2 4 0

Event Impact 4 4 4 4 4 4 2 4 4 4 4 4 2 4 4

Field Operating Locations

4 4 4 4 4 4 4 4 4 4 4 2 4 2 4

Man-Made Hazards 0 2 4 4 4 2 0 2 4 2 2 2 0 2 4

Natural Hazards 0 2 4 4 4 2 0 4 4 2 2 0 0 0 4

Page 9: Department of Homeland Security (DHS) Geospatial ...files.ctctcdn.com/39123c2e001/66faab8f-f335-448b-b... · management, procurement, and licensing of geospatial data. Furthermore,

DHS Geospatial Management Office Common Operating Data Requirements

July 11, 2007 Page 9 of 39

Population / Demographics

2 4 4 4 4 4 0 4 4 4 2 4 2 4 4

Specialized Response Teams

2 2 4 4 4 0 0 4 4 2 0 0 2 0 4

Threat / Suspicious Activity

2 4 4 2 4 2 0 2 4 4 4 2 4 0 4

ESF Imagery Data Requirements Imagery Usage

0 No 4 Yes

Indirect User - Benefactor of data acquired by others Direct User - Initiator/requestor/purchaser of imagery source material

Imagery Data

ESF 1

ESF 2

ESF 3

ESF 4

ESF 5

ESF 6

ESF 7

ESF 8

ESF 9

ESF 10

ESF 11

ESF 12

ESF 13

ESF 14

ESF 15

Indirect User

4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 Low Resolution

(1m to 30m)

Direct User

0 0 4 4 4 0 0 0 4 4 0 0 0 0 0

Indirect User

4 4 4 0 4 4 0 4 4 4 0 4 0 4 4 High Resolution (15cm to

1m) Direct User

0 0 4 4 4 4 0 0 4 4 0 0 0 0 0

Page 10: Department of Homeland Security (DHS) Geospatial ...files.ctctcdn.com/39123c2e001/66faab8f-f335-448b-b... · management, procurement, and licensing of geospatial data. Furthermore,

DHS Geospatial Management Office Common Operating Data Requirements

July 11, 2007 Page 10 of 39

Table 2: Data Category Definitions

Data Category Representative Sub-Categories Agriculture / Food Animal and health surveillance, agriculture and food supplies, support facilities,

product storage/transportation/distribution, ice manufacturing, etc. Banking / Finance Banking,/credit/ATM locations, securities, commodities and financial

investments, etc. Base Map Bodies of water, political boundaries, non-political boundaries, border crossings,

conservation areas, elevation, federal lands, etc. Cadastre Property boundaries, property ownership information, etc. Chemicals and Hazardous Materials Industry

Manufacturing facilities, hazardous materials inventories, superfund sites, etc.

Commercial Assets Industrial facilities, lodging, public venues, retail facilities, etc. Dams Dam locations, attributes, etc. Defense Industrial Base Location information, etc. Emergency Services American Red Cross, Emergency Operation Centers, Emergency Medical

Service, Rescue and Emergency services, Fire and law enforcement, etc. Energy Electricity, petroleum, natural gas, regulatory, oversight, industry, etc. Event Impact All impact information related to a disaster event Field Operating Locations Joint Field Offices, Disaster Recovery Centers, Joint Information Centers,

Staging Areas, Points of Distribution, etc. Government Facilities All government facilities Healthcare and Public Health

Direct patient healthcare, End-of-Life facilities, jurisdictional boundaries, offices, emergency room, etc.

Man-Made Hazards Biological, chemical, radiological, explosives related facilities, emergency warning, etc.

National Monuments & Icons

All National Monuments and Icons

Natural Hazards Weather, geologic, etc. Nuclear Facilities Active/inactive facilities, fuel storage, material transportation, waste, regulatory,

research, etc. Population / Demographics Census, crime, labor, employment, LandScan worldwide population database, etc. Postal / Shipping Postal service, shipping (residential and commercial) locations, etc. Specialized Response Teams

Urban Search and Rescue Incident Support Teams, Nuclear Incident Response Teams, Counterterrorism Response Teams, etc.

Telecommunications Wired/wireless infrastructure, coverage areas, etc. Threat / Suspicious Activity Surveillance or suspicious activity, threat reports, etc. Transportation Road, aviation, maritime, rail, Mass Transit, DOT Critical Infrastructure,

Regulatory oversight, etc. Water Raw water storage/supply, raw water intake, waste water facilities, distribution

systems, regulatory oversight, industry, etc.

Page 11: Department of Homeland Security (DHS) Geospatial ...files.ctctcdn.com/39123c2e001/66faab8f-f335-448b-b... · management, procurement, and licensing of geospatial data. Furthermore,

DHS Geospatial Management Office Common Operating Data Requirements

July 11, 2007 Page 11 of 39

3 GEOSPATIAL DATA REQUIREMENTS ANALYSIS RESULTS 3.1 Participation Summary The participation for Task Two is represented below in Table 3: ESF Respondents.

Table 3: ESF Respondents

Emergency Support Function

No. of Interview

Participants

Percent of Total

No. of Internet

Participants

Percent of Total

ESF #1 – Transportation 1 2% 1 3% ESF #2 – Communications 6 14% 0 0% ESF #3 – Public Works and Engineering 2 5% 2 5%

ESF #4 – Firefighting 2 5% 1 3% ESF #5 – Emergency Management 3 7% 12 32% ESF #6 – Mass Care, Housing, and Human Services 7 16% 2 5%

ESF #7 – Resource Support 0 0% 4 12% ESF #8 – Public Health and Medical Services 5 12% 4 12%

ESF #9 – Urban Search and Rescue 2 5% 2 5% ESF #10 – Oil and Hazardous Materials Response 5 12% 2 5%

ESF #11 – Agriculture and Natural Resources 3 7% 3 8%

ESF #12 – Energy 2 5% 2 5% ESF #13 – Public Safety and Security 1 2% 2 5%

ESF #14 – Long-Term Community Recovery and Mitigation 2 5% 1 3%

ESF #15 – External Affairs 1 3% 0 0% Total 42 100% 38 100%

3.2 Survey Results Following are the individual survey summaries by ESF. The information derived from these summaries will provide the base content upon which Tasks 3, 4 and 5 will further refine.

Page 12: Department of Homeland Security (DHS) Geospatial ...files.ctctcdn.com/39123c2e001/66faab8f-f335-448b-b... · management, procurement, and licensing of geospatial data. Furthermore,

DHS Geospatial Management Office Common Operating Data Requirements

July 11, 2007 Page 12 of 39

ESF #1 – Transportation Mission and Process ESF #1 supports DHS in assisting Federal agencies, State, local, and tribal government entities, and voluntary organizations requiring transportation for an actual or potential Incident of National Significance. With the responsibility to provide and/or coordinate the transportation of goods and persons, ESF #1 is constantly focused at the functionality of all means of transportation. The Department of Transportation (DOT), ESF #1 Coordinator and Primary Agency, operates offices in each state capitol which in turn maintain strong partnerships with State transportation departments. Information Movement and Reporting For general transportation information ESF #1 does not require access to secure information; however, when dealing with the movement of sensitive cargo or the status of sensitive infrastructure, information security is key in controlling access and ensuring an efficient response. Information intake is assisted by the day-to-day interactions with local partners. These relationships encourage local-level data sharing and assist with compiling information on post-event infrastructure damage with public and private sector transportation entities. Currently a mechanism for transferring geospatial damage and status information from the field to the National Operations Center does not exist. Information tracked and reported by ESF #1 includes:

• Road damage locations • Rail damage locations • Pipeline damage locations • Airport damage locations • Port and waterway damage locations

Vector Data The base data utilized by ESF #1 focuses on their transportation mission and is maintained at DOT headquarters. In defining the impact on an area, ESF #1 utilizes modeled data from other Federal agencies to target areas of concern. An information limitation noted was the long delays in the sharing of field level data between the field operations and the ESF leadership. Imagery Data ESF #1 uses imagery for various missions as required or available to them. As access to pre-event and post-event imagery increases, ESF #1 leadership intends on making better use of the technology. An additional imagery resource available through the ESF is the network of traffic cameras which are often under-utilized in post-event activities. Summary While standard reporting products do not contain geospatial products, ESF #1 leadership is interested in locational visibility into an event: what is damaged, what is the status of transportation infrastructure, and how are evacuation and response efforts going. Adding this visibility to the existing reporting mechanisms by exploiting post-event imagery within ESF #1 would greatly expand the sharing of information across the ESF and event. The majority of physical resources coordinated under ESF #1’s authority are owned by other government and private sector organizations. It is imperative that these resources support the collection and

Page 13: Department of Homeland Security (DHS) Geospatial ...files.ctctcdn.com/39123c2e001/66faab8f-f335-448b-b... · management, procurement, and licensing of geospatial data. Furthermore,

DHS Geospatial Management Office Common Operating Data Requirements

July 11, 2007 Page 13 of 39

maintenance of critical event related status information. With the existing State/local government and private sector partnerships, the development of a system for expediting the transfer of critical field information could be handled through a formal plan and coordination with the managing organizations. ESF Generated Data of Interest to the COD

• Transportation infrastructure damage/status • Emergency repair locations • Road closures • Road damage locations • Rail damage locations • Pipeline damage locations • Air traffic disruptions • Water traffic disruptions • Maritime transportation assets • Recommended alternate transportation routes • Access limitations • Status of mass transit systems • Private sector transportation information (Amtrak, bus service, etc.) • Air transportation (airports and air traffic)

Page 14: Department of Homeland Security (DHS) Geospatial ...files.ctctcdn.com/39123c2e001/66faab8f-f335-448b-b... · management, procurement, and licensing of geospatial data. Furthermore,

DHS Geospatial Management Office Common Operating Data Requirements

July 11, 2007 Page 14 of 39

ESF #2 – Communications Mission and Process ESF #2 ensures the provision of Federal communications support to Federal, State, local, tribal, and private-sector response efforts during an Incident of National Significance. This mission includes telecommunications, radio, and satellite networks for both voice and data communications across a combination of public and private systems. The DHS/Information Analysis and Infrastructure Protection/National Communications System is ESF #2 Coordinator and Primary Agency. Information Movement and Reporting Access to secure information sources is not a problem within ESF #2. Staff are accustomed to the restrictions of both incoming and outgoing information and are connected to the information systems they require. Information is collected through multiple means using internal and external sources. The formal system for compiling post-event information is augmented with anecdotal and other reported data obtained through an informal social network that quickly falls into place, ensuring frequent sharing of information and potentially filling data gaps. Efforts to compile information are complicated by the many public and private operators across the nation and the delays in identifying responsibility for evaluating specific outages. Information tracked and reported by ESF #2 includes:

• Quantity of customers affected • Infrastructure damage • Locations of outages

Vector Data ESF #2 uses the National Geospatial-Intelligence Agency’s (NGA) HSIP Gold as their primary base data. The ESF also utilizes propriety information from industry, including information on coverage of service, service outages, and specific details such as equipment shipped for repairs. Imagery Data ESF #2 is aware of expanding requirements of pre- and post-event planning efforts. To effectively utilize high-resolution imagery as a standard information tool, the dataset would need to be consistently available and include associated post-event topography. This solution would support the additional analysis required by the ESF and augment the existing data resources. Summary Despite complications in information collection, ESF #2 works aggressively to ensure that questions are answered as efficiently as possible with data collected through any means necessary. The pre-existing relationships with the local utilities and communications industry ensure the majority of the local-level vector data requirements are being met. To support external activities ESF #2 could provide aggregated data (degraded to address issues of proprietary information) to the response community at large. The most significant data requirement appears to be high resolution post-event imagery, topography, and big-picture impact delineations. Consistent and timely delivery of these datasets would assist ESF #2 in meeting their many response, planning, and reporting requirements.

Page 15: Department of Homeland Security (DHS) Geospatial ...files.ctctcdn.com/39123c2e001/66faab8f-f335-448b-b... · management, procurement, and licensing of geospatial data. Furthermore,

DHS Geospatial Management Office Common Operating Data Requirements

July 11, 2007 Page 15 of 39

ESF Generated Data of Interest to the COD • Sharable version of outage reports • Damage locations • Infrastructure locations

Page 16: Department of Homeland Security (DHS) Geospatial ...files.ctctcdn.com/39123c2e001/66faab8f-f335-448b-b... · management, procurement, and licensing of geospatial data. Furthermore,

DHS Geospatial Management Office Common Operating Data Requirements

July 11, 2007 Page 16 of 39

ESF #3 – Public Works and Engineering Mission and Process ESF #3 assists DHS by coordinating and organizing the capabilities and resources of the Federal government to facilitate the delivery of services, technical assistance, engineering expertise, construction management, and other support to prevent, prepare for, respond to, and/or recover from an Incident of National Significance. ESF #3 provides potable water and ice, debris collection and removal, temporary roofing, technical assistance, structural safety inspections, assistance with and temporary management of physical infrastructure, and many other services. An additional function which does not directly support a current disaster operation is the collection of critical information in support of the post-event Remedial Action Planning efforts. The US Army Corps of Engineers (USACE) is ESF #3 Coordinator and shares responsibility as Primary Agency with the Federal Emergency Management Agency (FEMA). Information Movement and Reporting There are two primary information systems supporting ESF #3, ENGLink and CorpsMap. ENGLink is the internal application used for managing all ESF #3 event related data, reporting products, operational documents, and other internal functions. CorpsMap is a mapping tool which uses a subset of geospatial information from ENGLink and makes it publicly available through the internet. Through partnerships with FEMA and other Federal and State organizations, information is shared regularly across the event. It was estimated that 99% of the data required to support the ESF mission would be described as For Official Use Only (FOUO) or public. Reporting products are passed through email channels and posted to both HSIN and ENGLink. Information tracked by ESF #3 includes:

• Impacted areas • Debris volume estimates • Staging area locations/status • Commodity distribution points • Emergency power requirements • Generator locations • Temporary housing • Vehicular access/control facilities • Commodity tracking • USACE assets • Temporary roofing requirements

Vector Data Through relationships built during non-disaster activities (e.g. hurricane planning, exercises) at the Joint Field Office and other field locations following an event, critical on-site information is created and collected in partnership with other Federal, State, and local organizations. In addition to maintaining large volumes of mission derived geospatial data, ESF #3 also hosts private sector data from NAVTEQ and TeleAtlas. Imagery Data For their general mission, ESF #3 makes use of any available satellite and/or airborne imagery resources available during an event. Imagery and the derived products from NGA and other

Page 17: Department of Homeland Security (DHS) Geospatial ...files.ctctcdn.com/39123c2e001/66faab8f-f335-448b-b... · management, procurement, and licensing of geospatial data. Furthermore,

DHS Geospatial Management Office Common Operating Data Requirements

July 11, 2007 Page 17 of 39

sources are used to identify inundated areas, determine how long areas were flooded, and assist with debris estimations. A specific task given to ESF #3 is the Blue Roof Mission which is focused at providing temporary repairs to residential roofs with rolled sheeting (often blue in color) in an effort to minimize additional weather-related damages. This project has been driven largely by the acquisition of high-resolution imagery which is used to estimate roof damage and identify candidate properties for emergency roofing and re-roofing following subsequent events. In addition to meeting the intended mission this imagery has supported many other ESFs and other Federal, State, and local entities. Summary An ESF #3 interviewee commented “When we are not responding we are planning.” This is apparent in the efforts put forth to ensure that lessons learned are applied to the next event. The geospatial information management systems supporting the ESF’s mission are very effective but could be improved with the addition of quality data identifying the initial impacts (estimated and reported), and the acquisition of high-resolution imagery and storage solutions for it. In responding to Hurricane Katrina large volumes of imagery from the Blue Roof Mission were transported to the many field operations on external hard drives, a cumbersome mechanism for sharing large volumes of data. ESF Generated Data of Interest to the COD

• High-resolution imagery of select areas (Blue Roof Mission) • Temporary roofing targets (identifier of severe wind damage) • Debris management sites (locations, staging areas, incinerators, etc.) • Temporary group housing locations • Vehicular access/control areas/sites • Emergency power assets (generators) • Modeled debris information • USACE flood-control assets • Distribution facilities for ice and water (Staging Areas, Points of Distribution) • Extent and depth of flooding • USACE managed infrastructure (levees, sea walls, etc.)

Page 18: Department of Homeland Security (DHS) Geospatial ...files.ctctcdn.com/39123c2e001/66faab8f-f335-448b-b... · management, procurement, and licensing of geospatial data. Furthermore,

DHS Geospatial Management Office Common Operating Data Requirements

July 11, 2007 Page 18 of 39

ESF #4 – Firefighting Mission and Process ESF #4’s mission is to manage and coordinate firefighting activities including fire detection and suppression occurring coincidently with an Incident of National Significance. The US Department of Agriculture (USDA) Forest Service (FS) is the ESF #4 Coordinator and Primary Agency. As Federal land managers, they have many pre-existing relationships with local land managers which can expedite access to accurate and sensitive information. Information Movement and Reporting To meet requirements of both on- and off-site efforts, the FS has multiple internet mapping applications (e.g. GeoMAC and MODIS Active Fire Mapping Program). The FS owns sensor-operating aircraft and employs staff trained to exploit the imagery. These geospatial resources ensure access to standard and dynamic geospatial datasets and availability of the products required for daily briefings and reports. Geospatial staff arriving on-scene to support ESF #4 operational and tactical objectives are often provided local data from the hosting jurisdiction. On demobilization, this local data and all event generated data and products are transferred back to the hosting jurisdiction for ongoing recovery efforts and archiving. The majority of ESF #4 reporting products contain geospatial products. Their leadership focuses on information such as:

• Location and status of current missions • Supplies availability • Quantity of resources committed/remaining • Analysis to assess likelihood of mission success • Analysis to anticipate future requirements

Vector Data Geospatial field activities usually include the collection and maintenance of ESF-specific geospatial data (helipad locations, facility locations, fire perimeters, etc.). Imagery Data ESF #4 utilizes its in-house aircraft based sensors, commercial infrared aircraft, and other Federal data sources to support its tactical information requirements. While these resources are adequate for normal fire seasons, they could be overtaxed with a very large season or when supporting both fire and non-fire events (e.g. hurricane response). For its strategic needs, the MODIS Active Mapping Program is the primary information source. Summary Due to a long history of fighting fires, ESF #4 is effectively using geospatial information in its mission. ESF #4 identified several datasets commonly unavailable to them. These include current imagery for the effected area, vector datasets for the jurisdictions adjacent to their operations, and a data storage solution to assist in their field operations. The geospatial staff will often invest much needed time, in the hours before they depart, pulling data from internet sources. Without a consolidated data resource available to them, geospatial data continues to be managed individually by multiple technicians at the workstation level.

Page 19: Department of Homeland Security (DHS) Geospatial ...files.ctctcdn.com/39123c2e001/66faab8f-f335-448b-b... · management, procurement, and licensing of geospatial data. Furthermore,

DHS Geospatial Management Office Common Operating Data Requirements

July 11, 2007 Page 19 of 39

ESF Generated Data of Interest to the COD • Fire perimeters by type • ESF related facility locations (fixed and temporary) • Resource locations

Page 20: Department of Homeland Security (DHS) Geospatial ...files.ctctcdn.com/39123c2e001/66faab8f-f335-448b-b... · management, procurement, and licensing of geospatial data. Furthermore,

DHS Geospatial Management Office Common Operating Data Requirements

July 11, 2007 Page 20 of 39

ESF #5 – Emergency Management Mission and Process ESF #5 is responsible for supporting overall activities of the Federal government for domestic incident management. ESF #5 provides the core management and administrative functions in support of National Resource Coordination Center (NRCC), Regional Response Coordination Centers (RRCC), and Joint Field Office (JFO) operations. As the coordinating entity for ESF #5, FEMA collects information from all ESFs and disseminates information to all parties involved in the event. In this capacity, ESF #5 is responsible for the management and coordination of all post-event geospatial and remote sensing activities, the acquisition of post-event imagery, tracking mobile resources, generating map products, managing geospatial data, and providing the support necessary for geospatial activities at the JFO. Information Movement and Reporting FEMA’s data management system, the National Emergency Management Information System (NEMIS), maintains all event related applicant information for all events. While this is not a geospatial data warehouse, a subset of information is pushed out to the geospatial staff. These NEMIS reports include coordinate information for funded damage locations under the Public Assistance program and applicant locations for the Human Services program. The FEMA Mapping and Analysis Center (MAC) provides full mapping support for the NRCC and limited mapping support to regional and field operations. FEMA maintains agency-wide geospatial data but does not support an agency-wide warehouse. Data is maintained individually at the regional and field level. The ESF’s geospatial support is all-inclusive for the event, deployed at the JFO under the Planning Section. Geospatial staff do not have direct access to secure information sources and must rely on managers leading other disciplines for their filtered interpretation of this critical intelligence. In an event response, the closer operations are to the actual damage locations, the more tactical their operations are in nature. As requirements increase for detailed data and products, so does the time required to discover and access local-level data, negatively impacting the delivery timelines. ESF #5 is the central hub for incident information reporting at the field, regional, and National levels. This includes the scheduled Situation Reports and ad-hoc reporting across the event. Internal reporting is covered by ESF #5 as well; all ESFs come to the Planning Section for information on the status of their counterparts. Information tracked and reported by ESF #5 includes:

• Damage locations • Displaced populations • Shelter needs • Homes destroyed • Overall impact • Historical repetitive loss areas/locations • Long-term needs • Pre-event status of region • Post-event status of region

Vector Data ESF #5 uses HSIP Gold, HAZUS, NEMIS, and other sources for their internal base data requirements. To support the post-event data and mapping requirements, the JFO staff

Page 21: Department of Homeland Security (DHS) Geospatial ...files.ctctcdn.com/39123c2e001/66faab8f-f335-448b-b... · management, procurement, and licensing of geospatial data. Furthermore,

DHS Geospatial Management Office Common Operating Data Requirements

July 11, 2007 Page 21 of 39

coordinate with their State and local counterparts for access to local, current datasets. The majority of geospatial data requirements for ESF #5 are intended to capture the multitude of un-mapped information passing from other ESFs through the many field offices and reports. Event-specific data is captured throughout the JFO in whatever manner possible. The labor required to accomplish this can insert additional delays in meeting urgent, time-sensitive requirements. Imagery Data The NRP identifies ESF #5 as the lead for all post-event remote sensing activities. Agencies supporting the NRP are required to coordinate with ESF #5 in their efforts. Imagery and derived products have been utilized by ESF #5 for some time to identify flooding, terrain, land cover, heat, and other remotely sensed information. NGA provides imagery derived damage polygons as requested by FEMA. These products are limited to the specific geographic areas requested and are not all-inclusive to an event or any political boundaries. All other imagery and remote sensing acquisitions are coordinated through the JFO and then through the Remote Sensing Coordinator who may deploy the Remote Sensing Strike Team to assist on large events. Summary The ESF #5 scope is incredibly broad, supporting the entire operation with information, resources, and centralized reporting. It is apparent that there are geospatial requirements ingrained in every mission aspect of the ESF. It is imperative that a system be implemented to capture the geospatial attributes of critical information with the initial compilation of the data rather than wait until an information crisis forces the issue. The network infrastructure can be tailored to support the passing of critical information from the field operations to the National Operations Center and back. Currently there are many issues preventing the full utilization of both geospatial technology and imagery resources available to the disaster responders. ESF #3 is the only group to provide ESF #5 with detailed pre-event imagery requirements in an effort to expedite the acquisition of post-event imagery in support of its mission. If the other ESFs provided similar information, ESF #5 would be in a better position to proactively acquire the imagery required for the disaster response community. While a very proactive effort is put forth for coordination efforts, this is hindered by the fact that many other groups operating under their own authorities do not make the effort to initiate coordination with FEMA. Formalizing a firm strategy for the coordination, collection, funding, analysis, and distribution of imagery is required to ensure that it is used to its potential. In addition it is imperative that all ESF staff have the opportunity to receive general training in the use of geospatial technology to include a thorough understanding of the potential it has for supporting their operations. ESF Generated Data of Interest to the COD

• Damage locations (imagery derived or other) • Event specific facility locations • Search status • Post-event imagery and associated imagery derived products • Public safety facilities • Repetitive loss locations • Modeled loss estimations • Impacted population demographics

Page 22: Department of Homeland Security (DHS) Geospatial ...files.ctctcdn.com/39123c2e001/66faab8f-f335-448b-b... · management, procurement, and licensing of geospatial data. Furthermore,

DHS Geospatial Management Office Common Operating Data Requirements

July 11, 2007 Page 22 of 39

ESF #6 – Mass Care, Emergency Assistance, Housing, and Human Services Mission and Process The mission of ESF #6 is to ensure that the needs of disaster impacted populations are addressed by coordinating federal assistance to impacted areas. ESF #6 supports State, regional, local, and tribal governments, and nongovernmental organization (NGO) efforts to address the nonmedical mass care, housing, and human services needs of individuals and/or families impacted by Incidents of National Significance. This effort begins with activities such as the high-profile sheltering/evacuation, carries on through temporary housing and financial assistance, and concludes with the longer-term projects of permanent repairs or reconstruction, relocation and future planning. One of the additional tasks filled for local jurisdictions is to provide technical assistance for ESF #6 related activities such as evacuation planning and local evacuation modeling. FEMA is the ESF #6 Coordinator and shares responsibility as Primary Agency with the American Red Cross. Information Movement and Reporting Multiple data-driven systems are employed to support the diverse yet interconnected activities of ESF #6. FEMA’s National Emergency Management Information System (NEMIS) houses information for response and recovery operations and the Small Business Administration (SBA) applies its Disaster Credit Management System. Other large information systems include the National Shelter System (with mapping), the National Emergency Child Locator Center, and the National Emergency Family Registry and Locator System (reunification system). These systems share non-geospatial information to provide timely assistance to the victims of an event and to support the efforts of Federal, State, and local governments as well as non-profits, NGOs and community groups in providing assistance to the human victims of an event. While this information has a geospatial component, very little is integrated into geospatial tools. In addition to these formal systems, there are requirements for developing a pre-event picture of the impacted area and a delineation of the post-event impacts. Supporting information products are frequently produced but in an ad-hoc format by multiple groups producing differing results. In supporting ESF #6 activities, SBA makes early estimates of loan volumes and values based on the anticipated quantities of FEMA applications submitted and processed in conjunction with such things as historical data for similar events. Efforts are in place to expand on this internal model to improve the accuracy of their early estimates, which are provided to US Office of Management and Budget for funding. Information is constantly tracked, compiled, and reported on topics such as:

• Applicant intake/processing/approval • Applicant distribution • Sheltered populations • Travel-trailer locations/availability • Demographic profiles • Feeding station locations and status • Economic impacts • Medical assistance locations • Employment opportunities • Temporary housing • Cost estimates for inspections and repairs

Page 23: Department of Homeland Security (DHS) Geospatial ...files.ctctcdn.com/39123c2e001/66faab8f-f335-448b-b... · management, procurement, and licensing of geospatial data. Furthermore,

DHS Geospatial Management Office Common Operating Data Requirements

July 11, 2007 Page 23 of 39

Vector Data The primary data requirements for ESF #6 are the local-level geospatial information maintained by State and local governments such as property ownership, value, building construction details, and other critical pieces of intelligence. Gaining access to this very useful data during response efforts can be extremely difficult due to formal data sharing agreements, processing and licensing fees, and the inherent delays in the Federal acquisition processes. Imagery Data Imagery has been utilized by ESF #6 in many past events but nowhere was it used more extensive than following Hurricanes Katrina and Rita. While low-resolution satellite imagery provided some big-picture awareness, access to high-resolution imagery allowed ESF #6 to expedite emergency funding to applicants with major damage and conduct quality control assessments without visiting properties in high-damage areas where access was limited. The combination of pre- and post-event imagery and easy to use software tools provided analysts with the ability to query local assessors information, measure structures, identify structure types and specific damages, and other items necessary in their reporting and approval process. While so far this approach was applied only to Katrina/Rita response, ESF #6 leadership expects to use these tools in the future when responding to major events. In areas where these imagery resources were not available, internet sources for maps, imagery, and viewing tools (Google Earth and Microsoft Virtual Earth) were utilized to assist in their work. Summary The information tracking, analysis, and display opportunities within ESF #6 are many; the challenge is determining which can provide the greatest value to the individuals affected. The inclusion of large coverage damage polygons, standardized across the event, would support much of the immediate needs for predicting the overall impact to the population. As identified above, adding critical local data and high-resolution imagery to the response and recovery efforts can drastically decrease the time required to directly assist the impacted communities and support the longer-term recovery efforts. Expanding on the social and economic impact analysis can not only create profiles of the reported populations but also assist in locating the disadvantaged populations that may be missing due to limitations such as age, income, language spoken, or physical location. ESF Generated Data of Interest to the COD

• Evacuee locations (quantity, medical, special needs, etc.) • Shelter locations • Feeding facilities • Homes destroyed • Generalized applicant damage and physical locations • Generalized financial statistics (grant amounts, loan amounts, average incomes, etc.) • Pre-event statistics on employment, special populations, etc.

Page 24: Department of Homeland Security (DHS) Geospatial ...files.ctctcdn.com/39123c2e001/66faab8f-f335-448b-b... · management, procurement, and licensing of geospatial data. Furthermore,

DHS Geospatial Management Office Common Operating Data Requirements

July 11, 2007 Page 24 of 39

ESF #7 – Resource Support Mission and Process ESF #7 assists DHS, supporting Federal agencies and State, local, and tribal governments requiring resource support prior to, during, and/or after Incidents of National Significance. This mission includes locating facility space, renting/leasing/purchasing office equipment and supplies, and other contracting services as required. They are involved in acquiring office space to house the Joint Field Office (JFO) and in some cases have pre-identified facilities for frequently impacted areas. The General Services Administration (GSA) is the ESF #7 Coordinator and Primary Agency. Information Movement and Reporting Information collection and maintenance by ESF #7 includes tracking generally stocked and historically required supplies for rapid response in emergencies. GSA has developed pre-event contracts with vendors for known resources and can identify resources within the GSA supply chain and pre-position them for event response. Information tracked and reported by ESF #7 includes:

• Monitoring the readiness of personnel • Locations of leased facilities (JFO and other event-specific) • Information to assist in the leasing of vehicles • Estimates on post-event requirements

Vector Data While minimal geospatial requirements were identified, one specific need was to provide the big-picture awareness in support of their operations. Imagery Data N/A Summary In an effort to meet their mission more effectively, staff are building from their past experiences and making plans to ensure that supplies are pre-staged and potential facilities are identified prior to an event. This information has a location component that can easily be added to a geospatial toolset to assist ESF #7 in their mission. Providing the technology to perform a site assessment with a list of potential JFO locations can ensure that a facility has adequate parking, is easy to access, is close to hotels and restaurants, and does not put the staff in harms way. Adding post-event imagery to this capability would further assist the analysis in factoring in any ill-effects from the event. Looking at their unmet data requirements, and ensuring that there is a timely feed of geospatial data identifying the big-picture impacts pre- and post-event, will support their planning requirements. Integrating geospatial technology into ESF #7 exercises would provide the education required to make better use of the technology in a post-event environment. ESF Generated Data of Interest to the COD

• Locations of JFOs • Locations of other temporary facilities (e.g. Distribution Centers, temp warehouses)

Page 25: Department of Homeland Security (DHS) Geospatial ...files.ctctcdn.com/39123c2e001/66faab8f-f335-448b-b... · management, procurement, and licensing of geospatial data. Furthermore,

DHS Geospatial Management Office Common Operating Data Requirements

July 11, 2007 Page 25 of 39

ESF #8 – Public Health and Medical Services Mission and Process ESF #8 provides the mechanism for coordinated Federal assistance to supplement State, local, and tribal governments in response to public health and medical care needs (to include veterinary and/or animal health issues when appropriate) for potential or actual Incidents of National Significance and/or during potential health and medical situations. ESF #8 participates regularly in national and international health related exercises. These events provide opportunities to work through existing plans, develop countermeasures for new event themes, share information, geospatial tools, and lessons learned. The Department of Health and Human Services (HHS) is the ESF #8 Coordinator and Primary Agency. Information Movement and Reporting HHS has a significant in-house mapping capability, integrating data from inside and outside sources into hard-copy map products and digital applications (e.g. the Health Resources and Services Administration [HRSA] Geospatial Data Warehouse and Interactive Map Tool). High security information is used when required; however, most information intake and output can be characterized as FOUO. Using various means for sharing information including email and WebEOC, ESF #8 is providing internal visibility (situational awareness) on hurricane tracks, agency personnel, vulnerable populations, and assessments of the emergency capabilities of hospitals in and around an impacted area. In day-to-day operations, worldwide events are monitored by 18 regional Emergency Coordinators across 10 regional offices to support early detection activities within the US. In support of local-level preparedness and response, close partnerships are in place with State ESF #8 counterparts to develop and maintain state-wide public health response plans and other documents. In their work, there is a conscious effort to avoid using information that cannot be shared with their state/local government counterparts. Information tracked and reported by ESF #8 includes:

• Overall impact assessments • ESF #8 related resources • Analysis for deployment planning of ESF #8 representatives

Vector Data Pulling geospatial information from a consolidated warehouse, managers have access to medical facility information, patient tracking records, blood bank locations, and other health-related resources. Event modeling applications and their derived data products come from in-house models and other health related modeling organizations including BioWatch (Centers for Disease Control [CDC] and DHS), the Interagency Modeling and Atmospheric Assessment Center (IMAAC), and the National Guard Bureau Civil Support Teams. ESF #8 staff are using HSIP Gold as their base-data source. Imagery Data On past events, imagery has been used as a back-drop to other critical information. ESF #8 has not made specific purchases of imagery for their response efforts and typically use whatever imagery is made available to them. The comment was made that they find the most value in vector map and data, capitalizing on data attributes.

Page 26: Department of Homeland Security (DHS) Geospatial ...files.ctctcdn.com/39123c2e001/66faab8f-f335-448b-b... · management, procurement, and licensing of geospatial data. Furthermore,

DHS Geospatial Management Office Common Operating Data Requirements

July 11, 2007 Page 26 of 39

Summary An emphasis was put on the requirements for vector-based geospatial data and products. These datasets are in complete control of the custodians and minimize erroneous information entering their systems and the cascading problems these situations can create. ESF #8 felt that imagery provides great value in post-event data collection and analysis but they are more concerned with having access to credible imagery derived products as opposed to the source imagery. ESF Generated Data of Interest to the COD

• ESF-specific modeling results • ESF #8 field facilities (DMAT, DMORT, VMAT, etc.) • Modeled results from other, supporting organizations • Medical facility status • Grocery distribution status • Patient tracking records (generalized) • Locations of blood bank and other mobile facilities • Locations other fixed health-related resources • EMS/Ambulance services (ground and air) • Medical capable landing zones (fixed and rotary) • Pharmacy locations

Page 27: Department of Homeland Security (DHS) Geospatial ...files.ctctcdn.com/39123c2e001/66faab8f-f335-448b-b... · management, procurement, and licensing of geospatial data. Furthermore,

DHS Geospatial Management Office Common Operating Data Requirements

July 11, 2007 Page 27 of 39

ESF #9 – Urban Search and Rescue Mission and Process ESF #9 rapidly deploys components of the National Urban Search & Rescue (US&R) Response System to provide specialized life-saving assistance during an Incident of National Significance. The two primary entities deployed under ESF #9 are the Incident Support Teams (IST) and the US&R Task Forces (TF). The IST is in place to provide overhead support to the US&R TFs and is closely integrated with the Joint Field Office. The US&R TFs conduct operations in the field and are closely connected to their local counterparts. To address their internal requirements the US&R program has 12 functional groups designed to work with topical items. This methodology assists the ESF in incorporating lessons learned, adapting new ideas, and making recommendations on implementing new tools and technology. FEMA is the ESF #9 Coordinator and Primary Agency. Information Movement and Reporting As users of the Incident Command System, many of the ESF’s standard reporting products and briefings require the inclusion of geospatial products to assist in situational awareness. A subset of ESF #9 personnel have security clearances, insuring that any relevant information from secure sources can be incorporated in their efforts. The US&R TFs work closely with their local counterparts, building relationships that assist in acquiring high-quality local-level geospatial information to support their efforts. In defining their pre-event requirements, ESF #9 works closely with their stakeholders to identify the potential impact of notice events and the predicted impact for no-notice events. In support of ESF #9 mission, the US Coast Guard (USCG) has deployed the Search and Rescue Optimal Planning System (SAROPS), a geographic information system (GIS) tool to be used for managing/monitoring incident response. Internal and external information requirements include:

• Locations of potential victims • Monitoring the number and locations of individuals rescued and recovered • Damaged structures • Tracking search status and progress • Monitoring of resource positions and activities

Vector Data Vector base data and event-specific data elements are minimum requirements; ESF #9 resources provide much of the field data collection. Adding local data as soon as possible after arriving on-site increases the accuracy and validity of products. Imagery Data High-resolution imagery is needed both before and after the event. Combining the post-event imagery with quality pre-event street data assists in navigating through an area where the land-marks and signage are heavily damaged or completely missing. Oblique imagery and tools have great potential but have been underutilized in the past. Summary With an aggressive focus on response activities, Search and Rescue efforts must have guaranteed access to a constant flow of critical information to assist in saving lives. This includes all

Page 28: Department of Homeland Security (DHS) Geospatial ...files.ctctcdn.com/39123c2e001/66faab8f-f335-448b-b... · management, procurement, and licensing of geospatial data. Furthermore,

DHS Geospatial Management Office Common Operating Data Requirements

July 11, 2007 Page 28 of 39

information reported by ESFs as well as any available imagery. Looking at past events where the overall event magnitudes were similar but the area impacted varied from small to enormous (9/11 in New York vs. Columbia Shuttle Recovery vs. Hurricane Katrina), a critical information source within ESF #9 was the daily out-briefs. The out-brief provided all the information from the US&R efforts on who was where, what was observed, and what was accomplished. On every significant deployment, geospatial data collection plans were created (and re-created), causing delays in providing current geospatial products. Without access to a geospatial data warehouse, opportunities to maintain near-real-time field information (e.g. structures searched, victims rescued, 911 reports to investigate), search efforts must be managed with less effective information tools. ESF Generated Data of Interest to the COD

• Field facilities (Base of Operations, Staging Areas, Drop Points, etc.) • Team locations • Mobile resource locations • Area divisions • Search grid boundaries • Search status • Aggregate rescue/fatality counts • Structure damage • Landing zones

Page 29: Department of Homeland Security (DHS) Geospatial ...files.ctctcdn.com/39123c2e001/66faab8f-f335-448b-b... · management, procurement, and licensing of geospatial data. Furthermore,

DHS Geospatial Management Office Common Operating Data Requirements

July 11, 2007 Page 29 of 39

ESF #10 – Oil and Hazardous Materials Response Mission and Process ESF #10 provides Federal support in response to an actual or potential discharge and/or uncontrolled release of oil or hazardous materials during Incidents of National Significance. In protecting public health and the welfare of the environment (air, water, solid waste, and toxic substances), geospatial technology is ingrained in many of the efforts undertaken by ESF #10. The Environmental Protection Agency (EPA) is the ESF #10 Coordinator. With specific threats facing different regions of the country, the EPA builds on the local expertise of their regional offices to develop standard operating procedures and other documents for their areas of expertise (e.g. hurricanes, earthquakes, mining). Information Movement and Reporting The Emergency Response Analyzer (ERA) is an internal application recently developed to visualize impacts from environmental emergency situations and identify potential effects on the population. The output from this and other models (e.g. NARAC, IMAAC) provide information to support critical decision making in the early stages of an event response. Extensive data warehouses are maintained and accessed from internal and external sources; specific examples are the Toxic Release Inventory, EnviroFacts, the Agency for Toxic Substances and Disease Registry (ATSDR), and chemical storage information (fixed facilities, vehicles, vessels, etc.). Information security is a significant concern due to the frequent reporting and information collection above the confidential classification. It is imperative that all communication of information from these environments be passed to the field staff supporting the tactical, on-site decision making. To share information and formal reports, many mechanisms are utilized including HSIN, WebEOC (internal to EPA) and others. Information sharing is promoted from the beginning of operations with field personnel operating as liaisons with local entities. In addition to the known sources of information, it is important for the other ESFs to understand that the theme-specific information they collect and/or produce can be utilized by others to assist them in accomplishing their objectives. Information tracked and reported by ESF #10 includes:

• Identification of the incident scope (big-picture) • Effected populations (human and/or environment) • Evacuation/transportation status • Environmental characterization (before/after) • Tracking/monitoring ESF progress in protecting public health/welfare • Assessing impacts on human health • Monitoring status of regulated facilities • Managing available assets • Transportation requirements associated with the ingress/egress of personnel • Monitoring of water intake status • Tracking waste disposal issues • Air/soil concerns

Vector Data The majority of ESF #10 vector data requirements are met through their existing systems and procedures. Unmet requirements are the big-picture impact themes and tentative plans for delivering the unique event-specific information.

Page 30: Department of Homeland Security (DHS) Geospatial ...files.ctctcdn.com/39123c2e001/66faab8f-f335-448b-b... · management, procurement, and licensing of geospatial data. Furthermore,

DHS Geospatial Management Office Common Operating Data Requirements

July 11, 2007 Page 30 of 39

Imagery Data Much of the imagery used within the ESF has been acquired by other functional areas of the response effort. As requirements for satellite and airborne imagery products increase it is important to ensure that these datasets are readily available for mass consumption across the responders. High-resolution imagery provides an unparalleled advantage in tactical decision-making. Currently efforts are on-going to access classified imagery sources in near-real-time to assist in this. Summary The statement was made in the interview that “We must have GIS tools.” This sets the stage for the use of geospatial technology for ESF #10 efforts. To add to the complexity of the ESF’s overall mission, the USCG is responsible for hazardous materials issues out to 200 miles off the US coast. The major unmet requirements identified were big-picture imagery and imagery derived products, availability of easy to access high-resolution imagery, and access to near-real-time imagery sources to meet the immediate efforts of their mission. Overall ESF #10 is maintaining large geospatial warehouses, sharing critical internal information freely between their systems, and serving data and compiled information to the public. ESF Generated Data of Interest to the COD

• Regulated facilities • Sensitive areas (environmental sensitivity index) • Chemical spill locations • Field Team locations • Jurisdictional boundaries (e.g. CG Jurisdiction, EPA Jurisdiction) • Boom placements (oil spill)

Page 31: Department of Homeland Security (DHS) Geospatial ...files.ctctcdn.com/39123c2e001/66faab8f-f335-448b-b... · management, procurement, and licensing of geospatial data. Furthermore,

DHS Geospatial Management Office Common Operating Data Requirements

July 11, 2007 Page 31 of 39

ESF #11 – Agriculture and Natural Resources Mission and Process ESF #11 supports State, local, and tribal authorities and other Federal agency efforts to address: (1) provisions of nutrition assistance; (2) control and eradication of an outbreak of significant occurrences of animal/zoonotic disease, exotic plant disease, plant infestation; (3) assurance of food safety and security, and (4) protection of natural and cultural resources and historic properties prior to, during, and/or after an Incident of National Significance. Several of the specific ESF #11 objectives identified were the determination of nutritional assistance requirements in the impacted areas, impacts due to the closure of animal processing facilities, support required for congregated feeding operations, and approving/monitoring emergency food-stamp programs for disaster victims. The USDA is the ESF #11 Coordinator and shares responsibility as Primary Agency with the Department of the Interior. Information Movement and Reporting Several information systems are used regularly including the in-house Non-Routine Incident Management System and the National Bio-Surveillance Integration System (NIBS) which will integrate internal information from multiple agencies into a sharing and collaborative environment. Modeling software applications are used regularly including HAZUS and HURREVAC. The results from these models combined with modeled information provided by the IMAAC allow analysts to create risk profiles and products providing estimations for planning activities. USDA has developed the web-based (also available on CD) USDA FND Disaster Assistance Tool Kit which contains documents detailing rules and regulations, ESF-specific procedures, points of contact, and other critical information. Close relationships are maintained with State and local stakeholders, the ESF’s support agencies, and other Federal agencies such as the CDC. Exercises are led and supported extensively by the ESF leadership to ensure that plans are kept current and personnel are trained. The majority of information accessed and reported by the ESF falls into the FOUO category. Some of the products developed to support leadership and others include ESF #11 resource locations, economic impact to the effected area, and impacted facilities. About 90% of the reported information is utilized internally. Information analyzed, tracked, and reported by ESF #11 includes:

• Needs assessment for food • Locations for meeting feeding requirements • Status of activities with States and relief organizations to get food out • Additional commodity needs • Analysis for food-stamp assistance requirements

Vector Data While the HSIP Gold datasets provide much of the core data for the ESF, internal information on facilities is updated regularly and integrated into their products. A specific data requirement noted was high-resolution elevation information. Imagery Data ESF #11 did not identify any significant requirements for imagery but did mention that they have looked into various federal sources.

Page 32: Department of Homeland Security (DHS) Geospatial ...files.ctctcdn.com/39123c2e001/66faab8f-f335-448b-b... · management, procurement, and licensing of geospatial data. Furthermore,

DHS Geospatial Management Office Common Operating Data Requirements

July 11, 2007 Page 32 of 39

Summary The mission of ESF #11 is enormous. It covers human nutrition, food safety, animal disease, and natural/cultural resource protection. The ESF accesses large volumes of data managed by other organizations; much of this information could be modified slightly and shared with other ESFs who could us it to assist with their decision making. Access to post-event imagery and derived products is a concern. In past events, data has been made available in a delayed environment, creating frustration for individuals who could have utilized it when it was current. This would indicate that they have not had the opportunity to utilize imagery successfully, a situation that could be resolved with a national strategy for post-event data. In meeting the dynamic objectives of the ESF, ensuring that the COD is available to support the many geospatial products would be of great benefit. ESF Generated Data of Interest to the COD

• Animal and plant disease areas/locations • Feeding stations • Natural resource locations • Cultural resource locations • Economic impact from the closure of ESF coordinated facilities • Public conveyance status • Number of persons requiring movement (all and special needs)

Page 33: Department of Homeland Security (DHS) Geospatial ...files.ctctcdn.com/39123c2e001/66faab8f-f335-448b-b... · management, procurement, and licensing of geospatial data. Furthermore,

DHS Geospatial Management Office Common Operating Data Requirements

July 11, 2007 Page 33 of 39

ESF #12 – Energy Mission and Process ESF #12 is responsible for providing Federal assistance to restore damaged energy systems and components during a potential or actual Incident of National Significance. As an industry coordinator, ESF #12 does not own infrastructure and relies on partnerships with the energy industry to support its mission. ESF #12 facilitates the restoration of energy systems through legal authorities and waivers and provides technical expertise to the utilities, conducts field assessments, and assists government and private sector stakeholders to overcome challenges in restoring the energy system. The Department of Energy (DOE) is the ESF #12 Coordinator and Primary Agency. Information Movement and Reporting Information security is critical to ensure that the competing interests of the infrastructure owners are kept secure. Most of ESF #12’s infrastructure location information is classified as “Critical Infrastructure” and must be protected in accordance with the Protected Critical Infrastructure Information (PCII) Program. Internally, the DOE National Laboratories (Visualization and Modeling Working Group) meet regularly to discuss and model the potential impacts to electric power, oil, natural gas, and coal infrastructures, analyze economic market impacts, and determine the effect a disruption has on other critical infrastructures and key resources. ESF #12 Regional Coordinators attend meetings and exercises covering national, state, and local pre-event disaster response efforts. Information intake is accomplished by accessing internet sources owned by various company and industry organizations, contacts with local governments and private industry, and industry oversight groups such as the Federal Energy Regulatory Commission. ESF #12 is responsible for providing information concerning the energy restoration process including projected schedules, percent completion of restoration, and geographic information on the restoration. ESF#12 representatives work with FEMA regions, states, and the private sector to develop procedures and products that improve situational awareness to effectively respond to a disruption of the energy sector. ESF #12 provides products and reports to the NRCC, RRCCs, and JFOs and posts to the ESF’s portal on HSIN. In addition, DOE produces an emergency wide situation report providing information awareness across the impacted area. The information products generated by ESF #12 includes:

• Status reports, maps, and graphics • Monitoring of energy status (electric, oil, natural gas, and coal) • Effected infrastructure • Restoration timelines • Interdependencies across the industry • Market impacts • Temporary power requirements • Restoration prioritization • Fuel distribution • Industry mutual-aid assistance (where to go, road blocks, transportation damage)

Vector Data Internally, geospatial data is used extensively to support modeling and visualization efforts. These datasets include detailed information on energy related facilities and infrastructure as well

Page 34: Department of Homeland Security (DHS) Geospatial ...files.ctctcdn.com/39123c2e001/66faab8f-f335-448b-b... · management, procurement, and licensing of geospatial data. Furthermore,

DHS Geospatial Management Office Common Operating Data Requirements

July 11, 2007 Page 34 of 39

as general base data for the US. When responding to an event, ESF #12 is collecting local-level damage information from their partners, validating their models, and sharing information on energy system damage. In addition they provide estimates on the impact of energy system outages within affected areas through reports and graphic representations of map products. Imagery Data ESF #12 uses satellite imagery indirectly, accessing data through internet tools (e.g. Google Earth) and utilizing imagery available at no-cost for map products. ESF #12 has not purchased commercial imagery but does have some capability to acquire and process imagery through the DOE laboratories. In the interview, ESF#12 leadership mentioned that adding a compliment of imagery tools to iCav would be beneficial to them due to the difficulties in managing and serving large volumes of data across their network infrastructure. Summary As a coordinator of assets and resources owned and operated by non-Federal entities, ESF #12 information collection and reporting is dependant on input from outside sources. While the post-event information is collected in both text and geospatial formats, reporting products do not typically include maps or geospatial data. In past events this has been a great burden on the response community at large as they struggle to interpret the reported information. The combination of the delay in processing reported information and the speed at which damaged systems are restored creates constant confusion in trying to monitor the status of the energy infrastructure. ESF #12 is currently developing tools to push geospatial information to the FEMA Regions in an effort to expedite the dissemination of energy related information to the crisis management community. ESF Generated Data of Interest to the COD

• Power outage locations • Infrastructure damage locations

Page 35: Department of Homeland Security (DHS) Geospatial ...files.ctctcdn.com/39123c2e001/66faab8f-f335-448b-b... · management, procurement, and licensing of geospatial data. Furthermore,

DHS Geospatial Management Office Common Operating Data Requirements

July 11, 2007 Page 35 of 39

ESF #13 – Public Safety and Security Mission and Process ESF #13 integrates Federal public safety and security capabilities and resources to support the full range of incident management activities associated with potential or actual Incidents of National Significance. The Department of Justice (DOJ) is the ESF #13 Coordinator and Primary Agency. Information Movement and Reporting As law enforcement members, ESF #13 staff have access to information available across all security levels to meet the public safety and security mission. During event responses this information flows internally and externally in the form of frequent written reports and briefings. Through exercise support and meeting attendance, the ESF mission is shared and local contacts are maintained. Common reporting topics include:

• Resource needs • Locations of ESF resources • Analysis for deployment planning of ESF #13 staff • Staff requirements, availability, and estimated time of arrival

Vector Data At present, ESF #13 makes minimal use of geospatial products. Imagery Data At present, ESF #13 makes minimal use of imagery. Summary ESF #13 currently makes little use of geospatial technology. Given their broad mission and diverse information requirements, adding this technology to their process would provide visibility into events which is currently unavailable. Providing leadership with an accurate picture of the situation-at-hand and the ability to answer dynamic questions from their desktop could add a new awareness of what geospatial technology can do for ESF #13. With respect to imagery, the combination of oblique imagery and its software can allow personnel to make critical field-level decisions without being on-site. In a terrorism related environment this could be the only picture into an impacted area. ESF Generated Data of Interest to the COD

• Static facility locations (Law Enforcement and Fire) • Event-specific field locations • Field Team locations

Page 36: Department of Homeland Security (DHS) Geospatial ...files.ctctcdn.com/39123c2e001/66faab8f-f335-448b-b... · management, procurement, and licensing of geospatial data. Furthermore,

DHS Geospatial Management Office Common Operating Data Requirements

July 11, 2007 Page 36 of 39

ESF #14 – Long-Term Community Recovery Mission and Process ESF #14’s mission is to provide a framework for Federal government support to State, regional, local, and tribal governments, NGOs, and the private sector designed to enable community recovery from the long-term consequences of an Incident of National Significance. FEMA, as the ESF #14 Coordinator, works closely with the local communities in developing detailed plans for post-event recovery. These plans generally include before-and-after assessments with supporting geospatial products. Information Movement and Reporting The Impact Assessment Tool is an internally developed model which provides prescreening of the impacted communities to warrant long-term recovery work then further analyzes the specific communities for housing, economic, infrastructure, government, and other functions. Access to secure information sources is of minimal concern; with the majority of the ESF’s work being preformed after the initial response and in close partnership with the local communities and citizens, information must be available to the public. One of the initial reports within the ESF is focused at the immediate deployment requirements and predictions for the long-term personnel and resources needs. Information tracked and reported by ESF #14 includes:

• Pre-event status of the region • Current status of the region • Duration (temporal) and depth of standing water • Analysis of economic and social impacts

Vector Data Datasets maintained to support the ESF include lists of multifamily property owners and available vacant housing units in the public and private sectors. ESF #14 typically relies on ESF #5 GIS operation to provide all data collection and mapping support. Imagery Data While ESF #14 has not identified any specific requirements for imagery, all available imagery was utilized in their post-Katrina efforts. Summary ESF #14 provides direct support to local communities and the private sector (e.g. businesses, agriculture operations, nonprofits) and therefore builds and maintains close relationships with them. These relationships support the efforts of the ESF and provide contacts for the critical local-level data collection required to support their projects. These datasets include high resolution pre-event imagery, assessors data, historic property inventories, soils data, environmental information, zoning, and many others. With specific requirements for local data and the large efforts required to acquire and make use of the data, data acquisition opportunities should be pursued as soon as possible following an event. ESF #14 should explore the advantages of adding a geospatial capability to the Impact Assessment Tool, as there are many datasets which could add significant value to their analysis, particularly the overall extent of damage (by type). Currently impact data is collected and disseminated as damage polygons, which offers information on impact locations but does not supply any specifics on damage type.

Page 37: Department of Homeland Security (DHS) Geospatial ...files.ctctcdn.com/39123c2e001/66faab8f-f335-448b-b... · management, procurement, and licensing of geospatial data. Furthermore,

DHS Geospatial Management Office Common Operating Data Requirements

July 11, 2007 Page 37 of 39

Without this big-picture scope, the current data is of little value for ESF #14. Imagery and the data products derived from it offer significant amounts of post-event information for ESF #14. Even without specific requirements for imagery, the ESF will expect to have access to suitable products collected earlier in the response and recovery efforts to support their pre-event/post-event analysis. ESF Generated Data of Interest to the COD

• Economic impact information • Social impact information • All event-specific local data • ESF project locations • Data supporting long-term recovery planning

Page 38: Department of Homeland Security (DHS) Geospatial ...files.ctctcdn.com/39123c2e001/66faab8f-f335-448b-b... · management, procurement, and licensing of geospatial data. Furthermore,

DHS Geospatial Management Office Common Operating Data Requirements

July 11, 2007 Page 38 of 39

ESF #15 – External Affairs Mission and Process ESF #15 ensures that sufficient Federal assets are deployed to the field during a potential or actual Incident of National Significance to provide accurate, coordinated, and timely information to effected audiences, including governments, the private sector, and local populace. As the ESF Coordinator DHS maintains contact with the entire industry, connecting with the media, agency representatives for public information, and other partners. Information Movement and Reporting The ESF needs access to every available information resource and employs personnel with the credentials required to access these resources. Specific data used include industry-proprietary information such as VOCUS, reported anecdotal evidence, media reports, and various imagery. All information is processed for public consumption. ESF #15 works to provide the most accurate information products (e.g, maps, charts, graphs, and data) in the shortest time possible to support press conferences and other requirements with hard deadlines. Geospatial products are used regularly to support internal communications and meet the multitude of external requirements (e.g. congressional briefing books, public outreach, VIP briefings, and press releases). Reporting requirements vary by event. Products are distributed generally using HSIN or directly to a specific customer. Some topics monitored and reported on in the past include:

• Location of big-picture impacts • Customer-specific impacts (e.g. congressional districts, cities) • Overall distribution of damages and specific damage types • Graphic comparisons (i.e., Hurricane Katrina was big enough to cover the UK)

Vector Data ESF #15 has no specific vector data requirements. Imagery Data Although ESF #15 has not acquired or purchased imagery directly, they frequently make use of imagery resources provided during response and recovery operations. These resources are used as backdrops for other elements and are shared when they can be made available to requestors. Summary ESF #15 uses a significant amount of geospatial products but does not appear to use the technology to its full potential. The ability to analyze event information collected by others and provide credible answers with the results could simplify and expedite the creation of information tools to support their mission. The ESF noted that questionable and/or inaccurate information needs to be avoided as it requires additional efforts to resolve. Ensuring the quality and integrity of information used by any ESF can be addressed through metadata and further development of the COD. Adding the big-picture data derived from imagery would provide immediate clarity to the situation and much-needed assistance in getting a message out as quickly as possible. ESF Generated Data of Interest to the COD

• High profile locations • Publicly consumable protective action information (evacuations, shelter, etc.)

Page 39: Department of Homeland Security (DHS) Geospatial ...files.ctctcdn.com/39123c2e001/66faab8f-f335-448b-b... · management, procurement, and licensing of geospatial data. Furthermore,

DHS Geospatial Management Office Common Operating Data Requirements

July 11, 2007 Page 39 of 39

Appendix A. List of Acronyms COD Common Operating Data DHS Department of Homeland Security DOE Department of Energy DOT Department of Transportation EPA Environmental Protection Agency ESF Emergency Support Function FEMA Federal Emergency Management Agency FOUO For Official Use Only FS Forest Service GIS Geographic Information System GMO Geospatial Management Office GSA General Services Administration HHS Department of Health and Human Services HIFLD Homeland Infrastructure Foundation-Level Data HSIN Homeland Security Information Network IST Incident Support Team JFO Joint Field Office NGA National Geospatial-Intelligence Agency NGO Nongovernmental Organization NRCC National Resource Coordination Center NRP National Response Plan RRCC Regional Response Coordination Centers SBA Small Business Administration USACE US Army Corps of Engineers USCG US Coast Guard USDA US Department of Agriculture US&R Urban Search & Rescue