Situation Awareness with IT for Regional Disaster Mangement Workshop


Published on

Regional Situation Awareness Module that I presented for the regional disaster management workshop sponsored by the British High Commission

Published in: Technology
  • Be the first to comment

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide
  • Information is powr
  • Situation Awareness with IT for Regional Disaster Mangement Workshop

    1. 1. Disaster Situation Awareness with Information Technology Chamindra de Silva SAHANA, Director and PMC Member W3C EIIF XG Co-Chair Virtusa, Technology Strategist
    2. 2. My Background <ul><li>12 Years of Experience building software </li><ul><li>Export and Local </li></ul><li>How did I get into disaster management? </li><ul><li>Tsunami: One of the IT industry volunteers
    3. 3. Sahana software tool for the CNO </li></ul><li>Later we embodied this into a free system </li><ul><li>A public good with a global community
    4. 4. Deployed for governments of Pakistan, Philippines, Peru, Bangladesh, China, US (New York, Galveston) and again in SL </li></ul></ul>
    5. 5. Agenda <ul><li>What is Situation Awareness? </li><ul><li>The problem of Situation Awareness in a Large Scale Disaster </li></ul><li>How IT can help and how it can fail?
    6. 6. Useful applications of IT for disaster management
    7. 7. Important considerations in applying IT
    8. 8. Demo Sahana </li></ul>
    9. 9. Situation Awareness Defn: “ Perception of the environment critical to decision-makers in complex and dynamic situations” <ul><ul><li>Studies show, lack of SA has been identified as one of the primary factors in accidents attributed to human error (Hartel, Smith, & Prince, 1991; Merket, Bergondy, & Cuevas-Mesa, 1997; Nullmeyer, Stella, Montijo, & Harden, 2005)
    10. 10. Making the best educated guess is inevitable!
    11. 11. Important especially in high information flow , high consequential impact domains (lives at stake) </li><ul><li>Air Traffic Control, Military Command and Control, Emergency Response, Disaster Management </li></ul></ul></ul>
    12. 12. Levels of Situation Awareness Current State of Situation Level 1 Perception of Elements In Current Situation Level 2 Comprehension of Current Situation Level 3 Projection of Future States Quality of Information Decision Information Action
    13. 13. SA in Emergency Management Well defined Response Process Well defined Information Flows Well Trained Responders e.g. Traffic Accident Building Fire Bus Bomb Blast Information Information Situation Awareness Act Decide
    14. 14. Disaster => Unexpected info Sources <ul><li>Government & Emergency Services relief capacity has been exceeded or crippled
    15. 15. To match relief capacity boundary of response effort extends to other groups (Other Gov, Civil Society, Foreign Aid, UN)
    16. 16. Core Decision Makers need to consult a wider group for better situation awareness
    17. 17. Information has to be gathered from non-traditional “uninitiated” sources for better Situation Awareness </li></ul>
    18. 18. Disasters Coordination Large Scale (like Tsunami) 10s of Orgs 100s of Orgs 1000s – 1 Mill Government Relief Government Ministries, Police, Army, Fire fighters, + Authorized coord + Well trained + Accountable +/- Big picture relief (e.g. national security) - Procedures create bottlenecks - Overloaded Local Relief Spontaneous volunteers, corporate village communities, friends and family + first responders + lot of capacity + instant aid - not trained - focus unknown - not accountable UN, NGOs Red Cross, OCHA, CARE, WHO, Sarvodaya, etc + focused on people + trusted to accept aid +/- less well trained + accountable - Donor driven - narrow focus / fragmented - sometimes competing Victims Effective Collaboration and Coordination! Relief
    19. 19. SA in Disaster Management Multiple Disparate Information Sources Information Overload Large delta to reality Diverse Responders Relief workers, Volunteers Multiple Parallel independent Processes Trust? Clarity Repetition Priority? Information Information Situation Awareness?? Act Information Information Information Decide
    20. 20. Levels of Situation Awareness Current State of Situation Level 1 Perception of Elements In Current Situation Level 2 Comprehension of Current Situation Level 3 Projection of Future States Quality of Information Decision Information Action
    21. 21. Typical Problems Responders have work on.. <ul><li>Search And Rescue
    22. 22. Evacuation
    23. 23. Setting up Shelters
    24. 24. Effective Distribution of Aid
    25. 25. Management of Donars and Donations </li></ul><ul><li>Tracing Missing People
    26. 26. Protecting Children
    27. 27. Trauma Counseling
    28. 28. Assuring Security of Affected Areas
    29. 29. Rehabilitation </li></ul>Live saving decisions need to be made very fast ! The best decisions are the most informed ones
    30. 30. The Manual Approach.. <ul><li>100-10,000s of paper forms </li><ul><li>That have to be managed
    31. 31. Inconsistent Terminology
    32. 32. Multiple orgs, same common data </li></ul><li>Coordination Complexity </li><ul><li>Telephone: O(N 2 ) </li></ul><li>Manual Reporting
    33. 33. Delayed Situation Awareness ! </li></ul>16 120 8 5 10 28
    34. 34. How Can I.T. Help? <ul><li>Scalable management of information </li><ul><li>Increase manageability of millions of records </li></ul><li>Consistent Propogation of Data </li><ul><li>Information is less prone to error on sharing </li></ul><li>Share data more effectively </li><ul><li>Accessibility of information without bottlenecks </li></ul><li>Live Situation Awareness </li><ul><li>Latest analysis, maps and reports automatically calculated </li></ul></ul>
    35. 35. Problem Areas IT Helps Manage <ul><ul><li>Tracing Missing People
    36. 36. Coordinating Who is doing What Where?
    37. 37. Tracking Displaced Families
    38. 38. Collaborative and live Incident Mapping
    39. 39. Aid Logistics Management
    40. 40. Scalable Alerting
    41. 41. Data Collation , Calculation and Reporting
    42. 42. Automated Messaging to the Public </li></ul></ul>“ Every Second Counts” => IT Maximizes Efficiency & Effectiveness
    43. 43. Who is doing What , Where & When ? <ul><li>Registry of operating relief organizations
    44. 44. Coverage of Services
    45. 45. Self-Allocation and Reporting
    46. 46. Contact Information </li></ul>The Organization Registry helps maintain data (contact, services, region, etc) of organizations groups and volunteers working in the disaster
    47. 47. Tracking Missing People / Casualties <ul><li>Shared Bulletin Board of lost / found
    48. 48. Computer based search heuristics
    49. 49. Tracking Displaced Family units
    50. 50. Analyzing networks of connections </li></ul>The Missing People Registry helps track and find missing, people
    51. 51. Matching Aid to Ground Realities <ul><li>Estimating Needs
    52. 52. Matching Aid to Ground Needs
    53. 53. Inventories/Catalog
    54. 54. Quantities
    55. 55. Expiration dates
    56. 56. Re-order levels
    57. 57. Tracking Allocation </li></ul>The Request Management System tracks all requests and helps match pledges for support, aid and supplies to fullfilment
    58. 58. Collaborative Situation Mapping Collaborative Map of <ul><li>Hazards / Incidents
    59. 59. Shelters (IDPs)
    60. 60. (field) Hospitals
    61. 61. Organizations
    62. 62. Responders
    63. 63. Stores
    64. 64. etc </li></ul>The Shelter Registry helps track data on all shelters setup following the Disaster
    65. 65. Mobility of Information (Field Access) USB Disk / Laptop PDA OLPC + Synchronization The Messaging Module sends and recieves SMS / emails from responders
    66. 66. Other Applications <ul><li>Disaster Victim (Displaced Family) Module </li><ul><li>Tracking displaced people </li></ul><li>Volunteer Management Module </li><ul><li>Handling volunteers, skills, availability, staff </li></ul><li>Inventory Management </li><ul><li>Handling supplies, expiry dates, allocations </li></ul><li>Evacuation Management </li><ul><li>Efficient process for registering and evacuating people </li></ul><li>Bio-Surveillance </li><ul><li>Identify patterns of incidents for early pandemic containment </li></ul></ul>
    67. 67. How Can I.T. Fail in a disaster <ul><li>Comms can be saturated or not accessible </li><ul><li>Systems have to be able to work disconnected </li></ul><li>User familiarity can be low </li><ul><li>Systems has to be as intuitive as possible </li></ul><li>Data centers can get impacted </li><ul><li>Systems have to be resilient ( simple ), mobile and self-sufficient </li></ul><li>Functionality can be inadequate </li><ul><li>System has to be quickly customizable </li></ul><li>Electricity Can be Down </li></ul>
    68. 68. Designing for disaster management
    69. 69. “Tactical” Hazard Info. Center (HIC)
    70. 70. Collaborative Virtual Helpdesk zone of trust (legislation)
    71. 71. Data Sharing Conundrum <ul><li>The problem of trust </li><ul><li>The data is sensitive people data
    72. 72. Data Validity or Accountability for data
    73. 73. Legislation and pre-existing MoUs </li></ul><li>Access vs Security </li><ul><li>Data needs to be protected from those you do not trust, yet shared freely from those you do
    74. 74. To much security creates bottlenecks in disasters </li></ul><li>Data Owner decides </li></ul>
    75. 75. If Sharing has Constraints <ul><li>Data Sensitivity Levels </li></ul><ul><li>Authentication, Authorization, Access </li></ul>Data Sensitivity
    76. 76. Peer 2 Peer Pony Express
    77. 77. RAD and Ownership <ul><li>Need a Rapidly Customizable tool </li><ul><li>Country Specific
    78. 78. Situation Specific
    79. 79. Organization Specific
    80. 80. I12N, L10N </li></ul><li>Key is Ownership </li><ul><li>Gov needs control and transparency of system accepted
    81. 81. Ownership of data </li></ul></ul>
    82. 82. Few Lessons Learned on Deployment <ul><li>Pre-deployment is best! </li><ul><li>Otherwise L10N and customization on the fly </li></ul><li>Encourage data centralization and sharing </li><ul><li>promote integration to trusted groups </li></ul></ul><ul><li>Get the system officially authorized </li><ul><li>Promoted through the central relief coordinating authority designated by the Government </li></ul></ul><ul><li>Build simple, flexible, resilient IT solutions </li></ul><ul><li>Securing the Perimeter vs Accessibility </li><ul><li>Solid ACLs and perimeter security is needed </li></ul></ul>
    83. 83. The Sahana Project Example <ul><li>What is it? </li><ul><li>A free portable web tool
    84. 84. Sub-applications designed to address th e common Disaster Management probs
    85. 85. A RAD platform </li></ul><li>Main Goals </li><ul><li>Bring Efficiencies to Disaster Coordination and Prompt Response
    86. 86. Facilitate the effective information exchange between a diverse groups of people (NGOs, Government, EM groups and victims)
    87. 87. Primary focus is to help victims </li></ul></ul>
    88. 88. I.T. Challenges handled by Sahana <ul><li>No or Low Budget for Disaster Coord. </li><ul><li>Zero license cost + works on old hardware </li></ul><li>Leaning curve of new users </li><ul><li>Sahana can be translated and has be designed to be as intuitive as possible </li></ul><li>Comms can be saturated or not accessible </li><ul><li>Sahana supports USB flash based exchange </li></ul><li>Data centers can get impacted </li><ul><li>Sahana can work both in mobile and centralize modes </li></ul></ul>
    89. 89. Deployment Overview <ul><li>Center for National Operations, Govt. of Sri Lanka, for Tsunami in Sri Lanka – 2005
    90. 90. NADRA, Govt. of Pakistan for Asian Quake in Pakistan – 2005
    91. 91. Govt. of Philippines, for Landslide disaster in Philippines– 2005
    92. 92. Pre-deployment in Sarvodaya, Sri Lanka
    93. 93. Yogjakarta Earthquake, Indonesia – 2006 </li></ul>
    94. 94. Sahana: Sri Lanka - CNO
    95. 95. Sahana: NADRA, Pakistan
    96. 96. Deployment Overview... <ul><li>Deployment for OEM, New York City Council, U.S.A, 2007
    97. 97. Deployment for office of the President, Peru, 2007
    98. 98. Deployment for Disaster Management Bureau, for Cyclone Sidr, Bangladesh, 2007
    99. 99. Used for Sarvodaya, Sri Lanka, 2008
    100. 100. Deployed and used in Myanmar, 2008
    101. 101. Deployed and used for Chengdu, China, 2008
    102. 102. Deployed and used for Bihar, India 2008 </li></ul>
    103. 103. Sahana: NYC Coastal, US
    104. 104. Sahana: Sarvodaya, Sri Lanka
    105. 105. How Sahana Differentiates Itself <ul><li>“Forged in the Fire”
    106. 106. Neutral A-Political Solution
    107. 107. Ownership and Empowerment of end-user (Government)
    108. 108. R.A.D Disaster Customization
    109. 109. Multi-Organizational (local) Support
    110. 110. Transparent and Open Community Development Process
    111. 111. Portable and Multiple Deployment Modes </li></ul>
    112. 112. What is Free and Open Source? <ul><li>Free as in Speech </li></ul><ul><ul><li>Freedom to access, run, modify and redistribute </li></ul></ul><ul><li>Open Source </li></ul><ul><ul><li>Is a set of principles and practices that promotes access to the design and production of goods and knowledge
    113. 113. Open APIs, Open Code (Blueprints), Open Standards </li></ul></ul><ul><li>Regulated by FOSS Licenses </li></ul><ul><ul><li>GPL (FSF), LPGL (FSF), Apache (ASF), BSD, CPL
    114. 114. Based on Copyright law, but spun on it's head (copyleft)
    115. 115. Rights are passed perpectually to users
    116. 116. GPL have been proven in court e.g. FSF vs BT </li></ul></ul><ul><li>Software is special </li></ul><ul><ul><li>Open Source software becomes a global public good </li></ul></ul>
    117. 117. How does Open Source Help Here? <ul><li>Low Cost </li><ul><li>Better accessibility to low IT budgets </li></ul><li>Freely Available to deploy </li><ul><li>No discrimination on access (Red Cross CC #2)
    118. 118. Ability to “leave technology behind” (RC CC #6) </li></ul><li>Rapid customization to actual needs w ith code </li><ul><li>L10N and integration
    119. 119. Building local capacities & self-reliance (RC CC #6) </li></ul><li>Open system => Transparent and trustworthy </li><ul><li>Better acceptance than “foreign” proprietary systems </li></ul><li>This should be a global public good </li><ul><li>Build on each others work by including it in project </li></ul></ul>Called Humanitarian-FOSS or H-FOSS
    120. 120. Now driven by a Global Community An Open Global Community (250+) <ul><ul><li>A diverse group of Emergency Management Practitioners, Humanitarian Workers, Academics and Programmers
    121. 121. LSF, IBM, Bluepoint, Respere, Google GSoC, ISCRAM, Universities: Uo Colombo (SL), Uo Moratuwa (SL), Trinity College (US), Uo Maryland (US), Tilburg University (Netherlands), NYC </li></ul></ul>
    122. 122. Quote from Philippines Response &quot;the NDCC and OCD value SAHANA's contribution to the relief and rehabilitation phases of the Southern Leyte landslides and recognize the tremendous boost to our preparedness for future disasters” “ while SAHANA cannot solve all the problems in a disaster, it is an excellent tool to create registries that can provide timely and reliable information on missing persons, donated goods and services, camp locations, and the like. It's technology that can help many people in a disaster. In fact, there is no greater innovation that matters more than that which saves lives. &quot; Avelino J. Cruz, Jr. Secretary of National Defense, Philippines
    123. 123. Thank You Further Questions? [email_address] Sahana Demo Sahana Website