LO-6: Demonstration Scenario

Lecturer: Ricardo Gonçalves

2

e-Procurement

• Actors: furniture manufacturer, raw-material supplier, retailer and customer

• Deals with the document flow of the buying/selling processes: Quotations, Orders, Invoices, Delivery notes– Furniture product list, descriptions and special specifications

– additionally, inclusion of an interior Decoration Project

• Till now– Manual management of the documents

– Hard-copy transfers

• Desired– Automated management of the documents

– Electronic copies

• Possible errors produced in the daily activities– configuration errors, missing information, non-legible characters, …

3

Selling Process. Customer oriented sub-scenario

Delivery

R5. Delivery NoteR6. Packing List R7. Invoice

Customer communication

R3.

O

rder

R1. Request for Quotation

R2. QuotationR

4. O

rder

C

onfi

rmat

ion Interior Decoration Project

Looks for furniture

Invoice

Delivery

MANUFACTURER

RETAILER

4

Procurement Process. Supplier oriented sub-scenario

M2. Quotation

M6. Invoice

M1. Request for Quotation

M3.

Ord

er

M4.

Ord

er C

onfi

rmat

ion

MANUFACTURER

PROVIDER

M5. Delivery Note

Delivery

5

eProcurement Scenario

M2. Quotation

M6. Invoice

M1. Request for Quotation

M3.

Ord

er

M4.

Ord

er C

onfi

rmat

ion

BUYER

SELLER

M5. Delivery Note

Delivery

Needof

Interoperability

6

From workflows to CBP

• Notion of business processes received increasing recognition as the ‘glue’

between originally disjoint activities within an enterprise.

• Business process systems (including workflow management systems)

demonstrated applicability within boundaries of enterprise.

• We envisage that this concept provides a significant opportunity also in the

cross-organizational business context.

• State-of-art focus on workflow models to represent workflows within

organisations and were extended to punctually expose communication points

to other workflows.

• Approach breaks the integrative purpose of business processes due to the

low-level in process orientation.

• Goal is to provide a solution that enables modelling and enactment

(execution) of CBP (Cross-organisational Business Processes)

7

CBP Modelling and Enactment Model

• CBP addresses Interoperability at the business layer

CreateOrder

ReleaseOrder

ProcessOrder

PrepareGoods-

out

PickUp

ProcessOrder

PickUp

ReleaseOrder

PrepareGoods-

out

B2B Process

LabelPrinting

Bring to Loading

Point…

…

…

…PublicProcessViews

PrivateProcess

BuyerPublicProcess

GenerateManifest

Seller

8

Framework to support Interoperability for CBP

Seller View ProcessBuyer Process

Enterprise Modelling

Private Business Process

CBP - Collaborative Business Process

Execution

Interface

Buyer

Seller

CBP Model

Process Engine Process Engine

WSWS

WSWS

Process Enactment InterfaceProcess Enactment InterfaceProcess Enactment InterfaceProcess Enactment InterfaceProcess Enactment Interface

Design

Formal methods will support integration of private

business processes in a coalition whilst maintaining privacy of the participating

enterprises

Business process execution will trigger Web Services associated to the process, and will monitor their execution. Furthermore, it will provide real-time commands and data

harmonisation between WS and has to be supported by infrastructure for message

handling, dispatching in a P2P approach.

Models are enriched through ontological information

and executed by IT systems, e.g. workflow engines

9

CBP Model High-level Requirements

1. Different user groups and modellers are involved in modelling cross-

organizational business processes. Their different perspectives and needs

have to be reflected in the modelling method

Met by introducing “Process Modelling levels of abstraction”

2. Modelling method allows for selectively hiding internal process steps while

offering a mechanism to expose CBP relevant information to partners.

Met by introduction of process views as an additional abstraction layer between

the private process and CBP model.

Process views provide a process-oriented interface towards business partners.

Private processes only known to owning organisation and not exposed to

others.

Process views are an abstraction of the private processes, containing

information that needs to be published for purpose of a specific interaction.

Several tasks of a private process can be combined to one view task.

10

Process Modelling levels of abstraction

Business Description

Business Description

xxxx

Business LevelAll processes

EPC, IEM,

Execution LevelExecutable processes

BPEL

process name="loanApprovalProcess" ...> <variables> <variable name="request" messageType="loandef:creditInformationMessage"/> <variable name="riskAssessment" messageType="asns:riskAssessmentMessage

"/> ... </variables> ... <flow> <receive name="receive1" partner="customer" portType="apns:loanApprovalPT"

operation="approve" variable="request" createInstance="yes"> <source linkName="receive-to-assess" transitionCondition= "bpws:getVariableData('request', 'amount')<10000"/> <source linkName="receive-to-approval" transitionCondition= "bpws:getVariableData('request',

'amount')>=10000"/> </receive>

ExecutionEngine

Business LevelExecutable processesBPDM (UML, BPMN)

ModellingTool

Business view on the cooperation and the cross-organisational process that describes the interaction of the

partners. The CBPs modelled on this level are not executable.

Detailed view on the CBP representing the complete control flow of the process. Non-executable tasks are

replaced by tasks that can be executed in a system. Message exchange between single tasks is modelled, but control flow is specified in a platform independent manner. This supports reuse of process models, as these can be

ported to different process engines bellow

CBP is modelled in the modelling language of an actual business process engine. It’s extended with platform specific interaction information, e.g. actual

message formats sent or received during CBP execution or the specification of particular data sources providing

data during process execution.

11

DE

SIN

G T

IME

RU

N T

IME

PROCESS SERVICES

Storyboard Picture

Interoperability Tool ModelExternal Tool Services

GRAI Tool

MO²GO

PrivateProcesses

Maestro

Nehemiah

Gabriel

CBP

Johnson

WSDL

Services Java

Messages XSDRules

Schematron

Conformance TestPlug-in

Messages with Rules Express

EXP2XSD EXP2SCH

ATHOS

A*

ARGOS

ARES Engine

BPM Suite WS Suite Conformance Suite Semantic Suite

Demonstration

12

Demo: Conformance Testing

Retailer

Manufacturer

<Request_for_quotation> <buyer>Tomas Smith</buyer> <sellller>Furniture Shop</sellller> <product>Blue Chair</product> <quantity>20</quantity></Request_for_quotation>

<Request_for_quotation> <buyer>Tomas Smith</buyer> <seller>Furniture Shop</seller> <product>Blue Chair</product> <quantity>20</quantity></Request_for_quotation>

Conformance Test

Conformance TestingDemonstration

13

THE END