1. Information Technology Planning Provost Hinshaw’s memo to John Bruno Review budget reduction plans and report on short-term information technology impacts Develop a long-term plan with a two-year horizon that can be updated annually Guide us in the application of our resources to meet the institution’s needs

2. Information Technology Planning New role for CODVC Participate in information technology planning Provide input on campuswide information technology needs Provide input regarding the allocation of resources to ensure greatest strategic effect

3. Information Technology Planning Process Draft plan ready early FQ 2003 informed by: Deans, Vice Chancellors, and Vice Provosts Sampling of Academic Departments, ORUs, and Graduate Groups Requests for local information technology support Mandates Technological constraints

4. Information Technology Planning Process Engage in broad campus review (FQ 2003) Senior Advisors Group/Technology Infrastructure Forum Other groups as appropriate (e.g., WASC follow up) Academic and Administrative Computing Coordinating Councils CODVC Retreat (WQ 2004) VPIET presents draft plan CODVC provides advice to VSH

5. First Round of Visits with CODVC Deans’ Lists Administrative Academic Infrastructure Administrative Units Business processes (New Business Architecture) Support services

6. Deans’ Lists (Administrative) Faculty merit and promotion process multiple systems being developed Online course evaluation Security concerns Contract and grant proposal preparation support Need for faculty and staff support for contract and grant preparation and management Need better information representation of contract and grant activity (reporting on multi-investigator awards)

7. Deans’ Lists (Administrative) Student information system improved handling of graduate students data warehouse development and integration with other data sources, e.g.,IAIS PPS cumbersome and time consuming Not a human resource information system Support for academic senate committees Course approval system Research subcommittee CAP

8. Deans’ Lists (Administrative) Need ability to produce reports based on consistent institutional data Many shadow systems continue to exist to support local needs

9. Deans’ Lists (Academic) Educational Technology (WASC follow-up) Institutional commitment to instructional technology Local support for faculty and staff Research Computing (discipline specific) Cluster computing (array of parallel processors)

10. Deans’ Lists (Infrastructure) Building wiring 100 Mbps (current upgrade to Network 21 electronics) 1000 Mbps (next round of upgrades) Capital project for targeted upgrade of building wiring Wireless Evolving standards Could prove useful in extending the infrastructure Wireless access is increasingly in demand Security issues Collaboration tools Voice, video, white board Bandwidth resource and incidental use

11. Administrative Units Provide online, integrated, and convenient (one-stop) services to students, faculty, and staff (New Business Architecture) Provide online services to an extended community of users Alumni, Parents, Friends of UC Davis, Applicants for admission (undergrads and grads), etc. Accountability/Reporting issues