BPMN & EPC

Hi,

no, that's impossible. A better strategy will be to stick to BPMN 2, but assign function allocation diagrams to those BPMN activities you want to annotate with non-BPMN elements like risks, locations, etc. In that way you get:

• a standard compliant BPMN 2 model
• all the richness of the EPC notation

Hi Sebastian,

Thank you for your reply. This will be the approach I'll propose at today's process meeting.

Regards,

Damian

Hi Sebastian,

any idea how to handle RASCI Informations within the FAD. My customer defined that the R(esponsible) is named in the lane, further Informations (ASCI) should be documented in the FAD.

I there a Workaround/idea to bring the R relation with correct  FAD/EPC notation to the task?

Regards,

Martin

Hi Martin,

in a FAD you can create a connection between a function and any organisational object to denote the responsible relationship. You may want to maintain the role attribute of this relationship to distiniguish between someone responsible or someone just needed to be informed.

Search ARIS Community for rasci to get more tips on how to generate RASCI reports out of your ARIS data.

Hi Sebastian,

While the integration of EPC/BPMN using FAD is doable, the approach is not so pragmatic considering the number of FAD diagrams that could be created over the course of 100's of BPMN processes. 

Not sure what is coming with the ARIS next generation application (i.e. Version 8) but it would be nice to see a RIA model  where non-standard BPMN classes such as KPI, Location, Control, Application, etc. can be leveraged in combination with BPMN Tasks. 

For example, KPI could be dragged on top of a BPMN Task and settable as an attribute.  However, while maintained as attributes the actual values could represent the object instance values created as part of the Object Library diagrams (i.e. KPI Allocation Diagrams, Org Chart, etc).  Certainly changes the definition of what an Attribute means under the ARIS covers but very powerful!

My 2 pesos,

Craig

Hi Craig,

usually, customers tell us the story the other way around. They argue that it is not good practice to have all the information (like KPI, location, etc.) in the process model, because the process models get overloaded. So it is good practice to move this information into another diagram.

Hi Sebastian,

I would not want the to see all of the information on a BPMN diagram either.  The BPMN Tasks would encapsulate/hide the information as attributes which could be displayed in a separate window or rendered if I double click on the task.

Creating a seperate diagram for non-standard but usefuel attributes is laborious and onerous. 

This discussion really is the basis of using EPC versus BPMN wars in ARIS. Some tooling flexibility would resolve the issue.

Craig

Hi Craig,

you are always free to create your own dialogs for this kind of editing. Take a look at the macro API and the various tutorials here on ARIS Community. I doubt that the approach you are envisioning can be generalised so that it fits all customers. Not everyone will agree that maintaing stuff in attribute dialogs is more convenient than creating a diagram.