George Graettinger NOAA OR&R Spatial Data Branch RRT9 Quarterly Meeting, COP Workshop Oakland, CA July 13 th, 2016 NOAA’s ERMA ® COP: Data Sharing, GRPs & New Features

OR&R/ERMA Overview Data Management and Data Sharing BSEE/NOAA GRP Project ERMA New Features Questions (anytime!) Presentation Overview 2

Office of Response & Restoration Assessment & Restoration Division Emergency Response Division Disaster Response Center Marine Debris Program Spatial Data Branch Scientific Support Coordinators National Ocean Service National Weather Service Office of Oceanic & Atmospheric Research National Environmental Data & Information Service National Marine Fisheries Service NOAA 3

Continuum of “Response” Framework for The Office of Response & Restoration Response (24 hours) Recovery or Restoration (Years/Decades) Assessment Restoration 4

What is ERMA? Common Operating Picture (COP) Web-based mapping tool Centralized access to information Increases communication, coordination, and efficiency Prepare for, respond to, assess impacts from incidents or conditions Analyze and visualize environmental information relevant to all hazards 5

What's a COP Worth? OR&R ERMA Application Areas Regional Response Planning Information Management Plans and Data Sharing Federal oversight of Incident data On-scene GIS and Data Management Data delivery, data sharing (ESI, GRP, SCAT, etc.) Hazardous waste site remediation (CERCLA) Natural Resource Damage Assessment (NRDA) case support Restoration planning and implementation 6

Where is ERMA? 7

What is Required for a Good COP? Operational and Environmental Data Secure Access of Data and Users Standard Presentation: Interface, Data, Symbology, & Products 8 Support On-Scene and Off- Site Leadership Needs Support Public Transparency and access to information

Foundation in Data “Situational Awareness and Common Operating Picture (SA/COP) support the Communications and Information Management component of the National Incident Management System (NIMS)” “Individuals and organizations at all levels of response have a responsibility to both contribute to and use reliable information as a part of incident response efforts.” (FEMA E0948 SA/COP Training Course)

Data Sharing Plan Began as DWH Command briefing delivery target Implemented at TX City Y Incident (Response) Fully implemented at Refugio pipeline breach NOLA PREP Ex goal Independent Shell use Martinez Drill/July 2015 Adopted by CA OSPR

Data Sharing Plan Concept Data is the foundation of any effective COP DSP documents all cooperatively collected and processed data Defines what, when and where data will be made available Cooperatively developed by RP, Feds, States & signed by Unified Command

Cooperative Development

What the DSP Ensures Cooperation between all data providers Data partners all have access to the same data Standard formats & approaches: Interoperability Data retention during and after the response Continuity of information

Data Sharing Plan in ICS Part of the ICS Documentation Plan Not about data ownership, ownership is not transferred, but data are shared Everyone gets copies of original, environmental and operational data “Need to DVR the data on a daily basis”

Many COPs: One Data Multiple Organizations means Multiple Audiences DSP goal is to ensure they’re all showing the same data “A COP without data is like a gun without bullets”

ERMA Security “Security through obscurity”…..is not a plan NOAA security assessment and guidelines Federal, secured Amazon Cloud environment – Full server redundancy – Cloud on 24/7 – Ability to expand as needed Data sharing security – Account privileges – Restrict download – Token access for map services 19

ERMA Account Access Public accounts – Publically available data (no login required) Restricted accounts for planning & response – Username/password required Verified by NOAA Various levels of access – Active incidents – Sensitive datasets – NRDA/Trustees – Drills – Password reset 90 days; Inactive accounts 6 months – Only NOS application that uses these password requirements Data available only to appropriate users and use 20

ERMA COP Interoperability & Standards Data Collection, Visualization, Query and Reporting Response Manager, Flex Viewer, NDOW Tablet Electronic Data Collection Mobile field data Collection, QA, Database Ingestion and Delivery 21

ERMA COP Interoperability & Standards NEW Feature: Secure Electronic Data Sharing By layer, by incident, or by permission Response Manager, Flex Viewer, NDOW, Shell, ArcGIS Online 22 TRG IAP/IMSS

BSEE/EPA Contingency Plan Support Contracts 2015 BSEE and EPA contact funding to inventory, ingest, and deliver current GRP data via ERMA Develop recommendations on GRP creation and visualization for ERMA and other GIS systems Create tools/leverage data to support creation of new GRP data 23

Current GRP Partners 24

GRP Project Status Initial inventory complete (but ongoing) Collecting and uploading GRPs into ERMA – GIS data when available – Indexes and downloads of PDFs Evaluating uniqueness and commonality Evaluating common symbology Developing Initial recommendations Produce full recommendations report in

GRP Project Status ERMA GRP Deployment – Oregon and Washington GRP updated and loaded – Carolina’s and Delaware Bay being finalized – New Massachusetts GRPs loaded (NUKA) – Inland GRP for New Hampshire and Maine (NUKA) – Inland GRP for New York being loaded as reviewed and released – Sector Guam GRP development with ERMA draw tool, documents linked from Homeport – Great Lakes USCG Sectors being created and loaded, training planned for September

GRPs in ERMA Data & Formats Currently Available: – Currently GRP data available in ERMA for 31 of 40 District, Sector, or States – Multi feature GIS data (points, lines, polygons) with linked ACP documentation/maps – Single feature GIS layer (points) with or without linked documentation – PDF maps linked to index map or similar – GRP updates continue to be captured and loaded 27

GRP and ERMA ERMA Tools support – ERMA Draw tool updated and deployed – On the fly feature creation and attribution – Allows the creation of preliminary GRP sensitive sites and strategies – Supports the consensus based review and modification of GRPs from Area Committee, RRTs and other partners 28

Leveraging ERMA: Sector Guam, ESI 29

Leveraging ERMA: Sector Guam, NOAA Charts 30

Sector Guam GRPs Planning Mode: Apra Harbor 31 NEW GRPs: 38 booming strategies across 4 Islands

Sector Toledo GRPs Response Mode: Tank Barge Argo 32 NEW GRPs: Sectors Duluth, Lake Michigan, Buffalo, and MSU Toledo

GRPs and ERMA ERMA GRP next steps – Continued support to District/Sector development of GRPs using ERMA tools Sector Guam D9 and all Great Lakes Sectors (District training scheduled for September) – Continued posting of GRPs as available – NOAA/BSEE planning for ongoing development and maintenance of ERMA GRP catalog (with USCG HQ) 33

ERMA Development Major system enhancements: – ERMA symbology libraries (GRP update, Sept) – Draw tool updates (GRP update, Sept) – API tools for updating data in ERMA (Sept) Python libraries for automated pushing into ERMA & System Accounts Integration with other ORR applications (DIVER, RL, Trajectories, etc) – User Interface updates, Angular code, OpenLayers 3 – Security updates

ERMA Development Major user enhancements: – Public and Secure data serving (in place) – Web Cam support (in place) – Time Slider for internal layers and external services (in place) – Watermarks for map products (Sept) – Enhanced Electronic Data Capture – Query Tool improvements IPAC new API – Select Records in table to view in map – ArcGIS 2 ERMA data package tool kit – Polar Projections

ERMA as a Federal COP ERMA provides secure 24/7 access Planning support & tools Operational AND Environmental data Data Interoperability with RP and other agencies Maintains data after the Incident ends Supports data sharing and data delivery Serves internal and external audience Federal COP supports the Public right to know and government transparency 36

Ongoing Incident Support Partnerships Planning Training Outreach Assessment Restoration Incident Notification 37

Acknowledgments NOAA: – Michele Jacobi – George Graettinger – Amy Merten – Mark Miller – Ben Shorr – Robb Wright Genwest Systems, Inc.: – Jill Bodnar – Michael Greer – JB Huyett – Zach Winters-Staszak – Rachel Fox I.M. Systems Group/Freestone: – Jay Coady – Nicolas Eckhardt – Matt Dorsey Development Team: – Aaron Racicot, Z-Pulley – David Bitner, Z-Pulley – Chander Ganesan, OTG – Robert St. Lawrence, UNH Funding Sources: Coastal Response Research Center, US EPA Region II, U.S. Coast Guard, NOAA’s Office of Response and Restoration and Coastal Storms Program, Oil Spill Recovery Institute, Bureau of Safety and Environmental Enforcement

Questions?