1 / 15

Emergency Services Enterprise Framework: A Service-Oriented Approach

Emergency Services Enterprise Framework: A Service-Oriented Approach. Sukumar Dwarkanath , Technical Director, COMCARE. Emergency Services SDO Workshop Columbia University, October 4-5, 2006. Roadmap. Concepts Emergency Services/Stakeholders Current Initiatives - COI Standards Conclusion.

rhoda
Download Presentation

Emergency Services Enterprise Framework: A Service-Oriented Approach

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. Emergency Services Enterprise Framework: A Service-Oriented Approach Sukumar Dwarkanath, Technical Director, COMCARE Emergency Services SDO Workshop Columbia University, October 4-5, 2006 COMCARE

  2. Roadmap • Concepts • Emergency Services/Stakeholders • Current Initiatives - COI • Standards • Conclusion COMCARE

  3. COMCARE Overview • A national advocacy organization of over 100 organizations dedicated to advancing emergency communications and response • Seamless information sharing for the most advanced response to emergencies COMCARE

  4. Concepts • Emergency Services? • It is the set of agencies that are involved in emergency preparedness, planning, response and recovery functions. • Diverse set of entities – from public safety to private industry • Stakeholders • Diverse • Varied needs and requirements • No single entity – in charge • Community of Interest: • a collaborative group of users/stakeholders with a common business objective and mission • Helps to provide shared perspective COMCARE

  5. Current Initiatives - Emergency Services Community of Interest (COI) • Recently Launched – COMCARE/NCOIC • Goals: • Serve as a forum to facilitate collaboration and resource/information discovery • Identify core/shared services that can enable ease of inter-domain emergency communications • Scope • International • Workgroups • Business Requirements Workgroup • Technology Workgroup • Policy Workgroup • Call to Join COMCARE

  6. Emergency Services Enterprise: A Framework COMCARE

  7. Services in the Enterprise ENTERPRISESERVICES Line Of Business (LOB) Services Core Services Shared Services • Vertical, intra-domain • Domain Specific • Ex: A traffic advisory LOB services - the regional domain. • Provisioned as a common shared capability across the enterprise • Ex: Identity and Access Management • Governed by the community - COMCARE/NCOIC Emergency Service Community Of Interest (COI) • Shared by a subset of the enterprise – a group of domains • May be offered as competitive services • Ex: Hospital Bed Availability Service - shared between hospitals, EMS, and EM. COMCARE

  8. Standards – The glue in the framework The OASIS Emergency Management TC Enabling information exchange to advance incident preparedness and response to emergency situations • http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=emergency COMCARE

  9. Message Distribution Alerting and Notification OASIS Common Alerting Protocol (CAP) OASIS EDXL Distribution Element (DE) Vehicular Emergency Data Set (VEDS) Capacity and Resources OASIS DRAFT EDXL Hospital AVailability Exchange (HAVE) OASIS DRAFT EDXL Resource Messaging (RM) Standards – “The Glue of the Framework” Resource: http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=emergency COMCARE

  10. OASIS EM TC Standards- Common Alerting Protocol (CAP) • Standardizes the content of alerts and notifications • Alert • Info • Resource • Area • All-hazards • Can be used for citizen-authority communication Resources: OASIS Emergency Management TC http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=emergency Incident.com http://www.incident.com/cookbook/index.php/Welcome_to_the_CAP_Cookbook COMCARE

  11. OASIS EDXL Distribution Element (DE) • Facilitates the routing of emergency messages • Distribution Type • Geography • Incident • Sender/Recipient Type • ‘Envelope’ with payloads (CAP, EDXL-RM etc) COMCARE

  12. Vehicular Emergency Data Set (VEDS) • Not an OASIS Standard • The Vehicular Emergency Data Set (VEDS) is an XML standard for the transmission of telematics data to emergency response agencies. • Source of Data • Incident Data • Agencies Notified • Automated Incident Data • Post Crash On-scene data • Personal medical data • Currently used in pilots and trials • Department of Transportation sponsored test being conducted in Minnesota. • It is also being tested in Orlando, FL where OnStar is sending crash data directly into its 9-1-1 Computer Aided Dispatch (CAD) system. COMCARE

  13. Conclusion Sukumar Dwarkanath Technical Director, COMCARE sdwarkanath@comcare.org 202-429-0574 Resources: COMCARE - http://www.comcare.org OASIS EM TC - http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=emergency COMCARE

  14. Backup Slides COMCARE

  15. Use Case Response Agencies COMCARE

More Related