= !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

=== Real Need ===
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.

=== Value to the Humanitarian Community ===
1. Improve the current system of information sharing in disaster response among responding agencies
1. Act as an information sharing platform for the public and media on the humanitarian community’s response activities
1. Potential resource mobilization tool for joint agency projects or emergency relief activities

=== Similar solutions ===

||=Solution=||=Description=||=Responsible actors=||
||[http://riskinfo.lk/ riskinfo.lk] ||“A public platform for GIS data to support development in Sri Lanka” including OpenStreetMap data etc. Launched 21 December 2017 ||Disaster Management Centre (DMC) supported by the World Bank through the Global Facility for Disaster Risk Reduction (GFDRR) ||
||[http://www.dmc.gov.lk/index_english.htm dmc.gov.lk] ||Static, text-based website which hosts various statistics and information databases. Difficult to navigate. ||Disaster Management Centre (DMC) ||
||http://www.ndrsc.gov.lk/web/ ndrc.gov.lk] ||Similarly, organisational site like DMC. ||National Disaster Relief Services Centre (NDRSC)  ||

== Stakeholders ==
<Who will be the users of the solution?>
<Who else will be affected by this solution? eg. Developers, Users of Existing Functionality that may be changed?>
<How will stakeholders be affected?>
Tip: Engage these stakeholders in the development of your !BluePrint.

== User Stories ==
<http://en.wikipedia.org/wiki/User_story>
<A good User Story should answer the following questions:>
<* Who the user is>
<* What they want the solution to do for them?>
<* Why they want it to do that? (goal)>
<eg. A <type of user> wants the solution to <do something for them> so that <can achieve a goal>.>

== Requirements ==
<Group requirements in subsections, e.g.,, etc.>
<http://en.wikipedia.org/wiki/Requirements_analysis requirements>
<Identify different types of requirements:>
=== Functional ===
=== Non-functional ===
http://en.wikipedia.org/wiki/Non-functional_requirements
=== Interoperability ===
=== Standards ===
=== System Constraints ===

== Design ==
<Where relevant include alternative design options>
=== Data Model ===
(e.g. EER or class diagrams)
=== Workflows ===
<Diagrams or Pseudocode> 
=== Site Map ===
<for User Interface solutions>
=== Wireframes ===
<for User Interface solutions>
=== Technologies ===

== Current Implementation ==
<Leave open for a list of existing implementation of this solution in Sahana Eden:>
<*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 ==
<List of goals for your implementations which you (include your name/github repo/IRC handle) are currently working on>

== Future Extensions ==
<List of features which could be included, but are outside of the scope of this extension>

== Outstanding Questions ==
<Questions about the features or design that haven't been (and need to be) answered>

== References ==
<Links to external resources>

== Current Status ==

==== Available features ====

==== Missing features ====

==== Prototype ====

== Other ==
----
BluePrint