Unified Incident Command and Decision Support (UICDS)

Transcription

1 Unified Incident Command and Decision Support (UICDS) 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.

2 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 3

3 Basic Principles and Benefits of UICDS 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 architecture and software Open standards encourage technology innovation and local adaptation UICDS is more than situational awareness; it is information exchange among applications using standardized data Warnings Dispatch Analytical modeling Lessons learned Weather Incident information Training and exercises Collaboration Equipment and resources 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 Page 4

4 UICDS Creates a Framework for Information Sharing Among Existing s UICDS uses existing applications to visualize shared data there is no UICDS user interface UICDS adds intelligent connectivity to all compliant applications Awareness Modeling Geospatial Sensor ICS Inspection Dispatch Pre-Plan Unified Incident Command and Decision Support (UICDS) Health Individual applications continue to support users as always EOC Dispatch Resource Page 5

5 UICDS Operates Every Day Page 6

6 Providing Local Incident Mutual Aid and State Awareness Page 7

7 Escalating Incidents to Include National Agencies Page 8

8 UICDS Helps Your s Turn Incident into Comprehensive and Actionable Content Page 9 Resource Management (EDXL-RM) Request/Commit OGC Sensor Observation Work Product Common Alerting Protocol (CAP) Incident Command Work Product Section Branch Role Resource Adapter Person NIEM, CAP, LEITSC Incident Work Product UICDS Incident Action Plan Work Product ICS Forms UICDS Task Work Product Role Job Accept UICDS Map Work Product OGC Map Context Map Feature Binary File Link URL KML GeoRSS Core Feed UICDS Notification Adapter Adapter Adapter s 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

9 Pilot Discussion Page 10

10 What You Get Out of a UICDS Pilot The UICDS project team will help you: Assess information sharing requirements of the pilot area Identify applications and agencies across jurisdictions that can participate in information sharing Coordinate the establishment of information sharing agreements Install UICDS Core(s) Work with Technology Providers to create and implement UICDS adapters Test and monitor pilots in accordance with participants goals Leave the complete UICDS installation at the conclusion of the pilot Page 11

11 What We Need to Know to Launch a Pilot What is your information sharing goal? Are there any past information sharing projects, authorities, or agreements in place? What jurisdictions should participate? What agencies or private sector organizations in those jurisdictions should participate? What applications are used by those agencies or organizations from which information should be shared? What are the high priority or quick win information exchanges that UICDS should enable? What is the key data that should be shared among agencies? Who is the UICDS pilot champion who will be the primary leader and point of contact? Page 12

12 Responsibilities of the Pilot Area Developing the Pilot Designate and prioritize participating jurisdictions/agencies and applications Hold area-wide kick-off meeting (in-person or via conference call) Ensure agencies contact their Technology Providers to encourage participation Participate in establishing UICDS information sharing agreements Operations During the Pilot Use UICDS for daily and emergency information sharing Participate in a demonstration exercise of information sharing Invite the expansion of the UICDS pilot to other jurisdictions and private sector critical infrastructure owner/operators Technical Requirements Provide a computer with Internet connectivity to serve as UICDS Core or enable the UICDS Core to be hosted remotely or on the cloud Open necessary ports in firewall Designate IT staff member as the part-time, occasional UICDS system administrator Page 13

13 Page 14 Typical Schedule Task Name Conduct Initial Interview Identify information sharing goal Identify past information sharing projects, authorities, or agreements in place Identify jurisdictions to participate Identify agencies or private sector organizations in those jurisdictions to participate Identify applications used by agencies or org anizations Identify hig h priority or q uick win information exchang es Identify key data that should be shared Identify UICDS pilot champion lead ag ency Conduct Site Survey Codify information sharing goal Current operational state Capability gaps Desired operational state Codify jurisdictions to participate Codify agencies and organizations to participate Codify applications to participate Codify networking and security controls and data Codify objectives of information sharing and key data to be shared Develop Pilot Area Use Cases Develop Site Survey Report Approve Pilot Area Local Participation Commitment Designate participating jurisdictions/ag encies and applications Identify POC for lead agency and POCs for all other organizations/functions Hold area-wide kick-off meeting Ensure all agencies contact all Technology Providers to encourage their participation Participate in establishing UICDS information sharing agreements Develop Resource Profiles Develop Information Sharing Agreement Develop, as needed, interagency policies or sharing agreements (UICDS provides a Local Technical Resources Commitment Identify machine on participant network to serve as UICDS Core Install core software Determine authentication for core (local LDAP or install OpenDS) Install Openfire Install UICDS Core Configure XMPP Set up Certificates (optional) Obtain certificate Install certificate for use in Openfire Install certificate for use with Tomcat Configure Firewall Open ports to UICDS cores with agreements Allow UICDS client machines acces to core Connectivity testing Test Resource Profiles Test Information Sharing Ag reements Create incidents and confirm sharing Identify local UICDS IT resource as UICDS administrator Train local UICDS administrator Implement Adapters Work with Technology Providers to build adapters Install adapters Test adapters Continuing Technical Support Maintain operational functionality of UICDS Core and adapters Capture and share UICDS operational performance statistics Provide Technical Support Local Operations Commitment Enable UICDS for daily and emergency information sharing throughout the term of the Participate in exercises of information sharing to validate and evaluate performance Provide information about UICDS project for public release, subject to reviews as req Promote the expansion of the UICDS pilot to other jurisdictions and private sector criti

14 Technical Discussion Page 15

15 H2 base Hibernate OpenFire XMPP Server OpenDS LDAP OGC WMS, WFS H2 base Hibernate OpenFire XMPP Server GIS System OpenDS LDAP OGC WMS, WFS GIS System Computer External User Adapter PDA/Cell Phone Device Services User Adapter Interface Standards: HTTP, SOAP, WSDL, NIEM, EDXL-DE, EDXL-RM, Atom, WS-Notification, WS-Topic, UICDS IEP Computer External User Infrastructure Services Agreement Profile Notification Work Product Directory Broadcast Interface Standards: HTTP, SOAP, WSDL, EDXL-DE, WS-Notification, WS-Topic OGC SOS EDXL-RM OGC - WPS OpenSearch Adapter Adapter Adapter OpenSearch, JDBC, etc Sensor Resource External Suite External Management Service / Service Simulation Adapter PDA/Cell Phone Device Services User Adapter Interface Standards: HTTP, SOAP, WSDL, NIEM, EDXL-DE, EDXL-RM, Atom, WS-Notification, WS-Topic, UICDS IEP Infrastructure Services Agreement Profile Notification Work Product Directory Broadcast Interface Standards: HTTP, SOAP, WSDL, EDXL-DE, WS-Notification, WS-Topic OGC SOS EDXL-RM OGC - WPS OpenSearch Adapter Adapter Adapter OpenSearch, JDBC, etc Sensor Resource External Suite External Management Service / Service Simulation The UICDS SOA Provides Multiple Options for Interfacing with s and Networks Computer Computer External User External User PDA/Cell Phone Device Services User UICDS Core Interface Standards: HTTP, SOAP, WSDL, NIEM/UICDS IEPs, EDXL-DE, EDXL-RM, Atom/GeoRSS, WS-Notification, WS-Topic UICDS Domain Services (Apache Tomcat) Tasking OGC WMS, WFS GeoRSS, KML Incident Management Incident Command Incident Action Plan OGC SOS Adapter Alert Map Resource Sensor EDXL-RM Infrastructure Services Agreement Profile Notification Work Product Directory Broadcast OGC - WPS Adapter Interface Standards: HTTP, SOAP, WSDL, EDXL-DE, WS-Notification, WS-Topic H2 base Hibernate OpenFire XMPP Server OpenDS LDAP OpenSearch UICDS Core XMPP via TCP Network UICDS Domain Services (Tomcat) Incident Management Alert Incident Command Map Incident Action Plan Resource Tasking Sensor External DB Adapter Adapter Adapter UICDS Core UICDS Domain Services (Tomcat) Incident Management Alert Incident Command Incident Action Plan Tasking Map Resource Sensor GIS System Sensor Suite Resource Management External Service / Simulation External DB External Service External DB Page 16

16 s are Connected to a UICDS Core Standard Standard Standard Web Services UICDS Middleware Web Services Standard Standard Standard 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 which distributes modified data to subscribing applications and the sharing continues Page 17

17 Concepts and Standards Detail CAD Metadata Digest Fractional UICDS Middleware The jurisdiction/end-user/application owns the Detailed to manage a response because the application user owns the response A UICDS Work Product consists of: (1) A fraction of the Detail that is shared through UICDS is enough to manage the relationship among response organizations (2) UICDS automatically creates Digest based on the UCore standard that summarizes the Who, What, Where, and When (3) Metadata provides the work product management information The Fractional 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 Page 18

18 Owners Control Who Gets What When Detail Selection Control SSL Authentication (HTTPS) Profile Service Controls Sharing UICDS Ingest Control Detail End-User Access Control UICDS Work Product Bilateral Information Sharing Agreements UICDS Work Product End-User Access Control UICDS UICDS UICDS UICDS is as secure in data transfer as anything you do Page 19

19 How Does UICDS Improve Other Sharing Designs Different Standards Aggregator or Federated Search Messaging Standards-Based Hub Sharing Single- User Network UICDS Middleware Share across versions and previously disconnected applications Page 20 Different data standards merge in UICDS to enable sharing Users reach outside their network to share and receive information The job of aggregating sensors, feeds, and data is eased by consuming UICDS standard data Messaging applications are the system of record but UICDS notifies others of current alerts UICDS shares among sharing systems UICDS adopts standards to connect to a hub and both consume and provide data

20 DHS S&T Program Manager Michael B. Smith DHS S&T Technical Lead Dr. Nabil R. Adam DHS S&T Program Support Tomi` Finkle UICDS Project Community Outreach Director James W. Morentz, Ph.D. (703) UICDS Project Project Manager Chip Mahoney (917) Page 22