Professional Documents
Culture Documents
ITIL - An Example Emergency CM Procedure PDF
ITIL - An Example Emergency CM Procedure PDF
Emergency Change Manager Calls ECAB ELAPSED TIME Logging of the emergency RFC
ECAB Quickly assesses impact, risk, resource and urgency Emergency? NO Normal change procedure
YES NO Change Builder(s) (Technology Expert) Urgently builds change and devises backout plan if time is available YES NO
TIME TO TEST?
SUCCESS?
YES
WORKING?
NO
YES Change Manager Change Manager ensures that the emergency RFC is complete and that a change review is completed CLOSED Back to start of process
U C I S A
I T I L :
A N
E X A M P L E
E M E R G E N C Y
C H A N G E
M A N A G E M E N T
P R O C E D U R E
1.
1.1
The role of the Change Manager in the emergency change process is to ensure that the ECAB is convened to discuss the emergency change and make the decision either to implement the change or to re-categorise and take time to plan the change. The Change Managers also ensure that all activities to implement the emergency change are undertaken in an appropriate manner and are documented (which can be retrospective).
U C I S A
I T I L :
A N
E X A M P L E
E M E R G E N C Y
C H A N G E
M A N A G E M E N T
P R O C E D U R E
The process diagram for the emergency change process is shown at the start of this procedure. Emergency changes should only be accepted for one of the following two reasons: To correct any issue/issue(s) on a business critical system or service To protect the business/organisation
The ECAB (Emergency Change Advisory Board) need to ensure that the request for emergency change is in line with one of the two reasons given above.
U C I S A
Third party/supplier involvement in the implementation of the emergency change Impact on other services that run on the same infrastructure (or on software development projects) Business approval (if required) Review/assessment of the change it may be considered that this change in NOT an emergency and is so the change is reprioritised and processed through the normal change management process
3.2.3 ECAB comments/issues All ECAB comments on each emergency change and any Issues that have been discussed must be documented by the Change Manager within the ECAB meeting information section of the request for change form. This information may be completed retrospectively once the emergency change has been implemented. 3.2.4 ECAB recommendations/decisions All ECAB recommendations and decisions that have been discussed must be documented by the Change Manager within the ECAB meeting information section of the request for change form. This information may be completed retrospectively once the emergency change has been implemented. 3.2.5 ECAB authorisation/approval Once all aspect of the emergency change have been considered (as per the ECAB discussion/consideration items above) the ECAB will then give authorisation for the emergency change to be progress into the emergency change build stage of the process. The Change Manager will update the change authorised By section of the request for change form with the names of all the Emergency Change Authorisers. Formal authorisation can be added with electronic signatures, if required. This information may be completed retrospectively once the emergency change has been implemented. 3.2.6 Reprioritisation of an emergency change by the ECAB If the ECAB rejects the emergency change as an emergency priority the change is reprioritised and processed through the normal change process. The Change Manager must inform the Change Initiator and give the reasons for the reprioritisation, and ensure that the change is submitted via the normal change management process. 3.2.7 Rejection of an emergency change by the ECAB If the ECAB rejects the emergency change and decide that it is not appropriate for the change to be considered even through the normal change management process, the Change Manager must inform the Change Initiator that the change has been rejected.
U C I S A
I T I L :
A N
E X A M P L E
E M E R G E N C Y
C H A N G E
M A N A G E M E N T
P R O C E D U R E
3.4.2 Details of the emergency change backout plan The Change Builder(s) needs to document an emergency change backout plan if time allows. High level information on the details of the emergency change backout plan needs to be documented in the request for change form in the section details of the change backout plan, but this again can be completed retrospectively. The name of the person who can authorise the emergency change backout plan with any relevant contact information also needs to be identified. 3.4.3 Emergency change building completed Once all emergency change build activities have been completed The Change Builder will complete date change building completed section of the request for change form, this can be completed retrospectively. 3.4.4 The Change Manager role during emergency change building The Change Manager has a coordination role during emergency change building alongside the normal line management controls, to ensure that the emergency change building activities are both resourced and also completed as a matter of urgency. The Change Manager also ensures that a backout plan is in place, if time allows.
U C I S A
I T I L :
A N
E X A M P L E
E M E R G E N C Y
C H A N G E
M A N A G E M E N T
P R O C E D U R E
3.5.2 Details of the emergency testing carried out The Emergency Change Tester needs to document all testing carried out, but this can be documented retrospectively. 3.5.3 Backout plan tested The Emergency Change Tester needs to ensure that the emergency backout plan is tested and that this is documented in the request for change, if time allows and the documentation can be completed retrospectively. 3.5.4 If emergency change failed testing reason for test failure The Change Tester needs to communicate if the emergency change failed testing and the reasons for this failure. The Change Tester may also make any observations or recommendations that they feel would be useful for the Emergency Change Builder as part of the rebuild of the emergency change. 3.5.5 The Change Manager role during change testing The Change Manager has an overseeing role to ensure that all emergency changes that can be, are thoroughly tested. In all cases involving emergency changes that have not been fully tested, special care needs to be taken during implementation. The Change Manager should assess the risk to the business of any emergency change that is to be installed without complete testing having taken place.
U C I S A
I T I L :
A N
E X A M P L E
E M E R G E N C Y
C H A N G E
M A N A G E M E N T
P R O C E D U R E
Where an emergency change has not achieved its objectives, the Change Manager (or the ECAB) should decide what follow up action is required, which could involve raising a new RFC. If the review is satisfactory the emergency change information should be checked to ensure that all fields have been completed and formally documented into the RFC form, and then the status should be set to CLOSED.
U C I S A
I T I L :
A N
E X A M P L E
E M E R G E N C Y
C H A N G E
M A N A G E M E N T
P R O C E D U R E