Guidebook on Integrating GIS in Emergency Management at Airports (2013)

Below is the uncorrected machine-read text of this chapter, intended to provide our own search engines and external engines with highly rich, chapter-representative searchable text of each book. Because it is UNCORRECTED material, please consider the following text as a useful but insufficient proxy for the authoritative book pages.

P a r t I I I Model GIS-EM Integration Plan How to Use the Model Plan This Model Plan (plan) has been developed as a standalone grab & go resource. The text discussing the various elements and tool are fully provided. Placeholders to insert your airport’s name appear in parentheses. Tool placeholders indicate the location of the tool to be completed and where to locate the tool in Appendix M-A. This appendix contains a complete tool set of all necessary tools for this plan in a full-page, ready-to-use format. This tool set, along with the plan and its appendices, is also provided on an enclosed CD-ROM. Once all tools have been completed and inserted, the result is a fully developed GIS-EM Integration Plan tailored to your specific situation.

Model GIS-EM Integration Plan 57 MODEL GIS-EM INTEGRATION PLAN (AIRPORT NAME) GIS-EM Integration Plan Date adopted Date of Last Revision

58 Guidebook on Integrating GIS in Emergency Management at Airports DOCUMENT REVISION Revision Date Content Revision Date Content

Model GIS-EM Integration Plan 59 TABLE OF CONTENTS INTRODUCTION.................................................................................................................................... 60 CHAPTER 1 – VISION........................................................................................................................... 62 CHAPTER 2 – RESOURCES................................................................................................................. 63 CHAPTER 3 – LAUNCH........................................................................................................................ 65 CHAPTER 4 – DEVELOP AND IMPLEMENT.................................................................................. 68 CHAPTER 5 – PROGRESS AND ENHANCE..................................................................................... 69 APPENDICES.......................................................................................................................................... 70

60 Guidebook on Integrating GIS in Emergency Management at Airports INTRODUCTION Purpose This document provides the GIS-EM Integration Plan (plan) for (AIRPORT NAME). It was developed by the airport’s GIS-EM Integration Committee under the sponsorship of Airport Operations. Membership in (AIRPORT NAME)’s GIS-EM Integration Committee comprises representatives from (AIRPORT NAME)’s department as well as (INSERT ORGANIZATIONS). The committee recognizes that understanding individual emergency management plans and the efforts of law enforcement, fire protection, emergency medical services, and other emergency management agencies/providers is essential to successfully implementing GIS in Emergency Management situations. This coordinated plan provides a common point of focus for (AIRPORT NAME)’s Emergency Management operations utilizing GIS. This plan is a “living” document that will be regularly updated and will incorporate lessons learned and best practices from Emergency Management response activities at (AIRPORT NAME). With an emphasis on continual improvement, this plan will identify areas where GIS integration has occurred successfully and where GIS can potentially be applied in Emergency Management situations involving (AIRPORT NAME). This process will involve an understanding of current emergency management procedures; GIS technology; data, system and operational requirements; personnel training; and audits and debriefing exercises. To ensure the validity of data and technology will require that this plan receive ongoing updates as well as associated communication and training for all agencies involved. Use of Terms The following is a list of terms and definitions used throughout this plan and associated tools. See the Glossary contained in ACRP Report 88: Guidebook on Integrating GIS in Emergency Management at Airports for additional terms and definitions. Geographic Information System (GIS) – The technology system inclusive of hardware, software, and infrastructure for the collection, management, analysis, and presentation of geospatial data. Geospatial data are primarily represented in a map format with symbols, icons, and text providing feature information. Emergency Management (EM) – The comprehensive set of functions that can be executed within its defined four phases that support an airport’s emergency operations. These phases are Mitigation / Planning – sustained actions taken to reduce or eliminate long-term risk to people and property from natural or man-made hazards and their effects Preparedness – processes to sustain and improve operational capability to prevent, respond, and recover from emergency incidents

Introduction 61 Response – immediate actions taken to contain, reduce, or prevent further impact of an incident on the public and environment Recovery – the long-term activities required to return all airport operations to a normal state after incident or emergency response has contained an incident Within each of these phases, there are functions that can be performed by a variety of entities that support an Airport’s Emergency Management operations. These entities may exist in locations that are on the Airport premises or outside of the Airport boundaries. Additionally, these entities may operate within the Airport’s authority, as a peer organization within a government organization, or through a mutual agreement or relationship developed between the Airport and external emergency response organizations. Regardless of how an Airport establishes its emergency operating structure, using Mutual Aid Partners and/or other emergency support entities, the term Emergency Management represents any of the operational actions within the subset of all Emergency Management phases. Emergency Management Technology Needs at Airports Responding to emergency situations at (AIRPORT NAME) is complex, as first responders need to immediately assess often incomplete and conflicting communication from a variety of sources. There is a need to enhance communication between responding organizations, including incident command, operations centers, remote stakeholders, government officials, news media, and the public. There are many technological means to capture and deliver organized communication using a wide array of technology during the four phases of Emergency Management. Mobile technology, such as smart-phones and tablets, enables solutions using GIS data for improving planning, situational awareness, and recovery functions. GIS Opportunities in Emergency Management at Airports GIS can provide mapping information as well as geospatial data layers that have been proven valuable to Emergency Management applications and functions. As a robust technology, GIS can serve in a variety of means in all four phases of Emergency Management. Airports primarily use GIS for asset identification, or the understanding of where things are and how they can be accessed to make decisions faster in emergency situations. Asset identification involves eALP data; facility floor maps and utility lines; and assets such as fire hydrants, defibrillators, emergency call boxes, access control maps, and hazmat locations. Specialized maps can also be developed using GIS to identify locations for staging areas and evacuation routes with assembly points, as well as routing of emergency response personnel and automatic vehicle location. These systems often have the ability to be interactively used by Emergency Management personnel.

62 Guidebook on Integrating GIS in Emergency Management at Airports CHAPTER 1 - VISION 1.1 Vision Statement & GIS-EM Integration Committee The (AIRPORT NAME) Vision Statement has been developed considering the input from stakeholders and leadership, as represented in the GIS-EM Integration Committee. Instructions: Create the Leadership/Stakeholder List (Tool 3-2a) as provided in Appendix M-A1 and engage them to develop the vision statement using Tool 3-2b, as provided in Appendix M- A2. Then insert the finalized and agreed upon vision statement here! (AIRPORT NAME)’s (ORGANIZATION and TITLE) provides the sponsorship and designates the chairperson of the committee. Members of the (AIRPORT NAME) GIS-EM Integration Committee include representatives of Airport staff involved with emergency response along with fire and law enforcement (on and off airport), government agencies, airlines, and mutual aid resources. Organizations and representatives are shown in the GIS-EM Integration Leadership and Committee tables. Instructions: Develop the GIS-EM Integration Committee List (Tool 3-2c), as provided in Appendix M- A3, and insert here! 1.2 Airport Emergency Event Assessment This assessment includes a selection of emergency situations at the airport, including small (i.e., aircraft fire); intermediate (i.e., prolonged snowstorm); and extensive (i.e., earthquake) events to assess. This review provides an understanding of how these events have been handled from an Emergency Management perspective. This assessment also looks at the specific hazards identified in the airport’s AEP. It also provides an opportunity to review how GIS has been used (successfully or unsuccessfully) in these situations and where opportunities might exist for either implementing new or improving on performance. Evaluating the application and role of GIS in the plans for each hazard could augment a historic event assessment. Instructions: Complete the Airport Emergency Event Assessment Tool (Tool 3-1), as provided in Appendix M-A4, and insert here! NOTE: Multiple scenarios could/should be developed and inserted here.

Resources 63 CHAPTER 2 - RESOURCES Current information on GIS, EM, and their integration, as well as staffing, training, and cost considerations have been incorporated in this chapter. The information in this chapter is periodically updated so that it represents the current situation. Changes are recorded when executed, making this a living document that can be referred to as needed. 2.1 Current GIS Environment It is recognized that (AIRPORT NAME) has GIS resources available for use in GIS-EM Integration. The GIS Availability and Accessibility table lists resources available, not just those directly involved in EM. Instructions: Complete the GIS Availability and Accessibility Tool (Tool 4-1), as provided in Appendix M-A5, and insert here! 2.2 Current EM Environment An understanding of the current EM environment is needed for identifying opportunities to integrate GIS and Emergency Management at (AIRPORT NAME). This is described and the specific EM equipment listed below. Instructions: Complete the Emergency Management Environment Tool (Tool 4-2), as provided in Appendix M-A6, and insert here! 2.3 Current GIS-EM Integrations Existing GIS-EM Integrations at (AIRPORT NAME) and their current purpose are provided below. Instructions: Complete the GIS-EM Integration Tool (Tool 4-3), as provided in Appendix M-A7, and insert here!

64 Guidebook on Integrating GIS in Emergency Management at Airports 2.4 Skills Availability Emergency Management staffing involves a variety of personnel who may be accessed from a combination of airport, emergency response, and mutual aid agencies. Specific GIS-EM skills are noted in the following table. Instructions: Complete the GIS-EM Skills Integration Tool (Tool 4-4), as provided in Appendix M-A8, and insert here! 2.5 Cost Identifying various cost items and considerations relating to both areas, start-up and sustainability are captured in the tables below. These costs come from a variety of sources, and include hardware, software, network, and personnel categories. Multiple agencies are involved in GIS-EM Integration and each agency’s cost considerations are reported in the table when available. Instructions: Complete the Resources Cost Considerations and Budget Tool (Tool 4-5), as provided in Appendix M-A9, and insert here!

Launch 65 CHAPTER 3 - LAUNCH This chapter of the (AIRPORT NAME) GIS-EM Integration contains tools that will be revisited by the committee to assess work that has been accomplished and identify potential new aspects of GIS-EM Integration. Collaboration Workshops are helpful in finding and evaluating GIS-EM Integration. 3.1 Milestone Matrix Understanding milestones is necessary to provide a historical context of GIS development and provides a breakdown of the system development which can be used in performance assessment. Milestones are indicated in the table below. Instructions: Complete a modified version, based on your objectives and situation, of the sample Milestone Matrix, as shown in the City of Phoenix Case Study Report in Appendix C of the Guidebook, and insert here. 3.2 Assessing /Auditing Performance Before launching GIS, it is important to develop an assessment and auditing tool so that the system can be evaluated from the start. Creating an auditing program to assess GIS performance is necessary for ensuring continual improvement of the system. This program can be administered as a series of performance-based questions. Instructions: Complete the Assessment / Auditing Tool (Tool 5-2), as provided in Appendix M-A10, and insert here! 3.3 Host GIS-EM Collaboration / Integration Workshops (AIRPORT NAME) will periodically host workshops that focus on GIS-EM integration. Reasons for scheduling a workshop can be assessing a recent event, testing new GIS-EM functionality, or annual updating of planned enhancements. Tabletop exercises focused on GIS-EM integrations bring together EM and technical staff on the GIS-EM Integration Committee. Historic exercise scenarios for integration prove to be a valuable tool for identifying integration opportunities. Assessment of recently completed integrations builds value by validating that each integration was completed successfully, and each effectively disseminates integration knowledge to personnel that will use it for EM.

66 Guidebook on Integrating GIS in Emergency Management at Airports Establish Workshop Parameters Time & Duration Location Method to Capture Information Method of Facilitation Determine Incident Actual Incident (recent) Actual Incident (historical) Hypothetical Incident Identify Participants Stakeholders engaged in the incident Stakeholders that should have been engaged but weren’t Stakeholders that maybe should have been engaged but weren’t Develop Incident Milestone Steps Major steps conducted during incident Determine steps where communication is required Determine steps where a stakeholder may engage Develop Questions What GIS Data/Information was used What GIS Data/Information was available What GIS Data/Information would be beneficial Prepare Matrix Questions (rows) Milestone steps (columns) Conduct Workshop Examine each milestone step Respond to questions Capture responses Collaboration / Integration Workshop – Planning and Preparation Process Instructions: Complete the GIS-EM Collaboration / Integration Workshop Tool (Tool 5-1), as provided in Appendix M-A11, and insert here! 3.4 Develop Functional Requirements A GIS-EM Integration workshop and its associated tools will identify specific integration needs. Using the Integration Functional Requirements tool will help define integration needs. A functional requirements document outlines the requirements of a GIS-EM integration from a business need perspective without discussing the technical detail of how the integration will be completed. Understanding the integration need, features, stakeholders, data requirements, and nonfunctional requirements allows the GIS-EM committee to understand the overall needs and benefits of specific integration tasks without costing or building. Nonfunctional requirements section of the functional requirements allows for general requirements like usability, performance and system limitations. Instructions: Complete the Integration Functional Requirements Tool (Tool 5-3), as provided in Appendix M-A12, and insert here!

Launch 67 The GIS-EM Committee will have to understand and maintain a very detailed picture of the GIS- EM environment. This understanding is needed to identify and design integrations that will benefit the airport EM. Multiple tools are used to fulfill this objective. 3.5 Hardware/Software/Network Resources Tracking limitations and vulnerability will allow the GIS-EM committee to make informed decisions with a complete picture of the technology available. Instructions: Complete the Hardware/Software/Network Resources Tool (Tool 5-4), as provided in Appendix M-A13, and insert here! 3.6 Data Model It is important to quickly assess what data is available and what is planned to be added. The data tracked for each layer should quickly give a picture of the data that is part of GIS-EM. Segments of the data model include access, security, sharing, accuracy, and maintenance. Future data layers are also captured. Instructions: Complete the Data Model Tool (Tool 5-5), as provided in Appendix M-A14, and insert here! 3.7 GIS-EM Integration Requirements The GIS-EM integration requirements will define the expected needs from integration. Formulating these requirements assists in the application of the committee’s vision for GIS-EM integration by demonstrating how functional and nonfuntional requirements can be implemented to support GIS-EM integration. It is important to note that while some application development will be controlled by the airport, some components will be determined by emergency management agencies. Instructions: Complete the Application Development Tool (Tool 5-6), and store with other planned integrations in Appendix M-C.

68 Guidebook on Integrating GIS in Emergency Management at Airports CHAPTER 4 – DEVELOP AND IMPLEMENT This section will be determined by the specific GIS output developed from the integrated system. As this information is developed, this section can be populated.

Progress and Enhance 69 CHAPTER 5 – PROGRESS AND ENHANCE The GIS-EM Integration Plan should be updated periodically with improved practices, procedures, and coordinated response. In order for this to happen, the GIS-EM Integration Committee should host GIS-EM integration workshops and training at least annually. The following sections document the progression of GIS-EM integration for (AIRPORT NAME). 5.1 GIS-EM Collaboration / Integration Workshops Periodic collaboration / integration workshops are held at (AIRPORT NAME) providing a common format and venue for ongoing reviews and GIS confirmation/updates. (AIRPORT NAME) will determine the frequency and specific agenda for these meetings, as appropriate. Complete the GIS-EM Collaboration / Integration Workshop Tool (Tool 5-1) as needed. The workshop table describes (AIRPORT NAME’s) plans for holding these workshops. Appendix M-B contains copies of previous workshop summaries that can be referenced. 5.2 Accomplishments The GIS-EM Integration Committee tracks completed integrations in Appendix M-C of this plan. Functional requirements, application design, and integration assessments are all stored in chronological order in this appendix. 5.3 Continuous Improvement In order to ensure that GIS is continually improved, it is important to review certain items on a regular basis. The following checklist should be consulted as needed to assess these areas. Instructions: Complete the Continuous Improvement Checklist (Tool 7-1), as provided in Appendix M- A16, and insert here!

70 Guidebook on Integrating GIS in Emergency Management at Airports APPENDICES Appendix M-A – Complete Tool Set Appendix M-B – Status of Plan Details Appendix M-C – Planned Integrations Appendix M-D – Accomplishments Appendix M-E – Reference Documents

Appendices 71 APPENDIX M-A – COMPLETE TOOL SET Appendix Tool # Tool Title M-A1 3-2a Vision Tool Step 1: Leadership / Stakeholder List M-A2 3-2b Vision Tool Step 2: Vision Statement Development Guide M-A3 3-2c Vision Tool Step 3: GIS-EM Integration Committee List M-A4 3-1 Airport Emergency Event Assessment Tool M-A5 4-1 GIS Availability and Accessibility Tool M-A6 4-2 Emergency Management Environment Tool M-A7 4-3 GIS-EM Integration Tool M-A8 4-4 GIS-EM Skills Integration Tool M-A9 4-5 Resources Cost Considerations and Budget Tool M-A10 5-2 Assessment / Auditing Tool M-A11 5-1 GIS-EM Collaboration / Integration Workshop Tool M-A12 5-3 Integration Functional Requirements Tool M-A13 5-4 Hardware/Software/Network Resources Tool M-A14 5-5 Data Model Tool M-A15 5-6 Application Development Tool M-A16 7-1 Continuous Improvement Checklist

72 Guidebook on Integrating GIS in Emergency Management at Airports APPENDIX M-A1 LEADERSHIP STAKEHOLDER LIST Organization Contact Name Possible stakeholders you might consider: Aircraft Rescue and Fire Fighting (on-airport only) Law Enforcement (on/off airport) Fire (on/off airport) Emergency Medical Services, which may or may not be a part of Fire (on/off airport) Emergency Management Agencies (on/off airport) FAA National Transportation Safety Board (NTSB) Transportation Security Administration (TSA) Immigration and Customs / Customs and Border Protection (ICE/CBP) Federal Bureau of Investigation (FBI) Centers for Disease Control and Prevention (CDC) Airlines City/county/state agencies Red Cross Salvation Army Air Marshals Air National Guard Coast Guard Harbor Patrol

Appendices 73 APPENDIX M-A2 VISION STATEMENT DEVELOPMENT GUIDE In making a statement about GIS-EM Integration, please complete the following sentences: 1) Our goal is to be __________________________________________________________________________________ __________________________________________________________________________________ ___________________________________________________________________. 2) We will do this by leveraging __________________________________________________________________________________ __________________________________________________________________________________ ___________________________________________________________________. 3) And we will ensure that we anticipate __________________________________________________________________________________ __________________________________________________________________________________ ___________________________________________________________________. 4) And we will invest in __________________________________________________________________________________ __________________________________________________________________________________ ___________________________________________________________________. 5) And we will be known for __________________________________________________________________________________ __________________________________________________________________________________ ___________________________________________________________________. 6) And we will work with unyielding __________________________________________________________________________________ __________________________________________________________________________________ ___________________________________________________________________.

74 Guidebook on Integrating GIS in Emergency Management at Airports APPENDIX M-A3 GIS-EM INTEGRATION COMMITTEE LIST [Please modify this table as appropriate for your needs, and add additional rows as necessary] Organization Contact Name & Phone # Alternate Contact Committee Chairperson Airport Operations Leaders Airport Emergency Operations Leaders Airport Emergency Responder Leaders (ARFF) Airport Executive Leadership Airport Public Safety & Security Leaders (Airport Police/Security) Law Enforcement (Local Sheriff/Police) Fire/EMS (Local Fire Department) Emergency Management Agencies FAA National Transportation Safety Board Transportation Security Administration Immigration and Customs / Customs and Border Protection (ICE/CBP) Federal Bureau of Investigation Centers for Disease Control Airlines City / County / State Agencies [Others – such as Salvation Army, Air Marshals, Air National Guard, U.S. Coast Guard, Harbor Patrol, etc.] Note: Contact details shown are for the representative’s organization office. Contact details for the Committee and points of contact for agencies during an emergency event should be listed in the appendix of the Model GIS / Emergency Management Plan.

Appendices 75 APPENDIX M-A4 AIRPORT EMERGENCY EVENT ASSESSMENT TOOL Scenario: Event Size: Small Intermediate Extensive Event Type: Historic Event Simulated Event GIS EM 1. Mitigation/Planning Phase (Before an event) Has this type of event been previously identified? Are historic events like this documented? What considerations about potential regulations need to be addressed? What tools and technology will be used? 2. Preparedness Phase (Before an event) How well have plans been formulated to address these events? Assess and report on how you meet or need to comply with current regulations related to these events. What considerations about potential regulations need to be addressed? 3. Response Phase (During an event): What was handled well? How could response have been improved? Could GIS have helped in the response effort? 4. Recovery Phase (After an event): Were any best practices identified? What lessons were learned? What action items have been identified and assigned?

76 Guidebook on Integrating GIS in Emergency Management at Airports APPENDIX M-A5 GIS AVAILABILITY AND ACCESSIBILITY TOOL Assessment Question Response/Notes Identification: Name of the department, agency, or entity with GIS Is this GIS airport-owned? Purpose/main use of the GIS Capabilities What do the existing GIS environments provide? What organizations and/or departments use this GIS? Do organizations share GIS? If so, how is this accomplished? Do you have an MOU or Principles for Operating? Are there regular meetings for sharing? Upcoming Development Are there forthcoming enhancements outside of EM? Data Availability What data exists? What additional data needs to be collected and who can do this? What processes exist for engaging the GIS (access, data sharing, data maintenance)?

Appendices 77 APPENDIX M-A6 EMERGENCY MANAGEMENT ENVIRONMENT TOOL Notes: 1) Create a narrative overview of the emergency management environment at your airport. 2) Bullet list of equipment and missions to ease readability.

78 Guidebook on Integrating GIS in Emergency Management at Airports APPENDIX M-A7 GIS-EM INTEGRATION TOOL GIS-EM Equipment Quantity Purpose GIS-EM Integrations Purpose NOTE: Compile a list of existing GIS-EM equipment and integrations and their purpose. Reference the GIS Availability and Accessibility Tool (Appendix M-A5) to review various GIS available for GIS-EM integration.

Appendices 79 APPENDIX M-A8 GIS-EM SKILLS INTEGRATION TOOL Name Agency Department Role GIS-EM Skill 1 GIS-EM Skill 2 Notes: 1. Individual GIS-EM skills columns need to be created for your airport. Potential GIS-EM skills include Desktop GIS editor, EOC GIS user, Fire MDT command user. People from multiple agencies that perform and support EM for the airport should all be listed as resources. 2. Further customize the Skills Availability tool as needed. Other columns to consider include employment status, contract end date for contract employees, 24-hour availability, and on-call status. 3. Additional Skills: Please check and list special skills or resources you feel would be an asset in an emergency situation.

80 Guidebook on Integrating GIS in Emergency Management at Airports APPPENDIX M-A9 RESOURCES COST CONSIDERATION and BUDGET TOOL Cost Item Agency One Time Cost Recurring Cost Recur Freq Item Detail Hardware Software Staff Services Note that ancillary benefits will likely result from GIS-EM spending (e.g., the Public Information Officer creates and shares maps with system). GIS-EM will also likely have zero-cost items that should be noted (e.g., the municipality that owns the airport maintains an enterprise GIS license that allows GIS-EM users at no cost).

Appendices 81 APPENDIX M-A10 ASSESSMENT / AUDIT TOOL Consideration Audit DEFINE What was the purpose of the integration? BENEFITS List benefits of integration. DEPENDENCIES List dependencies of integration. COST What direct costs were incurred for integration? Is there added maintenance cost or administrative time because of this integration? MAINTENANCE What will be the required level of existing staff commitment during the data preparation and GIS construction process? How long is this expected to remain active, is there a retirement date for this integration? STAFF Who will use this integration? Who administers this application? HARDWARE/SOFTWARE/NETWORK How is the integration accessed? EVALUATION Consideration Assessment BENEFITS Was the integration written as specified? Does this make a portion of EM more efficient? COST Does more need to be done to make this function as needed? MAINTENANCE Is data current? STAFF Is additional training needed? Is additional staff time needed to operate? HARDWARE/SOFTWARE/NETWORK Will this integration tax the existing technology infrastructure?

82 Guidebook on Integrating GIS in Emergency Management at Airports APPENDIX M-A11 GIS-EM COORDINATION / INTEGRATION WORKSHOP TOOL Please modify this table as appropriate for your needs, and add additional rows as necessary. Date Workshop Name Description

Appendices 83 APPENDIX M-A12 INTEGRATION FUNCTIONAL REQUIREMENTS TOOL GIS-EM Integration Overview Describe the integration Data Needs GIS-EM Data ID # Data Name Description Data Type User Need Note: Pull GIS-EM Data ID #, Data Name, Description, and Data Type from the GIS-EM Data Model [CONTINUATION OF TOOL ON NEXT PAGE]

84 Guidebook on Integrating GIS in Emergency Management at Airports Functional Requirements Required Feature Description Data Requirement Stakeholder Responsibility Note: Functional requirements are user-specified functions, tasks, or behaviors that the proposed system must support to meet the business need. A general description of the requirement is needed, along with the data requirements and any specific responsibilities. In addition to the user-specified functions, include system functions that are required by the integration to access and retrieve data in other systems. Nonfunctional Requirements Required Feature Category Description Priority Usability Reliability Performance Supportability Note: Nonfunctional requirements describe the “attributes of the application” or “attributes of the application environment.” They do not describe the behavior of the application (functional requirements). Priority should be listed as current or future; future is included so the design can factor known changes coming at the airport. There are several types of nonfunctional requirements: usability, reliability, supportability, and performance, which are described below. Usability: Requirements that describe the ease with which the system can be learned and operated by the intended user. Reliability: These requirements describe the degree to which the system must behave in a user-acceptable fashion. Supportability: These requirements are related to the ability of the application to be easily modified to accommodate enhancements and repairs, including coding standards, maintenance access and maintenance utilities. Performance: Requirements related to performance include such items as user load factors, bandwidth or communication capacity, throughput, accuracy, reliability and response times under a variety of loading conditions.

Appendices 85 APPENDIX M-A13 HARDWARE/SOFTWARE/NETWORK RESOURCES TOOL Network Speed Limitations Status Vulnerability Hardware Location/Number Limitations Status Vulnerability Software Seats Target Users Status Vulnerability

86 Guidebook on Integrating GIS in Emergency Management at Airports APPENDIX M-A14 DATA MODEL TOOL Tool Segment: Data Model-Considerations GIS-EM Data ID # Data Name Description Data Source Update Frequency Update Responsibility Tool Segment: Data Model-Access GIS-EM Data ID # Data Name Airport Ops User Police User Fire User City/County Agency User Tool Segment: Data Model-Security GIS-EM Data ID # Exceptions Security Options Airport Ops User Police User Fire User City/County Agency User

Appendices 87 DATA MODEL TOOL (continued) Tool Segment: Data Model-Sharing GIS-EM Data ID # Data Name Sharing Organizations Sharing Method Sharing Frequency Tool Segment: Data Model-Accuracy GIS-EM Data ID # Data Source Information (Collection method, date collected etc.) Data Confirmation (QA/QC review) Metadata Status Tool Segment: Data Model-Maintenance GIS-EM Data ID # Update Frequency Update Responsibility Updated by Airport Data Maintenance Flow Chart Exists and Followed

88 Guidebook on Integrating GIS in Emergency Management at Airports APPENDIX M-A15 APPLICATION DEVELOPMENT TOOL Consideration Description Notes Stakeholder Responsibility GENERAL Cost Budget for personnel and equipment needed to capture functional and nonfunctional requirements as well as hardware and software components. Components for the solution. Software component may be either: application development or third-party solution, or even a combination of both. Time to Deploy Timing involves several phases including data collection, software identification, application development, testing, and implementation. Inputs What data is required to meet the needs of the system application. Outputs What tools, maps and interfaces are needed by users. SYSTEM SPECIFICATIONS Database How and where data is stored in tabular or spatial format. Technology What hardware (i.e., server, client, printers, plotters) and software (i.e., GIS, document management, reporting, source control) components are needed. Security How user access is determined (i.e., ID requirements). INTEGRATION ARCHITECTURE Presentation How users will gain access to the application (i.e., Internet portal) Application How users will be able to manipulate data to view and modify outputs. Integration Methods How users will be able to integrate data from different databases and integrate various applications, including behaviors, concepts, objects or logic common to many applications that are designed to be re-used.

Appendices 89 APPENDIX M-A16 CONTINUOUS IMPROVEMENT CHECKLIST Develop auditing system that establishes certain goals to be reached and measures extent the goals have or have not been met. These goals should include: o Monetary goals o Systems output targets Conduct systems review on a regular basis. Conduct debriefing sessions after each emergency to assess GIS performance. Conduct tabletop training exercises on a regular basis and when significant changes to GIS occur. Maintenance o Planning and monitoring of systems and hardware (balancing new technology – hardware/software version changes with stability). Provide constructive feedback to the GIS/EMS Committee. Expand GIS-EM Integration as appropriate.

90 Guidebook on Integrating GIS in Emergency Management at Airports APPENDIX M-B – STATUS OF PLAN DETAILS The following table serves as a working summary of the actions within the current version of the (AIRPORT NAME) GIS-EM Integration Plan. It is intended that each item in the table be reviewed periodically for status and outlook by the GIS-EM Committee. Topic Last Update Expected Update Leadership / Stakeholder List Vision Statement Development Guide GIS-EM Integration Committee List Airport Emergency Event Assessment Tool GIS Availability and Accessibility Tool Emergency Management Environment Tool GIS-EM Integration Tool GIS-EM Skills Integration Tool Resources Cost Considerations and Budget Tool Assessment/Auditing Tool GIS-EM Collaboration / Integration Workshop Tool Integration Functional Requirements Tool Hardware/Software/Network Resources Tool Data Model Tool Application Development Tool Continuous Improvement Checklist

Appendices 91 APPENDIX M-C – PLANNED INTEGRATIONS The following pages document planned integrations that have been identified by the GIS-EM Integration Committee.

92 Guidebook on Integrating GIS in Emergency Management at Airports APPENDIX M-D – ACCOMPLISHMENTS The following pages document specific integrations that have been accomplished by the GIS-EM Integration Committee.

Appendices 93 APPENDIX M-E – REFERENCE DOCUMENTS Reference documents that should be included in this appendix include: Copies of procedures put in place with all GIS-EM organizations, such as: o ARFF o Law Enforcement o Fire Protection o City / County Emergency Organizations o Other Mutual Aid Agencies Copies of tools for repeated use o Local Emergency Response History o Assessment/Audit o Integration Functional Requirements o Application Development Requirements Copies of previous training exercises Copies of previous debriefing activities Copies of previous lessons learned