= !BluePrint: Sahana Relief and Rehabilitation (ShaRe) Hub = [[TOC]] [wiki:UserGuidelines/ShaRe#RequesterforReliefRehabilitation User Guidelines] == Introduction == The solution is a [https://www.humanitarianresponse.info/en/about-clusters/who-does-what Humanitarian Country Team] (HCT) '''relief and rehabilitation activities coordination platform'''. It would extends to the wider humanitarian community, government and the public. The main uses include: * Managing relief * requests - authorized users to report a request * suppliers (donors) - - commit supplies - dispatch (goods/services), - monitor the delivery & return of supplied (logistics) * Reporting * publish situational-reports and management summary reports * display of relief activities in list form, on a geographical map The real need for a solution was recognized during the onset of the 2017 Southwest Monsoon instigated flood and landslide events in Sri Lanka. The [https://lk.one.un.org/un-in-sri-lanka/un-resident-coordinators-office/ UN Resident Coordinators Office] (RCO) of Sri Lanka, supported by the UN Office for the Coordination of Humanitarian Affairs (OCHA) [http://www.unocha.org/roap Regional Office for Asia and the Pacific] (ROAP), developed a simple 3W (“Who does What Where”) template. 3W was: * simple and intended to capture the responding agencies activities and responding locations * reflected on a map of Sri Lanka as a visual aid. * eventually adapted into a 4W (“Who does What Where, and When”) * 4W was: * an enhancement to capture other details such as donors, responsible agencies and implementing partners. * exceeding the capacity of the RCO to conduct mapping of the 4W (i.e. only the raw data was released) * reliant on the manual regular distribution of the template, followed by manual “cleaning” of the data. The HCT in the Lessons Learned Action Plan of 2017, determined that the Sahana EDEN platform should be explored as an option to improve these methods. The ShaRe Hub would be developed as an Eden template that can be deployed to server other HCT and UN RCO teams in other countries. == Stakeholders == Tip: Engage these stakeholders in the development of your !BluePrint. == User Stories == <* Who the user is> <* What they want the solution to do for them?> <* Why they want it to do that? (goal)> wants the solution to so that .> == Requirements == === Functional === === Non-functional === http://en.wikipedia.org/wiki/Non-functional_requirements === Interoperability === === Standards === === System Constraints === == Design == === Data Model === (e.g. EER or class diagrams) === Workflows === === Site Map === === Wireframes === === Technologies === == Current Implementation == <*a brief description of the implementation (date/time, name, design options chosen)> <*a link to the code> <*list of deployments of the implementation> <*links to case studies> <*short analysis of achievements/problems> == Planned Implementation == == Future Extensions == == Outstanding Questions == == References == == Current Status == ==== Available features ==== ==== Missing features ==== ==== Prototype ==== == Other == ---- BluePrint