Negotiating an SLA

Unanswered Question
Jan 24th, 2008

We have a client who is in the process of negotiating a Service Level

Agreement with a carrier/VoIP service provider. The SLA needs to addess

avaialbility of the LAN/WAN, avaialbility of a the customer owned (Cisco

based) VoIP infrastucture, and time to repair any faults identified.

If you have specific experience

with similar SLA negotiations or knowledge of deployments where customer

problems may have been avoided through better SLA definitions, please elaborate.

Specifically I am interested in the following SLA features:

1. What reporting mechanisms have been used to verify WAN performance

(verification of bandwidth, verification of delay/jitter, verification

of

avilability)? Have these been customer driven or service provider

driven?

2. What data entry mechanisms have been used to input customer change

requests (web portal, on-site engineer, phone call, etc.)?

3. What change request response times have been supported (how long to

implement routine requests, priority requests, etc.)?

4. What level of service is required to initiate a truck-roll for

on-site

fault repair or system updates (because customer says it's broken, or

must

it be discovered and verified by the service provider)?

5. How are intermittent outages handled (circuit/system is flapping or

crashing)?

6. How are quality of service issues resolved (circuit/system works but

is

performing below expectation)?

I have this problem too.
0 votes
  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
Loading.

Actions

This Discussion