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


The five ITIL books can be obtained directly from the publisher's website:

Or as downloadable PDFs: HERE

Current Membership

Latest: StewartDug
New Today: 22
New Yesterday: 34
Overall: 231560

People Online:
Visitors: 138
Members: 0
Total: 138



Don't have an account yet? You can create one. As a registered user you have some advantages like theme manager, comments configuration and post comments with your name.

Related Resources

Service related resources
Service Level Agreement

How to set up
IT Change Management
Process Info-Graphic

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.


Select Interface Language:

Please contact us via the feedback page to discuss advertising rates.

The Itil Community Forum: Forums

ITIL :: View topic - Missed SLA reporting
 Forum FAQForum FAQ   SearchSearch   UsergroupsUsergroups   ProfileProfile   Log in to check your private messagesLog in to check your private messages   Log inLog in 

Missed SLA reporting

Post new topic   Reply to topic    ITIL Forum Index -> ITIL Service Delivery
View previous topic :: View next topic  
Author Message

Joined: Jul 06, 2009
Posts: 2

PostPosted: Tue Jul 07, 2009 1:47 am    Post subject: Missed SLA reporting Reply with quote

We're struck and need to drive the process for handling missed SLA.Please share your thoughts on following items-

1. In a 8 hrs service desk based support(9am to 5pm), when an SLA is missed, is the time for the missed SLA calculated based on SLA support hours or is it the wall time?

2. In case an SLA is missed, there is an escalation mechanism in place. The problem is that many SLAs get escalated. Can you share what is the best practise to review these missed SLAs?

3. How is the analysis for missed SLA done and what are other corrective actions you have come across( other than escalations!)

Back to top
View user's profile

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

PostPosted: Tue Jul 07, 2009 2:08 am    Post subject: Reply with quote

We have a 24hr support desk. We have varying SLAs depending on the severity/criticality of the incident. For High and Medium our SLOs and SLAs are based on 24x7. For Low incidents, we are on a 9x5 clock.

Not real sure what you mean by "Escalating SLAs". An SLA is a measurement - you either hit it or don't. Tickets are escalated.

All support activity *should* be logged in the ticket. If an SLA is missed, there should be ample documentation in the support ticket to identify where the miss occured.
Back to top
View user's profile
Senior Itiler

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

PostPosted: Tue Jul 07, 2009 2:33 am    Post subject: Reply with quote

As CKing said you will have incidents and problems which maybe relate to a SLA breach. The escalation for these should be defined within the Incident & Problem Mgmt process documents.

The SLM should manage the review of SLAs, and report on breaches, which would then be discussed with the customer within the Service Review meetings.
Back to top
View user's profile
Senior Itiler

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

PostPosted: Tue Jul 07, 2009 3:20 am    Post subject: Reply with quote

The answer is it depends on the contract / SL Agreemnt made with the customer

If the SLA is set to a 24 hours clock and you provide a 8 hour service (9a mto 5 pm), then you're screwed always. The people who signed the SLA from your company should be taken out, beaten up, down, charm and strange (quarks u know). and sent out to re-negotiate the SLA in line with the service provided

You have to clear all your tickets before the end of your day... Even ones that were raised at 1659:59:59

The other issue is what is the criteria of the SLA -

solve the issue or

respond to the ticket

if it is respond to the ticket, then as long as the activity shows that the SD has escalated to the right group w/in a time frame then you are OK

If the SLA and service are set to the same clock, then if a ticket is raised at 1600, then the next morning at 1000m, the ticket is 2 hours old.
John Hardesty
ITSM Manager's Certificate (Red Badge)

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

Joined: Jul 06, 2009
Posts: 2

PostPosted: Wed Jul 08, 2009 4:01 am    Post subject: Reply with quote

UKVIKING...That pretty much clarifies .......

The context here is that we are very much in initial stage of SLA based support rollout, and a pattern observed is that many of the tickets are missing their SLAs. Have any come across this while moving to SLA based support model ?

Whats are the possible approaches here to move ahead with corrective actions ?
Back to top
View user's profile
Senior Itiler

Joined: Mar 04, 2008
Posts: 1894
Location: Helensburgh

PostPosted: Wed Jul 08, 2009 7:37 pm    Post subject: Reply with quote


Analysis is the key here.

Were the SLAs based on analysis of incident resolution, or on identified customer requirement - or perceived customer requirement or perceived reasonableness?

If customer requirement is real (i.e. there is real customer detriment if services are unavailable/unduly slow for longer than a certain time) then this can only apply to incidents that have significant effect on service - so, are your SLAs selective about what incidents are critical?

Also, if customer requirement is real, has the cost of meeting the requirement been measured and appropriate resources put in place?

Are SLAs set against individual incidents (this is disastrous) or against averages or percentages over time - based on analysis of what is achievable?

Are you analysing the incident management process to determine whether the over-runs are due to the learning process (and therefore should go away very soon), the nature of the process (and therefore you need to improve the process), the nature of the incidents (and therefore you either need more resources or more time)?

One perspective you must obtain is a measure of the cost to the business of these breaches.

If they are "paper" breaches that have little effect on the business then you do not want to waste inordinate time bureaucratically administering an SLA regime that has unnecessary strictures.

If there is considerable cost to the business then you need to look at the cost of improvement to your incident management regardless whether it is more training, additional rersources or improved process.
"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 -> ITIL Service Delivery 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

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.