End-to-End Resource Planning (EERP) Model and Use Case - …...4 Last revision 23 June 2010 68...

An OASIS SOA-EERP White Paper

End-to-End Resource Planning (EERP) Model and Use Case

Detailed Context and Example for SOA-EERP Technical Committee

Specifications By : William Cox, Szu Chang, Andy Lee, James Zhang and Hong Zhou

On behalf of the OASIS SOA-EERP Technical Committee

Date: 23 June 2010 Deleted: January 6th,

Last revision 23 June 2010 2

1

2

3

4

5

6

7

8

9

10

The purpose of the OASIS SOA-EERP TC is to define standards for End-to-End Resource Planning (EERP) 11 in a Service-Oriented Architecture context. EERP is a technology that optimizes deployment of services onto a 12 SOA description of an application. This work is being carried out through continued refinement and the 13 addition of interoperation protocols to Business Quality of Services (bQoS), Business Rating of Services 14 (bRating), and Business Services Level Agreement (bSLA) specifications. See the TC Charter1 for more 15 information. 16

This white paper was produced and approved by the OASIS SOA-EERP Technical Committee as a 17 Committee Draft and as part of Public Review Draft 01. It has not been reviewed and/or approved by the 18 OASIS membership at-large. 19

20

Copyright © 2010 OASIS. All rights reserved. 21

All capitalized terms in the following text have the meanings assigned to them in the OASIS Intellectual Property Rights 22 Policy (the "OASIS IPR Policy"). The full Policy may be found at the OASIS website. This document and translations of it 23 may be copied and furnished to others, and derivative works that comment on or otherwise explain it or assist in its 24 implementation may be prepared, copied, published, and distributed, in whole or in part, without restriction of any kind, 25 provided that the above copyright notice and this section are included on all such copies and derivative works. However, 26 this document itself may not be modified in any way, including by removing the copyright notice or references to OASIS, 27 except as needed for the purpose of developing any document or deliverable produced by an OASIS Technical Committee 28 (in which case the rules applicable to copyrights, as set forth in the OASIS IPR Policy, must be followed) or as required to 29 translate it into languages other than English. The limited permissions granted above are perpetual and will not be revoked 30 by OASIS or its successors or assigns. This document and the information contained herein is provided on an "AS IS" basis 31 and OASIS DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY 32 WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY OWNERSHIP 33 RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR 34 PURPOSE. 35

1 Linked from http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=soa-eerp Deleted: <sp>

Deleted: 6 January

Formatted: Numbering: Continuous

EERP Model & Use Case 3

Table of Contents 36

37

Introduction ........................................................................................ 4 38

EERP Technology ............................................................................. 6 39

Overview ........................................................................................... 6 40

Challenges in Implementing EERP ................................................ 6 41

Enablers for Optimization ................................................................ 7 42

Use of EERP Techniques................................................................ 7 43

Terminologies used in EERP .......................................................... 8 44

Status of the Standards Process .................................................... 8 45

Conceptual Framework and Message Flow .................................. 10 46

Overview ..........................................................................................10 47

Conceptual Framework and Actors ...............................................10 48

Message Exchange Example.........................................................11 49

Message Flow..................................................................................11 50

Message Sequence Diagrams .......................................................13 51

A Guided Tour through the XML Vocabulary Specifications ........ 16 52

Overview ..........................................................................................16 53

The Three Specifications ................................................................16 54

EERP Business Quality of Service (bQoS) Specification and 55 Schema ............................................................................................17 56

Business Rating Specification and Schema .................................19 57

EERP Business Service Level Agreement Specification .... Error! 58

Bookmark not defined. 59

Use Case and Examples................................................................. 24 60

Overview ..........................................................................................24 61

The Use Case ..................................................................................24 62

The Scenario....................................................................................25 63

EERP Detailed Examples...............................................................25 64

References....................................................................................... 31 65

66

67

Field Code Changed

Field Code Changed

Field Code Changed

Field Code Changed

Field Code Changed

Field Code Changed

Field Code Changed

Field Code Changed

Formatted

Field Code Changed

Field Code Changed

Field Code Changed

Field Code Changed

Formatted

Formatted

Field Code Changed

Field Code Changed

Field Code Changed

Formatted

Field Code Changed

Field Code Changed

Formatted

Field Code Changed

Field Code Changed

Formatted

Field Code Changed

Field Code Changed

Field Code Changed

Field Code Changed

Field Code Changed

Field Code Changed

Field Code Changed

Field Code Changed

Formatted

Deleted: 4

Deleted: 5

Deleted: 5

Deleted: 5

Deleted: 6

Deleted: 6

Deleted: Status of the Standards Process

Deleted: 6

Deleted: Conceptual Framework and Message Flow

Deleted: 8

Deleted: Overview

Deleted: 8

Deleted: Conceptual Framework and ActorsDeleted: 8

Deleted: Message Exchange Example

Deleted: 9

Deleted: Flow

Deleted: 10

Deleted: A Guided Tour through the XML Vocabulary Specifications

Deleted: 12

Deleted: Overview

Deleted: 12

Deleted: The Three

... [32]

... [5]

... [6]

... [34]

... [13]

... [1]

... [38]

... [4]

... [18]

... [35]

... [7]

... [3]

... [20]

... [11]

... [33]

... [12]

... [22]

... [36]

... [23]

... [21]

... [14]

... [24]

... [15]

... [39]

... [25]

... [16]

... [40]

... [26]

... [41]

... [27]

... [2]

... [28]

... [37]

... [29]

... [17]

... [8]

... [30]

... [9]

... [19]

... [31]

... [10]


Introduction 68

This document introduces Service Oriented Architecture (SOA) End-to-End Resource 69 Planning (EERP). We discuss the motivations, then describe the conceptual framework, 70 model, specifications, and end with a detailed example of how the Technical Committee’s 71 work to date is used applying EERP. As of this writing, the OASIS SOA-EERP TC has 72 approved three XML vocabulary specifications as committee drafts; those committee 73 drafts and this white paper are part of Public Review. 74

For a given service there may a number of potential suppliers. EERP optimizes 75 deployment of services onto a SOA description of an application. Describing the required 76 information—business characteristics of a service, the reputation of potential service 77 providers, and business service-level agreements—enables analysis and optimization of 78 business results in the space of possible service deployments. 79

The specifications can be applied to other areas. For example, bQoS might be used for 80 describing the characteristics of energy or goods bought and sold, and the characteristics 81 of services such as medical, shipping, and more. The reputation of a trading or business 82 partner is useful in many contexts. 83

This whitepaper is coordinated with and part of the SOA-EERP Public Review. 84

85

86

87

Deleted: Draft 01

Deleted: 01

Deleted: <sp>

Deleted: 6 January


Deleted: <sp>


EERP Technology 88

Overview 89

As Service-Oriented Architecture (SOA)2 has matured as a development, deployment, and 90

governance paradigm, the performance of SOA deployments has received increasing 91 attention. 92

According to OASIS Reference Model for Service Oriented Architecture [SOA-RM], 93 Service Oriented Architecture (SOA) is a paradigm for organizing and utilizing distributed 94 capabilities that may be under the control of different ownership domains. The service 95 within SOA is a mechanism to enable access to one or more capabilities, where the 96 access is provided using a prescribed interface and is exercised consistent with 97 constraints and policies as specified by the service description. 98

End-to-End Resource Planning (EERP) applies the well-known technique, such as 99 Universal Description, Discovery and Integration [UUDI], WS-Discovery [WS-DD], and 100 Devices Profile for Web Services [WS-DP], for service discovery and optimization in a 101 novel way to improve business results. As the software industry has applied SOA to 102 eBusiness deployments, self-optimizing systems as exemplified by EERP have become 103 more feasible and more useful. 104

Different deployments of services onto a business process have varying business value. 105 For example, a shipper might offer faster but more expensive service. EERP models the 106 business process and the range of potential services, and then guides the selection and 107 deployment of services based on the overall end-to-end business value. 108

Modeling the business characteristics of a service is a prerequisite for estimating the 109 business value of the process that uses those services; likewise, the reliability of the 110 service provided needs to be understood. Finally, establishing agreements about the 111 business service is essential to long-term value chain improvement. 112

Many of these parts of EERP are useful separately. For example, descriptions of a service 113 can be part of defining characteristics of specific services or goods bought or sold, from 114 energy to medical services. 115

Challenges in Implementing EERP 116

The following issues are not addressed in Committee Draft3 4 / Public Review 02 and are 117

not part of the current work plan of the Technical Committee: 118

� The discovery, selection, assembly, and management of services supporting 119 business processes

4 120

2 While we describe services and their characteristics in the context of the Reference Model for Service-Oriented

Architecture [SOA-RM], we are not assembling or otherwise manipulating services in the descriptions in this white paper.

3 As defined in the OASIS Technical Committee Process http://www.oasis-open.org/committees/process.php

4 Other OASIS Technical Committees and other standardization work have addressed many of these challenges. For

example, the Web Services Device Discovery and Device Profile OASIS Standards address discovery and criteria by

which a selection can be made. The OASIS Service Component Architecture addresses assembly of SOA services.

Deleted: , composition, simulation,

Deleted: techniques

Deleted: Draft 01

Deleted: <sp>

Deleted: 6 January


� Monitoring and evolution over time of both the set of services selected and of the 121 performance of the business process itself 122

� Determining and implementing the types of optimization to be supported 123

The definition of the interoperation protocol is on the work plan of the Technical 124 Committee; however Public Review 02 defines message content rather than message 125 sequencing and exchanges. Examples in later sections are not intended to indicate the 126 final work of the Technical Committee. 127

Enablers for Optimization 128

We define "optimization" as maximizing business value by enabling improved real-life 129 eBusiness process and resource planning. Optimization can take place at both design 130 time and run time. The focus of the SOA-EERP Technical Committee is on enablers for 131 optimization and process improvement rather than on the complete EERP environment. 132

Enabling technology defined by the Technical Committee to date include definition of the 133 framework for representing business service characteristics (how to represent cost, time, 134 quality, and intended result), a means to describe the reputation of the service providers 135 to solicit and report information, and a means to describe what we call business service-136 level agreement. 137

Services are performed by people, machines, and hardware/software applications, and 138 represented by SOA services. The qualities of a business service are expressed by 139 means of the Business Quality of Service (bQoS) specification. The nature of bQoS 140 varies across industries and services. 141

Businesses improve their business processes in order to reduce cost, improve 142 efficiency, and otherwise improve business results. The definition and annotation of 143 business processes are outside the scope of the Technical Committee’s work. 144

Use of EERP Techniques 145

Parties interested in this work would include enterprises that deploy and manage solutions 146 that use SOA techniques and which want to develop effective business processes and 147 improve the performance and agility of those solutions. 148

The EERP specifications can be applied to other areas. For example, bQoS may be 149 applicable for definition of characteristics of energy, goods bought and sold, and services 150 such as medical, shipping, and more. The reputation (Rating) of a trading or business 151 partner is useful in many contexts. 152

Extensive applications of SOA-EERP techniques will likely be most cost-effective for long-153 running business processes, although SOA-EERP enabling specifications will also help in 154 the definition, design, and deployment of SOA end-to-end business processes. 155

Early versions of EERP and the SOA-EERP specifications are currently deployed in 156 industry portals in China to facilitate service selection and business process improvement, 157 For example, www.10109555.com , which is China's largest agricultural information 158 service platform, has used early versions of EERP. 159

Deleted: 01

Deleted: cost

Deleted: <sp>


Terminologies used in EERP 160

Business Quality of Service (bQoS) models the business characteristics of a service for 161 estimating the business value of one or a set of services in a business process. In 162 contrast to the QoS in the software/IT world, where the message is network/system 163 oriented measurement that deals with network performance and system availability, the 164 contents of bQoS in this specification is business oriented measurement that deals with 165 business characteristics of a service, such as price, performance, and quality. 166

Business Rating (bRating) defines credibility, reliability and reputation of the service 167 need to be understood for estimating the overall business quality of the process that uses 168 those services. It has two major kinds of rating: Rating and Credentials. Rating are 169 provided by the rating provider to show the ranking and reputation of a given service 170 provider, in comparison of other providers. In contrast, Credentials are provided by the 171 service provider itself to show the credibility of providing a given service. 172

Business Service Level Agreement (bSLA) is the agreement between the service 173 requestor and the service provider, and primary address the bQoS content, Rating and 174 Credentials. These contents are all business related. In contrast to the SLA (Service Level 175 Agreement) in the software/IT world, where SLA is the contract between the service 176 provider and the network/system provider, and the SLA is network/system oriented 177 agreement that deals with network performance and system availability. The bSLA in the 178 EERP is business oriented agreement that deals with price, time to deliver, and the 179 quality/rating of the service. 180

Status of the Standards Process 181

As of this writing, Committee Draft 4 of the SOA-EERP specifications has been approved 182 by the Technical Committee. This white paper will be edited and released with the 183 specifications as part of Public Review 02. The specifications are: 184

� SOA-EERP Business Quality of Service (bQoS) [EERP-bQoS] 185

� SOA-EERP Business Rating of Service (bRating) [EERP-bRating] 186

� SOA-EERP Business Service Level Agreement (bSLA) [EERP-bSLA] 187

These XML vocabulary specifications address the exchange of information that models 188 the business characteristics of a service, permits assertions or queries related to the 189 credibility of the service and its provider, and the establishment of agreements about the 190 use of business service. 191

The SOA-EERP TC will continue the standards development process toward to its 192 ultimate goal of standardizing protocols and message contents so users may apply EERP 193 to guide the selection and deployment of services based on end-to-end business value. 194

Deleted: 5 2

Deleted: 01

Deleted: BQoS

Deleted: BSLA

Deleted: <sp>

Deleted: 6 January


Deleted: <sp>


Conceptual Framework and Message Flow 195

Overview 196

This section describes a conceptual framework in which the current Technical Committee 197 XML vocabulary specifications would fit. In addition to the current work in progress, the 198 conceptual framework describes work that would facilitate service selection and business 199 process improvement from end-to-end. See the Technical Committee charter for the 200 scope of the work. 201

We include a diagram of the conceptual framework, and of messages flows with brief 202 descriptions to demonstrate how the current specifications fit into the overall EERP 203 architecture. We also include timeline and sequence diagrams to show how an 204 implementation would use these specifications in an end-to-end fashion and build a 205 continuous business process improvement loop. 206

Conceptual Framework and Actors 207

Figure 1 is the conceptual framework for EERP. In this figure, the Business Quality of 208 Service is abbreviated as bQoS, Business Rating is abbreviated as bRating, and 209 Business Service Level Agreement is abbreviated as bSLA. 210

The service requester is the client system who asks the EERP system to find an optimal 211 solution. 212

Service providers offer business services. Each service provider may offer the same 213 service but with different bQoS and bRatings

6. Services may be running on different 214

platforms with different implementations, but they all support EERP exchanges of bQoS, 215 bRating, and bSLA information in the XML formats defined by the Technical Committee. 216

The EERP Portal accepts the request from the Service requester, performs bQoS and 217 rating queries, calculates optimal solution(s), and then returns the result to the service 218 requester. 219

The Rating Provider is a party unaffiliated with either the requester or the target of the 220 rating request, such as a third party rating organization, given a reference to a particular 221 business service and provider, issues either a number or a classification description. 222

Note that this conceptual framework is just one way of implementing the EERP 223 technology. There are alternate ways to implement EERP without the EERP Portal. For 224 example, one could use the ebXML Registry/Repository or similar means to exchange 225 business quality of services information, and begin negotiations for establishing Business 226 Service Level Agreements (bSLAs). 227

228

6 The specifications as of this writing do not define the relationships between service providers and multiple bQoS and

Ratings.

Formatted: Font: Bold, Italic, Complex Script

Font: Bold, Italic

Formatted: Font: Not Bold

Deleted: provide

Deleted: provide

Deleted: <sp>

Deleted: 6 January


Message Exchange Example 229

We show the message exchanges graphically then in tabular form. Public Review Draft 01 230 (PR01) describes the XML vocabulary for the content of the message inside a SOAP or 231 REST request/response. For example, an EERP system might have the following 232 messages exchange flow as shown in Figure 1 below. 233

Figure 1 -- EERP Conceptual Framework 234

Information exchanged in messages 2 through 9 is defined by Committee Draft 4 of the 235 specifications. The results of these requests are used to calculate the optimal deployment 236 for a given set of services requests. 237 238 A list of alternatives might be returned in message 10. Each step in the process would 239 have a service provider determined for each service and for each alternative. 240 Messages 11 and 12 are exchanged between the service requester and the selected 241 service providers to define the bSLA. 242

Message Flow 243

The service requester wants to search for the optimal end-to-end solution for a given set 244 of services. The following sequence of messages would work. Note that the Technical 245 Committee has not defined the messages in steps 1, 10, 11, and 12. 246

247

Formatted: Complex Script Font:

Times New Roman

Formatted: Body Text


Times New Roman


Deleted: Public Review

Deleted: 01 versions

Deleted: business

Deleted: <sp>


Step Message Description

1 EERP Request* Service Requester sends EERP Request message to EERP Portal

2 bQoS Request EERP Portal sends bQoS Request messages to all Service

Providers to query the business quality of services

3 bQoS Response Message Service Providers send bQoS Responses back to EERP Portal

4 Rating Request EERP Portal sends Rating Request message to all Service

Providers to query the credentials of the Provider

5 Rating Response Message Service Providers send Rating Response message back to EERP

Portal

6 Rating Request EERP Portal sends Rating Request message to third party Rating

organization to query the rating for the given Provider

7 Rating Response Message The rating provider, such as a third party Rating organization,

sends Rating Response message back to EERP Portal

8 bSLA Request Based on the behavior of the Service Requester, EERP Portal can

send bSLA Request message to the Service Provider to obtain the

commitments from the Provider

9 bSLA Response Message Service Provider commits to the agreement and sends the bSLA Response message back to EERP Portal

10 EERP Response* The optimization will take place in the EERP Portal, which is not

part of these three specifications.

After the optimization calculation on all the information that

EERP Portal received from all Service Providers, EERP Portal sends EERP Response message back to Service Requester

11 bSLA Request* Service Requester sends bSLA Request message to the Service

Providers to obtain the commitments from the Service Providers

directly, instead of getting the bSLA via EERP Portal.

12 bSLA Response Message* Service Provider commits the agreement and sends bSLA

Response message back to Service Requester

* The contents of the indicated messages are not currently defined by the Technical 248 Committee 249

Optionally, a protocol might send a single message combining messages 2 and 4 with the 250 response combining messages 3 and 5. These are shown in Figure 3 as messages 2+4 251 and 3+5. 252

Formatted Table

Formatted: Font: 9 pt, Complex Script Font:

9 pt


9 pt


9 pt


9 pt


9 pt


9 pt


9 pt


9 pt


9 pt


9 pt


9 pt


9 pt


9 pt


9 pt

Formatted: Complex Script Font: Times New

Roman

Formatted: Body Text, Indent: Before: 0"


Roman


Roman


Roman


9 pt

Deleted: Third

Deleted: SAL

Deleted: for those no SLA service in

Deleted: set

Deleted: 1

Deleted: 4a

Deleted: 5b

Deleted: <sp>

Deleted: 6 January


Message Sequence Diagrams 253

We conclude this section with two sequence diagrams. The following is a message 254 sequence diagram without the optional messages: 255

256

Figure 2: EERP Message Sequence without optional messages 257 258


Times New Roman

Formatted: Body Text, Indent:

Before: 0"


Times New Roman


Times New Roman


Times New Roman

Deleted: timing

Deleted:

¶

Deleted: <sp>


The following is a message sequence diagram with the optional messages: 259 260

Figure 3: EERP Message Sequence with optional messages 261

262

Deleted: <sp>

Deleted: 6 January


Deleted: <sp>


A Guided Tour through the XML Vocabulary Specifications 263

Overview 264

As described previously, the current work in the TC includes the following three 265 specifications: 266

� SOA-EERP Business Quality of Service (bQoS) 267

� SOA-EERP Business Rating of Service (bRating) 268

� SOA-EERP Business Service Level Agreement (bSLA) 269 270 This section gives brief descriptions on these three XML vocabulary specifications, their 271 relationship and provides high-level diagrams for their XML schemas. 272 273 XML schema diagrams are produced by Altova XML Spy. For readability, some detail is 274 omitted. A key to the notation is available.

7 275

The Three Specifications 276 EERP applies service discovery, composition, simulation, and optimization techniques in a 277 novel way to improve business results. It takes as input a model of a business process 278 and the range of potential services, and then guides the selection and deployment of 279 services based on the end-to-end business value. 280 281 EERP Business Quality of Service (bQoS) Specification is an XML vocabulary by which a 282 business application may communicate selected business characteristics of the service it 283 provides. Modeling the business characteristics of a service is a prerequisite for 284 estimating the business value of the process that uses those services. 285 286 EERP Business Rating of Services Specification is an XML vocabulary for information 287 exchange on business credibility, reliability and reputation of the service providers. The 288 credibility, reliability and reputation of the service need to be understood for estimating the 289 overall business quality of the process that uses those services. 290 291 The business characteristics of the service defined in the bQoS specification and the 292 business rating characteristics of the service defined in the bRating specification together 293 will enable EERP to determine the varieties of optimization to be supported, and to select 294 an optimal end-to-end solution. 295 296 EERP Business Service Level Agreement (bSLA) Specification is an XML vocabulary for 297 information exchange by which a business application can manage and evaluate services 298 with agreed business quality of service, obligations and terms. 299 300 Modeling the business service-level agreements to manage and evaluate services and 301 establishing agreements about the business service is essential to long-term value chain 302 improvement. The details of the business service level agreement defined in the bSLA 303 specification will enable EERP to determine the varieties of optimization to be supported, 304 and to effectively manage the end-to-end business process. 305

7 The XML Schema diagrams were drawn using Altova XMLSpy. For an explanation of the symbols used in these

diagrams, see http://www.e.govt.nz/standards/e-gif/authentication/data-formats-v1.1/chapter15.html or

http://www.diversitycampus.net/Projects/TDWG-SDD/Minutes/SchemaDocu/SchemaDesignElements.html.

Formatted: Font: (Default) Arial, 10 pt,

Complex Script Font: Arial, 10 pt

Deleted: creditability

Deleted: creditability

Deleted: Business

Deleted: for (BSLA

Deleted: BSLA

Deleted: <sp>

Deleted: 6 January


306 For example, when a service requester sends an EERP request message to the EERP 307 Portal, the EERP Portal can query the business characteristics and the business rating 308 characteristics of each service within the business process for all qualified service 309 providers in the network, and calculate the possible optimized alternatives for the 310 requester. To achieve end-to-end business value for the business process, additional 311 message exchanges can be done to establish the business service-level agreements, and 312 to manage and evaluate services. 313

EERP Business Quality of Service (bQoS) Specification and Schema 314 The Business Quality of Service (bQoS) of the XML vocabulary is defined in XML Schema 315 format that defines many quality measurement indicators. It has the following major 316 elements: 317

� BQoSPrice indicates price or cost for the service 318

� BQoSPerformance indicates time to complete the service, or in the alternative, 319 throughput and latency 320

� BQoSQualities indicates additional properties and attributes 321

� Additional elements for quality of service 322

323

Deleted: <sp>


324

Figure 4 XML Schema for Business Quality of Service 325 Deleted: 3

Deleted: <sp>

Deleted: 6 January


Business Rating Specification and Schema 326

The Business Rating (bRating) specification is for business reliability and reputation of the 327 service and its services provider. It can have one or more of the following elements: 328

329

� ListOfRating element is for the rating provider to rating of service. Each Rating 330 element in the ListOfRating is issued by a rating organization that has either an 331 aggregated numeric rating or an aggregated classification description to 332 represent the rating of the given business service. 333

� Credentials element is for credentials for the service that the service provider 334 owns or holds. Credentials are issued by organizations regulating the service, 335 such as licenses, permissions, certifications, associations, or affiliations. This is 336 not the credential for authentication in the security term. Instead, they are 337 credentials that the service provider wishes to shown its credibility for providing 338 the service. Each individual element in Credentials contains a single credential for 339 the given business service. 340

� Any additional elements for rating the service. For example, this could be one or 341 more elements of PerformanceQualityAssertionEvaluation that provides a 342 mechanism for Service Rating Entities to render their evaluation for how well the 343 Service Provider fulfills the Service Provider’s own Quality Assertion(s) of its 344 service. 345

Figure 5 is the diagram of the XML Schema for Business Rating: 346

347

Deleted: third party

Deleted: .

Deleted: provide

Deleted: 4

Deleted: <sp>


348

Figure 5 XML Schema for Business Rating 349

Deleted: <sp>

Deleted: 6 January


EERP Business Service Level Agreement Specification 350

EERP Business Service Level Agreement Specification defines business Service Level 351 Agreement (bSLA) between the service requestor and service provider for a given service. 352 Business SLA is a formal contract between a service provider and a client guaranteeing 353 quantifiable business quality of service (bQoS) at defined levels. 354

355

It can have one or more of the following elements: 356

� SLAParties describes the parties involved in the bSLA for the service 357

� SLAParameters describes the parameters for the service, which are defined ways 358 of monitoring of bQoS metrics. 359

� SLAObligations describes the agreed bSLA obligations for the service. 360

� SLATerms describes the agreed bSLA Terms for the service. 361

� Any additional elements for the agreement of the service. 362 Figure 6 is the diagram of XML Schema for bSLA:363

Formatted: Normal, Don't keep with

next

Deleted: 5

Deleted: <sp>


364 Figure 6 -- XML Schema for bSLA365

Formatted: caption Char, Font: 12 pt,

Complex Script Font: Bold, Italic

Formatted: caption Char, Font: 12 pt,

Complex Script Font: Bold, Italic

Formatted: Centered

Deleted: Business SLA:Page Break

Deleted: <sp>

Deleted: Business Rating¶Page Break

¶

<sp>Figure 5 -- XML Schema for BSLA

Deleted: 4

Deleted: <sp>

Deleted: 6 January

... [44]


The following is the diagram of XML Schema for SLAObligations element within the bSLA: 366

Figure 7 -- XML Schema for SLAObligations Element 367

368

Deleted: Business

Deleted: 6

Deleted: <sp>


Use Case and Examples 369

Overview 370 This section describes a use case to illustrate how these specifications, EERP bQoS, 371 EERP bRating and EERP bSLA, would be used. 372

The Use Case 373 A typical EERP application system may be drawn as follows. 374

375

376

377

378

379

380

381

382

383

384

385

386

387

388

389

390

391

392

393

394

395

Figure 7 -- EERP Application Use Case 396

Deleted: <sp>

Deleted: 6 January


The Scenario 397

The Requester in our example is Sichuan My Gas Corporation 398 (http://www.mygascorp.com.cn), a Chinese gas company that supplies natural gas to 399 citizens living in the Sichuan Province, in Western China. It needs to order some gas 400 meters for its customers. 401

The service is to provide a batch of gas meters. One of the Service Providers is Hangzhou 402 MyGasMeter Technology Co. Ltd. (http://www.mygasmeter.com.cn), a gas meter producer 403 that produces high quality IC-gas-meter in a timely fashion. Our example Service Provider 404 is located in Zhejiang Province, in Eastern China. 405

The rating provider is 51Honest.org (http://www.51honest.org/), a rating organization that 406 has the experience to evaluate and certify a service provider in the industry. 407 51Honest.org is located in Northern China. 408

Detailed example XML instances are listed in this section. These examples follow the 409 schemas in Public Review Draft 01 for EERP bQoS, bRating and bSLA. 410

Actors 411

� Service Requester: requests a service through the EERP systems to find the 412 optimal solution 413

� Service Providers: offer the service, each with a different bQoS and Rating 414

� EERP Portal: a system that accepts the request from the Service requester. It 415 performs bQoS and Rating queries, calculates the optimal solution, and returns 416 the result back to Service requester. 417

� Rating Provider: a third party rating organization, such as 51Honest.org, 418 provides the rating service for the service providers 419

EERP Detailed Examples 420

Namespaces 421

Unless overridden by a namespace declaration inside an XML fragment, this document 422 uses the following namespaces: 423

Prefix Namespace

s http://schemas.xmlsoap.org/soap/envelope

eerp http://docs.oasis-open.org/ns/soa-eerp/eerp/200903

bqos http://docs.oasis-open.org/ns/soa-eerp/bqos/200903

bsla http://docs.oasis-open.org/ns/soa-eerp/sla/200903

rt http://docs.oasis-open.org/ns/soa-eerp/rt/200903



Times New Roman


Times New Roman


Times New Roman


Times New Roman


Times New Roman


Times New Roman


Times New Roman

Deleted: ¶

Deleted: ¶

Deleted: organization

Deleted: ¶

Deleted: provides

Deleted: Third Party

Deleted: <sp>


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

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

xsd http://www.w3.org/2001/XMLSchema

EERP bQoS Example 424

This bQoS example demonstrates the use of the EERP bQoS specification. The business 425 quality of service on the gas-meters, including price, throughput and some properties, are 426 described in XML to meet the specification provided by the gas-meter producer, 427 Hangzhou MyGasMeter Technology Co. Ltd. (http://www.mygasmeter.com.cn), the EERP 428 Service Provider. 429

The bQoS instance has the following items: 430

1. The price of the gas-meters is CNY(RMB) 120,000.00 per batch, and1,000 gas-431 meters a batch delivery 432

2. The throughput is 1,000 gas-meters in one batch, one batch per week or 7 days 433

3. Some of the gas-meter properties are listed in our example: integrated IC-Card-434 Box, with a solid iron shell. 435

436 (01) <?xml version="1.0" encoding="UTF-8"?> 437 (02) <bqos:BQoS ... 438 (03) xmlns:bqos="http://docs.oasis-open.org/ns/soa-439

eerp/bqos/200903" 440 (04) xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" > 441 (05) <bqos:BQoSPrice > 442 (06) <bqos:Price> 443 (07) <bqos:Unit unitCode="EA">1000</bqos:Unit> 444 (08) <bqos:Amount 445

currencyID="CNY">120000</bqos:Amount> 446 (09) </bqos:Price> 447 (10) </bqos:BQoSPrice> 448 (11) <bqos:BQoSPerformance> 449 (12) <bqos:Throughput > 450 (13) <bqos:Duration unitCode="DAY">7</bqos:Duration> 451 (14)  453 (15) <bqos:Quantity>1000</bqos:Quantity> 454 (16) <bqos:Latency unitCode="DAY">0</bqos:Latency> 455 (17) </bqos:Throughput> 456 (18) </bqos:BQoSPerformance> 457 (19) <bqos:BQoSQualities> 458 (20) <bqos:Property> 459 (21) <bqos:PropertyName languageID="zh-460

cn">外壳</bqos:PropertyName> 461 (22) <bqos:PropertyValue languageID="zh-462

cn">铁壳</bqos:PropertyValue> 463 (23) </bqos:Property> 464 (24) <bqos:Property> 465 (25) <bqos:PropertyName languageID="en">IC-466

Card-Box</bqos:PropertyName> 467 (26) <bqos:PropertyValue 468

languageID="en">integrated</bqos:PropertyValue> 469 Deleted: <sp>

Deleted: 6 January


Roman



(27) </bqos:Property> 470 (28) </bqos:BQoSQualities> 471 (29) </bqos:BQoS> 472

EERP bRating Example 473

This bRating example illustrates ratings and credentials for the gas-meter producing 474 service. In this example the service provider is Hangzhou MyGasMeter Technology Co. 475 Ltd. (http://www.mygasmeter.com.cn): 476

The bRating message has the following items: 477

1. Credit rating on provider is 980.1, rated by 51Honest.org 478 (http://www.51Honest.org), a third-party organization in northern China 479

2. License on gas-meter production is issued in December 1997, by the Zhejiang 480 Bureau of Quality and Technical Supervision in the P. R. of China 481 (http://www.zjbts.gov.cn/), a government agency. 482

3. Certificate on gas-meter product is the first Dual-Explosion-Proof Certificate in 483 November 1997. The Certificate is issued by a third-party organization, the 484 National Supervision and Inspection Center for Explosion Protection and Safety of 485 Instrumentation (NEPSI) in Shanghai in the P. R. China 486 (http://www.sipai.com/sitiias/nepsi.asp) 487

488 (01) <?xml version="1.0" encoding="UTF-8"?> 489 (02) <BRating xmlns="http://docs.oasis-open.org/ns/soa-490

eerp/rt/200903" > 491 (03) <ListOfRating> 492 (04) <Rate Type="Credit" > 493 (05) <RatingIssuer> 494 (06) <IssuerName languageID="zh-495

CN">信星计划51Honest.org </IssuerName> 496 (07) 497

<IssuerUri>http://www.51Honest.org</IssuerUri> 498 (08) </RatingIssuer> 499 (09) <RatingNumeric>980.1</RatingNumeric> 500 (10) <RatingDate>2008-12-31</RatingDate> 501 (11) <RatingReferenceUri/> 502 (12) </Rate> 503 (13) </ListOfRate> 504 (14) 505 (15) <Credentials> 506 (16) <Credential Type="License" > 507 (17) <CredentialIssuer> 508 (18) <IssuerName languageID="zh-509

CN">浙江省质量技术监督局</IssuerName> 510 (19) 511

<IssuerUri>http://www.zjbts.gov.cn/</IssuerUri> 512 (20) </CredentialIssuer> 513 (21) <CredentialClass languageID="zh-514

CN">中华人民共和国计量器具生产制造许可证</CredentialClass> 515 (22) <License languageID="en-us">ZJJHJDJ-516

JL1997120001</License> 517 (23) <CredentialDate> 518 (24) <DateIssued>1997-12-01</DateIssued> 519 (25) </CredentialDate> 520 (26) <CredentialReferenceUri/> 521 (27) </Credential> 522 Deleted: <sp>


Times New Roman


Times New Roman


Times New Roman



(28) <Credential Type="Certification"> 523 (29) <CredentialIssuer> 524 (30) <IssuerName languageID="en">National 525

Supervision and Inspection Center for Explosion Protection 526 and Safety of Instrumentation ( NEPSI ) in Shanghai, 527 P.R.China</IssuerName> 528 <IssuerUri>http://www.sipai.com/sitiias/nepsi.asp</Issue529 rUri> 530

(31) </CredentialIssuer> 531 (32) <CredentialClass languageID="en">the first 532

Dual-Explosion-Proof Certificate</CredentialClass> 533 (33) <License languageID="en-us">NEPSI-534

FB1997110001</License> 535 (34) <CredentialDate> 536 (35) <DateIssued>1997-11-01</DateIssued> 537 (36) </CredentialDate> 538 (37) <CredentialReferenceUri/> 539 (38) </Credential> 540 (39) </Credentials> 541 (40) </BRating> 542

EERP bSLA Example 543

This bSLA example shows the following agreement on the gas-meters between Hangzhou 544 MyGasMeter Technology Co. Ltd. (http://www.mygasmeter.com.cn), an EERP Service 545 Provider, and Sichuan Mianyang Gas Corp. (http://www.mygascorp.com.cn), an EERP 546 Service Requester: 547

The bSLA will have the following terms: 548

1. The service will charge CNY(RMB) 120,000.00 per batch of gas-meter products 549

2. The reservation fee for guarantee will charge CNY(RMB) 10.00 per batch 550

3. The Committed Time for delivery is 7 days (one week) or a little longer per batch, 551 but not later than April 1, 2009 552

4. The committed throughput is 1,000 gas-meters in one batch, per week (7 days) 553

5. The penalty will be CNY(RMB) 10.00 per batch, if entry #3 and #4 of the bSLA 554 cannot be met and is not fulfilled by the service provider 555

556 (01) <?xml version="1.0" encoding="UTF-8"?> 557 (02) <BSLA xmlns="http://docs.oasis-open.org/ns/soa-eerp/sla/200903" 558 (03) xmlns:bqos="http://docs.oasis-open.org/ns/soa-559

eerp/bqos/200903" 560 (04) xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" 561 (05) ...> 562 (06) <SLAParties> 563 (07)  566 (10) <ServiceProvider SPID="1"> 567 (11) 568

<ServiceUri>http://www.mygasmeter.com.cn</ServiceUri> 569 (12) <ServiceProviderName>Hangzhou MyGasMeter 570

Technology Co. Ltd, Zhejiang Prov., 571 P.R.China</ServiceProviderName> 572

(13) </ServiceProvider> 573 (14)  576 (17) <ServiceRequester> 577 (18) 578

<ServiceRequesterUri>http://www.mygascorp.com.cn</ServiceReques579 terUri> 580

(19) <ServiceRequesterName>Mianyang Gas Corp., Sichuan 581 Prov., P.R.China</ServiceRequesterName> 582

(20) </ServiceRequester> 583 (21) </SLAParties> 584 (22) 585 (23) <SLAParameters> 586 (24) <ServiceProfileUri>http://UnkownServiceURL 587

(http://www.mygasmeter.com.cn)</ServiceProfileUri> 588 (25) <ServiceOperations> 589 (26) <hasCommittedCost>true</hasCommittedCost> 590 (27) <hasCommittedTime>true</hasCommittedTime> 591

<hasAvailabilities>true</hasAvailabilities> 592 593 <hasCommittedThroughput>true</hasCommittedThroughput> 594 <hasOtherTerms>true</hasOtherTerms> 595

(28) </ServiceOperations> 596 (29) </SLAParameters> 597 (30) 598 (31)  599 (32) <SLAObligations> 600 (33) <Obligation> 601 (34) <ServiceLevelObjective> 602 (35) <CommittedCost> 603 (36) <bqos:Unit 604

unitCode="EA">1000</bqos:Unit> 605 (37) <bqos:Amount 606

currencyID="CNY">120000.00</bqos:Amount> 607 (38) </CommittedCost> 608 (39) </ServiceLevelObjective> 609 (40) <ActionGuarantee> 610 (41) <ReserveFee> 611 (42) <bqos:Unit 612


currencyID="CNY">10.00</bqos:Amount> 615 (44) </ReserveFee> 616 (45) </ActionGuarantee> 617 (46) </Obligation> 618 (47) <Obligation> 619 (48) <ServiceLevelObjective> 620 (49) <CommittedTime timeZone="CST" 621

description="+08:00 China Stand Time, Beijing Time or HK Time"> 622 (50) <bqos:Duration unitCode="DAY"> 623

7</bqos:Duration> 624 (51) <CommittedCompletionTime>2009-04-625

01T00:00:00</CommittedCompletionTime> 626 (52) </CommittedTime> 627 (53) </ServiceLevelObjective> 628 (54) <ActionGuarantee> 629 (55) <ReserveFee> 630 (56) <bqos:Unit 631


currencyID="CNY">0.00</bqos:Amount> 634 (58) </ReserveFee> 635 (59) </ActionGuarantee> 636 (60) </Obligation> 637

Deleted: <sp>


(61) <Obligation> 638 (62)  640 (63) <ServiceLevelObjective> 641 (64) <CommittedTime > 642 (65) <bqos:Duration unitCode="DAY"> 643

7</bqos:Duration> 644 (66) <CommittedCompletionTime>2009-04-645

01T00:00:00Z</CommittedCompletionTime> 646 (67) </CommittedTime> 647 (68) </ServiceLevelObjective> 648 (69) <ActionGuarantee/> 649 (70) </Obligation> 650 (71) <Obligation> 651 (72) <ServiceLevelObjective> 652 (73) <Availabilities > 653 (74) <Availability isAvailable="true"> 654 (75) <From>2009-01-655

01T00:00:00Z</From> 656 (76) <To>2010-01-01T00:00:00Z</To> 657 (77) </Availability> 658 (78) </Availabilities> 659 (79) </ServiceLevelObjective> 660 (80) <ActionGuarantee/> 661 (81) </Obligation> 662 (82) <Obligation> 663 (83) <ServiceLevelObjective> 664 (84) <CommittedThroughput > 665 (85) <bqos:Duration 666

unitCode="DAY">7</bqos:Duration> 667 (86)  669 (87) <bqos:Quantity 670

unitCode="EA">1000</bqos:Quantity> 671 (88) <bqos:Latency 672

unitCode="DAY">0</bqos:Latency> 673 (89) </CommittedThroughput> 674 (90) </ServiceLevelObjective> 675 (91) <ActionGuarantee/> 676 (92) </Obligation> 677 (93) <ActionGuarantee> 678 (94) <ReserveFee> 679 (95) <bqos:Unit unitCode="EA">1000</bqos:Unit> 680 (96) <bqos:Amount 681

currencyID="CNY">0.00</bqos:Amount> 682 (97) </ReserveFee> 683 (98) <Penalty> 684 (99) <bqos:Unit unitCode="EA">1000</bqos:Unit> 685 (100) <bqos:Amount 686

currencyID="CNY">10.00</bqos:Amount> 687 (101) </Penalty> 688 (102) </ActionGuarantee> 689 (103) </SLAObligations> 690 (104) </BSLA> 691

Deleted: <sp>

Deleted: 6 January


References 692

[EERP-bQoS] OASIS Committee Draft 03, “SOA-EERP Business Quality of 693 Service Version 1.0, 6 January 2010. 694

http://docs.oasis-open.org/soa-eerp/bqos/v1.0/SOA-EERP-bQoS-695 Spec-cd03.pdf 696

[EERP-bRating] OASIS Committee Draft 03, “SOA-EERP Business Rating of 697 Service Version 1.0”, 6 January 2010. 698

http://docs.oasis-open.org/soa-eerp/rt/v1.0/SOA-EERP-Rating-699 Spec-cd03.pdf 700

[EERP-bSLA] OASIS Committee Draft 03, “SOA-EERP Business Service Level 701 Agreement Version 1.0”, 6 January 2010. 702

http://docs.oasis-open.org/soa-eerp/sla/v1.0/SOA-EERP-bSLA-703 Spec-cd03.pdf 704

[SOA-RM] OASIS Standard, “Reference Model for Service Oriented 705 Architecture v1.0”, 12 October 2006. http://docs.oasis-706 open.org/soa-rm/v1.0/soa-rm.pdf 707

[UUDI] OASIS Standard, “Universal Description, Discovery and 708 Integration v3.0.2”, 19 October 2004, http://www.oasis-709

open.org/committees/uddi-spec/doc/spec/v3/uddi-v3.0.2-710

20041019.htm 711

[WS-DD] OASIS Standard, “Web Services Dynamic Discovery (WS-712 Discovery) Version 1.1”, 1 July 2009. http://docs.oasis-713 open.org/ws-dd/discovery/1.1/os/wsdd-discovery-1.1-spec-os.pdf 714

[WS-DP] OASIS Standard, “Devices Profile for Web Services Version 1.1”, 715 1 July 2009. http://docs.oasis-open.org/ws-716

dd/dpws/1.1/os/wsdd-dpws-1.1-spec-os.pdf 717

Deleted: BQoS

Deleted: BSLA

Deleted: BSLA

Deleted: <sp>

Page 3: [1] Change Unknown

Field Code Changed


Field Code Changed


Field Code Changed


Field Code Changed


Field Code Changed


Field Code Changed


Field Code Changed


Field Code Changed


Field Code Changed


Field Code Changed


Field Code Changed


Field Code Changed


Field Code Changed

Page 3: [8] Deleted symon chang 6/23/2010 8:17:00 AM

Status of the Standards Process ................................................................


Field Code Changed

Page 3: [10] Formatted symon chang 6/23/2010 8:17:00 AM

TOC 2


Field Code Changed


Conceptual Framework and Message Flow .................................................


Field Code Changed


TOC 1


Field Code Changed


Field Code Changed


Not Expanded by / Condensed by


Field Code Changed


Conceptual Framework and Actors ............................................................


Field Code Changed


Field Code Changed


Message Exchange Example ....................................................................


Field Code Changed


Field Code Changed


Field Code Changed


TOC 2


Field Code Changed


A Guided Tour through the XML Vocabulary Specifications ...........................


Field Code Changed


Field Code Changed


Field Code Changed


TOC 1


Field Code Changed


Formatted


Field Code Changed


Not Expanded by / Condensed by


Field Code Changed


EERP Business Quality of Service (bQoS) Specification and Schema ............


Field Code Changed


Field Code Changed


Business Rating Specification and Schema.................................................


Field Code Changed


Field Code Changed


Business SLA:

Page Break

Date post:	12-Aug-2020
Category:	Documents
Upload:	others
View:	1 times
Download:	0 times

End-to-End Resource Planning (EERP) Model and Use Case - …...4 Last revision 23 June 2010 68...

Documents