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: ydamoseh
New Today: 2
New Yesterday: 37
Overall: 231687

People Online:
Visitors: 133
Members: 2
Total: 135 .



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 - Urgency in Incident (pls advice)
 Forum FAQForum FAQ   SearchSearch   UsergroupsUsergroups   ProfileProfile   Log in to check your private messagesLog in to check your private messages   Log inLog in 

Urgency in Incident (pls advice)

Post new topic   Reply to topic    ITIL Forum Index -> The ITIL Service Desk
View previous topic :: View next topic  
Author Message

Joined: Aug 10, 2005
Posts: 1

PostPosted: Thu Jan 12, 2012 6:01 pm    Post subject: Urgency in Incident (pls advice) Reply with quote

I understand that in ITIL, Incident Prioritization is based on Urgency and Biz Impact. But what if my Priority is derived from System Impact and No. of user/ branches impact. Is it fine to have that?

Really need you all advice... Very Happy
Back to top
View user's profile
Senior Itiler

Joined: Mar 04, 2008
Posts: 1894
Location: Helensburgh

PostPosted: Thu Jan 12, 2012 9:10 pm    Post subject: Reply with quote

Okay, let's say you have two simultaneous incidents and only one available technician. This is what priority is for.

case 1: a single PC is down. But it is the only one capable for the task of completing a tender bid (dead-line 6 hours away) worth a potential 20 m.

urgency 5 hours; business impact huge
system impact negigible; no. of users impacted 1

case 2: a server is dow, preventing fifty staff from completing their forward plan for review next week.

system impact significant; no. of users impacted 50
urgency 4 days (say); business impact low to negligible

Success criteria (the reasons the business continues to use your services) are derived from how well the business continues to function. System impact and no. of users affected are blunt instruments that will not always correspond with business imperatives. They are a shortcut that can go spectacularly wrong.
"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
Back to top
View user's profile Send e-mail
Display posts from previous:   
Post new topic   Reply to topic    ITIL Forum Index -> The ITIL Service Desk 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.