IntroductionFrom BPMN 1.2 to BPMN 2.0, one of the significant improvement is the BPMN 2.0 defines an extensibility mechanism for both process model extensions and graphical extensions. Such extensions can be used by modelers and modeling tools to add non-standard elements or "artefacts" to satisfy a specific need and still have valid BPMN Core. Although BPMN 2.0 provides such extensibility mechanism, it is not commonly implemented on modeling tools.
BPMN Process Model without Extension ElementsFigure 1 is an example of a BPMN process diagram - Pizza Collaboration process. In the diagram, message flow element and message element are used to represent not only informational objects but also physical entities such as pizza, money and receipt. Although this is logical useful and acceptable at Descriptive process model level, it often cause confusion to business audience. How often you heard comment like this in a workshop, "I can understand the pizza order as a message in an envelop shape but why is the pizza shaped as an envelop?"
|Figure 1: BPMN Process Diagram using only BPMN Elements |
source: "BPMN 2.0 by Example" from OMG
Introducing BPMN Process Model with Extension ElementsHowever, using extended artefacts in the same process diagram makes the diagram more user-friendly and more intuititve to business audience. The process diagram below used a collection of extended artefacts to represent those entities that are not message or information in nature.
|Figure 2: BPMN Process Diagram with Extended Artefacts|
Two methods are used to associate the extended artefacts with activities in the diagram above. The "pizza" box is link with two associations - one with "Delivery pizza" task and the other with "Receive pizza" task. Using this method, no direction and flow are shown. However the payment and receipt artefacts are link with an association each to the message flow. The second method indicates a directional flow of artefact between the participants using the "message flow".
The simple association method can also be used to link useful pictorial information on the diagram. In the example, a "colourful boxes" shape is used to represent "materials" for making pizza.
Text Annotation versus Extension ElementsAnother use of extended artefacts is to provide graphical representation for different kinds of analytic information on the diagram. Hence instead of using text annotation element for all sorts of information such as risks, improvements or performance indicators; each type of analytic informations is represented by a specific shape. In the process diagram below (Figure 3) a red octagon represents risk; a spanner represents improvement; and an odometer represent performance indicator.
|Figure 3: Using Extended Artefacts for Risks, Improvements and Performance Indicators|
It is nice to have all these extended artefacts in BPMN 2.0 process diagram but it is strongly suggested to limit the number of types. Provides clear definitions and instruction of how to use them. Ensure that they are applied consistently across projects in the organisation.
Warning: As the implementation is tool dependent, using them reduces or even removes the portability of the model between tools.
ConclusionThe extension mechanism in BPMN 2.0 provides process modelling tool implementer a way to supplement the shortcoming of the core BPMN elements. <i>Yes, it depends on the tool implementer and not all tool include such extension mechanism.</i> With the extension implemented, a BPMN process model could be made compatible (in graphic representation) with other process modelling notation such as SIPOC, VAC and EPC. I will leave that to my next article - comparing process model 'drawn' in different types of process notation.
SIPOC stands for Suppliers, Inputs, Process, Outputs, Customers
VAC stands for Value Added Chain
EPC stands for Events driven Process Chain
- Object Management Group. 2011. Business Process Model and Notation (BPMN) Version 2.0 Specification
- Object Management Group. 2010. BPMN 2.0 by Example. Version 1.0