...

1. 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" } }

   Anchor
   _Toc404167090 _Toc404167090

   Field description

   Field	Description
   id	Unique identifier of the Service level Agreement (SLA)
   name	Name of the Service level Agreement (SLA)
   description	Description of the Service level Agreement (SLA)
   version	Version of the Service level Agreement (SLA)
   validityPeriod	Period where the clauses of the SLA are applicable
   startTime	Date/Time of the beginning of the validityPeriod
   endTime	Date/Time of the end of the validityPeriod
   template	SLA Template characteristics
   href	Reference of the Template
   name	Name of the template
   description	Description of the template
   relatedParty	Parties engaged in the SLA (SLA provider, SLA consumer, …)
   Role	Role attached to each party (SLA provider, SLA consumer, …)
   href	Reference of the party
   state	Service Level Agreement state
   approved	Indicates if the service level agreement is approved or not (True or false)
   rule	Common pattern or Template for the SLA parameters, metrics, and thresholds
   id	Unique identifier of the metric
   metric	Reference of metric stored in the Service Provider "Metrics Library"
   unit	Unit of measure of metric
   referenceValue	Reference value of metric
   operator	Operator used when calculating the rule
   tolerance	Allowable variation of metric
   consequence	defines the action to be applied as a result of a threshold crossing

   Anchor
   _Toc404167091 _Toc404167091

   Service Level Agreement "SLA" States

   Regarding "SLA States", the source considered is "WS-Agreement" diagram (state graphic) from which the allowed status changes as recommended in the "SLA Profile" document (section 4) when applicable.
   For instance, it is assumed that the processes that are linked to the "Negotiation Phase" of the SLA Management lifecycle such as SLA "Approval", "Terms or Conditions" and "Consequence" are in the status of "completed". That means, only one state "Observed" is considered which supposes the SLA is approved and accepted by the related Parties.

   Anchor
   _Toc404167092 _Toc404167092

   SLA resource model

   
   

   Anchor
   _Toc368488804 _Toc368488804

   Anchor
   _Toc404167093 _Toc404167093

   SLAViolation Resource

2. SLA Violation resource description

...

1. Example of the JSON representation of an SLAViolation

   { "id": "7467", "href": "http/www.acme.com/slaManagement/slaViolation/123444", "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" } ], "sla": { "href": "http/www.acme.com/slaManagement/sla/123444", "description": "sla of premium video" }, "violation": { "unit": "string", "referenceValue": "available", "operator": ".eq", "actualValue": "available", "tolerance": "0.05", "violationAverage": "0.1", "comment": "Availability below agreed level.", "consequence": "http://ww.acme.com/contract/clause/42", "attachment": { "href": "https://foo.bar/screenshot.123", "description": "availability statistics for August 2013" }, "rule": { "href": "http/www.zak.com/slaManagement/sla/123444/rules/availability", "description": "availability" } } }

   Anchor
   _Toc404167094 _Toc404167094

   Field description

   Field	Description
   id	The id of the resource model (SLAViolation)
   SLA
   description	Description of the Service level Agreement (SLA)
   href	Reference of the Service Level Agreement
   RelatedParty	Party engaged in the SLA (SLA provider, SLA consumer, …)
   role	Role attached to each party (SLA provider, SLA consumer, …)
   href	Reference of the party
   Violation	A discrepancy identified by applying rules to Service Level Agreement related entities.
   rule	The rule represents the value of the threshold of the metric. Once crossed it triggers a violation.
   description	Description of the rule
   href	Reference of the rule
   unit	Unit of measure of metric
   referenceValue	Reference value of metric
   operator	Operator used when calculating the rule
   actualValue	Actual value of the metric
   tolerance	Allowable variation of metric
   violationAverage	TBD
   Comment	Comment about violation
   consequence	defines the action to be applied as a result of a threshold crossing
   attachment	represents statistics, a dashboard or reporting data to be presented to the target parties
   description	Description of the attachment
   href	Reference of the attachment

   © TM Forum 2015. All Rights Reserved