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: FFrame
New Today: 6
New Yesterday: 50
Overall: 146269

People Online:
Visitors: 51
Members: 1
Total: 52 .

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

SLA development

 
Post new topic   Reply to topic    ITIL Forum Index -> ITIL Discussion
View previous topic :: View next topic  
Author Message
Shanners
Newbie
Newbie


Joined: Feb 20, 2007
Posts: 6

PostPosted: Thu Feb 22, 2007 10:15 pm    Post subject: SLA development Reply with quote

Hi All,

A bit of advice needed.

I'm tasked with developing SLAs, OLAs and reviewing UCs and have started gathering the information from the business and IT to form a service catalogue.

My problem relates to infrastructure services (backup mgt, patches & upgrades, database monitoring, hardware maintenance etc) I do not believe that the details should be in the service catalogue or SLAs as it doesn't mean anything to the Customer.

But.... where should the details of these services and responsibilities be documented.

Any advice welcome

Chris
Back to top
View user's profile
itilimp
Senior Itiler


Joined: Jan 20, 2006
Posts: 172
Location: England

PostPosted: Fri Feb 23, 2007 4:28 am    Post subject: Reply with quote

I'd say give them a brief mention in support section of SLA, and detail these aspects (backup, patches & upgrades, database monitoring, hardware maintenance etc.) in the OLAs and UCs.

Having said that, I'm not a SLM so I may be wrong Wink
Back to top
View user's profile Visit poster's website
UKVIKING
Senior Itiler


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

PostPosted: Fri Feb 23, 2007 7:25 am    Post subject: Reply with quote

Look in the ITIL red book for the definitions of what should/could be in an SLA

It is NOT a legal document but it should cover what the customer expects from the service and what the provider expects to provide

For example

A customer wants 24x7 support w/a 2 hour response time to fix hardware faults
The maintenance vendor can promise 16x5 with 4 hour response 8 hour fix time
the service provider should base the service on what they can get from the maintenance vendor

If the customer wants the 24x7 service then the service provider needs to find a vendor who will supply that for the right level of fee and up the fees the customer is charging

If an SLA is NOT clear on what the customer is suppose to get, you get bruised egos ont he part of the customer because he is not getting the service he expected (but did not pay for it - but the sales team promised him)
_________________
John Hardesty
ITSM Manager's Certificate (Red Badge)

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


Joined: Jan 03, 2007
Posts: 189
Location: Redmond, WA

PostPosted: Sat Feb 24, 2007 1:25 pm    Post subject: Re: SLA development Reply with quote

Shanners wrote:
Hi All,

A bit of advice needed.

I'm tasked with developing SLAs, OLAs and reviewing UCs and have started gathering the information from the business and IT to form a service catalogue.

My problem relates to infrastructure services (backup mgt, patches & upgrades, database monitoring, hardware maintenance etc) I do not believe that the details should be in the service catalogue or SLAs as it doesn't mean anything to the Customer.

But.... where should the details of these services and responsibilities be documented.

Any advice welcome

Chris


This is the difference between what the IT organization as a whole is promising to the customer (SLA), and what the functional IT groups promise to each other (OLA).

The SLA can state that "IT will ensure that computer equipment will be maintained". Of course that statement is a generalization that cannot be measured, so perhaps a better statement would be "There will be less than 100 lost man-hours per year due to lack of computer equipment maintenance".

The OLA will need to state everything that the functional IT groups will need to do in relation to each other to support the SLA. This will include what the server team will do for patching of the servers, what the desktop team will do to patch the desktop systems, what the DBAs will do to optimize the databases, etc, etc.

The idea is that the promise made in the SLA has to be measurable and completely supported by the OLAs that the SLA is reliant on.

Don
Back to top
View user's profile
Ziad
Senior Itiler


Joined: Sep 27, 2006
Posts: 91

PostPosted: Sat Feb 24, 2007 10:28 pm    Post subject: Reply with quote

Any service that is provided to the customer should be detailed in the SLA agreed with this customer.

An example is the backup service, you can add it to the SLA describing the service and the way you provide it and stating the level to which you commit to successfully complete a backup during the backup window.

That was just an illustrative example, things may be done in a totally different way.

Cheers,
Z!
Back to top
View user's profile Send e-mail
goitilcouk
Newbie
Newbie


Joined: Feb 24, 2007
Posts: 19

PostPosted: Mon Feb 26, 2007 5:02 am    Post subject: Reply with quote

Shanners, whats your structure in term of customer / IT supplier ?

This could influence how you position it. We outsource our IT. Our suppliers SLA's to us (which are UC's to support our customer facing SLA's) include this information.

Customer facing SLA's tend to include service hours, uptime etc. Thats all they are worried about. The detail temds to lie in the UC's and OLA's

Rob
Back to top
View user's profile Send e-mail Visit poster's website
Shanners
Newbie
Newbie


Joined: Feb 20, 2007
Posts: 6

PostPosted: Tue Feb 27, 2007 2:15 am    Post subject: Reply with quote

Thanks all,

I think the OLA document looks like tht ebest place so as not to bog the SLA down in technical language and details.

Cheers

Chris
Back to top
View user's profile
Display posts from previous:   
Post new topic   Reply to topic    ITIL Forum Index -> ITIL Discussion 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.