Locus Robotics Ideas Portal
In order to utilize the robots in the best possible way and to meet the Rhenus requirements regarding prioritization its necessary that the LOCUS System is able to distribute the tasks across different task types (putaway|B2B|B2C).
Logic in principle: highest priority for picking tasks, flexible change to putaway tasks if there are not enough picking tasks for the available robots.
Is it possible to configure such rules within your software or does this mean additional programming effort?
Conveyor systems for putaway and picking are not connected. In case of switching between putaway and picking tasks for one robot this means the putaway task has to be completed at the conveyer station for putaway (drop off empty putaway tote) before the robot can drive to tote induct for picking for the pick task. This also applies in the opposite case (change from picking to putaway task -> end picking task at picking drop off before driving to putaway conveyor station)
Can you confirm that this is possible?
Regarding putaway, we have 5 different conveyor stations which must be targeted by the robots. The interface message for putaway will contain the concrete station where the task has to be started. The task can end at any putaway conveyor station (drop off empty tote) so it´s preferred that LOCUS chooses the putaway conveyor station where the next task will start for drop off if the next task is a putaway task too.
Is this possible?
Regarding picking we have 2 different conveyor stations which must be targeted by the robots. The interface message for picking will contain the concrete station where the task has to be started. The task can end at any picking conveyor station (drop off) so it´s preferred that LOCUS chooses the picking conveyor station where the next task will start for drop off if the next task is a picking task too.
Is this possible?
|
Problem/opportunity trying to be solved
The workload for picking & putaway is often not evenly distributed throughout the day. Therefore, customers require to balance the workload between the two different processes in a flexible way. Thus, they will be able to avoid extreme daily peaks. If possible, further alignment for the induct & drop-off process with the conveyor is needed. |
|
|
Quantify the problem/opportunity
I am currently working on a 64 bots à 1,050 USD RaaS deal with Rhenus Logistics, one of the largest 3PLs. This is considered as a major entry point to many more opportunities and also for our new use cases e.g. case picking, pallet picking, etc. Important: This is a must-have for Rhenus to be able to sign the schedule in Q4 FY22 (February/March timeframe) |
|
|
What is the root cause of the problem/opportunity
During the development of the concept, we identified major daily peaks which would need to be absorbed by pickers or more robots. For the business case, Rhenus requires the ability to balance out the workload to avoid such peaks. This is highly critical to allow a very positive ROI. |
|
| Customer need date | Aug 8, 2022 |
| Urgent request | Yes |
| Report Tag | Tools |
Hi Julian - Can you please provide an update on this request.
Hi Julian, thank you, please can you set up a call with the relevant members of their team to discuss requirements and discuss possible designs for this. Please invite me and Lou (Luis) Jaquez.
Hi Dan, please see below the desired timeline:
Timeline/Overview on the possibilities from Product Management & Engineering until end of January 28, 2022
Kick-off the negotiation process with Legal from Rhenus -> Important: Having the timeframe in place is a requirement for Legal to negotiate a schedule
Signature beginning of March 2022
Desired availability: ASAP, but after talking to the customer, a timeframe of August - September would be considerable.
Julian, you have put this as an urgent request, and highlighted that will be a contractual requirement, but not needed until 08/08/22? What date do we need to confirm this by as you have highlighted contract signature in March?