1. Announcements and Introductions - Alan Laub

2. Data Warehouse Project

3. MyUCDavis Presentation by Steering Committee - Bob Franks

4. Contract with Oracle for Database software and tools - Kent Kuo

Absent: Carol Wall.

Staff to the Council: Ian Blake, Gilda Garcia, Bob Loessberg-Zahl, and Randy Moory.

Guests: Joyce Johnstone, Kent Kuo, Donna Olsson, Kelly Ratliff, Ray Reveles, and Sandra Stewart.

1. Announcements and Introductions - Alan Laub

   Dean Laub announced that the June meeting is rescheduled from June 5 to June 12. In addition, there will be no meeting in July.

   John Bruno announced the outcome of the request for proposals for outsourcing the campus modem pools. Three proposals were received from Pacific Bell, AT&T, and Coastal Web Online. The Pacific Bell proposal offers a cost less than the current campus expenditures, covers a larger geographic area than the campus modem pools, and provides a migration path to DSL. The AT&T proposal was very expensive. The proposal by Coastal Web Online offers free service but requires advertising on the Web pages.

   John Bruno emphasized that an outstanding issue remains about charging for this service to recover costs.

2. Data Warehouse Project
   1. Budget and Planning Review
      Handout: Data Administration Planning and Budget Analysis (May 8).

      Bob Loessberg-Zahl reported on the review by the Planning and Budget Office. The Planning and Budget Office recommended funding the completion of the pilot project through June 30, 2000. The Office recommended against permanent funding for the data warehouse project but recommended that the Council consider extending the pilot data project with limited funding.

      Council members asked questions regarding the strategic objectives of the data warehouse project. Members inquired about the demands for the data warehouse. Other council members asked whether the Planning and Budget Office proposal provided sufficient funding to move the project forward, and whether there were additional risks by moving forward with the reduced project scope.

      Council members asked about the technical construction of the data cubes and the need for the project to extract data from additional data sources.

      Action: The Council requested the Planning and Budget Office, Office of the Vice Provost-Information and Educational Technology, and Data Administration jointly meet and confer on the project recommendations. The Council also asks that the outcome of the meeting be communicated to AdC3 members via email within 2 weeks (May 29) so the Council can consider the recommendations.

       
      

   2. Technology Review
      Handout: Technology Review of the Data Warehouse Project (May 5).

      John Bruno reported that the Data Warehouse project review was the first time such a review was conducted on this campus. He suggested that the process might improve if the reviewers were given additional time to meet and discuss their independent reviews.

      Randy Moory reported the results of the review and recommendations from the Office of the Vice Provost-Information and Educational Technology. The Technology review focused on the dimensional analysis and extraction, translation, and loading tools used by the project. Nine recommendations were made including the evaluation of "data cube" linkage for the dimensional analysis tool. The project should also focus more effort on the extraction, translation, and loading processes to improve efficiency and data quality.

       
      

3. MyUCDavis Presentation by Steering Committee - Bob Franks
   Handout: Implementation Schedule and Communication Plan (Excel file) (May 8).

   The MyUCDavis Steering Committee reported to the Council on the status of the project. Joyce Johnston reported that the project would initially provide a Web portal to students and faculty. (A staff portal is scheduled to be ready by winter quarter, 2001). A beta version of the faculty and student portals will be tested in early fall, 2000 in the College of Engineering. A soft rollout to the remainder of campus students and faculty will occur in late fall. The sponsors wish to give the project a low profile so the project team is able to evaluate and fix problems before a campuswide rollout.

   Council members noted the need to educate faculty, students, and staff about MyUCDavis, its rollout and its use requirements (including Kerberos authentication).

    
   

4. Contract with Oracle for Database software and tools - Kent Kuo
   Handout: UC-wide Oracle Contract Proposal, May 1.

   Kent Kuo reported the status of the contract with Oracle. Although it is a system-wide contract, and as such plays a major role in the negotiations, the Davis campus is the major user of the software. Kent reported that contract negotiations are scheduled to be completed on May 24. The new license fee is based on the number of power units used. That number is determined by the size and number of CPU's running the software.

   Council questions focused on the cost impact to administrative computing systems. Kent noted that it is easier to distribute costs to actual users with the new contract. System upgrades in the future will raise Oracle licensing fees.

   Council members noted that the new licensing structure could lead towards a more centralized approach. In addition, the license provides an incentive to increase sharing of resources.

   Action: The Council requested further updates on the status of the contract as negotiations proceed.