1 / 33

Trans-enterprise Information Exchange

Trans-enterprise Information Exchange. Systems Engineering Department 6444 C5I Information Management Architecture. Objective. To communicate: Why Trans-enterprise Information Exchanges (TIEs) are needed National TIE characteristics Enabling TIE using SOA and EDXL

rocco
Télécharger la présentation

Trans-enterprise Information Exchange

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Trans-enterpriseInformation Exchange Systems Engineering Department 6444 C5I Information Management Architecture

  2. Objective To communicate: • Why Trans-enterprise Information Exchanges (TIEs) are needed • National TIE characteristics • Enabling TIE using SOA and EDXL • Trans-enterprise Services Grid (TSG) Summary and Conclusions

  3. The Bigger Picture • National Incident Management System (NIMS) • HSPD 5 and HSPD 8 • National Response Plan (NRP) • Emergency Support Functions (ESF) • Executive Order 13407 • “Establish or adopt, as appropriate, common alerting and warning protocols, standards, terminology, and operating procedures for the public alert and warning system to enable interoperability and the secure delivery of coordinated messages to the American people through as many communication pathways as practicable” • “Consult, coordinate, and cooperate with the private sector, including communications media organizations, and Federal, State, territorial, tribal, and local governmental authorities, including emergency response providers, as appropriate” • 9/11 and Katrina Lessons • “Employ all available 21st Century technologies both to update and utilize the national Emergency Alert System in order to provide the general public with advanced notification of and instruction for disasters and emergencies” • “Ensure situational awareness by establishing rapid deployable communications as well as instituting a structure for consolidated Federal operational reporting to the Department of Homeland Security”

  4. CONTEXT: LEGISLATIVE & HISTORICAL

  5. CONTEXT: LEGISLATIVE & HISTORICAL THE NATIONAL RESPONSE PLAN (NRP) IS INTENDED TO DRIVE EMERGENCY OPERATIONS PLANNING FOR ALL FEDERAL DEPARTMENTS/AGENCIES AND ALL STATE/LOCAL AGENCIES THE NATIONAL INCIDENT MANAGEMENT SYSTEM (NIMS) IS INTENDED TO INTEGRATE ALL NATIONAL CAPABILITIES TO ACHIEVE EFFECTIVE, EFFICIENT RESPONSES AT ALL SCALES AND TO ALL INCIDENTS

  6. CONTEXT: SCOPE

  7. CONTEXT: SCOPE AT SOME POINT, ALL OF FEDERAL AGENCIES AND PARTNERS WILL CONNECT SOME PORTION OF THEIR CAPABILITIES TO THE NIMS IN ADDITION, “Trans-enterprise Information Exchanges” – WILL BECOME THE MECHANISM FOR AQCCOMPLISHING THE NIMS CAPABILITY

  8. SITUATION ASSESSMENT • THE NRP & NIMS ARE BROAD SCOPE DOCUMENTS THAT LEAVE MUCH TO THE IMAGINATION AND ARE STILL EVOLVING • Few "Belly Buttons" Identified • Situation Dependent Interpretations • General Principles – Details Left to Later Plans • Federal Document, but Most Implementation is State/Local Responsibility • HURRICANE KATRINA SHOWED BIGGEST GAP IS INFORMATION SHARING AND COMMUNICATIONS (and associated knowledge & decision management) • NIMS "Mandates" Interoperability, but Doesn't Say Who or How • NIMS "Mandates" Single Point of Coordination, but Leaves the Process to Situation Dependent Decisions • THE ONLY TANGIBLE SOLUTION IS TO USE COMMON COMMUNICATION PROCESSES AND DATA SCHEMAS • Currently SOA is onlyfeasible approach to creating TIE Solutions • A Grid of Services is need to create the TIE capabilities

  9. Characteristics of Trans-enterprise Capabilities • Trans-enterprise Services Grid (TSG) is new term to capture the required characteristic of information exchanges capabilities • Trust Management • All entities trust other Enterprises for required emergency data • TSG capabilities are trusted to enable exchanges between Enterprises • Non-Repudiation of originator of information being exchanged • Negotiation of Exchange Contracts • Automate business processes • Dynamic choreography based on data exchange metadata • Secure Reliable Information Exchange Services • Pre-event discovery services (Publish/Subscribe) • Core Community of Interest (COI) exchange and inter-COI routing services • Mediation service • Auditing Service • Performance enabling services • Protection of Enterprise and Grid Resources • Identification, authentication, and access control mechanisms

  10. Situational Awareness (SA) & Reporting (Push) Primary & Secondary Reachback JAC & NISAC National EOCs NC JOC NOC Analysis Centers Decision Support FOC PEP PEP Situational Awareness Databases Homeland Data Sharing Program (SITREP and ESF reporting) and Chemical, Biological, Radiological,and Nuclear detection PEP PEP PEP USSTRATCOMSKYNET PEP PEP NOAA Sensors State and Local EOCs PEP Detectors

  11. Situational Analysis (Pull) Federal Agencies Reachback JAC & NISAC NC JOC National EOCs NOC Analysis Centers IMAAC and DTRADecision Support FOC PEP PEP Situational Awareness Databases Homeland Data Sharing Program Federated Data Framework (HFDF) and Pre /Post Event Data Analysis PEP PEP PEP USSTRATCOMSKYNET PEP PEP State and Local EOCstactical data storage Tactical field data storage and video

  12. Warning (Push) and Response C2 Reachback JAC & NISAC NC JOC National EOCs NOC Analysis Centers FOC PEP PEP National CommunicationsNCCC and IPAWS Infrastructure PEP PEP PEP PEP Alert & Warn State and Local EOCs Response

  13. How does TSG support NIMS • An emerging Federal, State, Local, Tribal and public-private partnership to share information about common interests across agency enterprises/jurisdictions • TSG supports delivering information (Push) about: • Changes in the real world environment (e.g. CBRN, NOAA) • Response guidance from appropriate decision authority (Warning and Response coordination) • TSG supports developing Situational Awareness and Decision Support (Pull) about: • Course of Action (COA) development for all levels of government • National Disasters, Pandemics, CBRNE Attacks, etc. • TSG enables Customized Operational Pictures (COP) based upon common shared data • Right Information, Right Person, Right Time to prevent/mitigate effects of national threats both natural and man-made

  14. nonXMLContent mimeType size digest uri contentData OR xmlContent keyXMLContent embeddedXMLContent EDXL DE Metadata EDXLDistribution distributionID senderID dateTimeSent distributionStatus distributionType combinedConfidentiality language senderRole * recipientRole * keyword * distributionReference * explicitAddress * targetArea circle * polygon * country * subdivision * locCodeUN * • Specific • Message Content • CAP 1.0 • CAP 1.1 • ANSI N42 • HAVE • CoT • EDXL-RM • IMPP • XMPP • DSEL • Sensor Event • etc. 0..* 0..* contentObject contentDescription contentKeyword * incidentID incidentDescription originatorRole* consumerRole * confidentiality 0..1

  15. Notional TSG Routing Grid Northeast Region Northwest Region EDXL Router EDXL Router Central Region EDXL Router Southeast Region Southwest Region EDXL Router EDXL Router

  16. TSG Distribution Path Northeast Region Southeast Region Router Router NationalHSOC & FOC LA MD Router Router MyStateUSAWeb Server DMISCOGs MyStateUSAWeb Server State EOC CAP + Video Default WSDL, Secondary WSDL, WSDLs of Last Resort in routing Configuration File

  17. TSG Message Replication Southwest Region EDXL-DE Router Low Medium High EDXL-DE Router Southeast Region Surveillance Camera

  18. Program View “End” State DHS Infrastructure (HSIN, DMIS, etc) DoD Infrastructure (USMTF, CoT, etc) NOC JOC Response PEP National Communications EDXL-DE Object Routing Infrastructure PEP PEP Response DOE PEP NISAC FEMA IPAWS EDXL-DE Infrastructure Reachback DNDO Rad/Nuc EDXL-DE Infrastructure DOJ/FBI EDXL-DE? FOC Alert & Warn Detectors

  19. TSG Architecture Scope Executive Briefing POTUS (Congress) National Command Capability ASD/HD DHS warning office Cross-Agency USNORTHCOM HDSP & HFDF DHS & DoD Interface DoD, DHS, DOE, DOJ NC FEMA FBI DTRA DNDO NIJ USSTRATCOM Federal Agencies DNDO Pilots Regions EOCs Counties / States Information Sharing Guardian Pilot? Installations  Local Community Data CCTV Situational Awareness VPS Sensors / Alarm Communications & Display Standards (OASIS, NIST, OGC, etc)

  20. TSG Roadmap / “End” State • EDXL-DE enabled National TSG • Trans-enterprise Information Exchange policy enablement • Standardized Information Exchange (Ontologies) • Open System / Standards • Secure TSG Access / Authentication (PEP) • Edge Enterprise Capabilities • Trans-enterprise Situational Awareness and Sensors • Trans-enterprise COP Display • Trans-enterprise Information Analysis • Trans-enterprise Decision Support • Trans-enterprise Data Fusion/Mining • Enabling information sharing/“intelligence”/situational awareness at all levels from local collaboration to the President’s National operational picture • Role-based Customized Operating Pictures (COPs) based upon common shared data

  21. TSG Roadmap / “End” State Reachback NISAC JOC National EOCs NOC Analysis Centers Decision Support FOC PEP PEP National TSG using EDXL-DE metadata Infrastructure PEP PEP Databases Sensors PEP PEP PEP PEP PEP Detectors PEP Alert & Warn State and Local EOCs Response

  22. QUESTIONS? and DISCUSSION

  23. Backup Slides

  24. OV-2 Levels of Abstraction vs.EDXL Value Pairing Consumer/ EDXL RecipientRole Producer/ EDXL SenderRole EDXL role value Application Application Sender Sender Facility Facility EDXL role value OV-2 Needline EDXL role value EDXL Classification Classification EDXL role valueListUrn EDXL keyword for specific Payload

  25. OV-3 Levels of Abstraction vs.EDXL Value Pairing Identifier/ EDXL ContentObject Identifier/ EDXL ContentObject EDXL keyword or Roles (e.g. OPREP3) Producer Consumer <alert xmlns="urn:oasis:names:tc:emergency:cap:1.1"> <identifier>Aug08_000001</cap1.1:identifier> <sender>dellis@sandia.gov</cap1.1:sender> <msgType>Alert</cap1.1:msgType> <scope>Public</cap1.1:scope> <info> <category>CBRNE</cap1.1:category> <event>Possible Terrorism</cap1.1:event> <urgency>Immediate</cap1.1:urgency> <audience>sensor Management</cap1.1:audience> <:senderName>Rad1</cap1.1:senderName> <headline>Radiation Detection</cap1.1:headline> <alert xmlns="urn:oasis:names:tc:emergency:cap:1.1"> <identifier>Aug08_000001</cap1.1:identifier> <sender>dellis@sandia.gov</cap1.1:sender> <msgType>Alert</cap1.1:msgType> <scope>Public</cap1.1:scope> <info> <category>CBRNE</cap1.1:category> <event>Possible Terrorism</cap1.1:event> <urgency>Immediate</cap1.1:urgency> <audience>sensor Management</cap1.1:audience> <:senderName>Rad1</cap1.1:senderName> <headline>Radiation Detection</cap1.1:headline> InformationExchange Identifier or EDXL contentKeyword or keyXMLContent OV-3 Needline Identifier EDXL contentObject signature and/or encryption EDXL Classification Classification EDXL role valueListUrn

  26. Taxonomy SecurityLevel Has a Have a Collection Of InterestvalueListUrn Have Have TBDAttributes Locations OWNS Owns Values forSenderRecipientOriginatorConsumerKeywordsContent Keywords

  27. Collection Of InterestvalueListUrn OWNS RoleType Sender-RecipientOriginator-ConsumerValues EDXLUsage Have a Have a EDLX MSG at Location B with System at Location A with System Sender Recipient EDXLHeader Communication Needline allowing XML Document transfer enabling theInformation Exchange Requirement (IER) Consumer Originator ContentObject

  28. EDLX MSG at Location A with System keyword EDXLHeader Communication Needline allowing XML Document transfer enabling theInformation Exchange Requirement (IER) keyword contentKeywordValues contentKeyword ContentObject or Paired as Has a Has a Allowed orused Values TagNames Schema orXML Format MIMEType Has Has

  29. Implicit Publish/Subscribe

  30. EDXL Header Usage

  31. ContentObject Elements Usage

  32. Payload Element Usage

  33. EDXL PEP: Edge EDXL Proxy Service CAP, CoT, ANSI N42, XMPP, etc. User Interface (Web, Desktop App) For Custom Creation If needed WSDL or file XML Content Object Via XSLT Security EDXL Constructor Non-XML Content Object Base 64 Encoded Encryption, Decryption, Signing, Verification EDXL Router WSDL or file MPEG, JPEG, Etc.

More Related