integrating process and organization models of collaborations through object petri nets

© 2005 ArKoS-Konsortium www.arkos.info

Integrating Process and Organization Models of Collaborations through Object Petri NetsK. Sarshar1, Th. Theling2, P. Loos1, M. Jerrentrup3

1 Institute for Information Systems (IWi) at DFKI, Saarbruecken2 Johannes Gutenberg-University Mainz, Information Systems & Management3 Interactive Software Solutions, Saarbruecken

Funded by


OutlineOutline

ArKoS – Project Motivation and Aim Object Petri Nets Specification of Notation Elements Transforming Notation Elements into PNML Exapmle Conclusion


OutlineOutline

ArKoS – Project Motivation and Aim Object Petri Nets Specification of Notation Elements Transforming Notation Elements into PNML Example Conclusion


Architecture for Collaborative Scenarios

01.10.2003 – 30.09.2006

new modeling methods • integrative architecture

reference models • software platform • showcases

for the improvement of collaboration in cooperations

Architecture for Collaborative Scenarios

01.10.2003 – 30.09.2006

new modeling methods • integrative architecture

reference models • software platform • showcases

for the improvement of collaboration in cooperations

Funded by


OutlineOutline



SituationSituation

Architecture for Collaborative Scenarios (Theling et al. 2005)

Configuration of Business Processes and Organisational Structures

Management and Controlling of Collaborations

Common Execution of Collaborative Processes

Common Available Repository


SituationSituation

Modeling of Business Processes and Organization Structures Considering Individual Interest of Collaboration Partners Using Different Tools for Modeling, e.g. ARIS Toolset

Storing of Models in Collaboration-Wide Unique Notations Business Process Models

• Business Process Modeling Notation (White, 2004)

• BPEL as XML-Notation is too powerful for our requirements• Defining specific XML-Format (BPMN-XML)

Organizational Models• Value Added Nets, “Organization Modeling Notation”• Defining specific XML-Format (OMN-XML)


SituationSituation

Business Process Model

Object Petri Net

Object Net System Net

Formalization

Visualization

Org-ChartEPC

V

V

Organizational Model

PNML Converter

BPMN-XML OMN-XML


Discussed TopicsDiscussed Topics

Question How can Organizational and Business Process Models be

simulated?• Verification

• Evaluating Lead Times, Costs, Resource Usage

• Identifying Interdependencies and Bottle Necks

Aim Integration of Business Process and Organizational Models for

Simulation Target Notation: XML-Noted Object Petri Nets (PNML)

(Billington et al. 2003)


OutlineOutline



Object Petri NetsObject Petri Nets

Token = Active Objects (“Object Net”, ON) (Valk 1996 u.a.)

Object Net can Fire without Firing Transitions in the System Net

Modeling on Different Levels

p6

<i4>

t7

t1

t2 t4

t3 t5

t6

<i2> <i3>

<i3> <i2>

p5

p1 p2

p3 p4e1

e2

e3

e4

e5

<i2>

<i3>

<i4>b1

b2

b4

b3

b5

b6

SNON


OutlineOutline



Specification of Process ElementsSpecification of Process Elements


Object Petri Net


Formalization

Visualization

Org-ChartEPC

V

V


PNML Converter

BPMN-XML OMN-XML


Specification of Process ElementsSpecification of Process Elements

BPMN-Element Notation XML-Spezification

Event: Start <ControlFlowObjectDefinition controlflow-object-type= "EVENT|ACTIVITY|GATEWAY" controlflow-object-definition-id="..." controlflow-object-subtype= "START|INTERMEDIATE|END|TASK|AND|OR" artifact-idlist="..." lane-idlist="..." linked-process-id="..."></ControlFlowObjectDefinition>

Event: Intermediate

Event: End

Activity

Gateway: AND

Gateway: XOR


Specification of Organizational ElementsSpecification of Organizational Elements


Object Petri Net


Formalization

Visualization

Org-ChartEPC

V

V


PNML Converter

BPMN-XML OMN-XML


OMN-Element Notation XML-Spezification

Organization <OMN-ObjectDefinition id="..." type="ORGUNIT" subtype="CONSORTIUM"></OMN-ObjectDefinition>

Hierarchy

<OMN-EdgeDefinition id="..." type="ORG" {subtype="CONTRACT|DELIVERY"} source-object-definition-id="..." target-object-definition-id="..."></OMN-EdgeDefinition>

Relation: Contract resp. Sales Order

Relation: Delivery

contract

Specification of Organizational ElementsSpecification of Organizational Elements

contract

delivery


Specification of Petri Net ElementsSpecification of Petri Net Elements


Object Petri Net


Formalization

Visualization

Org-ChartEPC

V

V


PNML Converter

BPMN-XML OMN-XML


BPMN-XML Notation XML-Spezifikation

Unmarked Place <place id="..."> <text>...</text></place>

Marked Place <place id="..."> <initialMarking> <text>...</text> </initialMarking></place>

Transition <transition id="..."> <name> <text>...</text> </name></transition>

Directed Edge <arc id="E1_F1" source="E1" target="F1" />

Specification of Petri Net ElementsSpecification of Petri Net Elements


OutlineOutline



Transforming into PNMLTransforming into PNML


Object Petri Net


Formalization

Visualization

Org-ChartEPC

V

V


PNML Converter

BPMN-XML OMN-XML


Transformation of Process ElementsTransformation of Process Elements

BPMN-Element Notation PNML-Target of Object Net

Event: Start

Event: Intermediate

Event: End

Activity

Gateways Split Join

AND

XOR


OMN-Element Notation PNML-Target of System Net

Organisation

Hierarchy

Relation: Contract resp. Sales Order

Relation: Delivery

contract

Transformation of Organizational ElementsTransformation of Organizational Elements

contract

delivery

contract

delivery

contract

delivery


Dynamic BehaviorDynamic Behavior

Converter proves which Organizational Unit is Responsible for Activities

Realization in BPMN: Assigning Activities to Lanes

Change of Organizational Unit Uplink resp. Downlink No autonomous Firing of ON, but Firing of ON within SN Challenge: Concurrency in more than one Organizational Unit


OutlineOutline



Case StudyCase Study

System Net: Organizational Model

Object Net: Business Process Model


Example for Dynamic BehaviorExample for Dynamic Behavior

Object Net

System Net System Net: Organizational Model

Object Net: Business Process Model

Interaction: SN: Event 2:SUB1_() ON: contract x:SUB1_()


Example for Dynamic BehaviorExample for Dynamic Behavior

Downlink:<transition id="MAIN_SUB1"> <name> <text>contract</text> </name> <downlink> <text>x:SUB1_()</text> </downlink></transition>

Uplink:<transition id="Event 2"> <name> <text>Event 2</text> </name> <uplink> <text>:SUB1_()</text> </uplink></transition>

Object Net

System Net


OutlineOutline



ConclusionConclusion

Verified Aspects Unique XML Modeling Notation XML-based Integration of Business Process and Organizational

Models Simulation is Enabled

Further Research Operational Values

• Lead Times

• Availability of Resources

• Path-Likelihoods

• Demand-Information

Interpretation of OR-Connector in different Notations• e.g. Empty-Path of BPMN


Thank You for Your Attention


Backup: Objekt-PetrinetzeBackup: Objekt-Petrinetze

Referenznetze (Kummer 2002)

Alle Marken des SN sind Referenz auf gleiche Instanz eines ON Prozess-Parallelisierung durch Kopieren der Marken Keine „echte“ Nebenläufigkeit möglich

Wertesemantik Alle Marken eines SN sind individuelle Kopie eines ON „Echte“ Nebenläufigkeit möglich Problem: Zusammenführung der Teilprozesse

integrating process and organization models of collaborations through object petri nets

Documents