{ Remove/replace all items in parentheses before sending.                   }
{ Recommend a minimum of 24 hours notice if possible to allow for response. }
{ This form is to be used when there is no anticipated outage for clients.  }
IT Service Notification - MAINTENANCE ALERT
Computing & Network Services {Unit name}

Remedy change request ID for pre-approved routine service: {enter the request ID here
example: CHG000000004843}

Maintenance being performed:

{ Brief description of the work being performed & service(s) that may be impacted. }
{ Clearly describe potential side effects from the maintenance such as slow        }
{ performance or EXPLICITLY state that no visible impact is anticipated.           }

Maintenanance Schedule:
--- Day:  {Monday, Tuesday, Wednesday, etc...}
--- Date: {month/day/year}
--- Start Time: {nn:nn am/pm - best estimate}
--- End Time:   {nn:nn am/pm - best estimate}

{Note: if the maintenance period is longer than one day, explicitly identify the }
{ duration of the maintenance event. }

Services, servers, or buildings affected:

{ Summary of services, servers, or buildings that may be impacted using names }
{ recognizable by the university community.                                   }

Clients affected:

{ Summary of all faculty staff, members of a LAN, clients that may be impacted.}

If you have questions, comments, or concerns about the proposed maintenance 
please contact:
--- Name:
--- E-mail: 
--- Phone: