COMPUTER-IMPLEMENTED METHOD AND ORCHESTRATION SYSTEM TO ORCHESTRATE CONFIGURATIONS OF SIMULATIONS BASED ON DIGITAL TWIN MODELS OF MODULAR PLANTS

Abstract

A method to orchestrate configurations of simulations based on digital twin models of modular plants such that the configurations of the model-based simulations are generated and deployed automatically, is proposed and based on a logical System Structure and Parameterization functionality including a Functional Mock-up Interface-functionality combined with a Functional Mock-up Unit-functionality to generate for distributed operational-technology-applications of the modular plants simulated model components including assignment rules for automation data captured due to automation of the plants and assigned to the distributed operational-technology-applications, and deploying the simulated model components on the distributed operational-technology-applications by using the SSP-functionality with Functional Mock-up Unit-functionalities as part of the FMI-functionality for the distributed operational-technology-applications and implementing for the distributed operational-technology-applications and as part of the FMI-functionality in a server-client-manner Remote Procedure Call-technology based Proxy-FMU-functionalities with Proxy-FMU-entities embedded in the SSP-functionality and corresponding Remote-Controlled-FMU-entities implemented on the distributed operational-technology-applications is provided.

Claims

1. Computer-implemented method to orchestrate configurations of simulations based on digital twin models (DTM.sub.1, DTM.sub.2, DTM.sub.3) of modular plants (P.sub.m, PM.sub.1, PM.sub.2, PM.sub.3), by which is used for the configurations of the model-based simulations a) a logical System Structure and Parameterization <SSP>-functionality (SSP-T) a1) describing in a logical way how a11) model components for the simulations are connected and composed for their deployment into composite components and a12) model parameterization data are stored and exchanged between each the model component and the composite component and a2) including a Functional Mock-up Interface <FMI>-functionality (FMI-T) for sharing the simulations via a ZIP-archive-based Functional Mock-up Unit <FMU>-functionality (FMU-T) packing XML-files and compiled C-code, characterized by: b) generating (grt) for distributed operational-technology-applications (OTA.sub.d, ED.sub.1, ED.sub.2, ED.sub.3) of the modular plants (P.sub.m, PM.sub.1, PM.sub.2, PM.sub.3), wherein the operational-technology-applications are edge devices (ED.sub.1, ED.sub.2, ED.sub.3) of field devices (FD.sub.1, FD.sub.2, FD.sub.3), simulated model components (MC.sub.s,1, MC.sub.s,2, MC.sub.s,3) including assignment rules (AR.sub.1, AR.sub.2, AR.sub.3) for automation data (AD.sub.1, AD.sub.2, AD.sub.3) captured due to automation of the plants (P.sub.m, PM.sub.1, PM.sub.2, PM.sub.3) and assigned to the distributed operational-technology-applications (OTA.sub.d, ED.sub.1, ED.sub.2, ED.sub.3), c) deploying (dpl) in the course of orchestrating the simulations configurations the simulated model components (MC.sub.s,1, MC.sub.s,2, MC.sub.s,3) on the distributed operational-technology-applications (OTA.sub.d, ED.sub.1, ED.sub.2, ED.sub.3) by using the SSP-functionality (SSP-T) with Functional Mock-up Unit <FMU>-functionalities (FMU-T.sub.1, FMU-T.sub.2, FMU-T.sub.3) as part of the FMI-functionality (FMI-T) for the distributed operational-technology-applications (OTA.sub.d, ED.sub.1, ED.sub.2, ED.sub.3) and implementing for the distributed operational-technology-applications (OTA.sub.d, ED.sub.1, ED.sub.2, ED.sub.3) and as part of the FMI-functionality (FMI-T) in a server-client-manner Remote Procedure Call <RPC>-technology based Proxy-FMU-functionalities (PFMU-T.sub.1, PFMU-T.sub.2, PFMU-T.sub.3) with Proxy-FMU-entities (PFMU-E.sub.1, PFMU-E.sub.2, PFMU-E.sub.3) embedded in the SSP-functionality (SSP-T) and corresponding Remote-Controlled-FMU-entities (RCFMU-E.sub.1, RCFMU-E.sub.2, RCFMU-E.sub.3) implemented on the distributed operational-technology-applications (OTA.sub.d, ED.sub.1, ED.sub.2, ED.sub.3), d) deploying (dpl) the automation data (AD.sub.1, AD.sub.2, AD.sub.3) on the distributed operational-technology-applications (OTA.sub.d, ED.sub.1, ED.sub.2, ED.sub.3) according to the assignment rules (AR.sub.1, AR.sub.2, AR.sub.3) for the automation data (AD.sub.1, AD.sub.2, AD.sub.3) and as a result of the deployment (dpl) of the simulated model components (MC.sub.s,1, MC.sub.s,2, MC.sub.s,3).

2. Computer-implemented tool (CIT) for carrying out the computer-implemented method according to the claim 1, in particular designed as a Computer-Program-Product, e.g., an APP, with a non-transitory, processor-readable storage medium (STM) having processor-readable program-instructions of a program module (PGM) for carrying out the computer-implemented method stored in the non-transitory, processor-readable storage medium (STM) and a processor (PRC) connected with the storage medium (STM) executing the processor-readable program-instructions of the program module (PGM) to carry out the computer-implemented method according to the claim 1.

3. Orchestration system (OS) to orchestrate configurations of simulations based on digital twin models (DTM.sub.1, DTM.sub.2, DTM.sub.3) of modular plants (P.sub.m, PM.sub.1, PM.sub.2, PM.sub.3), with a server-controller (SCRT) to configure the model-based simulations including a) a logical System Structure and Parameterization <SSP>-tool (SSP-T) a1) describing in a logical way how a11) model components for the simulations are connected and composed for their deployment into composite components and a12) model parameterization data are stored and exchanged between each the model component and the composite component and a2) including a Functional Mock-up Interface <FMI>-tool (FMI-T) for sharing the simulations via a ZIP-archive-based Functional Mock-up Unit <FMU>-tool (FMU-T) packing XML-files and compiled C-code, characterized by: b) a generation unit (GU) of the server-controller (SCRT) generating (grt) for distributed operational-technology-applications (OTA.sub.d, ED.sub.1, ED.sub.2, ED.sub.3) of the modular plants (P.sub.m, PM.sub.1, PM.sub.2, PM.sub.3), wherein the operational-technology-applications are edge devices (ED.sub.1, ED.sub.2, ED.sub.3) of field devices (FD.sub.1, FD.sub.2, FD.sub.3), simulated model components (MC.sub.s,1, MC.sub.s,2, MC.sub.s,3) including assignment rules (AR.sub.1, AR.sub.2, AR.sub.3) for automation data (AD.sub.1, AD.sub.2, AD.sub.3) captured due to automation of the plants (P.sub.m, PM.sub.1, PM.sub.2, PM.sub.3) and assigned to the distributed operational-technology-applications (OTA.sub.d, ED.sub.1, ED.sub.2, ED.sub.3), c) a deployment tool (DT) of the server-controller (SCRT) c1) deploying (dpl) in the course of orchestrating the simulations configurations the simulated model components (MC.sub.s,1, MC.sub.s,2, MC.sub.s,3) on the distributed operational-technology-applications (OTA.sub.d, ED.sub.1, ED.sub.2, ED.sub.3) by using the SSP-functionality (SSP-T) with Functional Mock-up Unit <FMU>-functionalities (FMU-T.sub.1, FMU-T.sub.2, FMU-T.sub.3) as part of the FMI-functionality (FMI-T) for the distributed operational-technology-applications (OTA.sub.d, ED.sub.1, ED.sub.2, ED.sub.3) and implementing for the distributed operational-technology-applications (OTA.sub.d, ED.sub.1, ED.sub.2, ED.sub.3) and as part of the FMI-functionality (FMI-T) in a server-client-manner Remote Procedure Call <RPC>-technology based Proxy-FMU-functionalities (PFMU-T.sub.1, PFMU-T.sub.2, PFMU-T.sub.3) with Proxy-FMU-entities (PFMU-E.sub.1, PFMU-E.sub.2, PFMU-E.sub.3) embedded in the SSP-functionality (SSP-T) of the server-controller (SCRT) and corresponding Remote-Controlled-FMU-entities (RCFMU-E.sub.1, RCFMU-E.sub.2, RCFMU-E.sub.3) implemented on the distributed operational-technology-applications (OTA.sub.d, ED.sub.1, ED.sub.2, ED.sub.3) including client-controllers (CCRT.sub.1, CCRT.sub.2, CCRT.sub.3), c2) deploying (dpl) the automation data (AD.sub.1, AD.sub.2, AD.sub.3) on the distributed operational-technology-applications (OTA.sub.d, ED.sub.1, ED.sub.2, ED.sub.3) according to the assignment rules (AR.sub.1, AR.sub.2, AR.sub.3) for the automation data (AD.sub.1, AD.sub.2, AD.sub.3) and as a result of the deployment (dpl) of the simulated model components (MC.sub.s,1, MC.sub.s,2, MC.sub.s,3).

4. Orchestration system (OS) according to the claim 3, characterized by a computer-implemented-tool (CIT), in particular a Computer-Program-Product, e.g., designed as an APP, up-loadable into the server-controller (SCRT) with a non-transitory, processor-readable storage medium (STM) having processor-readable program-instructions of a program module (PGM) for orchestrating the simulations configurations stored in the non-transitory, processor-readable storage medium (STM) and a processor (PRC) connected with the storage medium (STM) executing the processor-readable program-instructions of the program module (PGM) to orchestrate the simulations configurations.

Description

[0057] Moreover, additional advantageous developments of the invention arise out of the following description of a preferred embodiment of the invention according to FIGS. 1 to 4. They show:

[0058] FIG. 1 a scenario for orchestrating configurations of model-based simulations of a modular plant,

[0059] FIG. 2 a principle presentation of a computer-implemented-tool, in particular a Computer-Program-Product, e.g., designed as an APP,

[0060] FIG. 3 an exemplary message-flow-diagram for deploying the simulated model components by implementing in a server-client-manner Remote Procedure Call <RPC>-technology based Proxy-FMU-functionalities,

[0061] FIG. 4 an exemplary orchestration flow between involved units of the SERVER-CLIENT-based scenario depicted in the FIG. 1.

[0062] FIG. 1 shows a server-client-based scenario for orchestrating configurations of model-based simulations of a plant with a modular structure P.sub.m. The plant with the modular structure P.sub.m includes for example as depicted three plant modules, a first plant module PM.sub.1, a second plant module PM.sub.2 and a third plant module PM.sub.2, which can be regarded as modular plants. Each modular plant PM.sub.1, PM.sub.2, PM.sub.3 has always the same plant structure.

[0063] So, it belongs to the first modular plant PM.sub.1, a first control system of plant module CS.sub.1, which is connected or assigned on one side to a first digital twin model DTM.sub.1 and on the other to automated machines or processes, depicted in the FIG. 1 by robots. To the first control system of plant module CS.sub.1 belongsin general and well-knowna first Programmable Logic Controller <PLC>-unit PLCU.sub.1, which is connected with a first field device FD.sub.1 including a first edge device ED.sub.1. The first edge device ED.sub.1 is in the context of the preferred embodiment of the invention a distributed operational-technology-application OTA.sub.d, for which according to the objective of the invention and in the course of orchestrating the configurations of the model-based simulations are generated and deployed automatically.

[0064] The same structure have the second modular plant PM.sub.2 and the third modular plant PM.sub.3.

[0065] So, it belongs to the second modular plant PM.sub.2, a second control system of plant module CS.sub.2, which is connected or assigned on one side to a second digital twin model DTM.sub.2 and on the other again to automated machines or processes, depicted in the FIG. 1 by the robots. To the second control system of plant module CS.sub.2 belongs again a second Programmable Logic Controller <PLC>-unit PLCU.sub.2, which is connected with a second field device FD.sub.2 including a second edge device ED.sub.2. Also, the second edge device ED.sub.2 is in the context of the preferred embodiment of the invention a distributed operational-technology-application OTA.sub.d, for which according to the objective of the invention and in the course of orchestrating the configurations of the model-based simulations are generated and deployed automatically.

[0066] To the third modular plant PM.sub.3 consequently belongs a third control system of plant module CS.sub.3, which is connected or assigned on one side to a third digital twin model DTM.sub.3 and on the other again to automated machines or processes, depicted in the FIG. 1 by the robots. To the third control system of plant module CS.sub.3 belongs a third Programmable Logic Controller <PLC>-unit PLCU.sub.3, which is connected with a third field device FD.sub.3 including a third edge device ED.sub.3. Also, the third edge device ED.sub.3 is in the context of the preferred embodiment of the invention again a distributed operational-technology-application OTA.sub.d, for which according to the objective of the invention and in the course of orchestrating the configurations of the model-based simulations are generated and deployed automatically.

[0067] According to the FIG. 1 the orchestration is carried out by an orchestration system OS, which is for instance in a preferred and simplest design a simulator expanded to include SSP-, FMI/FMU-functionality, to orchestrate configurations of simulations based on the digital twin models DTM.sub.1, DTM.sub.2, DTM.sub.3 of the modular plants PM.sub.1, PM.sub.2, PM.sub.3, which includes a server-controller SCRT to configure the model-based simulations.

[0068] According to the depicted SERVER-CLIENT-based scenario server-controller SCRT of the orchestration system OS is the SERVER and the edge devices ED.sub.1, ED.sub.2, ED.sub.3 of the modular plants PM.sub.1, PM.sub.2, PM.sub.3 are the CLIENTS.

[0069] In the course of the orchestration the server-controller SCRT includes as part of a deployment tool DT a logical System Structure and Parameterization <SSP>-tool SSP-T, which is well-known (cf. https://ssp-standard.org) and describes in a logical way how model components for the simulations are connected and composed for their deployment into composite components and how model parameterization data are stored and exchanged between each the model component and the composite component. The logical System Structure and Parameterization <SSP>-tool SSP-T consist or includes a Functional Mock-up Interface <FMI>-tool FMI-T (cf. https://fmi-standard.org) for sharing the simulations via a ZIP-archive-based Functional Mock-up Unit <FMU>-tool FMU-T packing XML-files and compiled C-code.

[0070] Moreover in the course of the orchestration the server-controller SCRT includes a generation unit GU, which generates grt based on the digital twin models DTM.sub.1, DTM.sub.2, DTM.sub.3 of the modular plants PM.sub.1, PM.sub.2, PM.sub.3 and for the distributed operational-technology-applications OTA.sub.d respectively the edge devices ED.sub.1, ED.sub.2, ED.sub.3 of the modular plants PM.sub.1, PM.sub.2, PM.sub.3 simulated model components, (i) at least one first simulated model component MC.sub.s,1 for the first edge device ED.sub.1, (ii) at least one second simulated model component MC.sub.s,2 for the second edge device ED.sub.2 and (iii) at least one third simulated model component MC.sub.s,3 for the third edge device ED.sub.3, captured each due to automation of the modular plants PM.sub.1, PM.sub.2, PM.sub.3.

[0071] For this purpose, the first simulated model component MC.sub.s,1 includes first assignment rules AR.sub.1 for first automation data AD.sub.1 assigned to the first edge device ED.sub.1, second assignment rules AR.sub.2 for second automation data AD.sub.2 assigned to the second edge device ED.sub.2 and third assignment rules AR.sub.3 for third automation data AD.sub.3 assigned to the third edge device ED.sub.3.

[0072] These generated information MC.sub.s,1, MC.sub.s,2, MC.sub.s,3, AR.sub.1, AR.sub.2, AR.sub.3, AD.sub.1, AD.sub.2, AD.sub.3 are transferred within the server-controller SCRT to the deployment tool DT for deploying the information on the distributed operational-technology-applications OTA.sub.d respectively the edge devices ED.sub.1, ED.sub.2, ED.sub.3 of the modular plants PM.sub.1, PM.sub.2, PM.sub.3.

[0073] For this purpose, the deployment tool DT of the server-controller SCRT deploys dpl the simulated model components MC.sub.s,1, MC.sub.s,2, MC.sub.s,3 on the distributed operational-technology-applications OTA.sub.d respectively the edge devices ED.sub.1, ED.sub.2, ED.sub.3 by [0074] using the SSP-functionality SSP-T with Functional Mock-up Unit <FMU>-functionalities as part of the FMI-functionality FMI-T, (i) a first Functional Mock-up Unit <FMU>-functionality FMU-T.sub.1 for the first edge device ED.sub.1, (ii) a second Functional Mock-up Unit <FMU>-functionality FMU-T.sub.2 for the second edge device ED.sub.2 and (iii) a third Functional Mock-up Unit <FMU>-functionality FMU-T.sub.3 for the first edge device ED.sub.3, and [0075] implementing for the distributed operational-technology-applications OTA.sub.d respectively the edge devices ED.sub.1, ED.sub.2, ED.sub.3 and as part of the FMI-functionality FMI-T in a server-client-manner and based on a well-known Remote Procedure Call <RPC>-technology (cf. https://en.wikipedia.org/wiki/Remote_procedure_call in the version of Jul. 23, 2021) Proxy-FMU-functionalities, (i) a first Proxy-FMU-functionality PFMU-T.sub.1 with a first Proxy-FMU-entity PFMU-E.sub.1 embedded in the SSP-functionality SSP-T of the server-controller SCRT and a corresponding first Remote-Controlled-FMU-entity RCFMU-E.sub.1 implemented in a first client-controller CCRT.sub.1 on the first edge device ED.sub.1, which includes the first automation data AD.sub.1 assigned to the first edge device ED.sub.1 and to be deployed on (ii) a second Proxy-FMU-functionality PFMU-T.sub.2 with a second Proxy-FMU-entity PFMU-E.sub.2 embedded in the SSP-functionality SSP-T of the server-controller SCRT and a corresponding second Remote-Controlled-FMU-entity RCFMU-E.sub.2 implemented in a second client-controller CCRT.sub.2 on the second edge device ED.sub.2, which includes the second automation data AD.sub.2 assigned to the second edge device ED.sub.2 and to be deployed on, and (iii) a third Proxy-FMU-functionality PFMU-T.sub.3with a third Proxy-FMU-entity PFMU-E.sub.3 embedded in the SSP-functionality SSP-T of the server-controller SCRT and a corresponding third Remote-Controlled-FMU-entity RCFMU-E.sub.3 implemented in a third client-controller CCRT.sub.3 on the third edge device ED.sub.3, which includes the third automation data AD.sub.3 being assigned to the third edge device ED.sub.3 and to be deployed on.

[0076] Moreover, the deployment tool DT is designed such that the automation data AD.sub.1, AD.sub.2, AD.sub.3 are deployed dpl on the distributed operational-technology-applications OTA.sub.d respectively the edge devices ED.sub.1, ED.sub.2, ED.sub.3 according to the assignment rules AR.sub.1, AR.sub.2, AR.sub.3 for the automation data AD.sub.1, AD.sub.2, AD.sub.3 and as a result of the deployment dpl of the simulated model components MC.sub.s,1, MC.sub.s,2, MC.sub.s,3.

[0077] Furthermore, the orchestration system OS can be designed as a hardware solution or realized as a software solution such that the orchestration system OS is a computer-implemented-tool CIT, which is nothing else than a Computer-Program-Product being designed preferably as an APP and which is up-loadable into the server-controller SCRT.

[0078] FIG. 2 shows in a principal diagram of the computer-implemented-tool CIT how the tool could be designed. According to the depiction the computer-implemented-tool CIT includes a non-transitory, processor-readable storage medium STM having processor-readable program-instructions of a program module PGM for identifying manipulations of cyber-physical-systems stored in the non-transitory, processor-readable storage medium STM and a processor PRC connected with the storage medium STM executing the processor-readable program-instructions of the program module PGM to identify manipulations of cyber-physical-systems.

[0079] FIG. 3 shows starting from the FIG. 1 and based on the corresponding FIG. 1-description an exemplary message-flow-diagram for deploying the simulated model components by implementing in a server-client-manner Remote Procedure Call <RPC>-technology based Proxy-FMU-functionalities,

[0080] FIG. 4 shows starting from the FIG. 1 and based on the corresponding FIG. 1 -description an exemplary orchestration flow between involved units of the SERVER-CLIENT-based scenario depicted in the FIG. 1. Between the server-controller SCRT including an orchestration entity responsible for the orchestration and manage-clients-entity responsible for managing clients the orchestration flow is TCP/IP-based (cf. https://en.wikipedia.org/wiki/Internet_Paxocol in the version of Jul. 25, 2021).