Proposal: Splitting Operations into two new committees

DMS General
1

As the “catch-all” committee, Operations has slowly been accumulating a large number of roles. The committee’s focus is becoming too splintered to be easily maintained. Here are the roles that currently fall under Operations:

  1. Creating and enforcing rules for storage areas
  2. Restocking of general supplies
  3. Restocking, management and repair of general tools
  4. Maintaining general work areas
  5. Restocking snacks (food and drinks)
  6. General safety - First Aid, Fire extinguishers, cleared walkways
  7. Managing trash/recycling contractor
  8. Maintaining network infrastructure and Internet connectivity
  9. Building and maintaining end-user computers (desktops/laptops)
  10. Building and maintaining physical servers and VMs
  11. Deploying and managing the security camera system
  12. Maintaining website infrastructure (main website, forums, wiki, etc)
  13. Deploying and maintaining the access control system (RFID, makermanager)
  14. Managing electrical infrastructure and contractors
  15. Managing HVAC infrastructure and contractors
  16. Managing plumbing infrastructure and contractors
  17. Managing Compressed air infrastructure and contractors

My proposal is to split the Operations committee into two new committees, and divide the responsibilities between them. These would be the Logistics Committee and the Infrastructure Committee, with the following roles:

Logistics

  1. Creating and enforcing rules for storage areas
  2. Restocking of general supplies
  3. Restocking, management and repair of general tools
  4. Maintaining general work areas
  5. Restocking snacks (food and drinks)
  6. General safety - First Aid, Fire extinguishers, cleared walkways
  7. Managing trash/recycling contractor

Infrastructure

Deploying, managing and maintaining:

  1. Network infrastructure and Internet connectivity
  2. End-user computers (desktops/laptops)
  3. Physical servers and VMs
  4. Security camera system
  5. Website infrastructure (main website, forums, wiki, etc)
  6. Access control system (RFID, makermanager)
  7. Electrical infrastructure and contractors
  8. HVAC infrastructure and contractors
  9. Plumbing infrastructure and contractors
  10. Compressed air infrastructure and contractors

Questions? Thoughts?

7 Likes
2

Sounds like a great idea. An unhelpful thought: putting Managing / Maintaining on every line seems redundant / excessive / redundant.

2 Likes
3

Edited to be less redundant.

2 Likes
4

My reflection is that the actual doing is a heap load more than any writing or reading about it, and it reminds me to want to thank our operations volunteers next time I see them. And that is especially true if they are forced to do something to account for me, like clean out storage or organize something, or toss an old food item from the fridge.

I’m not going to do any of those things as an excuse to thank our ops members, of course. Seems to me that all of our active volunteers, from the friendly members who engage with lost-looking visitors to our (mostly) thankless ops members, to those poor unfortunate souls, the board members and committee chairpersons, all earn more thanks than they hear.

Thank you for all do.

Well, that’s what I was thinking when I read the proposal to split. Not really on topic and not very helpful, but it’s what I can offer on the topic.

2 Likes