Operations Management

Contents:

Change Advisory Board (CAB)

Technology Architecture Committee (TAC)


Change Advisory Board (CAB)

About

The Change Advisory Board (CAB) delivers support to the change management team by approving requested changes and assisting in the assessment and prioritization of changes.  The CAB helps ensure that changes are managed in a rational and predictable manner by enforcing change management policies and procedures.

Responsibilities

Members of the CAB will be responsible for:

  • Advising change owners in functional and organizational areas of change management guidelines with respect to assessment, change type and priority.

  • Assessment of Requests for Change (RFCs) considering impact, availability of resources, priorities, authorization and coordination of changes.

  • Supporting the Change Manager in the decision to approve RFCs.  Review and Approve the Forward Schedule of Change (FSC).

  • Periodically reviewing change metrics to provide input to the Change Process Owner for process improvement.

  • Posting Implementation Reviews, especially in the case of failed or partially failed implementations.

  • Assessing and Advising the Change Manager on Standard PreApproved Change applications.

  • Assuring Change Owners have properly communicated planned system outages to targeted internal or external audiences via email or status page posting when deemed necessary.

Composition

As a team the members of the CAB should demonstrate:

  • Varied perspectives

  • Professional courtesy

  • Willingness to engage

  • A commitment to ensuring a stable environment

Emergency CAB

Addresses requests for change due to an urgent business need that occurs out of the normal change cycle. Typically resulting from an existing Incident, Problem, or outside breach that impacts a critical IT Service that needs an immediate change to correct. Only the Change Manager or the designee has the authority to approve or reject an emergency change with the advice or recommendations from the eCAB members.

Members:

Release Management

Charlie Queiroga

Communications

Janet Jeddry

IT Service Lifecycle

TDB

Information Security

James Hunter

Endpoint Engineering

Elvin Torres

Campus Technology Services

Cyndi Welsh

Infrastructure Services

Michael Dunlap

Research Technologies

Paul Gluhosky

Health & Medicine IT

Marty Wallace

IT Service Management

Mandi Luca

Campus Community Tech.

John Ferraiuolo

Business System Group

Arun Darwar

Problem Management

Cheryl Boeher

One or more IT Partner Managers

Guidelines

Change Advisory Board (CAB) Charter

Technology Architecture Committee (TAC)

Overview

The Technology Architecture Committee (TAC) meets regularly to discuss and inform Yale’s architectural approach and to govern solution architectures for major technology inititatives. TAC members consult with solution architects to ensure architectural alignment to Yale’s technical environment and technology strategy. The TAC does formal reviews of the final design and votes to accept or reject the proposed architecture. 

The TAC is comprised of technology leaders from across campus who regularly commit a significant part of their professional engagement in enterprise, business, information and technology architecture practices.

Objectives

The TAC provides oversight and advice to institutional architecture strategy, execution, and alignment to IT operations and strategic planning.

The objectives of the TAC are to:

  • Support the importance of institutional perspective in technology decision-making
  • Define technology architecture standards and best practices
  • Define standard approaches for introducing new technology architecture initiatives
  • Encourage alignment and adoption of standards and best practices
  • Participate in project governance process as an advisory committee
  • Support risk management objectives

Responsibilities

The TAC provides recommendations on technology architecture opportunities, initiatives, and issues through formal solution design reviews. Reviews culminate in a vote of Accepted, Accepted with Modification or Rejected. The results are published on the ITS web site Technology Architecture Committee Presentations and Notes.

The TAC also considers strategic issues, technology explorations and issues escalated from other IT Governance committees and IT teams across the University. TAC provides recommendations in the context of established enterprise technology practices.

Composition

As a team the members of the Technology Architecture Committee should demonstrate: 

  • Active engagement in enterprise, business, information and technology architecture practices
  • Diversity of disciplinary backgrounds
  • Varied perspectives
  • Professional courtesy
  • Willingness to engage and transform

Members: 

Voting

Syed Alli, Sr. Software Engineer, Law School

Shane Anderson, Director Solution Architecture, ITS Business Systems Group

Michael Appleby, Head of IT, British Art Center

Vincent Balbarin, Solution Architect, ITS Infrastructure Design Services

John Coleman, Sr. IT Forensic Security Analyst, ITS ISPC

Ray Frohlich, Director of Enterprise Systems and Services, Library

Ken Hoover, Sr. Solution Architect, ITS Infrastructure Design Services

Louis King, Enterprise Architect, ITS (Chair)

Morrow Long, Associate Director Forensics, ITS ISPC

Andrew Newman, Enterprise Architect, ITS Infrastructure Design Services

Amit Poddar, Sr. Solution Architect, ITS Infrastructure Design Services

Andy Sherman, Senior Research Scientist, Computer Science

Ken Wieler, CIO, School of Management

Non-voting

John Eberhart, IT Associate Director, ITS