Method and operating unit for tracking the use of operating software

Abstract

The invention comprises a method for tracking the use of operating software (BS) which is executed on an operating unit (BE), wherein the operating unit (BE) establishes at least one communication connection to at least one automation technology field device (FG1, FG2) via at least one communication network (KN), wherein the operating software (BS) is designed to operate the field device (FG1, FG2) or field devices, wherein the operating software (BS) is a frame application or comprises a frame application, and is designed to execute device and communication drivers (GT1, GT2, KT), by means of which device and communication drivers (GT1, GT2, KT) the field devices (FG1, FG2) can be accessed and via which device and communication drivers (GT1, GT2, KT) operating functionalities are provided to the field devices (FG1, FG2), the method comprising: - capturing usage data (ND) of the operating software (BS) over a time period, the usage data comprising a respective number of uses of functionalities of the operating software (BS) within the time period, a usage duration of one or more of the functionalities of the operating software (BS) and / or communication data; and - storing the usage data (ND) on the operating unit (BE) and / or outputting the usage data (ND) by the operating unit (BE). The invention also relates to an operating unit (BE) for carrying out the method according to the invention.

Description

[0001] Method and operating unit for tracking the use of operating software

[0002] The invention relates to a method for tracking the usage of operating software executed on an operator unit, wherein the operator unit establishes at least one communication connection with at least one field device of automation technology via at least one communication network, in particular a fieldbus network or an Ethernet-based network, wherein the operating software is designed to operate the field device(s), wherein the operating software is a frame application or comprises a frame application, in particular an FDT frame application and / or an FDI host, and is designed to execute device and communication drivers by means of which device and communication drivers can access the field devices and via which device and communication drivers operating functionalities of the field devices are provided. The invention further relates to an operator unit.

[0003] Field devices are already known from the state of the art and are used in industrial plants. They are widely used in process automation as well as in manufacturing automation. In principle, field devices are defined as all devices that are used close to the process and that provide or process process-relevant information. Thus, field devices are used to acquire and / or influence process variables. Measuring devices or sensors are used to acquire process variables. These are used, for example, for measuring pressure and temperature, conductivity, flow rate, pH, level, etc., and acquire the corresponding process variables such as pressure, temperature, conductivity, pH value, level, and flow rate. Actuators are used to influence process variables.These include, for example, pumps or valves that can influence the flow of a liquid in a pipe or the fill level in a container. In addition to the aforementioned measuring devices and actuators, field devices also include remote I / Os, radio adapters, and generally any devices located at the field level.

[0004] A large number of such field devices are produced and distributed by the Endress+Hauser Group.

[0005] In modern industrial plants, field devices are typically connected to higher-level units via communication networks such as fieldbuses (PROFIBUS®, FOUNDATION™ Fieldbus, HART®, IO-Link, etc.) or modern Ethernet-based networks (Industrial Ethernet, such as PROFINET, EtherNet / IP, etc.). These higher-level units are usually control systems (CMS) or control units, such as a PLC (programmable logic controller). The higher-level units are used, among other things, for process control, process visualization, process monitoring, and commissioning of the field devices. The measured values ​​acquired by the field devices, especially sensors, are transmitted via the respective bus system to one (or possibly several) higher-level unit(s).In addition, data transmission from the higher-level unit via the bus system to the field devices is also required, in particular for the configuration and parameterization of field devices and for the control of actuators.

[0006] To operate the field devices, appropriate operating software (operating tools) is required. This software either runs independently on the higher-level units (Endress+Hauser FieldCare, Pactware, AMS Fisher-Rosemount, Siemens PDM) or is integrated into control room applications (Siemens PCS7, ABB Symphony, Emerson Delta V). The term "operating" includes, among other things, configuring the field device, updating the field device, and / or querying and visualizing process data and / or diagnostic data from the field device.

[0007] The integration of field devices into such operating software is achieved via device drivers or device descriptions. These are provided by the device manufacturers so that the higher-level units, or the operating programs running on these higher-level units, can recognize and interpret the meaning of the information supplied by the field devices. Such an operating program, into which the device descriptions or device drivers are loaded, is also referred to as a framework application.

[0008] For comprehensive operation of field devices, special device drivers, so-called DTMs (Device Type Managers), which comply with the FDT (Field Device Tool) specifications, are available. Many field device manufacturers supply corresponding DTMs for their field devices. The DTMs encapsulate all variables and functions of the respective field device and usually offer a graphical user interface for operating the devices within the framework application.

[0009] Another way to operate field devices in a bus system is based on EDD technology. EDDs (Electronic Device Descriptions) are text-based device description files. EDD technology also allows different device types from different manufacturers to be operated and parameterized with a single software tool. EDDs are written in the Electronic Device Description Language (EDDL), which serves as a universal language for technologies such as HART, PROFIBUS, and FOUNDATION Fieldbus. EDDs are executed analogously by a framework application.

[0010] A further development is FDI technology. Field Device Integration (FDI) combines the advantages of the two previously mentioned integration technologies. Existing EDDs can continue to be used with FDI technology without modification. FDI technology was jointly developed by process industry associations including the FieldComm Group, PROFIBUS International, the OPC Foundation, and the FDT Group, and is standardized in IEC 62769.

[0011] At the heart of the FDI standard is the FDI Device Package. This is a standardized container that holds all the components required to describe the field devices in an automation system. FDI device packages contain EDDs for field devices and optional UIPs (User Interface Plug-ins) for implementing complex device functions, such as the previously mentioned echo curve of a radar level gauge, and DTMs. FDI packages are executed by an FDI host, analogous to a frame application. FDT DTM technology, using an iDTM, enables the use of FDI device packages on any host computer running an FDT frame application. CodeWright's product serves as an example of an iDTM. EDDs and, if applicable, UIP components within the FDI device package are represented by the iDTM as device DTMs.

[0012] In addition to the higher-level units, operator panels are frequently used to operate the field devices. These panels run a corresponding framework application (EDD, FDT / DTM) or an FDI host. Examples of such operator panels include laptops and mobile devices like tablet PCs. They are connected to a fieldbus access unit linked to the fieldbus network for communication with the field devices.

[0013] As previously described, appropriate operating software is provided for various types of communication networks, e.g., HART, Profibus, etc., and offers a wide range of functionalities. This involves a significant investment of time and money in developing the operating software, without the developers or software providers knowing which of the variants will actually be used by customers.

[0014] Applications that enable the tracking of software function usage are known from the prior art. One such application is described, for example, in EP 305 3123 A1. However, these applications focus on tracking user interaction with the software, such as which windows a user opens and / or which buttons they click.

[0015] Based on this problem, the invention aims to present a method that allows a statement to be made about the use of operating software employed in automation technology. This objective is achieved by a method according to claim 1 and by an operating unit according to claim 8.

[0016] The method is designed to track the use of operating software, the operating software being executed on an operator unit, the operator unit establishing at least one communication connection with at least one field device of the automation technology via at least one communication network, in particular a fieldbus network or an Ethernet-based network, the operating software being designed to operate the field device(s), the operating software being or comprising a frame application, in particular an FDT frame application and / or an FDI host, and being designed to execute device and communication drivers, by means of which device and communication drivers the field devices can be accessed and via which device and communication drivers operating functionalities of the field devices are provided, the method comprising:

[0017] Recording usage data of the operating software over a period of time, wherein the usage data includes a respective number of uses of functionalities of the operating software within the period, a usage duration of one or more of the functionalities of the operating software and / or communication data; and storing the usage data on the operating unit and / or outputting the usage data by the operating unit.

[0018] The method according to the invention makes it possible to record or track the actual use of software functionalities. This use is divided into two principal aspects: Firstly, communication data is recorded. This means that it records how the operating software is used to communicate with field devices.

[0019] Secondly, tracking encompasses certain functionalities of the operating software. The operating software includes a wide range of functionalities, such as executing device drivers. Tracking includes the number, frequency, and duration of each use of these functionalities.

[0020] Usage data allows the provider of the user interface software to improve the software based on usage data. For example, they can optimize the software by improving existing connectivity and reducing the number of unused connections. This can reduce security vulnerabilities, storage space requirements, the risk of errors, and other issues. Furthermore, anomalies in the number or frequency of function calls can reveal timeout / retry calls that would normally go unnoticed.

[0021] The term "operation" includes, among other things, parameterizing the field device, updating the field device and / or querying and visualizing process data and / or diagnostic data of the field device.

[0022] Field devices mentioned within the scope of the invention described herein have already been mentioned by way of example in the introductory part of the description.

[0023] The standards listed (FDT / DTM, FDI, etc.) have already been explained in the introductory part of the description. Other standards not mentioned here, which are used to operate field devices, are also covered by the invention.

[0024] According to one embodiment of the procedure, the functionalities include executing one or more device drivers and / or performance monitoring of the device drivers. Performance monitoring includes, among other things, tracking system performance and resources during the execution of the device drivers, and how these are affected by their execution. It can also be verified for what purpose (specific operations, etc.) the device drivers are used.

[0025] The term "device driver" encompasses, for example, DTMs ("Device Type Managers") or FDI packages. In a broader sense, EDDs (device descriptions) also fall under this term.

[0026] According to one design of the procedure, the communication data is intended to include one or more of the following:

[0027] Information regarding the number and / or duration of communication links established via the relevant communication networks between the operator unit and field devices and / or other network participants, in particular gateways or edge devices;

[0028] Information regarding the communication protocols used for the communication links;

[0029] Information on the number of devices that can be connected to or are connected to the network;

[0030] Information on detected but unconnectable devices and information explaining the reasons for the unconnectability.

[0031] Information on the topology of other network participants; information on problems with the communication link, in particular comprehensive connection interruptions and / or reconnections.

[0032] The "devices" mentioned here can be field devices, but also other network participants such as gateways or edge devices.

[0033] According to one embodiment of the procedure, the output of usage data includes transmitting the usage data from the operating unit to a cloud-based platform. This cloud-based platform is specifically established on a server or server system accessible via the internet. One or more software applications can be executed on this server or server system and are accessible to an operator via the internet. In particular, in one embodiment of the procedure, the cloud-based platform executes at least one such software application, which processes the usage data and, in particular, generates statistics on the use of the operating software based on the processed usage data. The processed usage data and / or the statistics can also be visualized for the operator in a suitable format.

[0034] According to one design of the procedure, the operating software is intended to anonymize the usage data before outputting it.

[0035] It may also be provided that, in the event that there is no connection between the control unit and the cloud-based platform, the control unit collects the recorded usage data and, if a connection to the cloud-based platform exists, transmits it to the cloud-based platform.

[0036] With regard to the operating unit, it is intended that it is designed to establish at least one communication connection with at least one field device of the automation technology via at least one communication network and to execute operating software, wherein the operating software is used to operate the field device, orthe field devices, wherein the operating software is a frame application or wherein the operating software comprises a frame application, in particular an FDT frame application or an FDI host, and is configured to execute device and communication drivers by means of which device and communication drivers can access the field devices and via which device and communication drivers operating functionalities of the field devices are provided, wherein the operating unit is configured to record usage data of the operating software over a period of time, wherein the usage data comprises a respective number of uses of functionalities of the operating software within the period of time, a usage duration of one or more of the functionalities of the operating software and / or communication data, and wherein the operating unit is configured to store and / or output usage data.

[0037] One configuration of the control unit provides that the control unit is a computer unit, in particular a laptop. Alternatively, the control unit is a mobile device, in particular a smartphone or a tablet.

[0038] The invention is explained in more detail with reference to the following figure. It shows

[0039] Fig. 1 : an embodiment of the method according to the invention.

[0040] Figure 1 shows an application of the method. Two field devices FG1 and FG2 are integrated into a communication network KN. In this case, the field devices FG1 and FG2 are measuring instruments for acquiring physical, chemical, and / or biological measured values ​​of a process, such as temperature or flow rate. The communication network is, for example, a fieldbus such as HART, Foundation Fieldbus, or Profibus PA, or an Ethernet-based network such as Profinet or Ethernet / IP.

[0041] Field devices FG1 and FG2 are operated by an operating unit BE, for example, for parameterization. The operating unit BE, which may be a mobile device or a laptop, is connected to the communication network KN via a first communication interface KS1. Operating software BS runs on the operating unit BE; in this case, an FDT framework application (for example, the "Fieldcare" distributed by the applicant). The operating software BS allows the integration of various driver types to enable operation of field devices FG1 and FG2. A specific device driver, in this case a DTM, is executed for each field device FG1 and FG2, providing the user with a graphical user interface, for example, for parameter selection and value input, specific to that field device type.A communication driver, for example a Comm-DTM, encapsulates the operating commands received from the device drivers into telegrams designed in accordance with the protocol of the KN communication network.

[0042] Alternatively, other suitable types of operating system software (OS) can be used, such as an FDI host.

[0043] The method according to the invention allows for the collection of usage statistics for the operating software BS. For this purpose, the operating software BS comprises a logic element LE, which records usage data ND of the operating software BS over a predefined period or continuously. The logic element LE can also be a standalone software program that is hierarchically arranged outside of the operating software BS. The usage data ND is broadly divided into two categories:

[0044] Firstly, communication data is collected. This means that it records how the operating software is used to communicate with field devices. For example, it records how many communication connections are established with how many field devices FG1, FG2, and / or whether there are any connection failures.

[0045] Secondly, tracking encompasses specific functionalities of the operating software. The operating software includes a wide range of functionalities. Tracking includes the number and duration of each use of these functionalities. For example, the execution of device drivers GT 1 and GT2 is recorded. Specifically, it records which device drivers GT 1 and GT2 are open, for how long, and how the performance of the operating unit BE behaves during these sessions.

[0046] The recorded usage data ND is stored on the control unit BE and can be output via a second communication interface KS2. For example, the usage data ND can be transmitted via the internet to a cloud-based platform CP. The cloud-based platform CP runs one or more software applications SA, which further process the usage data ND and thus, for example, perform an analysis of the usage data ND.

[0047] Such an analysis of the usage data (ND) allows the provider of the operating software (BS), for example, to improve the operating software based on the usage data. For instance, they can optimize the operating software by improving existing connectivity and reducing the number of unused connections. This can reduce security vulnerabilities, storage space requirements, the risk of errors, and so on.

[0048] Reference symbol list

[0049] BE control unit

[0050] BS operating software CP cloud-based platform

[0051] FG1, FG2 Field devices GT1, GT2 Device drivers KN Communication network KS1 First communication interface KS2 Second communication interface

[0052] KT Communication Driver

[0053] LE Logic Element ND Usage Data SA Software Application

Claims

Patent claims 1. Method for tracking the use of operating software (OS) which is executed on an operating unit (UU), wherein the operating unit (UU) establishes at least one communication connection with at least one field device (FG1, FG2) of the automation technology via at least one communication network (CN), in particular a fieldbus network or an Ethernet-based network, wherein the operating software (OS) is used to operate the field device (FG1, FG2), orthe field devices, wherein the operating software (OS) is a frame application or comprises a frame application, in particular an FDT frame application and / or an FDI host, and is designed to execute device and communication drivers (GT1, GT2, KT) by means of which device and communication drivers (GT1, GT2, KT) can access the field devices (FG1, FG2) and via which device and communication drivers (GT1, GT2, KT) operating functionalities of the field devices (FG1, FG2) are provided, wherein the method comprises:. Recording usage data (ND) of the operating software (BS) over a period of time, wherein the usage data includes a respective number of uses of functionalities of the operating software (BS) within the period, a usage duration of one or more of the functionalities of the operating software (BS) and / or communication data; and Storing usage data (ND) on the control unit (BE) and / or outputting usage data (ND) by the control unit (BE).

2. Method according to any of the preceding claims, wherein the functionalities include executing one or more device drivers (GT1, GT2) and / or performing a performance check of the device drivers.

3. Method according to claim 1 or 2, wherein the communication data comprises one or more of the following: Information regarding the number and / or duration of communication links established via the relevant communication networks (CN) between the operator unit (UE) and field devices (FG1, FG2) and / or other network participants, in particular gateways or edge devices; Information regarding the communication protocols used for the communication links; Information on the number of devices that can be connected to or are connected to the network; information on detected but unconnectable devices and information about the reasons for the unconnectability. Information on the topology of other network participants; Information on problems with the communication connection, in particular comprehensive connection interruptions and / or reconnections.

4. Method according to one of the preceding claims, wherein the output of the usage data (ND) comprises transmitting the usage data (ND) from the control unit (BE) to a cloud-based platform.

5. Method according to claim 4, wherein the cloud-based platform executes at least one software application (SA), wherein the software application (SA) processes the usage data (ND) and in particular creates statistics on the use of the operating software (BS) based on the processed usage data (ND).

6. Method according to one of the preceding claims, wherein the operating software (BS) anonymizes the usage data (ND) before outputting it.

7. Operating unit (BE), configured to establish at least one communication connection with at least one field device (FG1, FG2) of the automation technology via at least one communication network (KN) and configured to execute operating software (BS), wherein the operating software (BS) is configured to operate the field device (FG1, FG2), or the field devices, wherein the operating software (BS) is a frame application or wherein the operating software (BS) comprises a frame application, in particular an FDT frame application or an FDI host, and is configured to execute device and communication drivers (GT1, GT2, KT) by means of which device and communication drivers (GT1, GT2, KT) can access the field devices (FG1, FG2) and via which device and communication drivers (GT1, GT2, KT) operating functionalities of the field devices (FG1, FG2) are provided.wherein the operating unit (BE) is designed to record usage data (ND) of the operating software (BS) over a period of time, wherein the usage data (ND) includes a respective number of uses of functionalities of the operating software (BS) within the period of time, a usage duration of one or more of the functionalities of the operating software (BS) and / or communication data, and wherein the operating unit (BE) is designed to store and / or output usage data (ND).

8. Control unit according to claim 7, wherein the control unit (CU) is a computer unit, in particular a laptop.

9. Control unit according to claim 7, wherein the control unit (CU) is a mobile terminal, in particular a smartphone or a tablet.

Images