CSUS Baseline Software Configuration

The CSUS BATS (Baseline Access Training and Support) Ad-hoc Recommendation Team, following the lead of the CSU's Integrated Technolgy Strategy (ITS) and serving under the guidance of the CSUS BATS Ad-hoc group, has developed a system for reviewing, selecting and defining a "baseline" set of software. The baseline software set promotes a consistent application environment, current software technology and improved support. In advance of the Spring, Summer and Fall semesters, a new software set is defined and adopted. The software set provides the base application environment for all CSUS BATS funded computing lab workstations (http://www.csus.edu/uccs/labs) and University Labs newly configured workstations.

Faculty, staff and students may submit a review request to add, change or delete an item from the baseline software set to the BATS Ad-hoc Recommendation Team (BAHRT). Faculty and college-based staff should make their request through their College Information Technology Consultant (ITC); non-College based staff through a University Labs ITC; and students through their faculty. For a list of ITC contacts, go to http://www.csus.edu/uccs/helpdesk/itc.stm.

BAHRT has created selection criteria when considering requests for software to be added to the baseline software set. Before submitting your baseline software set modification make sure your request meets the selection criteria below:

a)Software must be either site-licensed, licensed for every BATS lab station, freeware or permitted by the software company. A software company may state, using company letterhead, permission to install their software on each computer within a BATS-funded lab.

b) Software must be compatible with the lab environment. This includes the operating system, network OS, baseline software and discipline specific applications.

c) Software is deemed cross-discipline (can be used by students of more than one department or College).

d) Installation and maintenance requires reasonable staff, computer and network resources.

e) Only one version of an application is permitted, usually the latest version.

f) Software installation request must meet the deadline imposed by BAHRT. The proposed deadline is one month previous to the beginning of the semester.

g) Software must be Y2K compliant.h) Anything not cover by this criteria or exceptions to this criteria will be decided by BAHRT via consensus or vote.

i) If discipline specific software conflicts with baseline software, then the conflict must be communicated to BAHRT. The conflict will be prominently posted and must be addressed at the next BAHRT meeting.

j) The software does not require user specific setup or configuration. 

The current baseline software set for the Windows Platform can be found online.

Last Updated: January 10, 2007