You are here


University of Minnesota Enterprise Architecture (EA) seeks to align enterprise information technology across the University of Minnesota system in order to save money, innovate faster, and improve communication.

Purpose of Technology Review Board

The Enterprise Architecture Technology Review Board (TRB) represents the shared interests of the University of Minnesota Information Technology community (IT@UMN) and makes recommendations to the University’s Enterprise Architect 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


  • In consultation with the Enterprise Architect and committee members; schedule dates, times, and location for meetings
  • In consultation with the Enterprise Architect and 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 Architect


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 TRB
  • Acts as request coordinators when called upon by the TRB
  • Acts as subject matter experts when called upon by the TRB

Enterprise Architect

  • Delivers enterprise architecture decisions based on TRB 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 TRB process
  • Champions enterprise architecture within IT@UMN
  • Communicates decisions to the University IT community
  • Maintains TRB membership

Scope of Enterprise Architecture Technology Review Board

The EA Technology Review Board will address technology standards, principles and best practices in IT across the University of Minnesota, including colleges, non-collegiate units and system campuses. The TRB 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 TRB is available for researchers and research units for consultation.

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 Architect 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

Several critical success factors have been identified as important to ensure the success of the EA Technology Review Board. These factors include:

  • Knowledge of and alignment with EA 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 TRB process
  • Open communication between committee members, the University community, and the Enterprise Architect
  • Implementation of an established process for meetings, including agendas and issue resolution
  • Active participation of all committee members
  • Provide consultation to units engaged in the purchasing process for technology products


The EA Technology Review Board will consist of a Chair, Vice-Chair, a Communication Specialist, the Enterprise Architect and Board Members, representing several technology domains.

Current Membership


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.