The IT Architecture Committee (ITAC) is an advisory body for governance and oversight of York’s technology architecture, comprised of UIT and faculty domain subject-matter experts. ITAC ensures that York’s technology investments align with the organization’s strategic objectives and operational needs
To promote and ensure the alignment between our IT planning and strategy and York's University Academic Plan (UAP). The committee will provide strategic direction and oversight for the development and management of the enterprise architecture, promoting innovation, efficiency, and agility within our technological framework.
Objectives
Develop, maintain, and communicate the structural design and approach to York’s evolving digital infrastructure.
Optimize technology investments through informed decision-making, technology reuse, and consolidation—where possible.
Promote the adoption of shared infrastructure and services to enhance operational efficiency.
Provide a collaborative forum for discussing and resolving architecture-related issues and conflicts.
Ensure that all technology initiatives are aligned with architecture design principles and IT strategy.
Review and assess emerging technologies and their potential impact on the enterprise architecture.
Responsibilities
Developing and maintaining the enterprise architecture framework and repository.
Reviewing and approving architecture standards, patterns and policies.
Providing guidance and oversight to ensure technology projects align with the enterprise architecture.
Identifying and addressing architecture-related issues and risks.
Promoting the adoption of shared infrastructure and services.
Evaluating and assessing emerging technologies.
Meetings
The ITAC meets monthly. Meeting agendas and supporting materials will be distributed to members at least one week in advance. All meeting proceedings will be accurately documented, with action items recorded in the action list and regular status updates provided. Decision statements and meeting minutes will also be maintained.
October 2026 Summary
Reviewed efficiency tools in GitHub Copilot and discussed Model Context Protocol (MCP), including governance, security, identity management and data stewardship.
The committee reviewed efficiency tools in GitHub Copilot. The use of Model Context Protocol (MCP) was discussed along with governance, security, identity management, data stewardship, and other considerations, agreeing that additional technical review is required before decisions are made. The committee also continued its review of York Well-Architected Framework design patterns.
September 2026 Summary
Reviewed Admissions modernization, the growing adoption of GitHub and GitHub Copilot, and the committee's role in setting technology standards and architectural direction.
Reviewed progress on the Admissions modernization program. Members also discussed the growing adoption of GitHub and GitHub Copilot services and reviewed the committee's strategic role in establishing technology standards and architectural direction. Work continued on the development of York's Well-Architected Framework design patterns.
August 2026 Summary
Continued developing York's enterprise architecture standards, focusing on network design, testing practices, and committee governance.
Continued developing York's enterprise architecture standards, focusing on network design, testing practices, and committee governance. The committee also discussed how domain experts and faculty representatives can work together to create clear enterprise technology guidance and improve consistency across the university.
July 2026 Summary
Reviewed the first draft architecture patterns that will form part of York's Well-Architected Framework and continued oversight of the GitHub Enterprise rollout.
Reviewed the first draft architecture patterns that will form part of York's Well-Architected Framework and continued oversight of the GitHub Enterprise rollout. The committee also refined how future technology standards will be documented and communicated across the institution.
May 2026 Summary
Reviewed the impact of GitHub Copilot licensing changes, and discussed AI governance and institutional priorities.
Reviewed the impact of GitHub Copilot licensing changes, and discussed AI governance and institutional priorities. The committee approved updates to its design pattern template and began drafting the architectural guidance that will support future technology decisions across the university.
Approved: Framework for enabling GitHub Copilot more broadly. Framework for tracking IPPM process related communications.
Actions: Members to begin Design Pattern development. Domain Platform table to be posted once approved by IT Council.
December 2025 Summary
Discussed: GitHub Copilot, IPPM coordination and recommendations to improve technical feedback, Domain Platform documentation, Design Patterns.
Discussed: GitHub Copilot, IPPM coordination and recommendations to improve technical feedback, Domain Platform documentation, Design Patterns.
Approved: Expand GitHub Copilot communication group access. Develop mock-up of IPPM's tentatively approved adjustments to intake. Domain Platform data.
Actions: Members to begin Design Pattern development. Schedule review of intake document adjustments with IPPM. Domain Platform table to be posted.
November 2025 Summary
Discussed: ITAC website, Azure public network item, IPPM coordination and recommendations to improve technical feedback, Domain Platform documentation.
Discussed: ITAC website, Azure public network item, IPPM coordination and recommendations to improve technical feedback, Domain Platform documentation.
Approved: ITAC website updates. Azure public network proof-of-concept to proceed in 2026. Set of ITAC recommendations to be forwarded to PRB/IPPM.
Actions: Members to complete final review of Domain Platforms; co-chair to plan for publishing of Domain Platforms. Co-chair to schedule PRB/IPPM and CIO review of recommendations to improve feedback.
October 2025 Summary
Discussed: Transparency of committee meetings, domain platform responses, Azure public network item continued from September, Business case review for IPPM and platform governance/review process timing for interaction with IPPM.
Discussed: Transparency of committee meetings, domain platform responses, Azure public network item continued from September, Business case review for IPPM and platform governance/review process timing for interaction with IPPM.
Approved: Expand documentation to include external summary of committee meetings. Streamline platform responses before sharing broadly. ITAC review for IPPM will be for obvious risks and concerns, done between meetings to accommodate PRB/IPPM cycle.
Actions: Co-chair to coordinate external documentation solution. Members to identify any key items missing from platform shortlist, then work on publishing. Review and confirm final concerns of Infosec on Azure network item are addressed.
Approved: Method to track decisions internally; platform categories (Standard, Alternate, Deprecated); 6 month trial of GitHub Copilot; singular proof-of-concept for Azure public network interaction with private objects.
Actions: Co-chair to track, maintain, and communicate agenda summaries and decisions. Members to identify key platforms for categorization and sharing. Infosec to review allowing Azure network item implementation.
