The Computer Resources Committee was directed in 1986 to review all purchase orders involving the acquisition of computing resources. The intention was, and still is, to determine whether orders are complete and accurate (compatibility of components ordered; interface cards, cables, other peripherals and parts of the system are included as needed) and to alert offices purchasing the equipment of new developments or changes that may affect their order.
Goals:
To review all campus purchase requests for computing resources regardless of the funding source
To create lists of recommended computer resources (peripherals, software) and their source
To establish a means of notating whether an individual has had pre-purchase consultation (see Campus Computer Purchase Programs above)
To advocate purchasing activity by a department which is consistent with its computing plans and direction
The increasing number of personal computers on campus, and their role in academic instruction and daily activities, necessitate an effective and responsive maintenance program. In addition to training technicians to repair equipment, it will be imperative to establish a maintenance process which minimizes down-time.
By 1993, it is expected that the campus computer maintenance system will be sufficiently complete that it can handle on-campus maintenance for all but large system-level resources, and yet remain flexible enough to change with campus requirements. An equipment testing and replacement schedule will also be in place to actively prevent problems.
Goals:
To train technicians to repair equipment supported by the campus and purchase programs (Apple //-type, IBM-PCs, Macintosh and Zenith)
To establish a one-hour maximum downtime limit, during normal business hours, for communications/networking problems
To establish a 24-hour maximum downtime limit for individual user or department equipment failures
To establish a single point of contact for all campus computing users to call when they have communications/networking problems or equipment failures
To establish simple diagnostic and preventive-maintenance procedures which can be handled at the individual user or departmental level
To establish a campus- and departmental-level maintenance funding pool to cover maintenance and repairs
To acquire loaner equipment to replace personal computers which are out of service due to repairs
To establish a plan for receiving campus computing resources which includes the following:
* completion of warranty/registration materials for software and hardware
* bar coding each major piece of equipment for inventory and maintenance of a equipment repair history
* creating an equipment repair history record which is identified through the equipment's bar code sticker)
* a maintenance plan for each major item (e.g., purchasing an extended warranty)
* setting up, testing and "burning-in" new equipment
* notifying the destination site of the arrival of their equipment
Computing resources at Potsdam College are particularly precious and their security should be of utmost concern to insure against their loss or damage. This includes software, hardware and the information created with these resources. While the potential threat of computer viruses is currently receiving widespread attention, the threat to our resources from much more conventional means--illegal copying (see Software Policy), theft and mischievous vandalism-- is of far greater concern for our campus. The goals described below are intended to provide preventive as well as corrective measures.
Goals:
To establish a sign-up process for the use of Potsdam College computing resources which outlines user responsibilities and requires a user's signature
To formulate and publicize regulations and guidelines for the use of computing resources and services
To establish and inform users of consequences for violating those regulations covering the use of computing resources and services
To establish prevention, detection and correction measures for computer viruses