OIT Faculty Advisory Committee Charter


The Office of Information Technology (OIT) manages critical campus resources on behalf of the UCI faculty and the extended university community. An effective advisory mechanism is essential to ensure OIT operates in harmony with overall campus goals.

Currently, OIT receives advice and input using a variety of informal and formal mechanisms, including the Academic Senior Managers (ASMs), School IT Directors, the Computing Support Coordinators (CSC), and the Computing Lab Coordinators (CLC). The official Academic Senate advisory mechanism is the Council on Research, Computing and Library (CoRCL), where the Chief Information Officer (CIO) participates as an ex-officio member.

The amount of time the CORCL has to deal with computing and network issues is limited as their agenda is full with many other important matters. It has become clear to OIT and others that an additional formal advisory mechanism would be beneficial.

The OIT Faculty Advisory Committee

OIT has created the OIT Faculty Advisory Committee to review current and future computing and telecommunication issues and directions. Parameters of this group are listed below:

  • Meeting Schedule: Approximately every other month
  • Participation: The goal is for the OIT FAC to broadly represent the campus by having a faculty member from each school serve. When no faculty member can be identified, the school IT Director or Assistant Dean participates.
  • CoRCLR Participation: The OIT FAC includes one or more current members of the Academic Senate Council on Research, Computing and Library.
  • ASM/School ID Director participation: One representative comes from the Academic Senior Manager (ASM) group and one from the School IT Directors group.
  • Chair: The OIT FAC is chaired by the campus CIO.
  • Mailing List: The advisory committee may be contacted as a whole via the mailing list “oit-faculty-advisory@uci.edu

Potential Faculty Advisory Committee Topics

OIT will look to the Faculty Advisory Committee to help determine areas for review and participation. Examples of potential topics are listed below:

  • Future services:
    What new services should OIT be investigating? What is the relative importance of “new” technologies such as cloud computing, voice over IP, streaming video?
  • Review OIT services and service policies:
    Enterprise Service offerings and per-user resource allocations; what services might be outsourced and which should not; high performance computing directions.
  • Review relative priority of existing efforts for staff and financial resource allocation:
    Instructional technology/EEE, instructional labs, campus help desk, high performance computing, research computing and networking support, DCS, network consultation, subnet/LAN assistance, network security, e-mail services, indirect support, training coordination, etc.
  • Review high-level network and computing policies as needed:
    Computer and Network Use Policy, UCInet Guidelines, UCInetID allocation/maintenance policy, UCInet access and security policies, etc.
  • Advise on managing/allocating off-campus network bandwidth.
  • Provide input on budget requests and priorities.
  • Provide a conduit for feedback from individual schools and units about current or potential OIT services and activities.
    Advisory committee members can serve as spokespersons for their colleagues to help voice concerns about the quality or nature of OIT services