Federal Enterprise Architecture Data Reference Model

1
Putting Context to Work Semantic Keys to Improve
Rapid First Response

• Broadstrokes Group

1
2
Putting Context to Work Semantic Keys to Improve
Rapid First Response

• Train Derailment Example
• 6 January 2005, 350 A.M. Graniteville, SC
• Chlorine Tank Car Toxic Release
• Matching ResponseType with EventType
• Using Open Public Standards
• Getting the Right Information to the Right People
  at the Right Time

2
3
Original Timeline v. New Timeline

• Original Timeline 17 Days
• Incident Starts 200 A.M. 6 January 2005
• All Clear 21 January 2005
• New Timeline 12 Days
• Incident Starts 200 A.M. 6 January 2006
• All Clear 17 January 2006

3
4
Original Timeline Problems

• Incident Starts 200 A.M. 6 January 2005
• No Early Public Warning Alert
• First EPA Situation Report 1000 A.M.
• 8 Hour Response Quick, Given Circumstances
• Injuries, Deaths Acknowledged, Chlorine Hazmat
  Identified
• Second EPA Situation Report 400 P.M.
• EPA Region 4 Operations Support Command (OSC)
• Operations Underway

4
5
Original Timeline Problems

• Third EPA Situation Report 7 January 2005
• EPA Region 4 OSC on Scene - Air Monitoring
• Extent Hazmat Release Determined 76 of 131 Tons
• Fourth EPA Situation Report 7 January 2005 - Full
  Operations Begin
• Logistical Support Operations Non-NIMS
  Organizational Impedance
• All Clear 17 January 2005

5
6
New Timeline Improvements

• Incident Starts 200 A.M. 6 January 2005
• COMMON ALERTING PROTOCOL (CAP) Message with
  EMERGENCY DATA EXCHAGE LANGUAGE (EDXL) Header
  Optimizes Immediate Public Warning Alert 215
  A.M.
• Remote Sensors from Tank Cars Automatically
  Trigger Alerts, Trigger Train-Mounted Sirens/PA
  Systems
• First EPA Situation Report 400 A.M.
• Less Than Two-Hour Severe Emergency Response
  Triggered by Fatal-Level Hazmat Release

6
7
New Timeline Improvements

• Second EPA Situation Report 900 A.M.
• Semantically Triggered Response Allows Full
  Operations to Start within 8 Hours Versus Next
  Day
• Hazmat Automatically Identified, Severity
  Semantics Push First Responses and Eliminate
  Jurisdictional Duplication of Incident Command
  Systems (ICS)
• Logistical Support Operations NIMS Plus
  Semantics Eliminates Organizational Impedance
• All Clear 12 January 2006

7
8
Semantic Keys to Improvement

• Common Alerting Protocol (CAP) 1.1 Clarification
• Message ID
• CBRN added to Categories
• Chemical, Biological, Radiological, Nuclear
• Digital Signature Encryption
• Emergency Data Exchange Language (EDXL)
• Event Type and Sender/Recipient Type Ontologies
  will Drive Improved Routing

8
9
Event Type Ontology
Application Protégé http//www.protégé.stanford.e
du
9
10
Event Type Ontology in Context
Application Unicorn Workbench
http//www.unicorn.com
10
11
Ontological (Semantic) AnalysisElement Data
Asset Comparison
Result No Duplicated Elements
11
12
Anatomy of CAP-EDXL Emergency Response
Communications for New Timeline
12
13
Explanation Point by Point of Diagrams

• 1) Upon Notification of the incident, Sheriff
  calls in using his phone or PDA to trigger an
  emergency alert.
• 2) A CAP message is generated and posted to the
  ICS hub where it is posted as Currently Active
  in message repository regularly polled by
  Emergency Management Community. Rules-Based
  Registry Standards allows a publish-subscribe
  mechanism for propagating alert naming messages.
• 3) NIMS ICS Policy-Based messages are
  automatically routed to the Local EM Agency
  where operators can monitor and send out message
  updates.
• 4) The Secondary Providers Services switch to
  Active Polling for any immediate update-CAP
  messages routed by EDXL Distribution Header
  Component with a PublicAlerting value.
• 5) GIS map tool provider services respond to the
  CAP message and process the information, adding a
  new WSRP Portlet for this Incident. ICS
  incorporates mapping service.
• 6) A reverse 911 geo-coded lookup is performed
  and request for local area code-based automatic
  telephone notification is processes and
  performed.

13
14
Anatomy of CAP-EDXL Emergency Response
Communications for New Timeline
14
15
Network Concept

• A network is a graph representation for modeling
  objects of interest and their relationships. It
  contains the following elements
• Nodes objects of interests
• Links relationships between nodes
• Paths ordered list of connected links

x1
k2. s1
k1. x0
x0
s1
k3.s1
x2
15
16
RDF Data Model

• RDF data stored in a directed, logical network
• Subjects and objects mapped to nodes, and
  properties to links that have subject start nodes
  and object end nodes
• Link represent complete RDF triples

P1
S1
O1

• RDF Triples
• S1, P1, O1
• S1, P2, O2
• S1, P2, O2

P2
P2
O2
S2
16
17
Semantic Web Connects Web Services
17
18
Adding Value with Web Services
18
19
Broadstrokes-Reverse 911

• Wireless/VoIP outbound and inbound voice services
• Combines TTS and ASR technologies
• Support for web services, SOAP, VoiceXML, CCXML,
  CAP, XQUERY and XPATH

19
20
Broadstrokes-Features

• Message creation using Text-to-speech
• Message creation using Voice Recording
• Definition of call lists by static lists
• Answering machine recognition
• Call rules support
• Call Escalation
• Call Bandwidth control
• Critical response collection reporting
• Call Status Reporting
• Multiple Language Options

20
21
Broadstrokes-WSRP
21
22
MyStateUSA (Acting as National Incident
Management System-NIMS Incident Command
System-ICS)
22
23
MyStateUSA
23
24
TargusInfo

• Alert the public in any given location reach
  more people with the most complete, up-to-date
  name, address, and telephone records.
• Identify unique, non-public resident information
  for emergency use only TARGUSinfo can access
  and deliver telephone data that is not available
  through other public sources.
• Count on data availability during the most
  critical situations our sophisticated network
  has fully redundant systems, ensuring 24/7
  availability.
• Inform the community of non-emergency activities
  current name and address means you can stay
  connected through continuity of operations (COOP)
  announcements, procedures, special assistance and
  new developments.

24
25
Image MattersalertSmarts Application
25
26
ImageMattersalertSmarts Features
alertSmarts is a geospatially enabled alert
processing platform that provides
state-of-the-art community alert notifications
and alert mapping capabilities.

• Client access to all alertSmarts features via
  Internet
• Context-Sensitive User Interface for improved
  situation awareness and ease of use
• Map Viewer provides access to advanced real-time
  GIS capabilities
• Zone Editor supports Circle, Box, and Polygon
  shaped notification areas
• Notification Editor provides ability to create
  and edit notification using predefined templates
  and from scratch

• Unique map-based call progress/status reporting.
• Customized messages based on ALI record, distance
  from incident, direction from incident and other
  contextual information
• Responses are logged.
• Dynamic messages based on response, either voice
  commands or key press
• Leverages Broadstrokes Voice Server Plus based
  VoiceXML and capable of processing tens of
  thousands of calls per hour

26
27
ImageMattersalertSmarts Features

• Interoperability
• OASIS Common Alert Protocol standard for alerts
• NENA 02-010 ALI compliance for ALI Database
• All applicable W3C and IETF standards for Web and
  Internet OpenGIS Web Map Service

• GIS
• NENA ALI compliant database with fast spatial
  indexing supporting millions of entries
• ESRI ArcIMS / ArcSDE integration
• Real-time map overlays with notification status,
  incidents, alerts, etc.
• Hardware accelerated map rendering for rapid
  display of real-time map data

27
28
ImageMatters - Geospatial Knowledge Base

• Resources
• Any mime-typed object.
• Special treatment of RDF/OWL resources.
• Support mime-type transformation using Java
  Activation Framework.
• Metadata based on Dublin Core.
• Folder Model
• Folders are container of resources.
• Folder have a default RDF/OWL resource, much like
  an index.html

• OFC Ontology Foundation Classes
• Support for RDF/OWL
• XPath implementation.
• JDBC
• Driver and DataSource implementations using J2EE
  Connector Architecture.
• javax.sql.RowSet Implementation.
• SQL-based query language.
• Support for OGC Filter Specification, including
  spatial predicates.
• Support for XPath queries
• Stored procedures using Functor framework.

28
29
Starbourne
29
30
Starbourne
30
31
Putting Context to Work Semantic Keys to Improve
Rapid First Response

• Broadstrokes Group

31