Computer-implemented method and orchestration system to orchestrate configurations of simulations based on digital twin models of modular plants

Orchestration system (OS) to orchestrate configurations of simulations based on digital twin models (DTM1, DTM2, DTM3) of modular plants (Pm, PM1, PM2, PM3), 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 (OTAd, ED1, ED2, ED3) of the modular plants (Pm, PM1, PM2, PM3), wherein the operational-technology-applications are edge devices (ED1, ED2, ED3) of field devices (FD1, FD2, FD3), simulated model components (MCs,1, MCs,2, MCs,3) including assignment rules (AR1, AR2, AR3) for automation data (AD1, AD2, AD3) captured due to automation of the plants (Pm, PM1, PM2, PM3) and assigned to the distributed operational-technology-applications (OTAd, ED1, ED2, ED3),
• 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 (MCs,1, MCs,2, MCs,3) on the distributed operational-technology-applications (OTAd, ED1, ED2, ED3) by using the SSP-functionality (SSP-T) with “Functional Mock-up Unit <FMU>”-functionalities (FMU-T1, FMU-T2, FMU-T3) as part of the FMI-functionality (FMI-T) for the distributed operational-technology-applications (OTAd, ED1, ED2, ED3) and implementing for the distributed operational-technology-applications (OTAd, ED1, ED2, ED3) and as part of the FMI-functionality (FMI-T) in a server-client-manner “Remote Procedure Call <RPC>”-technology based Proxy-FMU-functionalities (PFMU-T1, PFMU-T2, PFMU-T3) with
• “Proxy-FMU”-entities (PFMU-E1, PFMU-E2, PFMU-E3) embedded in the SSP-functionality (SSP-T) of the server-controller (SCRT) and
• corresponding “Remote-Controlled-FMU”-entities (RCFMU-E1, RCFMU-E2, RCFMU-E3) implemented on the distributed operational-technology-applications (OTAd, ED1, ED2, ED3) including client-controllers (CCRT1, CCRT2, CCRT3),
• c2) deploying (dpl) the automation data (AD1, AD2, AD3) on the distributed operational-technology-applications (OTAd, ED1, ED2, ED3) according to the assignment rules (AR1, AR2, AR3) for the automation data (AD1, AD2, AD3) and as a result of the deployment (dpl) of the simulated model components (MCs,1, MCs,2, MCs,3).