© 2005-2006 the athena consortium. cross-organisational business processes - enabling technologies...

26
© 2005-2006 The ATHENA Consortium. Cross-Organisational Business Processes - Enabling Technologies and Tools Ulrike Greiner, SAP Sonia Lippe, SAP

Upload: tamsin-gilbert

Post on 02-Jan-2016

217 views

Category:

Documents


2 download

TRANSCRIPT

Page 1: © 2005-2006 The ATHENA Consortium. Cross-Organisational Business Processes - Enabling Technologies and Tools Ulrike Greiner, SAP Sonia Lippe, SAP

© 2005-2006 The ATHENA Consortium.

Cross-Organisational Business Processes - Enabling Technologies

and Tools

Ulrike Greiner, SAP

Sonia Lippe, SAP

Page 2: © 2005-2006 The ATHENA Consortium. Cross-Organisational Business Processes - Enabling Technologies and Tools Ulrike Greiner, SAP Sonia Lippe, SAP

2© 2005-2006 The ATHENA Consortium.

Course Structure

1. Recall of Concepts + Scenario Introduction

2. ATHENA CBP Modelling Tool Maestro

3. ATHENA CBP Enactment Tool Nehemiah

Page 3: © 2005-2006 The ATHENA Consortium. Cross-Organisational Business Processes - Enabling Technologies and Tools Ulrike Greiner, SAP Sonia Lippe, SAP

© 2005-2006 The ATHENA Consortium.

Recall of Concepts +

Scenario Introduction

Page 4: © 2005-2006 The ATHENA Consortium. Cross-Organisational Business Processes - Enabling Technologies and Tools Ulrike Greiner, SAP Sonia Lippe, SAP

4© 2005-2006 The ATHENA Consortium.

View Process Approach

CBP1 CBP2 CBP3

Organization A Organization B Organization C

VP1 VP2

PP1 PP2

VP3 VP4

PP3

VP5 VP6

PP4 PP5

CBP: Cross-OrganizationalBusiness ProcessesVP: View ProcessesPP: Private ProcessesAS: Applications and Services

AS AS ASThe process view approach provides a systematic way to selectively expose internal information and interweave process steps to cross-organizational business processes. View processes are introduced as an additional layer above the private processes of an organisation.

View processes provide an abstraction of the private processes that allows hiding internal data that must not be revealed by default. The information contained in the view processes must be sufficient to coordinate internal actions with activities of external trading partners. As shown in organization B different view processes can be created as abstractions from the same private processes allowing the partners to keep their internal processes static while being able to interact with different partners in different contexts.

The view processes are then linked up in cross-organizational business processes modelling the cooperation between partners. One view process can be used in different cross-organizational business processes. One cross-organizational business process links the view processes from two or more partners.

Page 5: © 2005-2006 The ATHENA Consortium. Cross-Organisational Business Processes - Enabling Technologies and Tools Ulrike Greiner, SAP Sonia Lippe, SAP

5© 2005-2006 The ATHENA Consortium.

3-Level Modeling Approach

• Business level:– business view on cooperation– processes are not executed

• Execution level:– executable business processes– platform specific

• Technical level:– specifies complete control

and message flow– platform independent

Execution Engine

Technical Level Processes

Business Description

Business Reality

Business Level Processes

xxxx

<variables> <variable name="request"

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

<variables> <variable name="request"

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

<variables> <variable name="request"

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

Execution Level Processes

Page 6: © 2005-2006 The ATHENA Consortium. Cross-Organisational Business Processes - Enabling Technologies and Tools Ulrike Greiner, SAP Sonia Lippe, SAP

6© 2005-2006 The ATHENA Consortium.

ATHENA CBP Approach

Technical Level Processes

Business Level Processesxxxx

<variables> <variable name="request"

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

<variables> <variable name="request"

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

<variables> <variable name="request"

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

Execution Level Processes

Private Process

Private Process

Private Process

View Process

View Process

View Process

CBP

CBP

Transformation automated

Transformation semi-automated with manual steps

Mapping with tool support

Page 7: © 2005-2006 The ATHENA Consortium. Cross-Organisational Business Processes - Enabling Technologies and Tools Ulrike Greiner, SAP Sonia Lippe, SAP

7© 2005-2006 The ATHENA Consortium.

Enactment Architecture: Big Picture

Company Internal Components

CBP Components

Interface Components CBP and View Modeling Tool

CBP Monitoring and Analysis

CBP Repository(CBPs)

Enactment Engine View Processes

View Processes Repository

(VPs)

Event and Document Correlation

Contain all building blocks which are encapsulated inside the company and which are not accessible by partners. For instance, these are all components that are linked to the modelling and execution of private processes or to the invocation of internal applications

Represent the information that has to be shared between partners in order to define and execute CBPs. They can also contain information that is necessary to monitor and analyze the CBP execution if this is required in a particular business scenario.

Represent the information that is published by the companies in order to take part in CBPs, for instance view processes of the partners’ private processes.

Page 8: © 2005-2006 The ATHENA Consortium. Cross-Organisational Business Processes - Enabling Technologies and Tools Ulrike Greiner, SAP Sonia Lippe, SAP

8© 2005-2006 The ATHENA Consortium.

Architecture Alternatives

Database

Database

Database

Application Components

Business Services

Private Business Process Engine

Application Components

View Process and Private Process

Implemented in one Engine

View Process Engine View Process Engine

Cross-Organizational Business Processes

Application Components with Embedded Private

Business Processes

Page 9: © 2005-2006 The ATHENA Consortium. Cross-Organisational Business Processes - Enabling Technologies and Tools Ulrike Greiner, SAP Sonia Lippe, SAP

9© 2005-2006 The ATHENA Consortium.

ATHENA View Process Engine

This engine executes private processes and view processes and invokes internal applications directly. It is provided as a complete tool that has to be set up and customized to link it appropriately with the existing applications.

Company Internal Components

Interface Components

Enactment Engine View Processes

Integrated Repository (PP, VP)

Event and Document Correlation

Private Process Modeling Tool

Internal Applications / Business Services

Partner Interface Components

The ATHENA View process engine can be used in a mediated as well as in a peer-2-peer physical architecture. In a peer-to-peer distribution, each partner would run an ATHENA view process engine and the engines would communicate with each other as shown above. If a mediator is needed the engines would not communicate directly but through the mediator. The mediator would forward the messages and status updates between the partners. If total anonymity is needed and the partners should not be informed about the status of the other partners, this information can be suppressed by the mediator.

Page 10: © 2005-2006 The ATHENA Consortium. Cross-Organisational Business Processes - Enabling Technologies and Tools Ulrike Greiner, SAP Sonia Lippe, SAP

10© 2005-2006 The ATHENA Consortium.

Furniture eProcurement

Interior Decoration Project

MANUFACTURER

RETAILER

SUPPLIER

R1: Request for Quotation

R2: Quotation

R3: Order

R4: Order Confirmation

M1: Request for Quotation

M2: Quotation

M3: Order

M4: Order Confirmation

• 4 Participants:– Retailer– Manufacturer Sales– Manufacturer Procurement– Supplier

• 2 Sub processes:– Selling Process– Procurement Process

Page 11: © 2005-2006 The ATHENA Consortium. Cross-Organisational Business Processes - Enabling Technologies and Tools Ulrike Greiner, SAP Sonia Lippe, SAP

11© 2005-2006 The ATHENA Consortium.

Selling Process

R2. Quotation

R1. Request for Quotation

R3.

Ord

er

R4.

Ord

er C

on

firm

atio

n

MANUFACTURER

RETAILER

R5. Delivery Note

Delivery

Page 12: © 2005-2006 The ATHENA Consortium. Cross-Organisational Business Processes - Enabling Technologies and Tools Ulrike Greiner, SAP Sonia Lippe, SAP

© 2005-2006 The ATHENA Consortium.

ATHENA CBP Modelling Tool

Maestro

Page 13: © 2005-2006 The ATHENA Consortium. Cross-Organisational Business Processes - Enabling Technologies and Tools Ulrike Greiner, SAP Sonia Lippe, SAP

13© 2005-2006 The ATHENA Consortium.

ATHENA CBP Approach

Technical Level Processes

Business Level Processesxxxx

<variables> <variable name="request"

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

<variables> <variable name="request"

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

<variables> <variable name="request"

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

Execution Level Processes

Private Process

Private Process

Private Process

View Process

View Process

View Process

CBP

CBP

Transformation automated

Transformation semi-automated with manual steps

Mapping with tool support

Maestro is a Business Process Modeling Tool on a technical level, that allows for modeling of private processes, view processes, CBPs and their links. Processes modeled can be exported into Nehemiah and run in this business process engine.

You will learn how to use Maestro in the Maestro_Basic SAP Tutor session. Maestro

Maestro offers functionality to manage business partners. Partners can be added and changed in Maestro and are directly updated in the Nehemiah repository. You will learn how to use Partnermanagement in the Maestro_Partnermanagement SAP Tutor session.

Page 14: © 2005-2006 The ATHENA Consortium. Cross-Organisational Business Processes - Enabling Technologies and Tools Ulrike Greiner, SAP Sonia Lippe, SAP

14© 2005-2006 The ATHENA Consortium.

Modelling Processes in Maestro

• Model private process• Generate a view process from the private process• Combine task of private process to view tasks• Take the view process of the partner and create a CBP

from the view processes of the two partners– link up the tasks in the appropriate sequence

• Create the messaging task in the CBP (automated)

• Propagate the messaging tasks to the view processes of the partners

Page 15: © 2005-2006 The ATHENA Consortium. Cross-Organisational Business Processes - Enabling Technologies and Tools Ulrike Greiner, SAP Sonia Lippe, SAP

15© 2005-2006 The ATHENA Consortium.

Modelling Elements

The rectangle represents an activity. Insert Activity

In order to insert an activity into a business process, drag it from modelling element area into the drawing area (business process). Note, the left mouse button has to be pressed.

Name ActivityEach activity needs to be marked with a unique name. A name can be entered by double clicking on the rectangle symbol.

The oval is a notation for coordinators. Insert Coordinator

Inserting works the same way as for activities.Choose Operator

Maestro offers several types of coordinators; the most popular are Begin, End, Choice, Merge, Fork, Synchronize (Sync). Just double click on the coordinator and a drop down menu allows appropriate selection.

Edges connect activities and coordinators with each other. You can draw edges by activating the drawing mode toggle edge icon. After creation of edges deactivate the toggle edge icon to return to the regular modus.

Begin – End ConstellationEach business process has to start with a Begin coordinator and to stop with the End coordinator. Thus the Begin and End coordinator enclose the actual private process.

Fork – Sync. Constellation:Fork initiates a parallel split of a process. A parallel process has to be finished with the coordinator Sync.

Choice – Merge ConstellationThe Choice coordinator initiates a decision within the process. In order to consolidate the choice process again, the Merge coordinator has to be inserted.

Loop - Constellation:A Loop is modelled by using the Merge – Choice Operator.

Page 16: © 2005-2006 The ATHENA Consortium. Cross-Organisational Business Processes - Enabling Technologies and Tools Ulrike Greiner, SAP Sonia Lippe, SAP

16© 2005-2006 The ATHENA Consortium.

Export into Nehemiah

Runtime -> Save

Choose processes and press save.

Page 17: © 2005-2006 The ATHENA Consortium. Cross-Organisational Business Processes - Enabling Technologies and Tools Ulrike Greiner, SAP Sonia Lippe, SAP

17© 2005-2006 The ATHENA Consortium.

Maestro Tool Training with SAP Tutor:• Modeling of Private Processes, Views and CBPs

(sap tutor Maestro_Basic)• Partner Management in Maestro (sap tutor

Maestro_Partnermanagement)

Page 18: © 2005-2006 The ATHENA Consortium. Cross-Organisational Business Processes - Enabling Technologies and Tools Ulrike Greiner, SAP Sonia Lippe, SAP

© 2005-2006 The ATHENA Consortium.

ATHENA CBP Enactment Tool

Nehemiah

Page 19: © 2005-2006 The ATHENA Consortium. Cross-Organisational Business Processes - Enabling Technologies and Tools Ulrike Greiner, SAP Sonia Lippe, SAP

19© 2005-2006 The ATHENA Consortium.

Architecture Alternatives

Database

Database

Database

Application Components

Business Services

Private Business Process Engine

Application Components

View Process and Private Process

Implemented in one Engine

View Process Engine View Process Engine

Cross-Organizational Business Processes

Application Components with Embedded Private

Business Processes

Neh

emia

h

Nehemiah is a Business Process Management Engine, that executes CBPs in a distributed environment and supports the process view approach. Nehemiah provides a Web front end for controling and monitoring CBP execution.

You will learn how to use Nehemiah in the Nehemiah SAP Tutor session.

Page 20: © 2005-2006 The ATHENA Consortium. Cross-Organisational Business Processes - Enabling Technologies and Tools Ulrike Greiner, SAP Sonia Lippe, SAP

20© 2005-2006 The ATHENA Consortium.

Nehemiah Options

Standard: Executes private, internal processes. Standard BPM Engine functionality.

CBP (by process): Simulate the whole business scenario with all partners which are involved in the process.

CBP (by partner role): Offers one partner the possibility to maintain his own processes rather than give access to every role involved in the scenario.

Page 21: © 2005-2006 The ATHENA Consortium. Cross-Organisational Business Processes - Enabling Technologies and Tools Ulrike Greiner, SAP Sonia Lippe, SAP

21© 2005-2006 The ATHENA Consortium.

Nehemiah Process Status

The activity is not available for execution, i.e. the control flow has not yet reached the activity or it has been skipped.

The activity has been running and has been temporarily suspended. It will be resumed later.

The activity has been terminated by a user. That means it is terminated immediately together with the process instance.

The activity has been aborted by a user. That means it is stopped when possible after a user has aborted the process instance.

The activity is available for execution, but has not been started yet. The activity is running.

The activity has been finished successfully.

Page 22: © 2005-2006 The ATHENA Consortium. Cross-Organisational Business Processes - Enabling Technologies and Tools Ulrike Greiner, SAP Sonia Lippe, SAP

22© 2005-2006 The ATHENA Consortium.

Nehemiah Process Execution

You can start a CBP by clicking the Start Button.

This part of the screen contains the CBP Model.

This part of the screen shows the view process that has been derived from the private process and is part of the CBP.

With these buttons you have the option to view and hide the view diagram and the CBP diagram.

Here you see the executed private process. This part is always visible.

Page 23: © 2005-2006 The ATHENA Consortium. Cross-Organisational Business Processes - Enabling Technologies and Tools Ulrike Greiner, SAP Sonia Lippe, SAP

23© 2005-2006 The ATHENA Consortium.

Private Steps and View Steps

The red edge around the activities shows which private activities belong to which view activity.

Page 24: © 2005-2006 The ATHENA Consortium. Cross-Organisational Business Processes - Enabling Technologies and Tools Ulrike Greiner, SAP Sonia Lippe, SAP

24© 2005-2006 The ATHENA Consortium.

Nehemiah Tool Training• Execution of CBP in distributed environment

(SAP Tutor Nehemiah)

Page 25: © 2005-2006 The ATHENA Consortium. Cross-Organisational Business Processes - Enabling Technologies and Tools Ulrike Greiner, SAP Sonia Lippe, SAP

© 2005-2006 The ATHENA Consortium.

Exercise

Page 26: © 2005-2006 The ATHENA Consortium. Cross-Organisational Business Processes - Enabling Technologies and Tools Ulrike Greiner, SAP Sonia Lippe, SAP

26© 2005-2006 The ATHENA Consortium.

ABC Engineering

BeginIdentify

Scope ofWork

PrepareRFT

PublishRFT

Publish RFT

DefineRelevantCriteria

CompareTender

ChooseTender

Award Cointract

Mange /MonitorWork

Mange /MonitorWork

MeasureWork

Escalate

SchedulePayment

MeasureWork

Escalate

SchedulePayment

Begin

Choice Merge End

Choice Merge End

Reject

Accept

BeginCalculate

Cost-Price

CalculatePremium

PrepareTender

SubmitTender

Submit Tender Response

Fork SyncAccept /

SignContract

Accept /Sign

Contract

Measurecompleted

Work

SubmitPayment

Claim

Claim PaymentReceivePayment

ReceivePayment

Begin End

End

Begin Publish RFTSubmit Tender

ResponseAward

CointractFork

Carry outScope of

Work

Carry outScope of

Work

Carry poutScope of

Work

Accept / SignContract

Mange /MonitorWork

ClaimPayment

MeasureWork

Escalate

SchedulePayment

Choice Merge

JJJ Mining

Private Process

CorrespondingProcess View

OfferContract

Reject

Accept

ReceivePayment

End

Cross-OrganisationalProcess

Private Process

CorrespondingProcess View

Sync