University of Rochester
   

Service Diagrams

University IT Maintenance Calendar

Contacts

Forms

Production Services

Rates

Solutions

Connections

University IT Home

IT Notices

Policies

About Us

PMR

Leaders

Contact Us

Request For Change (ITSF-006)       

This form is used to make a formal Request for Change (RFC) to any Production, QA and selected Development system or services supported by University Information Technology.  This includes ANY infrastructure changes including OS and Application Core updates.

.

An asterisk (*) indicates a required field.  Required fields must be filled in completely.  Missing information may result in the RFC being rejected and returned to the submitter.

 

Change Types:

    • ROUTINE:  Routine changes must be submitted a minimum 3 business days before requested date. Routine changes require the approval of the appropriate University IT Service Owner Manager or Assistant Director and may be subject to review and approval by the University IT Technical Advisory Board (TAB).
    • EMERGENCY:  For Emergency changes requested;
      • During normal business hours, once the form is submitted you must have the University IT Service Owner Manager or Assistant Director approve your change, then they MUST acquire approval from the University IT Service Owner Director.  All parties must Reply All to the email with their approval.
      • After normal business hours, once the form is submitted you must have the University IT Service Owner Manager or Assistant Director approve your change, then they MUST escalate for approval from the University IT Incident Manager On Call (IMOC).  All parties must reply all to the email with their approval. Since the change is being requested after normal business hours the University IT Service Owner Director must also be copied in.

    Upon submitting the form, an email will be sent to the proper management team Manager or Assistant Director for approval.
    Documents located in the University IT Change Management Processes SharePoint folder can further assist you with the use of this form or with the Change Management process.

    If you have any questions or concerns, please contact University IT Production Control at 275-9240. -->

Please review the University IT Change Management Processes for further information on the use of this form.

REQUESTOR INFORMATION

Name*
EMail Address*
CC
Telephone*
Cellular/Pager/Other
Department**
* Selecting "Test This Form" for your department sends messages only to yourself, you may use this if you're familiarizing yourself with this form.

CHANGE INFORMATION

Change Type:

Change Requestor or Sponsor: Who are you doing the work for or on request by.*

Change Partner (second set of eyes) or NA:What staff member will over see this activity - onsite or via shared screen?*

Change Coordinator: (A change coordinator may be assigned for large scale changes or projects)


Change Implementer(s):*


What is the source of this request: Please list ITSR, HEAT Ticket, Project Number, OAR Code, MANTIS Number or Other*


Search By:

Server Name*

Applications/Services Affected *

Select other if the item is not in the list (select multiple entries with the Ctrl key)
See the Service to Server Listing.

If other is selected for Server(s) above, please enter the information here in the text field.

If other is selected for applications/services above, please enter the information here in the text field.

List ALL departments or users whose service may be impacted: *

Proposed date and time (24 hour format):*

Pick a date

Friday is restricted to Urgent or Emergency changes only.

Within Standard Maintenance Window?

Yes No N/A

Proposed duration of activity:*

Service outage:*

Yes No

Restart (Reboot/IPL) of host required:*

Yes No

Provide a detailed technical description of the change being requested:*

Provide a non-technical summary of the change being requested:*

Describe in detail the justification for this change*

Was Documentation Updated:

Yes No

Documentation Comments:

RISK MATRIX

Greater Than 100 Users Affected *
Less Than 100 Users Affected*

Statement supporting risk evaluation:*


PLANNING
The following fields are MANDATORY and all must be filled out, completely and with detail. Missing or incomplete ("N/A" responses) will result in the change being rejected and sent back for more information.

Provide a complete and detailed backout plan, including duration time to execute the plan*

Provide a complete and detailed step by step Testing Plan*

Provide a complete and detailed step by step Post Change Validation Plan*

Other information or comments*

Is a maintenance notice required?

Yes No

Communication Plan Attached:

Yes No


If submitting multiple requests, please wait 1 minute before each submission for proper event ID assignment.

Communication Plan Attachment:


Backout Plan Attachment:


Testing Plan Attachment:


Validation Plan Attachment:
       

Text | Directory | Index | Contact | Calendar | News | Giving

©Copyright 1999 -- 2006 University of Rochester
Last Modified: Tuesday, 08-Nov-2011 17:04:37 EST