Acquisitions: Difference between revisions
Aaronn0130 (talk | contribs) No edit summary |
No edit summary |
||
(23 intermediate revisions by 5 users not shown) | |||
Line 1: | Line 1: | ||
'''Please submit acquisition requests on this spreadsheet:''' | '''Please submit acquisition requests and suggestions on this spreadsheet:''' | ||
[https://docs.google.com/spreadsheets/d/ | [https://docs.google.com/spreadsheets/d/1EQms1Ybk1Z9l_GXbuQfbKt3rMEz0lhtF/edit#gid=1924919744 Acquisition Spreadsheet] | ||
Large purchase research examples: | |||
* [https://docs.google.com/document/d/1KOc6Vh1ETbA2IyDT4jTZ0EbRmmazhZT7NJdXJ5Xdu4I/edit?usp=sharing Large 3D Printer] | |||
* [https://docs.google.com/document/d/1Ws5sHN6Jd_vQ9fKumIMm1cVW7XCR62o9zC4cjwzKLzk/edit Band Saw] | |||
* [https://docs.google.com/document/d/1QwQavngAN-tIYHUSbHNeycNVVUn2B8FjmiiZZJWmUSA/edit?usp=sharing 3D Printer] | |||
* [https://docs.google.com/document/d/1Rpxv3_2xrhOTggILviktYHjsBj6YkCYpPIOEVTu-JtE/edit?usp=sharing Mill] | |||
* [https://docs.google.com/document/d/1g7UZP1Tg1m2Hv94kSJ3gb-NHjqG6to4Yir9RRA7Ouqs/edit?usp=sharing Vinyl Cutter Research] | |||
Line 8: | Line 16: | ||
These are the guiding questions we ask when spending HackRVA member money. The word "tool" is used liberally. It could be a hammer, software, hardware, or infrastructure stuff(like lights, tables, storage). | These are the guiding questions we ask when spending HackRVA member money. The word "tool" is used liberally. It could be a hammer, software, hardware, or infrastructure stuff(like lights, tables, storage). | ||
- Does it inspire people to make awesome stuff? | - Does it inspire people to make awesome stuff?<br> | ||
- Is it a "key" tool that all makerspace, hackerspace, fab labs should have?<br> | |||
- Is it a "key" tool that all makerspace, hackerspace, fab labs should have? | - Does it create opportunities for a workshop or a learning experience for HackRVA members?<br> | ||
- Does it solve an existing problem?<br> | |||
- Does it create opportunities for a workshop or a | - Is there someone to maintain and be the "keeper" of the tool? <br> | ||
- Are there training or workshops designed around the tool?<br> | |||
- Does it solve an existing problem? | - Are there specific awesome projects related to that tool? <br> | ||
- Is it a tool that's going to last and be robust under amateur use?<br> | |||
- Will it fit in our space... like physically?<br> | |||
- What are the maintenance and consumable costs?<br> | |||
- Is there someone to maintain and be the "keeper" of the tool? | - Is there a software component? What is it and how will it be integrated?<br> | ||
- Are there any safety concerns/ factors? | |||
- Are there training or workshops designed around the tool? | |||
- Are there specific projects related to that tool? | |||
- Is it a tool that's going to last and be robust under amateur use? | |||
- Will it fit in our space... like physically? | |||
- What are the costs | |||
- Is there a software component? What is it and how will it be integrated? | |||
- | |||
'''Additional Thoughts:''' | '''Additional Thoughts:''' | ||
Getting new stuff for the space is exciting! | Getting new stuff for the space is exciting! | ||
Ultimately tool acquisitions are decided | When we're evaluating an acquisition we consider a number of variables. There's the normal ones like quality, affordability, and useability. But also we look at how it will be used in our community. A tool suggestion with a member attached that is willing to maintain and support that tool is highly desirable. A member/tool pairing that comes with scheduled training or events is even better. Having specific projects in mind is good too. If you'd like to see a tool bought for the space, please let us know why. Ultimately tool acquisitions are decided by consensus at HackRVA monthly business meetings, so please attend if you would like to pitch an idea in person. If you are not able to attend, that's ok too, just let us know on Slack. |
Latest revision as of 00:19, 13 April 2025
Please submit acquisition requests and suggestions on this spreadsheet:
Large purchase research examples:
Guidelines:
These are the guiding questions we ask when spending HackRVA member money. The word "tool" is used liberally. It could be a hammer, software, hardware, or infrastructure stuff(like lights, tables, storage).
- Does it inspire people to make awesome stuff?
- Is it a "key" tool that all makerspace, hackerspace, fab labs should have?
- Does it create opportunities for a workshop or a learning experience for HackRVA members?
- Does it solve an existing problem?
- Is there someone to maintain and be the "keeper" of the tool?
- Are there training or workshops designed around the tool?
- Are there specific awesome projects related to that tool?
- Is it a tool that's going to last and be robust under amateur use?
- Will it fit in our space... like physically?
- What are the maintenance and consumable costs?
- Is there a software component? What is it and how will it be integrated?
- Are there any safety concerns/ factors?
Additional Thoughts:
Getting new stuff for the space is exciting!
When we're evaluating an acquisition we consider a number of variables. There's the normal ones like quality, affordability, and useability. But also we look at how it will be used in our community. A tool suggestion with a member attached that is willing to maintain and support that tool is highly desirable. A member/tool pairing that comes with scheduled training or events is even better. Having specific projects in mind is good too. If you'd like to see a tool bought for the space, please let us know why. Ultimately tool acquisitions are decided by consensus at HackRVA monthly business meetings, so please attend if you would like to pitch an idea in person. If you are not able to attend, that's ok too, just let us know on Slack.