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: FYFE
New Today: 51
New Yesterday: 73
Overall: 143543

People Online:
Visitors: 50
Members: 1
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 - SLA to Service relationships
 Forum FAQForum FAQ   SearchSearch   UsergroupsUsergroups   ProfileProfile   Log in to check your private messagesLog in to check your private messages   Log inLog in 

SLA to Service relationships

 
Post new topic   Reply to topic    ITIL Forum Index -> Related Topics
View previous topic :: View next topic  
Author Message
kas
Newbie
Newbie


Joined: Jan 14, 2008
Posts: 3

PostPosted: Tue Jan 15, 2008 8:01 pm    Post subject: SLA to Service relationships Reply with quote

Few questions...

Can an SLA cover more than one service or should there be a distinct SLA for each service?

Likewise, can a service be covered by more than one SLA?

If a service can be covered by more than one SLA then could you potentially have different service support hours for the same service between the different SLAs leading to effectively different response times for two calls for the same service depending on which agreement they are covered by...?
Back to top
View user's profile
Mark-OLoughlin
Senior Itiler


Joined: Oct 12, 2007
Posts: 306
Location: Ireland

PostPosted: Tue Jan 15, 2008 8:23 pm    Post subject: Reply with quote

... and that is why it should be kept as simple as possible.

if you are an immature org starting out you may use one SLA to cover say a general response and resolution time. Over time you would develop an SLA per service to cover the specifics of that service.

You should aim to ahve one SLA per service However due to the possible number of services and the time required to upkeep and review then (one or twice a year) you hae to determine if you have the resources to do this and if not what you want to do.

Except in the situation above I don't like services being under 2 or more SLA's - it can get confusing or difficult to understand. Anyway be sure you have a service portfolio set up that can link the service directly to its SLA.
_________________
Mark O'Loughlin
ITSM / ITIL Consultant
Back to top
View user's profile
kas
Newbie
Newbie


Joined: Jan 14, 2008
Posts: 3

PostPosted: Tue Jan 15, 2008 8:33 pm    Post subject: Reply with quote

Thanks for the reply. So you are saying that you could have the same service under potentially multiple SLA's, each with their own agreed service support hours?

Effectively then, for example, if a service failed resulting in 2 or more related incidents then you could have 2 or more potential service support periods (with associated response times etc.) covering these multiple incidents depending on which agreement they come under? I.e. a multiple level tier of service depending on who the call comes from, even though the calls all relate to the same service you could have, for example, 2 hours to respond to call A but 4 hours to respond to call B?
Back to top
View user's profile
Mark-OLoughlin
Senior Itiler


Joined: Oct 12, 2007
Posts: 306
Location: Ireland

PostPosted: Tue Jan 15, 2008 8:55 pm    Post subject: Reply with quote

No,

I am saying the exact opposite. One SLA per service - keep it that simple.

Regarding "if you are an immature org starting out you may use one SLA to cover say a general response and resolution time"

this refers to say settig a global prioity response and resolution time for ALL services to beging with. As you develop the SLA's for the services they get removed from this umbrella SLA alltogether.

As you mention a service under 2 or more SLA's would be difficult to manage
_________________
Mark O'Loughlin
ITSM / ITIL Consultant
Back to top
View user's profile
kas
Newbie
Newbie


Joined: Jan 14, 2008
Posts: 3

PostPosted: Tue Jan 15, 2008 9:07 pm    Post subject: Reply with quote

Okay, thanks for that.

We've effectively got services and sub-services if you like to better manage call allocation so we could have a single SLA covering multiple services/sub-services but each one of those services/sub-services should only ever be covered by a single SLA with it's corresponding service support hours.

Makes things more logical as far as I'm concerned anyway, and easier to develop our escalation routines etc. based on working time spent on calls - potentially different support hours for the same service would cause issues...
Back to top
View user's profile
Display posts from previous:   
Post new topic   Reply to topic    ITIL Forum Index -> Related Topics 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.