Create an account Home  ·  Topics  ·  Downloads  ·  Your Account  ·  Submit News  ·  Top 10  
· Home
· Content
· Feedback
· News
· Search
· Statistics
· Surveys
· Top
· Topics
· Web Links
· Your_Account


The five ITIL books can be obtained directly from the publisher's website:

Or as downloadable PDFs: HERE

Current Membership

Latest: DarcyHersh
New Today: 3
New Yesterday: 39
Overall: 236473

People Online:
Visitors: 162
Members: 1
Total: 163 .



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.

Related Resources

Service related resources
Service Level Agreement

How to set up
IT Change Management
Process Info-Graphic

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.


Select Interface Language:

Please contact us via the feedback page to discuss advertising rates.

The Itil Community Forum: Forums

ITIL :: View topic - Emergency / Urgent Changes and Vital Business Need
 Forum FAQForum FAQ   SearchSearch   UsergroupsUsergroups   ProfileProfile   Log in to check your private messagesLog in to check your private messages   Log inLog in 

Emergency / Urgent Changes and Vital Business Need

Post new topic   Reply to topic    ITIL Forum Index -> Change Management
View previous topic :: View next topic  
Author Message
Senior Itiler

Joined: May 25, 2007
Posts: 105
Location: USA

PostPosted: Tue Jul 17, 2007 2:09 am    Post subject: Emergency / Urgent Changes and Vital Business Need Reply with quote

We have two kinds of Emergency Changes: One stems from an Incident or Problem record and one stems from a vital business need. We use vital business need as a bucket for security patches, application patches, customer needs (squeaky-wheel-types, sometimes), and such, but use it very sparingly.

We do not assess urgency separately but we do assess risk (impact).

Last week, someone refused to accept the vital business need for an emergency change to prevent an incident. (We are a data center and a customer missed something, which if not migrated with other changes would have disrupted services.) The Change priority became Expedited and was implemented in time to prevent the incident. So all is well there.

This brings me (finally) to the questions. Are we defining Emergency appropriately? How do Change Teams differentiate between urgently needed changes to restore services vs. those for business needs?

Thanks! R.
Back to top
View user's profile

Joined: Sep 06, 2006
Posts: 5
Location: London

PostPosted: Tue Jul 17, 2007 9:12 am    Post subject: Reply with quote

By defining emergency using category and priority is one thing, but moving on from there may be more difficult by making a decision to and having the full cooperation of all parties involved, hence the formation of a CAB or an EM to dissolve the issue and decide on he most appropriate way to move forward.

Restoring services is part of aligning with the business goals, but vital business needs might also have an impact on the services provided. Allocating the right amount of available resources to the relevant change is also key. Determining the source of the major impact may also shed some light on determining where a higher priority lies.

I might not be the one to determine if we are defining Emergency appropriately, but we are given a fair amount of tools and guidance to lead to a resolution. This being said, the solution may not come about easily, but it is a solution none the less.

I hope this helps!
Back to top
View user's profile MSN Messenger
Senior Itiler

Joined: Sep 16, 2006
Posts: 3607
Location: London, UK

PostPosted: Thu Jul 19, 2007 6:24 pm    Post subject: Reply with quote

The hard part about using the fuzzy phrase business need is how the term gets mis-used

The examples given cover too broad of an area

We use the following for emergency

Restore of a live service
Prevention of an impact(outage) to a live service
Security patches to prevent exploitation to the existing service
Business impact due a service impact costing $() a financial or reputation in the industry

Also any development or project automatically cant be an Emergency because the projects are not live

Application patching must meet the criteria above as well. Other wise it falls under the standard change process

All Emergency Changes get reviewed by Change Management and if a CAB/EC is required (dependign on the impact/approvers); the CAB/EC is held and includes snr mgmt.

As to the phrase 'business need'; I phrase that to mean 'business want' rather than 'need'
John Hardesty
ITSM Manager's Certificate (Red Badge)

Change Management is POWER & CONTROL. /....evil laughter
Back to top
View user's profile

Joined: Jul 08, 2015
Posts: 11

PostPosted: Thu Jul 09, 2015 7:11 am    Post subject: Reply with quote

Emergency Changes are opened/created when a Major Incident, or a Severity 1 or 2 can only be resolved via a Change... thus the Emergency Change - used to restore service.

An Expedited or Urgent Change is used when there is an urgent business need. Perhaps there is a need to make a Change due to a regulatory component... then the issue becomes, what risk will the business incur if the Change is NOT done.
Back to top
View user's profile
Display posts from previous:   
Post new topic   Reply to topic    ITIL Forum Index -> Change Management All times are GMT + 10 Hours
Page 1 of 1

Jump to:  
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

Powered by phpBB 2.0.8 © 2001 phpBB Group
phpBB port v2.1 based on Tom Nitzschner's phpbb2.0.6 upgraded to phpBB 2.0.4 standalone was developed and tested by:
ArtificialIntel, ChatServ, mikem,
sixonetonoffun and Paul Laudanski (aka Zhen-Xjell).

Version 2.1 by Nuke Cops 2003

Forums ©


Logos/trademarks property of respective owner. Comments property of poster. Rest 2004 Itil Community for Service Management & Foundation Certification. SV
Site source copyright (c)2003, and is Free Software under the GNU / GPL licence. All Rights Are Reserved.