Blue Print - Logistics

Also refer to BluePrintInventoryManagement (which is more comprehensive, but less up to date)

To Do:

• Be able to cancel processed send & recv shipments (and reverse the item movement)
• Add Unique Shipment Reference Numbers
• Generate Forms for shipments (Waybills or Goods Received Notes)
• The receive / send / commit buttons should depend on authorisation settings
• Adjust the commit button so that it only appears for un-fulfiled commitments
• Expiry times for Warehouse Items need to be linked to the unique batch, not consolidated across all batches (like CTNs)
• Aggregation and kitting/dekitting Functionality
• From IFRC Logs procedures:
  • Base Unit -> Unit of Measure
  • Packet -> Pack
  • Pictures of Items & Packs
  • Have field for loose units
• Create a better work-flow link from Req -> Commit -> Send -> Recv
  • Disable a single commitment to sent multiple times
• User visible ID numbers for Received and Sent Shipments. Possibly using a site prefix and a sequential number per site to allow for easier filing of the printed (and potentially) signed forms.
• Functionality to show requests which can be fulfilled by the items in a inventory (and perhaps visa versa).
• Ensure that only one packet per item can have a quantity = 1 (and thus be the unit of measure for that item)

References

The requirements for the Logistics module is described here:

• ​http://wiki.sahanafoundation.org/doku.php?id=req:logistics_module

The terminology used in this module is based on the following document:

• ​http://wiki.sahanafoundation.org/doku.php?id=req:logistics_module_definitions

Documentation

• UserGuidelinesLogistics
• DeveloperGuidelinesLogistics

Linked Modules

• Finance
• Request Management

---

BluePrints