Technical management system for orchestrating a plurality of technical components of a technical system

Abstract

The invention relates to a technical management system (1) for orchestrating a plurality of technical components (12) of a technical system (10), wherein each technical component (12) of the plurality of technical components is a hardware component or a software component, wherein each technical component (12) of the plurality of technical components comprises at least one active part, wherein the plurality of technical components (12) interact with each other in the technical system, comprising: a. a runtime environment (14) for the active parts of the plurality of technical components (12); wherein the active parts of the plurality of technical components (12) execute in the runtime environment (14); and b. an interface (16) for the active parts of the plurality of technical components (12); wherein the interface (16) is configured for establishing the execution of the active parts of the plurality of technical components (12) in the runtime environment (14). Further, the invention relates to a corresponding runtime environment, a corresponding interface, a corresponding computer-implemented method and a corresponding computer program product.

Description

Technical Field

[0001] This invention relates to a technical management system for multiple technical components of an orchestration system. Furthermore, this invention relates to the corresponding runtime environment, corresponding interfaces, corresponding computer-implemented methods, and corresponding computer program products. Background Technology

[0002] There is a current trend towards digitalization in the industrial sector. Therefore, processes such as product manufacturing can be digitally controlled. To describe several aspects of this trend, the term "Industry 4.0" (German: "Industrie 4.0") is commonly used. It has not only become a major part of modern industry but also drives business operations in many industrial sectors.

[0003] Considering the complexity of industrial plants, which typically comprise various technological components or units with multiple individual functions, these technological components can also be considered assets. Exemplary technological components in such industrial plants include sensors, actuators, robots, conveyors, machine tools, and the products being manufactured (e.g., bottles, cars, and screws). These technological components and their functions must be controlled and regulated interactively. They are typically monitored, controlled, and regulated by automated systems. Increasing digitalization allows for the automated manufacture or industrial assembly of products within production lines in industrial plants, performed by robotic units or other autonomous units, and has thus been at least partially efficient to date.

[0004] A technical component may include at least one part. For example, a technical component may include a reactive part. A technical component with a reactive part can be described by a description, such as a service metamodel (e.g., asset management shell, Internet of Things). This description may include static information, such as from digital nameplates, technical data, and / or documentation. A technical component with an active part includes specific functionality and may even establish a connection from a digital twin to a physical asset.

[0005] An exemplary technical component with active components is a robot. An exemplary robot proactively notifies other technical components when it requires maintenance (e.g., due to wear and tear on its grippers). Another exemplary technical component with active components is an AGV (Automated Guided Vehicle). An AGV can decide to interrupt its current transport task and travel to a specific location for repairs.

[0006] Because safety-critical technology systems (such as the industrial plants mentioned above) can make autonomous decisions, technological components with active parts are becoming increasingly important. For example, these components need to respond quickly to constantly changing demands within an industrial plant.

[0007] However, providing a method for managing technical components with active parts in a platform-independent and secure manner remains a challenge.

[0008] Therefore, the object of the present invention is to provide a technical management system for arranging multiple technical components of a technical system, which is more efficient and reliable. Summary of the Invention

[0009] According to one aspect of the invention, the problem is solved by a technology management system for orchestrating multiple technology components of a technology system, wherein each of the multiple technology components is a hardware component or a software component, wherein each of the multiple technology components includes at least one active component, and wherein the multiple technology components interact with each other in the technology system, including: a. A runtime environment for the active components of multiple technology components; among which The active components of multiple technical components execute in the runtime environment; and b. An interface for the active component of multiple technical components; wherein The interface is configured to enable the execution of active components of multiple technical components within the runtime environment. Furthermore, the interface can be configured to define lifecycle hooks and / or input / output connectivity.

[0010] Therefore, this invention relates to a technology management system for orchestrating multiple technology components of a technology system. The term "orchestration" can also be understood as management. The technology system can be designed as any technology system, such as a safety-critical system. Exemplary technology systems are industrial plants and autonomous vehicles. The technology system includes technology components in the form of hardware and / or software components. Thus, each technology component includes one or more active parts. Active parts may include programs or applications for the functionality of the technology components.

[0011] The technology management system consists of two components or units: the runtime environment and the interface.

[0012] Therefore, the term "runtime environment" can be interpreted in its usual sense, whereby it refers to the environment in which a program or application is executed. In other words, the runtime environment specifies the hardware and software infrastructure that supports the operation of a particular codebase, which can be in real time. Active components execute within the runtime environment.

[0013] Interfaces are required by active components of a technology in the runtime environment. Interfaces can also be used to describe logic, define lifecycle hooks, and / or access inputs and / or outputs. In other words, input / output functionality can be encapsulated and provided by the runtime environment through interfaces.

[0014] This invention ensures the orchestration of technical components with active parts in a platform-independent and reliable manner.

[0015] A technology management system for orchestrating technical components allows for improved efficiency.

[0016] In this way, technological components with active parts in a technological system (such as an industrial plant) can operate efficiently and safely. Therefore, unlike existing technologies, technological components with active parts can respond quickly to changing demands within an industrial plant. These components can communicate and interact with each other, and make improved autonomous decisions.

[0017] In one aspect, each of the multiple technical components can be described by a service meta-model, having at least one specified function or at least one specified functionality and / or being configured to communicate and / or connect with at least one other technical component, at least one technical system and / or at least one computing unit.

[0018] In another aspect, at least one function can be specified using JavaScript object notation JSON functions, WebAssembly binaries, and / or standardized interfaces. Therefore, the complexity and scope of the function vary between simple and complex functions. Simple functions can be implemented using JSON function descriptions. More complex functions, exceeding the capabilities of JSON function descriptions, can be implemented using WebAssembly binaries.

[0019] In another aspect, the runtime environment is defined as WebAssembly. WebAssembly allows for platform-independent implementations.

[0020] In another aspect, the lifecycle of active components of a technical component can be controlled using lifecycle hooks. Therefore, technical management systems and / or interfaces can be used to control the lifecycle of active components via lifecycle hooks. Lifecycle hooks allow technical components with active components to be executed at one or more predefined points in their lifecycle. For example, if a connection to a computing unit or technical system needs to be established using a fieldbus protocol, this can be done in a "post-start hook." The connection can then be detached in a "pre-stop hook." Lifecycle hooks allow for modular separation of components within a technical component. Another advantage is that users can add custom logic that can be executed for predefined applications.

[0021] In another aspect, the interface is configured to, preferably during runtime, exchange data between active components of multiple technical components and at least one other technical component, at least one technical system, and / or at least one computing unit. Therefore, the interface is configured not only for execution but also for data transmission and / or sharing. Data can be exchanged between an active component of a technical component and an active component of another technical component or any other computing unit. Thus, data is exchanged between the active components of the technical components. Additionally or alternatively, data can be exchanged between an active component of a technical component and any other component of another technical component, such as a reactive component or other computing unit. In other words, the active component of a technical component can communicate and share data with any other computing unit within or outside the technical system.

[0022] For example, industrial applications that need to exchange data with active components of technical components can do so directly, or alternatively, through an industrial message bus for decoupling. The interaction between the active component and the message bus can be handled by the runtime environment. Information about which data is provided by the active application and which topic of the message bus should be used can be described in the reactive component of the service metamodel.

[0023] In another aspect, data is exchanged between the active components of multiple technical components and at least one other technical component, at least one technical system and / or at least one computing unit via a bus, preferably an industrial message bus.

[0024] In another respect, the technical system is a safety-critical system, preferably in an industrial plant.

[0025] On another front, each of the multiple technical components has its own computing resources and is configured to execute itself within a runtime environment. Therefore, technical components have their own computing resources and can be referred to as constrained devices. The technical components themselves execute the runtime environment. The advantage is that they act as servers for the reactive components of the service metamodel, but also execute the active components. This enables direct interaction with connected hardware and input / output logic.

[0026] In another aspect, multiple technical components are provided as a compute cluster, and this compute cluster executes a runtime environment, preferably a Kubernetes cluster. Therefore, in cases where technical components do not have integrated compute resources, reactive and / or proactive components can be served by a suitable compute cluster, such as a Kubernetes cluster. These components can be provided as workloads. Workloads can also be executed in a runtime environment. Workloads have proven advantageous given the benefits of dynamic orchestration and the sandboxed nature of the runtime environment provided by Kubernetes.

[0027] Another aspect of the invention is a runtime environment for at least one active component of at least one technical component of a technical system; wherein At least one active component of at least one technical component executes in the runtime environment.

[0028] Another aspect of the invention is an interface for at least one active component of at least one technical component of a technical system; wherein The interface is configured to enable the execution of at least one active component of at least one technical component in a runtime environment.

[0029] Another aspect of the invention is a computer-implemented method for orchestrating multiple technical components of a technical system, wherein... Each of the multiple technical components is either a hardware component or a software component, among which Each of the multiple technical components includes at least one active component, wherein Multiple technical components interact with each other in the technical system, including: a. Provide a runtime environment; b. Active components that execute multiple technical components within the runtime environment; c. Provide interfaces for the active components of multiple technical components; and d. Execution of active components of multiple technical components in the runtime environment by means of interfaces.

[0030] Another aspect of the present invention is a computer program product that can be directly loaded into the internal memory of a computer, including a software code portion for performing the steps of the aforementioned computer-implemented method when the computer program product is run on the computer. Attached Figure Description

[0031] In the following detailed description, preferred embodiments of the invention are further described with reference to the following figures: Figure 1 A schematic diagram of a technology management system for orchestrating a technology system according to an embodiment is shown.

[0032] Figure 2 The illustration shows a flowchart of a computer-implemented method for arranging multiple technical components of a technical system according to the present invention. Detailed Implementation

[0033] Figure 1A schematic diagram of a technology management system 1 is shown for orchestrating multiple technology components 12 of a technology system 10. The technology system 10 includes one or more technology components 12 that interact with each other. The technology components 12 can also interact with any other computing unit 20. The technology components 12 are orchestrated by the technology management system 1. Therefore, the technology management system 1 includes a runtime environment 14 and an interface 16.

[0034] Figure 2 A flowchart illustrating a computer implementation method for orchestrating a plurality of technical components 12 of a technical system 10 according to the present invention is shown. In a first step, a runtime environment 14 is provided (S1). In a second step, active components of the plurality of technical components 12 are executed in the runtime environment 14 (S2). Then, an interface 16 is provided for the active components of the plurality of technical components 12 (S3). In a final step, the execution of the active components of the plurality of technical components 12 is established in the runtime environment 14 by means of the interface 16 (S4).

[0035] Runtime Environment 14 The reactions and active components of a technical component can be described using a service metamodel. The runtime environment 14 is provided for the active components of multiple technical components 12. Active components execute within the runtime environment 14. The runtime environment can be described as a so-called sandbox. The runtime environment 14 ensures the secure execution of the corresponding functionality of the technical components. For example, a technical component with active components may only access its authorized hardware resources. Furthermore, incoming and outgoing network connections can be controlled to ensure secure communication between technical components and other technical components or systems (e.g., asset discovery services or manufacturing execution systems).

[0036] Interface 16 Interface 16 for the active components of the multiple technical components 12 is essential for enabling the active components of the multiple technical components 12 to be executed in the runtime environment 14. Furthermore, interface 16 can describe the active components of the technical components 12.

Claims

1. A technology management system (1) for orchestrating multiple technology components (12) of a technology system (10), wherein Each of the plurality of technical components (12) is a hardware component or a software component, wherein Each of the plurality of technical components (12) includes at least one active component, wherein The plurality of technical components (12) interact with each other in the technical system, including: a. A runtime environment (14) for the active components of the plurality of technical components (12); in The active components of the plurality of technical components (12) execute in the runtime environment (14); and b. An interface (16) for the active component of the plurality of technical components (12); wherein The interface (16) is configured to establish the execution of the active components of the plurality of technical components (12) in the runtime environment (14).

2. The technology management system (1) according to claim 1, wherein each of the plurality of technology components (12) may be described by a service meta-model, having at least one specified function or at least one specified function and / or being configured to communicate and / or connect with at least one other technology component (12), at least one technology system (10) and / or at least one computing unit (20).

3. The technical management system (1) according to claim 2, wherein the at least one function can be specified using JavaScript object notation JSON functions, WebAssembly binary and / or standardized interfaces.

4. The technical management system (1) according to any one of the preceding claims, wherein the runtime environment (14) is defined as WebAssembly.

5. The technology management system (1) according to any of the preceding claims, wherein the lifecycle of the active component of the technology component (12) can be controlled by means of a lifecycle hook.

6. The technology management system (1) according to any one of the preceding claims, wherein the interface (16) is configured to, preferably during operation, exchange data between the active components of the plurality of technology components (12) and at least one other technology component (12), at least one technology system (10) and / or at least one computing unit.

7. The technology management system (1) according to claim 6, wherein the active components of the plurality of technology components (12) exchange data with the at least one other technology component (12), the at least one technology system (10) and / or the at least one computing unit via a bus, preferably an industrial message bus.

8. The technology management system (1) according to any one of the preceding claims, wherein the technology system (10) is a safety-critical system, preferably an industrial plant.

9. The technology management system (1) according to any one of the preceding claims, wherein each of the plurality of technology components (12) has its own computing resources and is configured to execute itself in a runtime environment (14).

10. A technology management system (1) according to any one of the preceding claims, wherein the plurality of technology components (12) are provided as a computing cluster, and the computing cluster executes a runtime environment (14), wherein the computing cluster is preferably a Kubernetes cluster.

11. A runtime environment (14) for at least one active component of at least one technical component (12) of a technical system (10); wherein The at least one active component of the at least one technical component (12) is executed in the runtime environment (14).

12. An interface (16) for at least one active component of at least one technical component (12) of the technical system (10); wherein The interface (16) is configured to establish the execution of the at least one active component of the at least one technical component (12) in the runtime environment (14).

13. A computer-implemented method for arranging multiple technical components (12) of a technical system (10), wherein Each of the plurality of technical components (12) is a hardware component or a software component, wherein Each of the plurality of technical components (12) includes at least one active component, wherein The plurality of technical components (12) interact with each other in the technical system (10), including: a. Provide runtime environment (14) (S1); b. Execute the active component (S2) of the plurality of technical components (12) in the runtime environment (14); c. Provide an interface (16) (S3) for the active components of the plurality of technical components (12); and d. Execution of the active component of the plurality of technical components (12) in the runtime environment (16) by means of the interface (14) (S4).

14. A computer program product that can be directly loaded into a computer's internal memory, comprising a software code portion for performing the steps of claim 13 when the computer program product is running on the computer.

Images