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: KSBFO
New Today: 7
New Yesterday: 54
Overall: 139819

People Online:
Visitors: 65
Members: 5
Total: 70 .

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

Major Incident

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


Joined: Jan 21, 2010
Posts: 9

PostPosted: Sat Apr 24, 2010 2:07 am    Post subject: Major Incident Reply with quote

Hello,

I'm implementing ITIL within our organization and management has a feeling tha Major Incidents belong within Problem. The assumption is that when a Major Incident occurs and SLAs are breached then it should be handed over to Problem management to "restore service and/or work with a team to figure out how to restore service". The reasoning behind all of this is that the Problem Manager has more technical knowledge than the Incident manager. This organization has identified the Problem Manager as the technical guru and not the Incident Manager, therefore the Problem manager is the most appropriate resource to bring teams together.

I view that Major Incidents stay within Incident Management and continue to work in that fashion and not be handed over to Problem.

Has anyone dealt with this before? If so, how were you able to implement that cultural change as to "why" Major Incidents should remain within Incident Management and not Problems.

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


Joined: Feb 27, 2009
Posts: 16
Location: North Coast, USA

PostPosted: Sat Apr 24, 2010 6:48 am    Post subject: Reply with quote

When I set up an Incident Management process, I stressed that I was defining Roles and Responsibilities. The People that filled those roles could change at any time.

This way, whoever is fulfilling the "Problem Manager" ROLE can certainly step in to help with the Incident Management process (hopefully putting politics aside) and still keep the activities within the IM process.

This also helps to step away from particular titles such as "Network Engineer" or "Help Desk Technician", or specific people's names in the documentation.

Operational Definitions also clarify what is meant by a Problem and an Incident . . . or an Event. I'm in the process now of educating our staff on those terms Wink
Back to top
View user's profile
Diarmid
Senior Itiler


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

PostPosted: Tue Apr 27, 2010 7:36 pm    Post subject: Reply with quote

Cking is correct. You can deal with this by having a major incident procedure that, amongst other things, states that all necessary technical and management skills will be brought to bear on the major incident. And by defining the skill and authority level/scope for the individual required to manage the major incident.

You could bear in mind that, perhaps, a major incident manager requires a modicum of technical expertise and a bucket load of management, planning, decision-making, co-ordinating and liaising skills and good understanding of the business perspective.

It would probably be best if any IT services manager could manage a major incident by following the major incident procedure, rather than the problem management procedure. After all, can you wait for your problem manager to return from holidays?
_________________
"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
pk_
Itiler


Joined: Feb 03, 2010
Posts: 30

PostPosted: Wed May 19, 2010 6:50 pm    Post subject: Reply with quote

I'd imagine the Problem Manager would also have more experience of managing the various 3rd party and/or internal resolution groups, and would have built up a stronger relationship with them through PM activities.

Depending on the scale of the Major Incident and the structure of the company this would probably come in handy
Back to top
View user's profile
aulvin
Newbie
Newbie


Joined: May 20, 2010
Posts: 4

PostPosted: Tue May 25, 2010 11:06 am    Post subject: Reply with quote

Dear all,

Regarding this major incident that require longer resolution time, if it is decided to create problem ticket for this, can we closed the incident? So that the monitoring will be done thru problem ticket..

Cheers,
Aulvin
Back to top
View user's profile
Diarmid
Senior Itiler


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

PostPosted: Tue May 25, 2010 11:21 am    Post subject: Reply with quote

aulvin,

problem management is unlikely to be geared up for service restoration since it is normally set up to investigate underlying causes and identifying solutions. Neither its processes nor its people are likely to be used to working to fix a downed system.

If you close the incident (presumably with an attribute of "not fixed") how will you ever restore the service? (theoretically speaking).

The problem ticket has nothing to do with the resolution of 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
viv121
Senior Itiler


Joined: Dec 15, 2007
Posts: 113

PostPosted: Thu May 27, 2010 12:23 am    Post subject: Reply with quote

Do we have failed incidents in that case?
_________________
regards,

Vivek
"the only statistics you can trust are those you falsified yourself"
Winston Churchill
Back to top
View user's profile Send e-mail
jpgilles
Senior Itiler


Joined: Mar 29, 2007
Posts: 123
Location: FRance

PostPosted: Thu May 27, 2010 5:02 pm    Post subject: Reply with quote

To me, whether or not a problem is open does not change IM's responsibility.

But you can probably adapt your IM process so that , in rare cases of a majour outage, for which no way to restore the service is identified, the incident is escalated to PM as a URGENT PROBLEM so it is investigated immediately and lead to a Urgent change to implement a work around tat will allow to resolve the incident and let the problem (now a knwon error) move to a normal status.

I think it realyy depends how you are organised, but the idea of involving groups or people that deal with long term investigations and technical aspects in the resolution of incidents that need speed and business ficus needs to seriously thought at befor implementation.

rgds
JP
_________________
JP Gilles
Back to top
View user's profile Send e-mail
Diarmid
Senior Itiler


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

PostPosted: Thu May 27, 2010 9:35 pm    Post subject: Reply with quote

JP,

I know it is different for different organizations, but I would be inclined to rope in the "clever" problem people as needed to work on the incident and therefore keep it under incident management which is geared up to the right focus for the sense of urgency, and can remain answerable for progress.

It is important to understand the difference between incident (investigation and resolution) activities and incident management.
_________________
"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.