Experts & Communities

Charter

five people at a meeting
577 gradient

Helping you choose technologies with confidence

Purpose

The Technology Advisory Council represents the shared interests of the University of Minnesota Information Technology community (IT@UMN) and makes recommendations to the University's enterprise architects regarding technology standards, principles, and best practices in IT.

Roles and Responsibilities

Technology Review Board Members

  • Maintain technology review and TRB process
  • Drive technology-review and TRB process development
  • Review technology requests and roadmaps and provide professional recommendations
  • Act as ambassadors of enterprise architecture within the University IT community
  • Be present at, be prepared for, and be engaged with meetings and TRB activities

Chair

  • In consultation with committee members; schedule dates, times, and location for meetings
  • In consultation with committee members; establish, prioritize, and confirm an agenda for each meeting
  • Ensure the meeting agenda and relevant documents are circulated to the members of the committee in advance of the meeting
  • Officiate and conduct meetings
  • Provide leadership and ensure committee members are aware of their obligations and that the committee complies with its responsibilities
  • Ensure that discussion on agenda items is on topic, productive, and professional
  • Ensure meeting notes are complete and accurate, retained, and reviewed at the next meeting
  • Provide final recommendations to enterprise architects

Vice-Chair

  • Carry out the chair's duties in his or her absence
  • Provide support and assistance to the chair in carrying out his or her responsibilities
  • May agree to take on specific responsibilities from the chair

University Community (units, service leads, IT@UMN, etc.)

  • Prepares and submits necessary documentation for requests and road maps to the council
  • Acts as request coordinators when called upon by the council
  • Acts as subject matter experts when called upon by the council

Enterprise Architects

  • Delivers enterprise architecture decisions based on council recommendations
  • Possesses primary enterprise architecture decision authority
  • Holds chair accountable for performing his or her role
  • Is the point of escalation for technology exceptions
  • Supports enterprise architecture and council process
  • Champions enterprise architecture within IT@UMN
  • Communicates decisions to the University IT community
  • Maintains council membership

Scope

The council addresses technology standards, principles and best practices in IT across the University of Minnesota, including colleges, non-collegiate units and system campuses.

The councll does not address services; rather, it addresses the underlying technologies that support services. For example, email is a service and Gmail is the underlying technology that supports that service. The council is available to consult with researchers and research units.

Objectives (Types of Requests)

  • Review and provide comment on six-year capital IT plan
  • Review and provide comment on six-year technology roadmaps that support enterprise services (annual)
  • Review and provide comment on collegiate and non-collegiate technology plans (annually)
  • Respond to enterprise architects' requests
  • Regularly review and update the Technical Reference Model (TRM)
  • Evaluate the wider emerging technology landscape (can sponsor fairs/discussions
  • Stay aligned with University security standards, needs, and initiatives

Critical Success Factors

  • Knowledge of and alignment with the technology selection guidelines guiding principles
  • Integration with the IT Governance process, where appropriate
  • Integration with the Change Approval Board (CAB) process, where appropriate
  • Alignment with University security standards, policies, and initiatives
  • Key stakeholder buy-in for the council's process
  • Open communication between committee members, the University community, and the enterprise architects
  • Implementation of an established process for meetings, including agendas and issue resolution
  • Active participation of all committee members
  • Consultation to units engaged in the purchasing process for technology products

Membership

The council includes a chair, a vice-chair, a communication specialist, the enterprise architects, and members representing several technology domains.

Meetings

Meetings will be conducted weekly, and may be scheduled more or less frequently based on demands and enterprise priorities. Committee members are expected to attend and actively participate in all meetings. Meeting times will be reviewed based on needs and initiatives. Recommendations will be documented by the board.