1 / 13

How Federal Data Programs Support Each Other

How Federal Data Programs Support Each Other. Patrick Gannon President & COO, Warning Systems, Inc. OASIS Emergency Management Adoption Committee Christopher (Scott) Shoup Enterprise Architecture Branch, Information Technology Directorate, FEMA Denis Gusty

jolene-prince
Télécharger la présentation

How Federal Data Programs Support Each Other

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. How Federal Data Programs Support Each Other • Patrick Gannon • President & COO, Warning Systems, Inc. • OASIS Emergency Management Adoption Committee • Christopher (Scott) Shoup • Enterprise Architecture Branch, Information Technology Directorate, FEMA • Denis Gusty • Deputy Director, Office for Interoperability & Compatibility, Science & Technology Directorate, DHS • Donna Roy • Executive Director, NIEM • Director, Enterprise Data Management Office, DHS

  2. Emergency Management Standards at OASIS Emergency Interoperability Summit NIEM National Training Event 29 Sep – 2 Oct 2009

  3. Mission To drive the development, convergence and adoption of open standards for the global information society. OASISOrganization for the Advancement of Structured Information Standards

  4. Background Not-for-profit consortium Founded in 1993 as SGML Open Global representation 5,000+ participants representing 600+ organizations and individual members in 100+ countries 70+ Technical Committees 9 Member Sections

  5. Accelerating the development, adoption, application, and implementation of emergency interoperability and communications standards and related work Representing and serving the needs of all constituents, from practitioners to technology providers and national, international and multinational oversight agencies

  6. Emergency Management at OASIS Emergency Interoperability Member Section (formed 2007) Steering Committee 2 Affiliated Technical Committees (TC) Emergency Management TC (formed 2003) EM GIS (Geographic Information Standards) SC EM Infrastructure Framework SC EM Messages and Notification SC EM Reference Information Model SC EM CAP Profiles SC Emergency Management Adoption Committee (formed 2009) EMA Events & Demos SC EMA Collateral & Documents SC EMA Outreach & Education SC

  7. History of EM Standards at OASIS Common Alerting Protocol (CAP) 1.0 ratified 2004 CAP 1.1 ratified 2005 CAP 1.1 Errata ratified 2006 ITU Recommendation x.1303 approved 2007 Emergency Data eXchange Language (EDXL) – Distribution Element (DE) ratified 2006 EDXL – Resource Messaging (RM) ratified 2008 EDXL – Hospital Availability (HAVE) ratified 2008 EDXL – Situation Reporting (SitRep) begun 2009 CAP v1.2 IPAWS Profile v1.0 approved as a Committee Specification 2009

  8. Next Steps for the EM TC CAP 1.2 – voting as Committee Draft RIM valueList URN, CAP Identifier Situation Reporting completion DE 1.1 requirements CAP 2.0 update

  9. Emergency Interop Scenario

  10. Emergency Interop Scenario Train accident with chemical leak Train with chlorine tank cars wrecks Chemical spill creates chlorine cloud Train sensors generate CAP message sent to EOC Hazmat Team is dispatched Incident Commander requests EAS community evacuation notice Local Emergency Operations Center issues EAS via CAP v1.1 wrapped in EDXL-DE, activated via sirens, TV, email, cell phones, radio Incident Commander requests more HazMat support via EDXL-RM wrapped in EDXL-DE Firefighters suffer injuries EM technicians use EDXL-HAVE wrapped in EDXL-DE to determine best medical facility Strong thunderstorms threaten area with possible tornados National Weather Service issues tornado warning via CAP Alert target area for tornado displayed via GIS; message sent via CAP with polygon info AMBER Alert from a NIEM IEPD is sent wrapped in EDXL-DE

  11. Emergency Interop Participants Plus OASIS Contributor Members: CellCast Technologies Evolution Technologies MyStateUSA Safe Environment Engineering Solace Systems TeleCommunication Systems

  12. Emergency Interoperability Summit Track ..................................................WEDNESDAY....................................................... 10:15am - 2:45pm: Interop Demo 2:45 - 4:00pm: Roadmap to Emergency Data Standards Roundtable 4:15 - 5:30pm: Coordinating Development and Adoption of Emergency Data Standards with NIEM 5:30 - 7:30pm: Reception and Interop Demo ....................................................THURSDAY...................................................... 10:15am -1:00pm: Interop Demo 1:00 - 2:15pm: Open Standard for Alert and Warning Messages in Any Medium - CAP 2:45 - 4:00pm: Expanded Family of Data Format for Exchanging Operational Information Beyond Warning - EDXL 4:00 - 4:15pm: Interop Demo 4:15 - 5:40pm: Future EDXL Standards: Tracking Emergency Patients 6:30 - 8:00pm: EDXL, CAP & DE: Ask the Experts

  13. Patrick Gannon President & COO Warning Systems, Inc. pgannon@warningsystems.com +1-256-468-4055 OASIS Emergency Interoperability Member Section Steering Committee Member OASIS EM Adoption TC's Outreach & Education Subcommittee Co-Chair

More Related