Disaster Management eGov Initiative (DM)

1. Disaster Management eGov Initiative (DM) Program Overview December 2004

2. Program History & Mission • One of the 24 eGov initiatives established by the President’s Management Agenda • Supports a multitude of Federal Agency missions including DHS and FEMA missions to reduce the loss of life and property in any phase of a disaster event • Supports the Federal mission to provide the Nation a comprehensive, risk-based emergency management program • Recipient of multiple awards

3. Program Components“Three Pillars” • Portal to information and services (www.DisasterHelp.Gov) • Disaster Management Interoperability Services (DMIS) • Data exchange standards: Facilitating the creation of information sharing capabilities between disparate incident management software applications

4. Portal to Information and Services 34,086 Registered Users 3,932 Collaboration Centers Emergency Management Community Public • Aggregated disaster-related • information and services • Federal agencies • Non-governmental organizations • Preparedness & recovery services • Secure • Authentication driven • Permission based • 128 bit encryption • Multiple tools & resources • Collaboration channel • Custom tools • Document repository

5. Disaster Management Interoperability Services (DMIS) 1000 user groups 50 states 67 real incidents 335 exercises Serving the Emergency Management Community • Core incident management tool set and shared services • Exchange of information across geographical and governmental • boundaries • Alerts, national maps, specific needs request, and • tactical information exchange

6. 32 54 9 10 20 15 85 38 5 32 2 3 17 9 5 7 34 11 11 10 19 19 97 18 1 1 70 10 15 7 1 4 8 2 4 5 9 5 2 27 38 11 12 24 5 8 18 20 2 46 34 50 Where is DMIS used? • American Samoa (AS) As of 11/23/04: • Total: 1000 User groups • 104 State/Regional User groups • (Coverage: 50 States) • 33 DHS & FEMA User groups • (Coverage: 8 FEMA Regional Offices) • Total: 142 Federal & National User groups • (Coverage: 20 Federal Agencies & Tribal) • - 22 NGO User Groups • 46 Vendors Participating in Interoperability = Currently executing state-wide roll-out = States with 10+ User Groups

7. Incident Management Standards Process Flow Practitioners identify, prioritize, and recommend standards for development Approved standards will be incorporated into DMIS and vendor products DHS/FEMA coordination activities Recognized standards making body(s) will publish standards DM facilitates draft standards with national practitioner groups, private industry; DHS supports trials Recognized standards making body(s) will review and approve standards Present draft standard to recognized standards making body(s)

8. Approach • Incident management data standards • Public standards • Facilitating, not producing • Practitioners define requirements and set priorities • DHS drafts standards based on above • Non Profit Consortium of Vendors implements standards and submits to: • Formal Standards Organizations for approval and publication • DHS grants used for incident management software must be for compliant systems • National standards driven by practioners, not Federal agencies

9. Where are we today? • Practitioner meetings held June 28 & November 3 to gather and update prioritized requirements • Common Alerting Protocol (CAP) approved by OASIS in April 2004 • Demonstrated Emergency Data Exchange Language (EDXL) “Message Header” standard on October 27, 2004 • Draft “Message Header” standard submitted to standards setting organization • Begin work on next EDXL standard: “Resource Management”