UICDS™ is the “middleware foundation” that enables information sharing and decision support among commercial and government incident management technologies used to support the National Response
Framework (NRF) and National Incident Management System (NIMS), including the Incident Command Structure (ICS), in order to prevent,
protect, respond, and recover from natural, technological, and terrorist events – especially applied to the public-private interface.
Unified Incident Command and Decision Support™ (UICDS™) Middleware Enables Information Sharing Among Radiological Utilities and Government Responders – A DHS Project
www.UICDS.us Trademark Attributions are on slide 22 Acronym definitions are on slide 23
Page 2 www.UICDS.us TM Trademark Attributions are on slide 22 Acronym definitions are on slide 23
Why We Can’t Share Information
• I won’t give anybody all the data I own • I’m too busy to take time to share • They won’t understand it and will misinterpret it • I need to trust the information I get and those I give it
to • Multiple sources of information will lead to
disagreements • We all use different formats • There is no way to share easily enough to make it
worth while
Page 3 www.UICDS.us TM Trademark Attributions are on slide 22 Acronym definitions are on slide 23
UICDS™ Program Background
• Sponsor: Department of Homeland Security (DHS), Science and Technology Directorate, Infrastructure Protection and Disaster Management Division – Phase I – Four Contending UICDS Architectures – Phase II – Final Architecture and Reference Implementation – Phase III – Nationwide Pilots
• UICDS Architecture Specification describes the standards and interfaces
• UICDS reference implementation, software that is piloted in a real-world, operational environment and includes example code for technology providers to use to adapt their products
Page 4 www.UICDS.us TM Trademark Attributions are on slide 22 Acronym definitions are on slide 23
The Goal of UICDS™ Is ….
Information sharing and decision support for all individuals, teams, and organizations in the National Response Framework (NRF) and National Information Management System (NIMS), including the Incident Command System (ICS)
Potential UICDS users include police, fire, EMS, EOCs (local, state, tribal, federal), public works, health, transportation, infrastructure, NGOs
• Cross-domain • Cross-role • Cross-function • Cross-echelon • Cross-hazard • Cross-application
Page 5 www.UICDS.us TM Trademark Attributions are on slide 22 Acronym definitions are on slide 23
Basic Principles and Benefits of UICDS™
• Personnel • Facilities • Situation reports • Vulnerability analysis • Sensors and video • Mutual aid • Hazard forecasts • Geospatial mapping • Operations procedures
• Intelligence • Consequence assessment • Public information • Operations plans • Infrastructure • Finance and accounting • Science and technology • Maintenance status • And others
• Warnings • Dispatch • Analytical modeling • Lessons learned • Weather • Incident information • Training and exercises • Collaboration • Equipment and resources
• Share information according to agreements among applications that are already used by participating organizations
• No new user interfaces, training, or applications to purchase
• Never come between a system of record and a data owner, a data owner and its end-users, or an application and its customer
• Royalty-free software using open standards technology
• Continuously share more than situational awareness; UICDS™ enables collaboration among operational applications
Page 6 www.UICDS.us TM Trademark Attributions are on slide 22 Acronym definitions are on slide 23
Information Sharing: Not a Product, a Multi-part Process
• What is it? – Incident management means keeping multiple agencies informed
• Where is it? – The geospatial view
• Who’s in charge? – Organizing incident command or emergency support function
• Who should know? – Alerts from one authoritative source sending to many
• What’s the impact? – Understanding the environment by sharing sensors, cameras
• What’s happening? – Situational awareness or common operating picture aggregating many sources
into one for a shared view • What’s next?
– Action plans coordinate through the Incident Command System
Page 7 www.UICDS.us TM Trademark Attributions are on slide 22 Acronym definitions are on slide 23
Cycles of Information Sharing
What is it? Where is it? Who’s In Charge? Who Should Know? What’s the Impact? What’s Happening? What’s Next?
What is it? Where is it? Who’s In Charge? Who Should Know? What’s the Impact? What’s Happening? What’s Next?
Shared Knowledge
Shared Knowledge
Individual Agency Actions
Individual Agency Actions
Individual Agency Actions
UICDS™ Provides Continuous Information Sharing
Page 8 www.UICDS.us TM Trademark Attributions are on slide 22 Acronym definitions are on slide 23
Everybody Knows What They Need For Little Problems
Expected event duration
0-2 hours 2-24 hours Days Weeks
Pre
pare
dnes
s
Inte
rope
rabi
lity
Local2nd division
1st divisionNational
Multi-national
Single-agency and public preparedness
Governance level responder-receiver organizations involved
Few local agencies
Several agencies from multiple local
jurisdictions with one regional (1st
division) agency
Agencies from many local and
multiple 1st division jurisdictions, and a
few 2nd division agencies
Agencies from many local, 1st
and 2nd division jurisdictions, and a several national-level
agencies
Agencies from a multitude of
local, 1st and 2nd division
jurisdictions, many national,
and some multi-national
agencies
12
3 45
6
• Coordination complexity• Sustained interoperability
8
1. Achieving Interoperability, p. 302.
Page 9 www.UICDS.us TM Trademark Attributions are on slide 22 Acronym definitions are on slide 23
UICDS uses existing applications to visualize shared data – there is no UICDS user interface
UICDS adds intelligent connectivity to all compliant applications
Individual applications continue to support users as always
EOC
Application Data
Dispatch
Application
Resource
Application Data Data
adaptor
Unified Incident Command and Decision Support™ (UICDS)
adaptor adaptor
adaptor adaptor
adaptor adaptor
adaptor
adaptor
adaptor
adaptor
UICDS™ Creates Information Sharing Among Existing Applications
Health Application
Awareness Application
Modeling Application
ICS Application
Dispatch Application
Inspection Application
Pre-Plan Application
adaptor
Geospatial Application
Sensor Application
Page 10 www.UICDS.us TM Trademark Attributions are on slide 22 Acronym definitions are on slide 23
UICDS™ Is a Service Oriented Architecture With Standards-based Web Service Interfaces
XMPP via TCP Network
Page 11 www.UICDS.us TM Trademark Attributions are on slide 22 Acronym definitions are on slide 23
Data Standard
Data Standard
Data Standard
Data Standard
Data Standard
Data Standard
Applications Are Connected to a UICDS™ Core
• Your Technology Providers write UICDS adapters for their applications that do two things:
(1) Translate application data into and out of UICDS data standards and
(2) Connect to UICDS web services to provide or consume data
• UICDS Cores can serve any set of organizations by using web services to connect and authenticate the application’s adapter
• Standardized data is distributed through the middleware based on sharing agreements
• Receiving applications consume the standardized data, visualize it, modify it
• The adapter provides the updated data back to UICDS middleware that distributes modified data to subscribing applications, and the sharing continues
UICDS™ Middleware Web Services
Web Services
Page 12 www.UICDS.us TM Trademark Attributions are on slide 22 Acronym definitions are on slide 23
Data Concepts and Standards
CAD Application
Detail Data
Metadata
Digest Data
Fractional Data
• The jurisdiction/end-user/application owns the Detailed Data to manage a response because the application user owns the response
• A UICDS™ Work Product (1) A “fraction” of the Detailed Data that is shared
through UICDS™ is enough to manage the relationship among response organizations
(2) UICDS automatically creates “Digest Data” based on the UCore standard that summarizes the who, what, where, and when
(3) Metadata provides the work product management information
• The Fractional Data is composed using defined data exchange standards –
• XML is the standard language • NIEM is the exchange dictionary • EDXL-DE, EDXL-RM, CAP, OGC WMS, OGC WFS,
OGC SOS, LEITSC, and others are the exchange formats
UICDS™ Middleware
Page 13 www.UICDS.us TM Trademark Attributions are on slide 22 Acronym definitions are on slide 23
• OGC Map Context • Map Feature • Binary File • Link
• URL • KML • GeoRSS • Core Feed
Incident Work Product
UICDS Map Work Product
• Role • Job • Accept
UICDS Task Work Product
Resource Management
(EDXL-RM) Request/Commit
OGC Sensor Observation
Work Product
• Section • Branch • Role
Incident Command Work Product
Resource Person
Adapter
NIEM, CAP, LEITSC
Why Care? UICDS is All About Comprehensive and Actionable Content
UICDS Notification
Adapter Adapter
Adapter
Common Alerting Protocol (CAP)
• ICS Forms
UICDS Incident Action Plan Work Product
• Applications create an Incident Work Product in UICDS by using their preferred message format
• UICDS notifies other applications with a UCore Digest of the incident (or update) plus details to obtain the work product
• UICDS creates an Incident Command Work Product to follow the “who” and “how”
• UICDS creates a Map Work Product to represent "where" and build a picture of the surrounding features
• UICDS provides and consumes CAP alerts • Tasking and dispatch applications assign
jobs to people and units • Sensor applications can contribute with
video, chem-bio, flood, whatever sensor is available to help explain the incident
• Resource applications use EDXL-RM to request and commit resources and EDXL-DE for routing
• The Incident Action Plan is created from ICS Forms describing “what” will be done
Page 14 www.UICDS.us TM Trademark Attributions are on slide 22 Acronym definitions are on slide 23
UICDS™ Is Deployed With Applications Sharing Information With Their Host UICDS Core
Page 15 www.UICDS.us TM Trademark Attributions are on slide 22 Acronym definitions are on slide 23
UICDS™ Core-to-core Sharing Agreements Allow Multi-agency and Multi-jurisdictional Sharing
Page 16 www.UICDS.us TM Trademark Attributions are on slide 22 Acronym definitions are on slide 23
UICDS™ Core-to-core Sharing Agreements Can Specify the Conditions to Include National Agencies
Page 17 www.UICDS.us TM Trademark Attributions are on slide 22 Acronym definitions are on slide 23
UICDS™ UICDS™
Data Owners Control Who Gets What Data When
Detail Data
Detail Data
UICDS™
UICDS™ Work
Product
UICDS™ Work
Product End-User Access Control
End-User Access Control
Data Selection Control
SSL Authentication (HTTPS)
Data Ingest Control
SSL Authentication (HTTPS)
UICDS™ is as secure in data transfer as anything you do
UICDS™
Profile Service Controls Sharing
Bilateral Information
Sharing Agreements
Page 18 www.UICDS.us TM Trademark Attributions are on slide 22 Acronym definitions are on slide 23
Goal • The NJ Radiological Emergency Response Planning (RERP) Unit wishes to improve interoperability between the New Jersey State Office of Emergency Management (OEM) and the Operation Centers for PSE&G and Excelon Corporation, who are the critical infrastructure key resources (CIKR) owners and operators of New Jersey’s three nuclear power generating stations: Salem, Hope Creek and Oyster Creek. • The pilot will provide information sharing between the commercial emergency management applications NC4™ ETeam, used by NJ state OEM, and ESi® WebEOC®, used at the nuclear power station operation centers, at a minimum.
www.UICDS.us
New Jersey (NJ) RERP Pilot Planning Concept
Salem and Hope Creek
Oyster Creek New Jersey Office of
Emergency Management
Delaware Emergency
Management Agency
Page 19 www.UICDS.us TM Trademark Attributions are on slide 22 Acronym definitions are on slide 23
Unified Incident Command and Decision Support ™(UICDS™)
PSEG WebEOC®
Coast Guard
JUMP
Resources
New York
UICDS™ Core
MEMA
UICDS™ Core
DEMA
UICDS™ Core
Excelon WebEOC®
UICDS Sharing: •PSEG Initial Message WebEOC® to State ETeam •Resource Requests and Commits •Hospital Availability •County Blue Force Tracking •Coast Guard JUMP
New Jersey Radiological Emergency Sharing Purpose: PSEG/Excelon WebEOC® Incidents Shared to State ETeam, Resource, and Local Sharing
UICDS™ Core
New Jersey ETeam Hippocrates/Health
Rutgers CIMIC Resources
Gloucester County
Drakontas
Rutgers CIMIC Hospital
Availability
Progress Key Current Effort Near-term Plan
Resource Management
Excelon = Excelon Corporation
Page 20 www.UICDS.us TM Trademark Attributions are on slide 22 Acronym definitions are on slide 23
UICDS™ Core
RERP Pilot Demonstration 1 Purpose: Originate WebEOC® PSEG Incident and Visualize in ETeam and Google Earth®
Software Layer N
C4™
D
emo
Site
SAIC Test
Server ESi ®
Dem
o Site D
emo Laptop
Public Internet Network Topology
PSEG ICMF Board
ETeam Incident
ETeam Incident
ICMF Incident
UICDS™ Incident Work
Product
UICDS™ Incident Work
Product
Page 21 www.UICDS.us TM Trademark Attributions are on slide 22 Acronym definitions are on slide 23
RERP Pilot Demonstration 2 Purpose: Two-way Flow of Incidents Between ETeam and WebEOC® Visualize in Google® Earth
Software Layer N
C4™
D
emo
Site
SAIC Test
Server ESi®
D
emo Site
Dem
o Laptop Public Internet
Network Topology
WebEOC UICDS™ Incident Board
ETeam Incidents
ETeam Incident
WebEOC Incident
UICDS™ Incident Work
Product
UICDS™ Core
UICDS™ Incident Work
Product
Page 22 www.UICDS.us TM Trademark Attributions are on slide 22 Acronym definitions are on slide 23
UICDS™ is the Ideal Public-Private Interface
• UICDS shares information according to agreements so that the data owner retains complete control over data sharing
• UICDS is two-way collaborative information sharing, unlike COPs and situational awareness tools that are one-way, visualize-only
• UICDS is middleware that works with existing applications; there is no new user interface to learn, no application to buy, no cost to obtain it
• Your existing application can originate information to share, and it is notified when there is new or updated incident data from other organizations
• Your application uses the data, improves it, and adds related data that is shared in the background without any disruption to your operation
• With UICDS you are better informed, your partners are better informed, and together you all make better response decisions
Page 23 www.UICDS.us TM Trademark Attributions are on slide 22 Acronym definitions are on slide 23
Comments and Discussions
UICDS™ Project Community Outreach Director
James W. Morentz, Ph.D. (703) 589-3706
DHS S&T Program Manager Michael B. Smith
DHS S&T Program Support Tomi` Finkle
UICDS™ Project Project Manager Chip Mahoney (917) 574-7356
DHS S&T Technical Lead Dr. Nabil R. Adam
TM
Page 24 www.UICDS.us TM Trademark Attributions are on slide 22 Acronym definitions are on slide 23
Trademark Attributions
• Unified Incident Command and Decision Support, UICDS, and the UICDS logo are trademarks of the United States Department of Homeland Security in the United States and/or other countries.
• SAIC is a registered trademark of Science Applications International Corporation in the United States and/or other countries.
• Opensearch is a registered trademark of A9.com, Inc. in the United States and/or other countries.
• Intergraph is a registered trademark of Intergraph Corporation in the United States and/or other countries.
• ESi and WebEOC are registered trademarks of ESI Acquisition, Inc. in the United States and/or other countries.
• NC4 is a trademark of NC4 Inc. in the United States and/or other countries.
• Google is a registered trademark of Google Inc. in the U.S. and/or other countries.
Page 25 www.UICDS.us TM Trademark Attributions are on slide 22 Acronym definitions are on slide 23
Acronym Definitions
• CAP = Common Alerting Protocol • CIKR = Critical Infrastructure Key Resource • CIMIC = Center for Information Management, Integration and
Connectivity • COP = Common Operational Picture • DB = database • DEMA = Delaware Emergency Management Agency • DHS = Department of Homeland Security • EDXL = Emergency Data Exchange Language • EDXL-DE = EDXL Distribution Element • EDXL-RM = EDXL Resource Messaging • EOC = Emergency Operations Center • EMS = Emergency Management System • FD = fire department • FEMA = Federal Emergency Management Agency • GeoRSS = an emerging Web feed standard for encoding
location • GIS = Geographical Information System • HSIN = Homeland Security Information Network • ICMF = Initial Contact Management Form • ICS = Incident Command System/Structure • IEPs = Information Exchange Packages • IIMG = Interagency Incident Management Group • JDBC = Java Database Connectivity • JFOCG = Joint Field Office Coordination Group • LDAP = Lightweight Directory Access Protocol • LEITSC = Law Enforcement Information Technology
Standards Council
• MACS = Multi-agency Coordination System • MEMA = Maryland Emergency Management Agency • NGO = Non-Government Organization • NIEM = National Information Exchange Model • NIMS = National Information Management System • NOC = National Operations Center • NRF = National Response Framework • OEM = Office of Emergency Management • OGC = Open Geospatial Consortium • OGC-SOS = OGC Sensor Observation Service • PDA = Personal Digital Assistant • PSEG = Public Service Enterprise Group • RERP = Radiological Emergency Response Planning • RRCC = Regional Response Coordination Center • SAFECOM = a DHS communications program • SIOC = Strategic information and operations center • SOAP = Simple Object Access Protocol • SOPs = Standard Operating Procedures • TCP = Transmission Control Protocol • UICDS™ = Unified Incident Command and Decision
Support™ • WFS = Web Feature Service • WMS = Web Map Service • WPS = Web Processing Service • WS = Web Services • WSDL = Web Service Definition Language • XMPP = Extensible Messaging and Presence Protocol