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: LorenzaOfs
New Today: 33
New Yesterday: 63
Overall: 149707

People Online:
Visitors: 70
Members: 1
Total: 71 .

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 - Example of Problem SLA / Priority
 Forum FAQForum FAQ   SearchSearch   UsergroupsUsergroups   ProfileProfile   Log in to check your private messagesLog in to check your private messages   Log inLog in 

Example of Problem SLA / Priority

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


Joined: Oct 08, 2012
Posts: 13

PostPosted: Tue Jan 22, 2013 1:00 am    Post subject: Example of Problem SLA / Priority Reply with quote

Are the metrics / SLA below a good indication to get a problem resolved. Or is the metric below related to the incident ticket? Can the SLA'S assigned to an incident be the same for resolving a Problem ?

How can you put a time line on getting a problem resolved?

o (Very High) up to 1 Day
 Multiple Incidents to critical Business System or infrastructure
 No workaround identified
 No Root Cause available

o (High) up to 3 days
 Multiple Incidents to critical Business System or infrastructure
 Workaround identified to restore service
 Root Cause not available

o (medium) up to 5 days
 Multiple Incidents to Business System or infrastructure
 Workaround identified to restore service.
 Root Cause Available

o (Low) Over 5 days
 Non-service impacting, workaround in place with Root Cause available
Back to top
View user's profile
UKVIKING
Senior Itiler


Joined: Sep 16, 2006
Posts: 3319
Location: London, UK

PostPosted: Tue Jan 22, 2013 6:16 am    Post subject: Reply with quote

Fulhamm

As Incident Management is to resolve the incident and restore the service a SLA is used to determine how quick the service is restored against what would be the norm for fixing that type - classification - of an incident

However, Problem management is about finding the cause of the incident - which may takes days. weeks months years or never

SLAs is not recommended then
_________________
John Hardesty
ITSM Manager's Certificate (Red Badge)

Change Management is POWER & CONTROL. /....evil laughter
Back to top
View user's profile
KenLuo
Senior Itiler


Joined: Nov 03, 2012
Posts: 55
Location: Singapore

PostPosted: Tue Jan 22, 2013 4:07 pm    Post subject: Reply with quote

Resolving problems is a bit complicated then restoring service, as you might need to work with different support teams or even vendors.

So a definitive SLA for problem management is quite difficult.

But we do track the problem with an aggressive way if it causes a severity 1 or severity 2 issues, e.g. system downtime, performance degradation:
1) We need update every day initially until a clear and detailed follow-up plan is in place.
2) And then we need update every week to check the progress.
3) If the issue happens again, we'll then change the weekly meeting to daily meeting with incident / problem support on the same call.
_________________
Luo, Tian-Hong (Ken)
Regional Operation Lead

ITIL Expert Certified
Back to top
View user's profile
fulhamn
Newbie
Newbie


Joined: Oct 08, 2012
Posts: 13

PostPosted: Wed Jan 23, 2013 12:25 am    Post subject: Reply with quote

UKVIKING wrote:
Fulhamm

As Incident Management is to resolve the incident and restore the service a SLA is used to determine how quick the service is restored against what would be the norm for fixing that type - classification - of an incident

However, Problem management is about finding the cause of the incident - which may takes days. weeks months years or never

SLAs is not recommended then


Agree, also company politics might come into consideration.
Back to top
View user's profile
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.