| | 3 | |
| | 4 | == Components == |
| | 5 | * pe_group/Req ('Community' or 'Family') |
| | 6 | * Shelter/Req |
| | 7 | * Hospital/Req |
| | 8 | * Organisation/Req |
| | 9 | * Office/Req <- can be used for internal requests, like IT/Stock Requests? |
| | 10 | |
| | 11 | == Roles == |
| | 12 | * Pledger marks status as 'Delivered' - pseudo role or onvalidation? |
| | 13 | * Requestor marks status as 'Received' - pseudo role or onvalidation? |
| | 14 | * Want Sync strategy for this |
| | 15 | |
| | 16 | == Issues == |
| | 17 | * Structured into category/subcategory (like Vol Skills widget?) |
| | 18 | * Link RMS to Inventory (Warehouse) |
| | 19 | * Separate Line Items in Single Req (like PR) |
| | 20 | * => Header info entered once :) |
| | 21 | * Pledges match line items (like PO) |
| | 22 | * RMS Timetable options? |
| | 23 | * 'Immediate' |
| | 24 | |
| | 25 | == Shelter Management/Needs assessment == |
| | 26 | * #families/#people => Food/Water/Shelter needs for simplified RMS reqs |
