GENERATING AND DISTRIBUTING CONFIGURATION DATA STRUCTURES FOR CONTROL SYSTEMS

Abstract

A configuration data structure for control systems in an automation system and to a method, a cloud computing unit, a control system, and a computer program for generating the configuration data structure. The configuration data structure comprises a cloud component, which provides at least one cloud function that can be carried out on the cloud computing unit, and a system component, which provides at least one system function that can be carried out on the control systems.

Claims

1. A method comprising: generating a first configuration data structure for a first subscriber of an automation system, which is a first control system, carried out by a second subscriber which is a second control system or a cloud computing unit in a cloud system; providing the first configuration data structure with a cloud component, which provides at least one cloud function which is carried out on the cloud computing unit; and providing the first configuration data structure with a system component, which provides at least one system function which is carried out on the first control system.

2. The method according to claim 1, wherein the cloud component further comprises: display names, data formatting, units, threshold values, authorization information, predefined visualizations, statistical evaluations, a control system status, meta information, alarm configurations, configurations of aggregate formations, definitions of additional calculations, user authorizations, algorithms for data analysis, data export definitions, VPN configurations, backup/restore information, diagnostic information, and/or rules.

3. The method according to claim 1, wherein the system component further comprises: information about a data collection frequency, information about a data transmission frequency, information about a data transmission type, information about a type of data sent, configurations of a PLC program, visualization components, firmware versions, backup and diagnostic settings, settings as to whether data should be sent compressed or uncompressed, settings about possible preaggregations or filtering of data, settings about scaling and/or conversion of values, and/or information about connected sensors/actuators.

4. The method according to claim 1, further comprising: sending, by the cloud computing unit, the first configuration data structure to the first control system via the second control system, wherein the second control system acts as a gateway.

5. The method according to claim 1, further comprising: obtaining a system component by the cloud computing unit from the first control system or from the second control system, wherein the generation of the first configuration data structure for the first control system is based on the obtained system component.

6. The method according to claim 5, further comprising: before the first configuration data structure is sent, modifying, by the cloud computing unit, the cloud component or the system component of the first configuration data structure based on user inputs input by a user via a user unit and/or based on entries in a database.

7. The method according to claim 6, wherein the database is formed in the cloud system in the first or second control system or in another memory.

8. The method according to claim 1, further comprising: obtaining a second configuration data structure, generated by the first control system, by the cloud computing unit from the first control system.

9. The method according to claim 1, further comprising: obtaining process data from the first or second control system by the cloud computing unit; evaluating the process data; and outputting input data to the first or second control system, which trigger at least one system function in the first or second control system.

10. The method according to claim 1, further comprising: obtaining a unique identifier from the first control system by the second participant; checking whether a configuration data structure corresponding to the identifier is present in a memory of the second subscriber; and if a configuration data structure corresponding to the identifier is present in the memory, sending the corresponding configuration data structure to the first control system.

11. A method for configuring a first control system of an automation system, the method comprising: receiving a first configuration data structure by a first subscriber of an automation system, which is a first control system, from a second subscriber which is a second control system or a cloud computing unit in a cloud system, wherein the first configuration data structure comprises: a cloud component which provides at least one cloud function which is adapted to be carried out on the cloud computing unit; and a system component which provides at least one system function which is adapted to be carried out on the first control system; and taking over the system component of the first configuration data structure.

12. The method according to claim 11, further comprising: sending a unique identifier by the first control system to the second subscriber when the first control system is connected to the automation system.

13. The method according to claim 11, further comprising: storing the cloud component of the first configuration data structure in a memory of the first control system.

14. The method according to claim 11, further comprising: generating a second configuration data structure based on an existing unique configuration and the cloud component from the first configuration data structure by the first control system; and sending the generated second configuration data structure to the cloud computing unit.

15. The method according to claim 11, further comprising: generating a system component, based on an existing unique configuration, by the first or second control system; and sending the generated system component to the cloud computing unit, wherein the generating of the first configuration data structure (600) is based on the system component.

16. The method according to claim 11, further comprising: sending process data by the first or second control system to the cloud computing unit, wherein the process data are evaluated by the cloud computing unit; and obtaining input data from the cloud computing unit after evaluating the process data, wherein the input data trigger at least one system function in the first or second control system.

17. A cloud computing unit configured to carry out the method according to claim 1.

18. A control system configured to carry out the method according to claim 1.

19. A computer program which has instructions for carrying out the method according to claim 1.

20. A configuration data structure configured for use in the cloud computing unit according to claim 17 and/or in a control system.

Description

BRIEF DESCRIPTION OF THE DRAWINGS

[0033] The present invention will become more fully understood from the detailed description given hereinbelow and the accompanying drawings which are given by way of illustration only, and thus, are not limitive of the present invention, and wherein:

[0034] FIG. 1 shows a schematic arrangement with a user unit, a cloud system, and three control systems of an automation system according to an exemplary embodiment of the present invention;

[0035] FIG. 2 shows a schematic structure of a configuration data structure according to an exemplary embodiment of the present invention; and

[0036] FIG. 3 shows an exemplary configuration data structure for a control system in the field of building automation according to an exemplary embodiment of the present invention.

DETAILED DESCRIPTION

[0037] FIG. 1 shows a schematic arrangement with a user unit 400, a cloud system 1, and three control systems 200, 300, and 700 of an automation system according to an exemplary embodiment of the present invention. Control systems 200, 300, and 700 can also be referred to as control/data collection units because, in addition to control functions, they also have data collection functions. Cloud system 1 comprises a cloud computing unit 100. Furthermore, cloud system 1 can have a storage/data management unit, a display unit, a user management unit, and/or a device management unit, etc. (not shown).

[0038] Cloud system 1 is located, for example, in an internal cloud infrastructure and/or in an external cloud infrastructure.

[0039] Cloud system 1 is connected to a user unit 400 via a network. User unit 400 can be, for example, a PC or a mobile terminal with a web browser and/or a specific application that enables access to cloud system 1. The network can be both wired and/or wireless.

[0040] Further, the network connects control systems 200, 300, and 700 to cloud system 1. In this example, three control systems of the automation system are shown in order to explain the corresponding functionalities. It is understood, however, that the number of control systems in an automation system can be as desired; more precisely stated, the number can be between 1 and N, where N is an integer greater than 1. In addition, control system 200 is also connected to control systems 300 and 700 via the network.

[0041] Further, FIG. 1 shows that cloud computing unit 100 can send a configuration data structure 600 (hereinafter also referred to as a cloud template) to control system 200 or 300. Control system 200 can also send a configuration data structure 600 to control system 300 or 700, and control system 200 or 300 can in turn send a configuration data structure 600 to cloud system 1. With the present structure, control system 200 can obtain a configuration data structure 600 from cloud computing unit 100 and send it further to control system 300 or 700; i.e., control system 200 in this case functions as a gateway between cloud computing unit 100 and other control systems. In addition, control system 200, 300, or 700 sends process data 800 to cloud computing unit 100, wherein process data 800 are evaluated by cloud computing unit 100. Cloud computing unit 100 then sends input data 900 to control system 200, 300, or 700 in response to the evaluation of process data 800. Further, input data 900 can also be generated, e.g., by clicking on a button in a dashboard, etc. These various scenarios are described in more detail below in FIG. 3 with a specific example of configuration data structure 600, after the structure of configuration data structure 600 is explained in more detail.

[0042] As shown in FIG. 2, a configuration data structure 600 (cloud template) according to one embodiment comprises a cloud component 601 and a system component 602. This modular structure of the cloud template is preferred in some embodiments, but it should be noted that aspects of the present invention can also function with differently structured cloud templates.

[0043] Cloud component 601 has at least one cloud function 601a, 601b, 601c, and/or 601d which can be carried out on cloud system 1.

[0044] Cloud function 601a contains a pointer element, e.g., for displaying a total power consumption of a building for use within a dashboard.

[0045] Configurations for forming an aggregate (e.g., a calculation formula for generating a sum of the total power consumption of a building) can be edited by cloud function 601b.

[0046] Configurations with respect to storage of the process data (e.g., relating to storage location and storage duration in the cloud) can be edited by cloud function 601c.

[0047] Cloud function 601d provides a bar chart (e.g., to display the course of the room temperature) for use within a dashboard.

[0048] Further, cloud component 601 includes, in particular, settings, configurations, contents, etc., which are required for the display of data with respect to the control systems on the cloud side. These include in particular configuration data (display names, data formatting, units, threshold values), authorizations, predefined visualizations connected to data points (e.g., SVG widgets), statistical evaluations (e.g., comparisons of values over time), device status, device meta information, alarm configurations, configurations of the aggregate formations, definitions of additional calculations, user authorizations, algorithms for data analysis, additional attributes, data export definitions, VPN configurations, backup/restore information, diagnostic information, and rules (e.g., IFTTT (“if this then that”) rules).

[0049] System component 602 has at least one system function 602a, 602b, 602c, and/or 602d which can be carried out on a control system 200, 300, or 700.

[0050] System function 602a provides information regarding a specific firmware version.

[0051] Configurations relating to the data collection frequency and the data transmission frequency can be edited by system function 602b.

[0052] System function 602c is a PLC program, e.g., for controlling a meeting room.

[0053] System function 602d provides connection information to the cloud (e.g., formed of an activation key and a device identifier).

[0054] Further, system component 602 comprises in particular settings and configurations which are required directly in the control systems. These include in particular information about the data collection frequency, the data transmission frequency, and the type of transmission (e.g., telemetry (=cyclical), event (=alarm), value change). Information about the type of data sent (e.g., raw data, aggregates, or about the format and the associated data units) can also be components. PLC programs, e.g., with defined functions such as “close fire doors,” “raise sunscreens at wind force 1,” visualization components, and firmware versions can also be contained in system component 602, as well as backup and diagnostic settings. Settings as to whether the data are to be sent compressed or uncompressed, or settings with regard to possible preaggregations or filtering of data, scaling and conversion of values, etc., can also be contained in system component 602. Further, changes can be made to the PLC program by means of system component 602, e.g., what data should be sent or the configuration of the PLC program. Information about connected sensors/actuators can also be components.

[0055] Cloud computing unit 100 can generate, change, copy, and/or save a configuration data structure 600. Through user input via user unit 400, cloud computing unit 100 can add a system function 602a, 602b, 602c, or 602d in a system component 602 or edit/change an existing system function 602a, 602b, 602c, or 602d in the system component, in order to create/generate a new configuration data structure (600), or to edit/change an existing configuration data structure (600).

[0056] Further, through user input via user unit 400, cloud computing unit 100 can add a cloud function 601a, 601b, 601c, or 601d in a cloud component 601 or edit/change an existing cloud function 601a, 601b, 601c, or 601d in cloud component 601, in order to create/generate a new configuration data structure 600, or to edit/change an existing configuration data structure 600.

[0057] In addition, a database can be integrated with cloud computing unit 100 and cloud computing unit 100 can use entries in the database in order to add/change a system function 602a, 602b, 602c, or 602d in a system component 602 or to add/change a cloud function 601a, 601b, 601c, or 601d in a cloud component 601. The database can be formed in the cloud, in a control system, or in any other memory.

[0058] Control system 200 further functions as a gateway and forwards configuration data structure 600 from cloud computing unit 100 to control system 300 and/or 700. Otherwise it is also possible that control system 200 generates a configuration data structure 600 by itself and this is sent to control system 300 and/or 700.

[0059] In a further example (not shown in FIG. 1), control system 200 is already configured and control system 200 generates a system component 602 based on its own configuration. This system component 602, which can be edited by cloud computing unit 100, is sent further to cloud system 1 in order to generate a new configuration data structure 600, wherein a user can change parameters of system component 602 via user unit 400 before the new configuration data structure 600 is generated.

[0060] In yet another example, control system 300 is configured and control system 300 generates a new configuration data structure 600 based on its own configuration and on a cloud component 601 of a previously obtained configuration data structure 600. This new configuration data structure 600, which can be stored, e.g., directly in a memory of cloud system 1 or can be distributed further to any control system, is then sent further to cloud computing unit 100. It is also possible for a user to change via user unit 400 the parameters of configuration data structure 600 sent by control system 300 before configuration data structure 600 is stored in the memory of cloud system 1 or distributed to any control system.

[0061] A configuration data structure 600 can be distributed from cloud computing unit 100 by means of instructions entered by a user via user unit 400.

[0062] Further, an automatic transmission of configuration data structures 600 without instructions via user unit 400 is also possible. The automatic transmission of configuration data structures 600 can take place both independently between the individual control systems as soon as an identical or similar control system is connected to the network or also via cloud computing unit 100, however. Here, the newly connected control system sends a unique identifier to cloud computing unit 100. In cloud computing unit 100, the unique identifier is compared with the stored configuration data structures. If they match, the matching configuration data structure 600 is automatically assigned to the corresponding control system. Otherwise, the newly connected control system can send a unique identifier, e.g., to control system 200. In control system 200, the unique identifier is then compared with the stored configuration data structures.

[0063] Configuration data structure 600 can be particularly suitable for a specific application, for example, for a control system in the context of tasks in office buildings, in discount stores, in water treatment, in industrial automation, etc. A specific application example is described below with reference to FIG. 3.

[0064] FIG. 3 shows an exemplary configuration data structure 600 for a control system 200, 300, or 700 in connection with a cloud system 1. According to the invention, configuration data structure 600 contains a cloud component 601 and a system component 602. In this example, configuration data structure 600 is provided for a control system 200, 300, or 700 in the field of building automation. More precisely, it concerns a control system 200, 300, or 700, which enables intelligent and efficient use of a meeting room.

[0065] A specific application example is described below.

[0066] Cloud component 601 contains, among other things, cloud functions which are designed for operating and monitoring a control system. The cloud functions can be carried out on cloud computing unit 100. As shown in FIG. 3, cloud component 601 has the following functions:

[0067] DASHBOARD_ROOM-CONTROL, which enables, e.g., remote operation of heating in the meeting room via a graphical dashboard, wherein the graphical dashboard can be accessed via user unit 400 and, in addition to temperature control, also provides insight into the actual current temperature;

[0068] DASHBOARD_ENERGY-MONITORING, which provides another graphical dashboard to enable access to energy monitoring in the context of the meeting room;

[0069] ANALYTIC_ENERGY-CONSUMPTION, which provides a basis for the cloud function DASHBOARD_ENERGY-MONITORING, which obtains process data 800 from control system 200, 300, or 700, analyzes it, and can thus provide information about past and expected energy consumptions;

[0070] ANALYTIC_VOICE, which is a cloud function for analyzing voice commands forwarded to cloud computing unit 100 by a system function in the form of process data 800;

[0071] COMMAND_VOICE, which enables transmission of a corresponding control command in the form of input data 900 back to control system 200, 300, or 700 after the voice commands have been evaluated by the cloud function ANALYTIC_VOICE;

[0072] ALARM_ACCESS_AUTHORISATION, which enables automatic alerting in the event of unauthorized access to the meeting room, wherein in this case the cloud function ALARM_ACCESS_AUTHORISATION enables defined persons to be notified by email, phone call, SMS, etc.

[0073] System component 602 contains, among other things, system functions which are carried out on a control system. As shown in FIG. 3, system component 602 has the following system functions:

[0074] APPLICATION_HEATING, which enables control of the heating;

[0075] APPLICATION_LIGHT, which enables control of the lighting;

[0076] APPLICATION_SHADOWING, which enables control of the sunscreens;

[0077] APPLICATION_VOICE-CONTROL, which enables input of voice commands and their forwarding in the form of process data 800 to cloud computing unit 100;

[0078] VISUALISATION_PANEL-OUTSIDE for the visualization of room functions on screens in front of a meeting room;

[0079] VISUALISATION_PANEL-INSIDE for the visualization of room functions on screens inside the meeting room;

[0080] SETTINGS_SECURITY, which enables security settings such as firewall, access rights, etc., for a control system;

[0081] SETTINGS_CLOUD-CONNECTIVITY, which enables settings regarding the communication between the control system and cloud system 1; and

[0082] SETTINGS_TELEMETRY-DATA-CONFIGURATION for writing data transmitted by the control system (e.g., with regard to data type, measured value unit).

[0083] The invention being thus described, it will be obvious that the same may be varied in many ways. Such variations are not to be regarded as a departure from the spirit and scope of the invention, and all such modifications as would be obvious to one skilled in the art are to be included within the scope of the following claims.