Standard Change Requests
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-23-2024 11:16 AM
One of the conditions that defines a standard change request is that it is performed "frequently". So is there any specific guideline for what it meant by "frequently"? Would a minimum of twice per year meet this definition?
- Labels:
-
Standard Change Requests
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-23-2024 02:02 PM - edited 01-23-2024 02:05 PM
Hi @Gary Langmeyer,
The best way to help explain 'Standard' changes and the frequency applied is to provide an example and compare against the other change types.
A Standard change is a pre-authorized change that is low risk, relatively common and follows a specified procedure or work instruction.
A standard change is one that is 'frequently' implemented, has repeatable implementation steps, and has a proven history of success such as applying a patch update or rebooting a server. (Think monthly or quarterly cadence for example)
In comparison, an Emergency change must be implemented as soon as possible, for example, to resolve a major incident or implement a security patch. This change is of such a high priority that it bypasses group and peer review and approval and goes straight to the Authorization state for approval by the CAB approval group.
A Normal change is any service change that is not a standard change or an emergency change.
Normal change requests follow a prescriptive process which requires two levels of approval before being implemented, reviewed, and closed. These changes require a full range of assessments and authorizations such as peer or technical approval, change management, and Change Advisory Board (CAB) authorization.
Emergency changes are those that need to be done quickly so can skip review before implementation but may require review afterward on what was changed to fix the situation.
Normal changes are those that are planned and reviewed before implementation.
I've provided a couple of links below from ServiceNow's doc site as well as a nice explanation from 'itsmtransition': "While ‘Normal’ and ‘Standard’ sound like two ways to describe the same thing, there’s a big difference. A Standard change must have a documented process that’s been reviewed and approved by Change Management. A Normal change is a non-emergency proposed change that needs to be reviewed by Change Management."
To help others (or for me to help you more directly), please mark this response correct by clicking on Accept as Solution and/or Helpful.
Thanks, Robbie
https://itsmtransition.com/2014/03/name-difference-standard-normal-changes-itsm/
