Lab Leads Program Summary
Purpose:
- We recognize there is a gap in some skill sets in our grad students. As a result, we will provide additional training in system admin, security, and good lab admin’ing practices.
- We plan to have 1 meeting during the semester where we bring together all the lab leads to discuss various security topics, and to hear what issues they are running into in their labs.
- We are setting up a Microsoft Team to help facilitate communication and share any information that we receive in a quick and timely manner.
Benefits:
- As security issues arise, techstaff can work directly with your lab lead to ensure your lab takes the appropriate actions.
- As VT policies and procedures continue to evolve, your lab lead can provide direct input on how changes will impact your lab. This will allow us to feed info back to the appropriate individuals.
- In addition, as things change, by working with your lab lead, we should be in a much better position to plan the rollout, as opposed to reacting.
- As you or your students identify technology gaps, your lab lead can communicate those needs to techstaff. Techstaff can then evaluate what technology needs to be implemented to better support research activities.
Once you identify the person(s), you decide what role the lab lead plays in your lab. On one end, this person could just be a conduit of information between techstaff and your lab. On the other end, they may be your one-and-only system administrator. Techstaff doesn’t care. You decide what makes sense for your situation.
FAQ:
- If Rob is admin’ing your systems, do you still need to identify a lab lead? Yes, techstaff suggests you identify a lab lead. In this scenario, this lab lead is sharing information and representing the needs of your lab. Many of the things shared in the meetings will have a direct impact on your lab.
- Can you identify more than one? Yes. Probably no more than 2.
- Are we cutting out/by-passing faculty? No. Techstaff will continue to keep faculty informed as appropriate.