When are UAA IT Services' Change Freeze Windows?

Background

A change freeze window is instituted to prohibit or limit system updates which may have an adverse affect on university business. These schedules aid in mitigating the risk of an outage or issues during important business cycles (e.g. student class registration, final exams, etc.), but also permits IT Services to schedule resources to get important system work done during non-freeze periods.

Note that this schedule has been created based upon input from the university community - if you feel your area and business processes have not been included, or are inaccurately represented, please contact UAA IT Services.

Ultimately, the goal of all parties is to reduce risk to users by performing system maintenance during times which have the lowest risk to a business segment in the unlikely event that something were to go wrong with the update.

Change Freeze Windows

The specific dates of the Spring and Fall semester change freeze windows will fluctuate based upon both the calendar cycle, and specific academic calendars for a specific year. The change window can usually be summarized as follows:

Change freeze for the start of a semester (Spring/Fall) begins the Sunday, the week prior to the first day of classes, and ends Friday the week after classes start.

Change freeze for the end of a semester (Spring/Fall) begins the Sunday, the week prior to the week of final exams, and ends the day after grades are due.

 

Be sure to take these periods into consideration when planning changes.

Example Start of Semester Change Freeze Window

Sunday Monday Tuesday Wednesday Thrusday Friday Saturday
December 29th December 30th December 31st January 1st January 2nd January 3rd January 4th
January 5th

Change Freeze
January 6th

Change Freeze
January 7th

Change Freeze
January 8th

Change Freeze
January 9th

Change Freeze
January 10th

Change Freeze
January 11th

Change Freeze
January 12th

Change Freeze
January 13th

Change Freeze

First
Day
Of
Classes
January 14th

Change Freeze
January 15th

Change Freeze
January 16th

Change Freeze
January 17th

Change Freeze
January 18th

Change Freeze
January 19th

Change Freeze
January 20th

Change Freeze
January 21st

Change Freeze
January 22nd

Change Freeze
January 23rd

Change Freeze
 
January 24th January 25th
January 26th January 27th January 28th January 29th January 30th January 31st Feburary 1st

Example End of Semester Change Freeze Window

Sunday Monday Tuesday Wednesday Thrusday Friday Saturday
April 12th April 13th April 14th April 15th April 16th April 17th April 18th
April 19th

Change Freeze
April 20th

Change Freeze
April 21st

Change Freeze
April 22nd

Change Freeze
April 23rd

Change Freeze
April 24th

Change Freeze
April 25th

Change Freeze
April 26th

Change Freeze
April 27th

Change Freeze

Finals
Week
Starts
April 28th

Change Freeze
April 29th

Change Freeze
April 30th

Change Freeze
May 1st

Change Freeze

Last
day
of
finals
May 2nd

Change Freeze
May 3rd

Change Freeze

Graduation
May 4th

Change Freeze
May 5th

Change Freeze
May 6th

Change Freeze
May 7th

Change Freeze

Faculty
submit
final
grades
May 8th May 9th
May 10th May 11th May 12th May 13th May 14th May 15th May 16th

Definitions

Change

The addition, modification or removal of anything that could have an effect on IT services. The scope should include changes to all architectures, processes, tools, metrics and documentation, as well as changes to IT services and other configuration items.
Useful Reference: What is a Change?

Change Freeze

  • Intent to prohibit all changes to production systems.
  • Goal of maintaining the ultimate in system stability.
  • There is a "NO GO" assumption for changes within the scope of the Change Freeze - one must justify need if an emergency change is necessary.
  • Exception Criteria: changes must be approved by any impacted units, and the Change Advisory Board.

Normal Period

  • All changes are acceptable, assuming UAA change management processes are being followed.
  • Goal of allowing the highest level of change available while maintaining system stability.
  • There is a "GO" assumption for changes, assuming UAA change management processes are being followed.

Details

Article ID: 105
Created
Wed 4/22/20 10:40 AM
Modified
Wed 7/26/23 10:50 AM