Locus Robotics Ideas Portal
Currently, identification of bot issues at a customer site are based on a customer submitting a ticket. The Locus system does not proactively identify/notify us of issues. We have encountered situations where a site may have multiple disabled/offline bots but don't know about it until the customer submits a ticket (e.g., ticket identifying 10 bots that are disabled and have not moved in days).
A bot mileage metric would provide a fairly simple method to identify bots with issues based on distance traveled over a defined time period (e.g., last 24 hours, last week). For example, if a bot has only moved a couple feet over the last 24 hours, it's likely the bot has an issue. Capturing bot mileage would also enable proactively maintenance planning based on total mileage since last maintenance/repair (similar to how automobile maintenance is managed). Also, bot mileage could be used for Marketing purposes to highlight how many miles the bot fleet has traveled and saved Associate walking.
If the bot has issues traveling then it's unlikely to make it to the charger and will be dead. If the bot is dead or offline how do you get the mileage? If you get it from wrangler or other server, how do you distinguish between bots that aren't being used and ones that are having issues? We also don't have any proactive maintenance requirements so I'm not sure what mileage is the indicator of in this case. Mileage is there for the taking if someone wants to use it but doesn't sound like the place to start when looking for issues.