LO-6 Demonstration Scenario Lecturer Ricardo Gonçalves e-Procurement

LO-6: Demonstration Scenario Lecturer: Ricardo Gonçalves

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, … 2

Selling Process. Customer oriented subscenario RETAILER R 1. Request for Quotation R 2. Quotation R 3. Order Delivery Interior Decoration Project R 4. Order Confirmation Customer communication Looks for furniture Delivery Invoice R 5. Delivery Note R 6. Packing List MANUFACTURER R 7. Invoice 3

Procurement Process. Supplier oriented sub -scenario PROVIDER M 1. Request for Quotation M 2. Quotation M 3. Order M 4. Order Confirmation Delivery M 5. Delivery Note M 6. Invoice MANUFACTURER 4

e. Procurement Scenario SELLER M 1. Request for Quotation M 2. Quotation Need M 3. Order M 4. Order Confirmation of Interoperability Delivery M 5. Delivery Note M 6. Invoice BUYER 5

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) 6

CBP Modelling and Enactment Model Buyer Public Process B 2 B Process Order Release Order Public Process Views Seller Release Order Private Process Create Order Pick Up Prepare Goodsout Process Order … Pick Up … Prepare Goodsout Label Printing Bring to Loading Point … Generate Manifest … • CBP addresses Interoperability at the business layer 7

Framework to support Interoperability for CBP Enterprise Modelling Seller Private Business Process Buyer Models are enriched through ontological information and executed by IT systems, e. g. workflow engines Design CBP - Collaborative Business Process CBP Model Buyer Process Formal methods will support integration of private business processes in a coalition whilst maintaining privacy of the participating enterprises Seller View Process Execution Process Engine WS Process Enactment Interface Business process execution will WS 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 Process Enactment Interface to be supported by infrastructure for message handling, dispatching in a Interface P 2 P approach. Process Engine 8

CBP Model High-level Requirements 1. Different user groups and modellers are involved in modelling crossorganizational business processes. Their different perspectives and needs have to be reflected in the modelling method § 2. Met by introducing “Process Modelling levels of abstraction” 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. 9

Process Modelling levels of abstraction Business Description x x Business Level All processes EPC, IEM, Business Level Executable processes BPDM (UML, BPMN) Modelling Tool process name="loan. Approval. Process". . . > . . . . . . Execution Level Executable processes BPEL Execution Engine 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. Nonexecutable 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. 10

Storyboard Picture BPM Suite WS Suite Conformance Suite GRAI Tool Messages with Rules Express Services Java MO²GO Semantic Suite ATHOS Demonstration DESING TIME EXP 2 XSD Private Processes WSDL EXP 2 SCH Messages XSD Rules Schematron A* Maestro ARGOS CBP RUN TIME Gabriel Conformance Test Johnson Plug-in Nehemiah PROCESS Interoperability Tool ARES Engine SERVICES External Tool Model Services 11

Demo: Conformance Testing Retailer Tomas Smith Furniture Shop Blue Chair 20 Conformance Testing Demonstration ance Test Conform Tomas Smith Furniture Shop Blue Chair 20 Manufacturer 12

THE END 13