1 / 13

LO-6: Demonstration Scenario

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

yama
Download Presentation

LO-6: Demonstration Scenario

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. 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. R1. Request for Quotation R2. Quotation R3. Order Interior Decoration Project R4. Order Confirmation Looks for furniture RETAILER Delivery Delivery Invoice R5. Delivery Note R6. Packing List R7. Invoice Customer communication MANUFACTURER Selling Process. Customer oriented sub-scenario

  4. M1. Request for Quotation M3. Order M4. Order Confirmation PROVIDER Delivery M5. Delivery Note M6. Invoice M2. Quotation MANUFACTURER Procurement Process. Supplier oriented sub-scenario

  5. M1. Request for Quotation M3. Order M4. Order Confirmation Delivery M5. Delivery Note M6. Invoice M2. Quotation eProcurement Scenario SELLER Need of Interoperability BUYER

  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 Buyer Process Order Pick Up Public Process … Release Order Process Order Prepare Goods- out Pick Up … B2B Process Public Process Views Seller Release Order Prepare Goods- out … Create Order Label Printing Bring to Loading Point Generate Manifest Private Process …

  8. Framework to support Interoperability for CBP Enterprise Modelling Seller Formal methods will support integration of private business processes in a coalition whilst maintaining privacy of the participating enterprises 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 Seller View Process Execution 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. Process Engine Process Engine WS WS WS WS Process Enactment Interface Process Enactment Interface Process Enactment Interface Process Enactment Interface Process Enactment Interface Interface

  9. CBP Model High-level Requirements • 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” • 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. Business Business Description Description x x x x Business Level All processes EPC, IEM, Business Level Executable processes BPDM (UML, BPMN) process name="loanApprovalProcess" ...> <variables> <variable name="request" messageType="loandef:creditInformationMess age"/> <variable name="riskAssessment" messageType="asns:riskAssessmentMessage "/> ... </variables> ... <flow> <receive name="receive1" partner="customer" portType="apns:loanApprovalPT" operation="approve" variable="request" createInstance="yes"> <source Execution Level linkName="receive - to - assess" Modelling transitionCondition= "bpws:getVariableData('request', Executable processes 'amount')<10000"/> <source linkName="receive - to - approval" Tool transitionCondition= "bpws:getVariableData('request', BPEL 'amount')>=10000"/> </receive> Execution Engine Process Modelling levels of abstraction 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. Storyboard Picture BPM Suite WS Suite Conformance Suite Semantic Suite GRAI Tool Services Java Messages with Rules Express ATHOS MO²GO Demonstration EXP2XSD EXP2SCH Private Processes WSDL Messages XSD Rules Schematron A* DESING TIME Maestro ARGOS CBP Gabriel Conformance Test Johnson ARES Engine RUN TIME Plug-in Nehemiah PROCESS SERVICES Interoperability Tool External Tool Model Services

  12. Demo: Conformance Testing Retailer <Request_for_quotation> <buyer>Tomas Smith</buyer> <seller>Furniture Shop</seller> <product>Blue Chair</product> <quantity>20</quantity> </Request_for_quotation> Conformance Testing Demonstration Conformance Test <Request_for_quotation> <buyer>Tomas Smith</buyer> <sellller>Furniture Shop</sellller> <product>Blue Chair</product> <quantity>20</quantity> </Request_for_quotation> Manufacturer

  13. THE END

More Related