Versions Compared
Key
- This line was added.
- This line was removed.
- Formatting was changed.
SummitAI Service Management Help
Scroll ignore | ||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||
Table of Contents type flat
What are Change Records?
You can create new Change Records (CRs) to add, modify, or remove Configuration Items (CIs) in an infrastructure and items associated within the infrastructure. You need to create CRs to add, modify, or remove policies or procedures or to modify the Knowledge Records (KRs). An Incident, Problem, Event, Service Request (SR) can also trigger a CR.
To create new CRs:
Select Change > User > New Change Record. The NEW CHANGE RECORD page is displayed.
Figure: NEW CHANGE RECORD page
2. On the NEW CHANGE RECORD page, select the Tenant and fill in the other required details as described in the following table:
Field | Description | |||||
---|---|---|---|---|---|---|
Tenant | Select the Tenant from the list. | |||||
Requestor | The user who requested the CR. You can also change the Requester by selecting another user using the Search icon. Note: When a CR is created from a Service Request (SR), Requester is the user who logged the SR. All the notifications sent to the CR Requestor are also sent to the SR Requester. | |||||
Owner Workgroup | Select a Workgroup from the list to indicate as an Owner Workgroup for this CR. | |||||
Workgroup Owner Details | Displays the details of the Workgroup Owner after you select the Workgroup in the Owner Workgroup list. | |||||
Log Time | Displays the time and date when the Change Record is created. | |||||
Status | Select the status from the list. The status indicates the stage at which a Change Record is in its life cycle, for example, Requested, Approved, Testing, Implemented, and so on. For more information about the various CR status values, see Change Record Status. | |||||
Category | Select the Category from the Category list: Small, Medium, andLarge | |||||
Change Category | Click the search icon and select the category of the Change Record.
| |||||
Change Type | Select the Change Type from the list: Standard, Normal, Emergency, andExpedited Notes: If the Authorizer selects Expedited from the Change Type drop-down list:
If Do Not Allow to Update CR Change Type check box is selected on the Tenant page of the Change Management module, Analyst cannot change the Change Type from Standard to other type and vice versa. | |||||
Trigger for Change | Type in a brief description about the scope and the reasons that triggered the CR. | |||||
Configuration Items | Allows you to select the CIs related to the CR to indicate the CIs that have an impact due to this CR. Click icon to open the SELECT CONFIGURATION ITEM pop-up page, where you can search for the CIs and link them with the CR. If you link Services, on saving the CR, the CIs linked to the Service are also linked to the CI under the RELATIONSHIP tab of the CR. You can delink the CIs if you want.
| |||||
Attachment | Click the Upload icon to upload the required file. |
3. Type in the other required fields under the GENERAL, RISK, LOGS, TEST, CHECKLIST, RELATIONSHIP, REQUIREMENTS, RELEASE, IMPLEMENTATION, and ADDITIONAL INFORMATION tabs. For more information about the fields under these tabs on the NEW CHANGE RECORD page, see Field Description.
4. Click SUBMIT. A new CR is created.
Saving as Draft
You can also save a CR as draft. You need to follow the same steps as creating a CR. However, instead of clicking SUBMIT, you need to click SAVE DRAFT. You can view the draft CRs on the CHANGE RECORD LIST page (Change > View Change Record List). Click the Filter icon on the ACTIONS panel and select Status as Draft on the FILTERS pop-up page. If the CR is in Draft status, you cannot create a new Incident, Problem Record (PR), and a new Work Order and link them with the CR (see: RELATIONSHIP Tab). The CR is Draft status can be modified further before saving and submitting as CR.
Field Description
This section describes the fields on the NEW CHANGE RECORD page.
Expand | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
You can provide the general information about the CR, such as Risk, Priority, deadline, assigned Workgroups, time lines, and so on under the GENERAL tab.
The following table describes the fields under the GENERAL tab:
|
Expand | ||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||||||||||
The Risks associated with the CR need to be analyzed. Under the RISK tab, you can capture the Risk details before and after the CR is implemented. You can also capture the downtime, Service outage, and the System Impact to implement the CR.
The following table describes the fields under the RISK tab:
|
Expand | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||
The observations and notes made by the Change Manager, Configuration Team, and Change Advisory Board members should be documented. Under the LOGS tab, you can capture all these detail, such as information log, configuration team log, Change Manager log, and Change Advisory Board Member log.
The following table describes the fields under the LOGS tab:
|
Expand | |||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| |||||||||||||||||||||||||||||||
The CR needs to be tested before it is implemented. You can capture the testing details of the Change Record (CR) and log the defects under the TEST tab. The test details, such as Test Stage, Test Planned Date, Test Plan, Test Results, Actual Test Date, Workgroup, Conducted by/owner, Test Status, Attachment, and so on can be updated.
The following table describes the fields under the TEST tab:
|
Expand | ||
---|---|---|
| ||
There may be a list of actions you need to perform before updating a Change Record. Under the CHECKLIST tab, you can verify these actions (if configured by the Administrator) and complete them before updating the Change Record. Based on what action is taken on the Task, update the Task Status and provide your remarks in the Remarks text box.
|
Expand | ||
---|---|---|
| ||
You can link related Incidents, Problem Records, Service Requests, Change Requests, Work Order, Assets, Service Catalogs, and User Assets to the CR using the Link list. You can also create new Work Orders, Tasks, Knowledge Records, Release Records, and link them to the CR using the Create list. You can De-link a linked record using De-link button. Select the record you want to De-link and click the De-link button. Select the Implement CR using last implemented task check box to create CR using the last implemented task (see: Creating Tasks for Change Records (CRs)). To link any module to a Change Record
|
Expand | ||||||||||||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||||||||||||||||||||||||||||||||||||||
Under the REQUIREMENTS tab, you can specify resource requirements, technical requirements, and financial requirements for the CR. The following table describes the fields under the REQUIREMENTS tab:
|
Expand | ||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||||||||||
After a CR is tested and implemented, the release details should be updated. Under the RELEASE tab, you can add the release details of a CR, such as Release Plan, Release Attachment, Release Workgroup, Release Executive, Post Release Notes, and so on. Figure: RELEASE tab The following table describes the fields under the RELEASE tab:
|
Expand | ||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||||||||||||
You must fill the fields on the Implementation tab while implementing the Change Record.
The following table explains the fields on the Implementation Tab of the Change Record:
|
Expand | ||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||
You can capture any additional information or detail about the CR under the ADDITIONAL INFORMATION tab of the CR. The Custom Fields configured by the Administrator are also displayed under this tab. Figure: ADDITIONAL INFORMATION tab The following table describes the fields under the ADDITIONAL INFORMATION tab:
|
Expand | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
This section explains all the icons displayed on the ACTIONS panel of the CHANGE RECORD ID page. SHOW LIST Click SHOW LIST to display the CHANGE RECORD LIST page showing all the available CRs. SHOW LIST FOR APPROVAL Click SHOW LIST FOR APPROVAL to display the APPROVE CHANGE RECORDS page showing only the CRs waiting for approval. ALERT CONFIGURATION You can configure the alerts to be sent out to the stakeholders for the CR. Click the ALERT icon to display the ALERT CONFIGURATION pop-up page.
The following table describes the fields on the ALERT CONFIGURATION page:
CREATE RECURRING CR Click CREATE RECURRING CR to create a recurring CR. The same CR is created as per the frequency details configured on the CUSTOM SCHEDULER pop-up page.
The following table describes the fields on the CUSTOM SCHEDULER pop-up page:
APPROVALA CR needs to be authorized by the Change Record Authorizer and approved by the Change Advisory Board (CAB) members before it is analyzed and then implemented. A CAB member who is configured as an Approver by the Administrator has the privilege to Approve, Reject or Refer Back a CR. By default, a CAB member who is not having approval privilege can object to a CR. If a CR is objected by any of the CAB members, the CR cannot be processed further. The CAB member who objected to the CR must clear the CR before implementing it. Click the APPROVAL icon on the ACTIONS panel. The APPROVAL pop-up page is displayed. The fields on this page are not editable if you are not the CR Authorizer or CAB member for the selected CR. There are two sections in this page: CR SUMMARYYou can view the CR Summary in this section. The fields on this section are not editable.
APPROVE CR - AUTHORIZATION
The following table describes the fields on the APPROVE CR (AUTHORIZATION) section:
APPROVE CR - CAB APPROVAL
The following table describes the fields on the APPROVE CR (CAB APPROVAL) section:
Anchor |
|
Field | Description |
---|---|
Planned PIR Date | Select the planned PIR date. |
Actual PIR Date | Select the actual PIR date. |
Post Implementation Review | Type in any reviews or comments about the PI review for the CR. |
Is CMDB Updated? | This field is enabled for you to modify only after the CR is implemented with the status field displaying Implemented on the CHANGE RECORD page.
|
Reviewer | Type in the name of the Reviewer. |
Review Date | Type in the review date. |
Revert to Previous Version ? | This field is enabled for you to modify only after the CR is implemented with the status field displaying Implemented on the CHANGE RECORD page.
|
Note | ||
---|---|---|
| ||
While closing the CR, the fields Actual PIR Date and Post Implementation Review are mandatory for the following conditions:
|
CHANGE HISTORY
Click CHANGE HISTORY to view the various changes that have occurred on the CR. This information is useful to track the various changes made on the CR.
Figure: CHANGE HISTORY pop-up page
The following table describes the fields on the CHANGE HISTORY page:
Field | Description |
---|---|
Column Name | Displays the name of the field on which the change is made. |
Change Date | Displays the date when the change is made. |
Changed By | Displays the name of the user who made the change. |
Old Value | Displays the old value of the field. |
New Value | Displays the new value of the field. |
IMPORT TEMPLATE
Click IMPORT TEMPLATE to import a configured template that can be used for creating Change Record(s). Select the Template name from the Select Change Record Template drop-down list you want to import.
Figure: IMPORT TEMPLATE pop-up page
SAVE AS TEMPLATE
Click the SAVE AS TEMPLATE icon to save a CR details as Template. Type in a name for the Template in the Change Template Name text box and click SAVE TEMPLATE to save the CR as a Template.
Figure: CREATE TEMPLATE pop-up page
EDIT TEMPLATE
Click EDIT TEMPLATE to edit a Template. On the EDIT TEMPLATE pop-up page, select the name of the Template you want to edit.
Figure: EDIT TEMPLATE pop-up page
On the CHANGE RECORD TEMPLATE - NAME page is displayed with the details of the selected Template. Make the required changes and SUBMIT. For more information about fields and icons on the CHANGE RECORD TEMPLATE - NAME page, see Field Description.
Figure: CHANGE RECORD - TEMPLATE-TEMPLATE NAME page
Scroll ignore | ||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||
|