Acquisitions: Difference between revisions

From HackRVA
Jump to navigation Jump to search
No edit summary
No edit summary
 
(26 intermediate revisions by 4 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/18NhVr7y7k46h6UP9wydMZUSUh-GcKaK5ycsZNGL8brQ/edit#gid=1340858507/ Acquisition Spreadsheet]
[https://docs.google.com/spreadsheets/d/1EQms1Ybk1Z9l_GXbuQfbKt3rMEz0lhtF/edit#gid=1924919744 Acquisition Spreadsheet]


Current purchase research:
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]


'''Guidelines:'''
'''Guidelines:'''


None or all of these can be successfully answered, but it's the questions we consider when we spend HackRVA member money.
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?
Line 12: Line 20:
- Is it a "key" tool that all makerspace, hackerspace, fab labs should have?
- Is it a "key" tool that all makerspace, hackerspace, fab labs should have?


- Does it create opportunities for a workshop or a core learning opportunity for HackRVA members?
- Does it create opportunities for a workshop or a sweet learning experience for HackRVA members?


- Does it solve an existing problem?
- Does it solve an existing problem?


- Does it solve a problem we'd like to have?
- Does it solve a problem we'd like to have?
- Does it serve the HackRVA community interests?


- Is there someone to maintain and be the "keeper" of the tool?  
- Is there someone to maintain and be the "keeper" of the tool?  
Line 24: Line 30:
- Are there training or workshops designed around the tool?  
- Are there training or workshops designed around the tool?  


- Is it a 'key' tool that all makerspace, hackerspace, fab labs should have?
- Are there specific awesome projects related to that tool?  


- Are there specific projects related to that tool? If so let us know which?
- Are there specific sweet events facilitated by that tool?  


- Is it a tool that's going to last and be robust under amateur use?
- Is it a tool that's going to last and be robust under amateur use?
Line 32: Line 38:
- Will it fit in our space... like physically?
- Will it fit in our space... like physically?


- What are the costs associated with upkeep or lots of people using it?
- What are the costs associated with upkeep? Especially with lots of people using it?


- Is there a software component? What is it and how will it be integrated?
- Is there a software component? What is it and how will it be integrated?
Line 41: Line 47:
'''Additional Thoughts:'''
'''Additional Thoughts:'''


Getting new stuff for the space is exciting! There are so many cool potential things we'd like to have. 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.  
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.
''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. Maybe it's just super useful in ways we haven't thought about. But we're actively seeking member/tool combos so that we get the most value for our community.
If you'd like to see a tool bought for the space, please let us know why.  


Having cool stuff is great, having a bunch of people using that cool stuff is even better.
Having cool stuff is great, having a bunch of people using that cool stuff is even better.


Ultimately tool acquisitions are decided on by consensus at HackRVA monthly business meetings, so please attend if you would like to pitch your idea in person. If you are not able to attend, that's ok too, just let us know in an email why it would be a great item and we'll put it out there at the meeting. And log it on the spreadsheet with a link.
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 in an email and log it on the spreadsheet with a link.

Latest revision as of 02:45, 16 June 2021

Please submit acquisition requests and suggestions on this spreadsheet:

Acquisition Spreadsheet

Current purchase research:

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 sweet learning experience for HackRVA members?

- Does it solve an existing problem?

- Does it solve a problem we'd like to have?

- 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?

- Are there specific sweet events facilitated by 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 associated with upkeep? Especially with lots of people using it?

- Is there a software component? What is it and how will it be integrated?

- Is it just so mind-blowing we have to have it!


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.

Having cool stuff is great, having a bunch of people using that cool stuff is even better.

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 in an email and log it on the spreadsheet with a link.