Context of Use
a longer statement of the goal, if needed |
Scope
Inventory Control System (ICS)
Level
Summary
Primary Actor
No one specifically.
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
- Warehouse Operations Manager (On site): Inventory accuracy; efficient process to get inventory into system quickly; product placement is correct so easily accessed
- Accounting Department: Reduction of extra cost due to inventory errors; inefficient processes that increase time spent handling inventory
- 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
- Vendor (Manufacturer or Distributor): Efficient process enables faster billing and payment; Reduction in time needed to handle error resolution; Enables vendor inventory accuracy; Track & Trace enabled
- IT Manager: Ensure the Inventory Control System (ICS) is operating as required to support the business.
- Logistics Process Governance Lead: Develop process documentation and ensure it's operational application
- Customer: Product in stock and ready for delivery; Timeliness of delivery
- Manufacturer: Efficient process enables faster billing and payment; Reduction in time needed to handle error resolution; Enables vendor inventory accuracy; Accurate information to base program payments etc. against. Track & Trace enabled
- Carrier: Quick unloading time; accuracy; speed up payment for service; Timeliness in reporting delivery complete back to logistics team
- Shipper Company: Receiving confirmation the delivery is completed; speed up payment for services
- Receiving Company's Procurement Dept.: Quick validation order has been fulfilled so they can close out PO
- Manufacturing Division within the receiving company: Real time visibility to inventory updates
- Store Managers - Receiving: Real time visibility to any inventory updates
- Warehouse Staff: Accurate placement and recording of location for product
Preconditions
- Product must have been ordered.
- Product is defined in the master inventory list.
- Advance Shipping Notice (ASN) has been received prior to the delivery if applicable
- Product is onsite at the receiver warehouse
- Bill of Lading (BOL) is present with required identifiers (Example is a Purchase Order #).
Minimal Guarantees
the interests as protected on any exit |
Success Guarantees
- Only products in acceptable condition have been received.
- ASN information matches the actual delivery (if applicable)
- Correct product, quantity, and lot number (where applicable) has been accurately recorded in the ICS.
- The product was delivered (received by) the correct location.
- All applicable stakeholders have been notified of receipt.
Trigger
ASN is received into system (if applicable). Otherwise carrier arrives at the site
Main Success Scenario
- ASN is received (if applicable)
- The carrier makes an unload request and presents BOL to warehouse staff.
- Warehouse staff reviews BOL.
- Matching order information is available
- Warehouse staff informs carrier of unload location.
- Warehouse staff weighs bulk product (if applicable).
- Carrier moves vehicle to unload location.
- The warehouse staff and carrier work together to move the product from the truck to the inspection/staging area.
- Warehouse staff Inspect product units. Possible Outcomes
- Warehouse staff notes lot numbers or serial numbers (if applicable).
- Warehouse staff signs off on bill of lading.
- Warehouse staff stores product in specific location, noting the location on the paperwork (if applicable).
Extensions
| Main Success Scenario Step | Condition | Branching Action |
|---|
8. | Not all product is accepted by warehouse. | The vehicle operator may need to sign off on some paperwork. |
| 8/9. | Sometimes each product is inspected as it is unloaded. Sometimes products are not inspected until all products have been unloaded | Nothing |
11 | is not necessary to not location | Store the product without noting location |
| 11 | | |
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 |