resolution time?

[abai84]

Hi to all members of the forum
i'm a new member and this is my first post, hope i'll find loads of benifits from this good forum
i'm kinda new in the datacenter business in the leading telecom company in saudi Arabia (STC).
straight to my question which is composed of 2 parts,
1- Is resolution time of an incident binding as per SLA usually?
2- Is there a standard resolution time (per priority\severity level) according to ITIL? for instance 1 hour for highest priority incidents,4 hours for 2nd level of priority, etc

Thanks in advance and looking forward to a alot of answers and enlightments.

[Diarmid]

2. ITIL makes no specifications whatsoever as to standards.

1. Consider the problems that will arise from a concept of binding resolution time for an incident.

The next bit is just my opinion.

Service Level Agreements should not be about such detailed matters as individual incidents. They should be about the overall levels of service. They should focus first of all on the availability and the quality of service and only through that focus establish requirements for incident resolution.
_________________
"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

[abai84]

Hi and thanks Diarmid for your reply
as you know average resolution time is used as a KPI in ITIL in incident management even if you are not commited by it in-front of the customer\user however it does remain a KPI. the question is, if there is no standard threshold for resolution time per severity level, isn't there a best practice average resolution time?

Thanks for your help

[BorisBear]

[Diarmid]

[StanleyLuces]

SLA's is bargaining between provider and the client, no standard values - sit it out with client and agree on the acceptable.. achievable SLA.

Well.. in your case - you as a provider might want to ask for more "resources" in case clients wants higher SLA's that you can currently offer.

[Flasheart]

As mentioned ITIL is not prescriptive...
That said, I can give you examples of SLA’s I’ve had in the past relating to resolution times..
One SLA may read: 90% of all mission critical incident tickets must be resolved within 4 hours.
Another could say 80% of all normal priority incident tickets must be resolved within 48 hours.
And another SLA example could indicate average resolution times for mission critical incident tickets must be 2 hours or less.

Again these are examples, as others have indicated its up to the service provider and the customer to agree upon these.

Just my 2 cents.

[abai84]

Dear All, really thanks for your useful posts.
you see, my case in detail is this....
we have a tier4 datacenter "uptime institute" which is being operated by a partner. I wanted to have something to measure the performance of our partner to ensure the best quality possible to our customers. our partners are insisting that resolution time shouldnt be commited to with the customer while my point of view was that i need to monitor the average resolution time regardless is we commit to it with the customer, after which we can have alot of information we can analyize and make use of.
Thanks flashheart for the useful suggestion.

[StanleyLuces]

I agree with you in wanting to have measurables from your partner. I would understand why your partner would not want to commit resolution time to the customers.. but when the time comes and your customer demands it.. you have to give something.. better iron out an underpinning contract with your external partner so you have something jsut in case..

But if your interest is just to monitor the resolution times then just do it.. I mean nothing can stop you from doing it.. with or without SLA

[abai84]

Thanks StanleyLuces.......