Changes between Version 25 and Version 26 of BluePrint/Requests


Ignore:
Timestamp:
09/03/13 08:28:07 (8 years ago)
Author:
Fran Boon
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • BluePrint/Requests

    v25 v26  
     1= Blue Print - Requests =
    12[[TOC]]
    2 = Blue Print - Requests =
    33
    44== Introduction ==
    55Sahana Eden needs to be able to manage requests for:
    6  * Items (Supplies)
    7  * Assets
    8  * People
     6* Items (Supplies)
     7* Assets
     8* People
     9* Shelter
    910
    10 This requires tracking requests, commitments to fulfil requests and the final fulfilment of requests.
     11This requires tracking requests, commitments to fulfill requests and the final fulfillment of requests.
    1112
    1213== Current Status ==
     14* UserGuidelines/Logistics
     15* Requests can be created for Items or Skills (or named People)
     16* Requests have to be made for a Site/Facility
     17* Requests can optionally have a Commit stage before fulfillment
     18* Fulfillment can link straight to Shipments
     19* Recurring Requests can be scheduled
    1320
    14 === To Do ===
    15  * Default Items' Pack Value to a value in the Catalog & allow manual updating to actual if-necessary
    16   * Doc: in a Procurement system, this is the max price that the budget holder (approver) is authorising, so they need to be checked back with before purchasing if the price is higher.
    17  * Imperial vs. metric UoM
    18  * Add more help to the req_item_inv_item page
    19  * Add Assets to Requests (as Components)
    20  * Remove req_item_id from inv_send and inv_recv. This link was used to show which shipments we meeting a request. Use a resource link instead.
    21  * Adjust the commit button so that it only appears for un-fulfiled commitments
    22  * Create a better work-flow link from Req -> Commit -> Send -> Recv
    23   * Disable a single commitment to sent multiple times
    24  * Functionality to show requests which can be fulfilled by the items in a inventory (and perhaps visa versa).
    25  * Ensure that only one packet per item can have a quantity = 1 (and thus be the unit of measure for that item)
    26  * Request Timetable options?
    27   * 'Immediate'
    28  * For Shelters #families/#people => Auto Calculate !Food/Water/Shelter for simplified reqs
    29  * Add Unique ID numbers to transactions [Site Code]-[Sequential Number]?
     21== To Do ==
     22* Complete support for Assets
     23* Add support for Shelter
     24
     25=== Estimation ===
     26* For Shelters #families/#people => Auto Calculate !Food/Water/Toiletries for base recurring requests
     27* Values are stored in localisable Scenario Templates
     28* Reports created to allow comparison of templates against historical data
     29
     30=== Notes from Pakistan ===
     31* Default Items' Pack Value to a value in the Catalog & allow manual updating to actual if-necessary
     32 * Doc: in a Procurement system, this is the max price that the budget holder (approver) is authorising, so they need to be checked back with before purchasing if the price is higher.
     33* Imperial vs. metric UoM
     34* Add more help to the req_item_inv_item page
     35* Add Assets to Requests (as Components)
     36* Remove req_item_id from inv_send and inv_recv. This link was used to show which shipments we meeting a request. Use a resource link instead.
     37* Adjust the commit button so that it only appears for un-fulfiled commitments
     38* Create a better work-flow link from Req -> Commit -> Send -> Recv
     39 * Disable a single commitment to sent multiple times
     40* Functionality to show requests which can be fulfilled by the items in a inventory (and perhaps visa versa).
     41* Ensure that only one packet per item can have a quantity = 1 (and thus be the unit of measure for that item)
     42* Request Timetable options?
     43 * 'Immediate'
     44* Add Unique ID numbers to transactions [Site Code]-[Sequential Number]?
    3045
    3146== Also See ==
    32  * UserGuidelines/Logistics
     47* UserGuidelines/Logistics
     48
    3349=== Other Requirements ===
    34  * HaitiRMSToDo
    35  * User Guide for Sahana Agasti: http://wiki.sahanafoundation.org/doku.php?id=doc:rms:english
    36  * Wireframes for a proposed system for Nashville Floods: http://bit.ly/9UW0tA
     50* [wiki:HaitiRMSToDo]
     51* User Guide for Sahana Agasti: http://wiki.sahanafoundation.org/doku.php?id=doc:rms:english
     52* Wireframes for a proposed system for Nashville Floods: http://bit.ly/9UW0tA