Изменения

[[Image:Elements of an Event-driven Process Chain.svg|350px|right]]

[[Image:Elements of an Event-driven Process Chain.svg|350px|right]]

; Событие : События являются пассивными элементами в EPC. They describe under what circumstances a function or a process works or which state a function or a process results in. Examples of events are "requirement captured", "material on stock", etc. In the EPC graph an event is represented as hexagon. In general, an EPC diagram must start with an event and end with an event.

; Событие : События являются пассивными элементами в EPC. Они описывают, наступление каких событий  будет приводить к выполнению каких функций. Примеры событий: "требование зафиксировано", "материал на складе", и т.д. В EPC график событий представлена в виде шестиугольника. EPC диаграммы должны как начаться с события, так и заканчиваются событием.

; Функция : Функции являются активными элементами в EPC. They model the tasks or activities within the company. Functions describe transformations from an initial state to a resulting state. In case different resulting states can occur, the selection of the respective resulting state can be modeled explicitly as a decision function using logical connectors. Functions can be refined into another EPC. In this case it is called hierarchical function. Examples of functions are "capture requirement", "check material on stock", etc. In the EPC graph a function is represented as rounded rectangle.

; Функция : Функции являются активными элементами в EPC. They model the tasks or activities within the company. Functions describe transformations from an initial state to a resulting state. In case different resulting states can occur, the selection of the respective resulting state can be modeled explicitly as a decision function using logical connectors. Functions can be refined into another EPC. In this case it is called hierarchical function. Examples of functions are "capture requirement", "check material on stock", etc. In the EPC graph a function is represented as rounded rectangle.

|}

|}

;Логические взаимосвязи

;Логические взаимосвязи

*There are three kinds of logical relationships defined in EPC:

*Есть три типа логических взаимосвязей, определенных в EPC:

** Branch/Merge : Branch and merge correspond to making decision of which path to choose among several control flows. A branch may have one incoming control flow and two or more outgoing control flows. When the condition is fulfilled, a branch activates exactly only one of the outgoing control flows and deactivates the others. The counterpart of a branch is a merge. A merge may have two or more incoming flows and one outgoing control flow. A merge synchronizes an activated and the deactivated alternatives. The control will then be passed to the next element after the merge. A branch in the EPC is represented by an opening XOR, whereas a merge is represented as a closing XOR connectors.

** Branch/Merge : Branch and merge correspond to making decision of which path to choose among several control flows. A branch may have one incoming control flow and two or more outgoing control flows. When the condition is fulfilled, a branch activates exactly only one of the outgoing control flows and deactivates the others. The counterpart of a branch is a merge. A merge may have two or more incoming flows and one outgoing control flow. A merge synchronizes an activated and the deactivated alternatives. The control will then be passed to the next element after the merge. A branch in the EPC is represented by an opening XOR, whereas a merge is represented as a closing XOR connectors.

<!-- Actually, the branch diagram at the right must show a second operand inputting to the XOR block as XOR is a binary operation. Perhaps it may help to think an operand named "condition" entering the XOR block. Or should it be an XOR block at all? -->

<!-- Actually, the branch diagram at the right must show a second operand inputting to the XOR block as XOR is a binary operation. Perhaps it may help to think an operand named "condition" entering the XOR block. Or should it be an XOR block at all? -->

; Поток информации : Information flows show the connection between functions and input or output data, upon which the function reads changes or writes.

; Поток информации : Information flows show the connection between functions and input or output data, upon which the function reads changes or writes.

; Organization unit assignment : Organization unit assignments show the connection between an organization unit and the function it is responsible for.

; Назначение организационный единицы : Organization unit assignments show the connection between an organization unit and the function it is responsible for.

; Process path : Process paths serve as navigation aid in the EPC. They show the connection from or to other processes. The process path is represented as a compound symbol composed of a function symbol superimposed upon an event symbol. To employ the process path symbol in an EPC diagram, a symbol is connected to the process path symbol, indicating that the process diagramed incorporates the entirety of a second process which, for diagramatic simplicity, is represented by a single symbol.

; Путь процесса : Process paths serve as navigation aid in the EPC. They show the connection from or to other processes. The process path is represented as a compound symbol composed of a function symbol superimposed upon an event symbol. To employ the process path symbol in an EPC diagram, a symbol is connected to the process path symbol, indicating that the process diagramed incorporates the entirety of a second process which, for diagramatic simplicity, is represented by a single symbol.

==Example==

==Пример==

As shown in the example, customer order received as the initial event, which creates a requirement capture within the company. In order to specify this function, sales is responsible for marketing, currency etc. As a result, event 'requirement captured' leads to another new function: check material on stock, in order to manufacture the productions. All input or output data about material remains in the information resource. After checking material, two events may happen-with or without material on stock. If positive, get material from stock; if not, order material from suppliers. Since the two situations cannot happen at the same time, XOR is the proper connector to link them together.

As shown in the example, customer order received as the initial event, which creates a requirement capture within the company. In order to specify this function, sales is responsible for marketing, currency etc. As a result, event 'requirement captured' leads to another new function: check material on stock, in order to manufacture the productions. All input or output data about material remains in the information resource. After checking material, two events may happen-with or without material on stock. If positive, get material from stock; if not, order material from suppliers. Since the two situations cannot happen at the same time, XOR is the proper connector to link them together.