8/3/2019 Change Request Release Form11092011V2 15 91

http://slidepdf.com/reader/full/change-request-release-form11092011v2-15-91 1/7

Change/Release Details Form

FILENAME: Change Request Release Form11092011V2 15 91 PAGE 2 OF 7TEMPLATE VERSION 2.0 PRINTED ON: 11/11/2011 12:06 PM

4Vendor/Partner  ANB Systems Reference Name/Release Num. EEPM11092011V2.15.91

Change Requestor ONCOR  Status To be Delivered in UAT

 Vendor Approver Raja Srinivasan Date to be implemented 11-09-2011

Current Date 11-09-2011 Date Completed 11-09-2011

Required Information for change

Fields Details Required

Summary of change  Please refer to the release file attached 

Business Impact - impact to the business,

how this change effects the business, chgs tofrontend or user interface etc

.Net Code, DB Changes 

Technical Impact - impact of systems, whatis chging in the backend systems

Code, DB Changes 

Hardware affected/associated- list of servers/machine names

Software affected/associated – such as

specific database names and/or tables,

applications effected

.Net Code, DB Changes 

Planned Implementer – who is expected toperform chg

ANB Team in QA, ECP in Production & UAT

Level of expertise forchg/implementation – such as DBA, DB

script, .net app chg, netwk chg, firewall chg,sharepoint chg: web parts

System admin with access to copying files from one environment to another.

DBA for running DB scripts and for backing up and restoring databases.

Deploy InfoPath forms

Specific Instructions for applying change –detailed step by step deploymentinstructions

Details below

Change Verification Process – details of how/what to verify, attach additional doc is

necessary

Please review the release file attached

Change Reviewer/Verifier- Person thatverified chg in test sys prior to prod imp,

written client approval prior to prod chg

Joe Nixon, ONCOR

Integrity of Systems – will chg effect data

directly or indirectly

Indirectly

Identified Risks None

Mitigation of Risks

Testing Methodology – how chg was testedand results

Please review the release file attached

Testing performed by Dev Team & Joe Nixon

Backout Plan/Removal of Change – detailed instructions on how to remove chg in

the event of errors

Details below

Development Contact – if problem arisesduring deployment the chg implementer must

be able to request additional information for

the deployment and/or a new codepackage/patch/release 

Raja Srinivasan, 610-952-8139

Expected Outage – any expected downtimeexpected in any systems or client outage

No outage is required.

Production ChangeReviewer/Development team Verifier

Raja Srinivasan, 610-952-8139

Business Owner Signoff 

Additional Details

8/3/2019 Change Request Release Form11092011V2 15 91

http://slidepdf.com/reader/full/change-request-release-form11092011v2-15-91 2/7

Change/Release Details Form

FILENAME: Change Request Release Form11092011V2 15 91 PAGE 3 OF 7TEMPLATE VERSION 2.0 PRINTED ON: 11/11/2011 12:06 PM

1.  Software Release Notes

Name of Releaser  Amar Anne

Release Version 2.15.91

Mode of Delivery

File upload

Release type

(Change Request/Both)

NA 

Environment Information(QA-Staging, QA-Production, UAT-Staging,

UAT-Production, Training, Production-Staging,

Production-Test, Production)

UAT  – 10.111.110.20/CYONAPU01

Production -10.111.110.140/CYONAPP01, 10.111.110.141/CYONAPP02 

Change Management Folder 10.111.110.21  – D:\change management

2.  Environments to be released in

3.  CC Release Package Details

Change RequestRelease Form110920

4.  Pre-Deployment Instruction

Create the subfolder with the release number under the instance being updated, as per the instruction below in thefolder setup instructions. (ANB Team will do this).

5.  Maintenance Message

QA  – Staging QA  – Production UAT  – Staging UAT  – Production

Training  – Staging Training  – Production Production  – Staging Production  – Test

Production

In IIS Manager, go to the Production .Net server 10.111.110.140 and change the default content page to themaintenance.aspx page by selecting and moving it up in the list. Do the same in the second server 10.111.110.141.

Environment Planned Release Date Completed Date

QA – Staging

QA – Production

UAT – Staging 11-09-2011 

UAT – Production 11-09-2011 

Training – Staging

Training – Production

Production – Staging

Production – Test

Production

8/3/2019 Change Request Release Form11092011V2 15 91

http://slidepdf.com/reader/full/change-request-release-form11092011v2-15-91 3/7

Change/Release Details Form

FILENAME: Change Request Release Form11092011V2 15 91 PAGE 4 OF 7TEMPLATE VERSION 2.0 PRINTED ON: 11/11/2011 12:06 PM

6.  Backup Instructions

QA  – Staging QA  – Production UAT  – Staging UAT  – Production

Training  – Staging Training  – Production Production  – Staging Production  – Test

Production

Backup the database to the already setup folder related to the instance being updated. The database name andlocation are provided in the database matrix. The DB backups are about 15 GB.

QA  – Staging QA  – Production UAT  – Staging UAT  – Production

Training  – Staging Training  – Production Production  – Staging Production  – Test

Production

Backup the code to the already setup folder related to the instance being updated. The code to be backed up and thelocation to obtain it from are provided below in the file location matrix. The code is about 90 MB. For productioninstances, there are 2 servers, 140 and 141 so the backup needs to be done for both servers.

8/3/2019 Change Request Release Form11092011V2 15 91

http://slidepdf.com/reader/full/change-request-release-form11092011v2-15-91 4/7

Change/Release Details Form

FILENAME: Change Request Release Form11092011V2 15 91 PAGE 5 OF 7TEMPLATE VERSION 2.0 PRINTED ON: 11/11/2011 12:06 PM

7.  Database Synch Instructions

QA  – Staging QA  – Production UAT  – Staging UAT  – Production

Training  – Staging Training  – Production Production  – Staging Production  – Test

Production

  Kindly run the SharePoint script after DB Synch

8.  DB Sync Script:

QA  – Staging QA  – Production UAT  – Staging UAT  – Production

Training  – Staging Training  – Production Production  – Staging Production  – Test

Production

9.  .Net Code / File Deployment Instructions

QA  – Staging QA  – Production UAT  – Staging UAT  – Production

Training  – Staging Training  – Production Production  – Staging Production  – Test

Production

  Copy over the .Net code from the change management folder to the instances code location. Refer to the filelocation section down below for location of the code in each of the instances. Replace all files.

10. Database Code Deployment Instructions

QA  – Staging QA  – Production UAT  – Staging UAT  – Production

Training  – Staging Training  – Production Production  – Staging Production  – Test

Production

  Connect to the database being updated, the details are provided in the database matrix.  Run the DB Scripts pertaining to the instance being upgraded, the script file will be present in the change

management folder, under the release number folder for the instance being updated.DBScript.sql

11. Rollback Procedures

QA  – Staging QA  – Production UAT  – Staging UAT  – Production

Training  – Staging Training  – Production Production  – Staging Production  – Test

Production

8/3/2019 Change Request Release Form11092011V2 15 91

http://slidepdf.com/reader/full/change-request-release-form11092011v2-15-91 5/7

Change/Release Details Form

FILENAME: Change Request Release Form11092011V2 15 91 PAGE 6 OF 7TEMPLATE VERSION 2.0 PRINTED ON: 11/11/2011 12:06 PM

  The code backup can be restored by copying the files over from the backup done in step 4 of this instruction.

12. Testing Procedures (the business analyst to provide this in the testing sheet of the excel workbook)

QA  – Staging QA  – Production UAT  – Staging UAT  – Production

Training  – Staging Training  – Production Production  – Staging Production  – Test

Production

Please refer to the excel workbook for testing instructions.

13. Final Steps

QA  – Staging QA  – Production UAT  – Staging UAT  – Production

Training  – Staging Training  – Production Production  – Staging Production  – Test

Production

Move the maintenance page down and put the default page back. This is basically reversing the pre-deploymentinstruction.

8/3/2019 Change Request Release Form11092011V2 15 91

http://slidepdf.com/reader/full/change-request-release-form11092011v2-15-91 6/7

Change/Release Details Form

FILENAME: Change Request Release Form11092011V2 15 91 PAGE 7 OF 7TEMPLATE VERSION 2.0 PRINTED ON: 11/11/2011 12:06 PM

1 General Instructions

Folder Setup Instructions (one time setup are NOT bolded)  – Currently setup on10.111.110.21

1.  Create a change management folder in a common drive which is accessible to the change management lead fromthe development team and EC Power.

2.  This folder should have a folder for each of the application instances.3.  Under each of these instances we should create a folder with the release number every time a

release is being made.4.  The release number folder will have 2 folders one for the backup and one for the code being rolled

out.5.  The change release document and the excel sheet should be placed in the root of the release folder.6.  We can have a DB backup folder and a Code backup folder under the backup folder.   An archival strategy

should be determined for this folder so we don’t let this grow uncontrolled.

Sample Folder Structure

Database Matrix

INSTANCE NAME IP ADDRESS DATABASE NAME SQL login user usedby app

QA STAGING 10.111.10.21 Staging_qa savant

QA PRODUCTION 10.111.10.21 oncor_eepm_qa savant

UAT STAGING 10.111.10.20 Staging_oncor_uat Oncor

UAT PRODUCTION 10.111.10.20 Oncor_uat Oncor

TRAINING STAGING 10.111.10.20 straining_uat Oncor

TRAINING PRODUCTION 10.111.10.20 training_uat Oncor

PRODUCTION STAGING 10.111.10.146 Staging_oncor_prod eepmprod

PRODUCTION TEST 10.111.10.146 Staging_prod eepmprodPRODUCTION 10.111.10.146 Oncor_prod eepmprod

8/3/2019 Change Request Release Form11092011V2 15 91

http://slidepdf.com/reader/full/change-request-release-form11092011v2-15-91 7/7

Change/Release Details Form

FILENAME: Change Request Release Form11092011V2 15 91 PAGE 8 OF 7TEMPLATE VERSION 2.0 PRINTED ON: 11/11/2011 12:06 PM

File Location Matrix

INSTANCE NAME IP ADDRESS SOURCE FOLDER NAME

QA STAGING 10.111.110.21 C:\Inetpub\wwwroot\QA\StagingQA PRODUCTION 10.111.110.21 C:\Inetpub\wwwroot\QA\Production

UAT STAGING 10.111.110.20 C:\Inetpub\wwwroot\UAT\Staging

UAT PRODUCTION 10.111.110.20 C:\Inetpub\wwwroot\UAT\Production

TRAINING STAGING 10.111.110.20 C:\Inetpub\wwwroot\UAT_Training\Staging

TRAINING PRODUCTION 10.111.110.20 C:\Inetpub\wwwroot\UAT_Training\Production

PRODUCTION STAGING  – Server 1

10.111.110.140 C:\Inetpub\wwwroot\ONOCR_EEPM\Staging

PRODUCTION TEST  – Server 1

10.111.110.140 C:\Inetpub\wwwroot\ONOCR_EEPM\Production_Test

PRODUCTION  – Server 1 10.111.110.140 C:\Inetpub\wwwroot\ONOCR_EEPM\Production

PRODUCTION STAGING  – 

Server 2

10.111.110.141 C:\Inetpub\wwwroot\ONOCR_EEPM\Staging

PRODUCTION TEST  – Server 2

10.111.110.141 C:\Inetpub\wwwroot\ONOCR_EEPM\Production_Test

PRODUCTION  – Server 2 10.111.110.141 C:\Inetpub\wwwroot\ONOCR_EEPM\Production