EP3805878B1 - Method for visualizing display data on a data display system and a data display system for visualizing display data - Google Patents

Description

The invention relates to a method for visualizing screen content on a data visualization system according to the preamble of patent claim 1 and a data visualization system for visualizing screen content according to the preamble of patent claim 6.

Requirements regarding the visualization of screen content can exist in different technical areas (technical domains), especially in industrial automation. As part of the development of the "Industrial Internet of Things (IIoT)", factory automation solutions will have to be able to support any number of networked devices in the near future FIGURE 1 is described - will no longer be effectively possible. Among other things, the frequency of changes in an automation system intended for the production process will also increase drastically.

Data visualization systems are used to visualize the screen content, which can be designed, for example, as a Human Machine Interface (HMI) terminal and are used in this form and form not only in the context of factory automation, but also in general in every technical field that involves the use of technical systems is concerned in order to enable a monitoring or control functionality related to a technical process, in particular the production process already mentioned above - eg a current status, access to historical data, etc. The collected data sets are typically displayed on devices with the help of easily understandable graphical objects such as graphs, lists, buttons, pointer instruments, etc for operating and monitoring like the HMI terminals shown.

In the factory automation environment, the screen content of the HMI terminals must be created manually and linked to the appropriate data sources. This is usually done using a central engineering tool, which can be implemented, for example, as a "Totally Integrated Automation (TIA)" portal. The creation must be carried out individually for each end customer - usually by a service specialist with domain know-how. This is below in connection with the description of the FIGURE 1 , which represents the state of the art, explained.

If changes then have to be made to the screen content of the HMI terminals, these require a restart of the entire automation software, i.e. production in the factory comes to a partial or even complete standstill. The changes in the system are adopted and delivered to the corresponding HMI devices when the automation software is restarted. Even with a large number of devices and frequent changes, the central engineering tool must always be used.

The patent application EP 2 840 455 A1 discloses a method for visualizing device operating data on a data visualization system in which, in the context of monitoring a connected, networked device of a technical installation, device operating data can be linked to visualization aspects and a plug-and-play protocol is run between the data visualization system and the device.

In addition, KEBA GmbH Automation offers the "Ke-Top" solution via the "KeStudio ViewEdit" tool, an engineering tool with which you can design user interfaces for their HMI devices and then make them available on Keba devices. With the "TwinCAT 3" tool, Beckhoff Automation GmbH & Co. KG also offers a central engineering framework with which user interfaces for HMI devices must be projected/configured and made available.

FIGURE 1 shows a central engineering for the visualization of screen contents on a data visualization system DVS as it is carried out in a known manner, in which the data visualization system DVS, as already mentioned above, can be designed as an HMI terminal, for example. The central engineering can also include several data visualization systems DVS. So it is according to the FIGURE 1 two data visualization systems DVS, on which screen contents can be visualized. The screen content visualization is explained as an example using a data visualization system DVS of the two data visualization systems DVS shown. Said data visualization system DVS has a non-volatile, readable memory SP, in which processor-readable control program commands of a program module PGM performing the screen content visualization are stored, a processor PZ connected to the memory SP, which executes the control program commands of the program module PGM for screen content visualization and a screen BS up.

To visualize a screen content BSI, the processor PZ accesses the memory SP with the program module PGM on the one hand in order to generate the screen content BSI and on the other hand controls the screen BS so that the generated screen content BSI can be visualized there. How the screen content BSI is generated in the processor PZ with the execution of the control program commands of the program module PGM for screen content visualization is explained below in connection with the description of the FIGURE 1 explained.

The screen contents to be projected/configured during the central engineering for the screen content visualization contain quite generally data from devices of a technical installation AL that are networked in terms of installation and operation to form a device network GNW. In principle, any type of technical installation and any device can serve as a data source as the technical installation AL with the devices. In the case shown, the installation AL is an automation installation AAL in the production process. With regard to the devices in the device network GNW, the system AL, AAL can include either a first device GE or several, e.g. three, devices, a first device GE, a second device GE' and a third device GE", which together with possibly further Devices as the three devices GE, GE', GE" shown as data sources all provide device operating data GBD and are connected to one another in the device network GNW.

From the ones in the FIGURE 1 shown, the device(s) GE, GE', GE" forming the device networks GNW, the first device GE has a first controller CTR, which is connected to a first sensor SE and a first actuator AK, with both the first sensor SE and the first actuator AK deliver data that are stored as operating data BD of the first device GE, ie as device-specific operating data BD, the device operating data GBD in the first controller CTR.

The second device GE' has a second controller CTR', which is connected to a second sensor SE' and a second actuator AK', with both the second sensor SE' and the second actuator AK' supplying data as well further operating data BD' of the second device GE, ie as further device-specific operating data BD', the device operating data GBD are stored in the second controller CTR'.

The situation is a little different with the third device GE". The third device GE" also has a controller, namely a third controller CTR", but this is different from the controllers CTR, CTR' of the other two devices GE 'GE' is not connected to a data-supplying sensor and actuator the third device GE" also has device-specific operating data of the device operating data GBD as a data source. Additional operating data BD" of the third device GE" are stored in the third controller CTR" and are designed as system generation data ALED of the technical system AL, AAL. The system generation data ALED is data that is generated in that the third device GE" receives device operating data GBD from the other two devices GE, GE' in the device network GNW and the system generation data ALED is generated from this transmitted device operating data GBD, e.g. by calculation.

The controllers CTR, CTR′, CTR″ are preferably and not least in the case of the automation system AAL designed as programmable logic controllers (PLC).

The device-specific operating data BD, BD', BD" stored in the devices GE, GE', GE" are now managed centrally. For this purpose, the devices GE, GE', GE" of the device network GNW are connected to a central device control system ZGKS via a communication link KV', which, for example, in the case of the automation system AAL can preferably be a PROFIBUS or PROFINET. The device-specific Operating data BD, BD', BD" either according to the PULL or PUSH mechanism to the Central Device Control System ZGKS. The central device control system ZGKS is preferably designed as a "Supervisory Control and Data Acquisition (SCADA)" system.

In addition to the central device control system ZGKS with the devices GE, GE', GE" in the device network GNW on the one hand and the data visualization system DVS or the data visualization systems DVS on the other hand, there is also a central control unit for project planning/configuration for carrying out the central engineering for displaying the screen content in a known manner This control unit ZSTG, designed as the central engineering tool already mentioned at the outset, is now preferred the TIA Portal running on a "Field PG/PC" component.

For the project planning/configuration of the screen visualization content, which is central in the central control unit ZSTG, in the offline mode of the system AL, AAL, for example, by a service system technician or by the user of the system by consulting an operating and/or service manual for each device GE, GE', GE" is carried out manually on site in the device network GNW, in the central control unit ZSTG from sets of visualization aspects available for the devices GE, GE', GE" - a first visualization aspect set VAS with, for example, five (as in the FIGURE 1 represented by a tally) visualization aspects for the first device GE, a second visualization aspect set VAS' with, for example, three (as in the FIGURE 1 represented by a tally) visualization aspects for the second device GE' and a third set of visualization aspects VAS" with, for example, four (as represented by a tally in FIG. 1) visualization aspects for the third device GE" - each visualization aspect with device-specific operating data linked to this visualization aspect BD, BD', BD" of the device operating data GBD are linked.

Thus, five first visualization aspects VA of the first visualization aspect set VAS with the first operating data BD, three second visualization aspects VA' of the second visualization aspect set VAS' with the second operating data BD' and four third visualization aspects VA" of the third visualization aspect set VAS" with the third operating data BD" manually With this manual link, a project planning/configuration program is generated in each case, namely a first project planning/configuration program PKP when linking the five first visualization aspects VA with the first operating data BD, a second project planning/configuration program PKP' when linking the three second visualization aspects VA' with the second operating data BD and a third project planning/configuration program PKP" when linking the four third visualization aspects VA" with the third operating data BD.

The visualization aspect, including the data binding, i.e. the binding to the operating data BD, BD', BD", includes, for example, the graphic representation of the desired or necessary image information, graphs, the visualization/presentation logic, the link to the data source as the device GE, GE', GE" with the device-specific operating data BD, BD', BD", etc.

The central engineering workflow for project planning/configuration of the screen visualization content on the data visualization system DVS or the HMI terminal via the central control device for project planning/configuration of the screen visualization content ZSTG is to be described below as an example using the in the first controller CTR of the first device GE of the system AL, AAL stored and managed in the central device control system ZGKS as a central collection point first operating data BD of the total of the devices GE, GE ', GE "delivered and managed device operating data GBD in the system ASL, AAL are explained.

Alternatively, the workflow could—without any restrictions—also be outlined using the second or third devices GE′, GE″ with the device-specific operating data BD′, BD″.

The central engineering workflow begins with the data visualization system DVS and the central control unit ZSTG being connected to the central device control system ZGKS via a further communication connection KV", each of which is characterized by a logical connection LOV" and a physical connection PHV". With the technical communication connection between the central control unit ZSTG and the central device control system ZGKS, it is possible to project/configure in relation to the exemplary manually link the screen visualization contents based on the first operating data BD of the first device GE, this device-specific operating data BD - now as already described above - with the first visualization aspects VA of the first visualization aspect set to the first planning/configuration program PKP.

In a next step of the central engineering workflow, the first project planning/configuration program PKP generated in this way in the central control unit ZSTG with the visualization aspects VA and the links to the first operating data BD (the data links) via the logical connection LOV" of the further communication link KV" to the central device control system ZGKS and from there to the first device GE and to the data visualization system DVS for storage there. In the data visualization system DVS, the first planning/configuration program PKP with the visualization aspects VA and the data bindings via the processor PZ is stored in the memory SP as part of the program module PGM, where the first planning/configuration program PKP is executed directly or with a time delay . In the course of this program execution (also referred to as deployment), the first operating data BD are now loaded from the central device control system ZGKS via the physical connection PHV" into the data visualization system DVS under the control authority of the processor PZ. These first operating data are also under the control authority of the processor PZ BD then at least partially visualized as the screen content BSI on the screen BS in relation to at least one and in the context of at least one dedicated visualization aspect of the first visualization aspects VA made available with the first planning/configuration program PKP.

The object on which the invention is based is to provide a method for visualizing screen contents on a data visualization system and a data visualization system for the visualization of screen content, with which the functionality monitoring and control will be possible in the future with a drastically increasing frequency of changes and in the course of the "Internet of Things"("Internet Of Things <IOT>") a sharp increase in the number of networked devices in technical systems, in particular automation systems in the production process can be carried out effectively.

Starting from the method defined in the preamble of patent claim 1, this object is achieved by the features specified in the characterizing part of patent claim 1.

Furthermore, starting from the data visualization system defined in the preamble of patent claim 6, the object is achieved by the features specified in the characterizing part of patent claim 6.

The idea on which the invention is based according to independent claims 1 and 6 consists in displaying screen content on a data visualization system - in particular automatically, dynamically, e.g Online operation of the devices or the system - to visualize, in which each visualization aspect of a set of visualization aspects available for the device can be linked to device-specific operating data provided by the system that are bound to this visualization aspect. This is done in that, after the system has been integrated into the device network, by executing a plug-and-play protocol in accordance with a pre-planning/pre-configuration program between the data visualization system and the device and with a dedicated (chosen) control of the device in the device network a project planning/configuration program provided in the device with a large number of monitoring/control objects, the monitoring/control objects being linked by linking the set of visualization aspects are determined and specified with the visualization aspects and visualization aspect-related data bindings to the device-specific operating data of the device operating data, is loaded into the data visualization system and this planning/configuration program is executed by (i) in relation to one of the set of visualization aspects with the visualization aspects selected visualization aspect, a monitoring/control object corresponding thereto is selected from the monitoring/control objects, (ii) according to the visualization aspect-related data binding of the selected monitoring/control object, corresponding operating data of the device-specific operating data are loaded for this selection and (iii) the selected operating data in be visualized as the screen content in relation to the selected visualization aspect.

According to one development of the invention (claims 2 and 7), it is expedient if the data visualization system is an HMI terminal or an HMI application. The HMI application is preferably an "APP" (APPLICATION) implemented and running on, for example, a conventional personal computer in the form of a notebook, tablet, smartphone, etc.

A further advantageous development of the invention (claims 3 and 8) is that the set of visualization aspects with the visualization aspects and the planning/configuration program with the monitoring/control objects is made available in the course of device manufacture.

With regard to a further aspect of the invention (claims 4 and 9), it is expedient if the operating data and the device operating data extend to sensor data, actuator data and/or system generation data of the technical system.

In terms of simple handling and operation, the invention can also be advantageously further developed (claims 5 and 10) in that the selected visualization aspect from the set of visualization aspects and the corresponding selected monitoring/control object are selected using a selection menu on a screen of the data visualization system becomes.

The solution according to the invention dispenses with the known and in the representation of FIGURE 1 contained, preferably as a central engineering tool, e.g. as a TIA portal, for the central engineering trained central control unit for project planning/configuration of screen visualization contents and allows device or system manufacturers based on domain know-how optimized visualizations or representations of the device operating data with the help of monitoring -/Control objects, in which the visualization aspects including the data bindings to the operating data are included. These can be decentralized, automatic, dynamic in a device/system setup without additional central engineering effort - with regard to the choice of visualization or display form, the link to the dedicated controlled device and its operating data, i.e. the data source of choice, etc and, for example, when the device or system is running, i.e. online, are loaded into the data visualization system. The engineering takes place in contrast to in the FIGURE 1 represented state of the art, where it happens manually and offline, takes place automatically and online without central engineering.

The visualization aspect, including data binding, i.e. the binding to device operating data, includes the graphic representation of the desired or necessary image information, graphs, the visualization/display logic, the link to the data source, etc.

The decentralized engineering workflow for project planning/configuration of the screen contents is determined by the order of the characterizing features specified in claims 1 and 6. In this way, the problem on which the invention is based can be implemented effectively, the project planning/configuration software used, in particular the project planning/configuration program, can be used continuously when changes occur frequently, and any number of devices can be supported.

The solution according to the invention is characterized in particular by the fact that any number can be supported, screen contents can be distributed at runtime without restarting, no engineering effort is required with regard to visualization/representation and the linking of the data source on the user/end customer side, the domain know-how -how only has to be applied once on the manufacturer side and not repeatedly on the customer side.

All of this is addressed via a decentralized provision of the screen content, i.e. the screen content (configuration, definition and project planning) is distributed at runtime.

The concept according to the invention prepares for future technologies, which are characterized by the "Industrial Internet of Things (IIoT)", particularly in the industrial environment. This concept also enables the end customer, i.e. the device or system user, to be offered a modular and flexibly expandable data visualization system in this way. From the point of view of the device/system manufacturer, this makes the end customer more flexible with regard to changes.

In addition, the technical connection is decoupled from the logical connection via a topic-based provision of data and services.

As an alternative to the provision of the visualization aspects including the data bindings, i.e. the provision of the monitoring/control objects, it is also conceivable for the whole thing to be offered not via the individual devices but via an Internet platform, for example in the industrial environment via the Siemens-specific "Mindsphere" platform. In this case, devices would register their data source with the "Mindsphere" and link it to the display descriptions provided by the manufacturer.

Further advantages of the invention result from the FIGURE 1 from the following description of an embodiment of the invention with reference to FIGURE 2 .

FIGURE 2 shows based on the FIGURE 1 a decentralized engineering for the visualization of screen contents on a data visualization system DVS as it is carried out in a known manner, in which the data visualization system DVS, preferably either as an HMI terminal or as an HMI application in the form of an "APP" (APPLICATION), for example on a implemented and running on a conventional personal computer in the form of a notebook, a tablet, a smartphone, etc. The decentralized engineering can also include several data visualization systems DVS. So it is according to the FIGURE 2 , as with the FIGURE 1 , again two data visualization systems DVS, on which screen contents can be visualized. The screen content visualization is used as an example, as in the FIGURE 1 , explained using a data visualization system DVS of the two data visualization systems DVS shown.

Said data visualization system DVS again has a non-volatile, readable memory SP, in which processor-readable control program commands of a program module PGM that performs the screen content visualization are stored, a processor PZ connected to the memory SP, which executes the control program commands of the program module PGM for screen content visualization and a screen BS.

To visualize a screen content BSI, the processor PZ accesses the memory SP with the program module PGM on the one hand in order to generate the screen content BSI and on the other hand controls the screen BS so that the generated screen content BSI can be visualized there. How the screen content BSI is generated in the processor PZ with the execution of the control program commands of the program module PGM for screen content visualization is explained below in connection with the description of the FIGURE 2 explained.

In contrast to the data visualization system DVS in the FIGURE 1 is at the in the FIGURE 2 shown data visualization system DVS a pre-project planning / pre-configuration program VPKP stored as part of the program module PGM in the memory SP and it can be displayed on the screen BS a selection menu AWM. What the pre-project planning/pre-configuration program VPKP and the AWM selection menu is all about is explained below in the description of the FIGURE 2 explained.

The screen contents to be projected/configured for the screen contents visualization in the decentralized engineering again contain, as shown in the central engineering in the FIGURE 1 , very generally data from devices of a technical installation AL that are networked in terms of installation and operation to form a device network GNW. In principle, any type of technical installation and any device can again serve as a data source as the technical installation AL with the devices. In the case shown, the installation AL is an automation installation AAL in the production process. With regard to the devices in the device network GNW, the system AL, AAL can include either a first device GE or several, e.g. three, devices, a first device GE, a second device GE' and a third device GE", which together with possibly further Devices as the three devices GE, GE', GE" shown as data sources all provide device operating data GBD and are connected to one another in the device network GNW.

From the ones in the FIGURE 2 like in the FIGURE 1 shown, the device(s) GE, GE', GE" forming the device networks GNW, the first device GE has a first controller CTR, which is connected to a first sensor SE and a first actuator AK, with both the first sensor SE and the first actuator AK deliver data that are stored as operating data BD of the first device GE, ie as device-specific operating data BD, the device operating data GBD in the first controller CTR.

The second device GE' has a second controller CTR', which is connected to a second sensor SE' and a second actuator AK', with both the second sensor SE' and the second actuator AK' supplying data as well further operating data BD' of the second device GE, ie as further device-specific operating data BD', the device operating data GBD are stored in the second controller CTR'.

The situation with the third device GE" is also a little different here. The third device GE" also has a controller, namely a third controller CTR", but this is different from the controllers CTR, CTR' of the other two Devices GE, GE' are not connected to a data-supplying sensor and actuator. Nevertheless, the third device GE" also supplies device-specific operating data of the device operating data GBD as a data source. Additional operating data BD" of the third device GE" are stored in the third controller CTR" and are designed as system generation data ALED of the technical system AL, AAL. The system generation data ALED are data that are generated by the third device GE" being other two devices GE, GE' in the device network GNW receives device operating data GBD and the system generation data ALED are generated from these transmitted device operating data GBD, for example by calculation.

The controllers CTR, CTR′, CTR″ are again preferably and not least in the case of the automation system AAL designed as programmable logic controllers (PLC).

In contrast to the controllers CTR, CTR', CTR" in the FIGURE 1 show the in the FIGURE 2 illustrated controllers CTR, CTR', CTR" respectively, like that in the FIGURE 2 shown data visualization system DVS, the pre-project planning/pre-configuration program VPKP, which is stored in the controllers CTR, CTR', CTR". What is the meaning of this pre-project planning/pre-configuration program VPKP stored in the controller CTR, CTR', CTR" in the context of the decentralized engineering in the project planning/configuration of the screen content for the screen content visualization is described below in the description of the FIGURE 2 explained.

For the decentralized project planning/configuration of the screen visualization content, a set of visualization aspects, a first visualization aspect set VAS with e.g. five (as in the FIGURE 2 represented by a tally) visualization aspects in the first device GE, a second visualization aspect set VAS' with, for example, three (as in FIGURE 2 represented by a tally) visualization aspects in the second device GE' and a third visualization aspect set VAS" with, for example, four (as in FIGURE 2 represented by a tally) visualization aspects are made available in the third device GE" and stored accordingly in the respective controller CTR, CTR', CTR".

Also preferably in the course of device manufacture, each visualization aspect can be linked to device-specific operating data BD, BD', BD" of the device operating data GBD that is bound to this visualization aspect. For example, five first visualization aspects VA of the first visualization aspect set can be linked in the course of device manufacture VAS with the first operating data BD, three second visualization aspects VA' of the second visualization aspect set VAS' with the second operating data BD' and four third visualization aspects VA" of the third visualization aspect set VAS" with the third operating data BD", e.g shortcut program), link.

With this link, a project planning/configuration program each with a large number of monitoring/control objects is generated and correspondingly stored in the respective controller CTR, CTR', CTR", namely a first project planning/configuration program PKP with five first monitoring/control objects ÜKO, which determine and specify the linking of the five first visualization aspects VA with the first operating data BD, a second project planning/configuration program PKP' with three second monitoring/control objects ÜKO', which link the three second visualization aspects VA' with the second operating data Determine and specify BD', as well as a third planning/configuration program PKP" with four third monitoring/control objects ÜKO", which determine and specify the linking of the four third visualization aspects VA" with the third operating data BD.

The visualization aspect, including the data binding, i.e. the bindings to the operating data BD, BD', BD", again includes, for example, the graphic representation of the desired or necessary image information, graphs, the visualization/representation logic, the link to the data source as the device GE , GE', GE" with the device-specific operating data BD, BD', BD", etc.

The decentralized engineering workflow for project planning/configuration of the screen visualization content on the data visualization system DVS or the HMI terminal or the HMI application is to be described below as an example using the in the first controller CTR of the first device GE of the system AL, AAL stored first operating data BD, the first visualization aspect set VAS stored there with the five first visualization aspects VA linked to the first operating data BD and the first project planning/configuration program PKP with the first plurality of monitoring/control objects ÜKO, which link the five determine and indicate the first visualization aspects VA with the first operating data BD.

Alternatively, the workflow could—without any restrictions—also be outlined using the second or third of the devices GE′, GE″, devices considered as dedicated, with the device-specific operating data BD′, BD″.

The decentralized engineering workflow begins with the fact that the data visualization system DVS is integrated into the device network GNW of the system AL, AAL by the data visualization system DVS being connected to the first device GE via a communication connection KV, this being connected in each case by a logical connection LOV and a Physical connection PHV is characterized. Of course, the data visualization system DVS or the other in the FIGURE 2 data visualization system DVS shown can also be connected accordingly to the other devices GE, GE or to the first device GE. On a corresponding consideration of the graphic representation in the FIGURE 2 has been omitted because of the exemplary explanation of the decentralized engineering workflow for projecting/configuring the screen visualization content using the first device GE.

In a next step of the decentralized engineering workflow, when integrating the data visualization system DVS into the device network GNW and executing the control program commands of the program module PGM by the processor PZ on the basis of the program module PGM of the memory SP in the data visualization system DVS and pre-planning/pre-configuration program contained in the first device GE VPKP executed and handled a plug-and-play protocol PPP between the processor PZ and the first device GE via the logical connection LOV in order to connect the data visualization system DVS with the first device GE in terms of communication and control technology.

In a subsequent step of the decentralized engineering workflow - during the further execution of the control program commands of the program module PGM by the processor PZ in the course of this communication and control-related connection and also via the logical connection LOV dedicated (chosen) control of the first Device GE in the device network GNW - the project planning/configuration program PKP generated and stored there in the first device GE, e.g determine and specify the first operating data BD, loaded into the memory SP of the data visualization system DVS for project planning/configuration of the screen content to be visualized BSI. This loading of the planning/configuration program PKP with the five first monitoring/control objects ÜKO preferably takes place in such a way that the planning/configuration program PKP becomes part of the program module PGM when it is loaded.

1. a) in Bezug auf einen aus dem ersten Satz der Visualisierungsaspekte VAS mit den ersten Visualisierungsaspekten VA ausgewählten Visualisierungsaspekt VA* ein dazu korrespondierendes Überwachungs-/Kontrollobjekt ÜKO* aus den ersten Überwachungs-/Kontrollobjekten ÜKO ausgewählt wird,
2. b) gemäß der Visualisierungsaspekt-bezogenen Datenbindung des ausgewählten Überwachungs-/Kontrollobjekts ÜKO* zu dieser Auswahl korrespondierende Betriebsdaten BD* der gerätspezifische Betriebsdaten BD, BD', BD" aus dem ersten Gerät GE in das Datenvisualisierungssystem DVS - z.B. in den Prozessor PZ oder vorzugsweise in den Speicher SP, wie in der FIGUR 2 dargestellt - geladen werden und
3. c) die zu dem ausgewählten Überwachungs-/Kontrollobjekt ÜKO* korrespondierenden Betriebsdaten BD*, also die ausgewählten Betriebsdaten BD*, in Bezug auf den ausgewählten Visualisierungsaspekt VA* als der Bildschirminhalt BSI visualisiert werden.

In a final step of the decentralized engineering workflow, the processor PZ executes the project planning/configuration program PKP loaded into the memory SP in such a way that

1. a ) in relation to a visualization aspect VA* selected from the first set of visualization aspects VAS with the first visualization aspects VA, a corresponding monitoring/control object ÜKO* is selected from the first monitoring/control objects ÜKO,
2. b) according to the visualization aspect-related data binding of the selected monitoring/control object ÜKO* to this Selection of corresponding operating data BD* of the device-specific operating data BD, BD', BD" from the first device GE into the data visualization system DVS - e.g. into the processor PZ or preferably into the memory SP, as in FIG FIGURE 2 shown - to be loaded and
3. c) the operating data BD* corresponding to the selected monitoring/control object ÜKO*, ie the selected operating data BD*, are visualized as the screen content BSI in relation to the selected visualization aspect VA*.

The visualization aspect VA* from the first set of visualization aspects VAS and the corresponding, selected monitoring/control object ÜKO* can be selected using the selection menu AWM.

Claims (10)

1. Method for visualizing screen content on a data visualization system (DVS), in which

   a) in the context of monitoring and controlling the functionality of at least one device (GE, GE', GE''), which is networked in an installation-related and operational manner to form a device network (GNW), in a technical installation (AL), in particular an automation installation (AAL) in the production process, for planning/configuring screen content (BSI)

   a1) device operating data (GBD) for monitoring and controlling the functionality are captured and are provided for the data visualization system (DVS),

   a2) from a set of visualization aspects (VAS, VAS', VAS") which is available for the device (GE, GE', GE"), each visualization aspect (VA, VA', VA") can be linked to device-specific operating data (BD, BD*, BD', BD") of the device operating data (GBD), which device-specific operating data are respectively tied to this visualization aspect,

   b) when incorporating (KV, LOV, PHV) the data visualization system (DVS) in the device network (GNW) on the basis of a preplanning/preconfiguration program (VPKP) contained in the data visualization system (DVS) and in the device (GE, GE', GE"), a plug-and-play protocol (PPP) is executed between the data visualization system (DVS) and the device (GE, GE', GE"), which is used to connect the data visualization system (DVS) in terms of communication and control to the device (GE, GE', GE"), characterized in that

   c) during this communication and control connection (KV, LOV, PHV) in the case of dedicated control of the device (GE, GE', GE") in the device network (GNW), a planning/configuration program (PKP, PKP', PKP") which is provided in the device (GE, GE', GE") and has a multiplicity of monitoring/control objects (UKO, ÜKO', ÜKO"), wherein the monitoring/control objects (UKO, ÜKO', ÜKO") are determined and stated by linking the set of visualization aspects (VAS, VAS', VAS") to the visualization aspects (VA, VA', VA") and visualization-aspect-based data bindings of the device-specific operating data (BD, BD', BD"), is loaded into the data visualization system (DVS) for the purpose of planning/configuring the screen content (BSI) to be visualized,

   d) the planning/configuration program (PKP, PKP', PKP") loaded into the data visualization system (DVS) is executed by

   d1) selecting, with respect to a visualization aspect (VA*) selected from the set of visualization aspects (VAS, VAS', VAS") having the visualization aspects (VA, VA', VA"), a corresponding monitoring/control object (ÜKO*) from the monitoring/control objects (UKO, ÜKO', ÜKO"),

   d2) loading, according to the visualization-aspect-based data binding of the selected monitoring/control object (ÜKO*), operating data (BD*) of the device-specific operating data (BD, BD', BD"), which correspond to this selection, into the data visualization system (DVS), and

   d3) visualizing the selected operating data (BD*) with respect to the selected visualization aspect (VA*) as the screen content (BSI).
2. Method according to Claim 1, characterized in that an HMI terminal or an HMI application is used as the data visualization system (DVS).
3. Method according to Claim 1 or 2, characterized in that the set of visualization aspects (VAS, VAS', VAS") having the visualization aspects (VA, VA', VA", VA*) and the planning/configuration program (PKP, PKP', PKP") having the monitoring/control objects (UKO, ÜKO', ÜKO", ÜKO*) are provided when producing the device.
4. Method according to one of Claims 1 to 3, characterized in that
   the operating data (BD, BD', BD", BD*) and the device operating data (GBD) are at least one of sensor data (SE, SE'), actuator data (AK, AK') and installation generation data (ALED) of the technical installation (AL, AAL).
5. Method according to one of Claims 1 to 4, characterized in that
   the selected visualization aspect (VA*) from the set of visualization aspects (VAS, VAS', VAS") and the corresponding selected monitoring/control object (ÜKO*) are selected with the aid of a selection menu (AWM) on a screen (BS) of the data visualization system (DVS).
6. Data visualization system (DVS) for visualizing screen content, having a non-volatile readable memory (SP) which stores processor-readable control program instructions of a program module (PGM) carrying out the screen content visualization, and a processor (PZ) which is connected to the memory (SP) and executes the control program instructions of the program module (PGM) for visualizing the screen content, wherein

   a) in the context of monitoring and controlling the functionality of at least one device (GE, GE', GE"), which is networked in an installation-related and operational manner to form a device network (GNW), in a technical installation (AL), in particular an automation installation (AAL) in the production process, for planning/configuring screen content (BSI)

   a1) device operating data (GBD) for monitoring and controlling the functionality are captured and are provided for the data visualization system (DVS),

   a2) from a set of visualization aspects (VAS, VAS', VAS") which is available for the device (GE, GE', GE"), each visualization aspect (VA, VA', VA") can be linked to device-specific operating data (BD, BD*, BD', BD") of the device operating data (GBD), which device-specific operating data are respectively tied to this visualization aspect,

   the processor (PZ) and the program module (PGM) are designed in such a manner and the processor (PZ) executes the control program instructions of the program module (PGM) in such a manner that

   b) when incorporating (KV, LOV, PHV) the data visualization system (DVS) in the device network (GNW) on the basis of a preplanning/preconfiguration program (VPKP) contained in the program module (PGM) of the memory (SP) in the data visualization system (DVS) and in the device (GE, GE', GE"), a plug-and-play protocol (PPP) is executed between the processor (PZ) and the device (GE, GE', GE"), which is used to connect the data visualization system (DVS) in terms of communication and control to the device (GE, GE', GE"),
   characterized in that

   c) during this communication and control connection (KV, LOV, PHV) in the case of dedicated control of the device (GE, GE', GE") in the device network (GNW), a planning/configuration program (PKP, PKP', PKP") which is provided in the device (GE, GE', GE") and has a multiplicity of monitoring/control objects (UKO, ÜKO', ÜKO"), wherein the monitoring/control objects (UKO, ÜKO', ÜKO") are determined and stated by linking the set of visualization aspects (VAS, VAS', VAS") to the visualization aspects (VA, VA', VA") and visualization-aspect-based data bindings to the device-specific operating data (BD, BD', BD"), is loaded into the memory (SP), preferably as part of the program module (PGM), via the processor (PZ) for the purpose of planning/configuring the screen content (BSI) to be visualized,

   d) the planning/configuration program (PKP, PKP', PKP") loaded into the memory (SP) is executed by

   d1) selecting, with respect to a visualization aspect (VA*) selected from the set of visualization aspects (VAS, VAS', VAS") having the visualization aspects (VA, VA', VA"), a corresponding monitoring/control object (ÜKO*) from the monitoring/control objects (UKO, ÜKO', UKO"),

   d2) loading, according to the visualization-aspect-based data binding of the selected monitoring/control object (ÜKO*), operating data (BD*) of the device-specific operating data (BD, BD', BD"), which correspond to this selection, into the data visualization system (DVS), for example into the processor (PZ) or preferably into the memory (SP), and

   d3) visualizing the selected operating data (BD*) with respect to the selected visualization aspect (VA*) as the screen content (BSI).
7. Data visualization system (DVS) according to Claim 6, characterized by
   an HMI terminal or an HMI application.
8. Data visualization system (DVS) according to Claim 6 or 7, characterized in that
   the set of visualization aspects (VAS, VAS', VAS") and the planning/configuration program (PKP, PKP', PKP") having the monitoring/control objects (UKO, ÜKO', ÜKO", ÜKO*) are provided when producing the device.
9. Data visualization system (DVS) according to one of Claims 6 to 8, characterized in that
   the operating data (BD, BD', BD", BD*) and the device operating data (GBD) are at least one of sensor data (SE, SE'), actuator data (AK, AK') and installation generation data (ALED) of the technical installation (AL, AAL).
10. Data visualization system (DVS) according to one of Claims 6 to 9, characterized by
    a screen (BS) on which the selected visualization aspect (VA*) from the set of visualization aspects (VAS, VAS', VAS") and the corresponding selected monitoring/control object (ÜKO*) can be selected with the aid of a selection menu (AWM).

Images