Changes

:When supporting computer systems the overseer (whether for business or volunteering purposes) becomes responsible for its protection and the its efficient operation. In this case, the volunteer becomes the "caretaker" of this system, and deals with a lot of issues that are usually "hidden" or "ignored" by the users of the system. This is not to point the blame at the user, but to emphasize the human nature of '''"out of sight, out of mind"'''.

:IT volunteers deal with many "behind the scenes" issues such as '''computer server backup''', '''running benchmarks''', '''Internet Security''', '''application installation''', and '''user documentation'''. Therefore, when users or instructors do not properly remove completed files from the computer system, it becomes yet another task that the computer administrator has to "deal with". In fact, the problem becomes compounded when the administrator is not certain whether or not the files are permitted to be removed, and may have to track-down the instructor to get permission to remove the file.

:Therefore the there is a tremendous need for operational mechanisms such as '''policies and procedures'''in the church's technical areas. In a sense, these guidelines become the '''"glue" ''' that helps to maintain holds the smooth operation of the computer labchurch's "system" together. Without policies and procedures there would be ''duplication'', ''miscommunication'', ''inefficiencies'', ''hurt-feelings'', and general ''chaos''.

'''The following table displays ===Policies / Strategies to Ensure a comprehensive "system" incorporating a series of computer lab automation and configuration combined with education and reinforcement (combined with policies and procedures) to help "distribute the load" among computer lab administration and computer instructors/endSmooth-users:'''Running Computer Lab===

:The following table displays a comprehensive "system" incorporating a series of computer lab automation and configuration combined with education and reinforcement (combined with policies and procedures) to help "distribute the load" among computer lab administration and computer instructors/end-users:  :<table border="1" cellpadding="2">

====="It Takes a Community to Raise a Computer Lab"=====

:In this exciting and critical phase of the Westminster Computer Lab, ALL participants (not just the AVIT deparment and AVIT volunteers) have a "stake" in the success of the computer lab's success. Therefore everyone taking the time to correctly following the policies and procedures is essential to the growth and success of this unique and special resource!