Scribd
Upload
375 views1 page

Template - Change Request Process and Description Requirements Final

This change request document outlines the necessary details to submit a change request, including the purpose of the change, its potential impact, who will implement it, a suggested schedule, the location of the change, an implementation plan, and any required pre-approvals. Key information to include is what is changing, what it may affect, when the change will occur, where in the infrastructure it will take place, and how the change will be carried out. Pre-approval documents should also be attached for reference.

Uploaded by

Santu Chatterjee
Copyright
© Attribution Non-Commercial (BY-NC)
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
375 views1 page

Template - Change Request Process and Description Requirements Final

This change request document outlines the necessary details to submit a change request, including the purpose of the change, its potential impact, who will implement it, a suggested schedule, the location of the change, an implementation plan, and any required pre-approvals. Key information to include is what is changing, what it may affect, when the change will occur, where in the infrastructure it will take place, and how the change will be carried out. Pre-approval documents should also be attached for reference.

Uploaded by

Santu Chatterjee
Copyright
© Attribution Non-Commercial (BY-NC)
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 1

Submit Change Request with the following details 1.

Purpose of the Change : Describe the reason for the change what business, or technical requirement, fix the change is expected. Need to answer the question Why 2. Impact of the Change: Describe what the change will impact, e.g. it may only impact one SQL Database and does not have any impact on rest of the applications sharing the same sql server instance. Need to clearly answer the question What in terms of the impact of the change, Applications, modules affected, and the apps that are not affected. If a service Outage is required, how long for, clearly indicating if it only requires failovers or a significant outage required. 3. Change Done by: Who is expected to make the change. If it is an informational change, UIT Teams (e.g. Apps Infrastructure team) makes the change. All changes done by NAEC/GOIS, indicate if it is done by Storage Management (All storage adds are done by Storage Mgmt); or Server group (all server installs done by Windows group); or Network (Network Engg Group of NAEC? Or Network Engg Group of UIT Global Infrastructure) ; Database Admin group (All Db changes are done by SQL DBA Group or Oracle DBA Group) 4. Suggested Schedule for the Change : Answer the question When. If this is already negotiated with users, on the schedule, please indicate. It is not always possible to get pre-approval on the CR because the change may need approval from many teams. If there are special requirements such as it need to be scheduled only after 8:00 PM EDT on a Friday or during non-US Business hours or weekend only, Please indicate here. If it can be scheduled during the business day, indicate why it is OK to do so. Typically non-production changes can be scheduled during the business day. Need to explain the reason why change is proposed at the time it is proposed. Many of the Applications have clearly defined/agreed change windows for Production, these will be documented in App Portfolio soon. When a change is being done during the already agreed scheduled window, the approvals can be given by UIT Change management, with a notification to the Application owners affected so that they can raise an exception if required. 5. Location for the change: Answer the question Where . This section should indicate location of the change - which servers/hosts; List the server names, database instance names etc. This should enable the UIT Change management team to identify the apps affected using the App Portfolio information. 6. Methodology or Implementation Plan Suggestions: This should describe if necessary How the change is done, if it is a complicated change, should indicate the sequence of steps process to be followed. This should also indicate for Production changes any back out plan (Roll Back plan) if one exists. If no back out plan exists, need to specify why there is no back out plan.
7. Pre-Approvals Any pre-approvals should be attached to the CR for reference.

You might also like