Locus Robotics Ideas Portal
Data capture needed on bluetooth and battery of each unit
|
Problem/opportunity trying to be solved
customers (and CS) have no visibility about the quality, status, battery level and bluetooth range of the user tags. there is no obvious way to test, and know when replacements are required. |
|
|
Quantify the problem/opportunity
Customers need to have confidence in the hardware they are using. we need to manage the availability and shelf life of the tags so custoemrs can have optimal picking opportunities |
|
|
What is the root cause of the problem/opportunity
No data available to know what tag shelf life and usability is (and when they need replacing) |
|
| Customer need date | Sep 30, 2023 |
| Urgent request | Yes |
| Report Tag | Tools |
To add more to this, i raised an issue with DHL Welham last week, and got the following as a formal response to inaccurate tag reading :
We have a reply from BST on TAC-10337, about this issue you reported:
"Unfortunately a limitation with the RFID tags is that the RFID signals can get mixed up at times. The user who is closer to the robot can possibly have a tag with a weaker connection and cause an associate’s RFID tag to register for the pick. There is a couple ways we go about resolving this issue:
If the user sees that their pick is being associated with another user, that user can reset the application via the Locus icon at the top left of the screen to retry the pick within the original user’s scope.
If this doesn’t work, the user can try to get a new tag or a tag with a new battery (if applicable) registered to their username. Please follow up with a desired course of action."
Let us know if you need anything else, otherwise we will close this ticket.
This doesn't feel like an failsafe data recording solution is we are reliant on custoemrs above for validation
Many of my sites are suffering same issue:
Penguin Pallejà
DHL Toledo
DHL Vignate
El Corte Ingles
among others