Version 11 (modified by Nuwan Waidyanatha, 6 years ago) ( diff )


BluePrint: Sahana Relief and Rehabilitation (ShaRe) Hub

User Guidelines


The solution is a 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

<What problem is this solution solving?> During the onset of the Southwest Monsoon in 2017, the UN Resident Coordinators Office (RCO) supported by the UN Office for the Coordination of Humanitarian Affairs (OCHA) Regional Office for Asia and the Pacific (ROAP) developed a simple 3W (“Who does What Where”) template. This 3W was simple and intended to capture the responding agencies activities and responding locations to the floods and landslides that had occured. This was then reflected on a map of Sri Lanka as a visual aid.

The 3W was eventually adapted into a 4W (“Who does What Where, and When”) and also began to detail other details such as donors, responsible agencies and implementing partners. This exceeded the capacity of the RCO to conduct mapping of the 4W, so only the raw data was released. Further, the 4W system was 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.

<How will this solution add value to Sahana?> <Name any similar existing solutions>


<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

<> <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>.>


<Group requirements in subsections, e.g. etc.> < requirements> <Identify different types of requirements:>





System Constraints


<Where relevant include alternative design options>

Data Model

(e.g. EER or class diagrams)


<Diagrams or Pseudocode>

Site Map

<for User Interface solutions>


<for User Interface solutions>


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>


<Links to external resources>

Current Status

Available features

Missing features




Attachments (3)

Download all attachments as: .zip

Note: See TracWiki for help on using the wiki.