Service Level Agreement "SLA" Resource- Description
This Service Level Agreement "SLA" Resource Model aims at illustrating the way to translating "SLA Resource Model" in JSON representation, reflecting the resource aspect described in the "SLA API Profile" (Management Requirements) document V0.2. Service Level Agreement (SLA) Resource Model and associate attributes are aligned with those described in SID Service Level Agreement modeling. Meaning no Resources are imported from other sources. Besides, the entities are represented in terms of roles, each with its rights & duties covering Multi-partner model illustrating B2BX model (SLA Provider, SLA Consumer, SLA Auditor, EndUser roles). In this model, "SLA Provider" is referring to a CSP while "SLA Consumer" is referring to a DSP. The "EndUser" is referring to the customer of the DSP, in some cases he could be a customer of both (CSP and DSP). "SLA Auditor" role is to monitor SLA as described in TR178V2. It could be played either by the CSP himself or delegated to a 3rd party. The "Agreed" or "Approved SLA" is described in terms of SLA rules which contains the Metrics, their related values or range, thresholds, valid period or date, consequences in case of violation of any clause of the SLA. It is also assumed all Metrics are the existing ones which are stored in the Service Provider "Metrics Library" with their attached references. Besides, each metric is attached to a given Product in the Catalogue with a dedicated reference e.g. "URL". The Service Level Agreement "SLA" resource model is also characterized by its "validity period". This use case covers the situation where the validity period is pre-determined (planned) which excludes the case of Time-variant SLA that could be attached to a "SLA on-Demand" use case. The latter could be considered in another release for specific use cases (Cloud, virtualization) for instance. In order to optimize the SLA resource, there is a need for defining a common pattern or Template "rule". This pattern is structured as following: the Id of the metric, its name, the measurement unit attached to the considered metric, its reference value, the tolerance value when the threshold is crossed and the consequence in case of violation. Regarding the financial-related aspect and penalties associated to a consequence, a pointer is simply mentioned to the Service Level Agreement "SLA" contract. Example of the JSON representation of an Service Level Agreement "SLA" resource { "id": "123444", "href": "http/www.acme.com/SlaManagement/sla/123444", "name": "HighSpeedDataSLA", "description": "SLA for high speed data.", "version": "0.1", "validFor": { "startDateTime": "2013-04-19T16:42:23.0Z", "endDateTime": "2013-04-21T09:43:54.0Z" },
"relatedParty": [ { "href": "http://", "role": "SLAProvider" },
{ "href": "http://", "role": "SLAConsumer" },
{ "href": "http://", "role": "SLAAuditor" },
{ "href": "http://", "role": "SLABusinessBroker" },
{ "href": "http://", "role": "SLATechnicalBroker" },
{ "href": "http://", "role": "ThirdPartySLAManager" },
{ "href": "http://", "role": "EndUser" } ],
"rule": [ { "id": "availability", "metric": "http://IEEE99.5/Availability", "unit": "string", "referenceValue": "available", "operator": ".eq", "tolerance": "0.05", "consequence": "http://ww.acme.com/contract/clause/42" },
{ "id": "downstream_GBR", "metric": "http://IEEE99.5/Data/bitrates/GBR/down", "unit": "kbps", "referenceValue": "1024", "operator": ".ge", "tolerance": "0.20", "consequence": "http://ww.acme.com/contract/clause/45" } ],
"template": { "href": "http/www.acme.com/slaManagement/slaTemplate/42", "name": "DataSLATemplate", "description": "basic template for Data SLA" } } |
|