View Procurement Queue

Notes

• The Procurement Queue is simply the list of cards that:
• Are in the REQUESTED, IN_PROCESS, or READY states
  • Are associated with the “Receiving Discharge” (See Minimal Configurations For Tenant)
• In the future, this will lead to the ordering features.
• Note that the Fulfill action transitions the card directly to the next station in FULFILLED State, skipping the FULFILLING (In transit) state in the loop. This is by design at this time to simplify the management of cards. In the future, this transition should be configurable or have two separate actions one that skips the intermediate step and one that does not.

Steps

1. User navigates to the procurement queue
2. Alternative Actions:
   1. User Selects Requested cards and Procure action
   1. Depending on order mechanism for that item, vendor links are opened in the browser, or text is generated for copying/pasting to an email, or a table is generated to copy and paste to a PO
   2. Cards are transitioned to IN_PROCESS
   2. User Selects IN_PROCESS Cards and “Received” action
   1. The selected cards are transitioned to READY
   3. User Selects READY and Fulfill action
   1. The Selected cards are transitioned to FULFILLED and associated with the Shipping Induct or the Internal Station Induct depending on the configuration of the tenant that is implemented

Scenario

See Kanban Cards Information Model for the lifecycle of a Kanban Card.

Note that this scenario allows shortcuts in the transitions from IN_PROCESS to FULFILLED and from READY to FULFILLED. In the future, the validity of these transitions should be controlled by a configuration at the Tenant or Facility level. It is also possible to have a direct transition from REQUESTED to FULFILLED if necessary.

---

Copyright: © Arda Systems 2025, All rights reserved

Comments