OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

soa-rm-ra message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]

Subject: Re: [soa-rm-ra] definition of SLA


Thanks for the pointer.  I was out of the office today and didn't have a chance to look at this beyond your summary below, but my first impression is that definition includes every possible aspect of a service, and that doesn't make sense.  Do you really expect the SLA of every service (or even a significant number) to go into the details of disaster recovery?  I may want some assurance a critical service will be there during times of extreme duress, but I probably do not care (and would not appreciate) the details of how the provider will do it.

But let me read this and the other responses to my SLA definition question and let me see if I migrate to a more enlightened view.


On Jan 23, 2007, at 12:47 AM, Danny Thornton wrote:

The following link is one description:

It lists the following pieces to the SLA:

Definition of Services
Problem Management
Performance Management
Customer Duties and Responsibilities
Warranties and Remedies
   Service quality
   Third party claims
   Remedies for breaches
   Force majeure
   Information Security Policies
   Security Audit and Internal Audit
Disaster Recovery

Several parts of the SLA can translate into policies
and configurables for services and devices.  The
policies created from the SLA can result in automated
run time adjustments to services and devices to meet
the requirements in the SLA.  A failure in ability to
meet the SLA in the SOA results in an elevation of the
problem which might have legal ramifications.

In terms of the service description, we could state
that Interactions Policies and Contracts can contain
an aggregation of one or more SLAs.  We could then
extend the SLA to include the above types of
information in a separate diagram.


--- Ken Laskey <klaskey@mitre.org> wrote:

This will probably need to be tackled at some point
and I have the  
question biting me now.  Is there an accepted
definition of a service  
level agreement?  How would we define it?  For what
purposes is it  
used?  When should someone care?

Answer these and I have more questions?



Ken Laskey
MITRE Corporation, M/S H305     phone:  703-983-7934
7515 Colshire Drive                        fax:     
McLean VA 22102-7508

The fish are biting. 
Get more visitors on your site using Yahoo! Search Marketing.

Ken Laskey
MITRE Corporation, M/S H305     phone:  703-983-7934
7515 Colshire Drive                        fax:        703-983-1379
McLean VA 22102-7508

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]