Internal Warehouse Movement - Not Auto-ID-Enabled
Context of Use
Document the steps of internal warehouse movement when not utilizing AIDC technology
Scope
Internal Movement of Product within a single business unit
Level
Summary
Primary Actor
Warehouse Staff.
Stakeholders and Interests
- Warehouse Manager (May be off site): Inventory accuracy; efficient process to get inventory into system quickly; product placement is correct so easily accessed; Ability to manage first in/first out for products.
- Warehouse Operations Manager (On site): Inventory accuracy; efficient process to get inventory into system quickly; product placement is correct so easily accessed; ability to manage first in/first out products
- Accounting Department: Reduction of extra cost due to inventory errors; inefficient processes that increase time spent handling inventory (Lost sales due to inventory errors)
- Sales: Current, accurate inventory to fulfill sales orders; timeliness in fulfillment of the order
- Inventory Control (Auditing of Inventory): Reduction of time needed to perform audit; Accuracy of inventory before and during the audit
- IT Manager: Ensure ICS is operating as required to support the business.
- Logistics Process Governance Lead: Develop process documentation and ensure its operational application.
- Customer: Product in stock and ready for delivery; Timeliness of delivery
- Manufacturing division within the receiving company: Real time visibility to inventory updates; Know where product is located when retrieving for manufacturing process
- Warehouse Staff: Accurate placement and recording of location for product so can easily pick and pack an order
- Regulatory Compliance: Ensure products are stored correctly according to regulatory requirements.
Preconditions
- Product must be in the facility
- Location control must be implemented in the facility.
- Locations labels or placards must be installed human readable characters
- Product defined in the master inventory list with company internal SKU cross referenced to suppliers or industry number.
- Inventory Control System (ICS) is in place.
- Product is labeled with description / lot # (if applicable
- Product qty is greater than zero.
- Product is showing in inventory of the ICS.
Minimal Guarantees
the interests as protected on any exit
Success Guarantees
- Accurate inventory tracking in facility.
- Timely inventory transactions in ICS.
- Correct product, quantity, and lot number (where applicable) has been recorded in the ICS.
- All applicable stakeholders have been notified of movement.
- Ability to locate product efficiently
Trigger
Decision is made to move product to another location in warehouse.
Main Success Scenario
- Office staff will instruct the warehouse staff to move product to another location.
- Warehouse staffs locates product in original location.
- Warehouse Staff moves product into new location.
- Warehouse Staff records applicable changes and signs off on document If required
- Warehouse Staff turns document into office staff to be recorded in the ICS system
Extensions
1. | Main Success Scenario Step | Condition | Branching Action |
---|---|---|---|
1. | .Warehouse staff may be instructed verbally for product movement. | Warehouse staff will respond according to procedure at their company. | |
1. | Product movement may occur based on warehouse staff making determination the product needs to be moved. | Appropriate forms need to be completed | |
4 | ICS may not have product in same location as product physically is located | Warehouse staff would correct via inventory adjustment or report to inventory manager for review/correction | |
4 | Qty entered for transfer may not match the qty on the request documentation | Warehouse staff would correct via inventory adjustment or report to inventory manager for review/correction | |
1. |
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