Global Change Management - Change Impl

Document Number:GOIS-GP-GO-TP-02244 Revision: 3.2

Document Title: Global Change Management - Change Document Type: Template

Implementation Plan Template
Document Owner: Sathish Kumar Mohan Document Status: Live

Unisys-Internal Confidential.
Caution: The online version of this document is the master. To ensure that printed copies are current, compare the revision lev
immediately after use.

Document History
Version Author/Editor Descri
1.0 RaviShankar Venugopal Document initiation and updates.
1.1 Syed Afzal Included the UAT CRQ number and SME
2.0 Piet Peek Uploaded to QMS
3.0 Piet Peek Changed approver to Govarthanan, Rang
3.1 Syed Afzal Updated the templated on Risk and Impac
3.2 Sathish Kumar Mohan Consolidated all tabs under single sheet t

Any change required to this template as per Account or Client Please update the version
nt - Change Implementation Plan Template

mplate
Revison Date: 02-Feb-2015

ve Approved By:Smith-Butz, Annamarie

Shannon

re current, compare the revision level and date of the printed copy to the online master. Destroy all printed copies

Document History
Description of Change Date
initiation and updates. 7/29/2008
he UAT CRQ number and SME approvals in the Implementation Plan 11/4/2010
to QMS 3/14/2011
approver to Govarthanan, Ranganathan 7/18/2011
he templated on Risk and Impact and communication plan, Removed Backout testing
12/20/2013
ted all tabs under single sheet to ease usage.Included Outage details. 1/14/2015

ient Please update the version history update the records that are added into the sheet
 Change Implementation Plan Template
Client HENKEL

Change Request Number CRQGB0000582333

UAT CRQ Number NA

Upgrade Oracle version on

Change Description
HKHKGSVVUT01 to 11.2.0.4
Upgrade Oracle version on
Change Title
HKHKGSVVUT01 to 11.2.0.4

Change Start Date and Time 2/21/2017 12:00:00 PM IST

Change End Date and Time 2/23/2017 11:00:00 AM IST

Change Class Normal

Impact Description :

Prerequisites:
 Implem

The Implementation Plan below is intended to document how the full Change Request will be implemented including all of the
required
Planned Start Date/Time Planned End Date/ Time
Task Sequence Duration
(dd/mmm/yyyy h:mm;) (dd/mmm/yyyy h:mm;)

1 2/21/2017 12:00:00 PM IST 2/23/2017 11:00:00 AM IST 24 Hours

 Test / V
The Test / Validation Plan below is intended to document how the full Change Request will be tested following completion of all i
Implementation Plan.
Client Testing Required (Yes/No) No

Client Test Contact Name

Contact Phone Number and Info

Planned Start Date/Time Planned End Date/ Time

Task Sequence Duration
(dd/mmm/yyyy h:mm;) (dd/mmm/yyyy h:mm;)

Bac
If a Back-out is required, the back-out plan documents the steps that would ensure that the environment has been returned to a
implementer and activity details.
 Back out Plan Description :
Planned Start Date/Time Planned End Date/ Time
Task Sequence Duration
(dd/mmm/yyyy h:mm;) (dd/mmm/yyyy h:mm;)

1 2/21/2017 12:00:00 PM IST 2/23/2017 11:00:00 AM IST

Comm

The communication plan is intended to document the individual/group to get notified in the following scenarios
Notify status to individual/group post change implementation
In event of outage caused by change implementation
In the event of change implementation going beyond the change window.
Date & Time Method Contact
Ernest Toh' Name/List
<ernest.toh@henkel.com>;
savita@aureoleinc.com;
2/23/2017
Mail Omkumar.RamachandraPai@in.unisys.c
11:00:00 AM IST
om
 S

List down the contact details of the support team members involved in implementing the change request

Client / Work team Contact Name/List

Oracle DBA Team Abishek Vidyashanker

Supporting Documents
1 Updates in Quality Documents Required for the Change? No
2 Updates in Contingency Plan Required? No
3 Acquisitions Identified No
4 Consulting work required? No
5 Training Required? No
6 Travel Required to implement the Change? No
7 Business Communiction Required? No
tion Plan Template
Risk Level (Auto Populated*)
1

Outage Required (Yes/No) No

Site or Location affected HKHKGSVVUT01

Services affected

Outage Start date and time

Outage End date and Time

Total Outage Duration

Impact Low

Database will be down during the change and application will not be functional.
 Implementation Plan - Details / Activities

st will be implemented including all of the tasks and activities to complete the Change Request. If the implementation requires that certain steps be co
required should be built into the Implementation Plan.
Steps:
Implementation Team 1. Shut down NonProd MES application
Activity/Step Detail
2. Clean shutdown of DRAGONDB DB, SESSIONDB and associated DB listener
3. Cold backup of DRAGONDB DB, SESSIONDB
ORACLE DBA 4. Confirm DB backup was successful
5. Install 11.2.0.4 Out of place in a new home
6. Perform standard DB upgrade from 11.2.0.1 to 11.2.0.4
7. Document any issues which occur and the resolution.
8. Perform a cold backup of the upgraded DRAGONDB DB, SESSIONDB
 Test / Validation Plan Details / Activities
st will be tested following completion of all implementation tasks/activities. If testing/validation need to be done for individual tasks/activities, the task/ac

Testing Team / Tester Activity/Step Detail

Back-out Plan Details / Activities

at the environment has been returned to a pre-change configuration/condition. This document must be a step-by-step technical guide including sequen
 Restore database from backup
Testing Team / Tester Activity/Step Detail

ORACLE DBA Restore database from cold backup performed prior to the upgrade.

Communication Plan Details / Activities

n the following scenarios

Client Communication / Update

Application team can proceed with the test, to validate if MES application works with 11.2.0
 Support Group Contact Details

he change request

Contact Number

9845227432

Comments / Special Instructions

 Risk Questionaire
How many users would potentially be impacted if a planned or unplanned
outage or degradation were to occur? 25% of users

During the implementation of a Planned Change does it render a product or

Yes
service unavailable to users?
If during the implementation of the change you encounter issues, can the
Yes
change be rolled back to a pre-change state?

When does the change need to be implemented: During Maintenance Window

Are multiple technologies being modified as part of the change

implementation? No
Does this Change affect an application that must adhere to regulatory
No
compliance guidelines (e.g. SOX, FERC/NERC)?
Does this Change have potential significant downstream service impacts on
No
other applications or systems?

Are there potential Security implications associated with this Change? No

during the change and application will not be functional.

 / Activities

te the Change Request. If the implementation requires that certain steps be completed in a specific order the task/actions sequence
mentation Plan.
Steps:
1. Shut down NonProd MES application
Activity/Step Detail Expected Outcome
ean shutdown of DRAGONDB DB, SESSIONDB and associated DB listener
3. Cold backup of DRAGONDB DB, SESSIONDB
4. Confirm DB backup was successful
5. Install 11.2.0.4 Out of place in a new home
6. Perform standard DB upgrade from 11.2.0.1 to 11.2.0.4
7. Document any issues which occur and the resolution.
Perform a cold backup of the upgraded DRAGONDB DB, SESSIONDB
s / Activities
s. If testing/validation need to be done for individual tasks/activities, the task/actions sequence required should be built into the

Unisys Testing Required (Yes/No) No

Testing Start Date/time

Testing End Date/time

Activity/Step Detail Expected Outcome

Activities
ndition. This document must be a step-by-step technical guide including sequence numbers, planned start date/times, duration,
Restore database from backup
Activity/Step Detail Expected Outcome

d backup performed prior to the upgrade.

s / Activities

Client Communication / Update

can proceed with the test, to validate if MES application works with 11.2.0.4 database
Details

Communication Email Address

abishek.vidyahsanker@in.unisys.com

Comments / Special Instructions