Reason For Change Link to any related prior or open RFC Perceived Impact (if change is made or not made) Output Change Record Metric Number of Change Records recorded per measurement period (e.g., weekly) compared to number of RFCs on file. Number of RFCs linked to prior RFCs 1.3 Examine The Change Record For Completeness Purpose To ensure that the Change Record is complete and practical. Requirement When examining the Change Record, it is the responsibility of the Change Statement Coordinator, Change Manager and Tier 1 to examine for completeness and practicality. Input Change Record Procedure or Examine the Change Record for completeness and practicality Work Assure that it is in compliance with Standards and Requirements Instruction Remediate information in Change Record if required Steps Update the Change Record Output Updated Change Record Metric D.1.4 Is the Change Request Rejected? Purpose Decide if the Change is practical determine if it should move forward. Decision Logic Yes Go to 1.4 Inform Requester that Submission was Rejected – No Go to 1.3 Inform Requester that Submission was Accepted – 1.5 Inform Requestor That Submission was Rejected Purpose To inform the Requestor that the RFC has been rejected. Requirement When advising the Requestor of the outcome of their RFC, it is the responsibility of Statement the Change Coordinator, Change Manager and Tier 1 to provide them with the required information. Input Change Record Procedure or Contact the Requestor and inform them that their RFC has been rejected Work Note that an RFC will not be reopened. A new RFC must be submitted Instruction Update the Change Record Steps Notification to Requestor Output Updated Change Record Metric Number of rejected RFCs 1.6 Inform Requestor That Submission was Accepted Purpose To inform the Requestor that the RFC has been accepted. Requirement When advising the Requestor of the outcome of their RFC, it is the responsibility of
Reason For Change Link to any related prior or open RFC Perceived Impact (if change is made or not made) Output Change Record Metric Number of Change Records recorded per measurement period (e.g., weekly) compared to number of RFCs on file. Number of RFCs linked to prior RFCs 1.3 Examine The Change Record For Completeness Purpose To ensure that the Change Record is complete and practical. Requirement Statement When examining the Change Record, it is the responsibility of the Change Coordinator, Change Manager and Tier 1 to examine for completeness and practicality. Input Change Record Procedure or Work Instruction Steps Examine the Change Record for completeness and practicality Assure that it is in compliance with Standards and Requirements Remediate information in Change Record if required Update the Change Record Output Updated Change Record Metric D.1.4 Is the Change Request Rejected? Purpose Decide if the Change is practical determine if it should move forward. Decision Logic Yes – Go to 1.4 Inform Requester that Submission was Rejected No – Go to 1.3 Inform Requester that Submission was Accepted 1.5 Inform Requestor That Submission was Rejected Purpose To inform the Requestor that the RFC has been rejected. Requirement Statement When advising the Requestor of the outcome of their RFC, it is the responsibility of the Change Coordinator, Change Manager and Tier 1 to provide them with the required information. Input Change Record Procedure or Work Instruction Steps Contact the Requestor and inform them that their RFC has been rejected Note that an RFC will not be reopened. A new RFC must be submitted Update the Change Record Output Notification to Requestor Updated Change Record Metric Number of rejected RFCs 1.6 Inform Requestor That Submission was Accepted Purpose To inform the Requestor that the RFC has been accepted. Requirement When advising the Requestor of the outcome of their RFC, it is the responsibility of
ITSMProcessDescription-ChangeManagement-2.0.docx