Skip to content
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

Perform an audit of the small tools, etc in the Workshop #362

Open
amcewen opened this issue Oct 12, 2016 · 4 comments
Open

Perform an audit of the small tools, etc in the Workshop #362

amcewen opened this issue Oct 12, 2016 · 4 comments

Comments

@amcewen
Copy link
Member

@amcewen amcewen commented Oct 12, 2016

It would be useful to work through the assorted drawers in the workshop and...

  • See what's there
  • Note it (not in excessive detail) somewhere on the wiki
  • Label the drawers
  • Ideally mark the tools too, as per #360.
@aubergine10
Copy link
Contributor

@aubergine10 aubergine10 commented Apr 29, 2017

Most of the small tools don't lend themselves to having printed labels. What about some small RFID tags and heat-shrink wrap them on to the tool handle? We can then make some sort of RFID reader to catalogue them, and potentially have RFID scanners built in to doorbots to detect when a tool leaves room (I have no idea how to do any of this BTW).

@DoESsean
Copy link
Contributor

@DoESsean DoESsean commented Dec 14, 2017

As stated in #360 this can be done as part of the move.

@DoESsean
Copy link
Contributor

@DoESsean DoESsean commented Jul 11, 2019

We've moved. We should really look at getting this done so that we know what we have and what we might need.

@chris-does
Copy link

@chris-does chris-does commented Jul 27, 2019

Adding relevant content from #1169 to enable a "clean close" of that issue:

@amcewen with regards to the tracking of / ensuring the return of tools in general, would a tracking (BLE or RFID based) system be deemed too cumbersome / excessive?
Could this aspect (the tracking) be addressed as part of #360 and #362 - or, indeed, perhaps combine #360 and #362 (closing them) and create a new "Inventory Management Mission"?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
5 participants