-
Notifications
You must be signed in to change notification settings - Fork 232
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Device ID / UUIDs cannot be reassigned #37
Comments
May need to work out a system whereby either the GPS/lock device (the part actually being tracked) or the vehicle/scooter are replaced. Maybe require new registration and new UUID/Device ID if they do that level of a repair or teardown. Will be good to track if the same device has ongoing mechanical issues or is reported often, but then they have an option to swap out the major parts if needed and can then start with a new UUID/device ID. |
John and I have been down this road several times. Our going in position should be a single UUID for a vehicle (no-reassignment). We'll let the companies decide what makes a scooter a scooter, bike a bike (Frame, battery, etc). Most likely only minor maintenance will be performed due to the low cost of these devices relative to labor and parts. As we progress toward higher value assets like Autonomous vehicles, this policy will become more important and we will get more specific about what makes car a car, etc. Make sense? |
Yes - this is mostly in response to some insight Jose and I gained from a chat with the folks from Seattle yesterday and the data they've already collected, that all the connected and tracking technology seems to be housed in the GPS/lock device. The concern is when say, a vehicle's frame is damaged, and the undamaged GPS/lock device is placed on a different vehicle, the operator may transfer the ID # to the replacement frame. Do we track it using the same UUID as the previous vehicle frame, or have them register it as a new vehicle? Basically Seattle's advice was whatever strategy we decide, to be clear about it up-front so operators are all doing the same thing. |
Got it... So we can mandate that as far as we are concerned, the bike/scooter is the GPS/lock device. UUID will stay with that item and thus we will mandate that operators not re-register. Everyone okay w that position? |
Are we all on the same page here? @jannasmith @hunterowens |
I want to get input from Jose just in case before finalizing this (if he anticipates needing to track the individual bikes/scooters for maintenance issues or anything else) @LADOTBikeshare, let me know if this needs to be resolved urgently though |
OK cool we can agree to referring to the GPS/Lock Device as the "Device" to which the UUID will be assigned. |
Great. Do we need to add any notes to meta to affirm this?
…On Mon, Aug 27, 2018 at 1:56 PM jannasmith ***@***.***> wrote:
OK cool we can agree to referring to the GPS/Lock Device as the "Device"
to which the UUID will be assigned.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#37 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ABp74oUKkOLxTbhcwhDuUy7MDuM7X9a1ks5uVF0TgaJpZM4WFAaB>
.
|
Clarify that they cannot reassign these numbers. Per @jannasmith
The text was updated successfully, but these errors were encountered: