Method for generating a device report for a field device, and system for generating a device report for a field device

Abstract

The invention relates to a method for generating a device report (22) for a field device (10), having the steps of: - providing a field device (10) with field device information (FI), providing a user device (20) with user information (BI), and providing a cloud server (30) with a database (31) and an analysis unit (32), wherein the database (31) comprises a user database and a device database, - connecting the user device (20) to the field device (10), - reading field device data (FD) and the field device information (FI) from the field device (10) by means of the user device (20), - connecting the user device (20) to the cloud server (30), - transmitting the field device data (FD), the field device information (FI), and the user information (BI) from the user device (20) to the cloud server (30), - analyzing the field device data (FD) by means of the analysis unit (32), - generating additional information (ZI) on the basis of the field device information (FI) and the user information (BI) using the user database and the device database of the cloud server (30), - reading analysis results and additional information (ZI) from the cloud server (30) by means of the user device (20), and - generating a device report (22) by means of the user device (20) on the basis of the analysis results and the additional information (ZI).

Description

[0001] Method for creating a device report of a field device and system for creating a device report of a field device

[0002] The invention relates to a method for creating a device report of a field device and a system for creating a device report of a field device.

[0003] Field devices used in industrial plants are already known from the state of the art. Field devices are widely used in process automation technology as well as in manufacturing automation technology. Field devices essentially refer to all devices used close to the process and that provide or process-relevant information. Field devices are used to record and / or influence process variables. Measuring devices or sensors are used to record process variables. These are used, for example, for pressure and temperature measurement, conductivity measurement, flow measurement, pH measurement, level measurement, etc. and record the corresponding process variables such as pressure, temperature, conductivity, pH value, level, flow, etc. Actuators are used to influence process variables.These include, for example, pumps or valves that can influence the flow of a fluid in a pipe or the fill level in a container. In addition to the previously mentioned measuring devices and actuators, field devices also include remote I / Os, wireless adapters, and generally 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 usually connected to higher-level units via communication networks such as fieldbuses (Profibus®, Foundation® Fieldbus, HART®, etc.). These higher-level units are usually control systems (DCS) or control units, such as a PLC (programmable logic controller) or an asset management system. The higher-level units are used, among other things, for process control, process visualization, process monitoring and for commissioning the field devices. The measured values ​​recorded by the field devices, in particular by sensors, are transmitted via the respective bus system to one (or possibly several) higher-level units. In addition, data must be transmitted from the higher-level unit to the field devices via the bus system, in particular for the configuration and parameterization of field devices and for controlling actuators.

[0006] Mobile operating devices are often used to operate field devices (e.g., parameterize or retrieve data). These are connected to a field device either wired (e.g., via a service interface) or wirelessly (e.g., via Bluetooth). Examples of operating devices include laptops, mobile devices such as smartphones or tablets, or central asset management stations.

[0007] To operate the field devices, appropriate operating programs (operating tools) are required. These programs run either independently on the higher-level units or on the mobile operating devices (Endress+Hauser FieldCare, PACTware, AMS Fisher-Rosemount, PDM Siemens) or are integrated into control center applications (Siemens PCS7, ABB Symphony, Emerson Delta V). The term "operating" includes, among other things, parameterizing the field device, updating the field device, and / or querying and visualizing process data and / or diagnostic data from the field device.

[0008] The integration of field devices into such operating programs 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 provided by the field devices. Such an operating program, into which the device descriptions or device drivers are loaded, is also referred to as a frame application.

[0009] 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. EDD drivers and FDI device packages are also available as alternatives. 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.

[0010] The device drivers offer the possibility of evaluating, diagnosing, and / or verifying specific device functionalities. Many modern field devices, for example, enable self-tests, for example, as part of the "heartbeat" (a self-test functionality or SIL functionality implemented in the applicant's field devices). The results of these self-tests, evaluations, etc., are output by the device driver in a report. This driver receives the relevant report parameters, i.e., test results, device status, etc. The report is sent directly to a printer and printed out in physical form. The report is processed, for example, by service personnel, who perform a visual inspection of the report and then sign it. After the signature has been received, the report is scanned or physically stored.

[0011] A method for creating such reports is known, for example, from DE 102021 124 249 A1. A disadvantage of this method, however, is that it is difficult to collect information that goes beyond the data stored in the field device. For example, it has not been easily possible to obtain information about whether the field device in use requires an update or whether a successor model of the field device is now available. Furthermore, it has not been easily possible to verify the legitimacy of the report creation or the identification of the user. In addition, the data read out from the field device is not currently evaluated, for example, checked for plausibility or existing sensor drift. This makes it difficult for the user to recognize possible malfunctions in the sensor or field device.

[0012] It is therefore an object of the invention to provide a method that enables the integration of additional information, which goes beyond the inherent information of a field device, into a device report, as well as the evaluation of the information read from the field device. This object is achieved according to the invention by a method for creating a device report of a field device according to claim 1.

[0013] The method according to the invention comprises:

[0014] Providing a field device with field device information, a user device with user information, a cloud server with a database and an analysis unit, wherein the database comprises a user database and a device database,

[0015] Connecting the user device to the field device,

[0016] Reading field device data and field device information from the field device by the user device,

[0017] Connecting the user device to the cloud server,

[0018] Sending the field device data, the field device information and the user information from the user device to the cloud server, analyzing the field device data by the analysis unit, creating additional information based on the field device information and the user information by the user bank and the device bank of the cloud server,

[0019] Reading analysis results and additional information from the cloud server by the user device,

[0020] Generating a device report by the user device based on the analysis results and additional information.

[0021] The method according to the invention enables a device report to be enriched with valuable additional information in a secure and efficient manner. Furthermore, it ensures that field device data can be reliably evaluated and reviewed. This allows the user to more quickly determine whether intervention is necessary or recommended.

[0022] According to one embodiment of the invention, the analysis results include information about the maintenance status.

[0023] According to one embodiment of the invention, the maintenance status indicates whether sensor drift is present in the field device and / or indicates the remaining expected service life of the field device. According to one embodiment of the invention, the additional information indicates whether a firmware update for the field device is available.

[0024] According to one embodiment of the invention, the additional information indicates whether a device successor model is available.

[0025] The above-described object is also achieved by a system for creating a device report of a field device according to claim 6.

[0026] The system according to the invention comprises: a field device with a field device communication unit and field device information, a user device with a user device communication unit and user information, a cloud server with a database of an analysis unit and an access point, wherein the user device communication unit is suitable for communicating with the field device communication unit and with the access point, wherein the user device is suitable for creating a device report for the field device.

[0027] According to one embodiment of the invention, the field device communication unit enables Bluetooth and / or WLAN communication, and the user device communication unit enables at least one internet-enabled communication as well as Bluetooth and / or WLAN communication. The invention is explained in more detail with reference to the following description of the figures. They show:

[0028] - Fig. 1 : a schematic representation of a system according to the invention,

[0029] - Fig. 2: a schematic representation of the method according to the invention.

[0030] The system 100 according to the invention shown in Figure 1 comprises a field device 10, a user device 20, and a cloud server 30. The system 100 enables the creation of a device report 22 for the field device 10. The field device 10 has field device information F1, which makes it possible to identify the field device 10 and its components. The field device 10 comprises a sensor, for example a pH sensor, a conductivity sensor, or another sensor. The field device 10 also comprises a transmitter connected to the sensor and suitable for processing the sensor data generated by the sensor. The field device 10 comprises a field device communication unit 11, for example a Bluetooth module, a WLAN module, or another communication module, such as a wired communication module suitable for communicating via HART.The field device information Fl includes, for example, a serial number of the sensor and / or the transmitter, the date the sensor was put into operation, runtime data of the sensor, a list of diagnostic events that have occurred, a date of the last self-test, information about the device type of the field device 10, information about the version of the firmware or software of the field device 10, information about the measuring point (or tag), or other data related to the sensor and / or the transmitter.

[0031] The user device 20 is, for example, a tablet, smartphone, or a PC with FieldCare software. The user device 20 has user information BI, which makes it possible to identify the user of the user device 20. Preferably, a password must be entered when starting the user device 20 to prevent an unauthorized user from using the user device 20. The user information BI includes, for example, a user number, a user name, information about the current shift of the maintenance personnel, and information about the user's customer organization. The user device 20 includes a user device communication unit 21, which enables internet-capable and / or intranet-capable communication.

[0032] The user device communication unit 21 is suitable for connecting to the first communication module of the field device 10 and to an access point 33 of the cloud server 30, whereby access point 33 is understood to mean merely a communication unit necessary to access the cloud server 30. For example, the user device communication unit 21 is a Bluetooth module, a WLAN module, a mobile radio module such as LTE or similar, or another communication module, such as a wired communication module suitable for communicating via HART. The user device communication unit 21 can also comprise multiple communication means, for example, a Bluetooth module and an LTE module. The user device 20 is suitable for creating the device report 22 for the field device 10. The device report 22 is, for example, a PDF document or an electronic document in another file format.The procedure for creating Device Report 22 is discussed in detail below.

[0033] A cloud server 30 should also be understood to mean a server on an intranet or a local PC. The cloud server 30 has a database 31 and an analysis unit 32. The database 31 comprises, in particular, a user database and a device database. Data for authenticating the user information BI is stored in the user database. Data for authenticating the field device information Fl is stored in the device database. The cloud server 30 is suitable for generating additional information ZI based on the field device information Fl, the field device data FD, the user database, and the device database with the aid of the analysis unit 32 and transmitting this additional information ZI to the user device 20. The additional information ZI includes, for example, an available firmware update or available successor models of the field device 10.Available firmware updates and / or successor models of field devices are continuously updated in the device bank of database 31, making it easy for the cloud server 30 to check, based on the field device information F1, whether a firmware update or a successor model is available for the field device 10. The additional information ZI includes, for example, information about a necessary calibration of the sensor of the field device 10 or whether sensor drift is present. The additional information ZI also includes, for example, information about the remaining expected service life of the sensor or other components of the field device 10.

[0034] The following describes the method according to the invention for creating the device report 22 of the field device 10. An exemplary embodiment of the method is shown in Figure 2. First, the system 100 described above, including the field device 10, the user device 20, and the cloud server 30, is provided. All components of the system 100 are operational. The user has activated the user device 20, i.e., logged in there, if the user device 20 has such a login function.

[0035] Subsequently, the user device 20 is connected to the field device 10 (see Figure 2, S1). The connection is established via the user device communication unit 21 and the field device communication unit 11. This is preferably a wireless connection, in particular a Bluetooth connection. As mentioned above, however, it can also be a wired connection.

[0036] The field device data FD and the field device information Fl are then read from the field device 10 by the user device 20 (see Figure 2, S2). The data readout is also represented, for example, by the arrow in Figure 1.

[0037] Next, the user device 20 is connected to the cloud server 30 (see Figure 2, S3). The connection is established using the user device communication unit 21 described above and the access point 33 of the cloud server 30. The connection is preferably a wireless internet connection via a mobile network. As mentioned above, however, it can also be a wired connection. When connecting to the cloud server 30, so-called credentials are preferably received from the cloud server 30. These can, in particular, only be retrieved from the cloud server 30 if a login process on the user device 20 was successful.

[0038] The field device data FD, the field device information Fl, and the user information BI are then sent from the user device 20 to the cloud server 30 (see Figure 2, S4). The field device information Fl is stored, for example, in the device bank of the database 31 of the cloud server 30 for later comparison purposes. The user information BI is stored in the user bank of the database 31 of the cloud server 30. The user database includes, for example, the user name, email address, company name, etc. When sending the field device data FD, the field device information Fl, and the user information BI, the credentials are preferably sent together with the field device data FD (also called raw data). Thanks to the credentials, the field device data FD can be verified on the cloud server 30 side.

[0039] The field device data FD is then analyzed by the analysis unit 32 (see Figure 2, S5). In doing so, the analysis unit 32 compares, for example, the just received field device data FD with field device data FD of the field device 10 stored in the device bank, provided that field device data for this field device has already been received in the past and loaded onto the cloud server 30. It is also possible that algorithms are used when analyzing the field device data FD which perform an analysis based on a single data set, for example, two parameters which normally have an x:y relationship to each other. Here, the algorithm checks and recognizes whether the expected relationship of the parameters matches or whether a different relationship exists. This provides information about the field device 10. When analyzing the field device data FD, it is also possible to recognize whether, for example, a measured value is close to a limit value.This makes it possible, for example, to detect whether sensor drift is present. When analyzing the field device data (FD), the field device data (FD) is also compared with anonymized field device data from the company's own or third-party field devices that are operating in comparable processes. This comparison allows, for example, an anomaly in field device 10 to be detected more quickly.

[0040] Next, additional information ZI is created based on the field device information Fl and the user information BI by the user bank and the device bank of the cloud server 30. The additional information ZI includes, for example, information about a necessary calibration of the sensor of the field device 10, or whether a sensor drift is present, information about the remaining expected service life of the sensor or other components of the field device 10, statistical information about the field device 10 or the field device type, information about available (firmware) updates, information about device successor models for the field device 10, etc. The analysis results and the additional information ZI are then read out from the cloud server 30 by the user device 20. The analysis results can also be read out separately from the additional information ZI (see Figure 2, S6, S7).The data communication again takes place between the user device communication unit 21 and the access point 33 (see double arrow in Figure 1 ).

[0041] Furthermore, a device report 22 is generated by the user device 20 based on the analysis results and the additional information ZI (see Figure 2, S8). The device report 22 includes, for example, information about the current

[0042] The condition of the field device 10, as well as whether, for example, a successor model for the field device 10 is available. The analysis results preferably include information about the maintenance status of the field device 10. The maintenance status indicates whether sensor drift is present in the field device 10 and provides information, for example, about the remaining expected service life of the field device 10.

[0043] List of reference symbols

[0044] 10 field device

[0045] 11 Field device communication unit

[0046] 20 user devices

[0047] 21 User device communication unit

[0048] 22 Device report

[0049] 30 cloud servers

[0050] 31 Database

[0051] 32 Analysis Unit

[0052] 33 access points

[0053] 100 systems

[0054] BI user information

[0055] ZI additional information

[0056] Fl field device information

[0057] FD field device data

Claims

Patent claims 1. A method for creating a device report (22) of a field device (10) comprising: - Providing a field device (10) with field device information (F1), a user device (20) with user information (BI), a cloud server (30) with a database (31) and an analysis unit (32), wherein the database (31) comprises a user database and a device database, - Connecting the user device (20) to the field device (10), - Reading field device data (FD) and field device information (Fl) from the field device (10) by the user device (20), - Connecting the user device (20) to the cloud server (30), - Sending the field device data (FD), the field device information (Fl) and the user information (BI) from the user device (20) to the cloud server (30), - analyzing the field device data (FD) by the analysis unit (32), - Creation of additional information (ZI) based on the field device information (Fl) and the user information (BI) by the user bank and the device bank of the cloud server (30), - Reading analysis results and additional information (ZI) from the cloud server (30) by the user device (20), - generating a device report (22) by the user device (20) based on the analysis results and the additional information (ZI).

2. The method according to claim 1, wherein the analysis results include information about the maintenance status.

3. The method according to claim 2, wherein the maintenance state indicates whether a sensor drift is present in the field device (10) and / or indicates the remaining expected service life of the field device (10).

4. The method according to claim 1 to 3, wherein the additional information (ZI) indicates whether an update of a firmware of the field device (10) is available.

5. Method according to one of the preceding claims, wherein the additional information (ZI) indicates whether a device successor model is available.

6. System (100) for creating a device report 22 of a field device (10), comprising: - a field device (10) with a field device communication unit (11) and field device information (Fl), - a user device (20) with a user device communication unit (21) and user information (BI), - a cloud server (30) with a database (31), an analysis unit (32), and an access point (33), wherein the user device communication unit (21) is adapted to communicate with the field device communication unit (11) and with the access point (33), wherein the user device (20) is adapted to create a device report (22) for the field device (10).

7. System (100) according to claim 6, wherein the field device communication unit (11) enables Bluetooth and / or WLAN communication, and the user device communication unit (21) enables at least one internet-enabled communication and one Bluetooth and / or WLAN communication.

Images