search

linked-usdl / usdl-core

Linked USDL core is a the foundation module for the Linked USDL family of vocabularies. It basically covers four essential aspects: i)service descriptions, ii) service offerings descriptions, iii) business entities involvement, and iv) service delivery communication channels and interaction points.
5 stars 1 forks source link

SLA violations #43

Closed tmetzke closed 11 years ago

tmetzke commented 11 years ago

I want to model an SLA agreement for a service but I couldn't find anything to include the consequences of a violation of the agreement. Neither in the SLA nor in the PRICE ontology, where I could both imagine them to fit.

Is there anything modelled so far that serves to express something like service credits for customers, if an SLA is not met?

(Let's say if the availability of a service is lower than 97%, this is made up to the customer by 1$ per hour of service usage or anything like that)

Thanks for your help! :)

drleidig commented 11 years ago

Hi Tobias,

the SLA vocabulary is not finalized yet. I think Carlos and his team is currently working on it. I derived the initial version from the USDL 3M5 specification, after talking to some SLA experts.The goal was to simplify it drastically with respect to essential, so called "competency questions", which are the types of questions you would like to have a real system to answer. The point is that you can model to arbitrary depth, which is somehow counter productive in respect to our goal of easy adoption and stepwise refinement. Or in other words: Keep it simple for the 80% of applications and provide specific extensions for the rest.

Your question also was recently raised by a student, who wanted to describe Cloud infrastructure services (Amazon EC2, ...) including pricing and SLA. In his thesis he suggested to introduce a property for Price Components (a price component can also be negative, if it's a reduction/credit), which refers to a certain SLA Statement.

We will discuss this when we will review the pricing and SLA vocabulary soon. You are invited to participate and feed in your requirements and use cases.

tmetzke commented 11 years ago

Ok, for the time being, I will use a self-written property that somehow correlates to what the other student seems to suggest in his thesis then, since this is what we thought about as well here. :)

Since we're just "playing around" with the linked usdl ontology in a university seminar over here, this is just fine for the moment.

I'd very well like to participate in the discussion, thanks. :)