Don't have an account yet? You can create one. As a registered user you have some advantages like theme manager, comments configuration and post comments with your name.
NOTE: ® ITIL is a registered trademark of OGC. This portal is totally independent and is in no way related to them. See our Feedback Page for more information.
Search
Languages
Select Interface Language:
Advertising
Please contact us via the feedback page to discuss advertising rates.
Posted: Fri Jan 11, 2013 3:13 am Post subject: Question on Standard Change
If a Standard Change has caused an outage (within or outside the change window) then can it still be considered a Standard Change? If yes, then how many times is a Standard Change allowed to cause outage?
Joined: Sep 16, 2006 Posts: 3591 Location: London, UK
Posted: Fri Jan 11, 2013 6:15 am Post subject:
Syona
What does your policy state for a standard change ?
That is all that is relevant.
If the outage that occurs is part of the standard change, then if the critieria and impact (outage) accepted as part , then it is a standard change
Consider desk / laptop windows updates, they usually require a reboot and most companies make it a standard change once the board / policy deem it so. _________________ John Hardesty
ITSM Manager's Certificate (Red Badge)
Change Management is POWER & CONTROL. /....evil laughter
Joined: Mar 04, 2008 Posts: 1894 Location: Helensburgh
Posted: Fri Jan 11, 2013 6:55 am Post subject:
To cover the other case:
if this was an unscheduled outage (i.e. something went wrong), then, just like anything else going wrong with a "standard" change, the the procedure for that change should be reviewed and it should no longer be a "standard" change until the reason is determined and any remedial action taken to prevent recurrence. _________________ "Method goes far to prevent trouble in business: for it makes the task easy, hinders confusion, saves abundance of time, and instructs those that have business depending, both what to do and what to hope."
William Penn 1644-1718
There is no law that says a standard change cannot include an outage.
That said and as Diarmid says, if the outage was due to a failed change, i.e. something went wrong, it should come off the list of standard changes until it is reviewed and the underlying cause is understood and remediated.
gotcha ! thanks for the response !! one of our Standard Change has caused multiple outages in the past including sev1 incident. Looks like we would need to remove it from Standard Change category as it is not safe to the environment.
Another quick question - What should be the criteria for considering any CI as a critical CI? We have already identified some points tho.
The criticality of a CI generally comes down to business impact. The question I ask is "what is the impact to the business if this CI fails?"
If the answer is that it will cause critical impact to business functions (e.g. orders can't be filled or shipped, or 50 people can't work without it, etc.), then the CI is critical.
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum