You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 14 Next »

To create a change, please complete the following steps:

  1. Navigate to the Change Control → Create New;
  2. Fill in the form and click Save.

The form description

FieldDescription
NumberIncident number. This field should have format CHGXXXXXXX. It is filled automatically.
Change type

The change type. Available choice options:

  • Standard;
  • Normal;
  • Emergency.
Requested byThe originator of the change request (also known as the caller)
ServiceThe service that will be affected by this change request.
Related CIsService-related CI that will be affected by this change request.
Assigned UserSpecify a responsible person to work on the request.
Assigned GroupSpecify a responsible for working on the request.
SubjectA brief description of the request.
ReasonA justification of the request.
DescriptionA detailed description of the request.
State

This field displays the work state and progress. Available choice options:

  • Registered;
  • Authorization;
  • Scheduled;
  • In Progress;
  • Completed;
  • Post-Implementation Review;
  • Closed.
Change Authority
Risk

A possible event that could cause loss or harm. Risk is a function of impact and probability. Possible choice options:

  • Low;
  • Medium;
  • High;
  • Very High.
Probability

The level of possibility of the event occurrence. Possible choice options:

  • High;
  • Low.
Impact

The measure of the effect that a change request may cause on the business processes. Available choice options:

  1. Low;
  2. Medium;
  3. High;
  4. Very High.
Urgency

The measure of time until a change request has an impact on the business. Available choice options:

  1. Low;
  2. Medium;
  3. High.
Priority

Identifies the importance of a request. The priority can be figured out based on its impact and urgency. Available options:

  1. Low;
  2. Moderate;
  3. High;
  4. Critical.
The Schedule Tab
Possible Conflicting ChangesChange requests that have time overlap with this request. It possibly can impact request implementation.
Planned Start DatePick a date and time you need the request to be started processing. The caller must fill this field.
Planned End DatePick a date and time you need the request to be finished processing. The caller must fill this field.
Planned DowntimeIf service downtime is expected, then put down its duration here.
Downtime NoteYou can put any notes about planned service downtime here.
Actual StartPick a date and time when the request was started processing. The responsible person must fill this field.
Actual EndPick a date and time when the request was finished processing. The responsible person must fill this field.
Actual DowntimeIf service downtime took place then put down its duration here.
The Planning tab
Pre-test PlanThis plan specifies the steps that need to be done and the criteria to be met before implementing the change.
Change PlanDescribe here the process of the change implementing.
Test PlanThe process of how the change must be tested after implementing,
Backout PlanThe plan that specifies the processes to restore the system to it's earlier state, in case of a failed implementation.
  • No labels