IT Architecture and Infrastructure Committee (ITAIC)

Charge

The IT Architecture and Infrastructure Committee (ITAIC) provides input on foundational IT services such as the data and voice network, email, calendar and productivity tools, as well as IT infrastructure services provided at scale, such as database, data center colocation, servers, storage and backup, and more.

Scope

  • The scope of ITAIC review and recommendation is campus wide core technology systems and services.
  • The ITAIC has an advisory role to the CIO and the Academic Senate CIT committee.

Membership

ITAIC membership is designed to be representative of campus IT leadership. 

ITAIC Committee Members (By role, voting member in bold)

Committee Chair (UC Berkeley CTO)

Bill Allison

Committee Co-Chair

TBD - selection by nomination & committee vote

Interim AVC-IT & CIO

Gabriel Gonzalez

Information Security (CISO) Allison Henry*, Charron Andrus
Campus Privacy Officer Scott Seaborn
College of Engineering (Assistant Dean) Eric Fraser
Faculty Representative (Academic Senate CIT Committee) Anthony Joseph
IT Client Services (Director) Jerry Yerardi
IT Council ( (Principal Chair and co-chair or assigned delegates from ITC) Edgar OrtegaCarolyn Knight
College of Letters & Sciences Amy Robinson*, Edgar Ortega
Library (Associate University Librarian for Digital Initiatives and Information Technology) Salwa Ismail
Professional Schools - Haas School of Business (COO) Courtney Chandler*, Pierre Chew, Phil Mahoney
Research, Teaching & Learning (Exec Director) Shawna Dark*, Erfan Mojaddam, Ken Lutz, Owen McGrath
Student Affairs/IT (Associate CIO) Anne Marie Richard*, Tuan Nguyen
Student Tech Council Cristóbal Olivares (convener of student attendees and undergraduate & graduate student votes/input)
University Health Services (Healthcare Technology Director) Jeff Kreutzen

Non-Voting / Ex-Officio Members

bIT Infrastructure Services Director Dave Browne
bIT Telecom/Network Manager Isaac Orr
bIT Campus Applications & Data Exec Director Jody Couch
bIT Data / Platform Services Director Walter Stokes
bIT Enterprise Data & Analytics Director Daniel Grieb


*These members have agreed to be responsible for their votes, and for understanding the content and strategic position of ITAIC decisions, but may employ delegates (listed beside their names) who will be the regular attendees in meetings. This will help the committee keep senior leaders engaged in important IT architecture and infrastructure decisions while accepting the realities of their busy schedules.

IT Governance Program Chart (2022)
select image to enlarge

ITAIC at a Glance

Upcoming Meetings:

Past Meetings:

Committee Documents

ITAIC Sub-Committees

  • Campus Infrastructure Architecture Team: CIAT provides cross-technical review of strategic policies, procedures, infrastructure and services for secure and robust campus IT architecture.
  • ITAIC Data Center Strategy Workgroup: ITAIC-DCSW oversees the campus roadmap for computing and storage solution architectures, including the hybrid strategy for public cloud, data center and edge data centers.
  • ITAIC End User Standards Computing Workgroup: ITAIC-EUSCW reviews overall architecture and technology standards used by ITCS and EOS that affect campus end user computing and the Berkeley Desktop.

Areas of Focus

The ITAIC will consider topics related to campus wide foundational technology systems and services for which IT is the functional owner, including but not limited to:

  • Core IT Infrastructure for the University
  • Core IT architecture for the University
  • Enabling IT services for the University

Procedures

  • Meeting frequency – Twice per semester. The Committee will determine modifications to the meeting schedule as needed based on current activities.
  • Time Commitment – In addition to the scheduled meetings, members can expect to spend 2-3 hours between meetings reviewing related material.
  • Meeting structure – The chair or a designee will collect agenda items and circulate agendas in advance of each meeting to ensure informed discussion of scheduled topics.
  • Reporting – The co-chairs will report on decisions.
  • Documentation of proceedings – All meetings will have notes of discussions, recommendations, and action items.
  • Voting – Quorum is 70% of voting members; one vote per person.
  • Sub-Committees/Working Groups – Additional ad hoc sub-committees or working groups may be established to work on specific projects or topics as needed.
  • Committee Support – The Office of the CIO will provide administrative support as needed by the co-chairs.

With these guidelines as a basis, the ITAIC will determine its need for other operational procedures. Questions may be directed to Berkeley CTO Bill Allison: cto@berkeley.edu