Software Request Policy for Labs & Classrooms
Purpose
|
The purpose of this policy is to centralize acquisition of software at BSC
in order to ensure compliance and compatibility with network
architecture as well as streamline utilization, reduce duplication, and
provide the highest level of support possible. |
Policy Statement
|
All requests for instructional software for use on public computer
workstations in classrooms, computer labs, the library, and other educational work spaces
will be reviewed and approved for purchase through the Information
Technology division. |
Applies to
|
All BSC Employees |
Responsibilities
|
Software requests for campus labs and classrooms will be evaluated and approved through the appropriate
channels, as outlined below:
- Software requests should be submitted to the Software Liaison by the deadlines listed below prior to the
desired semester to ensure enough time for evaluation,
purchase/licensing, and installation. The Software Liaison is responsible for coordinating the efforts of the Information Technology (IT) division as they relate to the processes of software acquisition, licensing, distribution, and overall coordination of all campus software requests. The Software Liaison works to ensure that Faculty software requests are processed in an efficient and timely manner.
| Semester |
Classes Begin |
Software Request Final Deadline |
| Spring |
Third week of January |
October 15 |
| Fall |
First week of September |
April 1 |
- The faculty member completes the online BSC Software Request form at http://it.bridgew.edu/facstaff/softwarerequests/requestform.cfm.
- Requested software must be the most current or -1 version (the most recent previously released version) of the product. Requested software must also be Windows XP or OS 10.3 compliant.
- The requested program will also be assessed for content/function as well
as technical requirements (including compatibility, load testing,
licensing, etc) by the Software Liaison and IT Systems staff. Once the technical evaluation is complete, the faculty member will
be notified of the outcome by the Software Liaison.
- For new software requests, consult your department chairperson and/or school dean for funding for the purchase of the necessary software. Best pricing quotes can be sought through the Software Liaison at bscsoftware@bridgew.edu. The Software Liaison will obtain a quote for the requested software from College approved vendors (or outside vendors in special cases). The Software Liaison will forward the quote to you to pass along to your department chairperson or dean for purchase. Once the software arrives, please provide the Software Liaison with a copy of the software and licensing for record-keeping purposes.
- Building
new lab and classroom images for the new set of software programs, as well as placing
these images on the designated computers, is a time and labor intensive
process. As a result, once new software programs are approved and
purchased, they will be added to the computers only during designated
times each year, coinciding with the start of a new semester. Requests
approved and purchased in mid-semester will be added to the computers for
the following semester. All software installation will be handled by
the IT Systems staff. IT Systems staff will perform basic testing for compatibility with other programs, but is unable to thoroughly test applications.
- IT will evaluate software requests received after the
deadlines (see above) for installation on the Citrix server.
If the software will not work within the Citrix environment, and the request
was submitted within the first 30 days of the semester, IT will evaluate if the
request can be incorporated into the final updated image for
installation at the end of the 30 day period. At that point, all
images will be considered "frozen" and no further changes will be made
until the following semester.
|
Request Form
|
BSC Software Request Form |
| Title: |
Software Request Policy |
| Approved By: |
Thomas Groh, Associate Vice President, College Information Systems |
| Approval Date: |
April 6, 2006 |
| Date of Last Revision: |
February 16, 2007 |
| Policy Category: |
Information Technology Division |