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
- Asset has been received and processed into inventory
- Unit has been inspected and maintained
Minimal Guarantees
the interests as protected on any exit
Success Guarantees
- Accurate inventory of returnable assets
- Visibility to chain of custody
Trigger
.
Main Success Scenario
- Receive customer order that will require a returnable asset or refillable container.
- Pick document is created
- Warehouse staff inspects asset
- Warehouse staff assigns to customer pick document.
- If order requires a refillable container, the container is filled with the product ordered and warehouse staff updates container's history log
- Office staff generates delivery document from pick document
- Carrier loads asset and signature obtained for chain of custody (Copy retained )
- Record asset shipment in ICS taking it out of inventory
- Carrier delivers asset to customer and customer signs delivery document as proof of delivery
- Carrier provides Proof of delivery document back to organization and attached to original document
- Customer calls to signal they no longer need asset and return process is initiated
- Dispatch carrier to pick up asset and obtains customer signature on return document
- Carrier signs return document to accept custody of asset
- Carrier returns asset to warehouse
- Asset is unloaded and inspected by the warehouse staff noting condition
- Warehouse staff signs return document to acknowledge received asset
- Warehouse staff provides return document to office staff and asset status is entered into ICS as on "service hold" for any maintenance needed
- Asset is put away and return ticket is submitted to office staff
- Asset status is changed in ICS as "available"
Extensions
1. | Main Success Scenario Step | Condition | Branching 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 container | Follow regulatory requirements and internal processes
| |
. |
Technology and Data Variations
the variation that will cause eventual bifurcation in the scenario
Main Success Scenario Step | Branching 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