1. Approval of Minutes
2. Tier System Designation Workgroup: Status Report
3. Data Warehouse
4. Wireless Policy

Excused: Joseph Calger, Bob Franks, Bob Loessberg-Zahl, Celeste Rose, Steve Roth, Kathi Sylva, and Carol Wall.

Absent: None.

Guests: Sandra Stewart, Ray Reveles, and Hebert Diaz-Flores.

Staff to the Council: Randy Moory, and Babette Schmitt.

1. Approval of Minutes - Chair Smiley

   Chair Smiley asked the Council for approval of the May minutes. Council requested that the minutes for the Data Warehouse Project Update (Item V) be changed to reflect that the $90,000 in quantifiable benefit is only a portion of the total benefit achieved by the project.
   
   Council approved the minutes as amended.
   
   Chair Smiley announced that PricewaterhouseCooper auditors would be on campus the week of June 25. The audit team led by Lori Hanover will examine the campus' information systems as part of a University-wide financial audit.
   
    
   

2. Tier System Designation Workgroup: Status Report - Director Moffitt

   Lana Moffitt, Director of Information Resources and Chair of the Workgroup, provided an update on the definition of criteria for assigning Tier 1, Tier 2, and Tier 3 status to campus computing systems. The workgroup is assessing the following criteria: project funding, use of standards, interoperability with other systems, and relationship to the UC-wide New Business Architecture (NBA). Moffitt indicated the group continues to refine these criteria over the next few weeks, using the NBA for guidance.
   
    
   

3. Data Warehouse - Director West, Analytical Studies

   Handout: Data Warehouse Scope

   Caroline West reported that she has established a team to provide oversight and governance for the Data Warehouse project. West reminded the group that she sent email describing possible directions the Data Warehouse project could take during the next year. She requested guidance from the Council on the priorities for next year and on the proposed governance structure.
   
   West reported that the project would need staffing support from the University before the biennial budget process. Annual support requirements for the Data Warehouse will be approximately $500,000.
   
   The discussion with Council members focused on the following:

   • The progress the Data Warehouse project has made on addressing the benchmarks requested by the Council a year ago. West reported that the project team addressed all the benchmarks except for the strategic planning that needs to await further development for the New Business Architecture. The project team has also not spent the time to build an employee module cube since they have already demonstrated their ability to integrate several data sources through another project.
     
     
   • The ability to use a single user ID and password to access various systems. This level of integration would eliminate the current need for multiple user IDs and passwords. A portal may provide a single access point into many systems, but it may not totally eliminate the need for multiple passwords.
     
     
   • Data integration. Members addressed the importance of a single repository for person data, the person registry, and the need for applications to share common data about people in an enterprise directory. The current version of the data warehouse extracts information from source data repositories and integrates it into a common data structure. It was noted that the data warehouse might already provide functions common to the registry. It provides a history of information.
   
   Council members strongly stressed the importance of integrating campus systems, including DaFIS, Banner, Payroll Personnel (PPS), as well as other existing and new systems. Members noted that the current lack of integration and the need to focus on integration issues must be addressed before proceeding with other proposals. It is equally critical to address issues related to data integration before data can be shared between systems. The Payroll and Personnel System (which is maintained by UCOP) might pose the greatest challenge to systems integration. On the other hand, with its next software release later this fall, Banner will be moving closer to integration with enterprise directories. The DaFIS team is considering using a common enterprise directory.
   
    
   
4. Wireless Policy - Vice Provost Bruno
   
   Vice Provost Bruno reported that a number of wireless networks have been deployed in the last few months on campus. While increasing users' mobility, these ad hoc deployments have created a number of issues that the campus needs to address, including:
   • The type of technology deployed and stranded investment costs
   • Possible breaches in privacy and security
   • Interference between various types of wireless equipment (such as telephones, appliances, audio speakers, and research equipment).
   
   To address these issues, Dr. Bruno recently charged a new workgroup with developing a campuswide policy on wireless technology. The workgroup includes Dave Klem, Bradford Luten, Randy Moory, and Bob Ono (Chair). The draft policy should be completed by July.
   
   Dr. Bruno noted that the responsibility for wireless deployments should be shared by campus departments and Information and Educational Technology (IET). He suggested that IET be responsible for wireless deployments over the campus common areas and that individual campus departments be responsible for networks deployed within their buildings.