Returnable / Refillable Asset Tracking- Not Auto ID Enabled

Context of U

  

Scope

 

Level

Summary

Primary Actor

.

Stakeholders and Interests

  • Warehouse Manager (May be off site):  Inventory accuracy;

Preconditions

  1. Asset has been received and processed into inventory
  2. Unit has been inspected and maintained

Minimal Guarantees

the interests as protected on any exit

Success Guarantees

  1. Accurate inventory of returnable assets
  2.  Visibility to chain of custody

Trigger

.

Main Success Scenario

  1. Receive customer order that will require a returnable asset or refillable container.
  2. Pick document is created
  3. Warehouse staff inspects asset
  4. Warehouse staff assigns to customer pick document.
  5. If order requires a refillable container, the container is filled with the product ordered and warehouse staff updates container's history log
  6. Office staff generates delivery document from pick document
  7. Carrier loads asset and signature obtained for chain of custody (Copy retained )
  8. Record asset shipment in ICS taking it out of inventory
  9. Carrier delivers asset to customer and customer signs delivery document as proof of delivery
  10. Carrier provides Proof of delivery document back to organization and attached to original document
  11. Customer calls to signal they no longer need asset and return process is initiated
  12. Dispatch carrier to pick up asset and obtains customer signature on return document
  13. Carrier signs return document to accept custody of asset
  14. Carrier returns asset to warehouse
  15. Asset is unloaded and inspected by the warehouse staff noting condition
  16. Warehouse staff signs return document to acknowledge received asset
  17. Warehouse staff provides return document to office staff and asset status is entered into ICS as on "service hold" for any maintenance needed
  18. Asset is put away and return ticket is submitted to office staff
  19. Asset status is changed in ICS as "available"

Extensions


1.
Main Success Scenario StepConditionBranching Action

7.

  Asset can be shipped thru 3rd party carrier, internal staff or picked up by customer

  If customer picks up or returns they sign the delivery & return documents .

4. If inspection reveals issue and other containers are available Asset needs to be taken out of service  until maintenance is performed 
 4. If inspection reveals issue and no other container is available Maintenance needed is performed before shipped out to customer
 4. If processing a refillable containerFollow regulatory requirements and internal processes 

 

   

.

Technology and Data Variations

the variation that will cause eventual bifurcation in the scenario



Main Success Scenario StepBranching Action
reference to the main success scenario # where the variation occurs

numbered list of variations

Notes

  • whatever the project wants to note
  • ideally such content would be recorded elsewhere (e.g., business rule table)

Related Resources

links to related resources

Contributors

list of contributors, using the wiki's "@First Last" feature, if possible