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

Abstract

In a method for operating a production machine or machine tool (10), which comprises a controller (17) for controlling actuators (19) of the production machine or machine tool (10) and at least one app (30) for providing additional functions for the production machine or machine tool (10), wherein the app (30) is administered, during operation of the production machine or machine tool (10), by an external app management system (40), an administrative measure of the app management system (40) in relation to the app (30) is prevented in the event of a predefined operating state of the production machine or machine tool (10). The production machine or machine tool (10) comprises an internal app administration unit (52) which is controlled by the external app management system (40) and converts the specifications of the app management system (40) into administrative measures in relation to the app (30), and wherein the app administration unit (52) does not convert the specifications of the app management system (40) in relation to the app (30) in the event of the predefined operating state. According to the invention, the app administration unit (52) provides a function (55) which, when called, does not convert the specifications of the external app management system (40) into administrative measures in relation to the app (30). As a result, error-free operation of the production machine or machine tool (10) can be ensured.

Description

[0001] Description

[0002] Method for operating a production machine or machine tool and production machine or machine tool

[0003] The invention relates to a method for operating a production machine or machine tool according to patent claim 1 and to a production machine or machine tool according to patent claim 13. The invention further relates to a computer program according to patent claim 14 and a computer-readable storage medium according to patent claim 15.

[0004] Production machines and machine tools are well known and typically include one or more actuators that convert electrical control signals output by a controller into mechanical movements or changes in physical quantities such as pressure or temperature, thus actively intervening in a controlled process. For example, an actuator can be a drive or a heating element.

[0005] The production machine can be a machine from the discrete manufacturing industry (e.g. a machine for producing vehicle components), the process industry (e.g. a machine for manufacturing a pharmaceutical product), the food and beverages industry or the energy generation industry (e.g. wind turbine, solar power plant). In the case of a machine tool, the actuators include, for example, one or more drives (feed drives) for positioning a tool. Such machines are each a complex combination of different logical and physical components (e.g. drives, axes, etc.) with diverse multiplicity. Such machines usually include a controller (e.g. a numerical controller) to control the actuators. Within the framework of Industry 4.0 and the so-called Internet of Things (IoT), it is possible to expand a specific function of such a machine with additional functions or microservices using so-called apps. Such apps are available for download in a so-called cloud, for example, and are provided there by a cloud platform (App Store). Downloading an app from a cloud platform and installing the downloaded app on a target system (host system), in this case a production or machine tool, is referred to as deployment.

[0006] A production machine or machine tool with such an app downloaded from a cloud, including an app with functionality encapsulated in a container, is known per se, for example from EP 3 650 968 A1.

[0007] An app can be offered in an app store for generic machines. The specific structure of a subsequent host system and the runtime environment of the host system are not known, and this knowledge is also not required. For this purpose, the app can comprise at least one virtual container used in so-called container virtualization (hereinafter referred to as container), and software functionality belonging to the app is embedded in the or each container comprised by the app. The or each container comprises at least one runtime environment necessary to execute the respectively embedded software functionality. The runtime environment comprised by the container enables the respective software functionality to be executed independently of the host system and its runtime environment.An app loaded onto a host system is launched on the host system by starting the container or containers it contains and is limited to the virtual container or containers it contains. Such containers are known per se, and in this respect, reference can be made, for example, to the software known as "Docker" for so-called container virtualization. Another example is "LXC" (Linux Containers).

[0008] The (usually optional) additional functionalities for the machine provided by the apps can, for example, relate to the recording and analysis of machine operating data. However, they can also enable safety-relevant functions such as collision monitoring for tools or robot arms, or functional extensions for production cycles (e.g., the calculation of complex traversing programs).

[0009] The expansion of a machine with such apps is often done with the help of a so-called "edge system", which is either integrated into the machine during production or retrofitted later.

[0010] The process of such apps usually runs on hardware that is different from the control of the actuators and is not synchronized in time, so it is external to the control and is not, for example, integrated into a real-time communication bus of machine components.

[0011] However, the apps or these edge systems are usually not managed by the machine, but by an "external" app management system, which is often spatially distant from the machine (e.g. in a cloud). Management actions of the external app management system with regard to an app can, for example, include starting the app, closing the app, updating the app, changing the app's configuration and / or uninstalling the app.

[0012] In this context, "external" for the app management system means that the app management system runs independently of the machine's control system and manages the apps, for example based on specifications (commands) from an operator or developer of the app or the app management system.

[0013] The app management system can also run locally on the edge system (for example, a UI of an app), but is then still considered external to the machine.

[0014] The document EP 3 923 095 A1 discloses a method according to the preamble of patent claim 1. In this method, software (e.g. an app) of a technical system, such as a production machine, is managed by a configuration device. An update server is used to control and monitor a software update on the basis of an update configuration and a software update provided by the configuration device. The update server comprises a monitoring module which, while the software update is being carried out, records operating parameters of the technical system and / or of the corresponding elements of the technical system, determines a test result based on operating specifications and the operating parameters, and controls the further implementation of the software update based on the test result.For example, if the operating parameters exceed the operating specifications, an alarm is triggered and / or the software update is aborted, and if the operating parameters comply with the operating specifications, the software update is continued.

[0015] Based on this, the object of the present invention is to ensure error-free operation of such a production or machine tool, in particular to ensure high operational reliability and to avoid operational disruptions and production errors.

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

[0017] The method according to the invention serves to operate a production machine or machine tool, which comprises a controller for controlling actuators of the production machine or machine tool and at least one app for providing (usually optional) additional functionalities for the production machine or machine tool. The app is managed during operation of the machine by an external app management system, in particular one that is spatially remote from the machine. In other words, the app is managed independently of the controller (or a control program) of the production machine or machine tool.

[0018] According to the invention, if a predefined operating state of the machine exists, an administrative action by the app management system with respect to the app is prevented. The app is thus blocked from an administrative action by the app management system with respect to the app in the predefined operating state.

[0019] Consequently, no management measures are carried out in relation to the app during the predefined operating state. Machine functionalities provided by the app cannot be impaired or even deactivated. For example, an operator of the app management system cannot trigger jobs that deactivate the app's function or change the app's functionality. This protects predefined operating states of the machine from being influenced by the external app management system. As a result, error-free operation of the machine can be guaranteed. A high level of operational reliability of the machine can be achieved, and malfunctions and production errors can be avoided.

[0020] The predefined operating state is therefore preferably a state relevant (e.g., critical) for the safe operation and / or production success (e.g., with regard to product quality, production volume) of the machine. However, other predefined operating states are also conceivable, such as an operating state with low energy consumption, low raw material consumption, low emissions, etc.

[0021] Preventing or blocking the app from administrative measures is preferably done directly within the machine. Alternatively, it can also be done directly by the app management system after appropriate notification has been sent to the external app management system.

[0022] The controller or an associated control program and / or the app can be located locally in or on the machine. For example, the app can be stored and executed in a so-called edge system. However, it is also possible that parts of the controller or the control program and / or the app are stored and executed on distributed storage and computing structures (e.g., a cloud platform). In the latter case, however, these are attributed to the machine, i.e., considered internal components of the machine.

[0023] An app workflow and an app management system workflow preferably run on hardware that is different from and not synchronized in time from the actuator controller. This means that they are external to the controller and are not integrated, for example, into a communication system for real-time communication between the controller and other machine components (e.g., actuators, sensors). The administrative measure can then be prevented as long as the predefined operating state exists (if necessary, with a defined follow-up time). When the predefined operating state no longer exists, approval for the implementation of administrative measures can be granted automatically.

[0024] The administrative measures may include, for example, starting the app, closing the app, updating the app, changing the app's configuration, and / or uninstalling the app. In this respect, the administrative measures are "technical" administrative measures.

[0025] The (usually optional) additional functionalities for the machine provided by the app can, for example, relate to the recording and analysis of machine operating data for machine diagnostics and / or quality monitoring. However, safety-relevant functions can also be enabled, such as collision monitoring for tools or robot arms using pre-calculations and simulations of movements, or extensions to machine functions (e.g., the calculation of complex traversing programs).

[0026] To ensure particularly high levels of error-free machine operation, the machine is preferably continuously monitored for the presence of the predefined operating state, for example by the control system or an associated control program.

[0027] Alternatively or additionally, the control or an associated control program can also comprise at least one functionality, the execution of which (automatically) results in the predefined operating state.

[0028] According to an advantageous embodiment, the production or machine tool comprises an internal (local) app management unit which is controlled by the external app management system and implements the specifications of the app management system for management measures with regard to the app, and wherein the app management unit does not implement the specifications of the app management system for management measures with regard to the app when the predefined operating state is present.

[0029] For this purpose, the app management unit advantageously provides a function (hereinafter referred to as the "operational status function"), which, when called, does not implement the specifications of the external app management system regarding administrative measures with regard to the app.

[0030] According to an advantageous embodiment, the production machine or machine tool is then continuously monitored during operation by the controller or an associated control program for the presence of the predefined operating state, and the controller or an associated control program can then call the function when the predefined operating state is present.

[0031] If the controller or an associated control program includes a functionality which, when executed (automatically), results in the predefined operating state, then the controller or an associated control program can call the function when executed or when the predefined operating state is present.

[0032] According to a further advantageous embodiment, the production or machine tool comprises an edge system and the app is stored in the edge system and is executed therein.

[0033] The external app management system then advantageously manages the entire edge system, whereby, if the machine is in a predefined operating state, any administrative action by the app management system related to the edge system is prevented. In addition to the administrative actions already explained regarding an app installed in the edge system, the administrative action can also include, for example, installing an app in the edge system, updating the edge system's firmware, configuring the firmware, or configuring the edge system's network settings.

[0034] The edge system preferably runs independently of and is not synchronized with the controller, i.e. it is external to the controller and is not, for example, integrated into a communication system for real-time communication between the controller and other components of the machine (e.g. actuators, sensors).

[0035] The app can be implemented in a manner known per se using container technology, i.e. it can comprise at least one virtual container with software functionality encapsulated therein which determines the function of the app.

[0036] According to a further advantageous embodiment, the app continuously determines whether the predefined operating state is present. This can be done, for example, by querying the operating status function of the local app management unit explained above. The app can then use the operating status for a graphical user interface assigned to it (e.g., display it).

[0037] If the predefined operating state no longer exists, the operating status function can automatically authorize the implementation of administrative measures. Alternatively, the authorization can be granted by an operator of the app or the app management system upon request.

[0038] In the event that, due to faulty circumstances (e.g., forgotten approval, process problems, programming errors), no approval for the implementation of administrative measures has been granted after the expiration of the predefined operating state, it can be provided that the prevention of administrative measures by the external app management system is terminated upon receipt of an approval command from an operator of the external app management system. An operator of the external app management system can thus be enabled (preferably after prior verification) to manually enforce the implementation of administrative measures.

[0039] A production machine or machine tool according to the invention comprises a controller for controlling actuators of the production machine or machine tool and a memory with at least one app stored therein for providing additional functionalities for the production machine or machine tool, wherein the machine has an interface to an external app management system via which the app can be managed by the app management system during operation of the machine. The machine is designed to prevent a management measure of the app management system with regard to the app if a predefined operating state of the machine exists.The production machine or machine tool comprises an internal app management unit that can be controlled by the external app management system and implements the app management system's specifications for management measures with respect to the app. The app management unit is configured not to implement the app management system's specifications for the app when the predefined operating state is present. The app management unit provides a function that, when called, does not implement the external app management system's specifications for management measures with respect to the app.

[0040] The advantages mentioned for the method according to the invention apply accordingly to the production machine or machine tool according to the invention. A computer program according to the invention comprises instructions which, when the program is executed by a production machine or machine tool, cause the machine to carry out the method explained above.

[0041] A computer-readable storage medium according to the invention comprises instructions which, when executed by a production machine or machine tool, cause the machine to carry out the method explained above.

[0042] The invention and further advantageous embodiments of the invention according to the features of the subclaims are explained in more detail below with reference to exemplary embodiments in the figures, in which:

[0043] FIG 1 a production or machine tool with apps stored in a memory of the production or machine tool,

[0044] FIG 2 Details of an app from FIG 1 .

[0045] The illustration in Figure 1 shows, in a highly simplified schematic form, a production machine or machine tool 10 of the type mentioned above, often referred to simply as machine 10 below. Mechanical details of the machine 10, such as axes or the like, are not shown. Rather, the illustration is essentially limited to a representation of a memory 12 included in the machine 10, namely a memory 12 for storing data.

[0046] A so-called runtime environment 14 (runtime environment or runtime for short) of the machine 10 is loaded into the memory 12 in a manner known per se. This determines the basic functionality of the machine 10 and depends on its configuration. In a machine 10 in the form of a machine tool with exactly two feed axes, the runtime environment 14 comprises, for example, a control program or control software 15 which comprises a plurality of modules or functional units 16, 16' implemented in software for controlling drives of these axes, for example for position-controlled, speed-controlled and / or acceleration-controlled axis control. A drive 19 is shown as an example in FIG 1. The control by the control program 15 is symbolized by an arrow 21.

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

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

[0049] The functionality of the runtime environment 14 is fixed at the time of delivery of the respective machine 10. In principle, the functionality of the runtime environment 14 can be changed or expanded by an update or upgrade of the runtime environment 14.

[0050] In addition, Machine 10 has been enhanced with additional optional functionality through Apps 30. The basic functionality of Machine 10 has remained untouched.

[0051] Such apps 30 are either already installed when the machine is delivered or were subsequently installed after commissioning.

[0052] The apps 30 are stored in a memory 53 of a so-called edge system 50. The edge system 50 is comprised by the machine 10 or at least communicatively connected to the machine 10. In this respect, the edge system 50 belongs to the machine 10.

[0053] In principle, however, it is also possible for parts of the controller 17 or the control program 15 and / or the apps 30 to be stored on distributed storage and computing structures (e.g., a cloud platform) and executed there. In the latter case, however, these are attributed to the machine 10, i.e., are considered internal components of the machine 10.

[0054] The illustration in FIG 2 shows a single app 30 in a simplified schematic form. So that an app 30 available, for example, in an app store can be executed on basically any machine 10, the app 30 comprises at least one so-called virtual container 32 or several virtual containers 32. Such a container 32 is the basic object of so-called container virtualization. The concept of container virtualization and the use of virtual containers are known per se. Further explanations of container virtualization and virtual containers are therefore not required here, and reference is made to the relevant specialist literature.

[0055] A container 32 comprises, in a manner known per se, at least one software functionality 34 belonging to the app 30 (FIG. 2) and a runtime environment (container runtime environment 36; FIG. 2) for the or each software functionality 34 included in the container 32. The software functionality 34 or the entirety of the software functionalities 34 included by the app 30 in a container 32 or more containers 32 determines the functionality of the app 30. The app 30 includes a configuration (app configuration 38) which includes configuration information (container interface) for at least one or the or each container 32 belonging to the app 30. A container interface maps the names of devices, resources, and the like used within the container 32 to a name for the respective device, resource, etc. that can be used outside the container 32.This means that within the container 32, for example, a name can be used for this network to access a (virtual or real) network, without it already being known what the network is called on a host system, for example a machine 10 onto which the app 30 comprising this container 32 is downloaded. The container interface ensures, in a manner known per se, the decoupling of the container 32 from the devices, resources and the like of a host system that is, on the one hand, unknown and, on the other hand, fundamentally arbitrary at the time of development of the container 32. The app configuration 38 belonging to a downloaded app 30 is the totality of all container interfaces of the containers 32 comprised by the app 30. The app configuration 38 and its configuration information is or are automatically evaluated, for example, according to the approach proposed in EP 3 650 968 A1, and if necessary.modified to prevent conflicts with other apps.

[0056] In the extremely simplified schematic representation in FIG 1, the edge system 50 is shown as a block within the machine 10, which itself is shown only as a block.

[0057] The edge system 50 comprises, in a manner known per se, its own processing unit 56 in the form of or in the manner of a microprocessor.

[0058] The execution process of the apps 30 thus runs on hardware that is different from the controller 17 and not synchronized in time. It is therefore external to the controller 17 and is not, for example, integrated into a real-time communication bus of the machine components. An external app management system 40 is used to manage the edge system 50, and in particular to manage the apps 30 stored therein. "External" in this context means that the app management system 40 runs independently of the controller 17 or the control program 15 and manages the edge system 50, and in particular the apps 30.

[0059] The external app management system 40 is a computer program that is loaded into a memory 45 of a computer or computer system accessible, for example, in a cloud 20, or possibly also into a distributed memory 45 of a distributed computer system.

[0060] The process of the app management system 40 also runs on hardware that is different from the controller 17 and is not synchronized in time.

[0061] The external app management system 40 manages the edge system 50, in particular the apps 30, through various management actions: With respect to the apps 30, a management action can be, for example, starting the app, stopping the app, changing the app's configuration, or uninstalling the app. With respect to the edge system 50, a management action can be, for example, installing an app in the edge system 50, updating firmware of the edge system 50, configuring the firmware, or configuring network settings of the edge system 50.

[0062] To implement management measures in the production machine or machine tool 10, the latter comprises an internal (local) app interface and app management unit, hereinafter referred to as the app management unit 52. The app management unit 52 is controlled by the external app management system 40 (symbolized by an arrow 25) and implements the specifications of the external app management system 40 regarding management measures with respect to the edge system 50, and in particular the apps 30. For this purpose, the app management unit 52 comprises an interface 51 for communication with the app management system 40.

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

[0064] According to the invention, if a predefined operating state of the machine 10 exists, an administrative measure of the app management system 40 with respect to the edge system 50 with the apps 30 is prevented. The edge system 50 with the apps 30 is thus blocked from an administrative measure of the app management system 40 in the predefined operating state.

[0065] The predefined operating state is a state relevant (e.g., critical) for the safe operation and / or production success (e.g., in terms of product quality, production volume) of the machine. However, other predefined operating states are also conceivable, such as an operating state with low energy consumption, low raw material consumption, low emissions, etc.

[0066] Consequently, during the predefined operating state, no management actions are performed with respect to the edge system 50 with the apps 30. Functionalities of the machine 10 provided by the apps 30 cannot be impaired or even deactivated. This allows predefined operating states of the machine 10 to be protected from influence by the external app management system 40. As a result, the error-free operation of the machine 10 can be increased.

[0067] For this purpose, the app management unit 52 provides a special function 55 (hereinafter referred to as "operating status function 55"), upon calling which the app management unit 52 does not implement the specifications of the external app management system 40 regarding administrative measures with regard to the apps 30. The prevention of the administrative measures by the operating status function 55 can then take place as long as the predefined operating state exists (if necessary with a defined follow-up time). When the predefined operating state no longer exists, approval for the implementation of administrative measures can then be given automatically.

[0068] The machine is continuously monitored by the controller 17 or the control program 15 during operation to ensure that the predefined operating state is present.

[0069] This is done, for example, by evaluating signals from sensors of the machine 10 (not shown in detail), evaluating the functions active in the controller 17 or the control program 15 and / or evaluating specifications from a higher-level control system such as an MES system or a process control system.

[0070] In addition, the predefined operating state is automatically present when the software functionality 16 ' is executed.

[0071] In both cases, the controller 17 or the control program 15 calls the operating status function 55 when the predefined operating state is present, thus preventing the management measures. For example, in FIG. 1, the software functionality 16 calls the operating status function 55, illustrated by the arrow 57.

[0072] The apps 30 also continuously determine whether the predefined operating state is present. This is done by querying the operating status function 55 explained above. The apps 30 can then use the operating status for a graphical user interface assigned to them (e.g., display it).

[0073] If the predefined operating state no longer exists (for example, the software functionality 16 is no longer executed), the controller 17 or the control program 15 also informs the operating status function 55 of this by a corresponding call. The operating status function 55 then automatically releases (or "unlocks") the implementation of administrative measures. Alternatively, after a corresponding request, the release can also be made by an operator of the apps 30 or the app management system 40.

[0074] In the event that, due to faulty circumstances (e.g., forgotten approval, process problems, programming errors), no approval for the implementation of administrative measures has been granted after the expiration of the predefined operating state, an operator of the external app management system 40 is enabled (preferably after prior verification) to manually force the implementation of administrative measures. To do so, the operator can issue an approval command and communicate with the internal app management unit 52 via the interface 51. Upon receipt of such an approval command, the internal app management unit 52 terminates the prevention of administrative measures by the external app management system 40.

[0075] The app management system 40 can also include an app store in a manner not shown in detail or be communicatively connected to such an app store. The downloading of an app 30 then takes place by downloading the app 30 together with the or each container 32 included in the app 30 as well as the app configuration 38 included in the app 30 from the app management system 40 to the edge system 50. The automatic evaluation of the app configuration 38 during deployment also takes place by means of the management unit 52. The management unit 52 provides defined interfaces 54 for downloaded or stored apps 30. Such interfaces 54 are shown schematically simplified in the illustration in FIG. 1 as "channels" through the management unit 52. The interfaces 54 can be implemented, for example, by special "adapter" applications of the edge system 50 (e.g.for S7 protocol, OPC-OA protocol, HMI services (OMS+ + S7) ).

[0076] Access to the runtime environment 14 of the machine 10 and to devices and resources comprised by the machine 10 or belonging to the machine 10 is only possible via the management unit 52 and the interfaces 54 defined there. In this respect, the management unit 52 acts as an interface to the machine 10 and as a security layer between a downloaded app 30 and the machine 10. Only the management unit 52 starts a downloaded app 30 and the or each container 32 comprised thereby (again controlled by the app management system 40). To the extent that downloaded apps 30 are each intended to execute at least one IoT function, the management unit 52 enables the functionality of the machine 10 to be supplemented with IoT functions, and the management unit 52 acts as a platform for machine-specific IoT extensions.

Claims

Patent claims 1. A method for operating a production machine or machine tool (10), which comprises a controller (17) for controlling actuators (19) of the production machine or machine tool (10) and at least one app (30) for providing additional functionalities for the production machine or machine tool (10), wherein the app (30) is managed by an external app management system (40) during operation of the production machine or machine tool (10), wherein, if a predefined operating state of the production machine or machine tool (10) exists, a management measure of the app management system (40) with respect to the app (30) is prevented, wherein the production machine or machine tool (10) comprises an internal app management unit (52) which is controlled by the external app management system (40) and implements the specifications of the app management system (40) for management measures with respect to the app (30),and wherein the app management unit (52) does not implement the specifications of the app management system (40) with respect to the app (30) when the predefined operating state is present, characterized in that the app management unit (52) provides a function (55) which, when called, does not implement the specifications of the external app management system (40) regarding management measures with respect to the app (30).

2. The method according to claim 1, wherein the management action is starting the app, stopping the app, updating the app (30), changing the configuration of the app (30) and / or uninstalling the app (30).

3. Method according to one of the preceding claims, wherein the predefined operating state is a state relevant for safe operation and / or for production success of the production or machine tool (10).

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

5. Method according to one of the preceding claims, wherein the production or machine tool (10) is continuously monitored during operation by the controller (17) for the presence of the predefined operating state and wherein the controller (17) calls the function (55) when the predefined operating state is present.

6. Method according to one of the preceding claims, wherein the control comprises a functionality (16') during the execution of which the predefined operating state is present.

7. The method according to claim 6, wherein the controller (17) when the predefined operating state is present performs the function (55) calls.

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

9. The method according to claim 8, wherein the external app management system (40) manages the edge system (50) and wherein, if the predefined operating state of the production or machine tool (10) is present, a management measure of the app management system (40) with respect to the edge system (50) is prevented.

10. The method according to claim 9, wherein the management measure is an installation of an app in the edge system (50), an update of a firmware of the edge system (50), a configuration of the firmware and / or a configuration of network settings of the edge system (50).

11. Method according to one of the preceding claims, wherein the app (30) continuously determines whether the predefined operating state is present 12. The method according to any one of the preceding claims, wherein the production or machine tool (10) terminates the prevention of management measures of the external app management system (40) after receiving a release command from the external app management system (40).

13. Production machine or tool (10) comprising - a controller for controlling actuators of the production machine or machine tool (10), - a memory (53) with at least one app (30) stored therein for providing additional functionalities for the production or machine tool (10), - an interface (51) to an external app management system (40), via which the app (30) can be managed by the app management system (40) during operation of the production machine or machine tool (10), characterized in that the production machine or machine tool (10) is designed to prevent a management measure of the app management system (40) with respect to the app (30) when a predefined operating state of the production machine or machine tool (10) exists, wherein the production machine or machine tool (10) comprises an internal app management unit (52) which is controllable by the external app management system (40) and implements the specifications of the app management system (40) for management measures with respect to the app (30), and wherein the app management unit (52) is designed not to implement the specifications of the app management system (40) with respect to the app (30) when the predefined operating state exists, characterized inthat the app management unit (52) provides a function (55) which, when called, does not implement the specifications of the external app management system (40) regarding management measures with regard to the app (30).

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

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

Images