Picking Process Flow
1. Wave & Job Creation (Logiwa):
The process starts within Logiwa IO. A "Robotics Wave" is created, generating the specific picking jobs for the orders in that wave.
2. Job Transmission (Logiwa -> Locus):
Logiwa sends the details of these jobs (tasks, locations, items, quantities) to the Locus Robotics system.
Important Note: Each Job can only have one order.
3. Tote Induct Notification, Initial Confirmation & Background Validation (Locus -> Logiwa -> Locus):
The Locus system informs Logiwa which specific tote it plans to use for the next task. Logiwa receives this notification and immediately sends back a message to Locus. Then, Logiwa performs the actual check to ensure the tote exists and is available.
If the tote exists and is available: Logiwa completes its check and finds no problems. No further tote-related message is sent.
If the tote does not exist or is already in use: Logiwa completes its check and identifies an issue. It then sends another message to Locus indicating the tote cannot be used.
Important Note: Since Locus is designed to proceed based on the first message and does not necessarily wait for the second message (confirming tote availability), discrepancies can occur between the Logiwa and Locus systems regarding tote status.
4. Guided Picking (Locus - Physical Action):
Based on the instructions received from Logiwa, Locus directs the robot to the pick location and guides the picker to start the task. The robot's screen shows the item, location, and quantity. The picker retrieves the item(s) and confirms the action on the robot's interface.
5. Pick Result Feedback (Locus -> Logiwa):
After the picker completes the action on the Locus interface, Locus sends the result of each task back to Logiwa, indicating if it was a "Full Pick" or "Partial Pick" or Partial Pick with Missing/Damaged Info.
6. Task Execution in Logiwa (Based on Feedback):
Full Pick: Logiwa executes the task with the full quantity.
Partial Pick: Logiwa executes the partial pick based on the feedback received.
Partial Pick with Missing/Damaged Info: Logiwa executes the partial pick and reflects the changes to its inventory based on the missing/damaged information received from Locus.
7. Inventory Recheck & Follow-Up (Logiwa):
For partial picks with Missing/Damaged Info, Logiwa checks if there's available inventory elsewhere for the remaining quantity needed.
If Inventory Available: Logiwa creates follow-up tasks for the remaining items and sends these new tasks back to Locus as an update (Return to Step 2 for the follow-up task).
If Inventory Not Available: No follow-up task is created for the short quantity, and no further update message is sent.
8. Completion:
The cycle finishes when all tasks from the initial Robotics Wave are fully executed or marked as finished due to inventory unavailability.
Job Cancellation Process
1. Cancellation Initiated (Logiwa):
A user cancels the specific job directly within the Logiwa IO web application for a job that has already been sent to Locus.
2.Cancel Message Sent (Logiwa -> Locus):
Logiwa transmits a cancel message to the Locus robotics system, referencing the specific job to be cancelled.
3.Cancellation Attempt (Locus):
Upon receiving the cancel message, the Locus system attempts to cancel the specified job activities if the job has not already been completed by the robots and pickers.
Note: Successfully stopping a job mid-process via this cancellation message is not guaranteed, as the tasks might already be finished or too far along for the system to cancel immediately.
For Technical Guide, Please visit Logiwa IO Locus Robotics Automation Integration Technical Guide