Hi,
Were looking into transforming to BPMN but there are at least 4 or 5 model types for this. Can you please explain the difference between those model types? And also, just to clarifym does it still need FADs?
BR,
Julie
Best Reply
Hello,
There are basically 4 BPMN model types. 2 of them are the "Standard" BPMN 2.0 model types Collaboration and Process. They have Lanes in the Collaboration model, which have the object type "Lane". That represents the unspecific layout element that the BPMN 2.0 specification defined. If you want to attribute any meaning to your lanes (such as roles, applications) it is up to your imagination to interpret it this way or you need to assign another model type to the Lane, where you somehow explain what you mean. This is anything but practical and a lot of hassle to maintain.
The other two model types are called "Enterprise BPMN" Collaboration and Process. They are the younger sisters of those above. Here you can actually add roles, org. unit or application system type objects to the model with a Lane symbol. In these cases tasks placed in the lane additionally get an automatic connection type "carries out" (for roles, org. units) or "supports" for application system types. So this is one object less that you need to declare in the FAD and it is more intuitive for a user, when you have a certain purpose for your Lanes.
FADs are not necessary any more. Since SR12 you can place all the non-BPMN objects in the EBPMN model, just like you would in an EPC. That's got little to do with the BPMN standard, because it allows you to do those things that are out of scope of the BPMN specification (see chapter 7 of the spec). So if you do that, be aware that this is your proprietary solution. It might crowd your BPMN model with all your additions.
Since SR14 you have more options with so-called "satellite modelling". Users of ARIS Elements and ARIS Advanced know this feature already. With SR14 it comes to ARIS Enterprise and it is configurable. With this feature you do not need to care about FADs any more. You define the satellite objects very much like you fill in attributes in the Properties panel. This allows you to remove the satellites from your EBPMN models, so they look like BPMN again.
Best regards,
M. Zschuckelt
2 Replies
-
Best reply
Hello,
There are basically 4 BPMN model types. 2 of them are the "Standard" BPMN 2.0 model types Collaboration and Process. They have Lanes in the Collaboration model, which have the object type "Lane". That represents the unspecific layout element that the BPMN 2.0 specification defined. If you want to attribute any meaning to your lanes (such as roles, applications) it is up to your imagination to interpret it this way or you need to assign another model type to the Lane, where you somehow explain what you mean. This is anything but practical and a lot of hassle to maintain.
The other two model types are called "Enterprise BPMN" Collaboration and Process. They are the younger sisters of those above. Here you can actually add roles, org. unit or application system type objects to the model with a Lane symbol. In these cases tasks placed in the lane additionally get an automatic connection type "carries out" (for roles, org. units) or "supports" for application system types. So this is one object less that you need to declare in the FAD and it is more intuitive for a user, when you have a certain purpose for your Lanes.
FADs are not necessary any more. Since SR12 you can place all the non-BPMN objects in the EBPMN model, just like you would in an EPC. That's got little to do with the BPMN standard, because it allows you to do those things that are out of scope of the BPMN specification (see chapter 7 of the spec). So if you do that, be aware that this is your proprietary solution. It might crowd your BPMN model with all your additions.
Since SR14 you have more options with so-called "satellite modelling". Users of ARIS Elements and ARIS Advanced know this feature already. With SR14 it comes to ARIS Enterprise and it is configurable. With this feature you do not need to care about FADs any more. You define the satellite objects very much like you fill in attributes in the Properties panel. This allows you to remove the satellites from your EBPMN models, so they look like BPMN again.
Best regards,
M. Zschuckelt
-