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

Current Membership

Latest: JPhilip
New Today: 34
New Yesterday: 49
Overall: 146063

People Online:
Visitors: 63
Members: 1
Total: 64 .

Languages
Select Interface Language:


Major ITIL Portals
For general information and resources, ITIL and ITSM World is the most well known for both ITIL and ITIL Books. A shorter snapshot approach can be found at ITIL Zone

Related Resources
Service related resources
Service Level Agreement
Outsourcing

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.


The Itil Community Forum: Forums

ITIL :: View topic - Assessing Business Impact (High-Medium-Low)
 Forum FAQForum FAQ   SearchSearch   UsergroupsUsergroups   ProfileProfile   Log in to check your private messagesLog in to check your private messages   Log inLog in 

Assessing Business Impact (High-Medium-Low)

 
Post new topic   Reply to topic    ITIL Forum Index -> Problem Management
View previous topic :: View next topic  
Author Message
DustinW07
Newbie
Newbie


Joined: Aug 02, 2012
Posts: 12

PostPosted: Fri Aug 03, 2012 12:21 am    Post subject: Assessing Business Impact (High-Medium-Low) Reply with quote

Hi guys...new to the Forum, 1st post.

As part of our Visual Management board for leadership, My department is looking at another way we can assess Business Impact (High-Medium-Low) on some of our core business processess after incidents take place, so I wanted to see how people have done this in the past.

It seems like there's so many variables that come into play when determining the level of the impact such as: What time of the day did the incident occur?, What process(es) did it effect, How long did it last?, Was sales volume in-line with the day's expected volume despite the incident occuring?, etc.

In the end, it feels like all we're left with is a gut-check of what we "feel" the impact was. Has anyone utilized a matrix or other tool that they use in their organization to help better assess the impact (High-Medium-Low) following an incident? Just wanted to gather your thoughts....Thanks in advance!
Back to top
View user's profile
Boydness
Itiler


Joined: Aug 03, 2012
Posts: 24

PostPosted: Fri Aug 03, 2012 11:48 pm    Post subject: Reply with quote

For Problems, it is derived from the Incidents, we have both a Technical and a User Impact rating for each Incident.

Do you separate your impacts into Technical and User?
You could go further, Technical, User, Financial and then determine your chart for a consolidating Impact rating, because it could vary each and every time.
Technical - High
User - Low
Financial - Low

Of course, each category would have defined criteria for assessing Low, Medium, High. Then you refine it until the outcome meets the gut/logical outcome that makes sense.

Some of the generic criteria we use involve:

Timing (Core Hours, non-core hours, peak)
SLAs (exceed/break)
Number of Registered Users / Number users typically active at that time
Volume of Transactions typical
Duration of Incident
Duration of resulting backlog/workflow


Is that any help to you?

Boydness
Back to top
View user's profile
Diarmid
Senior Itiler


Joined: Mar 04, 2008
Posts: 1884
Location: Newcastle-under-Lyme

PostPosted: Sat Aug 11, 2012 8:22 pm    Post subject: Reply with quote

This is the classic dilemma. you need to decide right now, but it takes a while to establish the facts.

Don't forget that the main initial reason for establishing impact is to prioritise your response and therefore only comes into play when you have a clash of demand for resources. That reduces the pain a bit.

If you are going by some intuitive judgement based on experience and background knowledge, then you need to involve the customer at a knowledgeable (and preferably, authoritative, level, since business impact is primary.

In an ideal world the customer will agree the priority with you and in a less than ideal world you should still try to get such agreement in particularly problematic cases in the high (business) risk areas of services.
_________________
"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 -> Problem 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 http://www.nukecops.com

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.