7.0 An Emergency Change is a change that must be introduced as soon as possible; for Emergency example, to resolve a Major Incident or implement a critical security patch. The Change Change Management Process includes a specific procedure for handling Emergency Changes. 8.0 Standard Changes are changes that are repeatable, occur frequently, and are proven Standard Change to be low risk. A pre-defined workflow will be established, approved by the CAB and subsequently followed. Approved Standard Changes are not reviewed by the CAB. Record and Review Process This section describes the Record and Review Process. Record and Review Process Flow 1.0 Record and Review Process Activity Descriptions D.1.1 Emergency Change? Purpose To determine if the Change is an Emergency. If the Change is an emergency, events will be handled by the separate Emergency Change Process Decision Yes Go to 8.0 Emergency Change Process – No Go to 1.1 Create Change Record – 1.2 Create Change Record To ensure all Changes are appropriately recorded in the ITSM Tool. Purpose Requirement When recording a Change Record, it is the responsibility of Tier 1 to correctly Statement complete all of the required information. Request for Change Input
7.0 Emergency Change An Emergency Change is a change that must be introduced as soon as possible; for example, to resolve a Major Incident or implement a critical security patch. The Change Management Process includes a specific procedure for handling Emergency Changes. 8.0 Standard Change Standard Changes are changes that are repeatable, occur frequently, and are proven to be low risk. A pre-defined workflow will be established, approved by the CAB and subsequently followed. Approved Standard Changes are not reviewed by the CAB. Record and Review Process This section describes the Record and Review Process. Record and Review Process Flow 1.0 Record and Review Process Activity Descriptions D.1.1 Emergency Change? Purpose To determine if the Change is an Emergency. If the Change is an emergency, events will be handled by the separate Emergency Change Process Decision Yes – Go to 8.0 Emergency Change Process No – Go to 1.1 Create Change Record 1.2 Create Change Record Purpose To ensure all Changes are appropriately recorded in the ITSM Tool. Requirement Statement When recording a Change Record, it is the responsibility of Tier 1 to correctly complete all of the required information. Input Request for Change
ITSM-Process-Description---Change-Management---Final.docx