Fig 1 - uploaded by Mirosław Zaborowski
Content may be subject to copyright.
Source publication
The set of the most significant concepts of the author's theory of Enterprise Process Control (EPC) has been given in the paper. Classification of the concepts has been presented in class diagrams by means of generalization relationships. It has been shown, by means of composition relationships, in any enterprise the structure tree of business obje...
Contexts in source publication
Context 1
... objects. For modeling and designing EPC systems one could use the UML [2], but the EPML, which is patterned on it, is easier. From among many types of diagrams of the UML only class diagrams and object diagrams are used in the EPML. Furthermore, from among relationships between objects only generalization and association relationships are used ( fig. 1). So the EPML is substantially simpler than the UML. Among association relationships one ...
Context 2
... composition and weak aggregation, as in the UML standard. In the case of composition each component belongs to only one composite. In the case of weak aggregation a given object may be an element of different groups of objects. Additionally, in class diagrams and in object diagrams of EPC systems order associations are marked with arrows ( fig. 1). Such relationships represent execution order of activities or actions of business agents, flow of products between activities, flow of information between business agents and the like. Class diagrams of EPC systems present relations between sets of EPML objects. Classes represent sets of objects and relations represent sets of ...
Citations
... It has been demonstrated that all enterprise objects, including structural objects (business units, enterprise activities, business accounts, business products, business tasks, products of business tasks and the like) and their attributes (business variables, functional variables, information-decision state variables and their records), belong to the enterprise structure tree of definite composition relationships [2,15]. The root of this structure tree is the enterprise as a whole. ...
... Practical conclusions from analysis of EntPC systems, regarded as complex control systems, always concern i-d state variables perceived as attributes of enterprise processes or attributes of structural objects that belong to these processes. Hence, the conceptual model of the structure of enterprise processes [2,10,15] is one of the main subjects of EntPC theory. Relationships between concepts corresponding to all the sets of software objects in any EntPC system are presented as relations between classes in class diagrams of the EntPCL metamodel. ...
... Class diagrams describing relationships between the most important subclasses of structural objects and between structural objects and information-decision state variables of EntPC systems have been discussed in [2,10,15]. Further details of relationships between subclasses of functional variables and i-d state variables are shown in Fig. 6. ...
This study presents cause-effect dependencies between inputs and outputs of business transitions that are software objects designed for processing information-decision state variables in integrated enterprise process control (EntPC) systems. Business transitions are elementary components of controlling units in enterprise processes that have been defined as self-controlling, generalized business processes, which may serve not only as business processes but also as business systems or their roles. Business events, which have zero durations by definition, are interpreted as executions of business actions that are main operations of business transitions. Any ordered set of business actions, performed in the controlling unit of a given enterprise process and attributed to the same discrete-time instant, is referred to as ‘the information-decision process’. The i-d processes may be substituted by managerial business processes, performed on the lower organizational level, where durations of activity executions are greater than zero, but discrete-time periods are considerably shorter. In such a case, procedures of business actions are performed by corresponding activities of managerial processes, but on the level of business transitions the durations of their executions are imperceptible, and many different business events may occur at the same discrete-time instant. It has been demonstrated in the paper how to control business actions to ensure that a given i-d state variable may not change more than once at a given instant. Furthermore, the rules of designing the i-d process structures, which prevent random changes of transitory states, have been presented.
Key words:
enterprise process control, complex control systems, industry 4.0, enterprise process state, enterprise integration.
... Tasks products are components of business products, which are components of business accounts and business accounts are components of generalised business activities, which in turn are components of business units and organisational systems (Fig. 8). Thus, all structural objects belong to a structure tree (similar to the one shown in Fig. 4), whose root is the enterprise as a whole (Zaborowski, 2016b). ...
This study demonstrates that integrated management and direct control systems may be organised as integrated enterprise process control (EntPC) systems, which are composed of self-controlling enterprise business processes. A business process has been defined as a control system for business activities, which are considered to be business processes of the lower level, or as base processes that are control systems for control plants in the form of infrastructure operations. An enterprise process also influences its delivery. This definition has been generally compared with definitions used in approaches of BPMN, YAWL, ARIS, DEMO and MERODE. Each enterprise process has its own controlling unit that contains one information unit and one decision unit, as well as memory places of the information-decision state variables that are processed by the business transitions that belong to these units. The i-d state variables are attributes of business objects, i.e. business units, business roles, business activities, business accounts and business products. Their values are transferred between business transitions that belong to the same or different controlling units. Relationships between business objects, business transitions and i-d state variables, as well as the other most important concepts of the EntPC system framework (EntPCF), are presented in this paper as the class diagrams of the enterprise process control language (EntPCL).
... For the same reason, business roles, i.e. business systems roles watched from the outside, are equated with corresponding sets of jointly managed business activities. It has been demonstrated that all enterprise objects, including structural objects (business units, enterprise activities, business accounts, business products, business tasks, products of business tasks and the like) and their attributes (business variables, functional variables, information-decision state variables and their records), belong to the enterprise structure tree of definite composition relationships [2,15]. The root of this structure tree is an enterprise as a whole. ...
... Practical conclusions from an analysis of EntPC systems regarded as complex control systems always concern i-d state variables perceived as attributes of enterprise processes or attributes of structural objects that belong to these processes. Hence, the conceptual model of the structure of enterprise processes [2,10,15] is one of the main subjects of the EntPC theory. Relationships between concepts corresponding to all the sets of software objects in any EntPC system are presented as relations between classes in class diagrams of the EntPCL metamodel. ...
... Class diagrams describing relationships between the most important subclasses of structural objects and between structural objects and information-decision state variables of EntPC systems have been discussed in [2,10,15]. Further details of relationships between subclasses of functional variables and i-d state variables are shown in the fig. ...
This study presents cause-effect dependencies between inputs and outputs of business transitions that are software objects designed for processing information-decision state variables in integrated enterprise process control (EntPC) systems. Business transitions are elementary components of controlling units in enterprise processes that have been defined as self-controlling generalized business processes, which may be not only business processes but also business systems or their roles. Business events, which have zero durations by definition, are interpreted as executions of business actions that are main operations of business transitions. Any ordered set of business actions, performed in the controlling unit of a given enterprise process and attributed to the same discrete-time instant, is referred to as 'the information-decision process'. The i-d processes may be substituted by managerial business processes, performed on the lower organizational level, where durations of activity executions are greater than zero, but discrete-time periods are considerably shorter. In such a case, procedures of business actions are performed by corresponding activities of managerial processes, but on the level of business transitions the durations of their executions are imperceptible, and many different business events may occur at the same discrete-time instant. It has been shown in the paper how to control business actions to ensure that a given i-d state variable may not change more than once at a given instant. Furthermore, the rules of designing the i-d process structures, which prevent casual changes of transitional states, have been presented.
... Enterprise activities are generalized business activities that may be business activities and business units or their roles as well. It has been demonstrated that all enterprise objects, including structural objects (business units, enterprise activities, business accounts, business products, business tasks, products of business tasks and the like) and their attributes (business variables, informationdecision state variables and their records), belong to the enterprise structure tree of definite composition relationships [2,3]. The root of this tree is an enterprise as a whole. ...
... Therefore any theory describing the structure and operation of all IMPC systems must include a universal model of the structure of enterprise processes, as well as the structure and functioning of their control systems and interactions between them. The theory of Enterprise Process Control (EPC3 theory) [2,3,16,17] satisfies these requirements. The Enterprise Process Control Framework (EPCF) is a part of the EPC3 theory. ...
... The enterprise process control (EPC) theory describes integrated enterprise process control (IEPC) systems, whose structure and behavior are in accordance with the enterprise process control framework (EPCF). The current version (EPC3) of this theory has been introduced in [2,3,16,17]. The main concepts of the EPC3 theory (generalized business processes, structural objects, business agents, i-d state variables and the like) as well as relationships between them have been presented in the form similar to the UML class diagrams. ...
This study briefly presents the structure of integrated enterprise process control systems (IEPC systems) and cause-effect dependencies between inputs and outputs of business agents that are software objects designed for processing information-decision state variables. Business agents are components of controlling units in enterprise processes that have been defined as self-controlling generalized business processes, which may be not only business processes but also business systems or their roles. Business events, which have zero durations by definition, are interpreted as executions of business actions that are main operations of business agents. Information-decision processes have been defined as ordered sets of business actions, performed in controlling units of enterprise processes. The i-d processes may be substituted by managerial business processes, performed on the lower organizational level, where durations of activity executions are greater than zero, but discrete-time periods are considerably shorter. In such a case, procedures of business actions are performed by corresponding activities of managerial processes, but on the level of business agents durations of their executions are imperceptible, and many different business events may occur at the same discrete-time instant. It has been shown in the paper how to control business actions to ensure that a given i-d state variable may not change more than once at a given instant. Furthermore, the rules of designing the i-d process structures, which prevent casual changes of transitional states, have been presented.
... All these relationships may be shown in tabular form or in EPCL diagrams (Zaborowski 2015(Zaborowski , 2016. They are patterned on UML object diagrams (Booch, Rumbaugh and Jacobson 1999), but they are simpler because the only relationships between the presented objects are associations. ...
... Enterprise activities are generalized business activities that may be business activities and business units or their roles as well. It has been demonstrated that all enterprise objects, including structural objects (business units, enterprise activities, business accounts, business products, business tasks, products of business tasks and the like) and their attributes (business variables, information-decision state variables and their records), belong to the enterprise structure tree of definite composition relationships (Zaborowski 2016b(Zaborowski , 2017. The root of this tree is an enterprise as a whole. ...
... Therefore any theory describing the structure and operation of all IMPC systems must include a universal model of the structure of enterprise processes, as well as the structure and functioning of their control systems and interactions between them. The author's theory of Enterprise Process Control (EPC3 theory) (Zaborowski 2015(Zaborowski , 2016a(Zaborowski , 2016b(Zaborowski , 2017 satisfies these requirements. The Enterprise Process Control Framework (EPCF) is a part of the EPC3 theory. ...
... The author's enterprise process control (EPC) theory describes integrated enterprise process control (IEPC) systems, whose structure and behavior are in accordance with the enterprise process control framework (EPCF). The current version (EPC3) of this theory has been introduced in (Zaborowski 2015(Zaborowski , 2016a(Zaborowski , 2016b(Zaborowski , 2017. The main concepts of the EPC3 theory (generalized business processes, structural objects, business agents, i-d state variables and the like) as well as relationships between them have been presented in the form similar to the UML class diagrams. ...
... EPC systems are IT systems; therefore, in modelling and designing these systems, UML (Booch, Rumbaugh, and Jacobson 1999) could be used, but the EPML (Zaborowski 2016aZaborowski , 2016b), which is patterned after UML, is easier to learn. From many diagram types of UML only object diagrams are used. ...
... The concepts of the EPC theory are defined deductively, beginning with the most general concepts and moving forward, step by step, to those related to the details of the EPC systems structure. The first part of the present version of the EPC framework and the EPC theory (Zaborowski 2016a(Zaborowski , 2016b) includes the information-decision (i-d) model of enterprise business processes, which is presented in this paper. ...
... EPC systems are IT systems; therefore, in modelling and designing these systems, UML (Booch, Rumbaugh, and Jacobson 1999) could be used, but the EPML (Zaborowski 2016a(Zaborowski , 2016b, which is patterned after UML, is easier to learn. From many diagram types of UML only object diagrams are used. ...
This study demonstrates that integrated multilevel management and direct control systems are enterprise process control systems (EPC systems). A business process has been defined as a control system that controls its subordinate processes, whereas a base process – as a control system whose controlled plant is an infrastructural process. EPC systems may be perceived as networks of controlling units of enterprise processes. The structure of these networks reflects the hierarchical and cooperative relationships between business activities. EPC systems may also be perceived as multiagent control systems with passive interactions between agents. This study defines the information-decision state variables of an EPC system and presents a general model of cause-result dependencies between the input and output variables of elementary business agents. In addition, it describes how to model the structure of concrete EPC systems using enterprise process modelling language (EPML) diagrams, which are such UML object diagrams that fulfil the constraints imposed by class diagrams of the EPML metamodel. Class diagrams for the relationships between the most important concepts of EPC theory are presented. In conclusion, it was noticed that the EPML metamodel may be implemented as the software framework, which is designed for modelling and generating EPC systems software that is built from replaceable controlling units of enterprise processes.
... Systemy sterowania procesami w przedsiębiorstwach, krócejsystemy EPC (Enterprise Process Control) [19,20,21] są to zintegrowane systemy zarządzania i sterowania bezpośredniego procesami przedsiębiorstw [13,14] o strukturze zgodnej z metamodelem języka EPML (Enterprise Process Modeling Language). Język EPML jest językiem graficznym, przeznaczonym do modelowania procesów biznesowych oraz struktur systemów zarządzania procesami w przedsiębiorstwach [20,21]. ...
... Systemy sterowania procesami w przedsiębiorstwach, krócejsystemy EPC (Enterprise Process Control) [19,20,21] są to zintegrowane systemy zarządzania i sterowania bezpośredniego procesami przedsiębiorstw [13,14] o strukturze zgodnej z metamodelem języka EPML (Enterprise Process Modeling Language). Język EPML jest językiem graficznym, przeznaczonym do modelowania procesów biznesowych oraz struktur systemów zarządzania procesami w przedsiębiorstwach [20,21]. Można go wykorzystywać, podobnie jak języki ArchiMate [1] i UEML [15], do modelowania architektury przedsiębiorstw. ...
... 1). Jednostki sterujące są uporządkowanymi zbiorami elementarnych agentów biznesowych, które przetwarzają zmienne stanu informacyjno-decyzyjnego przedsiębiorstwa [18,20,21]. Zatem system EPC może być także postrzegany jako sieć agentów elementarnych i rozdzielających je zmiennych stanu i-d, o strukturze podobnej do kolorowanych sieci Petriego [10]. ...
... Systemy sterowania procesami w przedsiębiorstwach, krócejsystemy EPC (Enterprise Process Control) [34] są to zintegrowane systemy zarządzania i sterowania bezpośredniego procesami przedsiębiorstw [23,24] o strukturze zgodnej z metamodelem języka EPML (Enterprise Process Modeling Language). Język EPML jest językiem graficznym, przeznaczonym do modelowania procesów biznesowych oraz struktur systemów zarządzania procesami w przedsiębiorstwach [34,35]. Można go wykorzystywać, podobnie jak języki ArchiMate [2] i UEML [20,27], do modelowania architektury przedsiębiorstw. ...
... Każdemu pojęciu odpowiada jedna z klas metamodelu EPML, a związki między nimi są widoczne na odpowiednich diagramach klas. Najważniejsze pojęcia aktualnej wersji teorii EPC przedstawiono w [32,33,34,35]. W niniejszej pracy przedyskutowano dynamikę zmian stanu i-d zachodzących w systemach EPC w wyniku zdarzeń biznesowych. ...
... Strukturę zmiennych stanu i-d oraz ich związki z agentami biznesowymi i ze zdarzeniami biznesowymi (rys. 4) omówiono w [34,35]. Zmienne wyjściowe elementarnych agentów informacyjnych i decyzyjnych są odpowiednio informacyjnymi i decyzyjnymi zmiennymi stanu i-d. ...
