All ideas

Currently there is no means to view the LP# mapped to each bin location ID at a customer site. If any issue is encountered with a bot traveling to the wrong location for an item pick or missing location, the customer must submit a ticket and then ...

Currently, identification of charger issues at a customer site are based on a customer submitting a ticket. The Locus system does not proactively identify/notify potential issues. We have encountered situations where a site may a charger has not c...

Send bot to nearest open charger

Per Nike Roll-out agreement and Mike Johnson's comments: We do not have any new/additional ways to get low level scan data from Aila. For the log – we do not get no read/read from the scanner – that is internal to device and we do not see this dat...

Per Nike Roll-out agreement: This tool will test the functionality of the scanner or camera that is onboard of the tablet. Visualized data: Current scan result Historical scan data = save last code scanned Reading rate log, as described in the “Sc...

Currently, customers need to submit a ticket to Locus Support to request Tag Locks to be enabled/disabled. This occurs more frequently during peak when there is a spike in temp labor and there may not be enough user tags, which leads to requests t...

Performance enhancement throughout, including reduction of data flows to manageable levels.

Enhance dynamic control to mitigate wheel slip and better handle varying payloads, including overloads.

Optimize orders into putwall groups and delivers to putwall where orders will be sorted into the putwall (Working group of orders) Would need configuration variables. Today WMS creates the putwall groups and prevent Locus from optimizing picking b...

Operations management intelligence. How many bots do I need? How many people do I need?