Skip to the content of the web site.

Campus Computing Committees

Several computing committees/groups exist to make decisions and share information.

UCIST -- University Committee for Information Systems and Technology

UCIST serves as a co-ordinating body for computing on campus, and has representation from each of the faculties (the associate dean, computing) and the major academic-support areas (the associate provosts, vice-president administration & finance, associate university librarian, and director of business operations).

CTSC -- Computing Techology and Services Committee

The CTSC provides advice to the Associate Provost, Information Systems & Technology and UCIST on the planning, design, implementation and operation of IT technologies at UW. CTSC makes recommendations to UCIST in these areas and initiates IT investigative projects of campus interest.

Academic Support Computer Rep Group The computing reps in academic support departments are the first point of contact for staff in their department having computer problems. The computing reps work with an IST liaison in Client Services on solving more complex problems, and are instrumental in helping with larger projects such as desktop deployment.
Campus Network Services Committee

To facilitate communication between IST and faculty and departmental IT staff to:

  • Ensure users are aware of, and make effective use of, current network services.
  • Ensure network services evolve to reflect the future needs of the user community.
  • Ensure network service provisioning tools evolve to ensure an efficient service is delivered to end users.
  • Ensure planned changes to services are communicated to the user community in an effective and timely fashion.
  • Ensure IST is aware of challenges users are facing in the use of network services.
Professional Development Advisory Group The UW IT Professional Development Advisory Group (PDAG) is reponsible for
  • organizing a schedule of professional development seminars held every Friday morning.
  • scheduling seminars as required to inform people of new technology.
  • help organize special training as requested by UW IT groups.
  • acquisition of training materials.
Computing Systems Advisory Group

To advise UCIST on the evolution of facilities, services, procedures and policies for all university-supported computing systems, to facilitate communication and interaction among the various computing support areas on campus, and to help coordinate decision making on related campus-wide issues.

CSAG members serve as advocates for the computing-systems architecture and environment, and are expected to take an active role in coordinating the successful evolution of the environment.

As an advisory committee to UCIST, CSAG will keep UCIST informed of issues under discussion through the preparation and distribution of minutes of meetings, through periodic reports of priorities and issues under discussion, and the expeditious referral of issues to UCIST.

FACulty Computing User Support Group FACCUS is a resource group for staff providing user support in the faculties, IST and the Library.
Waterloo Nexus Advisory Group

The purpose of the Waterloo Nexus Advisory Group is to facilitate discussion on technical issues related to development and ongoing support of the Waterloo Nexus environment. Each member is expected to bring to the Group issues for discussion and resolution, and to communicate information back to the Waterloo Nexus system administrators within the academic and academic support units they represent. The group is advisory to UCIST.

Web Advisory Committee (WAC) The Web Advisory Committee provides recommendations to and receives direction from the University's Web Steering Committee and UCIST (University Committee on Information Systems and Technology). It tracks evolving requirements and use of the Web and develops strategies for its ongoing evolution.
Security Working Group The Security Working Group is an ad hoc group of information technology professionals at the University of Waterloo who are concerned about security related issues.

Last updated by Bob Hicks (email bjhicks at UWaterloo.ca), September 15, 2009.