Context of U

  This use case will cover process of inspecting and capturing activity history for refillable container assets needed for regulatory compliance using bar coding

Scope

 

Level

Summary

Primary Actor

.

Stakeholders and Interests

Preconditions

  1. A refillable container has been received into the warehouse
  2. Refillable container has some type of asset tag to identify the unique container
  3. Container is in the ICS
  4. Facility is an authorized refillable container location
  5. Organization has implemented bar coding with ICS

Minimal Guarantees

the interests as protected on any exit

Success Guarantees

  1. Container is certified for use and can be refilled with product
  2. Past history is documented and available for review & reporting via electronic system

Trigger

Time to fill container

Main Success Scenario

  1. Warehouse Staff pulls up history on all empty container on mobile device
  2. Select appropriate container
  3. Warehouse Staff inspects container to determine if action is needed
  4. Perform needed actions
  5. Warehouse staff completes the container inspection form on the mobile device
  6. ICS is updated with information from inspection form

Extensions


221.
Main Success Scenario StepConditionBranching Action

 

 

 

   
   
 . 

 

   

 

   
   

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