Procurement EPC with XOR split
An ARIS event-driven process chain for purchase requisitions, branching on an XOR connector and re-joining on an AND. The engine validates EPC well-formedness — event/function alternation and the event-cannot-decide rule.
For the business-process analyst
What this shows
A SAP-style procurement process modelled as an ARIS event-driven process chain (EPC), the notation that strictly alternates passive events ("Material need identified") and active functions ("Create requisition"). After sourcing, an XOR connector splits the flow on a real decision — an existing stock supplier versus a new supplier needing a tender — and the two paths re-converge on an AND connector that fans back out to the dispatched order and the qualified-supplier outcome.
EPC's value here is structural validation, not a computed number. The engine checks the well-formedness rules and flags violations rather than silently drawing a broken model: event/function alternation along every path, single-in/single-out multiplicity carried by the connectors, reachability from start to end, and the event-cannot-decide signature rule — a passive event may not be the source of an XOR/OR split. That's why the decision routes through function F2 before reaching the XOR, which is the correct ARIS form.