BusinessServiceLevelAgreement-v1.0-spec-wd04-wtc

1

SOA-EERP Business Service Level
3Agreement Version 1.0
2

4Working
5June

Draft 04

8, 2009

6Specification URIs:
7This Version:
8
/>eerp/spec/sla/BusinessServiceLevelAgreement-v1.0-spec-wd04.html
10
/>eerp/spec/sla/BusinessServiceLevelAgreement-v1.0-spec-wd04.doc
12
/>eerp/spec/sla/BusinessServiceLevelAgreement-v1.0-spec-wd04.pdf
14Previous Version:
15
/>eerp/spec/sla/BusinessServiceLevelAgreement-v1.0-spec-wd03.html
17
/>eerp/spec/sla/BusinessServiceLevelAgreement-v1.0-spec-wd03.doc
19
/>eerp/spec/sla/BusinessServiceLevelAgreement-v1.0-spec-wd03.pdf
21Latest Version:
22
soa-eerp/sla/v1.0/BusinessServiceLevelAgreement-Specification.html

23
soa-eerp/sla/v1.0/BusinessServiceLevelAgreement-Specification.doc
24
soa-eerp/sla/v1.0/BusinessServiceLevelAgreement-Specification.pdf
25Technical Committee:
26OASIS Service-Oriented Architecture End-to-End Resource Planning (SOA-EERP) TC
27
28Chair(s):
29
Bill Cox, Cox Software Architects LLC
30
Andy Lee, Changfeng Open Standards Platform Software Alliance
31Editor(s):
32
Szu Chang, Changfeng Open Standards Platform Software Alliance
33
34Related work:
35
This specification is related to:

36
37

38

39
40
41
42

•
•

SOA-EERP Business Rating of Service specification, Version 1, SOA-EERP-Rating-Specification.pdf
SOA-EERP Business Quality of Service, Version 1, soaeerp/bqos/v1.0/SOA-EERP-bQoS-Specification.pdf

This document is one of three closely related specifications, SOA-EERP Business Quality of
Service (bQoS), SOA-EERP Rating and SOA-EERP Service Level Agreement which need to be
understood in combination as a set.

1SOA-EERP-SLA-V1.0-WD04
2Copyright â OASISđ 2009. All Rights Reserved.

8 June, 2009
Page 1 of 31


43
44Declared XML Namespace(s):
45
/>46Abstract:
47
This document indicates the business service level agreement (SLA) which to be used in end-to48
end resource planning (EERP) for describing the SLA of the business services.
49Status:
50
This document is a Work in Progress only and has not been extensively reviewed.
51
Comment on this document is encouraged.
52

53
54
55

This document was last revised or approved by the SOA-EERP TC on the above date. The level
of approval is also listed above. Check the “Latest Version” or “Latest Approved Version” location
noted above for possible later revisions of this document.

56
57
58
59

Technical Committee members should send comments on this specification to the Technical
Committee’s email list. Others should send comments to the Technical Committee by using the
“Send A Comment” button on the Technical Committee’s web page at />
60
61
62
63

For information on whether any patents have been disclosed that may be essential to
implementing this specification, and any offers of patent licensing terms, please refer to the
Intellectual Property Rights section of the Technical Committee web page ( />
64
65

The non-normative errata page for this specification is located at />
4SOA-EERP-SLA-V1.0-WD04
5Copyright â OASISđ 2009. All Rights Reserved.

8 June, 2009
Page 2 of 31


66Notices
67Copyright â OASISđ 2009. All Rights Reserved.
68All capitalized terms in the following text have the meanings assigned to them in the OASIS Intellectual
69Property Rights Policy (the "OASIS IPR Policy"). The full Policy may be found at the OASIS website.
70This document and translations of it may be copied and furnished to others, and derivative works that
71comment on or otherwise explain it or assist in its implementation may be prepared, copied, published,
72and distributed, in whole or in part, without restriction of any kind, provided that the above copyright notice
73and this section are included on all such copies and derivative works. However, this document itself may
74not be modified in any way, including by removing the copyright notice or references to OASIS, except as
75needed for the purpose of developing any document or deliverable produced by an OASIS Technical
76Committee (in which case the rules applicable to copyrights, as set forth in the OASIS IPR Policy, must be
77followed) or as required to translate it into languages other than English.
78The limited permissions granted above are perpetual and will not be revoked by OASIS or its successors
79or assigns.
80This document and the information contained herein is provided on an "AS IS" basis and OASIS
81DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY
82WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY
83OWNERSHIP RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A
84PARTICULAR PURPOSE.
85OASIS requests that any OASIS Party or any other party that believes it has patent claims that would
86necessarily be infringed by implementations of this OASIS Committee Specification or OASIS Standard,
87to notify OASIS TC Administrator and provide an indication of its willingness to grant patent licenses to
88such patent claims in a manner consistent with the IPR Mode of the OASIS Technical Committee that
89produced this specification.
90OASIS invites any party to contact the OASIS TC Administrator if it is aware of a claim of ownership of

91any patent claims that would necessarily be infringed by implementations of this specification by a patent
92holder that is not willing to provide a license to such patent claims in a manner consistent with the IPR
93Mode of the OASIS Technical Committee that produced this specification. OASIS may include such
94claims on its website, but disclaims any obligation to do so.
95OASIS takes no position regarding the validity or scope of any intellectual property or other rights that
96might be claimed to pertain to the implementation or use of the technology described in this document or
97the extent to which any license under such rights might or might not be available; neither does it represent
98that it has made any effort to identify any such rights. Information on OASIS' procedures with respect to
99rights in any document or deliverable produced by an OASIS Technical Committee can be found on the
100OASIS website. Copies of claims of rights made available for publication and any assurances of licenses
101to be made available, or the result of an attempt made to obtain a general license or permission for the
102use of such proprietary rights by implementers or users of this OASIS Committee Specification or OASIS
103Standard, can be obtained from the OASIS TC Administrator. OASIS makes no representation that any
104information or list of intellectual property rights will at any time be complete, or that any claims in such list
105are, in fact, Essential Claims.
106The names "OASIS", [insert specific trademarked names and abbreviations here] are trademarks of
107OASIS, the owner and developer of this specification, and should be used only to refer to the organization
108and its official outputs. OASIS welcomes reference to, and implementation and use of, specifications,
109while reserving the right to enforce its marks against misleading uses. Please see for above guidance.
111

7SOA-EERP-SLA-V1.0-WD04
8Copyright â OASISđ 2009. All Rights Reserved.

8 June, 2009
Page 3 of 31


112Table

of Contents

1131 Introduction....................................................................................................................................................5
114 1.1 Namespaces...........................................................................................................................................5
115 1.2 Schema Files..........................................................................................................................................5
116 1.3 Terminology............................................................................................................................................5
117 1.4 Normative References...........................................................................................................................6
118
1.4.1 Notational Conventions..................................................................................................................6
119
1.4.2 Reference........................................................................................................................................6
120 1.5 Normative References...........................................................................................................................7
121 1.6 Non-Normative References...................................................................................................................7
1222 SLA Contents.................................................................................................................................................8
1233 SLA Parties..................................................................................................................................................10
1244 SLA Parameters...........................................................................................................................................12
1255 SLA Obligations...........................................................................................................................................14
126 5.1 Obligation.............................................................................................................................................15
127
5.1.1 Service Level Objective................................................................................................................15
128
5.1.2 Action Guarantee..........................................................................................................................20
129 5.2 ActionGuarantee...................................................................................................................................20
1306 SLA Terms....................................................................................................................................................23
1317 SLA Examples..............................................................................................................................................25
132 7.1 Committed Throughput with Penalty Example....................................................................................25
133 7.2 SLA without Obligation Example.........................................................................................................26
1348 Conformance...............................................................................................................................................28
135A. Acknowledgements....................................................................................................................................29
136B. Non-Normative Text....................................................................................................................................30

137C. Revision History.........................................................................................................................................31
138
139

10SOA-EERP-SLA-V1.0-WD04
11Copyright © OASIS® 2009. All Rights Reserved.

8 June, 2009
Page 4 of 31


1401

Introduction

141This document presents the specification for the Business Service Level Agreement for End-to-End
142Resource Planning, a protocol by which business application may present its SLA electronic documents
143for resource planning purposes. All text is normative unless otherwise indicated.

144
1451.1 Namespaces
146The XML namespace URI that MUST be used by implementations of this specification is:
147

/>
148
149Table 1 lists XML namespaces that are used in this specification. The choice of any namespace prefix is
150arbitrary and not semantically significant.
151Table 1: Prefixes and XML Namespaces used in this specification.

Prefix

Namespace

Specification(s)

S

/>
[SOAP]

S12

/>
[SOAP12]

xsd

/>
[XML-Schema1],
[XML-Schema2]

cbc

urn:oasis:names:specification:ubl:schema:xsd:CommonBasicComponents-2

[UBL-20]

udt

urn:un:unece:uncefact:data:specification:UnqualifiedDataTypesSchemaModule:2

[UBL-20]

ccts

urn:un:unece:uncefact:documentation:2

[UBL-20]

bqos

/>
[EERP-BQoS]

sla

/>
This
specification

1521.2 Schema Files
153A normative copy of the XML Schema [XML-Schema1, XML-Schema2] description for this specification
154can be retrieved from the following address:
155 />
156

1571.3 Terminology
158The key words “MUST”, “MUST NOT”, “REQUIRED”, “SHALL”, “SHALL NOT”, “SHOULD”, “SHOULD
159NOT”, “RECOMMENDED”, “MAY”, and “OPTIONAL” in this document are to be interpreted as described

160in [RFC2119].

13SOA-EERP-SLA-V1.0-WD04
14Copyright â OASISđ 2009. All Rights Reserved.

8 June, 2009
Page 5 of 31


1611.4 Normative References
162
163
164

[RFC2119]
[Reference]

S. Bradner, Key words for use in RFCs to Indicate Requirement Levels,
IETF RFC 2119, March 1997.
[Full reference citation]

165

1661.4.1 Notational Conventions
167The key words “MUST”, “MUST NOT”, “REQUIRED”, “SHALL”, “SHALL NOT”, “SHOULD”, “SHOULD
168NOT”, “RECOMMENDED”, “MAY”, and “OPTIONAL” in this document are to be interpreted as described
169in [RFC2119].
170This specification uses the following syntax to define outlines for detailed elements:

171

•

The syntax appears as an XML instance, but values in italics indicate data types instead of literal
values.

•

Characters are appended to elements and attributes to indicate cardinality:

172

173
174
175
176
177
178

o

"*" (0 or more)

o

"+" (1 or more)

The character "|" is used to indicate a choice between alternatives.

•

The characters "(" and ")" are used to indicate that contained items are to be treated as a group
with respect to cardinality or choice.

•

The characters "[" and "]" are used to call out references and property names.

•

Ellipses (i.e., "...") indicate points of extensibility. Additional children and/or attributes MAY be
added at the indicated extension points but MUST NOT contradict the semantics of the parent
and/or owner, respectively. By default, if a receiver does not recognize an extension, the receiver
SHOULD ignore the extension; exceptions to this processing rule, if any, are clearly indicated
below.

•

XML namespace prefixes (see Table 2) are used to indicate the namespace of the element being
defined.

182
183
184
185

186

"?" (0 or 1)

•

179

180
181

o

187

188
189Elements and Attributes defined by this specification are referred to in the text of this document using
190XPath 1.0 expressions. Extensibility points are referred to using an extended version of this syntax:

191

•

An element extensibility point is referred to using {any} in place of the element name. This
indicates that any element name can be used, from any namespace other than the namespace of
this specification.

•

An attribute extensibility point is referred to using @{any} in place of the attribute name. This
indicates that any attribute name can be used, from any namespace other than the namespace of
this specification.

192

193

194
195
196

197Extensibility points in the exemplar may not be described in the corresponding text.
198

1991.4.2 Reference
200In this document reference is made to some basic elements and data types in UBL 2.0, in the following
201schema:
202
• UBL 2.0 Common Basic Components (UBL-CommonBasicComponents-2.0.xsd)
203
• UBL 2.0 Unqualified Data Type (UnqualifiedDataTypeSchemaModule-2.0.xsd)
16SOA-EERP-SLA-V1.0-WD04
17Copyright â OASISđ 2009. All Rights Reserved.

8 June, 2009
Page 6 of 31


204
205In addition, this document also reference to some elements defined in SOA-EERP Business Quality of
206Service Version 1.0.
207
208
209This standard is designed to work with the general Web Services framework including WSDL service
210descriptions, and SOAP message structure and message processing model, and bQoS should be

211applicable to any version of SOAP. The current SOAP 1.2 namespace URI is used herein to provide
212detailed examples, but there is no intention to limit the applicability of this specification to a single version
213of SOAP.
214

2151.5 Normative References
216[RFC2119]
217

S. Bradner, "Key words for use in RFCs to Indicate Requirement
Levels", RFC 2119, Harvard University, March 1997.

218

/>
219
220[URI]
221
222

T. Berners-Lee, R. Fielding, L. Masinter, "Uniform Resource Identifiers
(URI): Generic Syntax", RFC 3986, MIT/LCS, Day Software, Adobe
Systems, January 2005.

223

/>
224

225[UBL-20]

226

OASIS Standard, “Universal Business Language (UBL) v2.0”, 12
December 2006

227

/>
228
229[XML-Schema1]
230

W3C Recommendation, "XML Schema Part 1: Structures Second
Edition", 28 October 2004.

231

/>
232
233[XML-Schema2]
234

W3C Recommendation, "XML Schema Part 2: Datatypes Second
Edition", 28 October 2004.

235

/>
236
237[EERP-BQoS]

238

OASIS Standard (Draft), “SOA-EERP Business Quality of Service
Version 1.0”

239
240

/>
2411.6 Non-Normative References
242None.
243

19SOA-EERP-SLA-V1.0-WD04
20Copyright â OASISđ 2009. All Rights Reserved.

8 June, 2009
Page 7 of 31


2442

SLA Contents

245The BSLA is the root element for EERP- Service-level agreement (SLA). Business SLA is a formal
246contract between a service provider and a client guaranteeing quantifiable business quality of service
247(bQoS) at defined levels. It can have one or more of the following elements:
248
249
• SLAParties is for the SLA aspect of service which is measured in terms ofdescribes the parties

250
invoked in the SLA for the service
251
• SLAParameters is for the SLA aspect of service which is measured in terms ofdescribes the
252
parameters for the service, which are defined ways of monitoring of QoS metrics.
253
• SLAObligations is for the SLA aspect of service which is measured in terms ofdescribes the
254
agreed SLA obligations for the service.
255
• SLATerms is for the SLA aspect of service which is measured in terms of describes the agreed
256
SLA Terms for the service.
257
• Any additional elements for the rating aspect of service
258
259Syntax
260
261
262
263
264
265
266

<sla:BSLA xmlns:sla="..." xmlns:bqos="..." ...>
<sla:SLAParties ...>sla:SLAPartiesTypeType</sla:SLAParties>
<sla:SLAParameters ...>sla:SLAParametersType</sla:SLAParameters>
<sla:SLAObligations ...>sla:SLAObligationsType</sla:SLAObligations> ?

<sla:SLATerms ...>sla:SLATermsType</sla:SLATerms> ?
...
</sla:BSLA>

267
268The following describes the attributes and elements listed in the schema outlined above:
269/sla:BSLA
270
Root element of Business Service-level agreement (SLA) for EERP
271/sla:BSLA/sla:SLAParties
272
SLAParties is a required element in BSLA that defines parties invoked in this SLA for the service.
273
SLAParties element has both the service provider and services requester elements, see Section
274
3 for more details.
275/sla:BSLA/sla:SLAParties/@{any}
276
277

This is an extensibility mechanism to allow additional attributes, based on schemas, to be added
to the SLAParties element in the future. Unrecognized attributes SHOULD cause a fault.

278/sla:BSLA/sla:SLAParameters
279
SLAParameters element, SLA parameters aspect of the service, are defined monitoring of
280
QoS metrics, including service profile uri, operations and other optional elements. It is a required
281
element that uses sla:SLAParametersType, see Section 4 for more details.

282/sla:BSLA/sla:SLAParameters/@{any}
283
284

This is an extensibility mechanism to allow additional attributes, based on schemas, to be added
to the SLAParameters element in the future. Unrecognized attributes SHOULD cause a fault.

285/sla:BSLA/sla:SLAObligations
22SOA-EERP-SLA-V1.0-WD04
23Copyright â OASISđ 2009. All Rights Reserved.

8 June, 2009
Page 8 of 31


286
287

Agreed SLA obligations aspect of the service, including obligations, action guarantees. It is a
optional element that uses sla:SLAObligationsType, see Section 5 for more details.

288/sla:BSLA/sla:SLAObligations/@{any}
289
290

This is an extensibility mechanism to allow additional attributes, based on schemas, to be added
to the SLAObligations element in the future. Unrecognized attributes SHOULD cause a fault.

291/sla:BSLA/sla:SLATerms
292

Agreed SLA terms aspect of the service, including SLA term elements. It is optional, see
293
Section 6 for more details.
294/sla:BSLA/sla:SLATerms/@{any}
295
296

This is an extensibility mechanism to allow additional attributes, based on schemas, to be added
to the SLATerms element in the future. Unrecognized attributes SHOULD cause a fault.

297/sla:BSLA/@{any}
298
299

This is an extensibility mechanism to allow additional attributes, based on schemas, to be added
to the root BSLA element in the future. Unrecognized attributes SHOULD cause a fault.

300/sla:BSLA/{any}
301
302

This is an extensibility mechanism to allow different (extensible) elements/parameters to be
specified in the future. Unrecognized parameters SHOULD cause a fault.

303

25SOA-EERP-SLA-V1.0-WD04
26Copyright â OASISđ 2009. All Rights Reserved.

8 June, 2009

Page 9 of 31


3043

SLA Parties

305The SLAParties, the Parties element for BSLA, defines the describes the list of parties invoked in the
306SLA for the service.
307
308There SHOULD be one SLAParties element present in the SLA of service.
309
310Syntax
311
312
313
314
315
316
317
318
319
320
321
322
323

<sla:SLAParties xmlns:sla="..." ...>
<sla:ServiceProvider ...>sla:ServiceProviderType
<sla:ServiceUri ...>sla:SlaUriType</sla:ServiceUri>

languageID="...">sla:ServiceProviderNameType</sla:ServiceProviderName>
</sla:ServiceProvider>
<sla:ServiceRequester ... >sla:ServiceRequesterType
<sla:ServiceRequesterUri ... >sla:SlaUriType</sla:ServiceRequesterUri>
languageID="...">sla:ServiceRequesterNameType</sla:ServiceRequesterName>
</sla:ServiceRequester>
...
</sla:SLAParties>

324
325The following describes the attributes and elements listed in the schema outlined above:
326/sla:SLAParties
327
SLAParties element, SLA Parties aspect of the service, is for parties invoked in the SLA for the
328
service, including both service provider and service requester elements.
329/sla:SLAParties/sla:ServiceProvider
330
Service Provider element represents the provider for parties. It is a required element for SLA
331
Parties.
332/sla:SLAParties/sla:ServiceProvider/sla:ServiceUri
333
Service identifier in URI format, such as a service URL, is a required element for Service
334
Provider.
335/sla:SLAParties/sla:ServiceProvider/sla:ServiceProviderName
336

Service Provider Name is the name of the service provider. It is also a required element for
337
Service Provider.
338/sla:SLAParties/sla:ServiceProvider/sla:ServiceProviderName/@languageID
339
Language ID is an optional attribute in the ServiceProviderName element, using xsd:language
340
type. The value can be those defined in urn:un:unece:uncefact:codelist:specification:5639:1988.
341/sla:SLAParties/sla:ServiceProvider/@{any}
342
343

This is an extensibility mechanism to allow additional attributes, based on schemas, to be added
to the ServiceProvider element in the future. Unrecognized attributes SHOULD cause a fault.

344/sla:SLAParties/sla:ServiceRequester
345
Requester for the service, including requester’s name and the identifier (ID) that represents the
346
requester. It is a required element for SLA Parties.
28SOA-EERP-SLA-V1.0-WD04
29Copyright â OASISđ 2009. All Rights Reserved.

8 June, 2009
Page 10 of 31


347/sla:SLAParties/sla:ServiceRequester/sla:ServiceRequesterUri
348
Requester’s identifier (ID) for the service requester. It is a required element for Service

349
Requester.
350/sla:SLAParties/sla:ServiceRequester/sla:ServiceRequesterName
351
Requester’s name for the service requester. It is a required element for Service Requester.
352/sla:SLAParties/sla:ServiceRequester/sla:ServiceRequesterName/@languageID
353
Language ID is an optional attribute in the ServiceRequesterName element, using
354
xsd:language type. The value can be those defined in
355
urn:un:unece:uncefact:codelist:specification:5639:1988.
356/sla:SLAParties/sla:ServiceRequester/@{any}
357
358

This is an extensibility mechanism to allow additional attributes, based on schemas, to be added
to the ServiceRequester element in the future. Unrecognized attributes SHOULD cause a fault.

359/sla:SLAParties/{any}
360
361

This is an extensibility mechanism to allow different (extensible) elements/parameters to be
specified in the future. Unrecognized parameters SHOULD cause a fault.

362
363Example
364
365The following example illustrates the use of the SLA Parties element. It describes a SLA Parties. The

366Service Provider is Hangzhou Innover Co. Ltd. from Zhejiang Province. in P. R. China. ; the Service
367Requester is Mianyang Gas Corp. from Sichuan Province. in P. R. China.:
368
369
370
371
372
373
374
375
376
377
378
379

(001) <?xml version="1.0" encoding="utf-8"?>
(002) <SLAParties xmlns="..." ...>
(003)
<ServiceProvider>
(004)
<ServiceUri></ServiceUri>
(005)
<ServiceProviderName>Hangzhou Innover Co. Ltd</ServiceProviderName>
(006)
</ServiceProvider>
(007)
<ServiceRequester>
(008)
<ServiceRequesterUri></ServiceRequesterUri>
(009)

<ServiceRequesterName>Mianyang Gas Corp.</ServiceRequesterName>
(010)
</ServiceRequester>
(011) </SLAParties>

380

31SOA-EERP-SLA-V1.0-WD04
32Copyright â OASISđ 2009. All Rights Reserved.

8 June, 2009
Page 11 of 31


3814

SLA Parameters

382The SLA Parameters, Parameters element for EERP-SLA, is the SLAdescribes the parameters
383aspect of the service which isused to define defined monitoring of QoS metrics, including the service
384profile uriURI, operations and other optional elements.
385
386There SHOULD be one SLAParameters element present in the SLA of service.
387
388Syntax
389
390
391
392
393

394
395
396
397
398
399
400

<sla:SLAParameters xmlns:sla="..." ...>
<sla:ServiceProfileUri ...>sla:SlaUriType</sla:ServiceProfileUri>
<sla:ServiceOperations ...>sla:ServiceOperationsType
<sla:hasCommittedCost>xsd:boolean</sla:hasCommittedCost>
<sla:hasCommittedTime>xsd:boolean</sla:hasCommittedTime>
<sla:hasAvailabilities>xsd:boolean</sla:hasAvailabilities>
<sla:hasCommittedTroughput>xsd:boolean</sla:hasCommittedTroughput>
<sla:hasOtherTerms>xsd:boolean</sla:hasOtherTerms>
...
</sla:ServiceOperations> ?
...
</sla:SLAParameters>

401
402The following describes the attributes and elements listed in the schema outlined above:
403/sla:SLAParameters
404
SLA parameters aspect of the service which are defined monitoring of QoS metrics, including
405
service uri, operations and other optional elements.
406/sla:SLAParameters/sla:ServiceProfileUri
407

Service Profile Uri element represents web page url or other uri for the service profile It is a
408
required element for SLA Parameters.
409/sla:SLAParameters/sla:ServiceProfileUri/@{any}
410
411

This is an extensibility mechanism to allow additional attributes, based on schemas, to be added
to the ServiceProfileUri element in the future. Unrecognized attributes SHOULD cause a fault.

412/sla:SLAParameters/sla:ServiceOperations
413
Describe available operations and bQoS. It is a optional element for SLA Parameters.
414/sla:SLAParameters/sla:ServiceOperations/sla:hasCommittedCost
415
Describe if there is committed cost or not. It is a required element for SLA Parameters.
416/sla:SLAParameters/sla:ServiceOperations/sla:hasCommittedTime
417
Describe if there is committed time or not. It is a required element for SLA Parameters.
418/sla:SLAParameters/sla:ServiceOperations/sla:hasAvailabilities
419
Describe if there is availability or not. It is a required element for SLA Parameters.
420/sla:SLAParameters/sla:ServiceOperations/sla:hasCommittedTroughput
421
Describe if there is committed troughput or not. It is a required element for SLA Parameters.
422/sla:SLAParameters/sla:ServiceOperations/sla:hasOtherTerms
34SOA-EERP-SLA-V1.0-WD04
35Copyright © OASIS® 2009. All Rights Reserved.

8 June, 2009

Page 12 of 31


423
Describe if there are other terms or not. It is a required element for SLA Parameters.
424/sla:SLAParameters/sla:ServiceOperations/{any}
425
426
427

This is an extensibility mechanism to allow different (extensible) property or attribute
elements/parameters to be specified in the future. Unrecognized parameters SHOULD cause a
fault.

428/sla:SLAParameters /sla:ServiceOperations/@{any}
429
430

This is an extensibility mechanism to allow additional attributes, based on schemas, to be added
to the ServiceOperations element in the future. Unrecognized attributes SHOULD cause a fault.

431/sla:SLAParameters /{any}
432
433
434

This is an extensibility mechanism to allow different (extensible) property or attribute
elements/parameters to be specified in the future. Unrecognized parameters SHOULD cause a
fault.

435
436Example
437
438The following example illustrates the use of SLA Parameters element. It describes the SLA parameters:
439
440
441
442
443
444
445
446
447
448
449
450

(001) <?xml version="1.0" encoding="utf-8"?>
(002) <SLAParameters xmlns="..." ...>
(003)
<ServiceProfileUri></ServiceProfileUri>
(004)
<ServiceOperations>
(005)
<hasCommittedCost>true</hasCommittedCost>
(006)
<hasCommittedTime>true</hasCommittedTime>
(007)
<hasAvailabilities>true</hasAvailabilities>
(008)

<hasCommittedTroughput>true</hasCommittedTroughput>
(009)
<hasOtherTerms>true</hasOtherTerms>
(010)
</ServiceOperations>
(011) </SLAParameters>

451

37SOA-EERP-SLA-V1.0-WD04
38Copyright © OASIS® 2009. All Rights Reserved.

8 June, 2009
Page 13 of 31


4525

SLA Obligations

453The SLA Obligations, Obligations element for EERP-SLA,describes is the agreed SLA obligations
454aspect of the service, including obligations, and action guarantees.
455
456There MAY be zero or one SLA Obligations element present in the SLA of service.
457
458Note: There is a case for zero Obligation element on SLA. Section 7.2 is an example illustrates the SLA
459document without Obligation element. It has some additional SAL terms instead.
460
461Syntax
462

463
464
465
466

<sla:SLAObligations xmlns:sla="..." xmlns:bqos="..." ...>
<sla:Obligation ...>sla:ObligationType</sla:Obligation> +
<sla:ActionGuarantee ...>sla:ActionGuaranteeType</sla:ActionGuarantee> ?
...
</sla:SLAObligations>

467
468The following describes the attributes and elements listed in the schema outlined above:
469/sla:SLAObligations
470
SLA obligations aspect of the service, including obligations, action guarantees.
471/sla:SLAObligations/sla:Obligation
472
Agreed SLA obligation, including Service Level Objective (SLO) and the Action Guarantee that
473
associates with that SLO. There MAY be one or more obligation elements in the SLAObligations
474
element. see Section 5.1 for more details.
475/sla:SLAObligations/sla:Obligation/@{any}
476
477

This is an extensibility mechanism to allow additional attributes, based on schemas, to be added
to the Obligation element in the future. Unrecognized attributes SHOULD cause a fault.

478/sla:SLAObligations/sla:ActionGuarantee
479
Specify what happens if the Service Level Objective (SLO) is met or not met. This guarantee will
480
be associated to all Obligations within the SLAObligations element. It is an optional element for
481
the SLAObligations element. See Section 5.2 for more details.
482/sla:SLAObligations/sla:ActionGuarantee/@{any}
483
484

This is an extensibility mechanism to allow additional attributes, based on schemas, to be added
to the ActionGuarantee element in the future. Unrecognized attributes SHOULD cause a fault.

485/sla:SLAObligations/{any}
486
487
488

This is an extensibility mechanism to allow different (extensible) property or attribute
elements/parameters to be specified in the future. Unrecognized parameters SHOULD cause a
fault.

489

40SOA-EERP-SLA-V1.0-WD04
41Copyright â OASISđ 2009. All Rights Reserved.

8 June, 2009
Page 14 of 31

4905.1 Obligation
491The Obligation, obligation element for SLA Obligations in EERP-SLA, is the agreed SLA obligation,
492including Service Level Objective (SLO) and the Action Guarantee that associates with that SLO.
493
494There MAY be one or more Obligation elements present in the SLA Obligations.
495
496
497Syntax
498
499
500
501
502

<sla:Obligation xmlns:sla="..." xmlns:bqos="..." ...>
<sla:ServiceLevelObjective ...>sla:ServiceLevelObjectiveType
</sla:ServiceLevelObjective>
<sla:ActionGuarantee ...>sla:ActionGuaranteeType</sla:ActionGuarantee> ?
</sla:Obligation>

503
504The following describes the attributes and elements listed in the schema outlined above:
505/sla:SLAObligations/sla:Obligation
506
Agreed SLA obligation, including Service Level Objective (SLO) and the Action Guarantee that
507
associates with this Obligation.
508/sla:SLAObligations/sla:Obligation/sla:ServiceLevelObjective

509
Service Level Objective (SLO) for QoS guarantee. It is a required element for Obligation. see
510
Section 5.1.1 for more details.
511/sla:SLAObligations/sla:Obligation/sla:ServiceLevelObjective/@{any}
512
513
514

This is an extensibility mechanism to allow additional attributes, based on schemas, to be added
to the ServiceLevelObjective element in the future. Unrecognized attributes SHOULD cause a
fault.

515/sla:SLAObligations/sla:Obligation/sla:ActionGuarantee
516
Service Level Objective (SLO) for QoS guarantee. This guarantee will be associated to all
517
ServiceLevelObjective within this Obligation element. It is an optional element for Obligation. see
518
Section 5.1.2 for more details.
519/sla:SLAObligations/sla:Obligation/sla:ActionGuarantee/@{any}
520
521

This is an extensibility mechanism to allow additional attributes, based on schemas, to be added
to the ActionGuarantee element in the future. Unrecognized attributes SHOULD cause a fault.

522

5235.1.1 Service Level Objective

524The Service Level Objective, service level objective element for Obligation in SLA Obligations in
525EERP-SLA, is the Service Level Objective (SLO) for the QoS guarantee, including Committed Cost,
526Committed Time, Availabilities, Committed Throughput and SLATerm.
527
528There SHOULD be one Service Level Objective element present in the Obligation, and it can have
529one and more element within this Service Level Objective element.
530
531Syntax
43SOA-EERP-SLA-V1.0-WD04
44Copyright © OASIS® 2009. All Rights Reserved.

8 June, 2009
Page 15 of 31


532
533
534
535
536
537
538
539
540

<sla:ServiceLevelObjective xmlns:sla="..." xmlns:bqos="..." ...>
<sla:CommittedCost>bqos:PriceType</sla:CommittedCost> ?
<sla:CommittedTime ...>sla:CommittedTimeType</sla:CommittedTime> ?
<sla:Availabilities ...>sla:AvailabilitiesType</sla:Availabilities> ?
<sla:CommittedThroughput ...>bqos:ThroughputType</sla:CommittedThroughput>

?
<sla:SLATerm ...>sla:SLATermType</sla:SLATerm> ?
</sla:ServiceLevelObjective>

541

542The following describes the attributes and elements listed in the schema outlined above:
543/sla:SLAObligations/sla:Obligation/sla:ServiceLevelObjective
544
Service Level Objective (SLO) for QoS guarantee. It is a required element for Obligation.
545/sla:SLAObligations/sla:Obligation/sla:ServiceLevelObjective/sla:CommittedCost
546
Cost element in SLA. It is an optional element for ServiceLevelObjective. See Section 5.1.1.1 for
547
more details.
548/sla:SLAObligations/sla:Obligation/sla:ServiceLevelObjective/sla:CommittedTime
549
Committed time period element in SLA is an optional element for ServiceLevelObjective. see
550
Section 5.1.1.2 for more details.
551/sla:SLAObligations/sla:Obligation/sla:ServiceLevelObjective/sla:CommittedTime/@{any}
552
553

This is an extensibility mechanism to allow additional attributes, based on schemas, to be added
to the CommittedTime element in the future. Unrecognized attributes SHOULD cause a fault.

554/sla:SLAObligations/sla:Obligation/sla:ServiceLevelObjective/sla:Availabilities
555
The services availability indicators element, including a list of availabilities, is an optional element

556
for ServiceLevelObjective, see Section 5.1.1.3 for more details.
557/sla:SLAObligations/sla:Obligation/sla:ServiceLevelObjective/sla:Availabilities/@{any}
558
559

This is an extensibility mechanism to allow additional attributes, based on schemas, to be added
to the Availabilities element in the future. Unrecognized attributes SHOULD cause a fault.

560/sla:SLAObligations/sla:Obligation/sla:ServiceLevelObjective/sla:CommittedThroughput
561
Committed performance throughput is an optional element for ServiceLevelObjective. see Section
562
5.1.1.4 for more details.
563/sla:SLAObligations/sla:Obligation/sla:ServiceLevelObjective/sla:CommittedThroughput/@{any}
564
565
566

This is an extensibility mechanism to allow additional attributes, based on schemas, to be added
to the CommittedThroughput element in the future. Unrecognized attributes SHOULD cause a
fault.

567/sla:SLAObligations/sla:Obligation/sla:ServiceLevelObjective/sla:SLATerm
568
SLA Term. It is an optional element for ServiceLevelObjective, see /sla:SLATerms/sla:SLATerm in
569
Section 6 for more details.
570/sla:SLAObligations/sla:Obligation/sla:ServiceLevelObjective/sla:SLATerm /@{any}
571

572

This is an extensibility mechanism to allow additional attributes, based on schemas, to be added
to the SLATerm element in the future. Unrecognized attributes SHOULD cause a fault.

573

5745.1.1.1 Committed Cost
575The Committed Cost, Cost element of Service Level Objective for Obligation in SLA Obligations in
576EERP-SLA, isdescribes the cost element in SLA, including Unit and Amount.
46SOA-EERP-SLA-V1.0-WD04
47Copyright â OASISđ 2009. All Rights Reserved.

8 June, 2009
Page 16 of 31


577
578There MAY be zero or one Committed Cost element present in the Service Level Objective.
579
580Syntax
581
582
583
584
585
586

<sla:CommittedCost xmlns:sla="..." xmlns:bqos="...">
<bqos:Unit unitCode="clm66411:UnitCodeContentType">

cbc:BaseUnitMeasureType </bqos:Unit> ?
<bqos:Amount currencyID="clm54217:CurrencyCodeContentType">
cbc:AmountType </bqos:Amount>
</sla:CommittedCost>

587

588The following describes the attributes and elements listed in the schema outlined above:
589/sla:SLAObligations/sla:Obligation/sla:ServiceLevelObjective/sla:CommittedCost
590
CommittedCost element is the cost element in SLA. It is an optional element for Service Level
591
Objective.
592/sla:SLAObligations/sla:Obligation/sla:ServiceLevelObjective/sla:CommittedCost/bqos:Unit
593
Number of unit is a optional element that includes a attribute of unit of measurement uses
594
cbc:BaseUnitMeasureType. See /bqos:BQoSPrice/bqos:Price/bqos:Unit in Section 3: BQoS
595
Price in EERP-bQoS Specification for more details.
596/sla:SLAObligations/sla:Obligation/sla:ServiceLevelObjective/sla:CommittedCost/bqos:Amount
597
Amount element is a required element for the Committed Cost element. It uses cbc:AmountType
598
from UBL that has a required currencyID attribute for currency code. See
599
/bqos:BQoSPrice/bqos:Price/bqos:Amount in Section 3: BQoS Price in EERP-bQoS
600
Specification for more details.
601

6025.1.1.2 Committed Time
603The Committed Time, Committed Time element of Service Level Objective for Obligation in SLA
604Obligations in EERP-SLA, is the committed time period in SLA, including Duration, Latency and
605Committed Completion Time.
606
607There MAY be zero or one Committed Time element present in the Service Level Objective.
608

609Syntax
610
611
612
613
614
615
616
617
618

<sla:CommittedTime xmlns:sla="..." xmlns:bqos="..." ...>
<bqos:Duration unitCode="clm66411:UnitCodeContentType">
cbc:DurationMeasureType </bqos:Duration>
<bqos:Latency unitCode="clm66411:UnitCodeContentType">
cbc:DurationMeasureType </bqos:Latency> ?
<bqos:StartTime>udt:DateTimeType</bqos:StartTime> ?
<sla:CommittedCompletionTime>
udt:DateTimeType</sla:CommittedCompletionTime> ?
</sla:CommittedTime>

619
620The following describes the attributes and elements listed in the schema outlined above:

621/sla:SLAObligations/sla:Obligation/sla:ServiceLevelObjective/sla:CommittedTime
49SOA-EERP-SLA-V1.0-WD04
50Copyright â OASISđ 2009. All Rights Reserved.

8 June, 2009
Page 17 of 31


622
CommittedTime element is an optional element for Service Level Objective which is the
623
committed time period element in SLA.
624/sla:SLAObligations/sla:Obligation/sla:ServiceLevelObjective/sla:CommittedTime/bqos:Duration
625
Duration element is a required element in the CommittedTime element which is the duration to
626
complete the service. It uses cbc:DurationMeasureType from UBL that has a required unitCode
627
attribute for unit of measurement on the time. See
628
/bqos:BQoSPerformance/bqos:TimePeriod/bqos:Duration in Section 4: BQoS Performance in
629
EERP-bQoS Specification for more details.
630/sla:SLAObligations/sla:Obligation/sla:ServiceLevelObjective/sla:CommittedTime/bqos:Latency
631
Latency is an optional element for the time delay for starting the service. It uses
632

cbc:DurationMeasureType from UBL that has a required unitCode attribute for unit of
633
measurement on the time. See /bqos:BQoSPerformance/bqos:TimePeriod/bqos:Latency in
634
Section 4: BQoS Performance in EERP-bQoS Specification for more details.
635/sla:SLAObligations/sla:Obligation/sla:ServiceLevelObjective/sla:CommittedTime/bqos:StartTime
636
StartTime is an optional element for the date and time to start the service. It uses
637
udt:DateTimeType which is in Zulu time format. See
638
/bqos:BQoSPerformance/bqos:TimePeriod/bqos:StartTime in Section 4: BQoS Performance in
639
EERP-bQoS Specification for more details.
640/
641sla:SLAObligations/sla:Obligation/sla:ServiceLevelObjective/sla:CommittedTime/sla:CommittedCompletio
642nTime
CommittedCompletionTime is an optional element for the date and time for committed completion
time. It uses udt:DateTimeType which is in Zulu time format.

643
644
645

6465.1.1.3 Availabilities
647The Availabilities, Availabilities of Service Level Objective for Obligation in SLA Obligations in
648EERP-SLA, is services availability indicators including a list of availabilities, including a list of Availability
649elements.
650
651There MAY be zero or one Availabilities element present in the Service Level Objective.

652
653Syntax
654
655
656
657
658
659

<sla:Availabilities xmlns:sla="..." xmlns:bqos="..." ...>
<sla:Availability isAvailable="xs:boolean" ...>sla:AvailabilityType
<sla:From>xs:dateTime</sla:From>
<sla:To>xs:dateTime</sla:To>
</sla:Availability> +
</sla:Availabilities>

660
661The following describes the attributes and elements listed in the schema outlined above:

662/sla:SLAObligations/sla:Obligation/sla:ServiceLevelObjective/sla:Availabilities
663
Availabilities is an optional element for Service Level Objective which is the services availability
664
indicators including a list of availabilities.
665/sla:SLAObligations/sla:Obligation/sla:ServiceLevelObjective/sla:Availabilities/sla:Availability
52SOA-EERP-SLA-V1.0-WD04
53Copyright â OASISđ 2009. All Rights Reserved.

8 June, 2009
Page 18 of 31

Availability is a required element for the quality aspect of whether the service is present or ready
for immediate use.

666
667

668/sla:SLAObligations/sla:Obligation/sla:ServiceLevelObjective/sla:Availabilities/sla:Availability/sla:From
From is a required element for the date and time for availability starting time. It uses
udt:DateTimeType which is in Zulu time format.

669
670

671/sla:SLAObligations/sla:Obligation/sla:ServiceLevelObjective/sla:Availabilities/sla:Availability/sla:To
To is a required element for the date and time for availability ending time. It uses
udt:DateTimeType which is in Zulu time format.

672
673

674/sla:SLAObligations/sla:Obligation/sla:ServiceLevelObjective/sla:Availabilities/sla:Availability/@isAvailable
isAvailable is an optional attribute to illustrate whether the Availability is available or not. It uses
xs:boolean type.

675
676

677/sla:SLAObligations/sla:Obligation/sla:ServiceLevelObjective/sla:Availabilities/sla:Availability/@{any}

This is an extensibility mechanism to allow additional attributes, based on schemas, to be added
to the Availability element in the future. Unrecognized attributes SHOULD cause a fault.

678
679
680

6815.1.1.4 Committed Throughput
682The Committed Throughput, Committed Throughput element of Service Level Objective for
683Obligation in SLA Obligations in EERP-SLA, is the committed performance throughput, including
684Duration, Quantity and Latency.
685
686There MAY be zero or one Committed Throughput element present in the Service Level Objective.
687

688Syntax
689
690
691
692
693
694
695
696

<sla:CommittedThroughput xmlns:sla="..." xmlns:bqos="..." ...>
<bqos:Duration unitCode="clm66411:UnitCodeContentType">
cbc:DurationMeasureType</bqos:Duration>
<bqos:Quantity unitCode="clm66411:UnitCodeContentType">
cbc:BaseQuantityType</bqos:Quantity>

<bqos:Latency unitCode="clm66411:UnitCodeContentType">
cbc:DurationMeasureType</bqos:Latency> ?
</sla:CommittedThroughput>

697

698The following describes the attributes and elements listed in the schema outlined above:
699/sla:SLAObligations/sla:Obligation/sla:ServiceLevelObjective/sla:CommittedThroughput
700
CommittedThroughput is an optional element for ServiceLevelObjective element. This is the
701
committed performance throughput.
702/sla:SLAObligations/sla:Obligation/sla:ServiceLevelObjective/sla:CommittedThroughput/bqos:Duration
703
Duration element is a required element in the CommittedThroughput element. This is the
704
duration to complete the service. It uses cbc:DurationMeasureType from UBL that has a required
705
unitCode attribute for unit of measurement on the time. See
706
/bqos:BQoSPerformance/bqos:Throughput/bqos:Duration in Section 4: BQoS Performance in
707
EERP-bQoS Specification for more details.
708/sla:SLAObligations/sla:Obligation/sla:ServiceLevelObjective/sla:CommittedThroughput/bqos:Quantity
709
Quantity is a required element in the Throughput element. It is the numbers for the throughput,
710
with an attribute of unit of measurement, such as EA, pounds, cubic-feet, etc. See
55SOA-EERP-SLA-V1.0-WD04
56Copyright â OASISđ 2009. All Rights Reserved.

8 June, 2009
Page 19 of 31


711
/bqos:BQoSPerformance/bqos:Throughput/bqos:Quantity in Section 4: BQoS Performance in
712
EERP-bQoS Specification for more details.
713/sla:SLAObligations/sla:Obligation/sla:ServiceLevelObjective/sla:CommittedThroughput/bqos:Latency
714
Latency is an optional element for the time delay for starting the service. It uses
715
cbc:DurationMeasureType from UBL that has a required unitCode attribute for unit of
716
measurement on the time. See /bqos:BQoSPerformance/bqos:Throughput/bqos:Latency in
717
Section 4: BQoS Performance in EERP-bQoS Specification for more details.
718

7195.1.1.5 SLA Term
720The SLA Term, SLA Term element of Service Level Objective for Obligation in SLA Obligations in
721EERP-SLA, is the SLA term element in SLA.
722
723There MAY be zero or one SLA Term element present in the Service Level Objective.
724
725see /sla:SLATerms/sla:SLATerm in Section 6 for more details.
726
7275.1.2 Action Guarantee
728The Action Guarantee, action guarantee element for SLA Obligations in EERP-SLA, is to specify

729what happens if the SLO is met or not met, including Reserve Fee and Penalty element.
730
731There MAY be zero or one Action Guarantee element present in the Obligation element. See Section
7325.2 for the detail of ActionGuaranteeType.
733

7345.2 ActionGuarantee
735The Action Guarantee, action guarantee element for SLA Obligations in EERP-SLA, is to specify
736what happens if the Service Level Objective (SLO) is met or not met, including Reserve Fee and
737Penalty element.
738
739There MAY be zero or one SLA Obligations element present in the SLA Obligations.
740
741Syntax
742
743
744
745
746
747
748
749
750
751
752
753
754

<sla:ActionGuarantee xmlns:sla="..." xmlns:bqos="..." ...>
<sla:ReserveFee ...>bqos:PriceType

<bqos:Unit unitCode="clm66411:UnitCodeContentType">
cbc:BaseUnitMeasureType</bqos:Unit> ?
<bqos:Amount currencyID="clm54217:CurrencyCodeContentType">
cbc:AmountType</bqos:Amount>
</sla:ReserveFee> ?
<sla:Penalty ...>bqos:PriceType
<bqos:Unit unitCode="clm66411:UnitCodeContentType">
cbc:BaseUnitMeasureType</bqos:Unit> ?
<bqos:Amount currencyID="clm54217:CurrencyCodeContentType">
cbc:AmountType</bqos:Amount>
</sla:Penalty> ?

58SOA-EERP-SLA-V1.0-WD04
59Copyright â OASISđ 2009. All Rights Reserved.

8 June, 2009
Page 20 of 31


755

</sla:ActionGuarantee >

756
757The following describes the attributes and elements listed in the schema outlined above:
758/sla:SLAObligations/sla:ActionGuarantee/sla:ReserveFee
759
760

ReserveFee element is the reservation fee or money amount when Service Level Objective

(SLO) is met. It is an optional element for Action Guarantee.

761/sla:SLAObligations/sla:ActionGuarantee/sla:ReserveFee/bqos:Unit
762
Number of unit is a optional element that includes a attribute of unit of measurement uses
763
cbc:BaseUnitMeasureType. See /bqos:BQoSPrice/bqos:Price/bqos:Unit in Section 3: BQoS
764
Price in EERP-bQoS Specification for more details.
765/sla:SLAObligations/sla:ActionGuarantee/sla:ReserveFee/bqos:Amount
766
Amount element is a required element for the Reserve Fee element. It uses cbc:AmountType
767
from UBL that has a required currencyID attribute for currency code. See
768
/bqos:BQoSPrice/bqos:Price/bqos:Amount in Section 3: BQoS Price in EERP-bQoS
769
Specification for more details.
770/sla:SLAObligations/sla:ActionGuarantee/sla:ReserveFee/@{any}
771
772

This is an extensibility mechanism to allow additional attributes, based on schemas, to be added
to the ReserveFee element in the future. Unrecognized attributes SHOULD cause a fault.

773/sla:SLAObligations/sla:ActionGuarantee/sla:Penalty
774
775

Penalty element is the money amount when Service Level Objective (SLO) is not met. It is a

required element for Action Guarantee.

776/sla:SLAObligations/sla:ActionGuarantee/sla:Penalty/bqos:Unit
777
Number of unit is a optional element that includes a attribute of unit of measurement uses
778
cbc:BaseUnitMeasureType. See /bqos:BQoSPrice/bqos:Price/bqos:Unit in Section 3: BQoS
779
Price in EERP-bQoS Specification for more details.
780/sla:SLAObligations/sla:ActionGuarantee/sla:Penalty/bqos:Amount
781
Amount element is a required element for the Penalty element. It uses cbc:AmountType from UBL
782
that has a required currencyID attribute for currency code. See
783
/bqos:BQoSPrice/bqos:Price/bqos:Amount in Section 3: BQoS Price in EERP-bQoS
784
Specification for more details.
785/sla:SLAObligations/sla:ActionGuarantee/sla:Penalty/@{any}
786
787

This is an extensibility mechanism to allow additional attributes, based on schemas, to be added
to the Penalty element in the future. Unrecognized attributes SHOULD cause a fault.

788
789Example

790
791The following example illustrates the use of Action Guarantee element. It describes the penalty:

792
793
794
795
796
797
798
799

(001) <?xml version="1.0" encoding="utf-8"?>
(002) <ActionGuarantee xmlns="..." xmlns:bqos="..." ...>
(003)
<Penalty>
(004)
<bqos:Unit unitCode="EA">10</bqos:Unit>
(005)
<bqos:Amount currencyID="USD">17.15</bqos:Amount>
(006)
</Penalty>
(007) </ActionGuarantee>

800
61SOA-EERP-SLA-V1.0-WD04
62Copyright â OASISđ 2009. All Rights Reserved.

8 June, 2009
Page 21 of 31


801

64SOA-EERP-SLA-V1.0-WD04
65Copyright â OASISđ 2009. All Rights Reserved.

8 June, 2009
Page 22 of 31


8026

SLA Terms

803The SLA Terms, Terms element for EERP-SLA, is the agreed SLA terms aspect of the service,
804including SLA term elements.
805
806There MAY be zero or one SLA Terms element present in the SLA of service.
807
808Syntax
809
810
811
812
813

<sla:SLATerms xmlns:bqos="..." ...>
<sla:SLATerm ...>sla:SLATermType
...
</sla:SLATerm> +
</sla:SLATerms>

814
815The following describes the attributes and elements listed in the schema outlined above:
816/sla:SLATerms
817
The agreed SLA terms aspect of the service, including SLA term elements. It has a list of SLA
818
terms for SLATerms .
819/sla:SLATerms/sla:SLATerm
820
SLA Term element is an any type element to describe additional term for this SLA.
821/sla:SLATerms/sla:SLATerm /@{any}
822
823

This is an extensibility mechanism to allow additional attributes, based on schemas, to be added
to the SLATerm element in the future. Unrecognized attributes SHOULD cause a fault.

824/sla:SLATerms/sla:SLATerm/{any}
825
826
827

This is an extensibility mechanism to allow different (extensible) property or attribute
elements/parameters to be specified in the future. Unrecognized parameters SHOULD cause a
fault.

828/sla:SLATerms/@{any}
829
830

This is an extensibility mechanism to allow additional attributes, based on schemas, to be added
to the SLATerms element in the future. Unrecognized attributes SHOULD cause a fault.

831
832Example
833
834The following example illustrates the use of SLA Terms element. It describes the term of the SLA:
835
836
837
838
839
840
841
842
843
844

(001) <?xml version="1.0" encoding="utf-8"?>
(002) <SLATerms xmlns="..." ...>
(003)
<SLATerm xmlns:t="..." >
(004)
<t:ServcieLocation>
(005)
<t:Lat>37.7749295</t:Lat>
(006)
<t:Lng>-122.4194155</t:Lng>
(007)
</t:ServcieLocation>

(008)
</SLATerm>
(009) </SLATerms>

67SOA-EERP-SLA-V1.0-WD04
68Copyright â OASISđ 2009. All Rights Reserved.

8 June, 2009
Page 23 of 31


845

70SOA-EERP-SLA-V1.0-WD04
71Copyright â OASISđ 2009. All Rights Reserved.

8 June, 2009
Page 24 of 31


8467

SLA Examples

8477.1 Committed Throughput with Penalty Example
848This SLA example will show the following agreement between EERP Sample Service and
849EERP Service Requester:
850
1. The service is based on the Service profile defined on
851

/>852
2. It will charge $17.15 per service.
853
3. Starting from January 1st, 2009, the agreement last for one whole year.
854
4. The committed throughput is 10 services per day.
855
5. If the provider cannot meet the SLA for #3 and #4, the penalty will be $17.15 per 10
856
services.
857

858Example
859
860The following example illustrates the whole SLA document for above agreements:
861
862
863
864
865
866
867
868
869
870
871
872
873
874
875

876
877
878
879
880
881
882
883
884
885
886
887
888
889
890
891
892
893
894
895

(1)
(2)
(3)
(4)
(5)
(6)
(7)
(8)
(9)

(10)
(11)
(12)
(13)
(14)
(15)
(16)
(17)
(18)
(19)
(20)
(21)
(22)
(23)
(24)
(25)
(26)
(27)
(28)
(29)
(30)
(31)
(32)
(33)
(34)

<?xml version="1.0" encoding="utf-8"?>
<BSLA xmlns="..." xmlns:bqos="..." ... >
<SLAParties>
<ServiceProvider>

<ServiceUri>
/><ServiceProviderName languageID="EN">
EERP Sample Service</ServiceProviderName>
</ServiceProvider>
<ServiceRequester>
<ServiceRequesterUri>
</ServiceRequesterUri>
<ServiceRequesterName languageID="EN">
EERP Service Requester</ServiceRequesterName>
</ServiceRequester>
</SLAParties>
<SLAParameters>
<ServiceProfileUri>
/><ServiceOperations>
<hasCommittedCost>true</hasCommittedCost>
<hasCommittedTime>true</hasCommittedTime>
<hasAvailabilities>false</hasAvailabilities>
<hasCommittedTroughput>true</hasCommittedTroughput>
<hasOtherTerms>false</hasOtherTerms>
</ServiceOperations>
</SLAParameters>
<SLAObligations>
<Obligation>
<ServiceLevelObjective>
<CommittedCost>
<bqos:Unit unitCode="EA">1</bqos:Unit>
<bqos:Amount currencyID="USD">17.15</bqos:Amount>
</CommittedCost>

73SOA-EERP-SLA-V1.0-WD04

74Copyright © OASIS® 2009. All Rights Reserved.

8 June, 2009
Page 25 of 31