Discussion on:

DOWNLOAD: SLA for internal business units

http://techrepublic.com.com/5138-10878-729604.html

After you take a look at this download, please post your feedback, ideas for improvements, or further thoughts on this topic.

Thanks,
--The TechRepublic Content Team

Hi Jody,

I think this is a really good starting point. I would also consider including the following:

DR KPI's (Key Performance Indicators)
A corresponding OLA for the impacted support teams
A link to the CMDB to make sure that all CI attributes are updated.

Hope this helps,

Vawns

I too am new in the position of Service Level Management. I have found there there is no standard to SLA's. There are amany different types. We have been working on a 1 page SLA that covers the basics. So far it has been well received.
Norman

If you have a basic SLA that covers the basics and is overly broad, you could be thinking you are defining the white lines in the middle of the road, up until your worker bees get hit by the trucks that are on the road.

What I am saying is that you may have a basic SLA which is OK, and if that is the only stuff that is covered - both the users AND executives have to understand that anything that falls out of that is out of scope.

Our desktop support team is consistently being hit with requests to install servers. Their job is to ensure the desktops run, not the servers. That is my job. They don't like coming to me because if they can not use space on a server that is being utilized 10% of the time - they don't need one.

I tried to use the download link and the file is corrupt.

I think the general idea is good, it has a solid footing but, I have some questions about the details that each company might put into their individual sla's.


Maybe in appendix you could offer a few insights into what type of criteria you add in there?

Chris

The services you suggest in the SLA might be those an IT department provided to the business if the business were highly IT literate and independent of IT and had a poor perception of IT. If they treated IT as an ISP providing crude infrastructure and no more.

In general, I hope we work in IT departments that are more of an ASP: that provide managed applications to the business. In which case what you list are not services at all but technology layers that underpin the services.

Services should be as the business sees and consumes them: "what comes out of the pipe". e.g.
- communications (broken down into voice, email, voip ...)
- financials
- HR
- payroll
- inventory system
- desktop productivity tools
- desktop hardware management
etc...