As budgets go through lean and fat years, the most effective method I've
found in keeping departmental labs from proliferating it that we maintain
and upgrade the "central" labs but don't do the same for departmental
labs. Over time, only those departments with a strong need to maintain
their own labs continue to do so, and we have no problem with that.
Also, our central labs setup is overseen by representatives from each of
the colleges, so the departments get to have input on what software and
policies will be available in the central labs. I think that helps.
At 04:50 PM 5/29/2003 -0400, you wrote:
>I'm looking for folks to whom the solution to the problem of
>departmental lab proliferation is "old hat." I'm sure some of you have
>wonderful policies and/or procedures in place to manage the creation of
>new departmental labs, their maintenance, upkeep and replacement. If
>so, would you please share?
>We decided two years ago to include lab computers in our three-year
>refresh cycle. It has been problematic to convince departments that "I
>want my own lab" is not a good enough reason to create and maintain
>one. On the other hand, there are certainly programs that have specific
>enough needs to justify a specialty lab. Another problem is that having
>an existing lab does not necessarily mean that it should be continued.
>Any suggestions would be gratefully accepted!
>Eastern Michigan University
>Participation and subscription information for this EDUCAUSE Constituent
>Group discussion list can be found at http://www.educause.edu/memdir/cg/.
Participation and subscription information for this EDUCAUSE Constituent Group discussion list can be found at http://www.educause.edu/memdir/cg/.