interop concepts dhs preso contestabile 09 27 11

Concepts on Information Sharing and Interoperability

Department of Homeland Security Science and Technology

September 27, 2011

John M. ContestabileAsst. Program Mgr. Homeland

Protection

Overview

1. Concepts were developed in former role as the Maryland Statewide Interoperability Coordinator (SWIC) from 2003-2009

2. Originally developed this presentation to bridge the gap between Information Technologists, Practitioners and Decision makers.

3. While the concepts are straightforward, the application has broad ramifications and complexity.

2

3

Background/Contact Information

John Contestabile

Asst. Program Manager

Johns Hopkins University/Applied Physics Lab

[email protected]

443-220-8090

mailto:[email protected]

4

Why is there such a need for communications Why is there such a need for communications interoperability as related to emergency events?interoperability as related to emergency events?

Localized events do not tax the communications structure but, as the incident scale increases, more agencies/jurisdictions and disciplines [i.e. Fire, EMS, Police, Transportation, Public Works…] become involved and hence the need for communication across those entities becomes critical.

In fact, the ability to share information widely across the full range of response/recovery partners will in large measure determine the success or failure of managing that event.

LOCAL REGIONAL STATE NATIONAL

•Minor Traffic Incidents

•Minor Load Spills•Vehicle Fires•Minor Train/Bus

Accidents•Accidents w/

Injuries but No Fatalities

0 - 2 HOURS

•Train Derailment•Major Bus/Rail

Transit Accidents•Major Truck

Accidents•Multi-vehicle

Crashes•Hazmat Spills•Injuries & Fatalities

2 - 24 HOURS

•Train Crashes•Airplane Crashes•Hazmat Incidents•Multi-vehicle

Accidents•Tunnel Fires•Multiple Injuries &

Fatalities

DAYS

• Terrorist Attack/WMD• Floods, Blizzards,

Tornadoes• Transportation

Infrastructure Collapse• Extended Power/Water

Outage• Riots• Mass Casualties

WEEKS

Classification

EXAMPLES

EXPECTEDEVENT

DURATION

•Port/Airport Incidents

•Large Building Fire or Explosion

•Industrial Incidents

•Major Tunnel/ Bridge Closure

• Coordination Complexity• State & Federal Involvement

Public Preparedness

Incident Scale/Public Preparedness

System Must Expand with the Event 5

6

Why is there such a need for communications Why is there such a need for communications interoperability as related to emergency events?interoperability as related to emergency events?

The communications systems that reach across jurisdictions/disciplines must scale as quickly as the incident can grow.

Getting the right information to the right people at the right time is essential to successfully managing the incident.

“National” scale events [i.e. 9/11, Katrina…] involve more state and federal assets and the duration of those events is longer.

7

How might we achieve communications How might we achieve communications interoperability during emergency events?interoperability during emergency events?

Success lies in the ability to rapidly share information across agencies/jurisdictions and disciplines.

Success will require addressing People, Process, and Technology (in that order)

– that is, people must work through a process to agree to share information and the technology must support that decision.

8

People + Process + Technology Alignment

Practitioners Technical Experts

Academia Vendors NGONFP

Data Software

Applications Networks Security Hardware

Consensus building

Requirements Concept of Operations

Action steps identification sustained

commitment Long term Governance

SUCCESS!

9


It is a complex problem so it is necessary to view the various components

Imagine a conceptual interoperability framework in which there are three levels

– The Data LayerData Layer,

– the Integration Layer, Integration Layer, and

– the Presentation LayerPresentation Layer

DATA DATA LayerLayer

INTEGRATION INTEGRATION LayerLayer

PRESENTATION PRESENTATION LayerLayer

Conceptual Interoperability SchemaConceptual Interoperability Schema

10

11


One could try to achieve Interoperability at the data layer by connecting Local/State/National data sets across agencies and disciplines.

However, that would result in a multitude of interfaces between various systems…those systems often being of a proprietary, legacy, firewalled nature.

12


A more artful approach, in keeping with today’s networked architecture, would be for those data layer systems to “publish” once to an “integration layer” tool.

Those agencies/jurisdictions and disciplines who need to see that data, could now look to the integration layer tool to see the information fused with other pertinent data sets, to form a more complete operating picture.

13


Interoperability is achieved at the “Integration Layer” by connecting the various tools at that layer to one another.

This would result in only a few interfaces between a handful of key integration tools….those tools being standards/IP based, open architected, and secure in nature.

DATA LayerDATA Layer

INTEGRATION Layer *INTEGRATION Layer *

(*Addresses the 4 basic questions)(*Addresses the 4 basic questions)

PRESENTATION LayerPRESENTATION Layer

L L L R R R S S N N

L = Local data sets R = Regional data sets S = State data sets N = National data setsL = Local data sets R = Regional data sets S = State data sets N = National data sets


14

What information is needed during an Incident?What information is needed during an Incident?

One needs the answer to 4 questions:One needs the answer to 4 questions:

1. Where is it?

3. Can we talk about it?

5. What do we know about it?

7. Can we see it?

This has ramifications for 4 types of data This has ramifications for 4 types of data or capabilities:or capabilities:

Geographic Information Systems (GIS)/Geographic Positioning Systems (GPS)

Voice Communication Systems (as well as Critical Incident Management Systems – CIMS)

Access to disparate data sets (such as sensors) both static and real time

Video systems

Thus, the Integration Layer tools must address (at least) the 4 types of desired data: Thus, the Integration Layer tools must address (at least) the 4 types of desired data: CIMS, GIS, Video, Sensors - as well as other data setsCIMS, GIS, Video, Sensors - as well as other data sets

15

DATA LayerDATA Layer

INTEGRATION LayerINTEGRATION Layer

PRESENTATION LayerPRESENTATION Layer

L L L R R R S S N N

CIMS GIS VIDEO SENSORS


16

17


Now that the data has been published into a handful of integration tools and those tools have been connected to achieve interoperability, the fused data needs to be “served up” to allow visibility across agencies/jurisdictions and disciplines by publishing into the “Presentation Layer” using a variety of channels from telephony, to web based, to SMS, MMS; both wired and wireless.

This will allow the information to be delivered to those that need it [via push and pull methods] across emergency operation centers, incident command posts, responders as well as the public. The Presentation Layer can take advantage of existing social networking tools to extend their reach.

Conceptual Interoperability Model

19


Some jurisdictions are building systems/solutions that comport to this Conceptual Interoperability Schema.

– The National Capital Region, using Urban Area Security Initiative [UASI] funds, has put in place many tools in the integration layer to achieve information sharing. They have also investing in developing a region wide fiber network [called the NCRnet] and protocols for information sharing [called the Data Exchange Hub – DEH]. This architecture is depicted on the next slide.

NCR Adaptation of the Conceptual Interoperability Model


Such a system could support an operational model whereby Emergency Operation Centers, Fusion Centers, Traffic Management Centers could host/share the Integration layer tools.

– These tools provide near real time situational awareness in a “User defined Operating Picture” that supports decision making. These tools can also push information to the public as appropriate as well as support first responders “in the field” who are part of the Incident Command structure.

First Responder Communications Infrastructure

Public Notification Infrastructure

PUBLIC SAFETY COMMUNICATION

OPERATIONS CENTERS

Supports operations using voice and data

applications

Field Personnel

Provide critical information to

Operations Centers

Receives directions &

provides updates

Public

Receives and acts on critical

information from

Operations Centers

Traveler Advisory

Radio System

Reverse 911

Media /Social Media

Emergency Alert IPAWS

Fiber/Broadband

Network

Microwave Network

Radio Network

Integration Layer tools

“Engine”UDOP

VOICE/DATA

VOICE/DATA

VOICE/DATA

VOICE/DATA

VOICE

VOICE

VOICE/DATA

Proposed Operational Model

22

VOICE/DATA

What are the benefits and challenges?What are the benefits and challenges?

The benefits are access to a wealth of information while responding to or recovering from an emergency incident. This information may literally save lives (of both responders and victims).

The challenges are that it requires agencies/jurisdictions and disciplines agree to share their data as well as fund and share the needed integration tools.

The incentives are that one can drive down costs by sharing infrastructure/systems and pooling resources.

23

Benefits and Challenges of Integrated Systems ContinuumBenefits and Challenges of Integrated Systems Continuum

Local

State

Local

State

Local

State

Local

State

Separate Systems Connected Systems Integrated Systems Fused systemsSeparate Systems Connected Systems Integrated Systems Fused systems

GovernanceGovernanceEasy Challenging

CostCostMore Less

InteroperabilityInteroperability

HighLow

24

SummarySummary

The ability and speed with which you can share information across agencies/jurisdictions and disciplines during an emergency will determine how well you can manage that incident. This is why communications interoperability is so important.

Achieving interoperability at the Data layer, by connecting systems/data sets at the individual agency level is not prudent, scalable, manageable or realistic. Thus, creating an Integration layer with a handful of key applications/appliances which can consume published data (in near real time, optimally), is the strata at which interoperability can be achieved.

Of course, publishing into the Integration layer must respect network requirements, appropriate standards for the data being published and security. The data owner must be able to set the security level of their data, and which users can view that data.

Once the data is consumed into the Integration layer, it is shared across the other applications so as to achieve interoperability and contribute to a more complete operating picture during an incident. Analytical and decision support tools are useful in this layer to make sense out of what is now a very rich set of near real time data.

25

SummarySummary

Such a system could support an operational model whereby Public Safety Communications Operations Centers could host/share the Integration layer tools and provide near real time situational awareness that supports decision making. These tools can also push information to the public as appropriate as well as support first responders who are part of the Incident Command structure.

Benefits of creating an integration layer are: access to data across agencies/jurisdictions and disciplines, improved interoperability, and potentially reduced cost overall. But, recognize that governance becomes more important in shared systems.

Applying these concepts to any particular region will result in some variation based on what applications/networks are available but, the National Capital Region has built many of its existing systems consistent with this model.

The presentation layer is important to distributing the integrated data to end users and leveraging private resources [such as social networking tools]. While examples can be found of the data and integration layer concepts, effective utilization of the presentation layer remains largely underdeveloped at present.

26

Recent Case Study – National Capital Region Recommended “TO BE” Video Sharing Concept

Utilize a Layered Approach

• Interoperability is achieved in the Integration Layer

• Normalize the data

• Distribute the data utilizing a Secure Architecture

• Allow Data to be viewed in each Agency’s current Presentation

Layer Application

27

NCR CCTV Project Inventory

28

Recommended “TO BE” Video Sharing Concept

Pros:

• Provides Agency with source control and the ability to create multiple security domains

• Camera and Intranet are only accessed once• Firewall Friendly• Eliminates Vendor Dependence• Allows Agencies freedom to choose VMS and

Presentation Applications that meets their needs• Highly scalable• Low Bandwidth impact• Ability to share with Mobile devices• Ability to create instant access to video• No Client needed to see the video• Ability to Adjust Stream Bandwidth• Ability to Change Stream Output• Comparable Cost is low

Cons:• Additional Configuration

needed to extend PTZ control

• Limited Access to Video Archives

31

NCR Video Sharing Demo Sites

SSL Secure Portal Demo Site

– https://epicenter.skylinenet.net/ncrportal

ITS MAP Demo Site with Camera and Device Layers

– http://ncrnet.skylinenet.net

Virtual Video Wall Demo Site

– http://ncrnet.skylinenet.net/videowall.html

Mobile Phone Demo Site

– http://ncrnet.skylinenet.net/mobile32

https://epicenter.skylinenet.net/ncrportal

https://epicenter.skylinenet.net/ncrportal

http://ncrnet.skylinenet.net/



http://ncrnet.skylinenet.net/videowall.html



http://ncrnet.skylinenet.net/mobile

Questions?

Thank You!

John Contestabile

Asst. Program Manager

Johns Hopkins University/Applied Physics Lab

[email protected]

443-220-8090

Thank You!

33

mailto:[email protected]

interop concepts dhs preso contestabile 09 27 11

Documents