Filing a Normal or Emergency Change Request (Ivanti)
Filing a Change Request in WiscIT (Ivanti)
In the ‘Change’ workspace in WiscIT, select the ‘New Change’ menu and pick either New Change – Normal or New Change - Emergency type.
Change Types
New CR- Normal
-
Normal Change Requests are appropriate for all change requests that have more than 48 hours of lead time until their scheduled implementation.
-
Normal Change Requests are approved by Change Management or the Change Advisory Board, depending on their impact and risk assessment.
New CR- Emergency
-
Must be used if there is less than 48 hours or 2 business days until implementation of the change.
-
Require pre-approval from a Manager or Associate Director (or higher). The pre-approving Manager is notified of the Emergency CR upon submission.
-
Require 'Justification' to document the need for urgency and why this change should be implemented right away.
-
Do not otherwise require approval and skip the "Pending Approval" stage so that they may be implemented ASAP.
Change Request Form and Fields
Summary
Short description of the planned change.
Description
Detailed description of the planned change including technical details.
Should include an overview of the change, the process for implementing the change, testing activities performed, and backout plans if the change is not successful.
Start and End Date and Time
Specify the start and end dates and times for the change window.
CMDB Update (Configuration Management Database)
Checking this box indicates that the change will modify the linked Configuration Items (CIs) such that the Configuration Management Database (CMDB) will need to be updated by Configuration Manager.
If selected, a Task is created and assigned to Configuration Management.
Outage Required
Outage Types
-
Internal
-
Internal Outages are not posted on any Outage page and are only communicated via the Internal Outage mailing list.
-
-
External
-
External Outages are posted on one or more of the Outage Pages and are publicly viewable.
-
External Outages are also communicated via the Outage Notification List
-
Select:
-
No
-
No Outage needed
-
-
Yes- Both
-
Both an Internal and External Outage are required
-
-
Yes- Internal
-
Only an Internal Outage is required
-
-
Yes- External
-
Only an External Outage is required
-
Outage Details
Provide details about what should be included in the Outage and communicated to customers and end users. Outages should not include technical details.
Emergency CR only fields
Emergency Change Requests have two additional fields that are not included on Normal Change Requests.
Justification
Provide a brief explanation of why this Change needs to be implemented urgently. If the Change does not have sufficient justification for urgency, it should be filed as a Normal CR instead.
Approving Manager
Because Emergency CRs bypass the normal approval process, it is required that you select an Approving Manager from the drop down list. It is recommended that you inform the Approving Manager of the planned Emergency Change prior to submitting the Emergency CR. Approving Managers will receive an email notification of the Emergency Change Request upon submission.
Linked Configuration Items
Change Requests must link at least one Configuration Item via the ‘CI’ tab at the bottom of the CR form.
The linked CI may be the Service associated with the CR, specific CIs such as Network Devices, or any other CI that will be affected by the change.
