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: GeriNunley
New Today: 44
New Yesterday: 73
Overall: 150093

People Online:
Visitors: 58
Members: 1
Total: 59 .

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 - With mass outage - when to stop logging individual incidents
 Forum FAQForum FAQ   SearchSearch   UsergroupsUsergroups   ProfileProfile   Log in to check your private messagesLog in to check your private messages   Log inLog in 

With mass outage - when to stop logging individual incidents

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


Joined: Oct 21, 2009
Posts: 1

PostPosted: Thu Oct 22, 2009 5:02 am    Post subject: With mass outage - when to stop logging individual incidents Reply with quote

When an incident occurs that causes a mass outage, like the email goes down. SD starts logging incidents and could end up loggin hundreds of incident tickets. Should they stop at some point and create some type of incident ticket that covers the outage and not the individuals being disrupted?

I can see this from a couple of different perspectives and would like to hear some other opinions.

Thanks
Back to top
View user's profile
subh
Newbie
Newbie


Joined: Oct 14, 2009
Posts: 1

PostPosted: Thu Oct 22, 2009 8:04 am    Post subject: Master ticket for outage issue Reply with quote

Hi VooDu,
This is subhash here. when we are confirmed that its not a single user issue. We should stop creating unneccesary ticket, and create a master ticket with Incident manager involvement.
Ex: if an exchange server is down.

This will save time and kep SLA in place as well.

Thanks.
Back to top
View user's profile
Diarmid
Senior Itiler


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

PostPosted: Thu Oct 22, 2009 5:18 pm    Post subject: Reply with quote

There is a thread raised yesterday in the itsmfi forum on the exact same subject.

From a service management perspective, incidents are events not calls. To manage the incident you need the information that comes from calls, including who has been affected. There needs to be the capability to inform users when service is restored and there needs to be the capability to confirm that the restoration is universal and there needs to be the capability to ensure that the scale of the impact has not masked out separate incidents that perhaps had similar symptoms.

It may well be impractical to return every single call or to talk to every single user, and so you may have to rely on information cascading and on users still in trouble raising another call. But you cannot make a simple rule for this and therefore it is probably useful (or even very important) to record all calls that come in related to the incident.
_________________
"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
SwissTony
Senior Itiler


Joined: Feb 26, 2009
Posts: 118
Location: Geneva

PostPosted: Thu Oct 22, 2009 5:29 pm    Post subject: Reply with quote

To back up what Dairmid has said I would recommend logging individual calls & referencing them to the master incident. These individual tickets could be closed directly as being covered by the master ticket, but gives you a record of how many users contacted you. However, this can take up the HD agents time, so the alternative would be:

If you have a phone system allowing for automatic messages to be played before the user gets through to an agent, explain the problem & that it is being addressed, & reference the master ticket number. Once resolved change the message to state that it is now resolved, & if users need to reboot or something you can make the explaination there.

If you are serving multiple sites, and one goes down, then you would know the number of users affected anyway.
Back to top
View user's profile
Diarmid
Senior Itiler


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

PostPosted: Thu Oct 22, 2009 6:42 pm    Post subject: Reply with quote

Just as a little bit of fun, sometimes when something is fixed the users have to do something themselves to get back to normal. When that is the case, you want to consider the users who are away at the time but need to know when they return whether it is hours, days or weeks later.
_________________
"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 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.