Hello,
I am newby in ARIS Architect & Designer, I have tried to transform EPC to BPMN using the feature solution design and model generation. I want to know transformation rules for mapping EPC to BPMN, I have tried browsing and found this document (https://bpt.hpi.uni-potsdam.de/foswiki/pub/Public/OryxResearch/TransformEPC2BPMN.pdf). However, I think it's different. The document explains the rules of transformation from EPC to BPMN on OryxEditor.
Are there specific documents that explain the rules of transformation from EPC to BPMN at ARIS Architect & Designer?
Thanks
Fauzia
Hi Fauzia,
please refer to the ARIS Architect Online Help. There is the chapter "Special topics and functions -> webmethods Integration -> Modeling conventions -> EPC modeling conventions". In order to understand the use-case of the EPC -> BPMN transformation offered in ARIS please also take the entire chapter webmethods Integration into account.
Recently there was a similar thread on this topic with a very good comment by pica:
https://ariscommunity.com/users/1499272/2019-12-26-can-we-transform-epc-models-bpmn-20-models
In essence: If your use-case is exactly the same one the transformation was designed for and you followed the modelling conventions for the EPCs this may prove a useful feature. If you have different aims with your transformation you will have to make a business case and implement something individually. EPC and BPMN have different modelling scopes hence there is no one-fits-all transformation. You have to make quite a few decisions on how you want your EPC to be mapped to BPMN. The built-in transformation was designed to have a business view (EPC) translated to a BPMN process to be used as the starting point for a solution design that eventually could be implemented in webmethods Designer. This way you could keep business process and implemented process in sync.
Best regards, M. Zschuckelt
Hi,
I looked through that paper. It is a bit dated, since it discusses BPMN 1.1. While essentially the conclusions of the author are valid, they are not the only possible mapping to BPMN. The extended EPC is discussed very briefly. Indeed many satellite objects you might find in eEPC are entirely out of scope of BPMN. Roles are not mentioned, which are nowadays probably the most important object type of the eEPC, but what is said about positions fits roles even better.
The ARIS transformation supports the mapping of functions "supported by" IT services. They will be mapped to Service tasks, while functions "carried out by" roles will be mapped to User tasks.
The author's remarks on the usage of process interfaces are a bit vague. Usually they are not used for layering process levels of different degree of detail, but only for connecting processes at the same level of detail. There are several threads discussing "process interfaces" in BPMN, which do not exist as such. BPMN processes always collaborate through the exchange of messages across Pool borders.
