Method for operating production machine or machine tool, and production machine or machine tool

Abstract

The invention relates to a method for operating a production machine or machine tool (10), comprising a control unit (17) for controlling actuators (19) of the production machine or machine tool (10), and at least one application program (30) for providing additional functions for the production machine or machine tool (10), the application (30) is managed by an external application management system (40) during the operation of the production machine or machine tool (10), the management action of the application management system (40) with respect to the application (30) being prevented when a predefined operating state of the production machine or machine tool (10) exists. The production machine or machine tool (10) comprises an internal application management unit (52), which is controlled by an external application management system (40), and a specification of the application management system (40) is implemented as a management measure with respect to the application (30), and wherein in the event of a predefined operating state, the application (30) is controlled by the internal application management unit (52). The application management unit (52) does not implement the specification of the application management system (40) with respect to the application (30). According to the invention, an application management unit (52) provides a function (55) which, when the function is called, does not implement a specification of an external application management system (40) as a management measure for the application (30). As a result, error-free operation of the production machine or machine tool (10) can be ensured.

Description

Field of the Invention

[0001] The present invention relates to a method for operating a production machine or a machine tool according to claim 1, and a production machine or a machine tool according to claim 13. The present invention also relates to a computer program according to claim 14, and a computer-readable storage medium according to patent claim 15. Background Art

[0002] Production machines and machine tools are themselves known in the art and generally include one or more actuators that implement the electrical control signals output by a controller as mechanical movements or changes in physical quantities such as pressure, temperature, etc., thereby actively intervening in the controlled process. For example, the actuator can be a drive or a heating element.

[0003] The production machine can be a machine in the discrete manufacturing industry (such as a machine for manufacturing vehicle components), a machine in the process industry (such as a machine for producing pharmaceuticals), a machine in the food and beverage industry, or an energy production device (such as a wind turbine, a solar installation). In the case of a machine tool, the actuator includes, for example, one or more drives (feed drives) for positioning a tool. Such machines are generally composed of a complex combination of various logical and physical components (such as drives, axes, etc.) in a diverse multiplicity. Generally, such machines include a controller (such as a numerical control system) for actuator control.

[0004] In the context of Industry 4.0 and the so-called Internet of Things (IoT), more functions or microservices can be extended for specific functions of such machines through an application. Such an application can be downloaded, for example, in a so-called cloud and provided by a cloud platform (app store). Downloading an application from the cloud platform and installing the downloaded application on a target system (host system), here a production machine or a machine tool, is called deployment.

[0005] A production machine or a machine tool equipped with such an application downloaded from the cloud, including an application with functions encapsulated in a container, is itself known, for example, see EP 3 650 968 A1.

[0006] The application can be provided in the app store for general-purpose machines. In this process, the respective specific structures of the subsequent host system and the runtime environment of the host system are unknown and do not need to be understood. For this reason, the application can at least include virtual containers (hereinafter simply referred to as containers) used in so-called container virtualization, and the software functions belonging to the application are embedded in each container included in the application. The container or each container at least includes a runtime environment necessary for executing the respective embedded software functions. The runtime environment included in the container can enable the respective software functions to run independently of the host system and its runtime environment. The application loaded on the host system is started on the host system by starting one or each of the containers it includes, and is limited to one or each virtual container included in the application. Such containers are already known per se, for example, reference can be made to the software for container virtualization called "Docker". Another example is "LXC" (Linux Containers).

[0007] The additional functions provided by the application (usually optional) can involve the collection and analysis of machine operation data. In addition, safety-related functions such as collision monitoring of tools or robotic arms can also be implemented, or the function expansion of the production cycle (such as the calculation of complex process programs).

[0008] Such application extensions to the machine are usually implemented by means of a so-called "edge system", which can be integrated into the machine during machine manufacturing or added later.

[0009] The working processes of such applications are usually carried out on hardware that is different from and out of sync with the actuator controller in terms of time, so they belong to external devices independent of the controller and are not integrated into the real-time communication bus of the machine components, for example.

[0010] However, these applications or these edge systems are usually not managed by the machine itself, but by an "external" application management system, which is usually also spatially separated from the machine (such as located in the cloud). The management measures of the external application management system regarding a certain application can involve starting the application, terminating the application, updating the application, changing the application configuration, and / or uninstalling the application.

[0011] In this context, "external" means for the application management system that the application management system runs independently of the controller of the machine and is responsible for managing the application, for example, according to the specifications (instructions) of the operator or the application / application management system developer.

[0012] The application management system can also run locally on the edge system (e.g., the user interface of an application), but is still considered external to the machine in this case.

[0013] Document EP 3 923 095 A1 discloses a method according to the preamble of claim 1. In this method, software (such as an application) on a technical device (such as a production machine) is managed by a configuration device. An update server is used to control and monitor software updates based on update configurations and software updates provided by the configuration device. The update server includes a monitoring module that, during the execution of a software update, collects operating parameters of the technical device and / or its related components, determines a detection result based on operating specifications and operating parameters, and controls the further execution of the software update according to the detection result. For example, when the operating parameters exceed the operating specifications, an alarm and / or the software update will be aborted; while when the operating parameters comply with the operating specifications, the software update will continue. Summary of the Invention

[0014] Based on the above, the object of the present invention is to ensure the trouble-free operation of such production machines or machine tools, in particular to ensure a high level of operating safety and avoid operating failures and production failures.

[0015] This object is achieved by a method for operating a production machine or machine tool according to claim 1, a production machine or machine tool according to claim 13, a computer program according to claim 14, and a computer-readable storage medium according to claim 15. Advantageous embodiments respectively constitute the subject matter of the dependent claims.

[0016] The method according to the present invention is used to operate a production machine or machine tool, which includes a controller for controlling an actuator of the production machine or machine tool and at least one application program for providing (usually optional) additional functions for the production machine or machine tool. This application program is managed by an external application management system, especially spatially separated from the machine, during machine operation. In other words, the management of the application program is implemented independently of the controller (or control program) of the production machine or machine tool.

[0017] According to the present invention, in the presence of a predefined operating state of the machine, the management measures of the application management system regarding this application program will be blocked. Therefore, in the case of a predefined operating state, the management measures of the application relationship system regarding this application program are prohibited.

[0018] Therefore, during the predefined operating state, management measures regarding the application are not executed. The machine functions provided by the application are thus not affected and not activated. For example, an operator of the application management system cannot trigger tasks that would disable the functions of the application or change the functions of the application. In this way, the predefined operating state of the machine can be protected from the influence of an external application management system. Ultimately, a trouble-free operation of the machine can be ensured. High operating safety of the machine can be achieved, and operating failures and production failures can be avoided.

[0019] Therefore, the predefined operating state is preferably a (such as critical) state related to the safe operation of the machine and / or production achievements (such as product quality, production quantity). However, other predefined operating states can also be envisaged, such as operating states with low energy consumption, low raw material consumption, low emissions, etc.

[0020] The management measures for prohibiting or preventing the application are preferably implemented directly inside the machine. Optionally, they can also be directly executed by the application management system after providing the corresponding information to the external application management system.

[0021] The controller or its related control program and / or the application can be physically located inside or on the machine. For example, the application can be stored in a so-called edge system and executed. Part of the controller or control program and / or the application can also be stored in a distributed storage and computing structure (such as a cloud platform) and executed therein. In the latter case, these are still attributed to the machine, that is, regarded as internal components of the machine.

[0022] The working processes of the application and the working processes of the application management system preferably run on hardware that is different from and temporally asynchronous with the actuator control, that is, outside the controller, and for example, are not integrated into the communication system for real-time communication between the controller and other components of the machine (such as actuators, sensors). As long as the predefined operating state exists (including a regulated delay time if necessary), the implementation of management measures can be continuously blocked. When the predefined operating state no longer exists, the implementation of management measures can be automatically authorized.

[0023] The management measures involve, for example, starting the application, terminating the application, updating the application, changing the application configuration, and / or uninstalling the application. Therefore, the management measures belong to "technical" management measures.

[0024] Additional functions (usually optional) provided by an application for a machine, which may involve the collection and analysis of machine operation data for machine diagnosis and / or quality monitoring. In addition, it is also possible to implement safety-related functions through pre-calculation and simulation of movements, such as collision monitoring for cutting tools or robot arms, or extension of machine functions (such as calculation of complex process programs).

[0025] To ensure a highly error-free operation of the machine, it is preferred to continuously monitor whether the machine is in a predefined operating state through a controller or its associated control program.

[0026] As an alternative or supplement, the controller or its associated control program can also at least include functions that (automatically) bring the machine into a predefined operating state when executed.

[0027] According to a preferred embodiment, a production machine or a machine tool includes an internal (local) application management unit controlled by an external application management system. The application management unit performs management measures on the application according to the specifications of the application management system, and in the case of a predefined operating state, the application management unit does not implement the specifications of the external application management system as management measures regarding the application.

[0028] For this purpose, the application management unit preferably provides a function (hereinafter simply referred to as the "operating state function") that, when called, the application management unit does not implement the specifications of the external application management system as management measures regarding the application.

[0029] According to a preferred embodiment, during operation, a production machine or a machine tool is continuously monitored by a controller or a related control program for the presence of a predefined operating state, and in the case of a predefined operating state, the controller or the related control program can call this function.

[0030] If the controller or the related control program includes functions for the presence of a predefined operating state during its execution (automatically), the controller or the related control program can call this function during its execution or when there is a predefined operating state.

[0031] According to another advantageous embodiment, a production machine or a machine tool includes an edge system, and the application is stored and executed in this edge system.

[0032] The external application management system can advantageously manage the entire edge system. When there is a predefined operating state of the machine, the management measures of the application management system regarding the edge system will be blocked.

[0033] In addition to the aforementioned management measures for the installed applications in the edge system, the management measures can also involve, for example, installing applications in the edge system, updating the firmware of the edge system, configuring the firmware, or configuring the network settings of the edge system.

[0034] The edge system preferably operates independently of the controller and is not synchronized with the controller in time, that is, it is external to the controller and, for example, is not integrated into the communication system for the controller to communicate in real time with other components of the machine (such as actuators, sensors).

[0035] The application can be implemented using container technology known in the art, that is, it includes at least one virtual container, and the software functions that determine the application's functions are encapsulated within the container.

[0036] According to another preferred embodiment, the application continuously detects whether a predefined operating state exists. This can be achieved, for example, by querying the operating state function of the aforementioned local application management unit. Subsequently, the application can use the operating state assigned to the graphical user interface (for example, to display the operating state).

[0037] When the predefined operating state no longer exists, the implementation of the management measures can be automatically authorized through the operating state function. Alternatively, after the corresponding prompt, the authorization can also be performed by the operator of the application or the application management system.

[0038] If the implementation of the management measures fails to be authorized after the end of the predefined operating state due to error situations (such as forgotten authorization, process problems, programming errors), it can be proposed that after receiving a permission instruction from the operator of the external application management system, the production machine or machine tool stops blocking the management measures of the external application management system. Therefore, it is possible (preferably after prior review) to allow the operator of the external application management system to manually enforce the management measures.

[0039] A production machine or machine tool according to the present invention includes a controller for controlling an actuator of the production machine or machine tool, and a memory having at least one application program stored in the memory, the application program being used to provide additional functions for the production machine or machine tool. Wherein, the machine is provided with an interface for an external application program management system, and the application program can be managed by the application program management system via the interface during the operation of the machine. The machine is configured to prevent the application program management system from taking management measures regarding the application program when there is a predefined operating state of the machine. The production machine or machine tool includes an internal application program management unit, which can be controlled by an external application program management system and implements the specifications of the application program management system as management measures for the application program. Wherein, the application program management unit is configured not to implement the specifications of the application program management system regarding the application program in the predefined operating state. The application program management unit provides a function, when this function is called, the application program management unit does not implement the specifications of the application program management system as management measures regarding the application program.

[0040] The advantages described with respect to the method according to the present invention also apply to the production machine or machine tool according to the present invention. A computer program according to the present invention includes instructions that, when the program is executed by a production machine or machine tool, cause the production machine or machine tool to execute the above-described method.

[0041] A computer-readable storage medium according to the present invention includes instructions that, when executed by a production machine or machine tool, cause the production machine or machine tool to execute the above-described method. Description of the Drawings

[0042] The present invention and other advantageous embodiments according to the features of the dependent claims will be described in detail below in conjunction with the embodiments in the drawings; wherein:

[0043] Figure 1 A production machine or machine tool is shown, which has an application program stored in the memory of the production machine or machine tool

[0044] Figure 2 Shown in Figure 1 Details of the application program in. Detailed Description of the Invention

[0045] Figure 1 A production machine or machine tool 10 of the aforementioned type is shown in a highly simplified schematic form, and is hereinafter generally referred to as the machine 10 for short. The mechanical details of the machine 10, such as the shafts, etc., are not shown. In fact, this illustration is mainly limited to the display of the memory 12 contained in the machine 10, that is, the display of the memory 12 for storing data.

[0046] The so-called runtime environment 14 (Runtime) is loaded into the memory 12 of the machine 10 in a manner known in the art. This runtime environment determines the basic functions of the machine 10 and depends on its configuration. For a machine 10 in the form of a machine tool with exactly two feed axes, the runtime environment 14 includes, for example, a control program or control software 15, which contains a plurality of modules or functional units 16, 16' implemented in software for driving these axes, such as axis drives for position control, speed control, and / or acceleration control. As an example, Figure 1 the drive 19 is shown. The drive performed by the control program 15 is represented by an arrow 21.

[0047] To execute the runtime environment 14 and the software functional units 16 contained therein, the machine 10 includes at least one processing unit 18 implemented in the form or manner of a microprocessor.

[0048] Therefore, the processing unit 18 and the software functional units 16, 16' form the controller 17 of the machine 10. Among them, the software functional unit 16' is a key functional unit for faultless operation. Among them, the controller 17 is connected to various machine components such as sensors and actuators (such as the actuator 19) via a real-time communication bus (such as PROFINET) not shown in detail.

[0049] The functions of the runtime environment 14 are fixed when the corresponding machine 10 is delivered. In principle, the functions of the runtime environment 14 can be changed or extended by updating or upgrading the runtime environment 14.

[0050] In addition, the machine 10 is extended with additional optional functions by an application program 30. Here, the basic functions of the machine 10 remain unchanged.

[0051] Such application programs 30 are either installed when the machine is delivered or installed after it is put into operation.

[0052] For this, the application program 30 is stored in the memory 53 of the so-called edge system 50. The edge system 50 is included in the machine 10 or at least has a communication connection with the machine 10. In this regard, the edge system 50 belongs to the machine 10.

[0053] However, in principle, it is also feasible to store parts of the controller 17 or the control program 15 and / or the application program 30 in a distributed memory and computing structure (such as a cloud platform) and execute them there. But in the latter case, they are still regarded as the machine 10, that is, regarded as internal components of the machine 10.

[0054] In Figure 2The example in [the figure] shows a single application 30 in a schematically simplified form. In order for the application 30, which is available in an app store for example, to be able to run on any machine 10 in principle, the application 30 includes at least one so-called virtual container 32 or a plurality of virtual containers 32. Such containers 32 are the basic objects of so-called container virtualization. The concept of container virtualization and the use of virtual containers themselves are known. Therefore, there is no need to further explain container virtualization and virtual containers here, and reference can be made to relevant professional literature.

[0055] In a manner that is basically known per se, the container 32 includes at least one software function 34 belonging to the application 30 ( Figure 2 ), and a runtime environment for the software function or for each software function 34 contained in the container 32 (container runtime environment 36; Figure 2 ). The software function 34 or the set of all software functions 34 contained in the application 30 in one or more containers 32 determines the function of the application 30. The application 30 includes a configuration (application configuration 38), which includes configuration information (container interface) for at least one or the above-mentioned or each container 32 belonging to the application 30. The container interface maps the names of devices, resources, etc. used inside the container 32 to the corresponding names of devices, resources, etc. that can be used outside the container 32. Therefore, this allows, for example, using the name of the network to access a (virtual or real) network without having to know in advance how the network is named on the host system (for example, the machine 10 to which the application 30 containing the container 32 is downloaded). The container interface ensures, in a manner well-known in the art, the decoupling of the container 32 from the devices, resources, etc. of a host system that is unknown at the time of development of the container 32 and is arbitrary in principle. The application configuration 38 belonging to the downloaded application 30 is the set of all container interfaces of the containers 32 contained in the application 30. The application configuration 38 and its configuration information are automatically evaluated, for example, and modified if necessary according to the method proposed in EP 3 650 968 A1 to prevent conflicts with other applications.

[0056] In Figure 1 the extremely simplified schematic diagram, the edge system 50 is shown as a module of the machine 10, and the machine itself is only shown as a module.

[0057] The edge system 50 includes, in a manner well-known in the art, its own processing unit 56 in the form or manner of a microprocessor.

[0058] Therefore, the working process of the application 30 is carried out on hardware different from the controller 17 and is out of sync in time, that is, it is external to the controller 17 and is not integrated into the real-time communication bus of the machine components, for example.

[0059] An external application management system 40 is used to manage the edge system 50, in particular to manage the applications 30 stored in the edge system. In this context, "external" means that the application management system 40 operates independently of the controller 17 or the control program 15 and manages the edge system 50, in particular the applications 30 in the edge system.

[0060] The external application management system 40 is a computer program that is loaded into the memory 45 of an accessible computer or computer system (such as in the cloud 20), or can also be loaded into the distributed memory 45 of a distributed computer system.

[0061] Therefore, the working processes of the application management system 40 also take place on hardware different from the controller 17 and are asynchronous in time.

[0062] The external application management system 40 manages the edge system 50, in particular the applications 30, through a variety of management measures: with regard to the application 30, the management measures can, for example, involve starting the application, terminating the application, modifying the configuration of the application, or uninstalling the application. With regard to the edge system 50, the management measures can, for example, include installing an application in the edge system 50, updating the firmware of the edge system 50, configuring the firmware, or configuring the network settings of the edge system 50.

[0063] In order to implement the management measures in the production machine or machine tool 10, which includes an internal (local) application interface and an application management unit, hereinafter simply referred to as the application management unit 52. The application management unit 52 is controlled by the external application management system 40 (represented by the arrow 25) and implements the specifications of the external application management system 40 as management measures for the edge system 50, in particular the applications 30. For this purpose, the application management unit 52 includes an interface 51 for communicating with the application management system 40.

[0064] The management unit 52 is implemented as a computer program or a computer program module (which can be a distributed computer program, computer program module) and is loaded into the memory 53 of the edge system 50.

[0065] According to the invention, in the case of a predefined operating state of the machine 10, the management measures of the application management system 40 regarding the edge system 50 with the applications 30 are blocked. Therefore, in the predefined operating state, the edge system 50 with the applications 30 is blocked against the management measures of the application management system 40.

[0066] Accordingly, the predefined operating state refers to a state that is relevant (e.g., critical) to the safe operation of the machine and / or production achievements (e.g., related to product quality, production quantity). However, other predefined operating states can also be envisioned, such as operating states with low energy consumption, low raw material consumption, low emissions, etc.

[0067] Accordingly, during the predefined operating state, no management measures regarding the edge system 50 are executed on the application 30. Thus, the functions of the machine 10 provided by the application 30 are not impaired and do not even fail. Thereby, the predefined operating state of the machine 10 can be protected from the influence of the external application management system 40. Accordingly, the error-free operation of the machine 10 can be further improved.

[0068] For this purpose, the application management unit 52 provides a special function 55 (hereinafter referred to as "operating state function 55"), and when this function is called, the application management unit 52 does not implement the specifications of the external application management system 40 as management measures regarding the application 30.

[0069] Then the management measures can be blocked by the operating state function 55 during the time length in which the predefined operating state exists (which can have a defined operating time). When the predefined operating state no longer exists, the permission to implement the management measures can be automatically issued.

[0070] Accordingly, the machine is continuously monitored by the controller 17 or the control program 15 during operation to determine whether the machine is in the predefined operating state. For example, this can be achieved by evaluating sensor signals (not shown in detail) of the machine 10, evaluating functions active in the controller 17 or the control program 15, and / or evaluating specifications from a superior controller (such as an MES system or a process control system).

[0071] In addition, when the software function 16' is executed, the predefined operating state automatically appears.

[0072] In both of the above cases, in the case of the predefined operating state, the controller 17 or the control program 15 calls the operating state function 55 to block the management measures. For example, in Figure 1 the software function 16' calls the operating state function 55, as shown by the arrow 57.

[0073] Accordingly, the application 30 also continuously determines whether the predefined operating state exists. This is achieved by querying the aforementioned operating state function 55. Subsequently, the application 30 can use the operating state of the graphical user interface assigned to them in each case (e.g., display this operating state).

[0074] If the predefined operating state no longer exists (for example, software function 16 is no longer executed), the controller 17 or the control program 15 will also notify this situation to the operating state function 55 through the corresponding call. Then, the operating state function 55 automatically authorizes (or "unlocks") the implementation of the management measure. Optionally, after the corresponding prompt, authorization can also be performed by the operator of the application 30 or the application management system 40.

[0075] If the authorization for the implementation of the management measure fails after the end of the predetermined operating state due to an error situation (such as forgotten authorization, process failure, programming error), the operator of the external application management system 40 (preferably after prior review) is allowed to manually enforce the management measure. For this purpose, the operator can issue a permission instruction and convey the permission instruction to the internal application management unit 52 via the interface 51. After receiving the permission instruction, the internal application management unit 52 will terminate the blocking of the management measure for the external application management system 40.

[0076] For this, the application management system 40 can also include an application store in a manner not shown in detail or be communicatively connected to the application store. Then, the application 30 is downloaded from the application management system 40 to the edge system 50 in a manner that downloads the application 30 together with the container or each container 32 included in the application 30 and the application configuration 38 included in the application 30. During the deployment process, the automatic evaluation of the application configuration 38 is also performed by the management unit 52. The management unit 52 provides a defined interface 54 for the downloaded or stored application 30. These interfaces 54 are schematically simplified as "channels" passing through the management unit 52 in Figure 1 shown. The interface 54 can be implemented, for example, by a dedicated "adapter" application of the edge system 50 (for example, for the S7 protocol, OPC - OA protocol, HMI service (OMS++S7)).

[0077] Access to the runtime environment 14 of the machine 10 and the devices and resources included in or subordinate to the machine 10 can only be performed via the management unit 52 and the interfaces 54 defined here. Here, the management unit 52 acts as an interface for the machine 10 and as a security layer between the downloaded application 30 and the machine 10. Only the management unit 52 starts the downloaded application 30 and the container or each container 32 included therein (also controlled by the application management system 40). To such an extent, the downloaded application 30 is respectively prepared to execute at least one IoT function, the management unit 52 enables the IoT function to be supplemented to the function of the machine 10, and the management unit 52 acts as a platform for machine - specific IoT extensions.

Claims

1. A method for operating a production machine or a machine tool (10), the production machine or machine tool comprising a controller (17) for controlling an actuator (19) of the production machine or machine tool (10) and at least one application program (30) for providing additional functions for the production machine or machine tool (10), wherein, The application (30) is managed by an external application management system (40) during the operation of the production machine or machine tool (10), wherein, in the case of a predefined operating state of the production machine or machine tool (10), the management measures of the application management system (40) regarding the application (30) are blocked, wherein the production machine or machine tool (10) includes an internal application management unit (52) controlled by the external application management system (40), and the internal management unit implements the specifications of the application management system (40) as management measures regarding the application (30), and wherein, in the case of the predefined operating state, the application management unit (52) does not implement the specifications of the application management system (40) regarding the application (30), characterized in that the application management unit (52) provides a function (55), when the function is called, the application management unit does not implement the specifications of the external application management system (40) as management measures regarding the application (30).

2. The method according to claim 1, wherein, The management measures relate to: starting the application, terminating the application, updating the application (30), changing the configuration of the application (30) and / or uninstalling the application (30).

3. The method according to any one of the preceding claims, wherein, The predefined operating state is a state related to the safe operation and / or production achievement of the production machine or machine tool (10).

4. The method according to any one of the preceding claims, wherein, The production machine or machine tool (10) is monitored for the presence of the predefined operating state.

5. A method according to any one of the preceding claims, wherein During operation, the production machine or machine tool (10) is continuously monitored by the controller (17) for the presence of the predefined operating state, and wherein, in the case of the predefined operating state, the controller (17) calls the function (55).

6. The method according to any one of the preceding claims, wherein, The controller includes a function (16'), and the predefined operating state exists during the execution of the function.

7. The method according to claim 6, wherein, In the case of the predefined operating state, the controller (17) calls the function (55).

8. A method according to any one of the preceding claims, wherein The production machine or machine tool (10) includes an edge system (50), and wherein the application (30) is stored and executed in the edge system (50).

9. The method according to claim 8, wherein The external application management system (40) manages the edge system (50), and wherein, in the case of the predefined operating state of the production machine or machine tool (10), the management measures of the application management system (40) regarding the edge system (50) are blocked.

10. The method according to claim 9, wherein, The management measures relate to: installing an application in the edge system (50), updating the firmware of the edge system (50), configuring the firmware and / or configuring the network settings of the edge system (50).

11. The method according to any one of the preceding claims, wherein, The application (30) continuously determines whether the predefined operating state exists.

12. The method according to any one of the preceding claims, wherein, After receiving a permission instruction from the external application management system (40), the production machine or machine tool (10) stops blocking the management measures of the external application management system (40).

13. A production machine or machine tool (10), comprising: - a controller for controlling an actuator of the production machine or machine tool (10), - a memory (53) having at least one application program (30) stored in the memory, the application program being used to provide additional functions for the production machine or machine tool (10), - an interface (51) for an external application management system (40), the application program (30) being able to be managed by the application management system (40) via the interface during the operation of the production machine or machine tool (IO), characterized in that the production machine or machine tool (10) is configured to block the management measures of the application management system (40) regarding the application program (30) in a predefined operating state of the production machine or machine tool (10), wherein the production machine or machine tool (10) includes an internal application management unit (52), the internal application management unit can be controlled by the external application management system (40), and the internal application management unit implements the specifications of the application management system (40) as management measures regarding the application program (30), and wherein the application management unit (52) is configured not to implement the specifications of the application management system (40) regarding the application program (30) in the predefined operating state, characterized in that the application management unit (52) provides a function (55), when the function is called, the application management unit does not implement the specifications of the external application management system (40) as management measures regarding the application program (30).

14. A computer program, comprising instructions that, when the program is executed by a production machine or machine tool (10), cause the production machine or machine tool to perform the method according to any one of claims 1 to 12.

15. A computer-readable storage medium, comprising instructions that, when executed by a production machine or machine tool (10), cause the production machine or machine tool to perform the method according to any one of claims 1 to 12.

Images