The meeting commenced at 2:15 PM.
- Approval of Minutes
Chair Matthews asked for comments from the Council regarding the minutes from the April meeting. The minutes were approved as submitted.
- Announcements
Chair Matthews announced that he accepted the position of Faculty Director of the Instructional Technology and Digital Media Center. Chair Matthews notified the Council that he resigned as the Academic Computer Coordinating Council Chair. A request to the Academic Senate was made seeking nominations for a new chair of the Council.
- Report on the Activities and Efforts of the Administrative Computing Coordinating Council (AdC3)
Mary Jo Anderson reported on items before the Administrative Computing Coordinating Council during the past year. Her presentation focused on Security, Data Administration, Administrative System Reviews, the Oracle License, and Campus Information Technology Budgeting.
Security: Mary Jo reported that Disaster Recovery and Business resumption planning received considerable discussion by AdC3. John Bruno added that IT is currently addressing other security issues. The Data Center is preparing a Disaster Recovery plan. IT is undertaking a network vulnerability assessment and selection of the Security Coordinator is near completion. He will report to Provost Grey on the status of information security once the results of the Price Waterhouse Cooper audit are known.
Council comments focused on security risks in DaFIS and the trade-off of additional security versus functionality of the systems.
Action: The Council requested that a report be made to the Council once the current security assessments are complete.
Data Administration: Mary Jo continued her report on the Data Administration project. AdC3 recommended approval of a two-year pilot project. The focus of this project is on data standards, the data warehouse, and strategic planning, including cost benefit. She provided a handout about the data models for the data warehouse pilot to the Council. The data models can be viewed at: http://www.dataadmin.ucdavis.edu/HTML/current_projects.htm under the subject data models.
Council members asked several questions about the data warehouseâs capability to provide access to historic and other types of enrollment data. Mary Jo replied that the warehouse could provide this service and that the process of identifying users of the warehouse would help define the data requirements. Other Council members noted that managing scalability of the warehouse is difficult. A Council member asked whether the system provided an iterative process to help define the decision. Mary Jo responded this was possible.
Administrative Computing Systems: Mary Jo reported on projects that the AdC3 considered.These included permanent funding for DaFIS, the Data Administration Project, the Administrative Computing Plan, and the Student and Employee ID projects.
Council had numerous questions and comments about the Student and Employee ID projects. Council questioned whether the new employee and student numbers would be the ID number. The response was yes. Council commented that the new ID might need the same privacy protection as the Social Security Number.
Mary Jo mentioned that AdC3 observed that many systems hang off campus core systems, (e.g. Degree Navigator and MyUCDavis use the Student Information System). Council discussed the impact of changing core systems and the costs. Council suggested strategic efforts should be done to address change issues.
Oracle Software License and Campus Information Technology Budgeting: Mary Jo reported that the University negotiated a new 5-year agreement with Oracle that gives the campus substantial discounts for Oracle software. She also reported on new planning to integrate information technology budgets with the biennial budget processing.
- Report on Site License Administration at UC Davis
Handouts:
- Site Licence Coordination
- UC Davis Software Licensing Overview, July 2000
- Software Licensing at UC Davis (PowerPoint presentation)
Pat Kava presented the site license administration process for software at UC Davis (See Handout). The presentation distinguished between University licenses, campus licenses, and departmental licenses.
Council asked, How does the University got money for University site licenses. Pat responded that there was recharge from the campuses back to the University. Council asked about how much money the campus saved by site licenses. Council members responded that there was significant savings on individual licenses and that total savings were difficult because purchases were distributed to departments and individuals
- NOAC ResNet Recommendation
Doug Hartline presented the NOAC recommendation for addressing the MP3 (Napster) bandwidth issue at the residence halls. In the fall, the bandwidth to the internal campus will remain at 100 megabits per second, providing students with full access to campus resources. Bandwidth available to the Internet via the commercial circuit will be 10 megabits per second. MP3 traffic will be restricted. In conjunction with the change in network administration, IT will work with the residence halls to produce an educational document about network etiquette.
Council asked whether the approach Davis was taking was different from approaches used by other campuses. Doug replied that there were three methods generally applied. Most campuses follow an approach similar to one chosen. Other campuses ban MP3 and others employ caching servers to cache MP3 traffic to reduce the impact on the bandwidth.
The meeting adjourned at 3:34 PM.