Download - Systems Integration, Transition and Training Playbookfaculty.nps.edu/scrunyon/DHS/Monterey_Earthquake...Systems Integration, Transition, and Training Playbook # RSC-10 iii Executive

Transcript
Page 1: Systems Integration, Transition and Training Playbookfaculty.nps.edu/scrunyon/DHS/Monterey_Earthquake...Systems Integration, Transition, and Training Playbook # RSC-10 iii Executive

Systems Integration, Transition, and Training Playbook # RSC-10

i

Naval Postgraduate School Earthquake Response Project

Playbook #: RSC-10

Revised – 10/15/2013

Approved for public release; distribution is unlimited

Systems Integration, Transition and Training Playbook

Page 2: Systems Integration, Transition and Training Playbookfaculty.nps.edu/scrunyon/DHS/Monterey_Earthquake...Systems Integration, Transition, and Training Playbook # RSC-10 iii Executive

Systems Integration, Transition, and Training Playbook # RSC-10

ii

Playbook Table of Contents

Executive Summary……………….……………………………………… iii Overview……………….…………………………………………………… 1 Purpose/Objectives……………….……………………………………… 1 Hardware Required……………….………………………………………. 1 Data Provided……………….……………………………………….......... 2 Software Environment……………………………………………………. 2 NPS Earthquake Response Products…………………………………. 5 EOCIB Overview………….……………………………………………….. 8 HFN Communications……………………………………………………. 10 Systems Integration………………………………………………………. 11 Transition and Training…………………………………………………... 12 References……….…………………………………………………………. 14 Appendix A: EOCIB Instructions……………………………………….. 15

Page 3: Systems Integration, Transition and Training Playbookfaculty.nps.edu/scrunyon/DHS/Monterey_Earthquake...Systems Integration, Transition, and Training Playbook # RSC-10 iii Executive

Systems Integration, Transition, and Training Playbook # RSC-10

iii

Executive Summary This is the last in a series of “Playbooks” designed to assist first responders and emergency managers with the use of remote sensing data for improved earthquake response. This Playbook describes integration, transition and training implemented for a project funded by the Department of Homeland Security and conducted by the Naval Postgraduate School (NPS) Remote Sensing Center (RSC) to explore remote sensing imagery and other geographic information in support of earthquake response. It outlines the other playbooks, provides additional information about the hardware and software required, and discusses how all of the products can be integrated in to a framework for improving earthquake response using remote sensing and other geoinformation. This Playbook describes integration of RSC remote sensing products with several other existing NPS projects’ capabilities. It describes the RSC-developed products, their implementation, and combination of these with server and communications technology to provide a stand-alone emergency operations center (EOC). The prototype “EOC-in-a-Box” (EOCIB) implementation developed in a separate project by the NPS Cloud Computing Center and delivered separately to Monterey County is summarized. Independently Powered Command/Control/Communications System (IPC3) developed separately by the NPS Hastily Formed Networks Center (HFN), which provides support to the EOCIB is also described. Together, these aspects form the model for the overall integrated earthquake response project, including all of the required hardware, software, data, and communications to demonstrate the role that remote sensing and other geographic data can play in an austere field environment following an earthquake. The integrated model provides the framework for utilization of remote sensing data to assist with emergency response. The Playbook Directory near the end of this document shows the NPS Earthquake Response Playbook sequence to help put this Playbook into perspective and give an overview of products resulting from this research and some aspects of practical implementation. The content of each Playbook is briefly described; however, users are referred to the specific named and numbered Playbooks for full product descriptions. These provide additional detailed product information, instructions on how to separately utilize the individual products, and how to combine them into an integrated system for improved earthquake response.

Page 4: Systems Integration, Transition and Training Playbookfaculty.nps.edu/scrunyon/DHS/Monterey_Earthquake...Systems Integration, Transition, and Training Playbook # RSC-10 iii Executive

Systems Integration, Transition, and Training Playbook # RSC-10

1

Overview Sponsored by the Department of Homeland Security (DHS) Science & Technology Directorate, the Remote Sensing Center (RSC) at the Naval Postgraduate School (NPS) has developed a series of instructional playbooks designed to assist first responders and emergency managers with the use of remote sensing technology for improving earthquake response.

This playbook (Playbook #RSC-10) describes integration of all aspects of the project into a unified model for the use of remote sensing datasets and derived products as a valuable source of geographic information in support of emergency planning, change detection, and post-disaster event assessment, response, and management. The Playbook outlines the products developed, how they relate to each other, and the hardware, software, and communications environment required for stand-alone implementation of an Emergency Operations Center utilizing these capabilities.

Purpose/Objectives

The objective and purpose of this playbook is to provide details about the integrated EOC model implemented with remote sensing and other geographic data specific to Monterey County and City. This Playbook can be used to guide emergency operations using remote sensing data and products, server hardware, software, and communications support.

Hardware Required

Remote sensing data and supporting information specific to Monterey County and City are provided on an external USB disk drive compatible with MS-Windows (XP, VISTA, Windows-7) operating systems. Users should be able to plug this device directly into an USB port, have the drive recognized by the system, and be able to see the directory structure for data, products, and project information. Data can then be used directly on the drive, or copied to another EOC resource. They can also be supplemented by existing imagery and geographic information developed by the EOC. Hardware described in this playbook also includes the “EOC-in-a-Box” (EOCIB), a stand-alone emergency operations center developed and implemented by the NPS Cloud Computing Center that can act as the host for all of the software, data, applications, and products required to operate an emergency operations center utilizing remote sensing data in an austere operating environment. The first EOCIB hardware solution integrated with the data and software described in this Playbook has been delivered to Monterey County, CA. This playbook also describes an implementation of communications hardware and software developed by the NPS Hastily Formed Networks Group as a separate project in support of the EOCIB and other emergency response requirements and tested in conjunction with the EOCIB in an operational environment. In addition, one or more mobile Android devices are required for implementation of the mobile damage assessment capabilities designed for this project by NPS and described in Playbook#RSC-06.

Page 5: Systems Integration, Transition and Training Playbookfaculty.nps.edu/scrunyon/DHS/Monterey_Earthquake...Systems Integration, Transition, and Training Playbook # RSC-10 iii Executive

Systems Integration, Transition, and Training Playbook # RSC-10

2

Data Provided The USB drive described above is preloaded with a selection of baseline imagery and data to allow EOC personnel to train for and perform geospatial analysis in support of earthquake response and other disaster situations. The drive also contains digital copies of the Playbook Series, which includes operational instructions to perform these analyses. Sample analyses products are available to use as templates and guidelines for independent product generation. A stand-alone webpage is also provided, allowing easy access to the materials on the drive and summarizing additional information about the project and its implementation for Monterey County and the City of Monterey, CA. The folder structure of the data drive is shown in Figure 1 (see Playbook#RSC-02 for additional details).

Figure 1. NPS Earthquake Response Project data directory structure

These data have also been installed utilizing this directory structure on the EOCIB provided to Monterey County. Each user (operating a unique Windows 7 virtual machine) on the EOCIB has access to the data and Playbooks under a read-only data drive that can be accessed through “My Computer” on Windows. Combined, the USB data drive and the EOCIB mirror data provide the capabilities to train and implement solutions in the existing EOC, then, when the need arises, to move directly over to the EOCIB to utilize the same data and software environment for product generation under emergency response conditions.

Software Environment Specific software is required at each EOC implementing the NPS Remote Sensing Earthquake Response approach in order to take advantage of the remote sensing data and products provided. Note that the use of specific software or brand names in this Playbook and other Playbooks does not imply endorsement of specific products by the Naval Postgraduate School or the US Government. The following describes the basic software required to implement this approach. This software environment should be established at the native EOC and integrated into the CONOPS for emergency response. Specific implementations and other (incidental) software that may be needed for specific applications are described in the individual Playbooks. The software, data, and Playbooks can be used to train for and to guide response activities using remote sensing and other geographic data at the EOC. Additionally, having these software located on the EOCIB in addition to the native EOC provides the added advantage of seamless operation in the event that the EOCIB becomes the primary EOC. The EOCIB provides the ability to run these applications outside the EOC at either a disaster location or at an interim EOC location in the event the EOC has become critically damaged. This section provides an overview of the required software and applications.

Page 6: Systems Integration, Transition and Training Playbookfaculty.nps.edu/scrunyon/DHS/Monterey_Earthquake...Systems Integration, Transition, and Training Playbook # RSC-10 iii Executive

Systems Integration, Transition, and Training Playbook # RSC-10

3

ArcGIS Because of commonality between most emergency response organizations (and specifically Monterey County and the City of Monterey, CA) the NPS Earthquake Response project standardized all geospatial data viewing and analyses for this project using a software system, “ArcGIS”. ArcGIS is geographic information system (GIS) software package that is designed to allow users to create maps, as well as analyze and organize geospatial data (through databases). The system also provides a framework for sharing of maps and geographic information across an organization or government entity, as well as openly on the internet. ArcGIS, developed by ESRI, is the most popular GIS software package available today and is commonly used in most EOCs in California and around the US. It consists of several independently-run modules and their associated extensions. The most commonly installed modules are ArcMap and ArcCatalog, and these are required for use of the NPS Earthquake Response capabilities. Standardizing on ArcGIS for the NPS Earthquake Response Project will allow emergency response personnel to continue to work in a familiar environment and promotes extensions of capabilities in accordance with approaches described in the NPS Playbook series. Additional processing and analysis can be achieved using any image processing or GIS software. In the context of the NPS Earthquake Response Project, ArcMap is used to create and display spatial (map) and tabular (database) GIS data to generate information-yielding selections and queries, to perform spatial analyses, and to produce map and data output products. Within the map display, features can be viewed in greater or lesser detail using common zooming and panning utilities. Features on the display can be symbolized using colors, shades, and custom symbols to help identify what each feature represents. Information in the underlying database is displayed as tables similar to how Microsoft Excel or Access data are displayed. Both ArcMap and ArcCatalog, implemented as part of an ArcGIS 10.0 (or more recent version) are required software for the EOC in order to implement the approaches described in the NPS Playbooks. Two popular extensions for ArcMap: the Spatial Analyst and the Geostatistical Analyst are optional, but would also be useful. ArcCatalog is an important tool for constructing, entering, and managing sources of GIS data used within ArcMap. ArcCatalog also expedites input and viewing of metadata (i.e., source and historical information about the data files). Licenses are required to run the ArcGIS applications, and if not already installed in an EOC can be obtained (for a fee) from ESRI. For more information on ArcGIS, please go to http://www.esri.com/software/arcgis. To see how ArcGIS can be used effectively for earthquake response, consult Playbooks#RSC-02, 03, 04, 07, and 08. Web Browser(s) A standard web browser such as Internet ExploreR, Firefox, or others is required to access some materials provided by the NPS Earthquake Response Project. These can be downloaded from the internet as needed. Google Earth Google Earth is required to view the various KML/KMZ files associated with critical infrastructure. To download and activate the Google Earth application, navigate a web

Page 7: Systems Integration, Transition and Training Playbookfaculty.nps.edu/scrunyon/DHS/Monterey_Earthquake...Systems Integration, Transition, and Training Playbook # RSC-10 iii Executive

Systems Integration, Transition, and Training Playbook # RSC-10

4

browser to http://www.google.com/earth/index.html and follow the instructions for a PC installation. Microsoft Excel Excel (or equivalent spreadsheet software) is required to view some NPS Earthquake Response Project data (critical infrastructure database). Lighthouse Application The NPS damage assessment mobile application product is based on the NPS Common Operational Research Environment (CORE) Lab mobile application “Lighthouse”. This is available online at http://lhproject.info/install-odk/ as an Android application and provides the ability to collect field data using mobile devices into forms that are customizable to meet the needs of any emergency management agency. An implementation for Monterey County and the City of Monterey is are described in Playbook#RSC-06. Ushahidi Ushahidi is an open-source, customizable news and social-media messaging aggregation tool that can collect crowd-sourced geospatial and social-media information and map that information in real time. An Ushahidi deployment functions as a crowd-sourced, crisis mapping service by aggregating geospatial and social-media information. Use of Usihidi for the NPS Earthquake Response Project required some customization. Additional information is provided in Playbook#RSC-05A. A functional instance of the Ushahidi platform has been customized and installed on the Monterey County, CA, EOCIB. Access to the front-end of the Ushahidi deployment is done completely through a web browser. For more information including directions on the proper use of the Earthquake Response Project instance of Ushahidi, please see Playbook #5A. UICDS The Unified Incident Command Decision Support System (UICDS) is a DHS-sponsored software program designed to create a “middleware” type interface that joins together applications in order to share common information and offer communication between these ‘silos’ of technology. UICDS provides the overarching connectivity that brings together all compliant applications and delivers to end users, through their individual applications, information to the right people at the right time. Emergency management personnel involved become better informed about the disaster situation and are then able to make improved critical decisions. For the purpose of this project, field data were collected using the Lighthouse-ODK Android application (see Playbook#RSC-06) and uploaded to UICDS. These reports were converted to a UICDS-friendly file format and uploaded via a pair of Java-based communication programs provide by the Science Applications International Corporation (SAIC) under contract with DHS. UICDS can talk to WebEOC (see below) by using another Java-based communication program (a WebEOC Adapter) that has also been provided by SAIC. For additional information, including directions on the proper use of this specific implementation of UICDS, see Playbook#RSC-09.

Page 8: Systems Integration, Transition and Training Playbookfaculty.nps.edu/scrunyon/DHS/Monterey_Earthquake...Systems Integration, Transition, and Training Playbook # RSC-10 iii Executive

Systems Integration, Transition, and Training Playbook # RSC-10

5

WebEOC WebEOC is a commercially developed web application designed to offer a Common Operating Picture (COP) environment for local, state, and federal agencies to help communicate and manage a disaster event effectively. Authorized users in the emergency management and first responder community can enter and view incident information from any location. WebEOC “enables users to manage multiple incidents and daily events, assign and track missions and tasks, provide situation reports, manage resources, and prepare Incident Command System (ICS) and Incident Action Plan (IAP) reports”. (www.esi911.com). Monterey County Office of Emergency Services has their own instance of WebEOC running on the cloud services provided by ESI. For additional information, including directions on the use of the WebEOC interface, see Playbook#RSC-09. Sensor Island Developed by the Naval Postgraduate School’s Center for Asymmetric Warfare (CAW) and Peak Spatial Enterprises (Peak Spatial), Sensor Island offers a robust, trusted technology infrastructure that allow sensors, sensor platforms, and sensor users to communicate effectively. Sensor Island has the ability to provide organizations using a wide variety of geospatial output to collect, combine, share, and disseminate critical information in formats that support geospatial “common operational pictures” (COPs) and data formats. Sensor Island has simple software requirements. Access to the Sensor Island COP is accomplished via web browser and to the Sensor Island geographic web services via a geographic mapping software package such as ESRI ArcGIS or Google Earth (see above). To upload data/files to the Sensor Island backend, a file transfer application is required. BitKinex, a freeware utility program has been tested for use with Sensor Island and is described in Playbook#RSC-09. Once installed and properly configured, BitKinex provides the secure Dropbox client that gives users the ability to upload geospatial and remote sensing products to Sensor Island (with internet connectivity). BitKinex is currently installed on the Monterey County EOC-in-a-Box and configured to communicate with the Sensor Island Dropbox. For more information including directions on the proper use of earthquake response instance of Sensor Island, see Playbook#RSC-09.

NPS Earthquake Response Products The results and information derived during the NPS Earthquake Response pilot project are detailed in a series of ten (10) Playbooks (including this one) describing the individual products and how to use them. The Playbook Directory below shows the NPS Earthquake Response Playbook sequence. A short description of each Playbook follows the list.

Playbook#RSC-01: NPS-DHS Remote Sensing Project/Products Overview

Playbook#RSC-02: Monterey County Baseline Products and Pre-Event Data

Processing

Playbook#RSC-03: Monterey (City) Infrastructure Products

Page 9: Systems Integration, Transition and Training Playbookfaculty.nps.edu/scrunyon/DHS/Monterey_Earthquake...Systems Integration, Transition, and Training Playbook # RSC-10 iii Executive

Systems Integration, Transition, and Training Playbook # RSC-10

6

Playbook#RSC-04A: Airborne Imagery Change Detection Products (SDSU)

Playbook#RSC-04B: NOAA Night Lights/Power Change Detection and Fire

Detection Products

Playbook#RSC-05A: Social Networking Products (Ushahidi)

Playbook#RSC-05B: Social Networking Products (Twitter)

Playbook#RSC-06: Mobile Application Damage Assessment Product

Playbook#RSC-07: Post Event Processing Scenarios Products

Playbook#RSC-08: Soft and Hardcopy Output Products and Distribution

Playbook#RSC-09: Common Operating Picture (COP) Products

Playbook#RSC-10: Systems Integration, Transition, and Training

The content of each Playbook is also briefly described below; however, users are referred to the specific named and numbered Playbooks for full product descriptions. These provide additional detailed product information and instructions on how to utilize the individual products. Playbook#RSC-01 summarizes the NPS/DHS Remote Sensing Response project and its scope and provides the big picture for the other Playbooks. It outlines the organization of the project, the NPS and external participants, and the coordinated approach forming the model for the overall integrated earthquake response project. Playbook#RSC-02 details baseline remote sensing data and supporting information compiled for the pilot project. These include commercial satellite imagery, National Agricultural Imagery Program (NAIP) aerial photography data, USGS Orthoquad Mosaics, GIS datasets created by local GIS professionals, LiDAR data, and high resolution aerial photography. These databases form a “base layer” of information necessary for preplanning and then later performing change detection based on the acquisition of new data during or after an earthquake or other disaster event. Playbook#RSC-03 forms the basis for evaluation of critical infrastructure and key resources (CIKR). Infrastructure information compiled for and by the City of Monterey, CA is used for illustration. The original data provided by the City of Monterey was in a text report format. NPS compiled this information and supplemented it using site visits to compile location information, photographs, and additional details. The full CIKR information package was then used to construct an interactive directory of CIKR sites with hyperlinked datasheets providing easy access to site characteristics, overhead high-resolution imagery, and street-level views of current configuration and conditions. Pictures of the critical infrastructure were obtained by ground and aerial survey. This information forms the basis for pre-event status to be compared to similar post-event information for rapid damage assessment. Playbook#RSC-04 details fire and power outage detection capabilities and data distribution means for information derived by the National Oceanic and Atmospheric Administration (NOAA) that help with determination of what areas are affected by a disaster event. NOAA operates a satellite with the Visible Infrared Imaging Radiometer Suite (VIIRS). This system can easily detect and map out areas of night lights from

Page 10: Systems Integration, Transition and Training Playbookfaculty.nps.edu/scrunyon/DHS/Monterey_Earthquake...Systems Integration, Transition, and Training Playbook # RSC-10 iii Executive

Systems Integration, Transition, and Training Playbook # RSC-10

7

space. This collection builds a picture of the “normal” scene prior to the event which is then compared to the scene after the event. Power outages will show up as dark areas which are easily defined and reported. In addition the VIIRS has two daytime sensor bands that detect fires during the daytime pass and six bands that detect fires during the night time pass. This Playbook provides specific information about how to access the imagery and reports for Monterey California. Playbook#RSC-05 describes the attributes and use of Ushahidi and other social media applications, including Twitter, Facebook, email and SMS text messaging. Recent disasters have highlighted the importance of emerging capabilities like social media in provide rapid access to event information. The NPS project explored and demonstrated an instance of Ushahidi, an open-source, customizable news and social-media messaging aggregation tool that can collect crowd-sourced geospatial and social-media information and map that information in real time. Playbook#RSC-06 provides a more formal event assessment and reporting function using the NPS Common Operational Research Environment Lab (CORE Lab) “Lighthouse” Android application. Lighthouse provides the capability to digitally collect field data into customizable forms that can be transmitted via cell phone service (if available) or physically carried to the EOC and downloaded there for analysis. The application not only provides customized reports but can also incorporate supporting GPS tagged photos, video and audio as well. Playbook#RSC-07 provides scenarios and remote sensing procedures and products used for change detection. This substantiates the absolute need for pre-event data and imagery. Instructions and samples of specific products are provided as examples. While these could be used as templates for change detection in a disaster event, they are best used prior to occurrence for planning and development of products to be generated after a disaster occurs. The instructions provided are meant to be easy enough for most members of an EOC to understand, however, they would probably be best used by GIS professionals to construct CONOPS and procedures prior to a disaster event so that standard products could be produced in the highly stressful post-event situation. Most EOCs will be interested in three primary products derived from remotely sensed data. One class of products is digital elevation models (DEMs) and digital surface models (DSMs). Another is geometrically corrected aerial and satellite images. Finally, fused products that incorporate both DEMs and image data should be useful for visualization, situational awareness, and change detection for identification and characterization of damaged infrastructure. Playbook#RSC08 describes both softcopy (digital) and hardcopy (printed map) products in accordance with tiered deliver systems described in Playbook#RSC-01, and specifically recommends that EOCs use either Geospatial PDF or GeoPDF® formats for digital maps. Detailed instructions are provided for creating these products using ArcGIS software. Once created, GeoPDFs and Geospatial PDFs can be taken into disaster areas on mobile devices and be used to find and mark locations, and

Page 11: Systems Integration, Transition and Training Playbookfaculty.nps.edu/scrunyon/DHS/Monterey_Earthquake...Systems Integration, Transition, and Training Playbook # RSC-10 iii Executive

Systems Integration, Transition, and Training Playbook # RSC-10

8

measure distance, perimeter and area of damaged infrastructure. These can also be printed as hardcopy maps, which if cellular communications and the internet are not available, may be the only source available to pinpoint and report damage. Playbook#RSC-09 describes “Sensor Island”, a common operating picture (COP) used by the NPS Earthquake Response project to allow ingest of data from various remote sensing sources into the EOC for visualization and situational awareness. Sensor Island is a hardware and software system developed by the NPS Center for Asymmetric Warfare and Peak Spatial Enterprises that provides the capability to collect, combine, share and disseminate information from a wide range of sensors and incorporate that data into the COP as well as data formats that support external applications and users.

Emergency Operations Center In-A-Box (EOCIB) Overview

EOC in-a-box (EOCIB), which was developed as a component of the NPS/DHS/CHSC Independently Powered Command, Control, and Communications System of Systems and funded separately from the RSC NPS/DHS Earthquake Response Project, was used as a hardware solution by this project to integrate project software components, data, and products described above. EOCIB provides a portable hardware server platform and software-based Virtual Machines used to host baseline imagery and geographic information about Monterey County and City and the software environment for utilizing these data. The virtual machines as equipped for Monterey County, CA, are based on the Windows 7 operating system and are equipped with software applications as described above and in other Playbooks. The initial (prototype) EOC in a box has been delivered to the Monterey, CA, County Office of Emergency Services for use by 1st responders and emergency managers as part of the Emergency Operations Center resources. An additional system is under construction for the City of Monterey. This section describes the configuration, operation, and care of the EOC in a box and how it works with Remote Sensing applications and data sets. Full instructions for startup, operation, and shutdown of the EOCIB are provided in Appendix A. The EOC in a box is a complete data center in a mobile configuration. It is comprised of the following components:

An SKB brand hardened travel case with wheels and handles so two people can lift and move it with relative ease. The case has the highest shock absorption rating available and can withstand 100 airline trips.

A powerful server from V3 system. The server has solid state hard drives with over 1TB of internal storage, 144 GB of RAM, and a total of 12 CPU cores.

o VMware ESX 4.1 Hypervisor, optimized by V3 systems for virtual machine performance and managed by VMware’s Virtual Center and VIEW systems.

o Microsoft Windows Active Directory which provides user accounts, DNS, and other services which provides a traditional Windows Domain

Page 12: Systems Integration, Transition and Training Playbookfaculty.nps.edu/scrunyon/DHS/Monterey_Earthquake...Systems Integration, Transition, and Training Playbook # RSC-10 iii Executive

Systems Integration, Transition, and Training Playbook # RSC-10

9

o Microsoft Windows 7 virtual machines with Microsoft Office 2010, Symantec Anti-Virus, and several Remote Sensing applications and data sets outlined in other playbooks.

A Battery Backup system, which provided clean power as well as enough battery run-time to power off the system should land or alternative power fail or the system need to be relocated and remain running for a short period.

A 24 port Cisco Ethernet switch. The switch is fully managed, has Power over Ethernet (PoE) on all ports which can be used to power devices such as Wireless Access Points over a standard Ethernet category 5E cable, and supports the use of fiber optic cables with media converters to allow integration with an existing infrastructure.

A TrippLite keyboard/video/mouse (KVM) in a retractable tray provides the ability to manage the system locally by sliding the unit out of the case, raising the screen, and logging into the server. This capability is currently being updated to a USB device that works off of a laptop. An administrators laptop is being configured and will allow the operator to control the server via a USB connection that resembles an SSH connection. This was done to reduce weight by approximately 35 lbs and more closely align with a new EOC in a box currently being configured for the City of Monterey, CA.

A Raritan power distribution unit (PDU) controls how the power is turned on, and each outlet is staged to minimize the total load put on the system at startup. Each port also tracks power usage and is managed from a virtual machine. Data on power usage of each component, as well as aggregated totals is available and several report formats are available.

A Cisco Wireless Access Point (WAP) is included and acts as the interface to the Internet. Connections to a WAN, VSAT, or BGAN are made at the WAN port of the CISCO device and provides access to the Internet for all wired and wireless clients. The WAP also has the ability to do port forwarding so remote access to the EOC in a box via the Internet is possible. Simple DNS, NAT, and Firewall services are also provided and configured via a browser based interface.

A Coraid Etherdrive Storage Attached Network (SAN) with approximately 10 TB of storage is also included. This provides for the ability to store large data sets and make them available to the virtual machines. It also allows for the pre-loading of imagery data relevant to the applications and reduces the need for downloading data, often on expensive and constrained connections.

The EOCIB is designed to integrate with existing electrical power, and to use an existing Internet connection. Alternately, it can be used with the IPC3 alternative power system or a generator and can also use a BGAN or VSAT system such as the Monterey-County owned satellite trailers for Internet connectivity The EOC in a box and one of the two

Page 13: Systems Integration, Transition and Training Playbookfaculty.nps.edu/scrunyon/DHS/Monterey_Earthquake...Systems Integration, Transition, and Training Playbook # RSC-10 iii Executive

Systems Integration, Transition, and Training Playbook # RSC-10

10

VSAT trailers are stored at the Monterey County Office of Emergency Services in Salinas, CA. Access to the resources hosted on the EOC in a box can be by any personal computer, laptop computer, or iPad or Android tablet with a wireless card or Ethernet card. A software client can be downloaded from the EOC in a box server for laptop and desktop computers, and a client “app” for the tablet computers and smartphones is available at the Apple store and Google Play. This client is used to gain access to the Windows 7 virtual machines which run many of the Remote Sensing applications and have access to the data. For applications such as Ushahidi (Playbook#RSC-05) and Lighthouse (Playbook#RSC-06), a wireless connection via a device with a web browser is all that is needed.

HFN Communications The NPS Hastily Formed Networks Center (HFN) provides Independently Powered Command/Control/Communications System (IPC3) in support of the EOCIB. This technology, also funded separately from the RSC NPS/DHS Earthquake Response Project is designed to allow the EOCIB to operate independently of outside power and communications, which likely will be interrupted during a disaster. (See Figure below).

Figure: Example NPS/HFN Earthquake response communications and power setup

(Camp Roberts, August 2012)

Page 14: Systems Integration, Transition and Training Playbookfaculty.nps.edu/scrunyon/DHS/Monterey_Earthquake...Systems Integration, Transition, and Training Playbook # RSC-10 iii Executive

Systems Integration, Transition, and Training Playbook # RSC-10

11

During a recent exercise (NPS RELIEF 2012), a broadband WiFi cloud around an Incident site and/or Tactical Emergency Operations Center was established within 3 hours of commencement of these operations. This exercise at Camp Roberts, California during August 2012 demonstrated establishment of a total of 8 WiMAX bridges (Redline AN-80i) and 6 Meshed WiFi Access Points. A 3-hop link was used to establish communications between the TAC and the Incident Site. An independently powered (solar/wind) energy source was used to power most of the equipment at the incident site. The wireless networking technologies in-toto included MESHED WIFI/WIMAX/VSAT and BGAN for IP backbone access, an aircraft to relay communications and to provide surveillance, and solar/wind/fuel cell for primary or backup power. A 3/1 mbps VSAT terminal from Inmarsat was integrated into the exercise. On the other side of the network (at the TOC), a 12 mbps ViaSat VSAT terminal provided the network with a high speed Internet connection. A redundant Meshed WiFi network was overlaid on top of the WiMAX infrastructure using Persistent Systems Wave Relay (tm) meshed Access Points. These units were set up in "mesh" mode versus "bridge" mode for the redundancy. The network was provided with IP backbone access from both sides - the incident site and the tactical operations center (TOC). Alternate power systems (Yeti - solar only) and a SolarStik alternate power system (solar, wind, hydrogen fuel cell) were successfully used to run various network components. These systems performed perfectly and the included battery packs were keeping up with energy demands from all devices attached to them. These capabilities are indicative of those to be delivered to Monterey County under project funding separate from the NPS/RSC project.

Systems Integration The full NPS Earthquake Response data, software, and products capability described above can be set up on existing EOC hardware/software systems (without the EOCIB and HCN components) for use in training and in-place emergency response. This sets the stage to allow emergency response personnel to utilize the capabilities developed by NPS in day-to-day preparation for emergencies and to carry the lessons learned during the program development and various exercises to a full capability, useful when an emergency arises. The delivery of the EOCIB and HCN hardware to Monterey City (and in the near future to the City of Monterey) will allow emergency responders to take these capabilities one step further – to use in a field situation, deployed to the emergency, or a supporting location. This concept was tested in a field exercise/training scenario during August 2012 and additional demonstrations and training were conducted during February 2013. NPS plans to continue coordination and cooperation with both Monterey County and the City of Monterey to help fully integrate these equipment, software, data, and approaches into disaster response CONOPS. The existing EOCIB resides at the Monterey County EOC and has both hardware and software to become the EOC backbone in the case that the fixed site EOC becomes unusable. These systems and the NPS-provided data, however, require periodic updates to maintain full readiness for emergency situations. The first step is to make sure hardware, software and databases are updated and accurate. Routine steps that need to be taken include:

Page 15: Systems Integration, Transition and Training Playbookfaculty.nps.edu/scrunyon/DHS/Monterey_Earthquake...Systems Integration, Transition, and Training Playbook # RSC-10 iii Executive

Systems Integration, Transition, and Training Playbook # RSC-10

12

o Hardware, especially memory, should be upgraded as necessary to support command and control functions, growth in the resident data bases and new requirements.

o Software should be upgraded on a regular basis as new revisions become available from the software vendors. The primary software for mapping and GIS purposes is ArcGIS. Most counties and major municipalities have GIS professionals using ArcGIS as the primary mapping software. In addition, other software as specified may necessary to process specific imagery, maps, and supporting datasets.

o The EOC should implement a routine to test all supporting software when either hardware or supporting software is updated or changed. On occasion, updates to an operating system will cause software that did work to stop due to a now incompatible match.

o Imagery and other databases should be updated on a regular basis to ensure they are current. The key is to update pre-event databases as often as possible to insure that you the latest pre-disaster conditions can be compared to information collected during and after a disaster.

o All components should be tested in the context of earthquake response by the use of both formal an informal training and by integrating the data and products into disaster exercises and other preparatory events.

Transition and Training

The project team constantly sought the opinions and expertise of the Emergency Management Community (EMC) during the course of the project. The initial meeting occurred in January, 2012. It was attended by over 50 members of the EMC, academia, local, state and federal government attended as well as the program director and sponsor, Dr. Bruce Davis, Department of Homeland Security. A following series of meetings and interviews established the focus for the NPS Earthquake Response Project. Several sets of coordination meetings were conducted with emergency response and management personnel from Monterey County and the City of Monterey and other California communities to determine requirements. San Diego, Los Angeles, and Riverside Counties also participated in discussions and contributed valuable experience and information. Three significant exercises were conducted in support of the project. The first was held at a state park about 27 miles south of Monterey where the primary focus was on demonstrating the capabilities of the HFN Group’s communications and the EOCIB functions in an austere environment and determining initial feasibility of supporting the NPS Earthquake Response Projects hardware and communications requirements for remote sensing product development and distribution. The second was held at Camp Roberts, CA, in conjunction with NPS RELIEF, this time with the objective of demonstrating all capabilities detailed in this document to the emergency responders from other California communities. This exercise was used to coordinate, plan and execute the NPS Earthquake Response Project methodology and products, with the objectives of evaluating capabilities; identifying what worked and what needed to be fixed, improved, or changed; and to elicit feedback from the emergency response

Page 16: Systems Integration, Transition and Training Playbookfaculty.nps.edu/scrunyon/DHS/Monterey_Earthquake...Systems Integration, Transition, and Training Playbook # RSC-10 iii Executive

Systems Integration, Transition, and Training Playbook # RSC-10

13

community. The discussions and feedback were frank, direct and very much appreciated. The third exercise was a demonstration of all the capabilities of the integrated systems (excluding HFN), refined based on the emergency community’s feedback and deployed on the Monterey County EOCIB. Each of the approaches and products listed in the Playbooks were demonstrated to the audience in a training format, that is, each effort provided an overview and then a step-by-step demonstration of how it worked. Selected hands-on exercises were conducted by the participants. Feedback was elicited in real time with additional post exercise feedback, which was worked back into the project to hone each process and its description in the Playbooks. The NPS team then engaged with the city and county of Monterey, to allow direct user testing of the hardware/software/data systems comprising the full suite of capabilities deployed at the conclusion of the project. The support from both was tremendously useful and essential to the success of the project. Playbooks were revised again based on their comments and suggestions. The series of ten (10) Playbooks describing the NPS-developed data, approaches, analysis methods, and implementations in detail are the principal technology transfer vehicle for this project. They are provided in digital (PDF) format along with the digital imagery and supporting data on the USB drives provided to Monterey County and the City of Monterey. In addition, the stand-alone webpage provided on the drive allows directed single-point access to all of the data, the Playbooks, and supporting information derived during the project. This webpage is also publically available (with removal of some sensitive information) at: http://www.nps.edu/Academics/Centers/RSC/Projects/Earthquake-Response-Project.html.

The NPS Earthquake Response Project elicited unprecedented cooperation between the EMC and NPS remote sensing professionals. A new set of capabilities were delivered to the Monterey EOC specifically, and to the EOC community at large. Operational transition of the findings of this project for routine use during a disaster event, however, is dependent on further coordination and training to make sure data, processes, and findings are incorporated in EOC CONOPS at Monterey County and the City of Monterey. While this specific project is complete, the NPS team plans further coordination with Monterey County and the City of Monterey to be sure that these capabilities continue to be developed in support of possible earthquakes and other disaster situations.

Page 17: Systems Integration, Transition and Training Playbookfaculty.nps.edu/scrunyon/DHS/Monterey_Earthquake...Systems Integration, Transition, and Training Playbook # RSC-10 iii Executive

Systems Integration, Transition, and Training Playbook # RSC-10

14

References These are some of the publications describing elements of the NPS/RSC earthquake response remote sensing research efforts and products: Clasen, C.C., Kruse, F.A., and Kim, A.M., 2012, Analysis of LiDAR Data for Emergency

Management and Disaster Response: in Imaging and Applied Optics Technical Digest, 24 June - 28 June 2012, Monterey, CA, USA, Optical Society of America (paper RTu2E.2.pdfon CD-ROM).

Kim, A.M., Kruse, F.A., Olsen, R.C., and Clasen, C.C., 2012, Extraction of Rooftops from LiDAR and Multispectral Imagery: in Imaging and Applied Optics Technical Digest, 24 June - 28 June 2012, Monterey, CA, USA, Optical Society of America (paper RTu2E.1.pdf on CD-ROM).

Kruse, F.A., Clasen, C.C., Kim, A.M., and Carlisle, S.C., 2012, Use of Imaging Spectrometer Data and Multispectral Imagery for Improved Earthquake Response: in Imaging and Applied Optics Technical Digest, 24 June - 28 June 2012, Monterey, CA, USA, Optical Society of America (paper RM2E.1.pdf on CD-ROM).

Kruse, F.A., Clasen, C.C., Kim, A.M., Runyon, S.C., Carlisle, S.C., Esterline, C.H., Trask, D.M., and Olsen, R.C., 2012, Tiered remote sensing and geographic information system (GIS) based map products for improved earthquake response: in Proceedings 34th International Geologic Congress (IGC), 5 -10 August, 2012, Brisbane Australia.

Kruse, F.A., Clasen, C.C., Kim, A.M., and Carlisle, S.C., 2012, Effects of spatial and spectral resolution on remote sensing for disaster response: In proceedings, IEEE International Geoscience and Remote Sensing Symposium (IGARSS2012), 22 - 27 July 2012, Munich, Germany.

Naval Postgraduate School Remote Sensing Center (RSC), 2011, Workshop report: Remote sensing techniques for improved earthquake warning, monitoring, and response, NPS, January 25 – 27, 2011, 19 p. (available as PDF file).

Naval Postgraduate School Remote Sensing Center (RSC), 2012, After action report for NPS/RSC Earthquake Response Exercise, NPS RELIEF, August 15-16, 2012 (available as PDF file).

Page 18: Systems Integration, Transition and Training Playbookfaculty.nps.edu/scrunyon/DHS/Monterey_Earthquake...Systems Integration, Transition, and Training Playbook # RSC-10 iii Executive

Systems Integration, Transition, and Training Playbook # RSC-10

15

Appendix A: Emergency Operations Center In-A-Box (EOCIB) Instructions

This section provides detailed instructions on how to access and use the EOC in a box and its virtual machines. The figures are included to highlight overall configuration of key components as well as the location of various handles, locks, cables, power buttons, and connections. The playbook can be used as a step-by step guide on how to utilize the system, and also as a reference manual for the various components that comprise the EOC in a box.

Figure 1, SKB case

Figure 2 SKB case front/rear view

Page 19: Systems Integration, Transition and Training Playbookfaculty.nps.edu/scrunyon/DHS/Monterey_Earthquake...Systems Integration, Transition, and Training Playbook # RSC-10 iii Executive

Systems Integration, Transition, and Training Playbook # RSC-10

16

Figure 3 Front view showing all components

Figure 4 Front view with KVM in upright position

Page 20: Systems Integration, Transition and Training Playbookfaculty.nps.edu/scrunyon/DHS/Monterey_Earthquake...Systems Integration, Transition, and Training Playbook # RSC-10 iii Executive

Systems Integration, Transition, and Training Playbook # RSC-10

17

Figure 5 KVM Release Levers

Figure 6 Main UPS On-Off button

Page 21: Systems Integration, Transition and Training Playbookfaculty.nps.edu/scrunyon/DHS/Monterey_Earthquake...Systems Integration, Transition, and Training Playbook # RSC-10 iii Executive

Systems Integration, Transition, and Training Playbook # RSC-10

18

Figure 7 Rear view showing all components

Figure 8 Close-up of network and power connections

The EOC in a box is simple to deploy and simple to set-up. The step-by-step instructions will help users to setup the systems in a matter of minutes and be operational in under an hour.

Page 22: Systems Integration, Transition and Training Playbookfaculty.nps.edu/scrunyon/DHS/Monterey_Earthquake...Systems Integration, Transition, and Training Playbook # RSC-10 iii Executive

Systems Integration, Transition, and Training Playbook # RSC-10

19

INITIAL EOCIB SETUP and BOOT PROCEDURE

1. Figure 1 illustrates the lift handles that should be used to move the EOC in a box to the desired location. Once it has been placed, secure it with the foot locks on the four swivel casters.

2. Figure 2 illustrates the two locks on the front and rear panels of the unit. Simply twist and unlock these, and the doors can be swung open and left on the case, or lifted off and stowed if space is an issue.

3. The Cisco WAP is stowed in the rear door. Remove it from the door and place it on top of the SKB case.

4. Determine what you will connect to for Internet. If it is a VSAT or BGAN, you can plug an Ethernet cable from either device into the orange WAN port of the Cisco WAP. If using a local network, plug into an open switch port that provides DHCP and DNS to end devices on that network.

5. Figure 6 shows the only power cord that needs to be connected. It has a tag labled “MAIN POWER”. This can go into any suitable 110 power outlet, a generator, or other power source.

6. Once the power is connected, figure 5 shows the main power button of the front of the UPS. This is also labled “MAIN POWER”. Simply lift the plastic protective door and push the button. The UPS will self-test and begin to operate in about 10 seconds. The plastic cover is designed to prevent accidental shutoff of the system.

7. After the UPS has posted, it will take about 2 minutes for all the PDU outlets to power up. Once they have done so, the SAN and the SERVER will be ready to power on. There is a power button on the left front of the CORAID SAN, and it needs to be pushed. Once the SAN boots wait 1 minute.

8. Now that the SAN is booted, press the largest button on the V3 Server to power it on. It will take approximately 7 to 10 minutes for the server to boot and all of the virtual machines to start and be ready to access. You should hear a series of noises including fans that will cycle on and off as the system goes through a self-test boot up procedure. This is normal and the sound will reduce once booted.

Page 23: Systems Integration, Transition and Training Playbookfaculty.nps.edu/scrunyon/DHS/Monterey_Earthquake...Systems Integration, Transition, and Training Playbook # RSC-10 iii Executive

Systems Integration, Transition, and Training Playbook # RSC-10

20

ACCESSING and USING the EOCIB-SYSTEM

1. Figure 4 illustrates the login screen for the server. Username and passwords (provided

separately) will allow you to logon to the server. For most cases, you only need to do this so that you can shut the server down and it will correctly turn off all the running virtual machines. If need be, this is the screen you would use for trouble shoot VMware specific issues.

2. There are two methods for accessing the system as a user: a. Wired.

i. If you have a computer with an Ethernet port, you can simply plug it into any of the available ports on the EOC in a box.

ii. Turn on your computer and it will be assigned a network address by the Cisco WAP.

iii. Once your computer is booted, you need to use a web browser to access applications that are web based such as Lighthouse and Ushahidi.

iv. To access a Windows 7 virtual machine, you need to point your browser to http://192.168.125.105 This is the address of the VMware View server, and you will be presented with a list of client software. There are clients for 32 and 64 bit windows and for Macintosh desktop and laptop computers.

v. For Microsoft machines, simply double click on the correct client and accept all the defaults during installation. When the install program asks you for the name of the VIEW server you want to connect to, use the 192.168.125.105 address.

vi. Once the client is installed, you can launch it. If successful, it will ask you for a username and password. Username and passwords are provided separately. Once successfully logged in, you will be given a list of virtual machines you have access to. Simply select one and in a few moments you will have a Windows 7 machine running with all the Remote Sensing applications and data at your command.

vii. When you are done, simply logout of the Windows 7 vm as you normally would and you can disconnect your computer.

b. Wireless. i. There are two wireless networks available. One at 2.4 GHz and one at 5 GHz.

These support most popular wireless networks today including B, G, and N. Both networks are protected with WPA2 personal with AES security and require the user to enter a passphrase to authenticate. The passphrase is provided separately.

ii. Once you have authenticated to the Cisco WAP, your computer will be given a network address and you can follow steps iii thru viii above.

Page 24: Systems Integration, Transition and Training Playbookfaculty.nps.edu/scrunyon/DHS/Monterey_Earthquake...Systems Integration, Transition, and Training Playbook # RSC-10 iii Executive

Systems Integration, Transition, and Training Playbook # RSC-10

21

SHUTTING DOWN and STOWING for TRANSPORT and STORAGE 1. If you have not logged into the TrippLite KVM screen as described in step 1 in ACCESSING and

USING the SYSTEM, do so now with username and password provided separately 2. From the command prompt screen, issue the following command which is case sensitive

a. shutdown now –P b. Allow about 10 minutes for the system to shut down. You can watch the screen and see

that it will have a prompt stating that it is “shutting down vms”. It is critical to allow this to complete correctly as all Windows and Linux machines are performing a graceful shutdown.

c. Once the system is “down”, it will either power off automatically, or you will see a prompt on the screen like this sh-3.2#

If it stops at the prompt, you can press the “MAIN POWER” button on the server to power it off. See figure 3

i. Press the Power button on the Coraid SAN to turn it off. See figure 3 ii. Lift the plastic door on the UPS and press the “MAIN POWER button on it. See

figure 6 iii. All components are now safely powered off.

d. Un-plug the UPS power cord, coil in in a loop, and stow it under the rails of the SKB box e. If you removed the front and rear doors, re-attach those now. f. Lower and stow the TrippLite KVM. Note the release levers from figure 5 above. g. Close and latch the front door. h. Take the Cisco WAP, coil the cables, and stow it in the Velcro straps on the rear door. i. Close and latch the rear door.

Release the 4 wheel locks, transport, and stow as needed.