Home Campus Directory | A-Z Index
  1. Software for student use as a class requirement, installed on the system:
    1. To have software installed and ready for students to use as a course requirement, the Instructor should present the software to the campus Network Services Office (NSO) 60 days prior to the start of the fall term.  In cases when the software is not available to meet that deadline, the software will be ready for use upon clearance no more than 60 days after it is presented to the campus NSO.  Instructors who present software later than the pre-semester date will adjust their respective syllabi to reflect the delayed availability.
    2. For the spring term, it is requested that instructors present software no later than November 1st to allow for holiday and break time when the campus is closed.   Instructors who present software later than the pre-semester date will adjust their respective syllabi to reflect the delayed availability.  Cleared software will be available no later than 60 days after presentation to the NSO.
    3. Presentation of licensing documents for the software for NSO files is the responsibility of the requesting faculty member.
    4. Testing of the software will be the responsibility of the employee.
    5. Software will be made available on the network for use following testing and establishment of appropriate licensure.
    6. The NSO may participate in bulk purchase of software if it is appropriate.
  2. Software for employee use only on machines that are university property on dedicated machines:
    1. Specific software to be installed should be University-owned.  Software with personal licenses held by the employee should not be installed on University machines.   The campus NSO should hold the license.  An authorization sign-off by the campus DAA will be required.  This provision includes demo, approval, or trial academic software from a publisher or manufacturer or public domain software.
    2. If proper licenses are in order, the NSO will install the software in 2-5 working days from the date it is presented by the employee.
    3. Testing of the software will be the responsibility of the employee.
  3. Student or employee software for use on non-dedicated machines (e.g. free-standing machines in the Library):
    1. The campus NSO will not be responsible for the computer’s integrity if it is not on the campus network.  Likewise, the NSO will not be responsible for the operation of any student- or employee-installed software on any non-system machine.
    2. In the event of malfunction, the NSO may offer limited support to resolve hardware or operating system (OS) issues.  The rule of thumb from the Commonwealth College campuses in general will apply: the NSO will devote no more than two hours to fixing the problem.  If it cannot be resolved in that time, the unit will be restored to its original configuration.
    3. The NSO will not be responsible for software or data on any non-system machine.  The user operates at his/her own risk.
  4. Faculty members who elect to sign off for authority to install software on their dedicated machines:
    1. The same caveat as that for non-system (free-standing) will apply for employees who take responsibility for loading and maintaining software on their dedicated machines.  If the software causes a problem, the NSO will not be responsible for either the software or any data on the machine.
    2. The same two hour rule of thumb will apply to machines under individual employee control.  After two hours, if the problem cannot be resolved, the machine will be restored to its original configuration.
    3. The employee who signs for the authority to install personal software will be responsible for any network problems that personally-installed software may .  Any faculty member with multiple machines must sign a separate document for each unique machine.
  5. Note:  as of January 1, 2002, anyone running any system lower than Windows 2000 must sign for personal responsibility concerning the machine in question.
  6. NSO functional priorities will be processed as follows, from the highest priority to the lowest:
    1. Problems that affect the entire system and all users.
    2. Problems that prevent individual users from accessing the system (i.e. logging on).
    3. Problems with software on the system required for student use for course work.
    4. Hardware problems with faculty/staff computers.
    5. Installing/testing software (on the system) required for student use as a course requirement.
    6. Installing/testing software (on individual computers) for faculty/staff for individual use.
    7. Software problems in cases in which the user has installed his or her own software on an individual assigned machine (having signed off for such authority).

Revised 1/15/2002