All ideas

We are trying to see if there is an option to disable the blue spotlight on the bot when bots are dismissed.

But depending the distance between the pick lcoation and the CM queue, sometimes you would want this value to be a few seconds (when the CM queue is far way) or maybe half minute/minute when the CM queue is quite far away. Ideally we would be able...

They would like a functionality on the bot that they could trigger a color on the LEDs which is not used at the moment. They could somehow put the bot in a state that makes it visible for everybody that this bot is under investigation

Thoughts from the customer: The picker to press a button on the device to send an information-only message (location, SKU, task ID, required quantity) to the Troubleshoot team. This action should not create a final short pick in the system. ...

There is currently a parsing being done to the barcode that is scanned into Locus at pick. The customer would like no parsing to be done on certain SKUs or have a way to receive the exact barcode information that was scanned at pick. As far as I'm...

Alert from LokiMon/FA data to be proactive in fixing bots that are offline

The quantity to pick should always be black.

Customer is very keen on getting a UI change for the UI after you have scanned the item. They would only like to see information that is relevant to show on the UI to make sure to pick the item in the right tote. Proposal by the customer is made a...

LH (or equivelent) data dashboard per account (see attached mock up)

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 t...