Blueprint for the Request Management Module

We need to be able to track Requests for Aid & their Fulfilment.

Components

• pe_group/Req ('Community' or 'Family')
• Shelter/Req
• Hospital/Req
• Organisation/Req
• Office/Req <- can be used for internal requests, like IT/Stock Requests?

Roles

• Pledger marks status as 'Delivered' - pseudo role or onvalidation?
• Requestor marks status as 'Received' - pseudo role or onvalidation?
• Want Sync strategy for this

Issues

• Structured into category/subcategory (like Vol Skills widget?)
• Link RMS to Inventory (Warehouse)
• Separate Line Items in Single Req (like PR)
  • => Header info entered once :)
  • Pledges match line items (like PO)
• RMS Timetable options?
  • 'Immediate'

Shelter Management/Needs assessment

• #families/#people => Food/Water/Shelter needs for simplified RMS reqs

Haiti Requirements:

• HaitiRMSToDo

User Guide for old PHP system:

• ​http://wiki.sahanafoundation.org/doku.php?id=doc:rms:english

Wireframes for a proposed system for Nashville Floods:

• ​http://bit.ly/9UW0tA

Usability suggestion for Pakistan Vesion

• Home ​http://test.eden.sahanafoundation.org/eden/rms/index seems not necessary since the sub menu is quite clear to navigate.
• Submenu name should be consistent with the link page
  • View request & Pledge aid  Pledge Aid
  • View & edit pledge  Pledge. “List” & “Add” are two submenu under it.

---

BluePrints BluePrints BluePrints BluePrints