Вы находитесь на странице: 1из 50

Version

Version Date Changes Editor


D0a 7/9/2010 Draft version Mina Marinova
V02 7/15/2010 Document issueMina Marinova
V09 5/11/2012 Document issuePaolo Ferrari
V10 5/12/2012 Document issuePaolo Ferrari
V11 5/13/2012 Document issuePaolo Ferrari
V12 5/14/2012 Document issuePaolo Ferrari
V13 6/14/2012 Document issueLuca Tritonj
Instructions
The template should be used in the following cases
CASE 1: When Customer (with no access to workflow tool) raises Change Request and sends to HP CHGM Pro
CASE 2: When HP raises Change Request in the tool and needs to send the details of the Request to the Cus

General Info
Do not modify any cells and worksheets!
Cells for data entry are usually shaded light green when they are empty, changing to white (no fill) backgrou
Many data entry cells have drop down list options for completion, and will not allow any other text
Date cells should be completed using the DD/MM/YYYY hh:mm format

Change Request tab


CASE 1: Change Requesters must complete all fields marked with a Red asterisk (*), along with any other kn
On completion use the button "Email as Attachement" to send the form as an email attachment to t
CASE 2: This tab can be populated using SM export functionality and macros in the file, follow the below ste
Create a grid in SM7 with columns as per worksheet "Fields from SM7" -> Column C "Export Column
Then save an appropriate grid in SM7 (List Options -> Modify Columns -> Detail Options -> Save as
Export the list of changes from SM7: List Options -> Export to Text File, check Export Column Heade
C000xxxxx)
Then click on the "Update Fields" button and follow the instructions from the macro
Error messages might pop up, if:
There is a missing column from the export, a message will pop up specifying the missing column and
If the RFC ID entered is wrong or not existing in the export, there will be a message for the error and

Contacts tab
Details of all relevant contacts for the Change

PickLists tab
Do not change any of the values, except for: Process Mailbox, which should be updated for respective Custo

Fields from SM tab


Do not modify anything in this sheet, as it will corrupt the automation of the file!
NOTE 1: Starred items are mandatory for raising RFC
NOTE 2: Include any available information, even if not marked as mandatory
NOTE 3: Naming convention of the RFC file must be: [SM ID] - [Technology Area] - [Brief Description] Ver. 18
! For emergency change also make a phone call to the respective contact(s) (as per Contact Matrix) to alert them for the emergency change !

Change Details
RFC Number To be fulfilled if you have RfC number
External Change No. assigned
Customer * Ericsson H3G
Department * dba_be@h3g.it Indicate the Business Unit
Other BU/Country/Sites Impacted
(if applicable)
Initiated on * 2017-03-22 15:41:00 DD/MM/YYYY hh:mm:ss
Initiated By (Requester) * Ericsson_CFG_MGM@h3g.it
Requester Email * Ericsson_CFG_MGM@h3g.it
Requester Phone No. 39
Requester Job Title
Emergency ? No A change required to be applied to a managed environment as a
result of (or to prevent) sudden loss or reduction of service

Related Incident ID

Service Server Management/Unix

Environment * Production

Change Catalogue * Storage resources on phisycal servers

Change Type * Normal

Change Catalogue Description

SM9 Change Template H3G-SUX05-Storage resources on phisycal servers


Reason for Change(why?) * Capacity Change
H3G Approval required * No If Approval is required and the Catalogue item is set to routine,
then choose "Other" in Change Catalogue, and report the initial
catalogue item in the "Description of Change" field below
Impact * 3 - Multiple Users
Urgency * Low

Risk Assessment * 1 - Low risk


Priority Low
Requested End Date * 2017-03-29 00:00:00 DD/MM/YYYY hh:mm
Lead time Time to be ready for the implementation

Planned Start Date & Time DD/MM/YYYY hh:mm


Planned Finish Date & Time DD/MM/YYYY hh:mm
Downtime Start Date & Time DD/MM/YYYY hh:mm
Downtime End Date & Time DD/MM/YYYY hh:mm
Affected CI * prser069-prser06a
Associated Cis

Primary Affected CI Down (during Yes Yes/No (blank means No)


change)
Location
Title * Add storage for PRVDG database
1. Description of Change * dba_be@h3g.it: Hi,
for PRVDG database, running on prser069-prser06a, we need
Include all relevant information 1LUN, 100GB. Please add space as soon as possible.
about the requested Change Thank you

2. Impact Assessment/Risk
Analysis

Detail all affected or potentially


impacted:
- users
- services
- applications
and the estimated extent of the
impact and any mitigations that
may be possible
List risks associated with the
change
3a. Pre-Implementation Test Plan
3b. Implementation Plan
3c. Post-Implementation Test Plan

Tester(s)/Implementors
Desciption/Details
Success Criteria

4a. Back Out Plan

Duration
Method
Back Out criteria
Back Out implementer(s)

4b. Backout Duration


5. Communication Plan

Who needs to be informed


Who sends out communications

Before change
At Completion

6. Change Manager/CAB Notes

7. Part of Release No Yes/No (blank means No)


(if yes, provide Release Record Release Record ID
ID)
Implementation details (HP * DD/MM/YYYY hh:mm
resp)
Start Date & Time

Implementation details (HP * DD/MM/YYYY hh:mm


resp)
Finish Date & Time

Implementation details (HP *


resp)
(which Server Farm/Storage
infrastructure has been impacted
by the change - resource
consumption details)
Change Type 0
Change Title 0

Contact Type Name Email Address


Change Requestor
Change Manager H3G.ChangeManagement@hpe.com
Customer Change Manager
Change Supervisor
Change Implementer
Change Tester
Change Approver (Business)
Change Approver (Technical)
Change Approver (Customer)
Additional Required Approvers
Capacity Manager ericsson-h3g.capacity.apm@hpe.com
Situation Manager
Phone Job Title / Function
ChangeType
Routine
Normal

ReasonForChange
Incident Resolution
Problem Resolution
Capacity Change
User Dissatisfaction
New Configuration Item
Update/Obsolete Configuration Item
Release/Proposed Upgrade
Business Requirement
Security/Compliance
Vendor Product/Service Change
Preventative Maintenance
Continuous Improvement

RiskAssessment
0 - No risk
1 - Low Risk
2 - Some Risk
3 - Moderate Risk
4 - Somewhat high Risk
5 - Very high Risk

ImpactAssessment
1 Enterprise
2 Site/Dept
3 Multiple Users
4 User

Urgency
1 Critical
2 High
3 Average
4 Low

Phase
Assessment
Plan
Approve/Schedule
Test
Pre-Implementation Approval
Implement
Review/Closure
Closed

ProcessMailbox

PriorityCalc
1 Critical
2 High
3 Average
4 Low

YesNo
Yes
No

Service
Other
DataBase
Network Management
Network Secuity
Networked Storage Management & Data
Protection
Server Management/Unix
Server Management/Wintel
Storage Area Network

Location
H3G Ericsson-IT-BERNINA
H3G Ericsson-IT-ROMA
H3G Ericsson-IT-TREZZANO
RFC Form Fields Columns in SM7 Export Columns in SM7

RFC Number Change ID Change Number


External Change No. External Change No Foreign ID
Phase Phase Phase
Customer Company Company
Department Department Department
Other BU/Country/Sites Impacted (if
applicable)
N/A N/A
Initiated on Open Time Open Date
Initiated By (Requester) Initiated by Initiator
Requester Email N/A N/A
Requester Phone No. N/A Initiator Phone
Requester Job Title N/A Initiator Dept
Change Type Category Category
Reason for Change Reason for Change Reason for Change
Impact Impact * Initial Impact
Urgency Urgency * Urgency
Risk Assessment Risk Assessment * Risk Assessment
Priority (calculated) Priority header,priority.code
Requested End Date Requested End Date Requested Date
Planned Start Date & Time Planned Start Planned Start
Planned Finish Date & Time Planned End Planned End
Downtime Start Date & Time Downtime Start Downtime Start
Downtime End Date & Time Downtime End Downtime End
Service Service Affected Item
Affected CI Affected CI (first row) Affected CIs
Associated Cis Affected CI (second row a Affected CIs

Primary Affected CI Down (during Configuration Item(s) DowCI Down


change)
Location Location Location
Title Title Title
1. Description of Change

Include all relevant information about


the requested Change

Description Description
2. Impact Assessment/Risk Analysis

Detail all affected or potentially


impacted:
- users
- services
- applications
and the estimated extent of the impact
and any mitigations that may be
possible
List risks associated with the change Impact Assessment/Risk AImpact Assessment
3a. Pre-Implementation Test Plan
3b. Implementation Plan
3c. Post-Implementation Test Plan

Tester(s)/Implementors
Desciption/Details
Success Criteria

Implementation CommentImplementation Comments


4a. Back Out Plan

Duration
Method
Back Out criteria
Back Out implementer(s)
Backout Method Backout Method
4b. Backout Duration Backout Duration Backout Duration
5. Communication Plan

Who needs to be informed


Who sends out communications

Before change
At Completion

Implementation CommentImplementation Comments


6. Change Manager/CAB Notes
N/A N/A
7. Part of Release Release Management (cheRelease Candidate
(if yes, provide Release Record ID)
N/A (manually, as it can not be extracted)

NOTE: Fields marked with * are exported with number, who should be mapped to the respective word
DO NOT modify the rows or columns on this sheet.

0 0
0 0
0 0
0 0
0 0

0 0
0 0

0 0
0 0
0 0
0 0
0 0
0 0
0 0
0 0
0 0
0 0
0 0
0 0
0 0
0 0
0 0
0 0
0 0
0 0
0 0
0 0
0 0
0 0

0 0
0 0

0 0

0 0
0 0

0 0

0 0

respective word
Service Change Name

Other CR - Feasibility

No standard service
Other
request

Server Server dismission -


Management/Unix Ux

Server Server dismission -


Management/Wintel Ws

Server Disposal Ux - ESL


Management/Unix status update

Server Disposal Win - ESL


Management/Wintel status update

Server VIRTUAL SERVER


Management/Unix DISMISSION - UX

Other Canvass
Networked Storage
Management & Data Other
Protection

Networked Storage
Management & Data Backup Chain creatio
Protection

Networked Storage Back up client


Management & Data installation &
Protection scheduling backup
Back-up extra
Networked Storage
ordinary (extra-
Management & Data
scheduling on defined
Protection
back-up)
Networked Storage
Backup scheduling
Management & Data
change
Protection

Networked Storage
New backup (one
Management & Data
shot)
Protection

Networked Storage
Management & Data Restore Database
Protection
Networked Storage
Management & Data Media/tape archiving
Protection

Networked Storage
Management & Data Backup policy review
Protection

Networked Storage
Management & Data Restore filesystem
Protection

Networked Storage
CONTROLM AGENT
Management & Data
INSTALLATION
Protection

DataBase Other

New stand alone DB


DataBase
instance

New ORACLE Cluster


DataBase
failover Instance

New ORACLE RAC


DataBase
Instance

Perform Database
DataBase
Instance Tuning

DB
DataBase commission/decommi
ssion

Check database
security file
DataBase
permissions, internal
database security

DB shutdown and
DataBase
startup

DataBase Relinking database

Database Instance
DataBase
Listener configuration
Database Migration
DataBase (export-import
approach)
DataBase TNS entry addition

DataBase TNS entry addition

DataBase DB link creation

Determine the
necessary database
DataBase
software security
patching baseline
Setting oracle
auditing and
DataBase
monitoring security
audit logs
Create database user
DataBase
account
Modify database user
DataBase account/set/unset
privileges

Delete datbase user


DataBase
account
Setup basic database
DataBase security
administration
Create and manage
DataBase data files, table
spaces
Drop data files, table
DataBase
spaces
Online & offline
DataBase
defragmentation

Reorganize specific
DataBase database objects,
tables space, etc
Apply One-Off Oracle
DataBase
Patch
Apply CPU (Critical
DataBase Patch Updates)
Oracle Patch
Apply PSU (PatchSet
DataBase
Update) Oracle Patch
Upgrade Oracle
DataBase
Database
Data Archiving
DataBase
Execution
SQL Script Execution
DataBase PRODUCTION
environments

Storage Area
Other
Network

Storage Area Storage Space


Network allocation

Storage Area FC port (for storage)


Network add/change/configure

Storage Area HBA configuration


Network change

Storage Area Zoning


Network change/remove
Server
Other
Management/Unix

Server Storage resources on


Management/Unix virtual servers

Storage resources on
Server
virtual servers - NO
Management/Unix
IMPACT

Server Storage resources on


Management/Unix phisycal servers

Storage resources on
Server
phisycal servers - NO
Management/Unix
IMPACT

Server
Move to Operation
Management/Unix

Server INSTALLATION New


Management/Unix Server

Server Move to Operation


Management/Unix NO DB
Server Move to Operation
Management/Unix NO PROD

Server Move to Operation


Management/Unix NO PROD NO DB

INSTALLATION &
Server
Move To Operation -
Management/Unix
New Server
Server
RAM Installation
Management/Unix
Server
Disk SO
Management/Unix
Server
NAS File System
Management/Unix
Server
UX SW INSTALLATION
Management/Unix
Server Software update and
Management/Unix patch
Server
Unix patching
Management/Unix
Server UNIX PATCHING-NO
Management/Unix PROD
Server
NW Interface
Management/Unix
Server
GO LIVE APPLICATION
Management/Unix

Server P2V Move to


Management/Unix Operation

Server P2V Move to


Management/Unix Operation NO DB

Server
CHANGE-IP-ADDRESS
Management/Unix
Server AGENT DEPLOYMENT
Management/Unix CMO
Server
Other
Management/Wintel

Server Storage resources on


Management/Wintel virtual servers
Server Storage resources on
Management/Wintel virtual farm

Storage resources on
Server
virtual servers - NO
Management/Wintel
IMPACT

Server Storage resources on


Management/Wintel phisycal servers

Storage resources on
Server
phisycal servers - NO
Management/Wintel
IMPACT
Server Machine policy
Management/Wintel change
Server
User policy change
Management/Wintel

Server
Move to Operation
Management/Wintel

Server Move to Operation


Management/Wintel NO DB

Server Move to Operation


Management/Wintel NO PROD

Server Move to Operation


Management/Wintel NO PROD NO DB

Server Dismission of virtual


Management/Wintel FMO servers

Server New virtual server


Management/Wintel installation

New virtual server


Server
installation - Only
Management/Wintel
from Transformation
Server New physical server
Management/Wintel installation
Server
GO LIVE APPLICATION
Management/Wintel
Server P2V Move to
Management/Wintel Operation

Server P2V Move to


Management/Wintel Operation NO DB

Server Share on physical


Management/Wintel cluster
Server
CPU Resize
Management/Wintel
Server
NAS FILESYSTEM
Management/Wintel
Server
NAS FILESYSTEM
Management/Wintel

Server Snapshot of virtual


Management/Wintel machine
Workflow Tool Template - Production

CR - Feasibility

H3G-DISM01-SERVER DISMISSION - UX

H3G-DISM-02-Server dismission - Ws

H3G-DISM-03-ESL status update - Ux

H3G-DISM-04-ESL status update - Win

H3G-DISM0X-VIRTUAL SERVER DISMISSION - UX

H3G-DATA01-Backup Chain creation&update

H3G-DATA02-Back up client installation & scheduling backup

H3G-DATA03-BACK-UP EXTRA ORDINARY (EXTRA-SCHEDULING ON DEFINED BACK-


UP)

H3G-DATA05-Backup scheduling change

H3G-DATA06-New backup (one shot)

H3G-DATA07-Restore database
H3G-DATA08-media/tape archiving

H3G-DATA09-Backup policy review

H3G-DATA10-restore filesystem

H3G-DATA11-CONTROLM AGENT INSTALLATION

H3G-DB01-New stand alone DB instance

H3G-DB02-New ORACLE Cluster failover Instance

H3G-DB03-New ORACLE RAC Instance

H3G-DB04-Perform Database Instance Tuning

H3G-DB05-Perform Database Commission/Decommission

H3G-DB06-Check database security file permissions, internal database security

H3G-DB07-Database Shutdown and Startup

H3G-DB08-Relinking Database

H3G-DB09-Database Instance Listener configuration

H3G-DB10-Database Refresh (export-import approach)


H3G-DB11-Database TNS entry addition

H3G-DB11A-Database TNS entry addition (Client Machine)

H3G-DB12-Database link creation

H3G-DB13-Determine the necessary database software security patching


baseline

H3G-DB14-Setting oracle auditing and monitoring security audit logs

H3G-DB15-Create database user account

H3G-DB16-Modify database user account/set/unset privileges

H3G-DB17-Delete datbase user account

H3G-DB18-Setupdatabase security administration

H3G-DB19-Create and manage data files, table spaces

H3G-DB20-Drop data files, table spaces

H3G-DB21-Full DB Reorganization

H3G-DB22-Reorganize specific database objects, tables space, etc

H3G-DB25-Apply One-Off Oracle Patch

H3G-DB26-Apply CPU (Critical Patch Updates) Oracle Patch

H3G-DB27-Apply PSU (PatchSet Update) Oracle Patch

H3G-DB28-Upgrade Oracle Database

H3G-DB29-Data Archiving Execution


H3G-DB30-SQL Script Execution PRODUCTION environments

H3G-SAN01-Storage Space allocation

H3G-SAN07-FC port (for storage) add/change/configure

H3G-SAN08-HBA configuration change

H3G-SAN09-Zoning change/remove

H3G-SUX04-Storage resources on virtual servers

H3G-SUX04b-Storage resources on virtual servers - NO IMPACT

H3G-SUX05-Storage resources on phisycal servers

H3G-SUX05b-Storage resources on phisycal servers - NO IMPACT

H3G-SUX09 - Move to Operation - UNIX

H3G-SUX09A - INSTALLATION New Server- UNIX

H3G-SUX09B - Move to Operation NO DB - UNIX


H3G-SUX09C - Move to Operation NO PROD - UNIX

H3G-SUX09D - Move to Operation NO PROD NO DB - UNIX

H3G-SUX09E - INSTALLATION AND MOVE TO OPERATION - UNIX

H3G-SUX10-CPU/RAM installation

H3G-SUX11-Disk SO

H3G-SUX-15 - NAS FILESYSTEM CREATION FOR UNIX-LINUX

H3G-SUX24-UX SW INSTALLATION

H3G-SUX25-SW update and Patch

H3G-SUX26-Unix patching

H3G-SUX26-UNIX PATCHING-NO PROD

H3G-SUX32-NW Interface

H3G-SUX34-GO LIVE APPLICATION

H3G-SUX35-P2V-MOVE TO OPERATION - UNIX

H3G-SUX35B-P2V-MOVE TO OPERATION NO DB- UNIX

H3G-SUX39-CHANGE-IP-ADDRESS

H3G-SUX40 - AGENT DEPLOYMENT CMO - UNIX

H3G-SWIN04-Storage resources on virtual servers


H3G-SWIN04b-Storage resources on virtual farm

H3G-SWIN04c-Storage resources on virtual servers - NO IMPACT

H3G-SWIN05-Storage resources on phisycal servers

H3G-SWIN05b-Storage resources on phisycal servers - NO IMPACT

H3G-SWIN08-Machine policy change

H3G-SWIN09-User policy change

H3G-SWIN10-Move to Operation - WINTEL

H3G-SWIN10B - Move to Operation NO DB - WINTEL

H3G-SWIN10C - Move to Operation NO PROD - WINTEL

H3G-SWIN10D - Move to Operation NO PROD NO DB - WINTEL

H3G-SWIN11-DISMISSION OF VIRTUAL FMO SERVERS

H3G-SWIN13-new virtual server installation

H3G-SWIN13b-new virtual server installation - Only from Transformation

H3G-SWIN14-new physical server installation

H3G-SWIN15-GO LIVE APPLICATION


H3G-SWIN16-P2V-MOVE TO OPERATION - WINTEL

H3G-SWIN16-P2V-MOVE TO OPERATION NO DB - WINTEL

H3G-SWIN17-SHARE ON PHYSICAL CLUSTER

H3G-SWIN19-CPU RESIZE

H3G-SWIN21 - NAS FILESYSTEM CREATION FOR WINDOWS

H3G-SWIN22- NAS FILESYSTEM REMOVAL FOR WINDOWS

H3G-SVMW01-SNAPSHOT VM
Category ' Category
Workflow Tool Template - Non Production
Production Non-Production

Routine CR - Feasibility Routine

Normal Normal

Routine H3G-DISM01-SERVER DISMISSION - UX Routine

Normal H3G-DISM-02-Server dismission - Ws Normal

Routine H3G-DISM-03-ESL status update - Ux Routine

Routine H3G-DISM-04-ESL status update - Win Routine

Routine Routine
H3G-DISM0X-VIRTUAL SERVER DISMISSION - UX
Normal

Normal Normal

Normal H3G-DATA01-Backup Chain creation&update Normal

Routine H3G-DATA02-Back up client installation & scheduling backup Routine

H3G-DATA03-BACK-UP EXTRA ORDINARY (EXTRA-


Normal Normal
SCHEDULING ON DEFINED BACK-UP)

Routine H3G-DATA05-Backup scheduling change Routine

Normal H3G-DATA06-New backup (one shot) Normal

Normal H3G-DATA07-Restore database Normal


Normal H3G-DATA08-media/tape archiving Normal

Normal H3G-DATA09-Backup policy review Normal

Normal H3G-DATA10-restore filesystem Normal

Normal H3G-DATA11-CONTROLM AGENT INSTALLATION Normal

Normal H3G-DB01-New stand alone DB instance Normal

Normal H3G-DB02-New ORACLE Cluster failover Instance Normal

Normal H3G-DB03-New ORACLE RAC Instance Normal

Normal H3G-DB04-Perform Database Instance Tuning NO PROD Routine

Routine H3G-DB05-Perform Database Commission/Decommission Routine

H3G-DB06-Check database security file permissions,


Normal Routine
internal database security NO PROD

Normal OMT

Routine H3G-DB08-Relinking Database Routine

Normal H3G-DB09-Database Instance Listener configuration NO PRO Routine

Normal H3G-DB10-Database Refresh (export-import approach) NO P Routine


Normal OMT

Routine

Normal OMT

H3G-DB13-Determine the necessary database software


routine routine
security patching baseline

H3G-DB14-Setting oracle auditing and monitoring security


routine routine
audit logs

routine H3G-DB15-Create database user account routine

H3G-DB16-Modify database user account/set/unset


routine routine
privileges

Routine H3G-DB17-Delete datbase user account routine

Routine H3G-DB18-Setupdatabase security administration routine

Routine H3G-DB19-Create and manage data files, table spaces routine

Normal H3G-DB20-Drop data files, table spaces Normal

Normal H3G-DB21-Full DB Reorganization Normal

H3G-DB22-Reorganize specific database objects, tables


Normal Normal
space, etc

Normal H3G-DB25-Apply One-Off Oracle Patch Normal

Normal H3G-DB26-Apply CPU (Critical Patch Updates) Oracle Patch Normal

Normal H3G-DB27-Apply PSU (PatchSet Update) Oracle Patch Normal

Normal H3G-DB28-Upgrade Oracle Database Normal

Normal H3G-DB29-Data Archiving Execution Normal


Routine N/A use OMT OMT

Normal Normal

Normal H3G-SAN01-Storage Space allocation Normal

Normal H3G-SAN07-FC port (for storage) add/change/configure Normal

Normal H3G-SAN08-HBA configuration change Normal

Normal H3G-SAN09-Zoning change/remove Normal

Normal Normal

Normal H3G-SUX04-Storage resources on virtual servers Normal

Normal H3G-SUX04b-Storage resources on virtual servers - NO IMPA Normal

Normal H3G-SUX05-Storage resources on phisycal servers Normal

Normal H3G-SUX05b-Storage resources on phisycal servers - NO IMP Normal

Routine H3G-SUX09 - Move to Operation - UNIX Routine

Normal H3G-SUX09A - INSTALLATION New Server- UNIX Normal

Routine H3G-SUX09B - Move to Operation NO DB - UNIX Routine


Routine H3G-SUX09C - Move to Operation NO PROD - UNIX Routine

Routine H3G-SUX09D - Move to Operation NO PROD NO DB - UNIX Routine

Routine H3G-SUX09E - INSTALLATION AND MOVE TO OPERATION - UNIRoutine

Normal H3G-SUX10-CPU/RAM Installation Normal

Routine H3G-SUX11-Disk SO Routine

Routine H3G-SUX-15 - NAS FILESYSTEM CREATION FOR UNIX-LINUX Routine

Routine H3G-SUX24-UX SW INSTALLATION Routine

Normal H3G-SUX25-SW update and Patch Routine

Normal H3G-SUX26-Unix patching Normal

Routine H3G-SUX26-UNIX PATCHING-NO PROD Routine

Normal H3G-SUX32-NW Interface Normal

Routine H3G-SUX34-GO LIVE APPLICATION Routine

Routine H3G-SUX35-P2V-MOVE TO OPERATION NO PROD- UNIX Routine

Routine H3G-SUX35B-P2V-MOVE TO OPERATION NO PROD NO DB- UNIX Routine

Normal H3G-SUX39-CHANGE-IP-ADDRESS Normal

Routine H3G-SUX40 - AGENT DEPLOYMENT CMO - UNIX Routine

Normal Normal

Normal H3G-SWIN04-Storage resources on virtual servers Normal


Normal H3G-SWIN04b-Storage resources on virtual farm Normal

Routine H3G-SWIN04c-Storage resources on virtual servers - NO IMP Routine

Normal H3G-SWIN05-Storage resources on phisycal servers Normal

Routine H3G-SWIN05b-Storage resources on phisycal servers - NO IM Routine

Normal H3G-SWIN08-Machine policy change Normal

Normal H3G-SWIN09-User policy change Routine

Routine H3G-SWIN10-Move to Operation - WINTEL Routine

Routine H3G-SWIN10B - Move to Operation NO DB - WINTEL Routine

Routine H3G-SWIN10C - Move to Operation NO PROD - WINTEL Routine

Routine H3G-SWIN10D - Move to Operation NO PROD NO DB - WINTE Routine

Normal H3G-SWIN11-DISMISSION OF VIRTUAL FMO SERVERS Normal

Routine H3G-SWIN13-new virtual server installation Routine

H3G-SWIN13b-new virtual server installation - Only from


Routine Routine
Transformation

Routine H3G-SWIN14-new physical server installation Routine

Routine H3G-SWIN15-GO LIVE APPLICATION Routine


Routine H3G-SWIN16-P2V-MOVE TO OPERATION NO PROD - WINTEL Routine

H3G-SWIN16B-P2V-MOVE TO OPERATION NO PROD NO DB -


Routine WINTEL Routine

Routine H3G-SWIN17-SHARE ON PHYSICAL CLUSTER Routine

Normal H3G-SWIN19-CPU RESIZE Normal

Routine H3G-SWIN21 - NAS FILESYSTEM CREATION FOR WINDOWS Routine

Normal H3G-SWIN22- NAS FILESYSTEM REMOVAL FOR WINDOWS Normal

Routine H3G-SVMW01-SNAPSHOT VM Routine


Description

This request has to be used when customer intention is to engage Technical Office to
evaluate a business requirement (usually comes wit a CR number). Outcome of this
request is a technical deliverabl (the DID document) which explains to customer if the
requirements has impact on the menagaed environment or not

This request has to be used once customer doesn't find any suitable item in the catalogue
that matches with the need to engage HP. Once RfC is received, delivery teams will
analyze the request and, in case the request could be a new entry in the catalogue, they
will advice HP Change Manager to update the Change Catalogue accordingly

This request is used to trigger the operational teams in applying the decommissioning
checklists for Unix servers. Requestor has already received customer approval to proceed
with the decommissioning

This request is used to trigger the operational teams in applying the decommissioning
checklists for Windows servers. Requestor has already received customer approval to
proceed with the decommissioning

This request is used during the decommissioning phase once the servers have been
moved out of the datacenter; it implies only a status update in ESL with the "deinstalled"
value. It applies to Unix systems

This request is used during the decommissioning phase once the servers have been
moved out of the datacenter; it implies only a status update in ESL with the "deinstalled"
value. It applies to Wintel systems

This request is used to trigger the operational teams in applying the decommissioning
checklists for Unix Virtual Servers. Requestor has already received customer approval to
proceed with the decommissioning
This request has to be used to initiate a request for Canvass assigned to DBA team

This item to be used when in the catalogue requestor cannot find a suitable item that
properly matches with his request

This request has to be used when requestor needs to define a new chain of backup or
modified a chain of backup scheduled on Scheduler tool.

This request has to be used when requestor wants the installation of a backup client on a
new or existing server and want backup to be scheduled in accord with the backup policy.
The requestor must provide the backup policy.

This request has to used when requestor needs a backup (on demand) on a server that is
currently managed by the backup server. This activity could impact service (depending on
the specific backup needed)

This request has to be used when requestor wants to change the schedule of a specific
backup

This request has to be used when requestor needs a backup of a server that is not
managed by the backup server

This request has to be used when requestor needs a restore of a database on a server
that is currently managed by the backup server; this change can have an impact on
service then must be approved
This request has to be used when requestor needs an extra ordinary backup with a
specific retention

This request has to be used when requestor wants a change on the backup policies like
retention, filesystem dataset, etc

This request has to be used when requestor wants the restore of specific filesystems on a
server that is currently managed by the backup server; this change can have an impact
on service then must be approved

This request has to be used when requestor needs to install and configure on a server
ControlM agent.

This item to be used when in the catalogue requestor cannot find a suitable item that
properly matches with his request

OS, Network and Storage installed following Oracle Best Practices or installation Rules
The related KPI measures the time to make available for Application use of new Stand
Alone Oracle Database Instance

OS, Network and Storage installed following Oracle Best Practices or installation Rules
The related KPI measures the time to make available for Application use of new CLUSTER
FAILOVER DB INSTANCE

OS, Network and Storage installed following Oracle Best Practices or installation Rules
The related KPI measures the time to make available for Application use of new RAC
Oracle Database Instance

Performance, Capacity &


Availability Reporting: This activity consists in:
1)Edit database Instance init parameters accordingly to the user/customer request;
2)Edit database Instance init parameters accordingly to Oracle Diagnostic tools advice
(requires customer approval);
3)Statistics and indexes maintenance (requires customer approval)

This Request has to be used for Commissioning/Decommissioning of Database Instance

DB administration service

This Request has to be used for Shutdown/Startup of Database Instance

This Request has to be used for Relinking Database Instance

Maintenance & Housekeeping: edit Listener parameters according to the customer


request, may generate an outage due to listener recycle

Maintenance & Housekeeping


This Request has to be used for TNS Entry in Database Instance

This Request has to be used for TNS Entry in Database Instance for Client Machine

This Request has to be used for Database Link Creation

Security management: according to Oracle Security bullettin and Application Certification


matrix (provided by the Application management) determine what patches must be
applied to an Oracle databse instance

Security management: Oracle Audit setupaccording to Oracle Documentation

Security management: create a database user account, this task includes also an initial
privileges setup (details provided by the requestor)

Setup of new database instances: grant or revoke privileges of a database user

Setup of new database instances: drop database user this activity may generate a task
for Bur team

Setup of new database instances: e.g. Radius Implementation on a database

Storage Management: Tablespace, datafiles creation and resize; it could generate tasks
for SAN, BUR and Unix teams
Storage Management: Tablespace, datafiles drop, it could generate tasks for SAN, BUR
and Unix teams

Storage Management: Full DB segments reorganization

Storage Management:Reorganization of single databse objects

Upgrade & fix: Apply a One Off Patch to a Oracle Database according to the Oracle Patch
Documentation: may require instance recycle and could generate tasks for BUR and Unix
teams
Upgrade & fix: Apply a CPU to a Oracle Database according to the Oracle Patch
Documentation: may require instance recycle and could generate tasks for BUR and Unix
teams
Upgrade & fix: Apply a PSU to a Oracle Database according to the Oracle Patch
Documentation: may require instance recycle and could generate tasks for BUR and Unix
teams
Upgrade & fix: (e.g. From 10.2.0.4 to 11.2.0.1) according to the Oracle Patch
Documentation: may require instance recycle and could generate tasks for SAN, BUR and
Unix teams
Maintenance & Housekeeping: (e.g. GBC Data Archiving Execution)
Execute a SQL script(DCL, DDL, DML, PL-SQL) as a delivery against a database: no
validation or optimization will be provided. At the end of the execution a log will be sent
to the Application Management and possible errors reported. Valid for modification of the
DB structure in the PRODUCTION environments. Script execution not modifying the DB
structure or any script for NON PRODUCTION environments are managed via OMT.

This item to be used when in the catalogue requestor cannot find a suitable item that
properly matches with his request

This change is intended already approved by Capacity manager, if not please select
"Other" in service field and describe the change request in the Change Description field
Storage team will check if the needed volume is available and, if not, will create it and
then assign to server
This request is used when requestor wants a creation of a new space on storage
equipments, but no further activities on server side is required. If this is not the case, the
correct item is to be found inside the "Server Management" area.

This request has to be used when requestor wants a change on the storage FC ports
configuration or assignement, due to a specific requirements (i.e. performance of single
ports)
This request has to be used when requestor needs the HBA configuration of load
balancing or path failover. In case FC is not redundant this activity might impact the
service and then needs to be approved
This request has to be used when requestor needs to add or change the SAN resources
(ports) assigned to the specific server
This item to be used when in the catalogue requestor cannot find a suitable item that
properly matches with his request

This request has to be used when requestor needs a new LUN volume to be assigned to
an OS virtual, to increase the resources of an existing filesystem. This change is not pre
approved as it could be required a temporary outage to mount the new space on the
system. Request then has to be verified case by case
This request has to be used when requestor needs a new LUN volume to be assigned to
an OS virtual, to increase the resources of an existing filesystem. This change is pre
approved as the system where the request has to be implemented does not have any
impact on service
This request has to be used when requestor needs a new LUN volume to be assigned to
an OS phisyacl to increase the resources of an existing filesystem. This change is not pre
approved as it could be required a temporary outage to mount the new space on the
system. Request then has to be verified case by case
This request has to be used when requestor needs a new LUN volume to be assigned to
an OS phisyacl to increase the resources of an existing filesystem. This change is pre
approved as the system where the request has to be implemented does not have any
impact on service
This request is to be used when a new system (or number of new systems) of PROD
environment are required to be moved into operation, as the implementation phase has
been completed. This request aims to control that all the expected steps for the FMO
model are properly executed
Installation request for a new Unix server

This request is to be used when a new system (or number of new systems) of PROD
environment (No DB instances) are required to be moved into operation, as the
implementation phase has been completed. This request aims to control that all the
expected steps for the FMO model are properly executed
This request is to be used when a new system (or number of new systems) of NO PROD
environment are required to be moved into operation, as the implementation phase has
been completed. This request aims to control that all the expected steps for the FMO
model are properly executed

This request is to be used when a new system (or number of new systems) of NO PROD
environment (No DB instances)are required to be moved into operation, as the
implementation phase has been completed. This request aims to control that all the
expected steps for the FMO model are properly executed

This used when is required a INSTALLATION and take in charge of system

This request is to be used when are required other RAM memory. In this case we need the
authorization of competent LAA or service manger

This request is to be used when are required other disk S.O.

This request has to be used when the requestor is asking to create a NAS share

This request has to be used when the requestor is asking for Software Installation

This request is to be used when are required the SW Update and Patch. In this case we
need the authorization of competent LAA or service manger
This request is to be used when are required the Unix Patching. In this case we need the
authorization of competent LAA or service manger

This request is to be used when are required the Unix Patching for non-Prod Servers

This request is to be used when are required other NW interface. In this case we need the
authorization of competent LAA or service manger
This activity has to be requested when customer declares the application GO LIVE; with
this change, HP will set ESL system status "in production" and will activate the
infrastructure monitoring
This request is to be used when a new system (or number of new systems) are required to
be moved into operation, as the implementation phase has been completed. This request
aims to control that all the expected steps for the FMO model are properly executed
This request is to be used when a new system (or number of new systems) (No DB
instances) are required to be moved into operation, as the implementation phase has
been completed. This request aims to control that all the expected steps for the FMO
model are properly executed
This request is to be used when the IP Address of a Unix Server needs to be
Updated/Changed.

This request is to be used for Agent Deployment CMO.

This item to be used when in the catalogue requestor cannot find a suitable item that
properly matches with his request

This request has to be used when requestor needs a new LUN volume to be assigned to
an OS virtual, to increase the resources of an existing filesystem. This change is not pre
approved as it could be required a temporary outage to mount the new space on the
system. Request then has to be verified case by case
This request has to be used when requestor needs a new LUN volume to be assigned to
the virtual farm, to increase the resources of an existing filesystem. This change is not pre
approved as it could be required a temporary outage to mount the new space on the
system. Request then has to be verified case by case
This request has to be used when requestor needs a new LUN volume to be assigned to
an OS virtual, to increase the resources of an existing filesystem. This change is pre
approved as the system where the request has to be implemented does not have any
impact on service
This request has to be used when requestor needs a new LUN volume to be assigned to
an OS physical to increase the resources of an existing filesystem. This change is not pre
approved as it could be required a temporary outage to mount the new space on the
system. Request then has to be verified case by case
This request has to be used when requestor needs a new LUN volume to be assigned to
an OS physical to increase the resources of an existing filesystem. This change is pre
approved as the system where the request has to be implemented does not have any
impact on service
This request has to be used when requestor needs to apply specific local or domain
policies on a server or group of servers. In general this activity can have an impact, then
must be approved
This request has to be used when requestor needs to apply specific local or domain
policies on an account or group of accounts. In general this activity can have an impact,
then must be approved
This request is to be used when a new system (or number of new systems) are required to
be moved into operation, as the implementation phase has been completed. This request
aims to control that all the expected steps for the FMO model are properly executed

This request is to be used when a new system (or number of new systems) of PROD
environment (No DB instances) are required to be moved into operation, as the
implementation phase has been completed. This request aims to control that all the
expected steps for the FMO model are properly executed

This request is to be used when a new system (or number of new systems) of NO PROD
environment are required to be moved into operation, as the implementation phase has
been completed. This request aims to control that all the expected steps for the FMO
model are properly executed

This request is to be used when a new system (or number of new systems) of NO PROD
environment (No DB instances)are required to be moved into operation, as the
implementation phase has been completed. This request aims to control that all the
expected steps for the FMO model are properly executed

This request has to be used when requestor needs Dismission of Virtual FMO sevrers

This request has to be used when requestor needs an implementation of a new virtual
server.
Approval to this request is part of the "Go to development" that the related CR received.
As this request impacts the Virtual farm, the Capacity Manager approval is required before
moving into implementation
This request has to be used only to request new virtual servers that are in scope of the
Transformation stream. The only authorized requestors are:
Fabrizio Montanini , Giuseppe Proietti (HP employee)
This request has to be used when requestor needs an implementation of a new physical
server.
Approval to this request is part of the "Go to development" that the related CR received
This activity has to be requested when customer declares the application GO LIVE; with
this change, HP will set ESL system status "in production" and will activate the
infrastructure monitoring
This request is to be used when a new system (or number of new systems) are required to
be moved into operation, as the implementation phase has been completed. This request
aims to control that all the expected steps for the FMO model are properly executed
This request is to be used when a new system (or number of new systems) (No DB
instances) are required to be moved into operation, as the implementation phase has
been completed. This request aims to control that all the expected steps for the FMO
model are properly executed
This request is to be used when a nw share is needed on a physical cluster

This request has to be used when requestor needs to resize virtual CPU

This request has to be used when the requestor is asking to create a NAS share

This request has to be used when the requestor is asking to remove a NAS share

This request has to be used when requestor needs a snapshot of a virtual machine to be created on
the farm for test purposes on the original server. The snapshot will be removed from the farm within
a month.
Prevent Approval

To be checked with Stefan

To be checked with Stefan


Capacity Manager

Capacity Manager

Capacity Manager

Capacity Manager

Capacity Manager

Capacity Manager
Capacity Manager To be merged to RAM/CPU

Capacity Manager
Capacity Manager

Capacity Manager

Capacity Manager

Capacity Manager
HP Change Type
Normal

Normal Urgent

Routine

Emergency

Major

*HP Change Lead Time is the amount of time between the Request for Change being raised and the start dat
implementation
HP Description
Any temporary or permanent change to a service or the infrastructure with a certain level of
risk within a managed environment. Careful planning and adherence to the Change
Management process can reduce any potential risk and impact associated with an individual
change.
The Normal Change type also includes those changes which are considered as urgent by the
business. Urgent Changes follow the Normal Change process flow, but by the nature of their
potential impact to the business they by-pass normal Customer lead times and therefore may
need to be implemented prior to the next scheduled CAB review. The planning, review and
approval of these changes occurs in a streamlined controlled fashion. The risks associated
with Urgent Changes are higher since the available time to assess, plan and implement these
changes is reduced. It is important therefore to ensure that Urgent Changes are raised as
exceptions and not the norm.

A well defined, fully documented change with low risk and / or significant value in providing
stability to the business. These changes follow a predefined set of work instructions.
A change required to be applied to a managed environment as a result of (or to prevent)
sudden loss or reduction of service. Due to their nature Emergency Changes are always
derived from business critical incidents. Emergency Changes are the only change type that is
reactive, not proactive.

Major changes are those changes which have high Impact and Risk associated to them

nge Lead Time is the amount of time between the Request for Change being raised and the start date of the Change
entation
Change Lead Time *
for Production
Environment

Post implementation

10

nd the start date of the Change

Вам также может понравиться