wiki:BluePrint/ShaRe/UseCases

Use Cases

User Stories

During the Event

During an event (or disaster) following are the key workflows:

  1. Creating a new Event (e.g. SW Floods and Landslides 2017)
  2. Creating and Editing Needs
  3. Committing to Needs
  4. Entering and Editing 4W Updates
  5. Entering Situational Updates

Creating a new Event

An event (or disaster) is created in the platform is created in the system when the real-life situation has resulted in organisations reporting needs and response activities. This event allows needs/activities and other related information to be attributed to that particular event.

  1. The System Administrator (UN RCO)
    1. Creates a new event under the “More”>”Disasters” option
      1. Enters the title for the overall event
      2. Can select a “disaster type”
      3. Can provide a “start” date (onset)
      4. Can include the affected districts
      5. Saves the record
    2. Can enter “Situational Updates” to show the event on the Homepage

Creating and Editing Needs

In the HCT Phase, HCT members/Response agencies supply needs information through both periodic updates and in ad-hoc, as-required manner.

A need is a requirement (of items including food, clothing, skills, cash for work etc.) caused by an immediate or prolonged disaster.

In ShaRe Hub, each need is entered as a “row”. Each row is determined by the location (DS Division, GN Division), affected people and required response (“item”). The overall form as a whole reflects the “Group” of needs as determined by the location (Province and District).

The user organisation:

  1. Logs into the platform
  2. Selects “Needs” - “Create” from the menu bar
  3. Needs Entry form is opened:
    1. Enters the relevant information into the first fields (Disaster/Province/District/Date if different to date that the entry is occuring/Summary of Needs/Issue-Cause) note: Organisation is automatically filled with the user’s organisation as determined at registration.
    2. Enters one or more “needs entries” (one needs entry per row as defined by differences in location, number or type of affected people, and the required response (“items”)
    3. Completes any other relevant fields in the field (uploading of documents such as Letters of Request from authorities, showing government verification and contact details on the ground, delivery addresses)
    4. Saves the entry and is taken to the Needs Summary Table.
  4. To edit a need, the user:
    1. Opens the Needs Summary Table
    2. Selects “Edit” button in the column to the left of the appropriate row
    3. Selects the pencil icon on the right side to edit the row

Note: Only the organisation that created a need and the system administrator can edit a need.

Committing to Needs

Organisations can commit to deliver some or all of the items required, and/or reach some or all of the people affected within that overall need.

The user organisation:

  1. Logs into the platform
  2. Selects “Needs - View”, opening the Needs Summary Table
    1. The user selects the “Commit” button next to the desired need in the table
    2. Opens commitment form (activities/4W entry form) with the relevant information automatically copied from the needs form into the same fields in the commitment form:
      1. Disaster
    3. Location data
  3. Summary of Needs
    1. Issue/Cause
      1. The specific row of the need that is being committed to.
  1. The user selects the “edit” option on the right of the need information (row)
    1. The user changes the values of fields related to the response commitment they desire to make. These include:
      1. People Affected / Number
      2. Item Category / Item / Unit / Quantity
      3. Any other relevant information above or below the needs row (including contact details, addresses for delivery etc)
    2. Note:
      1. If the user commits to the total amount of people/items in the needs entry, then the need is “Fully committed”.
      2. If the user commits to a smaller amount of the people/items in the needs entry, then the need is “Partially committed”. Other users can commit to these needs to fill the gaps.
      3. Users can cancel their commitments if required, and the system will revise the figures accordingly.
      4. Users can mark the response as “complete” once the real-life need is met. For commitments with multiple organisations responding, this requires communication with the organisation that entered the need before marking the need as “complete”.

Entering and Editing 4W Activities

In the HCT Phase, HCT members/Response agencies supply information on activities through both periodic updates and in ad-hoc, as-required manner.

Entering 4W activities uses the same form as making a commitment; however, the 4W activity is entered without an associated “need” within the platform and so does not have pre-inputted data in the form.

The user organisation:

  1. Logs into the platform
  2. Selects “4W” - “Create” from the menu bar
  3. 4W Activity Entry form is opened:
    1. Enters the relevant information into the first fields (Disaster/Implementing Partners/Donors/Province/District/Date if different to date that the entry is occuring/Summary of Needs/Activities) note: Organisation is automatically filled with the user’s organisation as determined at registration.
    2. Enters one or more “Activity entries” (one activity entry per row as defined by differences in location, number or type of beneficiaries, and the response conducted)
    3. Completes any other relevant fields in the field (uploading of documents such as Letters of Request from authorities, contact details on the ground, delivery addresses)
    4. Saves the entry and is taken to the 4W Activities SummaryTable.
  4. To edit a 4W Activity, the user:
    1. Opens the 4W Activities Summary Table
    2. Selects “Edit” button in the column to the left of the appropriate row
    3. Selects the pencil icon on the right side to edit the row

Note: Only the organisation that created an activity and the system administrator can edit a need.

Entering Situational Update

RCO to update

Before the Disaster

Registering an HCT Organization

  1. Registering (creating) a user profile
  2. Registering an organisation

Registering (creating) a user profile

The new user:

  1. Opens the ShaReHub Platform in their browser
  2. Clicks on “Register” on the top-right of the page
  3. Completes the required fields (First Name/Last Name/Email/Password/Language/Organisation/Register as staff or volunteer
  4. Selects “Register” button at bottom of the page
  5. The user is then taken to the homepage, from which they can log-in.

Note: If the user’s organisation does not have a profile created in ShaRe Hub, the user must contact the administrator (humanitarian.lk@one.un.org) to have the organisation profile created.

Note: The user will not immediately have user permissions and must have these approved by the system administrator (humanitarian.lk@one.un.org).

Note: The “Profile” section consists of 13 tabs for the user to complete, containing information on qualifications, skills, contact details and other areas. The area is not compulsory to complete for platform use, but allows for users to register further information that may help in mobilising and coordinating response.

Registering an Organisation

Note: The general practice is the same for all users. However, this guidance has been written considering the initial user group of HCT agencies.

The new user:

  1. Logs into the ShaRe Hub

RCO TO COMPLETE

Use Case Diagrams

To refresh on the actors refer to the section on Stakeholders.

Import 4W updates (HCT Orgs)

  1. A single form can present features to:
    1. download a 4W sheet with login user's Org specific data for a selected event
    2. upload the 4W spreadsheet with updated data

http://eden.sahanafoundation.org/raw-attachment/wiki/BluePrint/ShaRe/UseCases/Upload_4W.png

Call Center (EOC) hotline service

  1. Anonymous user calls the ShaRe hotline to report a request
  2. Authorized Request Logger receives a request for aid
    1. if
      1. anonymous user - records all contact information to ensure its not a prank call
      2. known (trusted) or from own organization, then contact details unnecessary
    2. it is logged using the request type specific form
    3. includes identifying predefined item kits/packages and request site (location)
  3. Upon submission of the request, the system prompts Request Logger to
    1. select designated Request Approvers from the area
    2. submit an email and/or SMS requesting for verification and validation
  4. Approver confirms the request to be authentic
    1. clicks on approval URL in the Email or SMS
    2. log into the system to click approve
  5. Upon approval the request is confirmed and made visible for processing (i.e. commit and deliver)

http://eden.sahanafoundation.org/raw-attachment/wiki/BluePrint/ShaRe/UseCases/Request_Aid.png

Commit to request, supply and verify delivery

  1. Org Admin defines the
    1. supply items, kits, and packages
    2. locations for collecting the items (i.e. drop-off or assembly point)
  2. Donor (Supplier) filters through list of requests to
    1. search for specific request (i.e. by location or category)
    2. commit to the request and specifies the items (goods & service) and quantities
    3. arranges for gathering and delivering the items to the requested location
  3. Upon delivery and receipt of all items, the Requester updates the status = complete

http://eden.sahanafoundation.org/raw-attachment/wiki/BluePrint/ShaRe/UseCases/Supply_Aid.png

Publish Sitreps

  1. Rapporteur has permissions to create, read, update, or delete a sitrep
    1. access the Sitrep form to create new or edit existing)
      1. if new - relate to event (e.g floods 2017)
    2. add/edit content with sections for
      1. title (headline)
      2. paragraphs (with markups)
      3. reference URL(s)
    3. uploads
      1. multiple photos
      2. multiple documents (PDF, DOC, XSL, ...)
    4. select a location to relate the sitrep to (e.g. an Lx name - province, district, ... or a specific location)
    5. select an organization or default to Rapporteur's organization
    6. submit form to publish sitrep
      1. profile - create or update the styled html page
      2. email headline and link to the profile (attach PDF file)
      3. twitter - push headline with link to profile page
      4. RSS - update the RSS feed
  2. Anonymous user (i.e. anyone)
    1. access the sitrep through the menu
    2. selects either the list view or map view (i.e. hide or show map)
    3. see a summary of the stirep with more ... option
    4. clicks on more to navigate to profile page to read entire sitrep
    5. clicks on download control to receive a PDF copy of the sitrep

http://eden.sahanafoundation.org/raw-attachment/wiki/BluePrint/ShaRe/UseCases/Publish_Sitreps.png

Registering and Managing Users

Optional processes:

  1. SHARE registration system
    1. offers a form for users to register their name, organization, contact details (phone & email mandatory)
    2. system generate a random 4 digit code -
      1. is sent via SMS to registering user
      2. user enters code to authenticate their phone
      3. without phone authentication user cannot be granted permissions

http://eden.sahanafoundation.org/raw-attachment/wiki/BluePrint/ShaRe/UseCases/Register_Users2.png

and a Another

Last modified 4 years ago Last modified on 08/07/18 06:19:46

Attachments (5)

Download all attachments as: .zip

Note: See TracWiki for help on using the wiki.