Method for generating and handling applications for components of a distributed control system and engineering system for implementing the process
AssigneeSchneider Electric Automation GmbH
InventorsRalf Neubert, Karl-Heinz Wenzel
Life of this patent
Estimating the term…
Abstract
A method and an engineering system for generating and handling component applications (CA1 . . . CAn) for physical components (C1 . . . Cn) such as a programmable control (Programmable Logic Control (PLC)), Human Machine Interface (HMI) and/or a Supervisory Control and Data Acquisition Unit (SCADA) of a control system (CA), in which instances (ICF1 . . . ICFn) of component functions (CF1 . . . CFn) for the components (C1 . . . Cn) are produced and from which the component applications (CA1 . . . CAn) are generated, the generated component applications (CA1 . . . CAn) being loaded to the physical components (C1 . . . Cn).
Claims25
A method for generating and handling component applications (CA1 . . . CAn) for physical components (C1 . . . Cn) such as a programmable control (Programmable Logic Control (PLC), a Human Machine Interface (HMI) and/or a Supervisory Control and Data Acquisition (SCADA) unit of a control system (CA), wherein instances (ICF1 . . . ICFn) of component functions (CF1 . . . CFn) for the components (C1 . . . Cn) are generated, wherein the component applications (CA1 . . . Can) are generated from the instances, and wherein the generated component applications (CA1, . . . CAn) are loaded onto the physical components (C1 . . . Cn),
- characterized in that
- the instances (ICF1 . . . ICFn) are implemented as representatives (RC1 . . . RCn) of the component functions (F1 . . . Fn) distributed in a cloud-based environment, wherein each of the component applications (CA1, CA2, CA3 . . . CAn) is generated in one of the representatives (RC1, RC2, RC3 . . . RCn) in the cloud-based environment (CBE) on the basis of data that are exchanged through interaction between the representatives (RC1, RC2, RC3 . . . RCn) and between the representatives (RC1, RC2, RC3 . . . RCn) and the assigned physical components (C1, C2, C3 . . . Cn).
The method according to at least one of the preceding claims,
- characterized in that
- the interaction between the representatives (RC1, RC2, RC3 . . . RCn) and between the representatives and the assigned physical components (C1, C2, C3 . . . Cn) can be activated or deactivated via the service level agreements (SLA1, SLA2 . . . SLAn).
The method according to at least one of the preceding claims,
- characterized in that
- the generation of the component applications in a representative (RC1, RC2, RC3 . . . RCn) can be activated or deactivated via the service level agreements (SLA1, SLA2 . . . SLAn).
The method according to at least one of the preceding claims,
- characterized in that
- the generation of the component application (CA1, CA2, CA3 . . . CAn) in the representative (RC1, RC2, RC3 . . . RCn) is verified via the service level agreement (SLA1, SLA2 . . . SLAn).
The method according to at least one of the preceding claims,
- characterized in that
- the generation of the component application (CA1, CA2, CA3 . . . CAn) referred to the physical component (C1, C2, C3 . . . Cn) or the transfer of generated data to the physical component (C1, C2, C3 . . . Cn) is verified via the service level agreement (SLA1, SLA2 . . . SLAn).
The method according to at least one of the preceding claims,
- characterized in that
- the interaction between the representatives (RC1, RC2, RC3 . . . RCn) comprises the definition and the comparison of parameters, the drafting of control strategies and the visualization of control logic.
The method according to at least one of the preceding claims,
- characterized in that
- the use of the generated component applications (CA1, CA2, CA3 . . . CAn) is controlled by issuing user's rights with respect to the range of functions and access to data.
The method according to at least one of the preceding claims,
- characterized in that
- the representatives (RC1, RC2, RC3 . . . RCn) are hosted in the form of software building blocks on at least one hardware component (CU1, CU2, CU3) of the cloud-based environment.
The method according to at least one of the preceding claims,
- characterized in that
- the generated component applications (CA1, CA2, CA3 . . . CAn) are distributed by means of the physical component (C3) in the form of the supervisory control and data acquisition unit to the additional components (C1, C2) of the control system, taking into consideration the service level agreement (SLA1, SLA2 . . . SLAn).
The method according to at least one of the preceding claims,
- characterized in that
- the interaction between the representatives (RC1, RC2, RC3 . . . RCn) takes place by means of a uniform resource identifier (URI).
The method according to at least one of the preceding claims,
- characterized in that
- the generation of a component application (CA1, CA2, CA3) comprises the following process steps:
- querying/verifying a service level agreement (SLA1, SLA2 . . . SLAn) for generating a component application (CA1, CA2, CA3) between the representatives (RC1, RC2, RC3 . . . RCn),
- interaction between the representatives (RC1, RC2, RC3 . . . RCn) on the basis of web services (WS),
- generating a component application (CA1, CA2, CA3 . . . CAn) in the representative (RC1, RC2, RC3 . . . RCn), wherein the generation is verified via an internal service level agreement unit (SLAU) of the relevant representative (RC1, RC2, RC3 . . . RCn),
- distributing the component application (CA1, CA2, CA3 . . . CAn) to the assigned physical component (C1, C2, C3 . . . Cn), wherein a verification is optionally performed in advance via the service level agreement unit (SLAU).
The method according to at least one of the preceding claims,
- characterized in that
- the component functions (CF1 . . . CFn) are generated for specific subscribers, in the form of object types from component models (CM1 . . . CMn) and/or functional models (FM1 . . . FMn) stored in a library (BIB), using specific references and sets of parameters for the component functions to be used, the communication thereof, logic and variables.
The method according to at least one of the preceding claims,
- characterized in that
- the component functions (CF1 . . . CFn) that are specific to an application as a whole are identified, and in that, once the underlying ranges of functions (SLA1 . . . SLAn) have been verified, the instances (ICF1 . . . ICFn) are generated from the selected component functions (CF1 . . . CFn), and a transfer of the necessary parameters including the range of function parameter (PSLA1 . . . PSLAn) that is relevant to the generation of the component applications takes place.
The method according to at least one of the preceding claims,
- characterized in that
- the instances (ICF1 . . . ICFn) are distributed by means of a resource management component to components (CU1 . . . CUn) of the cloud-based environment (CBE), and are implemented on lower-level resources such as servers for executing the respective instances.
The method according to at least one of the preceding claims,
- characterized in that
- the component applications within an instance of a representative (RC1 . . . RCn) are generated by object representatives (GCOUM, GLU, GCONFU, DEPU), wherein a communications parameter generating unit for generating communications parameters, an application logic generating unit for generating application logic and/or a configuration information generating unit for generating configuration information is provided.
The method according to at least one of the preceding claims,
- characterized in that
- the communications parameters represent a variable, a baud rate or a storage location, in that the application logic represents a functional building block, and input variable, a storage location and/or an output variable and in that the configuration information represents a color for a background or a menu language.
The method according to at least one of the preceding claims,
- characterized in that
- the service level agreements for generation of the component application are defined and verified in a service level application unit (SLAU) of the instance of the representative.
The method according to at least one of the preceding claims,
- characterized in that
- the service level agreement unit (SLAU) controls the interaction of the object representatives within the representative and the interaction with other representatives and/or the distribution of the generated component application.
The method according to at least one of the preceding claims,
- characterized in that
- the communication takes place via an interface by means of a uniform resource identifier, which consists of a sequence of characters that is used for addressing/identifying an abstract or physical resource.
An engineering system (ES) for generating and handling component applications (CA1 . . . CAn) for physical components (C1 . . . Cn), comprising means for generating instances (ICF1 . . . ICFn) of component functions (CF1 . . . CFn) of the components (C1 . . . Cn), wherein the component applications are generated by the instances and wherein the engineering system has means for loading the generated component applications (CA1 . . . CAn) onto the physical components (C1 . . . Cn),
- characterized in that
- the engineering system (ES) has means for distributing the instances (ICF1 . . . ICFn) as representatives (RC1 . . . RCn) of the component functions (CF1 . . . CFn) in a cloud-based environment, wherein each of the instances (ICF1 . . . ICFn) has object representatives in the form of a communications parameter generating unit, an application logic generating unit and/or a configuration information generating unit for generating the component application.
A method according to a method according to at least one of the preceding claims,
- characterized in that
- the component applications (CA1, CA2, CA3) are generated in parallel in the cloud-based environment (CBE).
A method according to a method according to at least one of the preceding claims,
- characterized in that
- the data from the interaction between the instances, which data are authorized and released via the internal service level agreement unit (SLAU), are processed with the projected data (D), and in that the executable application parts that are required for the respective physical components (C1 . . . Cn), such as the program section according to standard IEC 61131-3 for SPS, are generated with corresponding functional building blocks and the specific parameters thereof, and are then distributed, and/or in that the projected data and the information obtained through interaction are used for compiling executable program parts that are adapted for the target component.
Dependencies are inferred from the claim text.