Context of U
Scope
Conducting physical or cycle counts within a site
Level
Summary
Primary Actor
Warehouse Staff.
Stakeholders and Interests
- Warehouse Manager (May be off site): Inventory accuracy;
- Warehouse Operations Manager (On site): Inventory accuracy;
Sales: Current, accurate inventory to fulfill sales orders; - Accounting: Financial impacts to inventory discrepancies
- Inventory Control (Auditing of Inventory): Accuracy of inventory before and during the audit
- IT Manager: Ensure ICS is operating as required to support the business.
- Process Governance Lead: Develop process documentation and ensure its operational application.
- Customer: Product in stock and ready for delivery;
- Manufacturing division within the receiving company: Inventory Accuracy and supply chain impacts
- Warehouse Staff: Accurate recording of location, product and qty.
- Safety / Regulatory Management Group: Compliance .
Preconditions
- Product must physically be in the facility
- Location control may or may not be implemented in the facility.
- If location control is implemented locations stickers or placards must be installed with bar code and human readable characters
- Product defined in the master inventory list with company SKU cross referenced to product GTIN for available package sizes.
- Bar code-enabled ICS is in place.
- Bar code equipment is in place and integrated with ICS.
- Product is bar coded or a bar code catalog is available
- Product qty does not equal zero.
- Product is showing inventory level not equal to zero in the ICS.
- “Physical Inventory or Cycle Count” Procedures are in place.
- Count can be generated out of the ICS.
- Warehouse staff must be authorized to conduct “Physical Inventory or Cycle Count”.
- Warehouse staff has ability to access system/reports to address any variances.
- No inventory transactions are taking place
Minimal Guarantees
the interests as protected on any exit
Success Guarantees
- Accurate inventory tracking in facility.
- Real-Time inventory transactions in ICS.
- Correct product, quantity, and lot number (where applicable) have been accurately recorded in the ICS.
- All applicable stakeholders have been notified or have ability to report on adjustments before, during and after “Physical Inventory or Cycle Count”
- Ability to locate product more efficiently.
- Ability to update On-Hand Inventory qty’s
Trigger
.
Main Success Scenario
- Inventory manager generates a Physical or Cycle Count in ICS for relevant inventory to count.
- Warehouse Staff will locate product.
- Warehouse Staff scans product GTIN.
- Warehouse Staff enters count into ICS.
- (If Location control is implemented, Warehouse Staff scans from Location at appropriate time in the process.)
- Warehouse staff repeats this process until all counts are entered.
- Warehouse Staff/ Inventory manager runs a variance report.
- Warehouse Staff/Inventory manager researches variance prior to updating count to ICS.
- Warehouse Staff/Inventory manager updates count to ICS.
- Transaction is completed
Extensions
1. | Main Success Scenario Step | Condition | Branching Action |
---|---|---|---|
1. | .For this example Physical Inventory is the complete count of all products in the warehouse. Cycle count is the determined scheduled count of limited specific product in facility | .Warehouse staff will count based upon count type. | |
2. | Do we need to have anything in here about counting floor to “Sheet”? | ||
2 | Do we want to address Negative Inventory? | ||
5 | 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 or enter info and allow system to adjust. | |
3 | Bar code may not be present such as on bulk beans | Receiving company creates a catalog of products that contain bar codes for any product where a bar code cannot be present. Or Warehouse staff has ability to look up product by item description. |
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