Locus Robotics Ideas Portal
We absolutely need actual robot distances traveled and not x-y. Please, please add odometry data!
Change “Seconds Dwell per Pick” and “Distance per Pick” to “per Line.” Per pick is not relevant unless Units per Line = 1.
Capture the lost mission time between drop-off and induct. This is currently missing and can be appreciable, especially if induct is separate from drop-off.
Allow user to enter the “inactivity interval” for pickers and robots (current 2 minutes, and 6 minutes).
Please note that there are several clients, including Nike, who are now aware of the shortcomings of how mission distances and times are reported (with regards to the distance being x to y and not actual odometry). Customers have expressed a lot of dissatisfaction with how this is reported, so this is not a request which would only affect internal members accessing these reports, but also clients. Definitely would really like to see odometry data.
1 and 2 are critical items for backtesting/troubleshooting active sites vs the COO.
3 would be nice to have, but I understand the difficulty in calculating it with the current data structure (can't be attached to a Job ID).
4 I think this is part of a bigger discussion around entirely re-thinking the way productivity is calculated. There currently isn't a good way to break out different workflows (Pick vs Put) with the "time-block" method.