Scribd
Upload
68 views2 pages

Change Assessment Document: CR Number # Basic Assessment Information

This document provides a template for assessing change requests that involve deploying updates or modifications to a production system. It includes sections for documenting details like planned downtime, testing requirements, rollback procedures, potential impacts, and step-by-step execution plans with assigned resources. The goal is to evaluate risks, coordinate activities, and establish accountability for successful deployment and verification of changes to the system.

Uploaded by

narashimreddy1
Copyright
© © All Rights Reserved
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
68 views2 pages

Change Assessment Document: CR Number # Basic Assessment Information

This document provides a template for assessing change requests that involve deploying updates or modifications to a production system. It includes sections for documenting details like planned downtime, testing requirements, rollback procedures, potential impacts, and step-by-step execution plans with assigned resources. The goal is to evaluate risks, coordinate activities, and establish accountability for successful deployment and verification of changes to the system.

Uploaded by

narashimreddy1
Copyright
© © All Rights Reserved
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/ 2

Change Assessment Document

# CR Number

# Basic assessment information


1 Actual downtime (outage) within the CR (In GMT 24HH:MM format)
window
2 Is PRE-PRODuction Testing / ORT
successfully completed (only for PROD
CRs)?
3 Do you think this should be verified by
DEV/QA (post PRODuction
deployment)?
4 Who all are required from DEV/QA/L1-
L2-L3 on standby?
5 Is the rollback verifiable (only for PRE-
PROD CRs)?
6 Is rollback verified in PRE-PROD (only
for PROD CRs)
7 What is the business benefit from this
change?
8 Is the PRE-PROD architecture same as
PROD? (Yes/No)

# Risk / Impact information


A Risk / Dependencies (in deployment)
A.1 Describe rollback steps
A.2 Describe Impact on other system or
domain managers because of this change
A.3 Provide details if any specific VMs,
Devices, infrastructure etc. is required
A.4 Describe if any specific testing required
B Impact on customer (and for how long)
B.1 What features / services will be impacted
because of this change?
Example:
 Reports generation will be
affected for 20 minutes,
 Ticketing will be delayed for 10
minutes etc.)

# MOP (Method of Procedure)


Some guidelines to fill the below section:
1. Sample data is shown in yellow color. Please delete all the yellow text and write all
the required activities along with their owner name.
2. It is responsibility of change submitter to work with other function SMEs and
identify all the required activities before raising the CRs.
3. If some required activities are found to be missing then Change Submitter will be
responsible for that)
4. Don’t delete the red text below
# Task Resource (activity Task time Contingency Actual
owner) (in GMT Time to kick Completion
24:00 hrs. rollback Time
format)
1 Disable Nagios checks Write owner’s name
OR
NA (if not applicable)
2 Take database backup Mr. ABC
3 Take config backup Mr. XYZ

4 Bring Remedy down Mr. ABC


5 Deploy BDD Mr. XYZ
6 Bring Remedy up Mr. ABC
7 Verify services Mr. XYZ

99 Activate Nagios checks Write owner’s name


OR
NA (if not applicable)
# Other mandatory tasks Owner
A Change CR status to COMPLETE Change Submitter
B Update CMDB CMDB manager
C Close CR CMDB manager (after ensuring CMDB is up-to-date)

You might also like