Using EEPC notation for graphic description of business processes. Description of the notation aris

Introduction Typical tasks of describing business processes

and early stages of projects, the purpose of which is the reorganization of business processes and the introduction of information systems, the leaders and specialists are most often the following questions arise:

what results from the point of view of improving the organization's activities can be achieved using the technologies for describing and reorganizing business processes;
what software is used in the project ("ARIS is better BPWIN?", "Erwin is better ARIS?", etc.);
how to model processes using the product "x";
how to analyze and identify problems with the help of the product "X";
which methodology is used to describe processes;
what to do next with the obtained business processes models.

Currently, the Russian market presents a sufficiently large number of CASE systems, many of which allow one or another to create descriptions (models) of business processes of enterprises. At the same time, there are systems oriented primarily on the creation of models of processes and uncomfortable or not intended for creating data models and settings. Obviously, the choice of the system is determined by the objectives of the project and significantly affects its entire further move. The rational choice of the system is possible when an understanding of the company's management and its specialists of several aspects:

project goals;
information requirements characterizing business processes and necessary for analysis and decision-making within a specific project;
the capabilities of the CASE systems on the description of the processes, taking into account the requirements of paragraph 2;
features of the developed / implemented information system.

Talking about the advantage of one or another system / notation is meaningless until the type and framework of the project, as well as the main tasks that this project must decide. Our article attempts to compare the most popular notations (designations adopted during modeling) used to describe business processes, and two systems that support these notations. It is assumed that this material will serve as a basis for a discussion on the problems of effective application of CASE systems for describing and analyzing enterprise business processes.

A description of business processes is carried out in order to further analyze and reorganize them. The purpose of the reorganization can be the introduction of an information system, reducing the cost of production, improving the quality of customer service, the creation of official and working instructions when implementing ISO 9000 standards, etc. For each such task, there are certain parameters that determine the set of critical knowledge according to the business process. From the task of the task of the requirements for the description of business processes may vary. In the general case, the business process model should give answers to the following questions:

what procedures (functions, work) must be performed to obtain a given end result;
in which sequence these procedures are performed;
what control and management mechanisms exist within the framework of the business process under consideration;
roles and responsibility - who performs process procedures;
what incoming documents / information use each process procedure;
what outgoing documents / information generates a process procedure;
what resources are needed to perform each process procedure;
what documentation / conditions regulate the implementation of the procedure;
what parameters characterize the execution of procedures and the process as a whole;
there is a sequence of processes, minimizing costs (including cost, time, etc.);
as far as the process is supported / will be supported by the information system.

Description of the business process is formed by notation and tool media to reflect all the above aspects. Only in this case the business process model will be useful for the enterprise, as it can be analyzed and reorganized.

Notation ARIS Organizational Chart

ORGANIZATIONAL CHART notation is one of the main notations of ARIS and is designed to build schemes. organizational structure Enterprises. As a rule, this model is built at the beginning of the project to model business processes. The model reflects the existing divisions of the enterprise in the form of a hierarchical structure, as shown in Fig. five .

The model is built from ORGANIZATIONAL UNIT, "POSITION", "INTERNAL PERSON", and others. The types of links are allowed to reflect different kinds relations between the objects of the organizational structure. In the presented in Fig. 5 Example "Enterprise" is managed by the "Director", while using the Type of Communication "IS Organization Manager For". The hierarchy of units is based using the "IS Composed Of" links. In addition, posts can be indicated - "Position" and surnames real employeesThey occupy them: "Internal Person", as well as the type of communication "Occupies".

In addition to models of the hierarchy of units, models of subordination hierarchy can be built in project teams, groups, etc. All objects reflected in models can be used in the future when building business processes. When constructing complex hierarchical structures, decomposition can be used, for example, the division structure can be reflected in a more detailed scheme.

Notations supported by BPWIN 4.0

Description of the notations IDEF0 and IDEF3

The notation of IDEF0 was developed on the basis of the SADT structural analysis and design methodology, approved as the US standard and successfully operated in many projects related to the description of enterprises. IDEF0 was extremely widespread and is, in particular, the standard in international organizations such as NATO and the IMF. The notation of IDEF3 was developed to more conveniently describe working processes (workflow) for which it is important to reflect the logical sequence of procedures. The objects of the notations IDEF0 and IDEF3 are shown in Table. 2 and.

The semantics of the construction of IDEF0 and IDEF3 models involves compliance with clear rules. Full description of IDEF standards can be found on the site http://www.idef.com/.

An example of a description of the business process in the notation of IDEF0 is shown in Fig. 8 (corresponds to the process shown in Fig. 3).

One of the features of the description of the processes in the notation IDEF0 is a clear detection of advantages and disadvantages of business processes. Works on the IDEF0 diagram are located in the order of dominance - from the upper left corner of the chart to the lower right. In the upper left corner is located either the most important work, or the work performed first. The arrows bind work, and five types of connections differ. The arrow directed from the exit of the superior work on the entrance or control of the subordinate, is a direct connection; The arrow directed from the output of the lower operation to the input or control of the higher, is feedback. No feedback, work without output or control, duplicate work indicate the imperfection of business processes.

In the notation of IDEF3, as well as in the notation of ARIS EEPC, logic symbols are used, reflecting the branching of the process. The Idef3 notation chart allows you to present the entire process, and the sequence of operations and the process execution logic is tracked.

Description of notation DFD

Notation DFD is designed to describe information flows in the organization's surveyed. DFD notation objects are shown in Table. four . The presence of "data warehouse" objects and bidirectional arrows allows you to most effectively describe the workflow and the requirements for the information system.

One of the most important aspects of the description of business processes models is reflected on the model of control influences, feedback on control and management of the procedure. In the notation of ARIS EEPC, the procedure management can be reflected only by specifying incoming documents that regulate the procedure and sequence of procedures in time (launching events). Unlike ARIS, in the notation of IDEF0, each procedure must have at least one control action (control input - the arrow from above). If, when creating a model in EEPC, only the sequence of procedures, without taking care of the reflection of control influences (for example, documents and information), the obtained models will have a low value from the point of view of analysis and further use. Unfortunately, this error is most common in practice. The Workflow model (work flow) is created, reflecting a simple sequence of procedures and incoming / outgoing documents, while the control (control) effects on functions in the model are not reflected.

Comparing two systems, it should be immediately noted that the object DBMS is used to store models in ARIS and a new database is created under each project. For the convenience of the user's user (models) can be stored in various groups, organized depending on the specifics of the project. It is quite natural that the ARIS provides various database administration functions: access control, consolidation, etc. In BPWin, these models are stored in the file, which significantly simplifies the work on the creation of the model. For group work on large projects, it is provided for the storage of BPWIN models in the Model Mart repository (comes separately). Model Mart is a storage of models for BPWIN and ERWIN and uses relational DBMS Oracle, Informix, MS SQLServer, Sybase). It provides administration, including the delimitation of access rights to the level of the model of the model, the comparison of versions, fusion of models, etc.

Often one of the disadvantages of BPWIN supporters ARIS call a limit on the number of objects on the chart. However, the experience of real projects shows that for the project, the results of which can be actually used (criterion - disorder), the number of objects in the ARIS database or the BPWIN model is 150-300. This means that with 8 objects on the same diagram, the total number of diagrams (sheets) in the model will be 20-40. ARIS Toolset databases (like BPWIN) containing more than 500 objects are actually impossible to use. It should be emphasized that the model is created to highlight and analyze problems, that is, a detailed description of the most complex, problematic areas of activity is required, and not a total description of all processes. Oddly, in the field of directors of companies, the conviction is common in the fact that a detailed description of the processes in itself is value and can solve many problems. But it is far from the truth. It is an understanding that it is necessary to describe and what aspects of the functioning of the real system to reflect, determines the success of the project to model business processes.

Aris provides substantially more opportunities for working with individual objects of the model, but precisely as a result of the excessive amount of settings, work on the creation of a model should be regulated by complex, multidimensional documentation - the so-called modeling agreements. The development of these agreements in itself is a complex, expensive and requiring considerable time (1-3 months) and qualified specialists. If the project using ARIS begins without a detailed study of such agreements, the probability of creating models of business processes that do not respond to the questions raised is 80-90%. In turn, BPWIN is easy to use and sufficiently strict regulation when creating diagrams (IDEF standard and recommendations for its use, the IDEF form to create a diagram, a limited number of required fields, limit the number of objects on one diagram, etc.). ARIS is definitely a more "heavy" tool compared to BPWIN, but in the end it turns into significant difficulties and high costs for its operation.

Conclusions. Recommendations for the use of systems depending on typical tasks

non-plant situations of the use of instrumental means of modeling business processes and their expert score on a 5-point scale are shown in Table. 7.

Positioning systems can be carried out with respect to solving the problem of modeling business processes (Fig. 13).

Thus, for maintaining small scale (small and medium enterprises, 2-5 people in the group of consultants) and duration (2-3 months) of projects rationally use BPWIN. For large and / or long projects (for example, such as the implementation of a continuous improvement system of business processes, ISO, TQM) is more suitable for ARIS. It should be noted that the ARIS ToolSet system is inconvenient to create information models, and the design and configuration of databases is not provided. In this case, preparatory work on the creation of regulatory documentation may take 1-3 months, but this is a necessary element of subsequent successful work.

August-Wilhelm Sheer. Business processes: basic concepts, theories, methods. Moscow: Enlightener, 1999.

ComputerPress 1 "2002

Introduction Typical tasks of describing business processes

what results from the point of view of improving the organization's activities can be achieved using the technologies for describing and reorganizing business processes;
what software is used in the project ("ARIS is better BPWIN?", "Erwin is better ARIS?", etc.);
how to model processes using the product "x";
how to analyze and identify problems with the help of the product "X";
which methodology is used to describe processes;
what to do next with the obtained business processes models.

project goals;
information requirements characterizing business processes and necessary for analysis and decision-making within a specific project;
the capabilities of the CASE systems on the description of the processes, taking into account the requirements of paragraph 2;
features of the developed / implemented information system.

It is pointless to talk about the advantage of a particular system / notation, until the type and framework of the project is defined, as well as the main tasks that this project should decide. Our article attempts to compare the most popular notations (designations adopted during modeling) used to describe business processes, and two systems that support these notations. It is assumed that this material will serve as a basis for a discussion on the problems of effective application of CASE systems for describing and analyzing enterprise business processes.

what procedures (functions, work) must be performed to obtain a given end result;
in which sequence these procedures are performed;
what control and management mechanisms exist within the framework of the business process under consideration;
roles and responsibility - who performs process procedures;
what incoming documents / information use each process procedure;
what outgoing documents / information generates a process procedure;
what resources are needed to perform each process procedure;
what documentation / conditions regulate the implementation of the procedure;
what parameters characterize the execution of procedures and the process as a whole;
there is a sequence of processes, minimizing costs (including cost, time, etc.);
as far as the process is supported / will be supported by the information system.

Notation ARIS Organizational Chart

The notation of Organizational Chart is one of the main notations of ARIS and is intended to build the enterprise organizational structure schemes. As a rule, this model is built at the beginning of the project to model business processes. The model reflects the existing divisions of the enterprise in the form of a hierarchical structure, as shown in Fig. five .

The model is built from ORGANIZATIONAL UNIT, "POSITION", "INTERNAL PERSON", etc., and others. The types of links are made to reflect the various types of relationships between the objects of the organizational structure. In the presented in Fig. 5 Example "Enterprise" is managed by the "Director", while using the Type of Communication "IS Organization Manager For". The hierarchy of units is based using the "IS Composed Of" links. In addition, posts may be indicated - "Position" and the names of real employees who occupy them: "Internal Person", as well as the type of communication "Occupies".

Notations supported by BPWIN 4.0

Description of the notations IDEF0 and IDEF3

The semantics of the construction of IDEF0 and IDEF3 models involves compliance with clear rules. Full description of IDEF standards can be found on the site http://www.idef.com/.

An example of a description of the business process in the notation of IDEF0 is shown in Fig. 8 (corresponds to the process shown in Fig. 3).

Description of notation DFD

Conclusions. Recommendations for the use of systems depending on typical tasks

non-plant situations of the use of instrumental means of modeling business processes and their expert score on a 5-point scale are shown in Table. 7.

Positioning systems can be carried out with respect to solving the problem of modeling business processes (Fig. 13).

August-Wilhelm Sheer. Business processes: basic concepts, theories, methods. Moscow: Enlightener, 1999.

ComputerPress 1 "2002

In this section, we consider the ARIS methodology. Currently, the market for modeling business processes is represented by the same name according to ARIS.
The ARIS methodology includes several different notations for describing the organization's activities from various points of view. The methodology integrated existing standards and specifications of descriptions of processes and data, such as IDEF3, ERD, DFD, UML, etc. The main concept of ARIS according to the organization's description is shown in Fig. 2.30.
Image in fig. 2.30 is often called "Aris house". The approach of the ARIS methodology to the description of the processes is based on the consideration of the organization's activities from four points of view: a look at the organizational structure, a look at the data (streams and structure), a look at the functions (functional hierarchies), a look at control and management (consolidated business processes) .
ARIS Methodology includes a large number of different notations that allow flexible creation of various models.

organizations. The most significant and practically used ARIS notations include: notation of the Value-Added Chain Diagram (chain champ chart adding value); Notation Nert, Extended Event-Driven Process Chain (extended notation of the process chain, managed by events) and PCD (process chain diagram); Notation Organizational Chart (organizational diagram); Notation FUNCTION TREE (functions tree); Notation Product Tree (product tree).
Fig. 2.30. Main types of models in ARIS Methodologies

The strength of the ARIS methodology (from a formal point of view) is its complexity, which manifests itself in the relationship of models built in various notations. The ARIS methodology allows you to describe the activities of the Organization from different points of view, while the models obtained are to a certain extent are interconnected. It should be emphasized that the main advantages of such a comprehensive approach are: require to implement the presence of an ARIS tool environment, expensive and quite complex to use, although there is a free, simplified version of this product called ARIS Express;
It is difficult to implement in practice, as they entertain the high consumption of resources (human, material and financial) for a long time. Notation Value-Added Chain Diagram (VAD)
In fig. 2.31 Presented one of the most important notations of ARIS - notation of the Value-Added Chain Diagram. The chain diagram of the process adding is used in describing the organization's business processes at the top level. As a rule, consultants using ARIS recommend highlighting six to eight top-level business processes and describe them in VAD notations. Then the decomposition of the obtained top-level processes is carried out, it is used either the VAD notation or non-era. Consider the main objects of VAD notation, presented in Fig. 2.31.
The main object of the VAD notation is Value Added Chain. In fact, this is a process or group of organization functions that serve to obtain value added. Objects are connected to each other with a dotted arrow having a type of IS Predecessor of ("is the predecessor"). This type of communication shows that one process is the predecessor of the other. Obviously, however, that in practice all the basic processes are cyclical. In addition, they have feedback. Therefore, the term is predecessor of, in our opinion, unsuccessful.
Between the processes shown in Fig. 2.31, models of material resources and information can be displayed. To describe them, you can use objects such as Cluster (to describe the information) and Technical Term (to describe material flows). To describe the infrastructure necessary to perform the process, the types of PRODUCT / SERVICE and INFORMATION SERVICE objects are selected in this example. The selection of object types to display real streams is sufficiently conditional. It is very important at the beginning of the work modeling work, determine which types of objects will be used and which objects real Mira They will display. So, in the example in fig. 2.31 It would be possible to show all the streams (informational and material) using TECHNICAL TERM objects.

Fig. 2.31. Model in Notation Value-Added Chain Diagram

In fig. 2.31 also features ORGANIZATIONAL UNIT, displaying organizational units that perform the appropriate processes.
Objects are binding to each other with a certain type of bonds (Fig. 2.31). For example, the information flow displayed by the Cluster object is incoming for the first process, and it is associated with it using an IS INPUT FOR type arrow ("is input for"). Another example is the Communication Type of Executes ("executes") between the objects of Value-Added Chain and Organizeal Unit. The IS Communication Type Used by By shows that Product / Service is used by the process, etc. Thus, in the ARIS methodology, the most important requirements are the correct choice and further use of relationships and objects of a certain type.
In fig. 2.32 is an example of a top-level model, made in the notation of ARIS VAD. You are already familiar with this process. In fig. 2.17 It is given in the notation of IDEF0.
The principles of constructing the top-level process diagram in VAD are significantly different from IDEF0: in the VAD arrows can enter any side of the Value-Added Chain object. (Recall that in IDEF0, each side of the Activity object (function) has deep meaning.)

3
ABOUT
§
ABOUT
ABOUT

In fig. 2.33 The situation is possible in the VAD notation, when a set of feedback is given on the process diagram, the meaning of which is clear only to the analytics model that has created a model.
The specified deficiency of the VAD can be circumvented in advance of the possibility of special use of feedbacks, such as in Fig. 2.34.
Fig. 2.33. Feedback in Notation Value-Added Chain Diagram

Fig. 2.34. Example of reverse links in the notation of Value Added Chain Diagram

Note that specialists in ARIS have such an approach can cause criticism, since the notation is contrary. But we adhere to
of the point of view that it is quite acceptable because the top-level models in the notation of VAD ARIS can actually be used as the simplest way graphic image chains of the process.
After reviewing the notation of ARIS VAD, once again focus on the fact that the specified notation is more illustrative and is not intended to create integrated models of the upper level of the organization. Notation ARIS Neck - Expansion of the Notation IDEF3
Notation ARIS Neck (Neux - Extended Event Driven Process Chain - An extended chain of the process managed by the Events) was developed by the German IDS Scheer AG (Germany) specialists, in particular Professor Sheer. In tab. 2.3 The objects used as part of the notation objects are given.
In addition to those specified in Table. 2.3 Main objects, many others can be used when constructing a diagram. In practice, the use of a large number of objects of various types is inappropriate, as this significantly increases the size of the model and makes it poorly readable.
To understand the meaning of the notation of the Neck, consider the basic types used types of objects and connections. In fig. 2.35 Presented the simplest model of the nonsense, describing the fragment of the business process of the enterprise.
In fig. 2.35 It can be seen that the links between objects have a certain meaning and reflect the sequence of performing functions within the framework of the process. The arrow connecting the event 1 and the function 1 activates (Activates) or initiates the execution of the function 1. The function 1 creates (Creates) Event 2, followed by a logical "and" symbol, which runs the execution of functions 2 and 3.
Attentive analysis of the notation of the Neck shows that it is practically no different from IDEF3. The most important difference between the Neck is the presence of an "event" object (EVENT). This object is used to display in the model of possible results of the implementation of functions, depending on which one follows
branch of the process. The notation of the nonsense is called extended, obviously, precisely due to the presence of an "event" object in it (there is no such object in the IDEF3). In fig. 2.36 An examples of the application of logic and events symbols are given when building models in the notation of non-era.
Table. 2.3. Main objects used as part of the notation ARIS Neck

№	NEMENOVA-. NIV	Description	Khigraphic representation
/>1	Function	The function "Function" is used to describe the functions (procedures, works) performed by divisions / employees of the enterprise		* "" H Function. J.
2	Event	The Event Object is used to describe the real states of the system that affect and manage the performance of functions.
3	Organizational unit	Object reflecting various organizational links of the enterprise (for example, management or department)		ija ^^ tionaui ^ it
4	Document	Object reflecting real storage media, such as paper document		Document
5	Applied system	The object reflects the real application system used in the framework of the function execution technology	BUT	I \| yplication Systjs. J? M.	m.
5	Applied system
6	Information cluster	The object characterizes the data as a set of entities and connections between them. Used to create data models
7	Communication arrow between objects	The object describes the type of relationship between other objects, such as activation of the execution of the function by some event	gt;
8	Logical "AND"		©
9	Logical "OR"	Logical operator defining links between events and functions within the process. Allows you to describe the branching of the process.	@
10	Logical excluding "OR"	Logical operator defining links between events and functions within the process. Allows you to describe the branching of the process.	®

Fig. 2.35. Notation Aris Ners

Fig. 2.36. Application of logical operators when building models in Neck

When building a model in ARIS, the nonsense must be observed the following rules: Each function is initiated and ends with an event; In each function, more than one arrow that runs the execution of the function cannot appear and exit more than one arrow describing the completion of the function.
In addition to these, there are other important rules Forming models in ARIS.
In fig. 2.37 shows the use of various objects of the ARIS non-notation, when creating a business process model.

J Activates.
alt \u003d "" /\u003e

In fig. 2.36 and 2.37 It can be seen that the business process in the notation of the Neck is a sequence of procedures located in the order of their execution. It should be noted that the real duration of the implementation of procedures in the nonsense cannot be reflected visually. This leads to the fact that when creating models, situations are possible when one performer is assigned to the execution of two tasks at the same time. The logic symbols used in constructing the model allow you to reflect the branching and merging of the business process. To obtain information about the real duration of processes and visual display of staff load, you can apply other description tools, such as Gantt graphics in the MS Project system.
Consider the examples of using the non-notation of the Neck for the description of business processes.

In fig. 2.38 A client order processing process is presented (it is also depicted in the Idef3 notation in Fig. 2.24).
The process begins with the event "entered the customer's order." It initiates the "Running order accounting" function, which is carried out by the Sales Department manager. For work, it uses the "Order Accounting System." The result of the function is displayed as an event "Order Accounting".
After that, the Sales Manager implements the "Perform an analysis of nomenclature analysis" function. The result is two alternative events: "Order corresponds to the nomenclature" and "Order does not correspond to the nomenclature." The process is branching. To display the branching of the process, a symbol of a logical exclusive "or" is used.
The "Notify Customer's Customer" function can be performed in two cases: if the order does not correspond to the nomenclature or production is impossible. To display the process of these options, the symbol of logical "or", etc. is used.
As can be seen from fig. 2.38, Process diagram in ARIS Nears differs from the schema in IDEF3 the presence of objects: events, documents, application systems and posts. The scheme in Aris is visually seemed more informative and perceived better, but its size significantly exceeds the scheme in the notation of IDEF3.
The process discussed above can also be presented in the notation of ARIS PCD (Process Chain Diagram) - varieties of nonsense. In fig. 2.39 presents the business process of processing the client's application in the PCD notation. When it is described, the same objects that make up the process in Fig. 2.38, but they are located in the form of a table. In the first column - events and some symbols of logic, in the second - functions, in the third - incoming and outgoing documents, in the fourth - types of applied softwareIn the fifth - posts involved in the process. Such a presentation of the process is more common. It is better suitable for documenting processes.

However, the PCD notation has a significant disadvantage - it can be effectively applied to simple (no more than five-eight functions), preferably linear processes. Complex processes, with branched logic, displayed with PCD is inconvenient, which is clearly displayed in Fig. 2.39.
Fig. 2.39. ARIS PCD diagram

Notation ARIS Organizational Chart
The notation of Organizational Chart is one of the main notations of ARIS and is intended for the construction of the enterprise organizational structure schemes. As a rule, this model is built at the beginning of the project to model business processes. The model reflects the existing divisions of the enterprise in the form of a hierarchical structure, as shown in Fig. 2.40.
Fig. 2.40. Model of organizational structure of the enterprise
alt \u003d "" /\u003e

The model is built from ORGANIZATIONAL UNIT, POSITION, INTERNAL PERSON, etc., etc. The types of links are allowed to reflect the various types of relationships between the objects of the organizational structure. In the presented in Fig. 2.40 Example "Enterprise" is managed by the "Director", using the Type of Communication of the IS ORGANIZATION MANARER FOR. The hierarchy of the divisions is built using the IS Composed Of Relations. Positions can also be indicated - Position, the names of their employees - Internal Person, Communication type - Occupies. In addition to the models of the hierarchy of units, models of subordination hierarchy can be built in design teams, groups, etc. All objects reflected in models can be used later when building models of business processes. When building complex hierarchical
the structures can be used decomposition, for example, the division structure reflects on a more detailed scheme. Notation ARIS FUNCTION TREE
This notation is designed to form functions tree models. An example of such a model is presented in Fig. 2.41. All functions on this diagram are connected by bonds. Topics are used by the types of IS EXECTION-ORIENTED SUPERIOR and IS PROCESS-ORIENTED SUPERIOR. The first type of communication is used to build a tree according to a functional basis (descriptions of the functions of the unit). The second type of communication is used when creating a tree of functions included in some business process.
Fig. 2.41. Model Function Tree (Function Tree)

The tree of functions can be built according to the functional, process and product principles. In practice, the first principle is often used - models of hierarchy of the functions of the unit are created. Notation ARIS Product Tree
In fig. 2.42 Presented the notation of ARIS Product Tree. It is designed to create product tree models. Models of this type can be used to describe the material inputs and process outputs.

Fig. 2.42. Product Tree Model (Product Tree)

Notation ARIS Information Flow
Notation Information Flow is an analogue of DFD and is used in constructing data stream diagrams or documents between the functions of the business processes of the enterprise. Simplicity of notation limits its areas useful use. Its main objects - FUNCTION (also used when building business processes) and Information Flow - information flow, as shown in Fig. 2.43.
Fig. 2.43. Notation ARIS INFORMATION FLOW (information flow)
information flow

When building models of business processes, the model of the nonsense can first be constructed, and then, using the functions defined during the functions, is a model of information flows. Use of several notations when creating models of processes in ARIS
When generating models of business processes in ARIS, several types of notations are used. In fig. 2.44 A diagram of applying models created in various notations is presented.

Fig. 2.44. Using ARIS notations when creating models

As a rule, work on the description of the business processes of the company in ARIS begins with the creation of a model of the organizational structure. At the same time (or later), models can be developed that describe the structure of the main material and information inputs and outputs. Using these models, models of top-level business processes in VAD notation are created. After that, models of units and other auxiliary models are being developed (for example, applied software Systems). Themes of the processes in the notation of the nec are formed. The models of the Neck are based on the already existing descriptions of the organizational structure, the functions of divisions, materials, systems, etc. The result of the work is a set of models describing the activities of the organization from various points of view.
The feature of work in full-fledged software products for modeling business processes is that the software product creates a database for objects and their attributes. With one
the parties, it allows us to consider various aspects of the interaction of model objects, choosing one of the notations (Fig. 2.44). On the other hand, a "insignificant" error when creating links between objects in one notation can significantly distort the type of diagram in other notation.

Modeling business processes is one of the methods of improving the quality and efficiency of the organization. This method is based on the process description through various elements (actions, data, events, materials, etc.) inherent in the process. As a rule, modeling business processes describes the logical interconnection of all elements of the process from its start before completion within the organization. In more complex situations, modeling may include external processes or system to organize.

Modeling business processes makes it possible to understand work and analyze the organization. This is achieved due to the fact that the models can be prepared on various aspects and control levels. In large organizations, modeling business processes is carried out in more detail and multifaceted than in small, which is associated with a large number of cross-functional bonds.

Objectives Business modeling:

Due to the modeling, you can trace what happens in processes from the beginning, before completion. Simulation allows you to get an "external" look at the processes and determine improvements that will increase their effectiveness.
Ruling processes. Modeling business processes sets the rules for performing processes, i.e. how they must be completed.
Modeling business processes establishes a clear connection between the processes and the requirements they have to perform.

ARIS. (Acronym from English. Architecture of Integrated Information Systems) - Methodology and replicable software product for modeling business processes of organizations. The product and methodology belong to the German company Software AG as a result of the absorption of the company IDS SCHEER of the author of the methodology of August-Wilhelm Sheera.

The implementation of the methodology is assumed to be engaged in a specialized software product providing joint work Above descriptions and diagrams. The first version of the product was released in 1994. By the end of 2000, the product was sold in 24 thousand organizations. Since 2009, a free version of the tool is supplied - ARIS Express.

The product provides for the server part (ARIS Server) with a centralized repository, stored in a relational DBMS and a series of user tools for maintaining objects and prepare graphic representations (ARIS Toolset in early versions, in the versions of the 2000s - ARIS Business Architect, ARIS Designer).
By the mid-2010, a public-cloud version of the product also appeared. Available at http://www.ariscloud.com/

The ARIS product is used in various projects on reengineering and optimizing business processes, IT projects such as the implementation and operation of ERP systems, in particular, there is a developed integration solution for SAP R / 3.

One of the illustrations of the structured ARIS approach to the reengineering project

ARIS software is based on Oracle Business Process Analysis Suite Business Process Process. Technically, the ARIS toolkit is quite simple for study, has an intuitive interface. Models are copied and inserted into document files (for example, Microsoft Word format) in the form of drawings.

Products ARIS provides the ability to create scripts to automate the preparation of various analytical reports, regulatory documents, new models. Each script is a subroutine that runs in ARIS Business Architect (or Toolset is an earlier version) or directly on the ARIS server. Scripts are written in a special programming language - Sax Basic. For the automated formation of a report in ARIS, the scenarios operates data from the database of models, extinguishing specific objects and models from it.

ARIS Script technology allows automatic mode produce:
formation of regulatory documents based on Aris models (for example, process passport, process regulation);
the formation of analytical reports based on Aris models;
integration of ARIS Toolset with other applications and databases;
Formation of the base of the ARIS models based on the finished specifications.

For example, any organization in the ARIS methodology is viewed from five points of view: organizational, functional, processed data, structures of business processes, products and services. At the same time, each of these points of view is divided into another three sublevel: description of requirements, description specification, description of implementation. To describe business processes, it is proposed to use about 80 types of models, each of which belongs to one or another aspect.

ARIS. Provides visual tools to ensure clarity of models. Also, the toolkit comes with a set of reference models, pre-developed for typical processes in various industries.

The general principle in the toolkit - the ability to integrate models different types Within one repository through decomposition (detail) of objects. Thus, any organization can be described using the models hierarchy - from generalization: for example, VACD (Eng. Value Added Chain Diagram) to the level of procedures and the resource environment of functions.

Among the large number of possible description methods, the following can be distinguished:

eEPC. (English Extended Event-Driven Process Chain) - Event Process Chain
ERM (eng. Entity-Relationship Model) - Model "Essence-Communication" to describe the data structure;
UML (Eng. Unified Modeling Language) - Unified object-oriented modeling language

The main elements used in the notation of ARIS:

Organizational Chart:
Organizational Unit;
Symbol "Person";
Symbol "Location";
Group of persons, role: "Role".
Process Landscape:
Process.
Business Process:
Event - event fixes the state of certain parameters at a certain point in time;
Activities - work, a certain actionperformed for a certain period of time;
Role - position in the organization;
IT System - Information System, Private Case "Data Warehouse"
Risks - risks;
INPUT AND OUTPUT DATA - sender or recipient of data.
Process Control Via Rules (and, or, xor) - intersection ("and", "or", "excluding or");
ProCcess Interface is a means of communication with the process under consideration.
Data Model:
Entity - Essence (Table);
Attributes - attribute of the essence (table field);
Primary Key - a unique entity attribute (primary key key);
Foreign Key - the external key of the table;
Relationship - relationships between entities (communication between tables);
IT Infrastructure:
IT System;
Hardware;
Network;
Network Components.
SYSTEM LANDSCAPE:
IT System;
Domain.
Deeneral Diagramm (English)

Available models in ARIS Express: Organization Chart, Process Landscape, Business Process, Data Model, IT Infrastructure, System Landscape, BPMN Diagram, Whiteboard, General Diagram.

Diagram example:

Organizational Chart.

Process Landscape (VAD)

Business Process (EPC (Event-Driven Process Chain)

BPMN (BUSINESS PROCESS MODELING NOTATION (BPMN 2.0))

BPMN notation describes legend To display business processes in the form of diagrams of business processes. BPMN is focused on technical specialistsand business users. To do this language uses basic set Intuitive elements that allow to determine complex semantic structures. In addition, the BPMN specification determines how the diagrams describing the business process can be transformed into executable models in BPEL. The BPMN 2.0 specification is also executed and portable (that is, the process drawn in one editor from one manufacturer can be executed on the engine of business processes of a completely different manufacturer, provided that they support BPMN 2.0).

Cloud version of ARIS CLOUD includes 4 types of diamraft: EPC, OC, VAD, Application System Type Diagram

The free version of the program, I mean Aris Express supports only the basic types of diagrams, does not have multiplayer support (ARIS Cloud supports) does not use the database, does not contain tools for generating reports and model analysis tools. ARIS EXPRESS does not support links between the objects created, in contrast to the full-fledged paid version, there is no monitoring of the integrity and consistency of the model. This means that when editing one model, the program will not make appropriate changes to another model, and will not check whether the posts indicated as responsible in the process, etc.

General structure of ARIS methodology

http://rudocs.exdat.com/docs/index-62596.html?page\u003d3

The notation of ARIS EEPC is decrypted as follows - Extended Event Driven Process Chain is an extended process chain managed by events. Notation developed by IDS Scheer AG (Germany) specialists, in particular Professor Sheer. The following Table 2.3.1 provides basic objects used in the framework of notation.

Table 2.3.1 Objects for describing business processes in the notation of ARIS EEPC.

In addition to the main objects specified in Table 2.3.1, many other objects can be used when constructing the EEPC diagram. In practice, the use of a large number of objects of various types is inappropriate, as this significantly increases the size of the model and makes it poorly readable. For understanding the meaning notation EEPC. Consider the basic types used types of objects and connections. Figure 2.3.5. The simplest EEPC model describing the enterprise business process fragment is presented.

Fig. 2.3.5. The simplest model in the notation EEPC

Figure 2.3.5. It can be seen that relations between objects have a certain meaning and reflect the sequence of functions within the process. The arrow connecting the event 1 and the function 1 "activates" ("Activates") or initiates the execution of the function 1. The function 1 "creates" ("Creates") event 2, followed by a logical "and" character, "Running" functions 2 and 3. Attentive analysis of the notation EEPC shows that it is practically no different from the notation of IDEF3. The most important difference between EEPC is the presence of an "event" object ("EVENT"). This object is used to display in the model of possible results of functions, depending on which one or another subsequent branch of the process is performed. The notation of EEPC is obviously extended due to the presence of an "event" object in it, there is no such object in IDEF3. When building a model in ARIS EEPC, the following rules must be followed:

each function must be initiated by the event and must end with the event;

in each function, more than one arrow, "running" execution of the function, and exit no more than one arrow, describing the completion of the function.

Figure 2.3.7 shows the use of various ARIS EEPC notation objects when creating a business process model.

Fig. 2.3.7. Application of various objects when creating a model in the notation EEPC

Figures 2.3.6. and 2.3.7. It can be seen that the business process in the notation EEPC is a sequence of procedures located in the order of their execution. It should be noted that the real duration of the procedures in EEPC visually reflects can not be. This leads to the fact that when creating models, situations are possible when one artist will be entrusted to perform two tasks at the same time. The logic symbols used in constructing the model allow you to reflect the branching and merging of the business process. For information on the real duration of processes and visual display of staff loading during the process, you can use other description tools, such as Gantt graphics in the MS Project application.

Figure 2.3.8. The business process is presented to the client order processing. The process begins with the event "entered the customer's order." This event initiates the "Running Order In the System" function, which is performed by the sales department manager. To perform work, it uses the "order accounting system". The result of the function is displayed as an event "Order Accounting". After that, the Sales Manager performs the function "Perform an analysis for compliance with the nomenclature". The result of the execution of the function is two alternative events "Order corresponds to the nomenclature" and "Order does not correspond to the nomenclature." The process is branching. To display the branching of the process, a symbol of a logical exclusive "or" is used. The "Notify Customer's Customer" function can be performed in two cases: if the order does not correspond to the nomenclature, or production is impossible. To display on the process of these options, the symbol of logical "or" is used, etc. As can be seen from Figure 2.3.8. The process circuit in ARIS EEPC differs from the schema in IDEF3 the presence of objects: events, documents, application systems and posts. The scheme in ARIS is visually seemed more informative and perceived better, but the size of this scheme significantly exceeds the size of the scheme in the notation IDEF3.
Fig. 2.3.8. An example of a description of the process in the notation of ARIS EEPC

Perhaps it will be useful to read: