Information Technology Committee Meeting Notes
Date: October 24, 2000
Time: 9:30-11:30
Location: McHenry Library – Room 325
1. Welcome and introductions - Larry Merkley
The committee introduced themselves to each other, and Merkley proceeded to provide a detailed background description of the events that led to the creation of the ITC and his appointment as the ITC chair.
Those present were:
2. Expectations and Background -- John Simpson
§ The committee members introduced themselves to the Executive Vice Chancellor.
§ Simpson outlined the fundamental basis for the committee structure he is forming.
o Simpson’s aim is to “Build the Best Institution We Can.”
o The committee structure is not designed as a representative form of governance.
o The committees are to provide Simpson advice which focus on the best interests of the campus from an institution-wide perspective.
o The new committee structure was discussed with particular emphasis on the recent history and structure of UCSC Information Technology committees, and the basis for Larry Merkley’s appointment as the campus CIO, and chair of the ITC.
o The role of the Information Technology Committee (ITC) is to advise Simpson and the Provost Advisory Committee (PAC) regarding Information Technology Policy and Resource decisions including:
§ All Information technology issues whether originating from Academic, Instructional, or Administrative initiatives.
§ Information technology critical to the future of the campus.
§ Strategic and tactical advice regarding large to moderate information technology issues.
o As a part of adopting a campus-wide perspective the ITC is expected to converse, consult, and recruit other individuals, committees, divisions and organizational units from within the campus and elsewhere to inform issues.
o Simpson suggested that the scope of the committees deliberations might include:
§ Large Near Term issues such the Planning and Implementation of the Academic Information System; and
§ Longer Term issues such as the development of a formal Campus IT Strategic Plan.
o Simpson concluded by stating that the ITC is considered a critical part of the university’s future and there is currently a great deal of interest in adding more representatives. He prefers to hold off making more appointments for the time being.
3. ITC Objective – Larry Merkley
Merkley proposed that the committee consider as it’s initial objective to: “Ensure that the campus investment in information technology meets the evolving information needs of the campus community.” There was general consensus from the group that this objective was consistent with the charge that Simpson had delivered and was also modest and flexible enough to provide some initial focus to committee activities.
4. ITC task categories - Larry Merkley
Merkley identified and discussed several categories of tasks which the committee should consider:
§ What are the baseline requirements for the system?
§ Are these baseline requirements being met?
§ Is the funding adequate to satisfy these baseline requirements?
§ Are people getting what they need from the system?
Committee discussion also identified the following perspectives:
§ Service reviews should be conducted in the context of the campus strategic planning process.
§ Service reviews should be viewed from the campus perspective rather than only where the current funding for the service resides.
Action: Merkley agreed to organize and distribute a list of these items to committee members in order to establish the range of issues, and encourage a process for committee consideration.
5. ITC Task Management Approaches - Larry Merkley
Merkley reviewed a list of management approaches which he proposed be used initially. These included:
6. ITC Values - Larry Merkley
Merkley introduced a set of values that could be used in guiding committee processes. His presentation and subsequent committee discussion established the following:
§ Is there a place for regular student representation on the ITC? It was agreed that student representation would add a valuable perspective, it was agreed that this question would be followed-up on.
Action: Larry Merkley indicated he would explore the possibility of adding a student perspective to the ITC membership.
§ How should members represent their role on the ITC to their constituents, and how do members represent the views and experience of their constituents to the committee? It was concluded that although the ITC membership must fulfill their charge to provide a strategic campus-wide perspective, each member in fact represents a particular functional part of the campus IT system and brings their own personal expertise as well as their relationship to their colleagues to bear on these issues.
7. Activities to Date - Larry Merkley
Merkley provided a brief update on some recent IT activities.
Action: Stephen Hull agreed to send the Data Warehouse Review guidelines to the ITC committee.
§ A document was distributed (Appendix 2) which provided a conceptual model for a financial assessment of campus IT systems.
8. Getting Started - Larry Merkley - Background information
The following documents were listed as valuable background material that should be viewed as a means of identifying key principles:
Action: Stephen Hull and Larry Merkley will develop a set of principles from this document and distribute to the committee.
o "University of California, Santa Cruz Academic Information System: Final Report and Recommendation of the AIS Project Team" – Provided by Mark Cianca.
o Several additional items were identified during committee discussion. These included:
o The E-Berkeley Document: E-Berkeley Task force background and report:
§ http://istpub.berkeley.edu:4201/bcc/Apr_May2000/gen.eberk.html
§ http://campus.chance.berkeley.edu/eberkeley/e-business-96.pdf
and now the E-Berkeley Implementation Task Force:
§ http://campus.chance.berkeley.edu/itf/itf.html
Of note is the "Building e-Berkeley" report
§ http://campus.chance.berkeley.edu/itf/building_eberkeley.html
and the Policy Working Group pages (note recently released report):
§ http://socrates.berkeley.edu:7015/EBITF_PWG/
o UCOP IT Documents: http://www.ucop.edu/irc/reports.html - Including links to:
§ Authentication Workgroup Report
§ Deloitte & Touche Review of Corporate Information Systems
§ Employee Systems Task Force Report
§ Future Directions for the Corporate Information Systems
§ UC whITe PAPERS on Information Technologies
o Further effort should be spent in surveying other possible documents and strategic models.
9. Issues to discuss:
Throughout the meeting specific campus IT issues were raised which have direct relevance to the scope of the ITC. These include:
Action: Mark Cianca agreed to prepare a presentation to the committee at the 11/14 meeting to provide a 30 minute overview of the AIS Selection Process, Lessons Learned, and Plans for System Implementation.
Action: Stephen Hull will notify the committee of the URL of the current draft of the committee webpage.
Action: Stephen Hull will draft the meeting notes and insure they are distributed to Merkley and the committee.
10. Next Meeting:
The next meeting will be held Tuesday, 11/14, from 12:00-2:00 PM, in McHenry Library, Room 481.Agenda Items planned include:
Action: Larry Merkley agreed to contact Janine Roeth, Liz Irwin, and Jim Burns and confirm their availability for presentations at the 11/14 meeting.
Maintained by Stephen Hull, Office of Planning and Budget
Last modified on 11/14/00.