[WEB4LIB] QoS Boilerplate

[Shirl Kennedy]

May I modestly recommend the extensuve collection of resources about Service
Level Agreements (SLAs), including negotiating, what to look for, etc., in
our Web Guide:

http://www.ecompany.com/webguide/0,1660,761|201|0|0|1|a,00.html

Shirl Kennedy
Web Guide Manager
eCompany Now
http://www.ecompany.com



> -----Original Message-----
> From: web4lib at webjunction.org
> [mailto:web4lib at webjunction.org]On Behalf Of Donald Barclay
> Sent: Monday, January 29, 2001 10:20 AM
> To: Multiple recipients of list
> Subject: [WEB4LIB] QoS Boilerplate
>
>
>
> I'm posting a query that was passed along to me. Though I don't
> have a ready
> answer for this query, I see that answers to it would be of
> interest to the
> members of this list. The question is:
>
> We're planning to migrate a Web application from local (on-campus) servers
> to
> servers maintained by the application vendor at its site. One thing we're
> concerned about is quality of service; specifically, server availability.
>
> Can any of you suggest boilerplate language for us to have inserted in the
> agreement that specifies service up-time and penalties for not
> achieving it?
> * Can we pick a relevant availability for our situation- 95%,
> 99.0%, 99.9%,
> 99.99%, etc.?
> * Do we define this availability over a time period?
> Daily-weekly-monthly-quarterly? How?
> * What are reasonable - or customary - penalties?
>
>
> Donald A. Barclay
> Houston Academy of Medicine-                         always the beautiful
> answer
> Texas Medical Center Library                         who asks a more
> beautiful question
> dbarclay at library.tmc.edu
> --e.e. cummings
> 713-799-7120
>
>