Event-driven Process Chain (EPC) Organizations use EPC diagrams to plan business process workflows. There are a number of tools for creating EPC diagrams, such as the ARIS toolkit and ARIS Express, Microsoft Visio, Adonis from BOC Group, Mavim Rules from Mavim BV, Business Process Visual Architect from Visual Paradigm. Some of these tools support the tool-independent EPC data exchange format, the EPML markup language. EPC diagrams use several kinds of symbols to show the control flow structure (sequence of decisions, functions, events, and other elements) of a business process. The EPC method was developed by August-Wilhelm Scheer as part of the work on the creation of ARIS in the early 1990s. Used by many organizations to model, analyze and reengineer business processes.

Using MS Visio In Visio 2013, the Business category includes the EPC Diagram template that you can use to create an Event Driven Process Chain (EPC) diagram to document business processes.

Conclusions Using the Microsoft® Visio® software tool is convenient, simple and accessible as a graph plotter for process models, but is not a modeling tool in the full sense. In professional modeling tools, objects and their properties are stored in database cells, which allows you to perform various operations with them. However, when using complex simulation systems, the acquisition, installation, development and serious support of such systems is required. This is justified only in those cases when there is a real need to use all the possibilities of databases to the fullest extent. Your choice will depend on the scope of application: whether you need a "light" solution or a professional software product.

Dmitry Pinaev / Modern technologies management

One of the most urgent problems facing modern Russian company is the improvement of business processes and the management system as a whole. Using Microsoft Visio 2003, a business analyst can simplify and speed up the basic work of describing a company's management system.

Description of the control system

Optimally designed business processes are able to implement strategic goals organization, as well as provide the ability to system analysis to make informed business decisions.

Today, management consultants, strategic and organizational development specialists, IT specialists and quality managers are engaged in the formalization and documentation of management systems. In doing so, they most often face the following tasks:

• description and optimization of business processes;
• designing a management system for a new business area;
• implementation automated systems management;
• building a quality management system.

The description of the management system, as a rule, includes a model of the company's business processes, organizational structure and documents fixing official duties and the responsibility of company employees for a particular process.

Company business process model

The model describes the company's activities in the form of a system of business processes and shows what is done in the company and what results are obtained as a result. A business process is a purposeful sequence of actions leading to a given result that is valuable to the company. Most in a simple way building a business process model is the use of one of the common graphic notations, while the business process is depicted using a diagram using special graphic symbols.

Organizational structure

The organizational structure shows the hierarchy of positions and departments in the organization and includes the distribution of the main functions of the enterprise, areas of responsibility and authority along the hierarchical management ladder.

Graphically, the organizational structure is depicted in the form of a diagram, on which units and units are shown in blocks. officials companies, and lines - the relationship of subordination between them.

To date, most business modeling technologies are based on the use of graphical charts. With this in mind, Microsoft has included in its business diagramming system Microsoft Visio 2003 special tools for describing business processes and organizational structure of the company.

For modeling business processes, Visio 2003 offers business intelligence templates for creating 7 types of diagrams:

1. basic flowchart;
2. Cross-Functional Flowchart (vertical or horizontal traces);
3. EPC (Event Driven Process Chain);
4. IDEF0;
5. DFD (Data Flow Diagrams) in two notations: Hein-Sarson and Jordan-De Marco;
6. WFD (Work Flow Diagram)

Of these notations, IDEF0 and EPC are the most popular.

The IDEF0 modeling notation is based on the SADT (Structured Analysis and Design Technique) methodology.

Diagram of the "Purchase of goods and materials" process, depicted using IDEF0 notation

The elements of the IDEF0 notation graphical language are Processes (represented by a rectangular block) and Arrows denoting the inputs and outputs of the process. In total, there are 4 types of arrows, which differ depending on which side of the rectangle they are attached to.

Arrow Types of IDEF0 Notation

Such a designation reflects certain system principles: inputs are converted into outputs, control limits or prescribes the conditions for performing transformations, mechanisms show who performs or with the help of what a function is performed.

Another important principle of the methodology is the hierarchical decomposition of processes (works): a process can be represented as a sequence of its constituent subprocesses. Decomposition can be performed to the required level of detail in the description of the process.

The IDEF0 notation is typically used to describe business processes. top level companies. It allows you to simply and visually depict the composition of the main processes, the outputs of business processes, depicting the desired result of their implementation, and the inputs, showing what resources are needed to obtain the result.

To provide navigation through hierarchical business process models, Visio 2003 allows you to create hyperlinks from one diagram to another. For example, you can specify that when you click on a process, a page opens with a diagram of its decomposition.

Order Processing process diagram depicted using EPC notation

To describe the business processes of the lower (operational) level, you can use the EPC notation developed by the Institute of Information Systems of the University of Saarland (Germany) in collaboration with SAP AG. A key feature of EPC diagrams is the description of a business process as a sequence of alternating events and functions.

The main graphic elements of the EPC diagram:

• functions,
• developments,
• organizational units responsible for the performance of functions,
• information or material objects that are used in the performance of functions,
• connectors (AND, OR, XOR).

Unlike IDEF0 notation EPC notation allows you to conveniently describe the non-linear execution of a business process. With the help of connectors, you can designate some process functions that are performed in parallel, and some only when certain conditions occur.

The second step in describing the company's management system is to build a model of the organizational structure. To solve this problem, Visio 2003 includes the Organization Chart template, which allows you to quickly create a hierarchical diagram of the positions and divisions of the company and define their parameters.

Organizational structure

The Organization Chart template contains a set of graphic elements denoting job types:

• executive - senior manager,
• manager - leader,
• position - position,
• consultant - consultant,
• vacancy - free vacancy,
• assistant - assistant.

If the organization chart is large and difficult to fit on one sheet, then Visio 2003 allows you to break the organization chart into multiple pages. Once the top part of the org chart has been created, it can continue to be described on a new page starting from the selected department. Elements denoting the same department on different pages will be synchronized with each other when changing the name and parameters of the department.

Process owners

After describing the organizational structure, it is necessary to determine the owner of the process from among the leaders and managers of the company. The owner is a person who is responsible for the result of the process and has the authority to manage the resources (material, labor, etc.) necessary for its implementation. In order to assign a process owner on the IDEF0 diagrams, you need to create a user parameter "Process owner" for all processes and enter the position name from the organizational structure into it.

Filling in process properties

According to the developed business process models, Microsoft Visio 2003 allows you to generate reports in the following format:

• Microsoft Excel Pages,
• web pages (HTML file),
• visio shape to embed the report as an Excel spreadsheet directly into a Visio diagram,
• XML file.

For example, to get a report on processes indicating process managers, you need to configure the report by specifying the required columns and start its execution.

Generated report on processes in Microsoft Excel format

A distinctive feature of Visio 2003 is the simplicity and convenience of creating diagrams and integration with other products Microsoft office. Thanks to this, specialists who saw Visio for the first time, within a few hours, begin to create business process diagrams and organizational structures and use these charts in Microsoft Word documents.

For process simulation we will use Microsoft Visio 2010, but everything written is applicable to other versions.

Before starting work on the process model, it is necessary to select and, if necessary, adapt notation- a set of graphic elements that will be used when building a diagram. In Microsoft Visio, such graphic elements are grouped into special templates(stencils): a template for a functional block diagram (cross-functional flowchart), a template for EPC (event-driven process chain - an analogue of the diagram type of the same name in ARIS), a template for a value stream (one of the visualization methods used within the " Lean Manufacturing"), etc.

We will take the first of these templates (see Figure 1) and adapt it in some way.

Rice. 1. Choose a Visio Template

In template stencils (there are three in Visio 2010), you can find basic elements. When modeling the process, we will use only some of them. And, in order to make further work more convenient, it is better to place the elements we need in a separate set, after which we adapt and supplement them a little (see Fig. 2). The set shown in the figure can be downloaded.

Rice. 2. A set of elements for modeling processes

Let's give a brief explanation of the elements in the set:

1. Process- a component denoting the activities of the employees of the organization, carried out as part of the described process and aimed at obtaining a result.
2. Event- some fact that can be discovered and identified by the employees of the organization. Processes are executed as a consequence of the events that have occurred, and, in turn, generate new events.
3. Document- specially structured information placed on paper or electronic media.
4. Logic "AND"- a relationship between the objects of the diagram, showing the need for a logical association of several objects. For example, if the "AND" includes two events, this means that the further passage of the process is impossible until both of these events occur. If two events come out of "AND", this means that both one and the second event always occur (in this case, the events do not have to occur simultaneously).
5. Logical "OR"- a logical connection between the objects of the diagram, showing the variability of the process. For example, if the "OR" includes several events, this means that the further passage of the flow is possible when any of these events occurs. If several events come out of "OR", this means that any combination of these events can occur: either one of them or several.
6. Exclusive "OR"- a logical connection between the objects of the diagram, showing alternatives. For example, if multiple events are included in the exclusive "OR", this means that they are alternative, mutually exclusive ways of initiating further flow. If multiple events come out of an XOR, this means that only one of them can occur at the output, all the others are excluded.
7. Resource- a material or information object involved or formed in the process.
8. Subprocess- an activity for which there is a decomposition diagram.
9. External process- activities of the organization that are outside the scope this process, which is also formalized as a process (more precisely, as a component of the activity model).
10. External organization- a third-party organization whose activities are not described within the framework of this model.
11. Track- a horizontal role track in the diagram, the title of which indicates the performer (organization, division, position or role) and within the boundaries of which all processes are placed, for the execution of which this performer is responsible.
12. Separator- a vertical line, with the help of which one of the stages of the described process can be marked on the diagram (it is desirable to mark all other stages in the same way).

In fact, the proposed notation is a symbiosis of two "classical" notations - Cross-functional flowchart and Event-driven process chain. As you can see, within the framework of the described approach, the traditional element of functional block diagrams - "decision" is not used, instead, an explicit designation of events is used, indicating the logical relationships between them. This provides a relatively greater visibility, flexibility and the possibility of a more complete description of the logic of the process.

I am often asked - what to read about business processes?
One of the best sites on the Runet is www.klubok.net. I myself "grew up" on the forum and articles on this site. Many articles have not lost their relevance even now. I recommend starting with him.

But if we talk about books, I can confidently say best book about business processes is a book written by Repin and Yeliferov: "Business processes of the company. Construction, analysis, regulation".

Description of business processes: striving for simplicity.

The article deals with the issues of choosing a notation for describing processes for the purpose of subsequent regulation. Frequently used Work Flow notations are compared with each other, such as: "Simple flowchart" in MS Visio, "Procedure" of Business Studio, ARIS eEPC notation and others.

When comparing notations, the focus is on creating simple and understandable process diagrams for employees of the organization.

For business analysts of companies, the theses discussed in the article are a serious reason to think about how effective the approaches they use to develop graphical diagrams of organizational processes are.

Introduction

One of the most important goals for the formation of graphic process diagrams is their subsequent use in the regulatory documents of the organization. As a rule, these schemes are used by employees who are not trained in complex notations, do not have system analysis skills, etc. For them, simplicity and clarity of schemes are very important. Complex, intricate schemes containing many different symbols, are poorly perceived by people, which makes it difficult for them practical use. Therefore, for practical purposes, the correct choice and use of the notation (method) for describing processes is important. By what criteria should such a notation be chosen? How to compare different notations with each other? Let's look at some popular notations and try to answer these questions.

Notation Comparison

The following process description notations were chosen for comparison:

1. "Simple flowchart" (with displaying the movement of documents, using the "Decision" block);
2. "Simple block diagram" (without displaying the movement of documents, without using "Solution" blocks);
3. "Procedure" business systems Studio (one of options representation);
4. ARIS eEPC.

A simple and intuitive process was chosen as a test case. The results of the description of this process are presented in fig. 1-4.

Rice. 1. Process diagram in the notation "Simple flowchart" in MS Visio (with the movement of documents, using the "Solution" block).

On the diagram of Fig. 1. The sequence of process operations in time is shown with thick arrows, and the movement of documents is shown with thin dotted arrows. Blocks "Solution" are used in a classic way. They display information (questions) on which the subsequent course of the process “depends”. This approach to the use of "diamonds" is very common. But in fact, the entire logic of decision-making and the formation of certain outputs (documents) should be contained within the operations of the process. If you think about it, the value (meaning) of drawing these "diamonds" is not obvious. What are these objects: process operations, events? It seems to be neither one nor the other. These are rather statements for making a decision on some condition. But after all, we are developing a process diagram for people, and not writing a computer program in a special language. In a computer program, "diamond" would be a full-fledged operation for comparing conditions, and so on. But on the process diagram, you need to show real objects - processes performed by people, documents, Information Systems etc. Think about it, is it correct to show “diamonds” separately from the process operation on the diagram? Instead, you can:

a) describe the decision-making logic in the form of a sequence of operations on the scheme of the process under consideration;
b) describe the logic in the form of a diagram of the steps of the corresponding sub-process, moving to the level below;
c) describe the logic in text (in the text attributes of the operation) and subsequently bring it into the process execution schedule.

Let us formulate the “pluses” and “minuses” of the above (Fig. 1.) method of using “diamonds”.

"Simple flowchart" in MS Visio (with the movement of documents, using the "Solution" block)
"Pros"	"Minuses"
Visual display of the "logic" of the choice of certain outputs of the process. Focusing the performer's attention on the decision point / process branching depending on the conditions.	Removing the decision-making logic “outside” of the process operation (incorrect from the point of view of the formal decomposition of processes). It is inconvenient to document the process (you have to duplicate the “diamonds” with text when forming a text description of the operation). The process diagram becomes information overloaded. "Diamonds" are often used too formally, without a real need.

On fig. 2. shows an example of the same process, only described without the use of "Solution" blocks and documents. It is easy to check that there are 24 less graphic elements in this diagram than in the diagram in Fig. 1. Scheme fig. 2. looks much simpler. From the graphic elements it does not dazzle, but from the point of view of informativeness, this scheme is quite understandable and accessible to the end user. If for each operation of the process the requirements for its implementation are described in text, then by combining the tabular and graphical forms of presentation, it is possible to adequately describe the procedure for the execution of the process for company employees.

Rice. 2. Process diagram in the notation "Simple flowchart" in MS Visio (without the movement of documents, without using the "Decision" block).

"Pros" and "cons" of the graphical representation of the process in the form shown in fig. 2. are shown below.

In general, the use of schemes in a format similar to that shown in Fig. 2 is convenient for both developers and employees working according to these schemes.

On fig. 3. the process diagram is presented, formed in the "Procedure" notation of the Business Studio modeling environment. The scheme has several features. Firstly, the "Decision" blocks are not used in a standard way - not as a graphic element for displaying a question and branching, but as a full-fledged decision-making process operation. In Business Studio, a “diamond” has almost all the attributes of a full-fledged process, but cannot be decomposed (perhaps the system developers will make this possible in due course). Using a "rhombus" (instead of a quadrilateral) makes the diagram clearer. At the same time, any textual information can be entered into the diamond attributes: description, beginning, end, deadline requirement, etc.

The second feature of the process diagram shown in Fig. 3., is the use of arrows. To display the sequence of operations, you can use an arrow with a single tip - the "precedence" arrow. You can use an arrow with two tips to show the movement of documents. But it is in Business Studio that you can use only one type of arrow - the "precedence" arrows. At the same time, the required number of documents, which are defined in the directory of activity objects, can be attached to the named arrows. This approach makes it possible:

• significantly reduce the number of graphic elements on the process diagram, and at the same time:
• put in the process schedule necessary information about incoming and outgoing documents.

Thus, without cluttering the diagram with unnecessary elements, we can, nevertheless, fully describe the process and upload all the necessary information to the regulations.

"Pros" and "cons" of the graphical representation of the process in the form shown in fig. 3. are shown below.

Rice. 3. “Procedure” of the Business Studio system (variant with non-traditional use of “Solution” blocks).

In the case of using Business Studio, the "Procedure" notation can be used in slightly different ways. The author of the article tends to the approach presented in Fig. 3.

On fig. Figure 4 shows a diagram of the process under consideration, developed in the ARIS eEPC notation. Note that some operations of the process did not fit on the diagram. This incomplete diagram of the simplest process, made in ARIS eEPC notation, contains four logic statements and eight events! The person reading the diagram must be able to correctly interpret all of these logical operators. Without special training and some skills in reading such diagrams, an ordinary employee is unlikely to be able to understand the logic of the process in question without a detailed textual description or the help of a qualified business analyst.

Note that the process diagram in the ARIS eEPC notation takes up significantly more space than the diagrams shown in Fig. 1-3. The complexity of the formation of such a scheme is also significantly higher.

Process diagram in ARIS eEPC notation (built in Business Studio)
"Pros"	"Minuses"
When forming the scheme, a strict, formal logic of the process is maintained. All events occurring during the process are clearly defined.	Difficulty of perception. Significant complexity of the formation of the scheme. Employees should have special skills and experience in interpreting such schemes. information redundancy. Takes up too much space, which is inconvenient for documentation.

In general, if you are not going to buy SAP R / 3, then the choice and use of the ARIS eEPC notation is not, from the point of view of the author of the article, optimal solution. It is worth paying attention to more visual and intuitively understandable notation for process descriptions. However, for some, the ARIS eEPC notation may seem more clear and understandable. To a certain extent, it's a matter of taste.

Rice. 4. Process diagram in ARIS eEPC notation (built in Business Studio).

Description of the process for subsequent automation purposes

It is interesting to look at the process diagram in question if it is described in the BPMN 2.0 notation. This notation is intended to describe "executable" processes, i.e. processes supported by the BPM system.

Your opinion on using BPMN 2.0. shares A.A. Belaichuk - CEO"Business Console" company:

On fig. 5 shows the same process in BPMN notation. As we can see, this figure is similar to Fig. 1: in BPMN notation, tasks are represented by rectangles, forks - by diamonds, data - by an icon similar to a document. Control flows are solid lines, data flows are dashed. It should be noted that only a small part of the BPMN notation is involved in this diagram: only one type of fork out of 5 available in the palette, one type of task out of 8. In addition to a wider palette, this notation is distinguished by the ability to model not only an isolated workflow, but also several processes interacting with each other through messages or data. In addition, this notation is more strict: it defines not only icons, but also the rules by which they can be combined with each other. The need for such rules is dictated by the fact that the BPMN notation is focused not only on the fact that people will read it, but also on direct execution by a special software- "engine" BPM-system. At the same time, as shown given example, when using a limited subset of the BPMN palette, it turns out to be no more complicated than a familiar flowchart. Well, for those who want to master BPMN professionally, we recommend specialized training www.bpmntraining.ru.

Rice. 5. Process diagram in BPMN 2.0 notation.

Life practice

On fig. Figure 6 shows a fragment of a process diagram developed by business analysts of a very specific company in the notation they invented. The scheme is built using the principles of the "Simple block diagram" - the "Solution" block is used in its classic version. In addition, the diagram shows many other symbols used in a non-standard way.

When forming the scheme of Fig. 6, business analysts obviously "fought" for visibility and maximum clarity for the average user. They sought to minimize, or even eliminate, textual commentary on process diagrams. The performers simply printed an A3 format diagram, when reading which everything immediately became clear: what to do, how, what documents to use, etc.

The scheme under consideration is, of course, not an example of simplicity and clarity. But it was formed in order to convey the maximum of useful information to the executors of the process.

conclusions

So, it is obvious that when describing processes, one should strive for simplicity and understandability for employees.
The use of complex, formalized notations when describing processes leads to:

• difficulties in the use (interpretation) of schemes by ordinary employees;
• the impossibility (difficulty) of organizing work on describing processes by employees of departments who have not undergone special training;
• a significant increase in the labor costs of business analysts for the formation of schemes;
• additional difficulties in documenting circuits (large volume, etc.);

Therefore, do not clutter up the process diagram with various graphic elements. But even if they are used, it is better that they carry useful information for employees, and are not simply a consequence of the formal application of modeling notations.

V.V. Repin, Ph.D., Associate Professor, Executive Director of BPM Consulting Group LLC, Head. Department of Business Process Management NOU HPE "IEF "Synergy", founder of the portal www.FineXpert.ru

It is these simple principles that I am trying to convey to business leaders who are fascinated by beautiful presentations. software products often forget that a simple checklist is often better than 10 pages of regulations.

In this lesson, you will learn about building simple (top-down diagram, data tracking diagram, process scheduling diagram, etc.) and functional block diagrams (displaying the relationship between a business process and departments).

Simple block diagram

The Simple Flowchart template is designed for designing flowcharts, top-down diagrams, data tracking diagrams, process planning diagrams, and structural forecast diagrams. The template contains the necessary shapes, connectors, and links.

Exercise 1

Rice. 3.3.Simple block diagram (step 3)

8. Enter text in the flowchart shapes (see Figure 3.4). To enter text into a shape, follow these steps:

9. Tab home in a group Service select tool Pointer.

• Click the shape in which you want to enter text.
• Type in the desired text.

Note:

1. To zoom in on the figure, press the keyboard shortcut + and left-click on the shape until you reach the desired scale.
2. To zoom out on the figure, press the key combination on the keyboard + and right-click on the shape until you reach the desired scale.

Rice. 3.4. Simple block diagram (step 4)

Figure numbering in a block diagram

Visio can number the shapes in a flowchart. To specify numbering options, on the tab View in a group Macros click the button add-ons and select in the group Additional Visio Solutions command Figure numbering. In the opened window Figure numbering specify the desired numbering options and click the button OK.

Task 2

1. In the flowchart prepared during task 1, add automatic numbering of all figures (see Fig. 3.6).

   For this:

   • On the tab View in a group Macros click combo button add-ons, select a group Additional Visio Solutions, and in it the command Figure numbering.
   • In the opened window Figure numbering specify parameters
     • tab General:
       • Operation - Autonumbering;
       • Apply To - All Shapes;
       • Start at - 1;
       • Interval - 1;
       • Select the Continue numbering shapes when dragging onto page check box.
     • On the tab Additionally:
       • Place number - Before the text of the shape;
       • Numbering order - Left to right, top to bottom;
       • Check the box Exclude connecting lines.
     • Click the button OK.
2. Save the block diagram.

Rice. 3.6. Simple block diagram (step 6)

Changing the flowchart

Adding a shape between two other shapes

To add a new shape between two other flowchart shapes, drag the new shape onto the connector connecting the shapes between which the new one is inserted. Visio inserts the new shape between the existing ones and automatically expands the flowchart.

Deleting a shape

To remove a shape from the flowchart, select the shape and click on keyboard.

Renumbering figures

To renumber the flowchart shapes, do the following:

1. On the tab View in a group Macros click the button add-ons and select in the group Additional Visio Solutions command Figure numbering.
2. In the opened window Figure numbering tab General select radio button Renumber in the same order, specify starting number for numbering and click OK.

Task 3

1. Modify the flowchart prepared in task 2:
   • Delete figure Document(Submit application).
   • Between figures Solution(Application is completed correctly) and Document(Send rejection) place the figure Process(Forward to trade show assistant).
   • Add a Shape Process(Call exhibitor about payment) below figure Document(send invoice).
   • Renumber the flowchart shapes in the same order, starting with the initial number - 1.
2. Save the block diagram.

Rice. 3.7. Simple block diagram (step 7)

Repositioning connected shapes

Once the connection of the flowchart shapes is created, you can completely reposition them and rebuild the connections. To do this, on the tab Constructor in a group Layout click combo button Change page layout and select the desired layout.

If you change the flowchart layout, it may not fit on the document page. In this case, change the page size (tab Constructor, Group Page settings, the Size combo box) or its orientation (the Constructor, Group Page settings, combo button Orientation).

Task 4

Function block diagram

Purpose of Layout Functional Block Diagram

Layout Function block diagram is designed to display the relationship between a business process and organizational or functional units, such as departments responsible for performing the steps in this process.

The lanes in a flowchart represent functional units, such as departments, positions, or some other function. Each shape representing a step in the process is located in the track of the functional unit responsible for that step.

Task 5

Adding, moving, deleting a track

For additions tracks into a functional block diagram, do one of the following:

• Right-click an existing track on the diagram and select the item from the context menu. Insert "Track" before or Insert "Track" after.
• Hover your mouse over a corner of one of the tracks. Click the blue arrow that appears Insert path shape.
• On the tab Function block diagram in a group Insert press the button Track. The track will be added after the selected track or at the end of the strip if no track is selected.
• From a set of elements Function block diagram shapes drag the track to the desired location on the lane boundary.

For displacement tracks:

1. Click the title of the track you want to move to select it. The mouse pointer will change to a move icon.
2. Drag the track to the desired location.

Shapes placed on the track will move with it. To check if a shape is on the track or just on top of it, select the shape. If the shape is on a track, the color of the track will change to yellow-orange. If the shape is not on the track but needs to be placed there, move it a bit and the track will identify it.

For removal tracks:

1. Click the label of the track you want to delete.
2. Press key on keyboard.

Note. Deleting a track also deletes all the shapes it contains.