By ITIL® from Experience©
As discussed in the article describing the content of a standard change, a Standard Change1 was approved to address a specific issue, for a specific circumstance while respecting a particular set of precise conditions and applied using the documented work instructions.
The change is no longer a standard change when it cannot be implemented using this exact procedure. In other words, it stops being a standard change. It is now a normal change since the conditions upon which the approval was granted are no longer the case, thus it needs to reviewed and approved.
For example, if a change needs to be made:
- Outside of its approved release/change window (e.g. the change was pre-approved for Thursday evenings between 20:00 and 22:00, but needs to be made now to resolve an incident)
- To a Configuration Item it was not approved for, even though the procedure is identical (e.g. the approved procedure if for routers model 1500 and the change is needed on a router model 1510)
- The step-by-step instructions cannot be followed exactly as documented (e.g. a permission change needs to be made at the domain level, while the procedure was approved for a change at the group level)
Moreover, if the organization has implemented a Standard Change Maintenance Process the standard change is no longer authorized when it expires or fails to re-certify according to that process’ business rules or policies.
In addition, the Change Manager can revoke (i.e. demote) it's approved status if this change generates incidents.
- What is the content of a standard change
- How is a Standard Change Pre-Approved
- People are confused between a normal and a standard change. What is another name for it
- Are changes approved or authorized
- Why a process to maintain standard changes should be implemented
- Do we need to log an RFC for a Standard Change
Copyright 2013-2014 - ITIL® from Experience - D.Matte