CSUSB - Technology Advisory Council

See All Minutes

Technology Advisory Council Meeting Minutes - October 3, 2003

Attendees: : Kurt Collins, Bill Takehara, Dick Botting, Tony Coulson, Jim Monaghan, Owen Owens, Steve Cuddigan, Jason Reimer, Mike Ross, Ramiro DiazGranados

Sub Committees
Platform standards ?Ian Jacobs was not available to give a report. The Committee was reminded that the goal is not to buy computers this year but to establish standards

The issue of virus software was brought up. There is software that can push virus scan software. There are other solutions for different operating systems for desktop machines like linux and Mac. A question was asked about the impact and feasibility to make this happen. It might be necessary to get away from Windows environment in servers as well. IBM has a virus proof server but it is very expensive. Should this be a separate sub committee? No consensus was arrived at.

New Initiatives / Strategic Directions - No one was available to report.

Training Committee ?No one was available to report

Distributed system central servers ?committee has agreed to continue meeting to make this work because it needs tech time.

Telecom Chargeback ?This report is delayed because a greater breakdown of data collected by TNS is needed. Current issue: the many unseen costs of the telephone system are being covered by TNS. The goal is to cover all the charges for upgrades and maintenance for the phones and phone system.

It was suggested that people other than Technology Advisory Council members be on the Sub Committees. There is a great depth of people on campus and it would prevent BATS members from being overwhelmed. A thought was that the sub committees should possibly drive the Technology Advisory Council.
All BATS Sub Committees are to establish a schedule by the second BATS meeting. The BATS Chair is to be advised of the schedule. A motion was made that the Sub Committees should be meeting every two weeks and the suggested time is on Fridays at 1:00 pm and 3:00 pm. The motion was seconded and passed unanimously.

ADA Interim Policy ?Mike Ross presented the interim policy and gave background information. 204 web sites and web masters have been identified. There is a web tool that will be used to identify sites not in compliance. This policy is an awareness tool. ACM is looking for feedback from BATS. A presentation from the ADA Compliancy Policy Group has been requested and Mike Ross will make arrangements for this to happen at the next meeting. BATS is to review the interim policy and give feedback

Computer Inventory software –The Council of Deans wants a concrete count of how many computers there are on campus. The consensus of the group was that using push technology to achieve this goal was okay. To make push technology work a software program would need to be loaded on to each machine either through a button clicked on at a web site or someone going to each machine. A concern is that this issue requires a written policy to be created.

Advantages and Disadvantages

Aids in security updates and application updates

Adds a lot of time and responsibility for each different configuration

Is risky if a “push?doesn’t work right

It was suggested that a cost benefits analysis be done along with the feasibility then list the factors that impact campus cost benefits. Another suggestion was that a mixed strategy is needed for implementation. Jim Monaghan is going to send a query to the CATS listserv.Owen Owens is to send one to his as well.

TOPICS NOT ADDRESSED

The misuse of Technology ?something for Committee to think about. Details are sketchy. A suggested interpretation is illegal software like Kazaa

Meeting Maker license renewal - Is BATS going to buy it?

The next BATS meeting will be on October 17, 2003 at 1:00 pm in PL-002, ACM’s conference room.

Minutes compiled by Michelle Behne