1 Sukumar Dwarkanath, Technical Director, COMCARE Agency Locator Services: EPAD Emergency Services SDO Workshop October 4-5, 2006 New York

2 Outline  COMCARE – Overview  Two Core Services  Agency Locator and Identity Management - EPAD  Overview  Prototype  Alpha version - design overview  Next Steps - NEARS

3 COMCARE Overview  A national advocacy organization with over 100 members dedicated to advancing emergency communications and response  Our goal: seamless, geographically targeted information sharing for the most advanced response to emergencies

4 Outline  COMCARE – Overview  Two Core Services  Agency Locator Service and Identity Management - EPAD  Overview  Prototype  Alpha version - design overview  Next Steps - NEARS

5 Core Service - Agency Locator Service (EPAD)*  A national directory of agencies, NOT individuals  Secure, shared community utility that will operate as a non-profit public/private partnership  Geospatially-enabled, web-based registry that enables the accurate routing of emergency and warning messages * EPAD Emergency Provider Access Directory

6 Agency Locator Service - EPAD  Information profiles are established and maintained by the agencies themselves  Agencies choose what information they receive  Agencies choose when and how they receive it  Agencies choose who has access to its information  Messaging systems query EPAD to determine to whom and where messages should be sent  EPAD returns a list of agencies — based on geographic area and incident type — that can be used for simultaneous message distribution

7 Core Services - Identity Management and Access Control  Linked to EPAD, but independent  Verifies entities and their authority to perform certain actions, such as sending out or receiving messages for certain incidents  Enables secure and reliable information sharing  Four basic functions:  Identification and authentication  Role-based access control  Policy enforcement and administration  Usage Auditing  Serves multiple applications  Flexible; assumes different policies in different areas  Information sharing rules are established and maintained by the appropriate authorizing organizations:  What information can registered organizations receive?  What messages can registered organizations send?  Agencies choose who has access to their information

8 EPAD - Prototype  Locator only, not identity management functionality  Developed by member – DICE  Used in Various Pilots and Demonstrations 

9 EPAD – Detailed Design (Alpha Version)  Funded by Department of Justice (DOJ) grant  Developed detailed requirements  Process and Participants  Outreach to identify stakeholder requirements  National Emergency Response Organizations  Working Groups –Health, EMS and Medical –Transportation –Emergency Management –Public Safety –Federal, State and Local Government  Detailed Design Deliverables:  Design Compositions  Process Flows  Traceability Matrices  Use Cases  Wireframes  Technical Architecture

10 Architecture - Services SOAP EPAD External Facing Components EPAD Query SystemEPAD Admin HTTP GIS Services Web Services Struts EPAD Internal Shared Components SunOne Directory Server SunOne Directory Server SHAREid COREid COREsv PostGIS MapServer MoxiMedia GeoServer Identity Management System

11 Technology Matrix Logical ComponentProductVersion Operating SystemRed Hat Linux Enterprise ASEnterprise AS 4.0 Web ServerApache Web ServerApache 1.3 & 2.x Web ContainerTomCatTomcat 4.x & 5.x Application ServerJBoss Application ServerJboss AS 4.x DatabasePostgreSQL (including Spatial PostgreSQL)Postgres 8.x LDAP ServerSun ONE Directory ServerSun ONE DS 5.2+ Access Manager and Identity Manager Oracle/Oblix COREid, SHAREid, and COREsvCOREid: , SHAREid: 2.5+, COREsv 4.+ GIS ComponentsPostGISPostGIS 1.0 MapServerMapServer GeoServerGeoServer MoxiMedia IMFIMF Enterprise Edition (for OpenGIS) TopoZone Web Mapping ServiceGeoZone OGC WMS

12 Design Summary  Adherence to Open Standards  Adherence to Government Standards  Promote Reuse  High Availability, Scalability, Performance  Secure resources  Minimize custom developed code  Utilize open source solutions  Maximize out-of-the-box COTS functionality  (Identity Management)

13 Outline  COMCARE – Overview  Two Core Services  Agency Locator Service and Identity Management - EPAD  Overview  Prototype  Alpha version - design overview  Next Steps - NEARS

14 Next Steps - The National Emergency Alerting and Response System (NEARS) Initiative  A non-profit cooperative effort focused on demonstrating and deploying interoperable emergency messaging systems using:  National emergency message data standards  Commercial information technologies  Shared, electronic routing directory of agencies  A three-track program that demonstrates the concept, builds production version of EPAD and integrates them into existing emergency response infrastructures  Partners will the lead the effort and ensure directory population and development of business rules for operation.

15 NEARS Partners  American College of Emergency Physicians (ACEP)  Emergency Nurses Association (ENA)  International Association of Emergency Managers (IAEM)  National Association of EMTs (NAEMT)  National Association of State EMS Directors (NASEMSD)  National Emergency Number Association (NENA)  National Association of Emergency managers (NEMA)  National Volunteer Fire Council (NVFC)  Brain Trauma Foundation (BTF)  Emergency Interoperability Consortium (EIC)  Fraternal Order of Police (FOP)  American Public Health Association (APHA)  Brain Injury Association (BIA)  George Washington University Homeland Security Policy Institute  COMCARE  Public Broadcasting Service (PBS)

16 NEARS – Focus Areas  NEARS Tracks:  Nationwide demonstrations to increase Awareness and focus attention on data communications preparedness  Interoperability toolkit that includes the production version of EPAD  Regional Demonstrations and Trials Resource:

17 Conclusion Sukumar Dwarkanath Technical Director, COMCARE Resources: