Purpose and authority
The Strategic Information Technology Committee (SITC) is entrusted with raising, hearing, and discussing IT issues that affect significant portions of the University of Utah community or cross multiple areas of oversight. The SITC is expected to make recommendations to the President’s Executive Leadership Team based on a consensus opinion of the majority of the major campus academic and administrative units, and in the best interests of the University of Utah as a whole.
Mission, scope and key goals
The SITC considers 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 decision for the University at large.
SITC considers programs, policy and initiatives that address central architecture, new technologies, funding, strategic and enterprise programs, and projects affecting units campus-wide, such as:
- IT that UIT does not control
- Technical 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)
- UIT Strategic Plans, Scope
- Special central infrastructure and ERP needs
- Security plans and issues
- Application 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 needs that are not common services
- Scheduling and managing UIT resources and operational decisions
- Functional and technical specifications for specific projects (applications)
- Analyze, vet and obtain consensus on recommendations for the president’s executive committee
- Charter targeted ad hoc working groups to explore and pose solutions
- Manage, approve, recommend campus IT services and university architecture (apps, data, infrastructure, process)
- Obtain campus-wide input
- Approve campus IT Strategic Plan
- Analyze and make recommendations on Total IT spend
- Take action on IT Risks
- Develop unified plans among IT groups on campus
Chair: Amy Wildermuth, Professor, Quinney College of Law & associate vice president for faculty
|Cathy Anderson||Associate vice president of Budget and Planning|
|Melissa Bernstein||Director, Faust Law Library|
|Kirsten Butcher||Associate professor and director of the Center for the Advancement of Technology in Education|
|Holly Christmas||Web developer, College of Fine Arts|
|James Elder||Web systems manager, Continuing Education & Community Engagement|
|Aaron Fogelson||Associate dean of research & professor, Department of Mathematics|
|Bo Foreman||Associate professor, College of Health|
|Demian Hanks||IT director, College of Social & Behavioral Science; voting member|
|James Herron||Associate professor and associate dean for Student Affairs, College of Pharmacy|
|Steve Hess||Chief information officer, University Information Technology|
|John Horel||Professor, Department of Atmospheric Sciences; voting member|
|Jakob Jensen||Associate dean of research, College of Humanities|
|Mike Kirby||Associate director, School of Computing; voting member|
|Nancy Lombardo||Associate director for IT, Eccles Health Sciences Library|
|Harish Maringanti||Associate dean for IT and Digital Library Services, Marriott Library; voting member|
|Ken Nye||Director of Business Services, Facilities Management; voting member|
|Andrew Olson||Assistant professor, School of Dentistry|
Associate vice president of Enrollment Management; voting member
|Kevin Runolfson||Assistant dean, College of Nursing|
|Ryan Smith||Associate dean, College of Architecture + Planning|
|Rick Smith||HR director of Health Sciences; voting member|
|Cory Stokes||Associate dean of Undegraduate Studies, UOnline director; voting member|
|Mike Strong||Chief medical information officer; voting member|
|Jess Taverna||Director of undergraduate programs, Eccles School of Business; voting member|
|Jim Turnbull||Chief information officer, Hospitals and Clinics|
|Jeff West||Associate vice president, Financial and Business Services|
|Rob White||IT director, Continuing Education & Community Engagement|
|Thomas Wolfe||IT director, College of Humanities|
|Joanne Yaffe||Professor, College of Social Work|
The voting rights (and thus the voting representative) will rotate among each of the areas every 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 representatives will contact the non-voting representatives in their bloc and other knowledgeable stakeholders in their unit to gather input for the full SITC. Voting members are expected to attend all SITC 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 SITC 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 SITC agenda is gathered and prepared by a governance liaison within University Information Technology and approved by the SITC Chair. The committee meets once a quarter, but may meet more frequently or hold virtual votes if necessary. The 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 Scott Sherman, special assistant to the CIO.