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: MReyes
New Today: 34
New Yesterday: 69
Overall: 148114

People Online:
Visitors: 51
Members: 0
Total: 51

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 - Major Incidents?
 Forum FAQForum FAQ   SearchSearch   UsergroupsUsergroups   ProfileProfile   Log in to check your private messagesLog in to check your private messages   Log inLog in 

Major Incidents?

 
Post new topic   Reply to topic    ITIL Forum Index -> ITIL Discussion
View previous topic :: View next topic  
Author Message
martin_d
Newbie
Newbie


Joined: Jul 08, 2005
Posts: 8

PostPosted: Fri May 12, 2006 12:01 am    Post subject: Major Incidents? Reply with quote

When there is a major service affecting incident, is it ITIL best practice to log an incident for each user that reports it, or log one incident for all?

Thanks in advance
Back to top
View user's profile
rjp
Senior Itiler


Joined: Mar 12, 2005
Posts: 255
Location: Melbourne, Australia

PostPosted: Fri May 12, 2006 12:28 am    Post subject: Reply with quote

This one does cause some 'debates' from time to time.

There are a few things worht considereing and none preclude the others.

Have a clear definition in place for a major incident and ensure there is a protocol dedicated to the handling of such.

Having said that - it's easy to say a major incident is an availabilty or capacity disruption that has gobal (or wide scope) - but sometimes it may only be the fact the you start to get a large number of duplicate incident reports that a major incident is detected. (Though with infrastructure monitoring technoligies maturing at the current rate this is becoming rarer.)

But on the other hand every report should be logged regardless. It's highly likely that when a major incident is occurring some poor sod will ring up and say 'X isn't working' and be told, 'yes, Y is happening and we are working on it' - but it turns out that the users report had nothing to do with an outage, and now he/she is sitting out there wondering how long it will be, and eventaully call back in a more frustrated tone.

So, yes log every incident.

But...won't the desk be swamped, and all those call back be a waste of time? Well, yes if you have crappy major incident protocols. One of the most important tasks for the service desk in a major incident is to get the message out to the community ASAP - with an intelligible description of the effect user can expect it to have on them, and regular progress reports. You'll get some who still call, but in this case they are only calling for an update, so you can log it as such and set it straight to resolved - because you gave them the update. Very useful data. Most won't, if they are confident they have been given good information and trust they will be informed as soon as the issue is resolved they will let you get on with it.

So best practice is logging every incident, but not just that.
Back to top
View user's profile Send e-mail AIM Address Yahoo Messenger
martin_d
Newbie
Newbie


Joined: Jul 08, 2005
Posts: 8

PostPosted: Fri May 12, 2006 1:22 am    Post subject: Reply with quote

Thanks!
Back to top
View user's profile
Jamiey
Newbie
Newbie


Joined: Mar 14, 2006
Posts: 2

PostPosted: Fri Jun 30, 2006 9:07 pm    Post subject: Reply with quote

What if you have multiple services affected by the incident?

for example, failure of a data centre which takes out several customer systems. I'm correct that to assess impact you would need to have a call for each service.

A secondary question about Major Incidents is if you have support teams who would investigate and resolve incidents outw ith the service desk where would these incidents sit?

With the support teams doing the work or with one "lead" call with the support teams and further incidents either for services or users sitting with the Service Desk.
Back to top
View user's profile
OOSLVR
Newbie
Newbie


Joined: Jul 18, 2006
Posts: 2

PostPosted: Wed Jul 19, 2006 9:56 am    Post subject: Re: Major Incidents? Reply with quote

martin_d wrote:
When there is a major service affecting incident, is it ITIL best practice to log an incident for each user that reports it, or log one incident for all?


Within my organization, we are using the Remedy service desk application, which allows us to create ONE Incident record for the outage.
This becomes the "master" record.

Encounter records are created, and attached to the "master"
Incident record, as other users call in to report the problem.

Having one master incident record will help cut down on the
confusion, prevent multiple paging from going out, keep
everyone on the same page, ensure details and updates are
entered into a single incident worklog, etc.
Back to top
View user's profile
Display posts from previous:   
Post new topic   Reply to topic    ITIL Forum Index -> ITIL Discussion 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.