Maryland Emergency Geographic Information Network July 20, 2005

Project Partners

Copyright © 2005 Towson University Center for Geographic Information Sciences

Matt Felton

Towson University Center for GIS

2

The Challenge

LOCAL

REGIONAL

STATE

NATIONALClassifications

EXAMPLES

EXPECTED EVENT

DURATION

Coordination ComplexityState & Federal Involvement

PublicPreparedness

• Minor Traffic Incidents

• Traffic Crashes• Minor Load Spills• Vehicle Fires• Minor Train/Bus Accidents

• Accidents w/ Injuries

0 - 2 HOURS

• Train Derailment

• Major Bus/Rail Transit Accidents

• Major Truck Accidents

• Multi-vehicle Crashes

• Hazmat Spills

• Some Casualties &

Fatalities

2 - 24 HOURS

• Terrorist Attack/WMD• Floods, blizzards• Transportation

Infrastructure Collapses• Extended power/water

outage• Large Riots• Mass Casualties

WEEKS

• Port/Airport Incidents

• Large Building Fire or Explosion

• Industrial Incidents

• Major Tunnel or Bridge Closure

DAYS

•Train Crashes•Airplane Crashes•Hazmat Incidents•Multi-vehicleAccidents•Tunnel Fires•Major Casualties & Fatalities•Tornadoes

DAYS

Used with permission of the Maryland Department of Transportation

3

Incident Scale and Complexity

• As emergencies “spin up” there is a need for more information and multi-agency coordination

• To effectively respond to incidents, first responders and decision-makers need …• Data – Information about the incident• Tools – A way to manage and interpret that data• Interoperability – A way to share knowledge

LOCALREGIONAL

STATENATIONAL

Coordination ComplexityState & Federal Involvement

PublicPreparedness

4

Maryland Model For Data Sharing

Regional/State

WebEOCBlue 292 RamSafe

Local National

JREIS

Data

County GIS

Health

Transit

Public Works

Law Enforcement

Fire/ EMS

Transportation Weather

Planning

EmergencyManagement

Licensing

MedicalNatural

Resources

State Police Environmental

EPA

USGS

DHS

Interoperability

Tools

Turning Data Into Information

Turning Information Into Knowledge

Turning Knowledge Into Coordinated Action

Federal Applications (HSIN / DMIS)

Interoperability Backbone

5

What is EMMA©?

• Tool that adds a spatial component to the incident management process• “Where is it?”• “What’s nearby?”• “What information can I

learn about that location?”• “Thin Client” software built

upon ArcIMS (ESRI)• Web-based Geographic

Information System (GIS) • Provides the ability to

create dynamic maps• Access and assemble data

from multiple sources including real-time

6

How does EMMA© relate to Incident Management Software?

• Adds a spatial component to the decision making process

• “Common Operating Picture”– A picture is worth a thousand words…

• Turns data into information– Map visualization– Location analysis– Report generation

©

7

EMMA© Functionality

• Identify an incident location• Field to EOC communication

• Generate a location report• EOC to field communication

• Visualize an incident location• Integrate multiple data sets into one view

• Analyze an incident location• Analyze an impacted area

• Coordinate resources• Real time, resource tracking

©

8

©

Enterprise Architecture

VisualizeMaps

AnalyzeIncident

GenerateReport

LocateIncident

Knowledge

GISDatabase

Maps

Information

Integration withIncident Management Tools

DecisionsRemote InteroperabilityConnector Kit (RICK) ©

Real-TimeData

Public / PrivateDatabases

Web Pages

Data

RemoteMap Servers

Sh

ared M

aps

9

The Need for More Data

• Successful implementation of Incident Management Suite of Tools (September 2004)

– EMMA Version 1.0 installed at MEMA• Accessed by local county EOCs• Available to State EOC representatives and MEMA staff

– WebEOC installed with EMMA linkages for• Locating incidents by address or map click• Viewing all incidents statewide• Saving location reports and briefing maps for collaboration

– Incorporation of over 40 map layers from publicly available sources• MEGIN Proposal submitted to U.S. Department of Homeland Security,

Information Technology Evaluation Program (Summer 2004)– Leverage existing efforts underway in Maryland– Interoperable architecture– Non-intrusive– Finding, sharing, and integrating maps into the decision making process– Before, during, and after incidents

10

*MEGIN Diagram*

City 1

City 2

City n

County n

County 2

County 1

RegionalCouncil

WebService

WebService

WebService

WebService

MetadataServer/Explorer

DataWarehouse

HotBack-up

State Agency 1

State Agency 2

State Agency n

WebService

WebService

Federal Data Sets

County EOCEOC

SEOC

MarylandSecure Intranet

GOS

EMMA(Geospatial Tools)

WebEOC(Incident

Management Tools)

EmergencyResponse

Community

Maryland Emergency Geographic Information Network

EDXL / HSIN

(InteroperabilityTechnology)

11

Addressing Barriers to Information Sharing

• Information dispersal: Best data is kept where it is used in daily business process– MEGIN documents the location, use-constraints, and accuracy of

data• Pride of ownership: Data owners fear that costly data may be

leaked, misused, or modified– MEGIN provides a secure, non-intrusive structure for gradual,

controlled sharing• Access to secure databases: May be blocked, unknown,

inaccessible, or destroyed– MEGIN provides tools to facilitate visualization and sharing of data

to illustrate critical information• Timely and accurate integration of disparate data: Multiple

languages and cultures exist across the EM community– MEGIN provides a framework for documenting policies before an

incident occurs, sharing a common operating picture during an incident, and creating a data backup after an emergency

12

What is MEGIN?

• A new kind of GIS clearinghouse– Access to relevant information during emergencies– Automatic, controlled access to data– Allows backup to a secure off-site location

• Secure, intranet environment– Multiple tiers of security– Controlled access

• Optimized for first responders– Easy to use– Familiar language / terminology– Support collaborative decision-making and conversation across

communities

•Delivering the right data, at the right time, to the right person

13

Sharing Data Between Agencies

Shared Map Shared MapWebEOC

Web Server

WebEOCIncident

Database

IncidentInformation

WebEOC

Web Server

WebEOCIncident

Database

IncidentInformation

Agency 1 Agency 2

Custom(i.e. “scraping”)

EMMA

Web Server

Inte

rna

l Ma

p

RICK

ConversionTo GIS Format

RemoteData

RemoteData

RemoteData

GML XML

Relate

IncidentMaps

RemoteData

FeatureIngestion

ScheduledHarvesting

Agency 3 Agency 4 Agency n

MEGINMEGIN

Secure GIS PortalSecure GIS Portal

EMMA Software

ESRI Software

ESi Software

Existing Infrastructure

Data

EMMA

Web ServerIn

tern

al M

ap

Relate

IncidentMaps

RICK

ConversionTo GIS Format

GMLXMLCustom(i.e. “scraping”)

RemoteData

RemoteData

RemoteData

RemoteData

ScheduledHarvesting

ArcIMS

Spatial Server

Database Connection

ArcSDEGIS

Database Server

GISData

ArcIMS

Spatial Server

ArcSDEGIS

Database Server

Database Connection

GISData

Share

d M

apOracle

SecurityComponent

Shared Map

Shared Map

Shared Map

OracleSecurity

Component

14

MEGIN Components

• Metadata repository with publisher and explorer– Modification of Maryland Mapping Resource Guide

(MMRG) data input application– GIS Portal Toolkit (ESRI)

• Map Services– Identification and documentation of existing web services– Creation of selected new web services

• Map Viewer and Data Integrator– Emergency Management Mapping Application (EMMA)

• Rights Management– Oracle Identity Management (formerly Oblix CoreID)– Oracle Web Services Manager (formerly Oblix CoreSV)

15

Metadata Repository

Public Internet

MMRGRepository

GeospatialResources

PublicAccess

Post Search

NSDIMMRG Survey

MMRGRepository

SensitiveGeospatialResources

Search Post

EmergencyAccess

EmergencyPersonnel MEGIN Survey

MEGINRepository

Secure Intranet

Firewall

Harvesting

16

Sharing Information About Your Data

17

MEGIN Domain

Rights Management

UserDirectory

Authentication Engine

Authorization Engine

User

Web Client

Client Domain

PortalHome

LoginScreen

Digital Certificate

User NamePasswordDigital Certificate

Authenticated

Search for Data

Authorized

MetadataTables

MetadataSecurityTables

Web Service Security

MapService

Session Token

SearchResults

PublishData

Monitoring

Policy Manager

Remote Data Provider Domain

User NamePasswordDigital Certificate

Connection Information

IPSEC

IPSEC

Audit Logs

Data Sharing Policies

User NamePasswordDigital Certificate

SSL

SSL

Version 1.0.1March 15, 2004

MEGIN Security Concept

18

MEGIN Portal

19

Benefits of MEGIN

Improving the decision making process before, during, and after emergencies

• Access– Providing emergency personnel with the information they need,

when they need it most

• Coordination– Bridging multiple disciplines across jurisdictional boundaries at

all levels of government

• Security– Protecting sensitive information for those who need to know

20

Meeting Complex Needs for Homeland Security

• Data Analysis– Ability to ask questions of the data and get

actionable answers

• Data Fusion– Decision support tool that creates a common

operating picture for emergency management needs

• Data Accessibility– Harvesting real-time and/or remote data

• Data Discovery– Secure card catalog (a “Google”) that allows EM

community to identify and access data

• Data Deployment– Securely sharing data with trusted partners

• Data Development– Converting or creating data from multiple formats

• Data Collection– Locating and describing information in a usable GIS

format

21

Questions?

Matthew S. FeltonAssociate Director, Center for GIS

Towson University410-704-5292

mfelton@towson.edu

Maryland Mapping Resource Guidehttp://www.MarylandGIS.net/interoperability