Purpose and authority
The Architecture and New Technology Committee (ANTC) is entrusted with addressing IT issues and proposing recommendations that affect IT architecture and architecture standards, IT common services, and the adoption and implementation of significant new technologies. The ANTC is expected to make recommendations to the Strategic Information Technology Committee (SITC) based on a consensus opinion of the representatives, and in the best interests of the University of Utah as a whole.
Mission, scope and key goals
The ANTC considers architecture and technology-related issues brought forth by faculty,
students, staff, and researchers and seeks solutions that align with the University’s
mission and strategic goals, as well as represent the most appropriate and efficient
decision for the University at large.
ANTC considers programs and initiatives that address central architecture, new technologies, funding, strategic and enterprise programs, and projects affecting units campus-wide, such as:
- Technical architecture
- Application architecture
- Data architecture
- Campus-wide IT policy
- New, current and retired UIT services (strategic fit, funding)
- Ubiquitous, commodity services
- Regulatory change and compliance
- Enterprise projects (big, strategic, cross-functional)
- Special central infrastructure needs
- Security plans and issues
- Integration into central systems
Out of scope issues include, but are not limited to:
- Strategic priorities of the functional groups, such as Student, Finance, HR, and other campus-wide applications
- Individual administrative and academic unit needs that are not common services
- Scheduling and managing UIT resources and operational decisions
- Overall UIT strategic plan
- Analyze, vet and obtain consensus on recommendations for the Strategic Information Technology Committee
- Charter targeted ad hoc working groups to explore and pose solutions
- Manage, approve, and recommend university architecture
- Obtain campus-wide input
- Take action on IT Risks
- Develop unified plans among IT groups on campus
Chair: Mark Beekhuizen, IT director, Quinney College of Law
|Derick Bingman||IT director, College of Architecture + Planning|
|David Blackburn||IT director, Eccles School of Business; voting member|
|Pieter Bowman||Computer operations manager, Department of Mathematics|
|Joe Breen||IT architect, UIT Center for High Performance Computing|
|Steve Dean||IT director, College of Engineering|
|Tim Ebner||Registrar; voting member|
|Jeff Folsom||IT supervisor, Eccles Health Sciences Library; voting member|
|Demian Hanks||IT director, College of Social & Behavioral Science|
|Matt Harting||Associate director of operations and logistics, College of Social Work|
|Matt Irsik||Interim director for user support and computing services, Marriott Library|
|Sylvia Jessen||IT director, School of Medicine; voting member|
|Josna Kotturappa||HRIS manager; voting member|
|John Levandowski||Associate director, Business Analysis and Support Services|
|Jim Livingston||Chief Technology Officer|
|Jim Logue||IT director, College of Education|
|Mike Mcintosh||IT project manager, College of Nursing|
|Chris Roberts||Computer professional, College of Fine Arts; voting member|
|Steven Seal||IT director, College of Health|
|Jon Thomas||Director of Teaching & Learning Technologies|
|Wes Tolman||IT product manager, College of Pharmacy|
|Daniel Trentman||Senior systems engineer, College of Mines & Earth Sciences; voting member|
|Rob White||IT director, Continuing Education & Community Engagement|
|Thomas Wolfe||IT director, College of Humanities|
The voting rights (and thus the voting representative) will rotate among each of the areas once a year.
Responsibilities, roles and duties
All representatives are expected to review governance documents and participate in the evaluation and recommendation phases of the process. Representatives are also asked to act as the first line of communication regarding IT governance to the rest of their academic or administrative unit. Voting bloc representatives will contact the non-voting representatives in their group and other knowledgeable stakeholders in their unit to gather input for the full ANTC. Voting members are expected to attend all ANTC meetings and to cast a vote that represents the collective view of the bloc he or she represents. Members also may be asked to serve on ad hoc committees or to find suitable stakeholders to serve on ad hoc committees.
Representatives serve on the ANTC at the discretion of the dean or director of his or her academic or administrative unit. There is no specified minimum requirement or maximum limit.
Agenda and meetings
The ANTC agenda is gathered and prepared by a governance liaison within University Information Technology and approved by the ANTC Chair. The committee meets once a quarter, but may meet more often or hold virtual votes if necessary. Meetings are considered open, though space may be limited based on location.
Written agendas and meeting minutes are prepared by a governance liaison within University Information Technology and posted publicly on the Chief Information Officer’s website.
Additional information related to ongoing governance committee operations can be found in the operating guidelines.
Changes to this charter must be approved either by the Strategic Information Technology Committee or the President’s Executive Leadership Team.
Questions or Comments?
Contact Emily Rushton, special assistant to the CIO.