1 SOA-EERP Business Service Level 3Agreement Version 1.0 4Working 5June Draft 04 8, 2009 6Specification URIs: 7This Version: http://www.oasis-open.org/apps/org/workgroup/soa9 eerp/spec/sla/BusinessServiceLevelAgreement-v1.0-spec-wd04.html 10 http://www.oasis-open.org/apps/org/workgroup/soa11 eerp/spec/sla/BusinessServiceLevelAgreement-v1.0-spec-wd04.doc 12 http://www.oasis-open.org/apps/org/workgroup/soa13 eerp/spec/sla/BusinessServiceLevelAgreement-v1.0-spec-wd04.pdf 14Previous Version: 15 http://www.oasis-open.org/apps/org/workgroup/soa16 eerp/spec/sla/BusinessServiceLevelAgreement-v1.0-spec-wd03.html 17 http://www.oasis-open.org/apps/org/workgroup/soa18 eerp/spec/sla/BusinessServiceLevelAgreement-v1.0-spec-wd03.doc 19 http://www.oasis-open.org/apps/org/workgroup/soa20 eerp/spec/sla/BusinessServiceLevelAgreement-v1.0-spec-wd03.pdf 21Latest Version: 22 http://docs.oasis-open.org soa-eerp/sla/v1.0/BusinessServiceLevelAgreement-Specification.html 23 http://docs.oasis-open.org soa-eerp/sla/v1.0/BusinessServiceLevelAgreement-Specification.doc 24 http://docs.oasis-open.org 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, http://docs.oasisopen.org/soa-eerp/rt/v1.0/ SOA-EERP-Rating-Specification.pdf SOA-EERP Business Quality of Service, Version 1, http://docs.oasis-open.org 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 June, 2009 Page of 31 43 44Declared XML Namespace(s): 45 http://docs.oasis-open.org/soa-eerp/sla/200903 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 http://www.oasisopen.org/committees/soa-eerp/ 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 (http://www.oasisopen.org/committees/soa-eerp/ipr.php 64 65 The non-normative errata page for this specification is located at http://www.oasisopen.org/committees/soa-eerp/ 4SOA-EERP-SLA-V1.0-WD04 5Copyright â OASISđ 2009 All Rights Reserved June, 2009 Page 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 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 http://www.oasis110open.org/who/trademark.php for above guidance 111 7SOA-EERP-SLA-V1.0-WD04 8Copyright © OASIS® 2009 All Rights Reserved June, 2009 Page of 31 112Table of Contents 1131 Introduction 114 1.1 Namespaces 115 1.2 Schema Files 116 1.3 Terminology 117 1.4 Normative References 118 1.4.1 Notational Conventions 119 1.4.2 Reference 120 1.5 Normative References 121 1.6 Non-Normative References 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 June, 2009 Page 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 http://docs.oasis-open.org/soa-eerp/sla/200903 148 149Table 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 http://schemas.xmlsoap.org/soap/envelope/ [SOAP] S12 http://www.w3.org/2003/05/soap-envelope [SOAP12] xsd http://www.w3.org/2001/XMLSchema [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 http://docs.oasis-open.org/soa-eerp/bqos/200903 [EERP-BQoS] sla http://docs.oasis-open.org/soa-eerp/sla/200903 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: 155http://docs.oasis-open.org/soa-eerp/eerp-sla/200903/eerp-sla.xsd 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 June, 2009 Page of 31 1611.4 Normative References 162 163 164 [RFC2119] [Reference] S Bradner, Key words for use in RFCs to Indicate Requirement Levels, http://www.ietf.org/rfc/rfc2119.txt, 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 June, 2009 Page 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 http://www.ietf.org/rfc/rfc2119.txt 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 http://www.ietf.org/rfc/rfc3986.txt 224 225[UBL-20] 226 OASIS Standard, “Universal Business Language (UBL) v2.0”, 12 December 2006 227 http://docs.oasis-open.org/ubl/os-UBL-2.0/ 228 229[XML-Schema1] 230 W3C Recommendation, "XML Schema Part 1: Structures Second Edition", 28 October 2004 231 http://www.w3.org/TR/2004/REC-xmlschema-1-20041028/ 232 233[XML-Schema2] 234 W3C Recommendation, "XML Schema Part 2: Datatypes Second Edition", 28 October 2004 235 http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/ 236 237[EERP-BQoS] 238 OASIS Standard (Draft), “SOA-EERP Business Quality of Service Version 1.0” 239 240 http://docs.oasis-open.org/soa-eerp/bqos/200903 2411.6 Non-Normative References 242None 243 19SOA-EERP-SLA-V1.0-WD04 20Copyright â OASISđ 2009 All Rights Reserved June, 2009 Page 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:SLAPartiesTypeType sla:SLAParametersType sla:SLAObligationsType ? sla:SLATermsType ? 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 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 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 June, 2009 Page 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 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 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 June, 2009 Page 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:ServiceProviderType sla:SlaUriType sla:ServiceProviderNameType sla:ServiceRequesterType sla:SlaUriType sla:ServiceRequesterNameType 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 June, 2009 Page 10 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 cbc:BaseUnitMeasureType ? cbc:AmountType 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 cbc:DurationMeasureType cbc:DurationMeasureType ? udt:DateTimeType ? udt:DateTimeType ? 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 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:AvailabilityType xs:dateTime xs:dateTime + 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 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 cbc:DurationMeasureType cbc:BaseQuantityType cbc:DurationMeasureType ? 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 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 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 bqos:PriceType cbc:BaseUnitMeasureType ? cbc:AmountType ? bqos:PriceType cbc:BaseUnitMeasureType ? cbc:AmountType ? 58SOA-EERP-SLA-V1.0-WD04 59Copyright â OASISđ 2009 All Rights Reserved June, 2009 Page 20 of 31 755 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) (002) (003) (004) 10 (005) 17.15 (006) (007) 800 61SOA-EERP-SLA-V1.0-WD04 62Copyright â OASISđ 2009 All Rights Reserved June, 2009 Page 21 of 31 801 64SOA-EERP-SLA-V1.0-WD04 65Copyright © OASIS® 2009 All Rights Reserved 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:SLATermType + 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) (002) (003) (004) (005) 37.7749295 (006) -122.4194155 (007) (008) (009) 67SOA-EERP-SLA-V1.0-WD04 68Copyright â OASISđ 2009 All Rights Reserved June, 2009 Page 23 of 31 845 70SOA-EERP-SLA-V1.0-WD04 71Copyright © OASIS® 2009 All Rights Reserved 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 The service is based on the Service profile defined on 851 http://www.serviceprovider.com/eerp/service/profile 852 It will charge $17.15 per service 853 Starting from January 1st, 2009, the agreement last for one whole year 854 The committed throughput is 10 services per day 855 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) http://www.serviceprovider.com/eerp/service EERP Sample Service http://www.servicerequester.com EERP Service Requester http://www.serviceprovider.com/eerp/service/profile true true false true false 1 17.15 73SOA-EERP-SLA-V1.0-WD04 74Copyright â OASISđ 2009 All Rights Reserved June, 2009 Page 25 of 31 896 897 898 899 900 901 902 903 904 905 906 907 908 909 910 911 912 913 914 915 916 917 (35) (36) (37) (38) (39) (40) (41) (42) (43) (44) (45) (46) (47) (48) (49) (50) (51) (52) (53) (54) (55) (56) 1 2009-01-01T00:00:00Z 1 10 10 17.15 918 9197.2 SLA without Obligation Example 920This SLA example will show the following agreement between EERP Sample Service and 921EERP Service Requester: 922 The service is based on the Service profile defined on 923 http://www.serviceprovider.com/eerp/service/profile2 924 There is no obligation 925 Additional SLA terms include service location and service hours: 926 a Service location is near San Francisco, CA with geocoding of 37.7749295 and 927 -122.4194155 928 b Service hours will be x 24, that is days per week and 24hours per day 929 930Example 931 932The following example illustrates the whole SLA document for above agreements: 933 934 935 936 937 938 939 940 941 942 943 944 945 946 947 948 949 (57) (58) (59) (60) (61) (62) (63) (64) (65) (66) (67) (68) (69) (70) (71) (72) http://www.serviceprovider.com/eerp/service EERP Sample Service http://www.servicerequester.com EERP Service Requester 76SOA-EERP-SLA-V1.0-WD04 77Copyright â OASISđ 2009 All Rights Reserved June, 2009 Page 26 of 31 950 951 952 953 954 955 956 957 958 959 960 961 962 963 964 (73) (74) (75) (76) (77) (78) (79) (80) (81) (82) (83) (84) (85) (86) (87) http://www.serviceprovider.com/eerp/service/profile2 37.7749295 -122.4194155 965 966 79SOA-EERP-SLA-V1.0-WD04 80Copyright © OASIS® 2009 All Rights Reserved June, 2009 Page 27 of 31 9678 Conformance 968An implementation conforms to this specification if it satisfies all of the MUST or REQUIRED level 969requirements defined within this specification A SOAP Node MUST NOT use the XML namespace 970identifier for this specification (listed in Section 1.1) within SOAP Envelopes unless it is compliant with this 971specification 972 973This specification references a number of other specifications (see the table above) In order to comply 974with this specification, an implementation MUST implement the portions of referenced specifications 975necessary to comply with the required provisions of this specification Additionally, the implementation of 976the portions of the referenced specifications that are specifically cited in this specification MUST comply 977with the rules for those portions as established in the referenced specification 978 979Additionally normative text within this specification takes precedence over normative outlines (as 980described in section 1.4.1), which in turn take precedence over the XML Schema [XML Schema Part 1, 981Part 2] and WSDL [WSDL 1.1] descriptions That is, the normative text in this specification further 982constrains the schemas and/or WSDL that are part of this specification; and this specification contains 983further constraints on the elements defined in referenced schemas 984This specification defines a number of extensions; compliant services are NOT REQUIRED to implement 985OPTIONAL features defined in this specification However, if a service implements an aspect of the 986specification, it MUST comply with the requirements specified (e.g related "MUST" statements) If an 987OPTIONAL message is not supported, then the implementation SHOULD Fault just as it would for any 988other unrecognized/unsupported message If an OPTIONAL message is supported, then the 989implementation MUST satisfy all of the MUST and REQUIRED sections of the message 990 82SOA-EERP-SLA-V1.0-WD04 83Copyright â OASISđ 2009 All Rights Reserved June, 2009 Page 28 of 31 991A Acknowledgements 992The following individuals have participated in the creation of this specification and are gratefully 993acknowledged: 994Participants: 995 996 Rex Brooks, 997 Szu Chang, 998 Bill Cox, 999 Andy Lee, 1000 Carl Mattocks, 1001 James Zhili Zhang, 1002 Hong Zhou, Individual Changfeng Open Standards Platform Software Alliance Cox Software Architects LLC Changfeng Open Standards Platform Software Alliance CheckMi TIBCO Software Inc Changfeng Open Standards Platform Software Alliance 1003 85SOA-EERP-SLA-V1.0-WD04 86Copyright â OASISđ 2009 All Rights Reserved June, 2009 Page 29 of 31 1004B Non-Normative Text 1005None 88SOA-EERP-SLA-V1.0-WD04 89Copyright â OASISđ 2009 All Rights Reserved June, 2009 Page 30 of 31 1006C Revision History 1007 Revision Date Editor Changes Made 0.9 03/10/2009 Szu Chang Initial draft WD01 04/24/2009 Szu Chang Renamed draft 0.9 to working draft 01 WD02 05/12/2009 Szu Chang Fixed issue # I011, I012, and I014 WD03 05/17/2009 Szu Chang Added conformance section WD04 06/08/2009 Szu Chang Fixed issue # I017, I018, and I020 1008 1009 91SOA-EERP-SLA-V1.0-WD04 92Copyright â OASISđ 2009 All Rights Reserved June, 2009 Page 31 of 31