ITS leadership team meeting

October 3, 2019

The ITS leadership team met on Wednesday, September 28. The team discussed the IT Balanced Scorecard objectives and the Technology Architecture Standards Team gave an Architecture Technology Standards update. The meeting also included a presentation of the hard work of so many during the Banner student system migration and upgrade.

Balanced Scorecard update and next steps

A list of defined objectives has been created in addition to individual charters. These charters and objectives will be sent to the IT Leadership team for review and feedback. After receiving feedback, dates and milestones will be set, and the scorecard will be given to department leaders for dissemination and discussion with their staff.

The balanced scorecard, a three-year plan tied to these objectives, covers fiscal years 20, 21, and 22, and focuses on introducing consistency, clarity, and standards across the organization. The scorecard outlines expected outcomes, how they will be measured, and who on the senior leadership team is responsible for leading initiatives tied to outcomes. All objectives are related to at least one of our strategic anchors: One IT at Yale, Service Quality, and Workplace of Choice.

Architecture Technology Standards update

The Technology Architecture Standards Team (TAST), a group responsible for prioritizing the creation of technology-related standards, reported on their quarterly progress.

Standards completed and ratified:  

  • digital accessibility standard
  • load balancing
  • enterprise integration architecture and data services

Standards under review: 

  • authentication
  • storage
  • wiring closets 
  • testing
  • privileged access management  
  • ETL/Data Vault

Banner AIX to Linux wrap-up

Members of the migration team gave a quick overview of the successful production instance migration of Banner, also known as BAN1, from the AIX to Linux operating system that occurred in July.

For many, the work consumed several months, as over 350 scripts, more than 200 integrations, over 50 applications, batch jobs, administrative pages, user IDs, the job scheduler, file movements, and printer connections were analyzed and assessed for modification, decommissioning, or simply testing. Once the development work was completed, the testing consisted of more than 700 distinct cases, along with over 60 specific post-go-live system-to-system validations, and the reviewing of system and firewall logs following the production deployment.

The team thanked all those involved.