Can BPMN and EPC process models live together in the same ARIS Cloud environment, within the same database, in peace and harmony and without creating conflicts with each other? If yes, what are the main concepts and requirements to make this work?
I am asking because our consultant is saying we must pick one or the other, because (a) they don't get along and will create conflicts, and (b) we need one standard for our entire company. I do not understand what are the problems they are talking about in (a) and that is the subject of this post. Regarding part (b); I think we should use the model that is best suited to the purpose. I see EPC as being much more business-friendly than BPMN, and I don't see why we would force the business to deal with all the complexities and difficulties of BPMN, if there is no reason to do that (such as RPA). So I want to address any technical issues before I advocate for the use of both.
I would think that the objects, attributes, and relationships should work correctly and consistently across both model types to provide one coherent and integrated database, I cannot understand why that would not be the case.
General comments on the overall approach (picking one versus making both available), and the specifics (such as selecting the correct connections and attributes to make it work) will be very much appreciated.
Thanks In Advance,
John
M. Zschuckelt on
Hello John,
there are certain points your consultant is probably trying to point out:
EPC and BPMN use the same terms, but there may be differences in what they are used for. E. g. an "Event" is quite differently used in BPMN and EPC. Certain difficulties you may have in EPC like "which process does the event belong to?" at the process interface do not occur in BPMN, because BPMN processes don't share events. They communicate via message flows.
I fully agree with your evaluation of the two notations. There may be different reasons for using both notations:
- different parts of the business have different legacy process assets, e.g. due to cultural background or M&A events
- You use EPC for the business level and BPMN in its full beauty for the technical design description, including backend service integrations and the like.
You definitely have to strip down the BPMN vocabulary for business-oriented processes. I have seen projects fail because business people started interpreting the technical details of the BPMN notation instead of focusing on describing their business need. They are not developers.
So regarding the confilicts: Listen to your consultant what he has to say about them and deal with them in a conscious way. Define what level of detail you want to have in each notation. Define how the two worlds shall be linked, when processes in both notations interact with each other.