Integration of several plant modules, each with at least one process unit, into a modularly designed overall plant

Description

[0001] The invention relates to a system and a method for integrating several plant modules, each with at least one process-engineering unit, into a modular overall plant.

[0002] As is well known, the majority of process plants today are controlled by a central master computer with the central control technology (CCT) of a digital control system (DCS). This master computer is connected to all sensors in the plant via a fieldbus system or directly via cable (typically 4-20 mA). All relevant control processes are handled centrally by this computer. In recent years, however, there has also been a growing demand for new products in ever smaller batch sizes. Since production based on a central control concept can generally only be adapted slowly to changing products and production conditions, or the associated process conditions, a technology has been developed that delivers better results, particularly shorter engineering times and more flexible production conditions.This technology is known as MTP (Module Type Package) and concerns the development of continuously reconfigurable process units (modules), particularly chemical units. MTP (Module Type Package) defines the interfaces and functions of the automation technology of such modules, ultimately enabling the integration of such modules into a higher-level process control level. The concept here consists of essentially self-contained production or process modules, each of which is automated by a small-scale controller. Such modules are described, for example, in DE 10 2016 201 075 A1.

[0003] To integrate such modules into the process control level, they can then be easily and quickly connected to a central control system using an MTP software container, for example, Fig. 1This leads to significantly faster and more efficient engineering than was possible in the past. Each module, Fig. 1with the reference numbers 1 to 4, a standardized service description, as well as an object list are available. Both are described in a so-called exchange or description file, usually in a standard format AML (Automation Markup Language), which is a neutral, XML-based data format for the storage and exchange of plant planning data and is available as an open standard, thus ensuring a smooth connection of the modules to the central control system. This file, used within the framework of MTP, thus summarizes all the information required for the integration of data into the process control level. The modules have a control technology, usually designed as a programmable logic controller, which controls the module and in particular the hardware contained therein to carry out a function of a technical process and also communicates with the respective control system, in the case of Figure 5 assigned the reference number 5, communicates, with OPC UA generally being used for communication 6 or the data exchange between modules 1 to 4 and the central control unit 5. OPC UA ("Open Platform Communications Unified Architecture") describes a collection of specifications for communication in the field of industrial automation and M2M communication, which covers the transport of data as well as interfaces, security mechanisms, and the semantic structure of data, such as measured values, sensor data, controlled variables, or control instructions.

[0004] The central control unit orchestrates the autonomous modules and thus ensures that the respective product can be produced with the desired quality. In addition to communication, i.e., online communication during the process, the configuration of the entire system and thus of the individual modules is always controlled via the central control unit (ZLT / DCS). However, there is a market need for the autonomous units to communicate with each other. This requires a decentralized link between autonomous modules. This requires both the link during the engineering phase, particularly at the process control level (PFE), and the online data exchange during production.

[0005] DE 10 2016 201 075 A1, on the other hand, proposes a system for carrying out a process using a technical system, which includes a plurality of such autonomous modules, a request module, and a network connecting the autonomous modules and the request module. The request module can request a service for an end product from the modules via the network. The request module can communicate with the autonomous modules via the network and send a request for an end product to them. If this request is received from an autonomous module that provides the end product as the output product, this autonomous module then, in turn, requests the other autonomous modules to provide it with the required input products in the desired quantity, at the desired time, and in the desired condition.If corresponding autonomous modules then register, they in turn request the required input products from other autonomous modules. This gradually builds up a technical process that, with the corresponding autonomous modules, leads to the final product requested by the requesting module. The starting point of such a process is usually a self-sufficient module that stores an input product from another self-sufficient module and provides it to it.

[0006] A prerequisite for this approach, however, is that for such an interconnection of the modules and the corresponding coupling of the respective services, hereinafter also referred to as services, each of the self-contained modules must always have a completely self-contained function.

[0007] Unfortunately, in reality this is often different.

[0008] WO 2017 / 129606 A1 discloses a module for a technical system comprising technical hardware for executing a technical subprocess, a controller for locally controlling the technical hardware, and an external interface of the controller, as well as a method for controlling a technical system. The controller is configured to control the technical hardware autonomously. The external interface comprises an OPC UA server that has a predefined information structure with static information and dynamic information. The static information describes the technical hardware and the controller. The controller writes the dynamic information into the information structure as real-time values ​​of the technical hardware.

[0009] DE 10 2014 222508 A1 relates to a module for a process-engineering plant comprising process-engineering hardware for executing a process-engineering subprocess, a controller for locally controlling the process-engineering hardware, and an external interface 22 of the controller, as well as a method for controlling a process-engineering plant composed of multiple modules. The controller is configured to independently control the process-engineering hardware and to bring it into a number of specific, defined states. The external interface can receive a number of defined commands that correspond to the specific, defined states of the process-engineering hardware.

[0010] EP 3 246 773 A1 discloses a method for engineering a process or process-engineering plant with at least one functional module, furthermore a corresponding functional module and a programmable logic controller for such a functional module. The functional module has a programmable logic controller and a process or process-engineering module that can be controlled and / or regulated by means of the programmable logic controller for use as part of the plant. A user program that can be configured using parameters is loaded into the programmable logic controller. During plant engineering, information on the function module integration is provided in a file, the parameters for the application-specific configuration of the function module are defined using a plant engineering tool, and stored in a memory area of ​​the controller via an interface specified in a formal description language for configuring the user program.This no longer requires an engineering tool that is specific to the programmable logic controllers used in the function modules.

[0011] The solution according to the invention is characterized by a method and a system for integrating several plant modules, each with at least one process-technical unit, into a modularly constructed overall plant according to claim 1 or claim 7.

[0012] The invention therefore provides a method for integrating a plurality of plant modules, each with at least one process-engineering unit which, in addition to hardware for carrying out a function of a technical process, also houses control technology for controlling the hardware, into a modular overall plant. In this method, the plant modules are spatially arranged and mechanically and electrically connected to one another according to a description of the overall plant, such that at least one data connection is established between the plant modules via one or more communication protocols. A configuration of the overall plant is compiled and stored on a central server unit which is data-linked to the plant modules, and each plant module is assigned at least one access path to the stored configuration.The system modules are then started, and each system module then establishes a connection to the stored configuration via the access path, reads out specific configuration data for the reading system module via the access path, and establishes the necessary communication connections to at least one other system module based on the read configuration data, whereby links between individual data objects are established and service interfaces are called, and the system modules then make their respective functions available to the outside via data points and services.

[0013] The invention also proposes a corresponding system according to claim 7.

[0014] A significant advantage over the prior art is therefore that the solution according to the invention dispenses with a central DCS system and instead decentralizes the DCS tasks and distributes them among the process-related plant modules. In particular, the data points of the individual plant modules are also taken into account, allowing each plant module to access external data and sensors / actuators originally assigned to another plant module via OPC UA-based communication.

[0015] Further advantages and features of the invention will become apparent from the following description of preferred embodiments, given by way of example, with reference to the accompanying drawings, in which: Fig. 1 shows a sketch of self-sufficient modules integrated into an overall system, in particular integrated into the process control level, with access to a central data memory with the configuration of the overall system stored therein according to the invention, Fig. 2 shows a sketch of self-sufficient modules integrated into the process control level with interconnected service interfaces according to the invention, Fig. 3 shows a sketch of self-sufficient modules integrated into an overall system, in particular integrated into the process control level, with access to a central data memory, but designed as part of a self-sufficient module, with the configuration of the overall system stored therein according to the invention, Fig. 4 shows a sketch of self-sufficient modules integrated into the process control level with interconnected data objects according to the invention, and Fig.5A sketch of a connection of autonomous modules to a central control system for integration into the process control level according to the state of the art.

[0016] In the following we will first refer to the Figure 1 and 3 with further involvement of Figure 4Reference is made to the drawings which each show a sketchy view of a plurality of modules which can be integrated as an alternative to a modular overall system, in particular modules which are integrated in the process control level. Each module, also referred to below and in the claims as a system module, encloses a process engineering unit, in particular a unit from the field of process engineering, such as a mixing unit with inlets for various materials as well as a valve and pump for pumping out the processed material, a reactor unit with inlets and outlets for a cooling medium of a cooling circuit or a refrigeration machine with inlets and outlets for the cooling medium. Such a process engineering unit, according to the definition and within the scope of the invention, has not only hardware for carrying out a specific function of a technical process, but also control technology, in particular local PLC control technology for controlling the hardware.

[0017] While the Figure 1 and 3 For reasons of clarity, such system modules, marked with the reference numerals 11 to 14 or 11 to 16, are shown only abstractly, Figure 4 Two system modules 11' and 17 are shown as examples with such hardware and control technology 50 and 50' respectively. Figure 4The plant module 11' is, for example, a reactor module and houses, as a process-engineering unit, a reactor with corresponding hardware, wherein, at the lower end of a reactor vessel 53, for example, a removal option 53a for a material processed in the vessel is provided. For example, the plant module 11' can thus be intended for a biotechnological application. The exemplary reactor vessel 53 is further provided with a heat jacket 54, on which a temperature measuring point 55 is located for recording a relevant temperature data point. Furthermore, the plant module 11' in the example shown expediently has, as control technology 50, a local control with reactor regulation, to which the temperature data point recorded at the temperature measuring point is also transferred. As with Figure 4As shown by way of example, the process-engineering unit of the system module 11' is further integrated into a cooling circuit, with a coolant inlet 56 and a coolant outlet 57 being schematically illustrated, by means of which coolant is supplied to the reactor vessel for cooling, and heated coolant is discharged from the reactor vessel again. For example, it can be provided that the control technology 50 must maintain a certain temperature range within specified upper and lower temperature limits in order to function as intended.

[0018] The rest at Figure 4The system module 17 shown is, by way of example, a temperature control module and, as a process-technical unit, accommodates, for example, a refrigeration machine 58 with corresponding hardware and, in the example shown, as control technology 50', expediently a local control with temperature control, which processes data points comprising manipulated variable parameters for the temperature control of the refrigeration machine, in particular for the temperature control and expediently also for the supply 56' of a correspondingly tempered coolant into a cooling circuit (coolant inlet) and return 57' of heated coolant from the cooling circuit (coolant outlet) back to the refrigeration machine.

[0019] It is further assumed that the two Figure 4 exemplary and compared to the Figure 1 and 3The plant modules 11' and 17 shown in more detail are connected to the same cooling circuit and are therefore also integrated into a common, modularly constructed overall plant, ie according to the present example with a plant module 11' comprising a reactor and a plant module 17 comprising a refrigeration machine for cooling the reactor.

[0020] To integrate the at least two (cf. Figure 4 ), or even a larger majority (cf. Figure 1 and 3) of system modules according to the invention to form a modular overall system, the system modules are or are spatially arranged and mechanically and electrically connected to one another in accordance with the description of the overall system. This also provides at least one data connection between the system modules via one or more communication protocols. The basis for such a data connection can therefore also be, for example, an Ethernet network, via which the system modules can communicate with one another, preferably using OPC UA, in particular also for establishing the communication connections 40 described below, for which purpose in particular the respective control technologies of the system modules can be set up with an OPC UA server (not shown in detail in the figures).

[0021] Furthermore, as particularly the Figure 1 and 3As can be seen, a central server unit 20 is provided, which is also linked to the system modules in terms of data technology, on which a configuration of the entire system is or is stored. To store the configuration, the server unit therefore expediently provides a correspondingly designed data memory. Such a central server unit 20, e.g., an SQL server (SQL - Structured Query Language), can, as in Figure 3 to be seen, be part of one of the plant modules, ie in particular the process engineering units, itself, or, as in the case of Figure 1 outlined, have a highly available, especially independently developed infrastructure.

[0022] In order to be able to access the configuration and in particular the respective configuration data intended for a system module, at least one access path 30 to the stored configuration is assigned to each system module before commissioning and is expediently set as a corresponding address on each module, in particular in the respective control technology.

[0023] Furthermore, the connection management is expediently configured such that the connection always originates from the data sink, i.e., that read access to the configuration always occurs. Consequently, it is also clear which connection is assigned to which system module, so that the configuration data intended for each system module is clearly determined via the respective access path. Such expedient connection management therefore applies not only to access to the configuration but also, in particular, to the communication connections 40 described below, which are to be established based on the read-out configuration data. This is because connections always originate from a data sink, i.e.,Read connection access, also with regard to the communication relationships between the plant modules, can ensure that even a single, standalone plant module can be controlled into a secure mode in the event of a data connection loss. If connections originating from a data source, i.e., write connection access, are also used, there is a risk that a "written" plant module will not know what to do in the event of data transmission losses, and would therefore be considered unsafe in the eyes of the process industry.

[0024] When the entire system is commissioned, i.e., when the system modules start or "boot up," they are each configured to establish a connection to the stored configuration via the assigned access path and to read out configuration data specific to the system module. Depending on the underlying protocol, appropriate services are usually available for establishing such a connection and reading out data.

[0025] Each system module, or its respective control technology, then establishes the communication connections 40 corresponding to the read configuration data and, in particular, checks whether its own operational readiness exists, i.e., whether all connections are established. A respective system module reading configuration data subsequently establishes communication connections 40 to at least one other system module. Establishing such connections includes both establishing links between individual data objects and calling interfaces for services, so that the system modules can thus make their respective functions available externally via data points and services through direct communication with one another during operation.

[0026] Such a data object is known to represent the IT mapping of a data point and contains the value of the data point enriched with further information such as physical quantities. To represent a reactor temperature of 78°C, for example, a data point value at temperature measuring point 55 ( Figure 4 ) e.g. the corresponding data object with a value "78" and a physical quantity "°C" to represent a reactor temperature of 78°C.

[0027] The entire process engineering plant is therefore constructed through a self-sufficient orchestration of these plant modules, whereby a central DCS system can be dispensed with and the DCS tasks are instead solved in a decentralized manner and distributed among the process engineering plant modules.

[0028] Also for such a smooth integration of the self-sufficient system modules according to the invention, the system modules 11 to 14 ( Figure 1 ), or 11 to 16 ( Figure 3 ) or 11`, 17 ( Figure 4 ) are appropriately described in a description file which, depending on the function to be performed, contains information about Parameters (constants), list of connectable data points with data type, access rights, etc., list of offered services / service interfaces, list of services / service interfaces to be used (stubs), and / or possibly further descriptions of alarms, etc. contains.

[0029] The decentrally stored configuration, however, includes, in a practical implementation, the interconnection or linking of data objects between the system modules as well as the interconnection of service interfaces. It is also possible to combine a set of services into a common service interface for a system module, which is described below using the example of Figure 2will be explained in more detail. Each system module knows, for example, after reading in the configuration intended for it, which services / service interfaces (stubs) should be used. These then represent, for example, the data sinks for which a connection to a service of another module is established. The linked data objects can also be used, for example, to access data and / or sensors / actuators of a second system module from a first system module. For example, in Figure 4 By establishing corresponding communication connections 30 between the system modules 11' and 17, a link 60 is established between the data object 51 contained in the control technology 50 and the control technology 50' in such a way that the system module 17 for its process-technical function, ie according to the example according to Figure 4 for temperature control, on control and / or measurement variables of the system module 11', ie according to the example according to Figure 4in particular the reactor temperature.

[0030] If the read-out configuration data also contains parameters in a suitable further development, these are implemented as constant values ​​and automatically copied locally to the respective system module's own data objects.

[0031] In a preferred development, a flow logic can also be part of the configuration. Such a flow logic can therefore also be loaded when configuration data intended for a system module is read out and then executed by the control technology of the system module reading the data and loading the flow logic. Such a flow logic can, for example, be a piece of PLC code. It could therefore be, for example, a logic link or the generation of maximum values ​​for several temperature measuring points. Overall, the configuration of the entire system can therefore be considerably more flexible. Alternatively, the necessary control logic for the (sub-)process to be executed by this system module is already completely stored in the control technology of a respective system module.

[0032] Depending on the design, an operating mode, for example the actual process start of the entire system, or even different operating modes can then be triggered, for example, by an external trigger and can be controlled additionally or alternatively by exchanged services and / or data objects and / or hardware switches coupled with inputs and / or outputs for recording data points. In practice, however, this usually requires an explicit action and can, for example, also be carried out using a visualization page on a web interface.

[0033] The configuration data can be conveniently monitored by the individual system modules via access paths 30, even during operation. If changes occur in the configuration data of one or more system modules, these can be adopted immediately or after reinitialization, depending on the design and / or status of the process. In the simplest case, these can involve adjusted parameters to optimize the process or procedure. However, extensions and / or modifications to the entire system can also be flexibly handled in this way. Depending on the technical solution used, the configuration data can be monitored for changes, e.g., using a polling process or an event-based protocol.

[0034] Consequently, if a complete system is required to carry out a specific task, e.g. Figure 1 and further involving Figure 2Constructed from four such self-contained plant modules 11, 12, 13, and 14 according to the invention, plant modules 11 and 12 can, for example, be storage and feed modules. Furthermore, plant module 13 is, for example, a reactor module, and plant module 14 is, for example, a storage tank module. Thus, materials are conveyed from plant modules 11 and 12 into the reactor module, and after the reaction, the produced material is transported further to the storage tank module. From there, the finished product can then be removed later, for example.

[0035] As previously described, the necessary services and communication relationships, as well as the interconnection of data objects, are configured without central control and stored on the central data storage server 20. Each system module is assigned an access path 30 to the location of the configuration data, and the system modules are thus enabled, after appropriate startup, to independently read the configuration data intended for them and serve as part of the overall modular production (see also Fig. 2a).

[0036] At Figure 2 In this regard, the established communication relationships 40 between the system modules are outlined by way of example and for the sake of clarity only with regard to the called service interfaces or, in particular, linked service interfaces 42, 43, for which preferably a set of service interfaces is combined.

[0037] For example, the services of initialization, pre-cleaning and subsequent material supply are combined into the common service interfaces 42, which according to the embodiment relate to the interaction between the reactor module and the feed modules.

[0038] The configuration data could therefore include, for example, the following service configuration summarized in the service interface 42: interface IFeed { void Initialization(...); void Cleaning(...); void PumpMaterial(...);}

[0039] Of course, other and / or additional services can also be included. For example, it can also be specified that the feed should only start after a predetermined time following the pre-cleaning.

[0040] Furthermore, the shared service interface 43 concerns, for example, the interaction between the reactor module and the storage tank module. Services combined for this purpose can, for example, again concern basic initialization, a valve check, and the subsequent inerting of the storage tank.

[0041] The configuration data could therefore include, for example, the following service configuration summarized for service interface 43: interface IStorage { void Initialization(...); void CheckValveStatus(...); void Inerting(...);}

[0042] With regard to the service interface 43, other and / or additional services can also be combined.

[0043] As in Figure 2 see, two further service interfaces 44 of the plant module 13 are not linked. For example, it is assumed that the plant module 13 designed as a reactor module supports up to four feed modules. In the example according to Figure 2Initially, only two feeder modules are used in the overall system. If one or two additional feeder modules were added, the service configuration summarized in the configuration data for a respective service interface 44 could essentially correspond to that of the service interface 42. A connection table 21 of data objects contained in the configuration stored on the central data storage server 20 could, in the example, be configured according to the Figure 2 look like this: Reactor.FeedA = Feed1.Feed Reactor. FeedB = Feed2. Feed Reactor.FeedC = ZERO Reactor.FeedD = ZERO Reactor. StorageX = Storage1. Storage; where Reactor.FeedA identifies a data object of the plant module 13 that is to be linked to a data object of the plant module 11, identified as "Feed1.Feed"; Reactor.FeedB identifies a data object of the plant module 13 that is to be linked to a data object of the plant module 12, identified as "Feed2.Feed"; Reactor.FeedC and Reactor.FeedD identifies respective data objects of the plant module 13 that are not yet to be linked and are therefore set to NULL; and Reactor.StorageX identifies a data object of the plant module 13 that is to be linked to a data object of the plant module 14, identified as "Storage1.Storage".

[0044] As mentioned, for the sake of clarity, Figure 2The established communication relationships 40 between the system modules concerning the linked data objects are omitted. However, the autonomous structure is essentially the same. However, as already mentioned, such a linking of data objects is not possible in the example according to Figure 4 shown. If, in the overall system outlined there, for example, at least one measured variable from the system module 11' designed as a reactor module is required for temperature control by the system module 17 designed as a temperature control module, this is automatically made available as a data object 51 via the corresponding link 60 without detours via a PFE (process control level, DCS, PCS).

[0045] All calls to the services and also access to external data points via the linked data objects are therefore carried out directly between the system modules without going through a central control system (ZLT / DCS).

[0046] The start and control of the entire system according to Figure 2 or according to Figure 4 In these examples, this can be done using manual switches on the reactor module.

[0047] Based on the example Figure 2 If a different but similar product is required at a later date, the modular overall production plant can be expanded, for example, to include another template for an additive, for example, using plant module 15 according to Figure 3 and / or a mixer, for example by system module 16 according to Figure 3 be expanded. Here, too, only the configuration data stored in the central data storage server 20 needs to be adjusted and the added system modules assigned corresponding access paths 30.

[0048] For example, when expanding the entire system with system module 15, "Reactor.FeedC = Feed3.Feed" is added to the wiring table above.

[0049] As already mentioned, a plant module itself can also assume the role of central data storage, especially if it, and especially its control technology, provides sufficient computing power and data storage. This is already the case with today's programmable logic controllers (PLCs). Thus, modular, flexible process plants or plant components can be constructed without a central controller.

[0050] Taking the above description into account, it can thus be summarized once again that an overall system according to the invention can be constructed and operated in a modular manner without a central control system, whereby a higher level of fail-safe protection is generally provided by the use of at least partially autonomous processes.

[0051] The respective system modules involved make their interfaces available to other system modules and also use the interfaces of other system modules, so that both service links and data links are possible. The communications maintained directly between the autonomous system modules based on communication relationships stored in a centrally stored configuration thus include data and services, such as requests and / or commands. While, depending on the desired overall system, the individual, modularly integrated system modules each contribute a specific function of a technical process to the overall process, the respective specific parameters can be specified externally and stored on the central server, so that even process variants of a process to be carried out can be extremely flexibly part of such a centrally stored configuration.Process logic to be adopted by one or more system modules can also be part of the centrally stored configuration. Changes in the configuration, e.g., parameter adjustments, can be monitored by the system modules and, depending on the specific design, taken into account accordingly. For example, an affected sub-process can be stopped, additional system modules can be mechanically and electrically integrated, and then reintegrated into a modified process according to the changes made in the configuration after a restart and automatic adoption of the changes.

Claims

1. Method for integrating a plurality of installation modules (11, 11',12, 13, 14, 15, 16, 17) each having at least one process-technical unit, which houses besides hardware for carrying out a function of a technical process also control technology (50, 50'), to a modularly constructed overall Installation, wherein the installation modules (11, 11',12, 13, 14, 15, 16, 17) are arranged three-dimensionally and, according to a description of the overall installation, are connected mechanically and electrically to one another such that at least one coupling for data exchange is formed between the installation modules (11, 11',12, 13, 14, 15, 16, 17) via one or more communication protocols, and wherein a configuration of the overall installation is assembled and stored on a central server unit (20) having a data link to the installation modules (11, 11',12, 13, 14, 15, 16, 17) in terms of data technology, each installation module (11, 11',12, 13, 14, 15, 16, 17) is allocated at least one access path (30) to the stored configuration, and the installation modules (11, 11', 12, 13, 14, 15, 16, 17) are started, furthermore, after the installation modules (11, 11',12, 13, 14, 15, 16, 17) have been started, each installation module (11, 11',12, 13, 14, 15, 16, 17) carries out the following steps: establishing a connection to the saved configuration via the access path (30), reading out of configuration data respectively intended for the readout installation module (11, 11',12, 13, 14, 15, 16, 17) via the access path (30), establishing, in accordance with the configuration data read out, necessary communication links (40) to at least one further installation module (11, 11', 12, 13, 14, 15, 16, 17), wherein linkages (60) are established between individual data objects (51) and also service interfaces are requested, and the installation modules (11, 11',12, 13, 14, 15, 16, 17) provide their respective function to the outside via data points and services.

2. Method according to claim 1, wherein the linked data objects (51) are used by a first of the installation modules (11, 11', 12, 13, 14, 15, 16, 17) to access data and / or sensors / actuators of a second of the installation modules (11, 11',12, 13, 14, 15, 16, 17).

3. Method according to either claim 1 or claim 2, wherein parameters contained in the read out configuration data are converted as constant values and automatically copied locally by each installation module (11, 11',12, 13, 14, 15, 16, 17) to their own data objects.

4. Method according to any of claims 1 to 3, wherein, when reading out respective configuration data, also sequence logic is loaded and then executed by means of the control technology (50, 50') of the installation module (11, 11',12, 13, 14, 15, 16, 17) that is reading out and loading the sequence logic.

5. Method according to any of Claims 1 to 4, wherein at least one operating mode of the overall installation is controlled by services exchanged via communication links (40) and / or by data objects and / or by hardware switches coupled to inputs and / or outputs for recording data points.

6. Method according to any of Claims 1 to 5, wherein the configuration data contained in the configuration are monitored by the installation modules (11, 11',12, 13, 14, 15, 16, 17) during the operation of the overall installation and, when changes are made to the configuration, are accepted by at least one of the multiple installation modules (11, 11',12, 13, 14, 15, 16, 17) immediately or after re-initialization, wherein a polling method or an event-based protocol is used for monitoring the configuration data.

7. System for integrating a plurality of installation modules (11, 11',12, 13, 14, 15, 16, 17) each having at least one process-technical unit, which houses besides hardware for carrying out a function of a technical process also control technology (50, 50'), to a modularly constructed overall Installation, wherein the installation modules (11, 11',12, 13, 14, 15, 16, 17) are arranged three-dimensionally and, according to a description of the overall installation, are connected mechanically and electrically to one another such that at least one coupling for data exchange is formed between the installation modules (11, 11',12, 13, 14, 15, 16, 17) via one or more communication protocols, further comprising: a central server unit (20) which is coupled to the installation modules (11, 11',12, 13, 14, 15, 16, 17) for data exchange and on which a configuration of the overall installation is stored, wherein each installation module (11, 11',12, 13, 14, 15, 16, 17) knows at least one access path (30) to the stored configuration, so that after the installation modules (11, 11',12, 13, 14, 15, 16, 17) have been started, they are set up for - establishing a connection to the saved configuration via the access path (30), - reading out of configuration data respectively intended for the read out installation module (11, 11',12, 13, 14, 15, 16, 17) via the access path (30), - establishing, in accordance with the configuration data read out, necessary communication links (40) to at least one further installation module (11, 11',12, 13, 14, 15, 16, 17), which includes both establishing linkages between individual data objects (51) and requesting service interfaces, and wherein the installation modules (11, 11',12, 13, 14, 15, 16, 17) then providing their respective function to the outside via data points and services.

8. System according to claim 7, wherein the central Server unit is part of one of the installation modules (11, 11',12, 13, 14, 15, 16, 17), in particular one of the process-technical units, or wherein the central server unit (20) has a central, highly available infrastructure.

9. System according to either Claim 7 or claim 8, wherein the configuration includes the interconnection of data objects (5) between the installation modules (11, 11', 12, 13, 14, 15, 16, 17) and the interconnection of service Interfaces, wherein in particular one set of service interfaces in each case is combined to form a common service interface (42, 43) for an installation module (11, 11', 12, 13, 14, 15, 16, 17) and / or wherein a sequence logic program is part of the configuration.

10. The System according Claim 7, Claim 8, or Claim 9, wherein each of the installation modules (11, 11', 12, 13, 14, 15, 16, 17) itself is described by a description file , which contains in particular: - parameters, - list of connectable data points with data type, access rights, etc., - list of offered services / interfaces, and / or - list of used services / interfaces (stubs).