Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Sahana & Disaster Management Software: Past, Present & Future


Published on

Talk by Mark Prutsalis at the Sahana Conference 2009, Colombo. Sri Lanka. March 24-25 2009.

Published in: Technology, Business

Sahana & Disaster Management Software: Past, Present & Future

  1. 1. Sahana & Disaster Management Software: Past, Present & Future What can we learn from the experience of professional disaster managers and humanitarian aid workers to build better humanitarian FOSS software Mark Prutsalis President, Globaliist Inc. Sahana PMC March 25, 2009
  2. 2. <ul><li>Employers, Customers, Clients </li></ul><ul><li>NGOs </li></ul><ul><ul><li>Refugees International </li></ul></ul><ul><ul><li>Rocky Mountain Institute </li></ul></ul><ul><ul><li>World Vision International </li></ul></ul><ul><li>UN Agencies </li></ul><ul><ul><li>UNHCR </li></ul></ul><ul><ul><li>UNICEF </li></ul></ul><ul><ul><li>UNJLC </li></ul></ul><ul><li>US Government </li></ul><ul><ul><li>Center of Excellence in Disaster Management & Humanitarian Assistance </li></ul></ul><ul><ul><li>US Navy’s Third Fleet </li></ul></ul><ul><ul><li>DARPA </li></ul></ul><ul><li>Private Sector </li></ul><ul><ul><li>Crisis Response Team (IBM) </li></ul></ul><ul><ul><li>IT Crisis Services </li></ul></ul><ul><li>On Site Emergency Management Experience </li></ul><ul><li>Cambodia 1993 (elections) </li></ul><ul><li>Bosnia & Herzegovina 1993-94 (conflict) </li></ul><ul><li>Tanzania 1994 (refugees) </li></ul><ul><li>Uganda, Kenya, Rwanda, Burundi, Zaire 1994-96 (Great Lakes region refugee emergency & civil conflict) </li></ul><ul><li>Kenya, Southern Sudan, 1997 (OLS) </li></ul><ul><li>Mali 1997 (emergency response team training) </li></ul><ul><li>Central America 1998 (Hurricane Mitch) </li></ul><ul><li>East Timor 1999 (conflict) </li></ul><ul><li>Ecuador 1999 (volcano) </li></ul><ul><li>Turkey 1999 (earthquake) </li></ul><ul><li>Taiwan 2000 (emergency planning) </li></ul><ul><li>Gujarat, India 2000 (earthquake) </li></ul><ul><li>New York 2001 (9/11) </li></ul><ul><li>India, Sri Lanka, Indonesia 2004-05 (earthquake, tsunami) </li></ul><ul><li>Kashmir, Pakistan 2005 (earthquake) </li></ul><ul><li>City of New York 2004-08 (emergency planning) </li></ul>
  3. 3. Today’s Talk <ul><li>Part 1 : History of Disaster Management Software </li></ul><ul><ul><li>Early efforts (1993-2004) </li></ul></ul><ul><ul><li>Indian Ocean tsunami (2004-05) </li></ul></ul><ul><ul><li>Post-tsunami experience (2005-09) </li></ul></ul><ul><li>Part 2 : the Present State of Sahana </li></ul><ul><ul><li>Challenges of moving Sahana into a public stable 1.0 release </li></ul></ul><ul><ul><li>What 1.0 means for Sahana and the humanitarian community </li></ul></ul><ul><li>Part 3 : the Future of Disaster Management Software </li></ul><ul><ul><li>Mission critical functions that have yet to be developed: logistics </li></ul></ul>
  4. 4. PART ONE <ul><li>Personal History with </li></ul><ul><li>Disaster Management Software </li></ul>
  5. 5. Tanzania 1994 <ul><li>Estimated 200,000+ Rwandan Refugees enter Tanzania in a single day. </li></ul>
  6. 13. Turkey 1994 <ul><li>Kocaeli Earthquake and resulting influx of international donations of drugs and medical supplies cripple Turkish Ministry of Health’s ability to respond. </li></ul>
  7. 21. Organizing the Warehouse
  8. 26. Deploying the System
  9. 33. Commodity Tracking System Architecture for Turkish Ministry of Health
  10. 36. <ul><li>Affected Population: 16,972,606 </li></ul><ul><li>Human Fatalities: 30,000 + </li></ul><ul><li>Injured Persons: 68,478 </li></ul><ul><li>Destroyed Houses: 228,906 </li></ul><ul><li>Damaged Buildings 397,538 </li></ul>Bhuj, India January, 2001 Gujarat Earthquake M7.9
  11. 37. The Mission: Logistics Management
  12. 38. Gujarat Earthquake Relief: Receipt, Packaging and Distribution of Supplies
  13. 39. Deploying CommTrack System: Ahmadabad, India, 7 February 2000
  14. 43. Cell phone towers still operating <ul><li>Bachau, India, </li></ul><ul><li>5 February 2000 </li></ul>
  15. 44. Bhuj, India
  16. 49. Bhuj Relief Warehouse
  17. 53. Our Pony Express
  18. 54. Anjar, India 13 February 2000
  19. 55. Semankyali Checkpoint, India
  20. 57. Adasar Checkpoint, India
  21. 62. The Indian Ocean Tsunami
  22. 63. India: Sunil Raghavan
  23. 64. India: Tsunami Management System: Victim Tracking, Logistics, Information System Open source, Linux Operating System, MYSQL Database
  24. 65. India: Warehouse Management
  25. 66. India: Logistics System
  26. 67. India: Information System
  27. 68. Sri Lanka
  28. 70. Person/Victim Registration System
  29. 71. Camp/Shelter Registration System
  30. 72. Request/Assistance Management System
  31. 73. Organization Registration System
  32. 75. Students configuring Sahana in Colombo
  33. 76. Sahana Training Provided by Crisis Response Team’s Dr. Tom Phelan
  34. 77. Indonesia <ul><li>Banda Aceh </li></ul><ul><li>7 Days after tsunami </li></ul>
  35. 78. SIMBA <ul><li>Sistem Informasi Manajemen Bencana Aceh (SIMBA) </li></ul><ul><li>Information Management System for Aceh Disaster </li></ul>
  36. 79. SIMBA First create a new POSKO, “double-click” on ‘Create new Posko’ Requirements meeting with Government Programming Team in Aceh
  37. 80. Secure Wireless Infrastructure System (SWIS) Installed in Banda Aceh and Teunom Crisis Response Team installs and adjusts wireless network communications hardware in Teunom camp Setting up SIMBA in Teunom SWIS was used in Indonesia to enter and transmit IDP (Internally Displaced Person) information. Previously, these records were hand written and sent by helicopter from Teunom to Banda Aceh .
  38. 81. Hurricane Katrina, 2005
  39. 82. Challenge: Nearly 50 Missing and Located Persons Registries (examples) <ul><li> </li></ul><ul><li> </li></ul><ul><li> </li></ul><ul><li> </li></ul><ul><li> </li></ul><ul><li> </li></ul><ul><li> </li></ul><ul><li> </li></ul><ul><li> </li></ul><ul><li> </li></ul><ul><li> </li></ul><ul><li> </li></ul><ul><li> </li></ul><ul><li> </li></ul><ul><li> </li></ul><ul><li> </li></ul><ul><li> </li></ul><ul><li> </li></ul><ul><li> </li></ul><ul><li> </li></ul><ul><li> </li></ul><ul><li> </li></ul><ul><li> </li></ul><ul><li> </li></ul><ul><li> </li></ul><ul><li> </li></ul><ul><li> </li></ul><ul><li> </li></ul>* Based on a full compilation as of Sept 2, 2005 at 8:30pm (list available)
  40. 83. Challenge: Duplicate Reporting 3595 registrations in just the letter “B”. Over 34,000 in total.
  41. 84. Recommendations <ul><li>Information Sharing MOUs </li></ul><ul><li>Agreed data collection standards and formats </li></ul><ul><li>Identifying duplicate records & false records </li></ul><ul><li>Only one official Missing Persons site per disaster – one database </li></ul><ul><li>Sahana can fill this role </li></ul>
  42. 85. NYC Sahana Intake Based on Official Paper Forms
  43. 86. Kashmir Earthquake 2005
  44. 87. Kashmir Earthquake 2005 Maj. General Khalid Nawaz, GOC Muzaffarabad (GOC 12 DIV)
  45. 88. Balakot, Pakistan <ul><li>60% loss of life </li></ul>
  46. 92. NYC Sahana Branch – 2007+
  47. 93. NYC Branch Staff Registration System
  48. 94. NYC Branch Site System
  49. 95. NYC Branch – GIS Integration
  50. 96. NYC Branch Shelteree Registration System Reporting
  51. 97. NYC Branch SANDS System
  52. 98. NYC Branch SANDS: Assigning Staff to Activated Sites
  53. 99. NYC Branch SANDS: Staff Management
  54. 100. NYC Branch SANDS: Tracking and Updating Staff Status
  55. 101. NYC Branch SANDS: Situation Awareness of Staffing
  56. 102. NYC Sahana Branch: Next Steps <ul><li>More automation of business processes </li></ul><ul><li>More situational awareness reports (dashboard) </li></ul><ul><li>Logistics management for shelters and community distribution points </li></ul><ul><li>Development, support & maintenance from City University of New York (CUNY) </li></ul><ul><li>Merging NYC Branch features back into Sahana trunk </li></ul>
  57. 103. LESSONS LEARNED <ul><li>Fully functional offline / standalone </li></ul><ul><li>Development priorities driven by emergency/disaster management domain experts </li></ul><ul><li>Stable, reliable, easy to install & run on Windows/IE </li></ul>
  58. 104. PART TWO <ul><li>The Present State of Sahana: </li></ul><ul><li>Whither Sahana 1.0? </li></ul>
  59. 105. <ul><li>“ Sahana is not being utilized in Aus [Australia] at this time for fire evacuee and refugee management due to several fundamental considerations: </li></ul><ul><li>  </li></ul><ul><li>o Sahana is still in pre-release and thereby not demonstrably robust (hopefully rectified when Sahana 1.0 is released) </li></ul><ul><li>o Sahana is not easily installed on Microsoft Windows servers and notebooks </li></ul><ul><li>o Sahana is currently considered to be overly complex in terms of features and the complexities of deployment methodologies….” </li></ul><ul><li>- e-mail from Don Cameron, Sahana PMC member, 3/16/09 </li></ul>
  60. 106. A call for Sahana 1.0 this year <ul><li>Open Source = constant innovation, results in betas – “release often” </li></ul><ul><li>At odds with need for stable & reliable code that emergency managers can depend on to save lives </li></ul><ul><li>If Sahana wants to be “the disaster management software” it has to be stable & reliable. </li></ul>
  61. 107. Whither Sahana 1.0?
  62. 108. Sahana 1.0 Release Plan <ul><li>Take a little longer than normal release schedule. </li></ul><ul><li>Clean up code </li></ul><ul><li>Fix all outstanding bugs </li></ul><ul><li>Rigorous bug test & QA </li></ul><ul><li>Professional packaging with installation/configuration scripts for windows, Linux, MAC OSX, Solaris, portable applets, etc. </li></ul><ul><li>Professional documentation for installation & end-users. </li></ul>
  63. 109. We need your help <ul><li>We need developers to support the 1.0 release. </li></ul><ul><li>Activities & tasks are documents on wiki: </li></ul><ul><ul><li> </li></ul></ul><ul><li>It is not sexy work, but fulfilling. You will be part of team that will make Sahana 1.0 a reality. </li></ul><ul><li>Get involved. On Sahana-Maindev; IRC #sahana </li></ul>
  64. 110. Sahana 1.0 launches Sahana into Stratosphere <ul><li>No, it won’t be in Python. </li></ul><ul><li>No, it won’t have all the bells and whistles planned for with the 0.7 and 0.8 releases and GSoC 2009 projects. </li></ul><ul><li>BUT – when next major sudden onset disaster strikes, no one will hesitate to recommend Sahana’s deployment. </li></ul>
  65. 111. PART THREE <ul><li>The Future of Sahana and Disaster Management Software </li></ul>
  66. 112. Sahana needs a Logistics Management System <ul><li>Emergency experience demonstrates need </li></ul><ul><li>No disaster management system is complete without it </li></ul><ul><li>“ Logistics efforts can account up to 80% of disaster relief spending and thus, efficient and effective logistics activities become crucial for successful humanitarian operations .” – ISCRAM 2009 </li></ul>
  67. 113. Logistics <ul><li>Basic Principle: Get things and people to right place, at right time, for right price. </li></ul><ul><li>Must organize: </li></ul><ul><ul><li>Procurement </li></ul></ul><ul><ul><li>Transport </li></ul></ul><ul><ul><li>Warehousing </li></ul></ul><ul><ul><li>Distribution </li></ul></ul>
  68. 114. Design for Sahana Logistics (1)
  69. 115. Design for Sahana Logistics (2)
  70. 116. Next Steps for Sahana Logistics <ul><li>GSoC 2009 Project for NGO Warehouse Management </li></ul><ul><li>Again, we need your help! </li></ul><ul><li>Post Sahana 1.0, Sahana logistics should be next major voluntary effort </li></ul>
  71. 117. THANK YOU <ul><li>Mark Prutsalis </li></ul><ul><li>President, Gl  bal iist Inc. </li></ul><ul><li>Sahana PMC </li></ul><ul><li> </li></ul><ul><li> </li></ul><ul><li>[email_address] </li></ul><ul><li>Skype: mark.prutsalis </li></ul><ul><li>IRC #sahana: mprutsalis </li></ul>