Returnable / Refillable Asset Tracking- Bar Code Enabled
Context of U
This use case documents the process for orders that require use of a returnable asset using bar coding
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 as available
- Unit has been inspected and maintained
- Order is in system requiring a returnable asset
- Fully automated delivery system is in place with bar coding
Minimal Guarantees
the interests as protected on any exit
Success Guarantees
- Accurate inventory of returnable assets
- Visibility to chain of custody
Trigger
Time to deliver
Main Success Scenario
- System generates a pick task
- Warehouse staff accesses pick task on mobile device
- Warehouse staff inspects asset
- Warehouse staff assigns asset to customer in ICS by scanning appropriate bar codes.
- If order requires a refillable container, the container is filled with the product ordered (refer to order bar code enabled fulfillment process)
- Organization generates delivery document in ICS from completed pick document and updates the refillable container history log
- Carrier loads asset and provides an electronic signature for chain of custody
- Asset's inventory status is updated in ICS
- Carrier delivers asset to customer and customer electronic signature obtained for chain of custody
- ICS accepts carrier's proof of delivery and system is updated
- Customer calls to signal they no longer need asset and return process is initiated in ICS
- Organization dispatches carrier to pick up asset and obtains customer's electronic signature on mobile device
- Carrier adds their electronic signature to return document accepting custody of asset
- Carrier returns asset to warehouse
- Warehouse Staff unloads and inspects asset
- Warehouse staff scans asset to return asset to inventory noting condition
- Warehouse staff signs carriers return document to acknowledge received asset
- Item scanned to bring back into inventory recording warehouse location
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 | Warehouse Staff Inspects Refillable Container and Logs Results
| |
| 15 | If asset returned requires maintenance | Asset is placed on Service Hold. When maintenance is completed asset is placed back into service and status updated to available. (May require movement to another location - requiring another scan.) | |
| 15 | if refillable container has product in it | Must have return paperwork to include regulatory requirements. Follow company processes. | |
| 15 | If refillable container has product in it | Container must be weighed to determine qty of product left so credit can be issued |
Technology and Data Variations
Maintenance of refillable container may need to be it's own use case
| 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