Академический Документы
Профессиональный Документы
Культура Документы
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
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
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
Environment * Production
2. Impact Assessment/Risk
Analysis
Tester(s)/Implementors
Desciption/Details
Success Criteria
Duration
Method
Back Out criteria
Back Out implementer(s)
Before change
At Completion
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
Description Description
2. Impact Assessment/Risk Analysis
Tester(s)/Implementors
Desciption/Details
Success Criteria
Duration
Method
Back Out criteria
Back Out implementer(s)
Backout Method Backout Method
4b. Backout Duration Backout Duration Backout Duration
5. Communication Plan
Before change
At Completion
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
Other Canvass
Networked Storage
Management & Data Other
Protection
Networked Storage
Management & Data Backup Chain creatio
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
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 Instance
DataBase
Listener configuration
Database Migration
DataBase (export-import
approach)
DataBase TNS entry addition
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
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 resources on
Server
virtual servers - NO
Management/Unix
IMPACT
Storage resources on
Server
phisycal servers - NO
Management/Unix
IMPACT
Server
Move to Operation
Management/Unix
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
CHANGE-IP-ADDRESS
Management/Unix
Server AGENT DEPLOYMENT
Management/Unix CMO
Server
Other
Management/Wintel
Storage resources on
Server
virtual servers - NO
Management/Wintel
IMPACT
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
CR - Feasibility
H3G-DISM01-SERVER DISMISSION - UX
H3G-DISM-02-Server dismission - Ws
H3G-DATA07-Restore database
H3G-DATA08-media/tape archiving
H3G-DATA10-restore filesystem
H3G-DB08-Relinking Database
H3G-DB21-Full DB Reorganization
H3G-SAN09-Zoning change/remove
H3G-SUX10-CPU/RAM installation
H3G-SUX11-Disk SO
H3G-SUX24-UX SW INSTALLATION
H3G-SUX26-Unix patching
H3G-SUX32-NW Interface
H3G-SUX39-CHANGE-IP-ADDRESS
H3G-SWIN19-CPU RESIZE
H3G-SVMW01-SNAPSHOT VM
Category ' Category
Workflow Tool Template - Non Production
Production Non-Production
Normal Normal
Routine Routine
H3G-DISM0X-VIRTUAL SERVER DISMISSION - UX
Normal
Normal Normal
Normal OMT
Routine
Normal OMT
Normal Normal
Normal Normal
Normal Normal
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
DB administration service
This Request has to be used for TNS Entry in Database Instance for Client Machine
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: drop database user this activity may generate a task
for Bur team
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
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 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 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 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
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