Your thoughts around "Routine" Emergency Changes?

Discuss and debate ITIL Change Management issues
Post Reply
User avatar
JuanChange
Newbie
Newbie
Posts: 1
Joined: Mon Aug 12, 2013 8:00 pm

Your thoughts around "Routine" Emergency Changes?

Post by JuanChange » Tue Aug 13, 2013 3:02 pm

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.



User avatar
UKVIKING
ITIL Expert
ITIL Expert
Posts: 3639
Joined: Fri Sep 15, 2006 8:00 pm
Location: London, UK

Post by UKVIKING » Wed Aug 14, 2013 1:41 am

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

User avatar
JScratch
Itiler
Itiler
Posts: 12
Joined: Mon Sep 05, 2016 8:00 pm
Location: Minnesota

Post by JScratch » Tue Sep 06, 2016 3:51 pm

agreed, the words routine and emergency should not be used together in relation to CM.
Josh - Senior Change Manager - Minnesota

User avatar
Hoverhead
Itiler
Itiler
Posts: 10
Joined: Mon Nov 28, 2016 7:00 pm

Post by Hoverhead » Thu Dec 01, 2016 10:44 am

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?

User avatar
LiamHeather
Newbie
Newbie
Posts: 2
Joined: Wed Apr 05, 2017 8:00 pm
Contact:

Post by LiamHeather » Thu Apr 06, 2017 6:49 am

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.

Post Reply