Sahana overview and history of sahana-aaai 2015

Click here to load reader

Embed Size (px)

Transcript of Sahana overview and history of sahana-aaai 2015

PowerPoint Presentation

Overview &History of Sahana

AAAI Spring Symposium 2015March 23-25, 2015Stanford University, Palo Alto, CA

Chamindra de SilvaDirector, Sahana Foundation | Director, Virtusa Corporation

Ramindu DeshapriyaMember, Sahana Foundation | Mphil Student University of Kelaniya

AgendaSahana Intro (20 mins) Chamindra de SilvaAn Overview of SahanaA History and Evolution of Sahana (SI -> SIII AKA Eden)Deployment Examples and Case StudiesSahana-Eden Demo (30 mins) Ramindu DeshapriyaHow to setup SahanaSahana Eden FeaturesBuilding a new moduleHow to create a new (structured) data modelSahanas support for Linked DataImport and Export optionsOther customization Options & API

AgendaThe Sahana Project:What is it in a nutshell?Free and Open SourceGlobal Community Built Disaster Management RAD PlatformFoundation Mission To save lives by providing information management solutions that enable organizations and communities to better prepare for and respond to disasters

3At the end of this why Open Source is key, gl

The Historic Trigger: 2004 Indian Ocean Earthquake & TsunamiAt least 226,000 deadUp to 5 million people lost their homes, or access to food and water1 million people left without a means to make a livingAt least $7.5 billion in the cost of damagesFacts and Figures: Asian Tsunami DisasterNew Scientist, 20 January 2005

Government Relief Local Authorities, Police, Army, Fire fighters, + Authorized coord+ Well trained+ Accountable +/- Big picture relief (e.g. national security)- Procedures create bottlenecks- Overloaded

Local ReliefSpontaneous volunteers, corporate village communities, friends and family+ first responders+ lot of capacity+ instant aid- not trained- focus unknown- not accountableUN, NGOsRed Cross, OCHA, CARE, WHO, Sarvodaya, etc+ focused on people+ trusted to accept aid+/- less well trained+ accountable- Donor driven- narrow focus / fragmented

Victims Effective Collaboration and Coordination!ReliefDisasters CoordinationRapid Info Sharing and Collaboration Needed10s of Orgs100s of Orgs1000s 1 Mill5Sahana Relief in Sinhalese Rapidly custom build for SL Gov to handle TsunamiSahanaSoftwareRapidly Builds Tsunami 2004

CNO Urgent RequirementsSri LankanIT CommunitySri Lankan IT Community = LSF/LKLUG + SL IT Industry + AcademiaSahana Phase I6Sahana first deployed for Sri Lanka tsunami response for SLGov

Sahana Phase I Independent Hazard Info. Center

8The First CommunityWe just wanted to help our countrymenWe used our skills to provide a toolOperational model - Chaos400 IT volunteers1st week 24hr developmentMajor releases almost dailyApplicationsMissing Person Registry, Organization Registry, Request management System, Camp Registry9Tracking Missing People / Casualties

Shared Bulletin Board of lost / foundComputer based search heuristicsTracking Family unitsAnalyzing networks of connectionsThe Missing People Registry helps track and find missing, people10Who is doing What, Where & When?

Registry of operating relief organizationsCoverage of ServicesSelf-Allocation and ReportingContact InformationThe Organization Registry helps maintain data (contact, services, region, etc) of organizations groups and volunteers working in the disaster11Matching Aid to Ground Realities

Estimating NeedsMatching Aid to Ground NeedsInventories/CatalogQuantitiesExpiration datesRe-order levelsTracking AllocationThe Request Management System tracks all requests and helps match pledges for support, aid and supplies to fullfilment12Lessons: Large Scale Disaster Management Systems were rare!Surprisingly no one had built such a system before! (we had asked FEMA, IBM)Identified many of the common coordination problems of a large scale disaster disaster and formulated modules to address themBUTNEVER build a disaster management system from scratch during a disaster again!!13Learned how I.T. Fail in a disasterComms can be saturated or not accessibleSystems have to be able to work disconnectedUser familiarity can be lowSystems has to be as intuitive as possibleData centers can get impactedSystems have to be resilient (simple), mobile and self-sufficientFunctionality can be inadequate System has to be quickly customizable14Sahana Generic Platform Rebuild A generic disaster management platformLSF Team(+ SIDA)SahanaSoftware A Global Need (2005)

TsunamiRequirementsLSF Team = FOSS Geeks on FellowshipsBuilds and DonatesSahana Phase II15Slightly different design goals than what we were used to at the timeTypical Enterprise Software Disaster Management AppNetworkLAN/WAN connected high bandwidth expectedIntermittently connected, low bandwidth, most often WIFIUser InterfaceHighly interactive, Chatty AJAX lookups, graphics rich and engagingLow throughput, Simple, highly intuitive, low size graphics if anyDeploymentDesigned for one particular deployment environment in Cloud or Data CenterDesigned for any available environment from cloud, server, to portable appDependenciesDependent on 3rd party internal and external web servicesMinimize dependencies, and potential point of failure, caching when neededDevelopmentWell typed, compiled, security manager, clear interface definitionsEasy to pickup and dynamically modifiable scripting languageCollaborative Virtual Helpdesk

zone of trust

(legislation)17Peer 2 Peer Pony Express

18Started to look at portable

USB Disk / LaptopMobileOLPC+ Synchronization19

Collaborative Situation Mapping

Collaborative Map ofHazards / IncidentsShelters (IDPs)(field) HospitalsOrganizationsRespondersStoresetcThe Shelter Registry helps track data on all shelters setup following the Disaster20Why does Open Source make this better?This was a natural alignment to Humanitrian ValuesFreely Available to deployNo discrimination on access (Red Cross CC #2)Ability to leave technology behind (RC CC #6)Rapid customization to actual needs with code L10N and integration (RC CC #5)Building local capacities & self-reliance (RC CC #6)Open system => Transparent and trustworthyBetter acceptance than foreign proprietary systemsCountries/NGOs can collaborate to developGet the best minds from the world to participate in building the softwareThis should be a global public good Build on each others work by including it in projectCalled Humanitarian-FOSS or H-FOSS21Lessons: Open Source in this domain had tremendous acceptanceThe open source community coupled with the humanitarian community sprit provided a strong contributor motivationSoftware Engineers without BoardersAcceptance of an Open Source Disaster Management system and HFOSS was tremendous(UNDP IOSN, ISCRAM, AsiaOSS, Govs)Integration and interop can be achieved by source code empowerment22

LSF + IBM + Community2004 - Indian Ocean Earthquake & Tsunami2005 - Pakistan - Kashmir Earthquake2005 - Philippine - Landslides2006 - Indonesia - Yogjakarta Earthquake,2007 - Peru - Ica Earthquake2007 - Bangladesh - Cyclone Sidr2008 - China - Chengdu-Sitzuan Earthquake2008 - Myanmar - Cyclone Nargis2008 - India - Bihar Flooding

Sahana Open Source Phase Global Open Source Incubation PhaseLSF Team +Global CommunitySahanaSoftwareBuilds + RefinesAttracts + GrowsDisaster Incident

Urgent RequirementsAttracts24The importance of CommunityThe system is nothing without communityExpand the community to as many organizations as you can trust with the dataMore capacity builds more resilianceCreates pre-existing relationships and trustWhich a software takes to another level of efficiencyUse MoUs if needed Don't forget there is a global community to help as well25The Community Spreads (2007)An Open Global Community (300+)

26The 4 Sub-Communities of SahanaH-FOSSFree & Open SourceCommunityHumanitarianCommunity(NGOs)EmergencyManagement(Gov, UN)AcademicResearchCommunity27Different Perspectives of the elephantSahana became a melting pot of innovationSAHANACool Open SourceDevelopmentPlatform!Grass Roots: By the Communityfor the CommunityRapidly CustomizableEM System A great CrisisResearch Platform28A Community Support ExampleMultiple local groups reach out to Sahana Call out made in Sahana communityOne initiative progresses furtherL10N / Promotion, QA, DeploymentIBM-China for Chendu Gov and then Police (China)24x7 Technical SupportLSF (SL), Trinity College (US), Community IndividualsFunds and SponsorshipIBM-Foundation (US,China)40+ Families reunited within first few days29A Community Response Example

30Lessons: CommunityThe diversity of our community both by geography and role created a tremendous melting pot of best practicesWe had not perfected the best modelApache by developer for developer was a good baseline but it was not the right model for usWe needed a model that supported By developer, for user in ultimate benefit of victimRespect the meritocracy of contribution and the community will growWhen we did not respect the meritocracy we lost community

31

LSF + IBM + Community2004 - Indian Ocean Earthquake & Tsunami2005 - Pakistan - Kashmir Earthquake2005 - Philippine - Landslides2006 - Indonesia - Yogjakarta Earthquake,2007 - Peru - Ica Earthquake2007 - Bangladesh - Cyclone Sidr2008 - China - Chengdu-Sitzuan Earthquake2008 - Myanmar - Cyclone Nargis2008 - India - Bihar Flooding

We received a lot of endorsementsNew Free Software Foundation (FSF) award for Social Benefit won and inspired by SahanaSourceforge Project of the Month, June 2006Software 2006, CA USA Good Samaritan AwardOne of the top 10 Open Source Project to keep an eye on Network World articleRecognized by forums such as:US WSIS, ISCRAM, UNDP IOSN, StrongAngel, AsiaOSS Symposium, Emergency Communications Asia33Sahana is not just Software Global Community Incubation PhaseLSF Team +Global CommunitySahanaSoftwareBuilds + RefinesGrowsDisaster Incident