Integrating Process and Organization Models of Collaborations through Object Petri Nets

1. Funded by Integrating Process and Organization Models of Collaborations through Object Petri Nets K. 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

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

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

4. 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

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

6. Situation • 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

7. Situation • 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)

8. Situation

9. Discussed 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)

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

11. Object 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

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

13. Specification of Process Elements

14. Specification of Process Elements

15. Specification of Organizational Elements

16. Specification of Organizational Elements

17. Specification of Petri Net Elements

18. Specification of Petri Net Elements

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

20. Transforming into PNML

21. Transformation of Process Elements

22. Transformation of Organizational Elements

23. Dynamic 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

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

25. Case Study Object Net: Business Process Model System Net: Organizational Model

26. Example for Dynamic Behavior • System Net: Organizational Model • Object Net: Business Process Model • Interaction: • SN: Event 2:SUB1_() • ON: contract x:SUB1_()

27. Example 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>

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

29. Conclusion • 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

30. Thank You for Your Attention

31. Backup: 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