The document introduces BPeX, a new approach to BPMN model portability. BPeX was built from scratch to directly support all BPMN elements and features, addressing weaknesses in existing standards like XPDL. BPeX uses a clear conceptual model with XML serialization, unique IDs, and constraints to enable static analysis and validation of BPMN models without additional software. It aims to strengthen connections between BPMN elements and allow seamless interchange of process models.

1. Michele Chinosi University of Insubria – Varese (Italy) BPeX: A New Approach to BPMN Model Portability

4. BPeX: Business Process eXtensions Michele Chinosi - Architecture & Process - 2008 The BPMN-XPDL-BPEL value chain From Keith Swenson blog “Go Flow”, posted May 26, 2006

5. BPeX: Business Process eXtensions Michele Chinosi - Architecture & Process - 2008

6. A Comparison Between WS-BPEL and XPDL Michele Chinosi - Architecture & Process - 2008 WS-BPEL XPDL Expressive power Less expressive More expressive Naming convention Completely different Some names different Structure of the model Completely different Some relevant differences Native referential integrity Partially Missing Execution capabilities Full support No execution allowed Graphical information Not at all Full graphical support Validation / Analysis Complex queries Complex queries

11. A Complex Conceptual Model Michele Chinosi - Architecture & Process - 2008

13. A Complex Conceptual Model Michele Chinosi - Architecture & Process - 2008 BPMN XPDL Processes are children of Pools elements Pools are defined separately from WorkflowProcesses, referencing them through relationships Tasks are specifications of Activity elements Tasks are children of an Implementation element, descendant of an Activity block which belongs to a unique Activities element Events are directly referenced from a Lane element Events are children of an Activity element One Gateway is defined within a Lane The Route element is defined as child of an Activity

15. Lack of Native Referential Integrity Constraints Michele Chinosi - Architecture & Process - 2008

17. Lack of Native Referential Integrity Constraints Michele Chinosi - Architecture & Process - 2008

22. Example Process in BPeX Michele Chinosi - Architecture & Process - 2008

23. XPDL and BPeX comparison Michele Chinosi - Architecture & Process - 2008 BPeX XPDL

24. Conclusions Michele Chinosi - Architecture & Process - 2008 XPDL BPeX Expressive power More expressive Bijective correspondence Naming convention Some names different No differences Structure of the model Some relevant differences Few adjustments due Native referential integrity Missing Strong Execution capabilities No execution allowed Not yet but planned Graphical information Full graphical support Supported with extensions Analyses Complex queries required Simple queries

25. Questions? [email_address] http://bpex.sourceforge.net Michele Chinosi - Architecture & Process - 2008