Scheduled IT Maintenance

Change Management is the process Information Technology (IT) uses to discuss and implement changes to the University computing environment. All changes must be reviewed and approved prior to being implemented.

Change Management encompasses four service groups within IT: Networking, Systems, Applications, and Desktop Infrastructure (with Canvas as a sub-category of Applications). Each service group performs weekly maintenance during one or more well-defined maintenance windows in order to minimize the impact to the campus community.

The standard scheduled IT maintenance times are listed below. These times are reserved for maintenance specifically to minimize the impact any maintenance procedures may have on campus computing. Most maintenance occurs behind the scenes and does not directly affect customers of IT.

 

  Primary Secondary Tertiary
Network Mon 10p.m. - 6 a.m. Tue Wed 6 - 8 a.m. Thu 6 - 8 a.m.
Systems Thu 10 p.m. - 2 a.m. Fri Wed 3 - 8 a.m. Sat 8 a.m. - 12 p.m.
Applications1 Tue 5 - 7 p.m.    
Desktop2 Sat 12 a.m. - 6 a.m.    
Canvas 3rd Sunday of month
12 a.m. - 12 p.m.
   
IT RSS Tue 5 p.m - 11 p.m. Wed 10 a.m. - 12 p.m. Fri 10 a.m. - 12 p.m.

 

Notes:

  1. Applications maintenance includes all Web applications commonly used on campus, such as PeopleSoft, Terminal Four, and the Online Help Request system. In many cases, customers will see little to no impact other than the inability to access a particular Web application. Canvas services have a special maintenance window reserved in case any updates are applied to the Canvas environment.

  2. Desktop maintenance primarily refers to the monthly Windows updates to all campus-standard installations of Windows. The updates are installed between 12 a.m. and 6 a.m. Saturday mornings.

Emergency Maintenance

IT reserves the right to perform emergency maintenance as needed to prevent any catastrophic events that are likely to occur or to recover services from such an event. This may result in interruptions of campus computing services lasting several hours or longer.

 

Change Management

Change management is a process meant to ensure that any changes to existing, or introduction of new, software or hardware within
the Missouri University of Science and Technology’s (S&T) Information Technology (IT) production environment is done is an orderly and controlled manner. Ensuring effective change management within the S&T IT production environment is extremely important in
ensuring the efficient delivery of IT services while reducing risk.

 All change requests are reviewed during the weekly CM meetings. The normal process for a change request is to be reviewed at least 1 week prior to being implemented in production. Any CM request with less than 1 week of lead time to review is considered an emergency change and requires management approval and a post review audit. All areas of IT and select other campus groups are encouraged to attend the CM meeting each week as this is the forum to debate what changes are being proposed and approved. Any change owner with requests scheduled for review is required to attend or send a proxy, otherwise the request is denied.

All CM entries must be submitted by Wednesday at midnight one week prior to review.

  •     Every Thursday Morning: A report will be sent to IT staff that lists the upcoming changes for their review prior to the meeting.
  •     Questions for the CM entries will be addressed during the scheduled CM meetings; however staff can optionally email the submitter prior to the meeting to have questions addressed offline.
  •     The meeting will only consist of anyone who has questions on a specific CM entry.  All CM entries will not be reviewed due to the report going out a week prior.

CM Policy & Procedures

Change Management Freeze Windows

The CM freeze windows outlined here are necessary to help the campus during increased student and faculty need. During these
peak times when students and faculty are beginning the semester or ending the semester campus administration runs as fluid as possible without multiple changes to the IT system.

If a change is determined as being crucial to the campus infrastructure the CIO can be requested to approve the change through an emergency promotion.

  • Beginning: The freeze window will be 2 weeks prior to semester start and the first week of the fall semester.

  • End: The freeze window will be 2 weeks prior to semester end, until grades are posted.

  • Beginning: no changes one week prior to semester start and the first week of classes

  • End: The freeze window will be 2 weeks prior to semester end, until grades are posted

  • Beginning: No changes for the first week of classes.

  • End: No changes during finals week, and until grades are posted.