The AS-IS model or "as is" model is a model of business processes at the time of the survey of the enterprise and is built in order to understand how this enterprise functions from the standpoint of systems analysis. This model is built in order to identify errors and bottlenecks, as well as formulate proposals for improving the situation.

In the second chapter of this workshop, when studying methodologies and design technologies, we have already built a model of this business process. Therefore, in this part of the tutorial, we will only refine this model using the information obtained during the collection process.

Context model:

Title: Sale of finished products from the warehouse.

Goal: Increase sales.

Point of view: Head of sales department.

Input data: copy of the invoice, copy of the contract, order.

Output data: requirement, invoice, extract from the journal, report, refusal to complete the order.

Management: the nomenclature of fasteners, the current price of fasteners, the charter of the enterprise, the position of the sales department.

Mechanisms: employee of the sales department.

The context model is shown in Figure 18.

Fig.18. Context diagram

Let's move on to constructing a decomposition diagram. Having processed the questionnaires, we can identify the main functions: checking the readiness of the order, arranging payment, organizing issuance, preparing reports. The decomposition diagram is shown in Figure 19.

Fig.19. Decomposition diagram

Let's analyze the interview and consider real technology work of a sales employee. Based on these data, the main functions can be decomposed. The main function "Order readiness check" can be decomposed into the following actions: selection of contracts for the current date, acceptance of orders for the current date, reconciliation with the finished product log. The decomposition is shown in Figure 20.

The main function "Organization of payment" can be decomposed into the following actions: calculation of the amount of payment, invoicing, payment of the invoice. We decompose the main function "Organization of issuance" as follows: statement of requirement, notification to the warehouse about the preparation of goods, preparation of an extract for the contract department, change in the sales log. We decompose the main function "Preparation of reports" into the following actions: data analysis, data sampling, report printing. The corresponding diagrams are shown in Figure 21, 22, 23.

Fig.20. Decomposition diagram A1

Fig.21. A2 decomposition diagram

Fig.22. A3 decomposition diagram

Fig.23. A4 decomposition diagram

Since the goal of automating the workflow has been set before the designers, it makes sense to consider the workflow model before decomposing the processes. At the same time, you can go in two ways: consider a separate workflow model and decompose individual business processes using the construction of DFD diagrams.

⇐ Previous567891011121314Next ⇒

Related information:

Site search:

ARIS Value-added Chain Diagram (ARIS VAD) notation

On fig. 2.30 shows one of the most important ARIS notations - the ARIS VAD notation. A value-adding process chain diagram is used to describe an organization's business processes at the top level. As a rule, consultants using ARIS recommend identifying six to eight top-level business processes and describing them in the ARIS VAD notation. Then, the resulting top-level processes are decomposed in the ARIS VAD or ARIS eEPC notation.

Models AS-IS and TO-BE

Consider the objects of the ARIS VAD notation shown in Fig. 2.30.

The main object of the ARIS VAD notation is the Value-added chain - a process or some group of organization functions that serves to obtain added value. Objects are connected to each other by a dotted arrow, which is of type is predecessor of. This type of link indicates that one process is the predecessor of another. It is obvious, however, that in practice all basic processes are cyclical. In addition, they have feedback. Therefore, the term is predecessor of, in our opinion, is unfortunate.

Between the processes shown in Fig. 2.30, flows of material resources and information can be displayed, for the description of which you can use objects of the Cluster and Technical term types, respectively. To describe the infrastructure required to complete the process, in this example, the object types Product/Service and Information service are selected. The choice of object types for displaying real flows is rather conditional. It is very important at the beginning of work on modeling processes to determine what types of objects will be used and what objects of the real world they will display. So, in the case of the example shown in Fig. 2.30, it would be possible to show all flows (information and material) using objects of type Technical term.

On fig. Figure 2.30 also shows Organizational unit objects that represent the departments that perform the corresponding processes.

Objects are interconnected using links of a certain type (see Figure 2.30). For example, the information flow displayed by the Cluster object is incoming to the first process and is associated with it using an arrow of type is input for ("is input for"). Another example is the type of relationship executes (“executes”) between Value-added chain objects and Organizational unit. The is used by relationship type indicates that the Product/Service is being used by a process, and so on. Thus, in the ARIS methodology, the most important requirement is the correct choice and further use of links and objects of a certain type.

On fig. 2.31 shows an example of a top-level model made in the ARIS VAD notation. You are already familiar with these processes. Above, in fig. 2.16, the same process is represented in IDEF0 notation.

88____________________________ BB. Repin, V.G. Eliferov

Chapter 2 Choosing a methodology for describing business processes ________________________________ 89

The principles of constructing a top-level process diagram in the ARIS VAD notation differ significantly from the IDEF0 notation. So. in ARIS VAD notation, arrows can enter any side of the Value-added chain object. (Recall that in the IDEF0 notation, each side of the Activity object (function) has deep meaning). On fig. 2.32 shows the situation possible in the ARIS VAD notation. when a process diagram shows a set of feedback, which are understood only by the analyst who created the model.

This disadvantage of the ARIS VAD notation can be eliminated by stipulating in advance the possibility of special use of feedback, as, for example, in Fig. 2.33. Note that this approach may be criticized by ARIS specialists, as it contradicts the notation. But we adhere to the point of view that this is quite acceptable, since the top-level models in the ARIS VAD notation can really be used only as the simplest way of graphical representation of the process chain.

Concluding the review of the ARIS VAD notation, we once again focus on the fact that this notation is more illustrative and is not intended to create complex models of processes at the top level of an organization.

90 V.V. Repin, V.G. Eliferov. Process approach to management

2.7.2. ARIS eEPC notation - extension of IDEF3 notation

The ARIS notation eEPC (extended Event Driven Process Chain) is an extended chain of an event-driven process.

The notation was developed by specialists from IDS Scheer AG, Germany, in particular, by Professor Scheer. In table. 2.2 shows the main objects used in the framework of the notation.

Table 2.2 The main objects used in the construction of eEPC diagrams

In addition to the main objects listed in Table. 2.2, many other objects can be used in constructing an eEPC diagram. In practice, the use of a large number of objects of various types is impractical, as this significantly increases the size of the model and makes it difficult to read.

91

To understand the meaning of the ARJS cEPS notation, consider the main types of objects and relationships used (Fig. 2.34-2.38). On fig. Figure 2.34 presents the simplest ARIS eEPC model that describes a fragment of an enterprise's business process.

From fig. 2.34 it can be seen that the links between objects have a certain meaning and reflect the sequence of functions within the process. The arrow connecting Event 1 and Function 1 "activates" or initiates the execution of Function 1. Function 1 "creates" (creates) Event 2, followed by a logical AND symbol, "starting" the execution of Functions 2 and 3 .

A careful analysis of the ARIS eEPC notation shows that it practically does not differ from the IDEF3 notation. The most important difference between ARIS eEPC is the presence of an "event" object. This object is used to display in the model possible outcomes execution of functions, depending on which one or another subsequent branch of the process is executed. The ARIS eEPC notation is obviously called extended precisely because of the presence of the “event” object in it (there is no such object in IDEF3). On fig. 2.35 provides examples of the use of symbols of logic and events when building models in the ARIS eEPC notation.

When building models in ARIS eEPC, the following rules must be observed:

1. Each function must be triggered by an event and terminated
an event;

2. Each function cannot include more than one arrow, “I start
cabbage soup” its execution, and no more than one arrow will come out, describing
completion of the function.

In addition to these rules, there are other important requirements for the formation of models in ARIS. They can be studied using the methodological material "ARIS Methods". which is installed on the computer simultaneously with the demo version of the product, as well as in .

On fig. 2.36 shows the use of various objects of the ARIS eEPC notation when creating a business process model.

92____________________________ VV. Repin, V.G. Eliferov.Process approach to management

From fig. 2.35 and 2.36 it can be seen that the business process in the ARIS eEPC notation is a sequence of procedures arranged in the order of their execution. It should be noted that the actual duration of the procedures in ARIS eEPC cannot be visually reflected. This leads to the fact that when creating models, situations are possible when one performer will be entrusted with

Chapter 2 Choosing a methodology for describing business processes ___________________________________ 93

completing two tasks at the same time. The logics used in the construction of the SIM-YULA model make it possible to reflect the branching and merging of the business process. To obtain information about the actual duration of processes and visually display the workload of personnel in the process, you can use other description tools, such as Gantt charts in the MS Project system.

Consider examples of using the ARIS eEPC notation to describe business processes. On fig. 2.37. the business process of processing a customer order is presented. The same process is depicted in IDEF3 notation in Fig. 2.23.

The process starts with the event "Customer order received". This event triggers the "Perform Order Posting in System" function, which is performed by the Sales Manager. He uses the "Order Accounting System" to get the job done. The result of the function execution is displayed by the "Order posting completed" event. After that, the manager of the Sales Department performs the function "Perform analysis for compliance with the nomenclature." The result of the function execution is two alternative events "The order corresponds to the range" and "The order does not correspond to the range". The process is branching. To display the branching of the process, the symbol of the logical operator is used - the exclusive "OR".

The function "Notify the customer about the impossibility of fulfilling the order" can be performed in two cases: 1) the order does not correspond to the range and 2) production is not possible. To display these options on the process diagram, the symbol of the logical operator “OR”, etc. is used.

As can be seen from fig. 2.37, the process diagram in ARIS eEPC differs from the diagram in IDEF3 by the presence of objects: events, documents, application systems and positions. The schema in ARIS eEPS is visually more informative and perceived better, but the size of this schema is much larger than the size of the schema in IDEF3.

The process discussed above can also be represented in the ARIS PCD (Process Chain Diagram) notation, a variation of ARIS eEPC. On fig. 2.38 shows the business process for processing a client's request in ARIS PCD notation. When describing this process, all the objects that make up the process shown in Fig. 2.37, but they are arranged in the form of columns of a table. The first column contains events and some logic symbols, the second - functions, the third - incoming and outgoing documents, the fourth - types of application software, the fifth - the positions of employees involved in the process. This representation of the process is more "standard". It is better suited for process documentation purposes. However, the representation in the ARIS PCD notation has a significant drawback - it can be effectively used for simple (no more than five to eight functions), preferably linear, processes. It is inconvenient to display complex processes with branched logic using ARIS PCD notations, which is clearly seen in Fig. 2.38.

94_________________________________ VV. Repin. V.G. Eliferov. Process approach to management

Rice. 2.37. Process Model Example

Chapter 2 Choosing a methodology for describing business processes_______________________________ 95

in AR1S eEPC notation.

96____________________________ V.V., Repin, V.G. Eliferov.Proc Essence approach to management

Rice. 2.38. Processing example

Chapter 2 Choosing a Business Process Description Methodology 9 7

applications and AR1S PCD notations.

98 V.V. Repin, In G. Eliferov Process approach to management

AR1S Organizational Chart Notation

The ARIS Organizational Chan notation is one of the main ARIS notations and is intended for constructing diagrams of the organizational structure of an enterprise. Typically, this model is built at the start of a business process modeling project. The model reflects the existing divisions of the enterprise in the form of a hierarchical structure, as shown in fig.

The model is built from Organizational unit, Position, Internal person, etc.

The types of relationships embedded in the notation allow you to reflect different kinds relations between objects of the organizational structure. In the one shown in Fig. 2.39 example An enterprise is managed by a Director, using the relationship type is Organization Manager for. The hierarchy of subdivisions is built using links of the is composed of type. In addition, positions can be indicated - Position and the names of real employees who occupy them - Internal person, type of communication occupies.

In addition to models of the hierarchy of departments, models of the hierarchy of subordination in project teams, groups, etc. can be built. All objects reflected in the models can be used later in the formation of business process models. When building complex hierarchical structures, decomposition can be applied, for example, the structure of a subdivision can be presented in more detail.

Chapter 2 Choosing a methodology for describing business processes _________________________________ 99

Previous78910111213141516171819202122Next

Model AS-IS- this is an "as is" model, i.e. model of an already existing process/function. A process survey is an essential part of any project to create or develop a system. Building functional model AS-IS allows you to clearly fix what processes are carried out at the enterprise, what information objects are used when performing functions of various levels of detail.
Model Based AS-IS a consensus is reached among the various stages of the process on "who did what" and what each stage adds to the process. The AS-IS functional model is the starting point to analyze the needs of the enterprise, identifying problems and bottlenecks, and developing a business process improvement project. The AS-IS model allows you to find out “what and how we are doing now” before determining “what and how will be done tomorrow”. Analysis of the functional AS-IS model allows you to understand where the problem situation is, what the benefits of new processes will be, and what changes the existing structure of the process organization will undergo. Necessity Study restructuring(detection and elimination of deficiencies) in existing processes is achieved through the use of decomposition (analysis), which is carried out even where the functionality is obvious at first glance.

AS-IS Functional Model

So, for example, signs inefficiency existing processes can be:

• useless, unmanaged and duplicate functions;
• inefficient paperwork desired document not being in the right place at the right time)
• lack of feedback on control (the function is not affected by its result), input (objects or information are used irrationally), etc.

When creating an AS-IS model by an inexperienced analyst, a fairly common mistake can occur - this is the creation of an idealized model, especially when the model is created under the influence of the manager's knowledge (point of view). Usually the manager is familiar with how the function is supposed to be performed according to manuals and job descriptions and often does not know how subordinates actually perform the required functions. Therefore, models can be created, called SHOULD BE(as it should be), and carrying false information and which cannot be further used for analysis.

BPMN (Business Process Management Notation) is a business process modeling language that is an intermediate link between the formalization/visualization and implementation of a business process.

Simply put, such a notation is a description of the graphic elements used to build a business process flow diagram.

At a minimum, such a scheme is needed in order to build a business process in accordance with it and clearly regulate it for all participants.

As a maximum, it allows you to subsequently automate business processes in accordance with the existing scheme.

History of BPMN

The first version of the BPMN notation was released in May 2004 (BPMN 1.0). The next version appeared in January 2011 (BPMN 2.0). Finally, in January 2013, OMG released the version that is still mostly used today, BPMN 2.0.2.

Basic BPMN Graphic Elements

A BPMN process is any business process expressed using a notation. Processes consist of elements, each of which is indicated on the diagram with a special icon.

The elements of BPMN notation are the elements of the graphic diagram, but also the elements of the business process itself.

The notation is based on the following basic graphical elements:

• Pool and Tracks
• Actions
• Gateways or forks
• Events
• streams
• Artifacts

In BPMN 2.0, elements are represented by special icons. The creators of this system sought to ensure that the set of icons was comprehensive and provided the ability to visually display the maximum variety of business process diagrams. As a result, there are a lot of icons and with complete list can be found in the BPMN documentation, which is translated into Russian by members of the Association of BPM Professionals of Russia. Here we will focus only on the basic elements, without which no business process scheme can do. This is enough for a general acquaintance with BPMN and an understanding of the basic principles of the notation.

BPMN elements “Pool” and “Track”

The entire business process consists of pools: a set of operations + persons who perform these operations.

For example, the pool will be the entire set of actions for loading goods and sending it to the client.

In this case, the so-called “tracks” are singled out, which any pool consists of. For our example, one of the tracks will be the execution of documents related to the loading and dispatch of goods, the second track will be the physical loading of the desired batch on the car and the car's trip to the client. Both of these paths complement one another, run in parallel, but in general serve to fulfill the same stage of the business process.

BPMN element “Action”

An “action” is a unit of work performed during the execution of a business process. Actions can be either elementary (task) or compound (sub-process).

There are several types of elementary actions that differ in terms of execution:

• Multiple execution of an action within the same process. For example, the same action can be performed in parallel for each item in a sales order.
• The cyclic action is executed repeatedly while the specified condition is true.

BPMN assumes the following graphical representations for the main types of actions:

	abstract task	Used to denote a simple action or operation that has no further decomposition within the current business process.
	Subprocess	Used to display a decomposed process included in the process in question. The sub-process is described in more detail in its diagram.
	process-reference	Used to refer to one of the most frequently repeated processes.

It is worth noting here that modern BPM systems often offer a wider range of action types than BPMN offers. For example, in the business process modeling tool in the Comindware Business Application Platform, you will find graphical elements for several types of elementary actions, as well as built-in cases:

	Custom task	Used to display the task a person is performing.
	Script task	Used to display the process step, upon reaching which the script is automatically executed.
	Service call task	Used to illustrate a process step where a web service or C# script is called.
	Integrated case	Used to represent a non-standard task supervised responsible person or a group of people. Cases are used when you need to quickly organize unstructured or semi-structured activity within a process.

BPMN elements “Fork” or “Gateway”

Gateways are elements that define the branching and merging of workflows.

BPMN describes 7 types of forks. There are 2 main types:

	XOR Gateway	Used to create alternative process flows or converging control flows.
	Parallel gateway	Used to create parallel paths without evaluating any condition, or for converging flows and synchronizing the parallel branches of a process.

The two forks described above are enough to build business processes of any complexity. Other types of forks described in BPMN allow building more compact process diagrams, but many experts question this advantage, because it is unlikely that people without special training will understand such diagrams.

An example of using the XOR gate to create alternate process flows:

• Stage 7. Calling the client to evaluate the quality of service.
• 1. If the client is satisfied, fixing a positive assessment, closing the business process.
• 2. If the client is dissatisfied, find out the reason.

The further scheme can branch out strongly: if the client is dissatisfied with the delivery, then you need to contact the head of this service; and if the quality of the products, then the next step will be the transfer of the claim to the production department, or escalation (raising the hierarchical level) in order to convey information about such a claim to a higher management.

In fact, gateways are among the most responsible and difficult stages business processes. The effectiveness of the entire system largely depends on how competently all the conditions and consequences are written according to the “If ... then” principle.

BPMN element “Event”

“Event” is one of the main elements of BPMN and serves to describe what should happen (as opposed to a task, when something should be done). An event can be, for example, the signing of a contract, or a conversation with a client.

Event graphic elements in BPMN are classified in two ways:

1. Depending on the position of the event on the process diagram:

	Start event (initiating a business process)
	Intermediate event
	End event (ending the business process).

In the case of the delivery of goods, the initial event will obviously be the customer's order. Or - a call from the manager to the client with an offer to make a purchase. The final event in such a chain will be the fact of delivery, confirmed by the signature of the client.

1. By type of event, the classification is as follows:

	simple event	Represents an untyped event.
	message event	Shows sending or receiving a message.
	Timer event	Used to simulate regular events. Also, the timer can be used to simulate points in time, time intervals and exceeding the time limit.

Very often, start and end events are message events.

BPMN elements “Flows”

A flow is a sequence of actions, which is indicated by an arrow. The “flow” element shows what action after which it is necessary to perform.

	Control flow	The standard flow of control is not affected by conditions and does not pass through gateways, i.e. is uncontrollable.
	Conditional control flow	It is used to show that further execution of the process will occur on a specific thread only if the specified condition is met. A diamond at the bottom of the arrow is added if the conditional flow of control is from a process. The diamond is not added if the conditional control flow is from a gateway.
	Default control flow	It is used when it is necessary to show that the further execution of the process will occur on a certain thread only if none of the specified conditions is met.
	message flow	Used to display inter-process communication - displays the transfer of messages or objects from one process to another process or an external link.
	Association	It is used to visualize the relationship between flow elements and objects that are not flow elements (artifacts).

BPMN elements “Artifact”

Artifacts in BPMN are understood as objects that do not directly affect the execution of a business process. It can be documents, data, information.

Main types of artifacts:

	Group of objects	Used to group graphic elements that belong to the same category and improve the readability of the diagram.
	Text Annotation	It is used for clarifications to the diagram - comments and explanations that will increase the readability of the diagram.
	data object	Used to display information about the data that is processed during the process.

Benefits of BPMN

BPMN business process description has several advantages.

The first is the ease of translating diagrams into executable models using a formal business process description language.

The description of BPMN elements is understandable to most participants in business processes and often does not require any additional explanation. Using a simple graphical expression, you can draw up specific regulations that will be followed by employees.

Along with the fact that the description of the BPMN 2.0 notation allows employees to understand how business processes occur, this notation is supported by most modern instruments business modeling, which allows the import of ready-made business process diagrams into BPM systems.

Elena Gaidukova, marketing analyst, brand manager of solutions based on , partner relations specialist.

The world has been dealing with a process approach to business organization for a long time and quite effectively, and the Business Process Model and Notation (BPMN, notation) standard is a well-thought-out procedure with a correct description of business processes. Companies are constantly improving various specializations of this standard and thereby achieve a very significant increase in all quality indicators of their work. BPMN notation is understandable not only for experts of the subject area in which it was created, any worker can operate with its logical calculations.

Modeling and standardization

Simultaneously with simplicity, this standardization is the most complete model of the described business process, compiled in a machine-readable form. BPMN (when viewed in the BPMN 2.0 version of the notation) builds models of the most complex processes in business in a very powerful and expressive way, and in the most understandable system. Most importantly, along with this standard, graphical models are defined and converted into a beautifully structured and machine-readable form that is based on XML. The BPMN notation language is absolutely executable, that is, it allows you to model processes that are subsequently performed using BPMS ( automated systems business process management). Such standardization is extremely useful precisely because modelers can use some software products, and performers - others, if they support this standard.

To build a certain model, more than one version can be used (BPMN 2.0 notation (PDF) and others), sometimes the model is made up of fragments of different notations, but the way they are systematized and read is the same. An increasing number of entrepreneurs are implementing in their companies the execution of business processes based on this standard. The demand for specialists who know this modeling language is growing every day. An increasing number of people are studying the graphic elements of BPMN notation and the rules for building models. For this, there are special courses where those who wish will get acquainted with the purpose of this language, with the types of diagrams, and see the possibilities of automatic execution of the constructed models. The most interesting thing is practical experience in BPMN 2.0 notation (also available in Russian), modeling and analysis, development of a business process.

Specialists

Who is capable of describing business processes? BPMN modeling notation is easily performed by anyone involved in automation, business process development. project managers, system analysts, architects and developers computer systems, methodologists, employees of quality services. Usually these people can read technical documentation in English, participated in any analysis projects, described BPMN notation, optimized or automated business projects, or developed and maintained software. This methodology has an international status, and not a proprietary one, like many other standards, and not even a national one. That is why since 2005 they have been analyzing and reorganizing business using process modeling in BPMN notation.

This technique provided almost all users with accessible information - from the largest analysts who create schemes, and developers who implement technologies for executing business processes according to these schemes, to company executives, that is, ordinary users who are busy managing and monitoring the implementation of the built model. In this way, Business Process Modeling Notations (BPMN) bridge the gap between model creation and model implementation. Here are some of the best ideas from other methodologies. For example, for better flexibility and readability in BPMN 2.0 notation, it follows the flowchart tradition.

Symbols (elements) BPMN

Supports and develops BPMN organization OMG. This is not a meme of Internet regulars, meaning "oh mine goth", but the very famous Object Management Group, which includes more than eight hundred companies that develop standards like BPMN notation. We owe all the useful changes in new versions to the OMG developers. It was this organization that chose the promotion of the UML BPMN notation, which is used to model object-oriented systems, as a key direction. Therefore, when developing diagrams, in addition to concepts and concepts (control flow, action, data object, etc.), there are many concepts in BPMN that are characteristic of the object-oriented approach: message, exchange, and message flow.

Symbols of graphic notation are parsed according to their purpose and combined into categories. Objects - stream objects, Data - data, Swimlanes - areas of responsibility, Connecting Objects - connecting objects, Artifacts - artifacts. The control flow, data object, and flow object symbols are further subdivided into subgroups according to semantic features in order to display the specifics of ongoing events, flow branching features, execution of actions, and so on. They indicate the specifics due to additional graphic images - markers, icons placed inside the main symbol. Also, event symbols come with a different type of outline and background color.

Events by time

During the execution of a business process, various and numerous events always occur that have their impact, despite the fact that most often they are optional elements and are not displayed in the business process diagram. This is receiving and responding to a message, changing the status in documents, and much more that it makes no sense to list - a lot of events happen literally at every step. To classify them, the characteristics of each are determined. The first group - by the time of the onset. This is the start event that will show the beginning of the chart. From here, the control flow can only be outgoing, and the message flow can go both ways. The start event on the business process diagram is usually one, but you can not display it at all. Sometimes there are even several of them, if the mapping occurs with tracks, pools and deployed subprocesses. The outline of the event is shown as a thin single line.

An end event is the result of executing a business process. The flow of control only enters here, and the flow of messages still moves both to the input and to the output. The incoming stream is represented by an arrow. The diagram displays only one end event or several - they are outlined as a thick single line. An intermediate event is any of the others that occur during the execution of a business process. One stream enters here and one exits too. Only Boundary (boundary event) occurs and is processed immediately - either at the very beginning or at the end of the action. It is displayed on the contour (border) of the action, and contains only one stream - either incoming or outgoing. And such an event is indicated by a thin double line.

Events: subprocess interruption and result type

Since events during the modeling of a business process occur in a variety of ways, the next block was classified those that can interrupt the execution of an action. The first to be marked are non-interrupting events - these are intermediate or start events that occur during execution, however, initiate the outgoing thread associated with it only when the activity is completed. The contour of such an event is depicted by a dashed line. Next is a interrupting event that occurs before or after the standard action. In exceptional situations, this event needs to be stopped or aborted if missing necessary information or an error is shown during processing, if there is a need for additional actions, and the like. Here the outline is shown as a solid line.

The third kind of events is classified according to the type of result. First of all, here we need to talk about the processing initiator. This is an intermediate or start event that occurs as a result of the execution of actions and is the result of the execution of a process - standard or not. The triggering event is represented by an unfilled icon. It is necessary to add one more event to this section, which also speaks of performance, only here it is the result of processing. This is an intermediate or final event that occurs during the execution of actions and is one of the final results of the execution of the process - standard or not, it is displayed as a filled icon.

Actions

A process, depicted as a diagram, looks like an ordered set of actions that are performed to obtain a certain result. On a BPMN notation vertical diagram, from top to bottom, a sequence is specified showing the execution of a process over time. You can also trace it in the direction of the arrows of the connecting elements from left to right. The displayed actions have three main views and many varieties, each with its own icon or icon.

task - a task. Elementary action, that is, indivisible. The type or specificity of the task is indicated by a marker or icon in the upper left corner of the action symbol. The task can be Service (service), for the provision of a service, which is an automated application or web service. Send - send a message. If the message is sent at least once, the task can be considered completed. Receive - receiving a message (same principle: if a message is received once, the task is completed). The User's task is considered characteristic and is performed by the executor with the help of software and with the assistance of other employees. A task that requires manual execution is Manual, which is performed without the help of automation. Business-Rule - a business rule, according to technology, the fulfillment of this task depends on the circumstances, the choice of a method helps to set a business rule. Script - a script where the execution of operations is strictly in the order described in a language recognized by the performer. Typically, this kind of task is performed by automated means.

Subprocesses

Sub-Process - subprocess. It includes gateways in BPMN notation, workflows, events, and many other activities. Thus, a sub-process is a composite action, the parts of which are directly displayed inside the symbol on the diagram or are placed on a separate decomposition diagram. In the latter case, the main diagram should show a + sign in the center of the sub-process (bottom edge of the activity). There are standard subprocesses, but they are not enough, so two specific varieties of it appeared. This is an Event Sub-Process - an event subprocess that always starts when a start event occurs. The diagram shows it in no way related to the rest of the activities and workflows. The contour of such a subprocess is depicted by dots.

The second variety is Transaction (transaction), this is an action consisting of different operations with a successful completion, that is, obtaining a positive result. You can get a specific result only if all the components are successfully completed. If problems occur during the execution of the subprocess, the results of all previous operations will be canceled (cancel event). Such interference may be the impossibility of performing a particular operation or its incorrect performance. To avoid canceling previous events, you can try a failed operation to compensate (event compensation). The outline of such a sub-process is shown as a double solid line. To include in the diagram all tasks or sub-processes that are reused, there is a Call - a call, which is indicated in the diagram by a bold outline.

Gateways

Gateways in BPMN notation are intended to indicate the specifics of the flow of operations and their passage through parallel or alternative branches. The gateway can do without outgoing or incoming flows, but always has at least two own either incoming or outgoing flows. The marker inside its symbol specifies the gateway type. It can be Exclusive, XOR - exclusive with an exclusive "or", designed to split the flow into alternative routes. During the process, only one of the suggested routes can be activated. Skip conditions are contained next to the designator line. Inclusive, OR - non-exclusive with logical "or" gate designed to divide the flow into routes, where each is activated if the condition of the truth of the logical expression associated with it is met. Several paths can be taken in this process, but if at least one of them is not true, then the choice is impossible.

An analogue of a non-exclusive gateway is Complex (complex). The difference is that there is only one expression that determines the activation of a particular workflow. Parallel, AND - a parallel with logical "and" gateway is needed for branching or merging parallel operations. Exclusive Event-Based - An exclusive but event-based gateway that separates the workflow into alternative routes. Exclusive Event-Based Gateway to start a Process is also an exclusive gateway, the events on which it is based start the entire process. This is the start character of a process or subprocess that has no input streams. Parallel Event-Based Gateway to start a Process works in the same way - a parallel gateway, also based on events that start the process. However, with its help, you can activate several processes at the same time if the events associated with them work. Naturally, it has no incoming streams. The pictures clearly show the BPMN notation in the examples of diagramming with two kinds of gateways.

Data and streams

The data object is contained and used in charts specifically, which demonstrates the use of additional markers. Data Inputs - input data, that is, the initial information in order to start the execution of actions. Appears on the top edge of the symbol. Data Collection - a set of data, that is, an entire array or collection of data of the same type. Displayed below the symbol. The data object and the action are connected by a relationship using an association.

The standard workflow image can be supplemented in the diagram by indicating specific flows. Conditional Sequence Flow - designation of a conditional flow of operations when branching it. Shown as coming from an action (if you don't want to use a gateway in the diagram). Default Sequence Flow - the flow of operations that occurs by default, most often comes from a gateway or action, is not associated with logical expressions.

Examples and Conclusions

The start event, as the name implies, indicates the start point of a process. This is the starting point, which means the absence of any kind incoming flow. The start event in BPMN notation examples is denoted by a circle in which the center is free. Such an event can be a letter or a call from a client, for example, sent to an online store or to the website of a company that models this business process. Further, the flow of operations goes along the lines and indicates the execution of the process up to the red circle, which indicates completion, the end event. By the way, there may be several of them, and it is easy to trace where exactly the flow of operations came to an end, completing the process. No outgoing flow from the red circle is possible.

If the diagram is not in color, then the end event is highlighted with a thick circle-shaped line. For example, in practice this event may be the issuance of an ordered product that has gone all the way from clearance through processing to issuance. In the course of all this work, the diagram shows the actions that were performed on the way from the start to the end event. The action is indicated by a rectangle with rounded edges. Gateways - rhombuses. This language is understandable to users, it is only necessary to slightly familiarize yourself with the display system that is present here in the illustrations.

« In what notation is it better for us to build our business processes? ” is a fairly common and one of the strangest questions I have ever heard. The fact is that the choice of notation for business modeling depends entirely on the goals and objectives of the enterprise that has decided to move to process management.

Once again about IDEF0

It is the IDEF0 notation that is still beloved among consultants and business analysts. Most seminars and trainings on process management today are held on the basis of this notation, although I personally have already expressed my opinion on this matter in the article "".

IDEF0 is well suited for building top-level processes, that is, for displaying logical interaction between jobs. At the same time, the diagram can be decomposed, that is, each individual element can be represented as a new interaction scheme that details the selected block. Due to the display on the diagram not only of inputs and outputs, but also of "control" and "mechanism", it is possible to follow the movement and transformation of resources in your processes.

Unfortunately, many business consultants do not realize that for all the advantages of IDEF0, it is unwise to use it to build lower-level processes that detail the detailed work of personnel (WorkFlow). Firstly, the IDEF0 notation is not capable of displaying the time sequence of work execution, and secondly, it does not contain conditional transition blocks, so all processes will describe the work only linearly, and not detailed enough.

Conclusion: IDEF0 notation is suitable for building top-level processes in order to display interactions between departments and the movement of resources.

BPMN - a new look at processes

BPMN is a relatively new notation, the first version of which appeared in 2005. The notation is focused on the detailed description of workflows, and is best suited for modeling processes at a lower level. BPMN notation has one key feature- all diagrams built in compliance with the BPMN specification can be "executed" by the system in real time.

When a process is executed, its "instance" is created and the manager or owner of the process can control the execution of tasks in real time.
The ability to "execute" processes by the server requires a sufficiently high qualification of a process modeling specialist and sufficient detail of the process. For example, if the business analyst did not provide for an appropriate transition or the ability to return to the previous function, then at a certain stage the process may “stop” and not be executed, which will lead to the need to make changes to the process and restart it.

With all its merits, the BPMN notation is quite difficult to use for regulatory purposes, for example, to describe all the functions of the staff in order to analyze and generate job descriptions, departmental regulations and process regulations.

Conclusion: BPMN notation is best suited for modeling only the key processes of an enterprise, for further control of their execution in real time.

FlowChart - back to basics

In fact, there is no notation with this name, there are many variations on the theme of the usual flowchart, for example, Basic FlowChart, Сross Functional Flowchart, etc. All these notations allow you to describe workflows and distribute responsibility for the functions performed within the process. Many software products use variations of these notations to describe low-level processes in addition to describing top-level processes using IDEF0.

Business modelers can determine the level of detail of such diagrams themselves; there are no strict requirements for describing process diagrams, since these diagrams are not intended to be executed by the system in real time.

Very often, these notations are used in specialized business modeling systems to build a single integral process model of an enterprise with reference to organizational structure. Software developers also often introduce additional blocks to denote resources, documents, and so on.

Conclusion: the simplicity of modeling processes in FlowChart notations makes them ideal candidates for use in business modeling systems for the purpose of further automatic generation of regulatory documentation: job descriptions, regulations, regulations.

eEPC - we will go our own way

The authors of the eEPC notation are the well-known German company IDS Scheer AG. Like FlowChart-based notations, eEPC is designed to describe lower-level processes, but it is not based on staff functions, but on events that, in turn, already initiate the execution of any action on the part of staff. Due to this feature, standard processes are almost twice as large compared to their counterparts described in the FlowChart notation.

The functionality of the eEPC notation is redundant for the average user, it does not make sense to use all the available blocks, therefore, as a rule, when developing a process model in the eEPC notation, users first draw up a special document (modeling agreement), which stipulates in advance which blocks will be used in process model of the enterprise.

Conclusion: the eEPC notation can be used to build lower-level processes if, for some reason, the easier-to-use FlowChart notation does not meet the requirements of the enterprise for the depth of the model description.

Of course, this note does not represent the completeness of the presentation and does not reveal the features of using each notation separately, but I hope that after reading this article, questions in the style of “ Should we choose BPMN or IDEF0? ' will become smaller.

8. Select the advantages of a formal approach to the formation of an enterprise business model:

9. The disadvantages of the humanitarian approach to the formation of the business model of the enterprise are:

Topic 2. Process business model of an enterprise

2.1. Business Organization Evolution

2.2. Process approach to management, the essence of the concept of "business process"

2.3. Classification of business processes of an enterprise

2.4. Enterprise Business Process Management

Key success factors (cfu)

2.5. Evaluation of the effectiveness of business process management

Topic 3. Basics of business process modeling

3.1. Essence and necessity of business process modeling

3.2. Notations for creating business processes

3.3. Modern methodologies for business process modeling

business processes

methodology

idef3 methodology

2. Select modeling subject areas:

Topic 4. Methodology of business process quality management

4.1. Business Process Improvement Concept Systems

Kanban system

5s system

"Three" system

Quality circle system

pdca cycle

Shewhart-Deming cycle

Six Sigma

In the concept of Six Sigma

Kaizen system

4.2. Business process quality management tools

bar chart

Control cards

Stratification

Ishikawa diagram

Pareto chart

4.3. Methodological tools for quality management of individual business processes

17. What is Six Sigma?

18. Select the sequence of actions when using the Deming wheel:

20. How many cycles does the Shewhart-Deming cycle contain?

Topic 5. Resource business model of the enterprise

5.1. Resource approach in enterprise management

5.2. Essence, types and structure of enterprise resources

5.3. The dependence of the performance of the enterprise on resources

5.4. Formation of the resource business model of the enterprise

5.5. Optimization of the distribution of raw materials in the enterprise

Topic 6. Information business model of the enterprise

6.1. Basic concepts and elements of an information business model

6.2. Information environment of economic activity of enterprises

6.3. Information systems: development, types, characteristics

6.4. Cloud computing - business platform of the XXI century

6.5. Formation of the information business model of the enterprise

11. What is the information industry?

Topic 7. Matrix business model of an enterprise

7.1. Basic concepts and types of matrix models in economics

7.2. Matrix tools in the enterprise management system

Priority Matrix

7.3. Economic matrix models in assessing the effectiveness of an enterprise

7.4. Formation of the matrix business model of the enterprise in the external environment

1. What is meant by a matrix model?

2. What is a matrix chart?

14. The figure shows the matrix of indicators. Rank the indicators in order of importance to initiate improvement actions.

Topic 8. Competence-based ("3d") business model of an enterprise

8.1. The essence and main elements of the competency-based ("3d") business model of an enterprise

competencies

8.2. Methodical approach to the formation of a competency-based ("3d") business model

Annex e

Enterprises

3.2. Notations for creating business processes

Model- this is a display of any process created to solve problems. To create models, specialized languages ​​are used, such as graphics, diagrams, tables or textual descriptions and are called "notation" of business process description.

Under the methodology (notation) creating a model (description) of a business process is understood as a set of ways in which objects of the real world and the relationships between them are represented in the form of a model. A number of parameters are characteristic for each object and links (attributes) reflecting certain characteristics of a real object (object number, name, description, execution time (for functions), cost, etc.).

Business process model- applied representation (in a given notation) of the work performed by the enterprise.

In the practice of enterprises, models of different directions are used:

top-level business process model- aggregated, the most general model of the business process of the enterprise;

algorithmic business process model, reflecting the composition and logic of the work performed by the enterprise during its implementation;

streaming business process model, reflecting the material, financial and information flows of objects;

functional business process model, reflecting the functional composition of the business process, assigning the functions of the process to the performers.

In modern conditions, models began to be considered as a new type of regulatory documents. In cases where the model is developed using a special program, it is used as electronic regulation. And in terms of the application of such models, a special methodology began to develop - business engineering.

Business process description forms:

text;

tabular;

algorithmic.

To detail the process, the text description is supplemented by a description in the form of a table or an algorithmic diagram.

Application tabular form(Figure 3.2) makes the description of the process clear and simplifies its perception. Each process parameter is reflected in the designated column of the table, and is not "blurred" in the text.

Description of the business process	Responsible executor	input information	Deadline	outgoing documentation result	Business process result consumer

Rice. 3.2. Example of a tabular representation of a business process

Usage algorithmic schemes(Fig. 3.3; 3.4) it is advisable in cases where the sequence of execution of a business process (subprocesses, procedures) allows for variability in execution (serial execution is combined with parallel, process branching, etc.). Algorithmic diagrams are designed to display the logical connection of processes, moreover, they are more visual and "readable".

It is not advisable to use only one form - textual, tabular or algorithmic. The textual form is not so clear and not structured; it is difficult to reflect the logical and temporal interconnection of processes in the tabular form, and therefore it is difficult to do without an algorithmic scheme.

If only an algorithmic scheme is used, it will be necessary to indicate on it all the essential parameters of the process - performers, inputs, outputs, suppliers, customers, etc. As a result, the scheme will turn out to be cumbersome and “hard to read”, which will reduce its practical value.

To draw up algorithmic schemes, use special graphic elements(Fig. 3.5), the totality of which determines modeling notation. The most popular for describing business processes are: flowchart, Basic Flowchart, Cross-Functional Flowchart, Event-driven Process Chain,

IDEFO, 1DEF3, Data Flow Diagrams, Work Flow Diagram. The choice of modeling notation depends on its goals and on the software product used for this. Usually 3^1 or more notations are used.

Most common detail notation(methods of describing business processes) is the representation of processes as algorithms in the form of block diagrams and the description of the process in the form of a stream of objects. Object flow refers to information, documents, and other resources.