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.
The Itil Community Forum: Forums
ITIL :: View topic - Your thoughts around "Routine" Emergency Changes?
Posted: Wed Aug 14, 2013 5:02 am Post subject: Your thoughts around "Routine" Emergency Changes?
We have a support group within our organization that periodically performs emergency changes to replace faulty disk drives in our storage arrays. They do these 3-4 times a week and is adversely impacting our metrics of keeping the emergency volume to a minimum.
We, the Change Management team consider these as valid emergency changes but the support group consider these as routine and reactionary changes that when performed, pose no risk. The risk comes if they are not performed in a timely manner, data might get lost and we lose the redundancy. The support team wants us to re-categorize their routine emergency change as a normal change so our metrics are not impacted by their Emergency changes.
What do you guys think would be a viable solution? I have several ideas roaming around but based on our definition of an Emergency changes, which is basically the standard ITIL definition, their reactionary changes would still be Emergencies. They just don't want to get penalized for having such high number of E-CRQs.
By the way, re-aligning our emergency metric is not an option.
Thank you.
Joined: Sep 16, 2006 Posts: 3590 Location: London, UK
Posted: Wed Aug 14, 2013 3:41 pm Post subject:
one
there should be no such thing as Routine emergency changes
second, the fact that the fault leads to an emergency h/w fix is a fault restoration and if the work has to be done quickly and your CM policy has such h/w work as changes, then the work is an emergency
Third, the ticket classification is correct
foruth the issue is not the classification forCM but the fact that the storage environment is poor.
Cease worrying about the statitistics
Worry more about the shitty storage environment.... and escalate this to your management _________________ John Hardesty
ITSM Manager's Certificate (Red Badge)
Change Management is POWER & CONTROL. /....evil laughter
We only allow Emergency changes to be performed in the event of a P1 or P2 incident and this has been incorporated into Servicenow. If they do not have one, then the request is logged under a Normal unplanned changed and assessed by change management.
I guess also that the resolution could be resolved under incident, if an incident has been raised?
I would suggest that there is no such thing as a Routine Emergency Change. It may be a regular high priority change that needs to be implemented, however, I would categorise Emergency Changes as those that are unexpected, usually of high priority.
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