METHOD FOR CAPTURING RESULTS OF AN EVALUATION, DIAGNOSIS AND / OR VERIFICATION OF AT LEAST ONE DEVICE FUNCTIONALITY OF A FIELD DEVICE

Description

[0001] The invention relates to a method for capturing the results of an evaluation, diagnosis and / or verification of at least one device functionality of a field device, wherein the field device generates at least one raw data set of report parameters containing the result of the evaluation, diagnosis, or verification as part of the evaluation or verification.

[0002] Field devices are already known from the state of the art and are used in industrial plants. They are widely employed in process automation as well as in manufacturing automation. In principle, field devices are defined as all devices used close to the process that provide or process process-relevant information. Thus, field devices are used to acquire and / or influence process variables. Measuring instruments 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.

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

[0004] In modern industrial plants, field devices are typically 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 controllers, 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). Data transmission from the higher-level unit to the field devices via the bus system is also necessary, particularly for configuring and parameterizing field devices and controlling actuators.

[0005] Mobile operating devices are frequently used to operate field devices (e.g., to configure parameters or retrieve data). These are connected to a field device either via cable (e.g., 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.

[0006] To operate the field devices, appropriate operating programs (operating tools) are required. These run either independently on the higher-level units or in the mobile operating devices (Endress+Hauser FieldCare, PACTware, AMS Fisher-Rosemount, Siemens PDM) or are 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 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 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] The device drivers offer the possibility to evaluate, diagnose, and / or verify certain device functionalities. Many modern field devices, for example, enable a self-test, such as within the framework of the "Heartbeat" (a self-test functionality implemented in the applicant's field devices) or SIL functionality. The result of these self-tests, evaluations, etc., is output by the device driver in a report. This report contains the relevant report parameters, i.e., test results, device status, etc. The report is sent directly to a printer and printed 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 signing, the report is scanned or stored physically.

[0010] Since the reports are often several pages long, scanning is a labor-intensive process that is prone to errors (poor scan quality, accidental omission of pages, etc.). Furthermore, the scanned reports are not machine-readable and consist primarily of images.

[0011] Methods are known from the prior art that provide for the use of graphical codes for the transmission of field device-related data.

[0012] DE 10 2019 134 895 A1 discloses a method for the non-interfering transmission of field device-related data between a first and a second control unit. In this process, a two-dimensional graphic code is generated, which is visualized as a sequence of several images on a display unit of the first control unit. The sequence is captured by an optical detection unit of the second control unit, and the contained data is extracted.

[0013] DE 10 2016 124 146 A1 relates to a method for commissioning or maintaining a field device in which identification information and diagnostic information are optically read via static and dynamic codes and transmitted to a cloud-based service platform.

[0014] Based on this problem, the invention aims to simplify the handling and long-term storage of such reports.

[0015] The task is solved by a method for capturing the results of an evaluation, diagnosis and / or verification of at least one device functionality of a field device, wherein the field device, within the scope of the evaluation, diagnosis, or verification, generates at least one raw data set of report parameters containing the result of the evaluation, diagnosis, or verification, comprising: a) Generating a physical report, wherein the physical report has a graphical code containing coded information, the coded information including at least the raw data set, a device identification of the field device and the date of the report, and wherein the physical report is signed by at least one person with at least one signature; characterized by the fact thatThe method further comprises the following steps: b) Capturing a digital scan of the title page of the signed report using an optical scanning unit, on which the graphic code and the at least one signature are located; c) Separating the graphic code from the scan and decoding the raw data set contained in the graphic code using a code extraction unit, and in parallel separating the at least one signature from the captured digital scan in image format using a signature extraction unit, whereby report data is generated by enriching the raw data set extracted from the decoded graphic code with field device-specific information; d) Generating a machine-readable report and / or a report in a publishable file format, in particular in a PDF format, containing the decoded information, wherein the machine-readable report contains the report data.wherein the report in the publishable file format contains the report data, wherein the report in the publishable file format contains at least one separated signature; and e) transmitting the machine-readable report and / or the report in the publishable format to a server.

[0016] Using the method according to the invention, reports are generated that are available in a machine-readable format, for example as code, or in a publishable file format, in particular PDF or XPS. The manual effort required to scan the physical, i.e., printed, report is reduced, as are potential sources of error, since only the graphic code and at least one signature need to be scanned.

[0017] The graphic code is in particular a two-dimensional code, for example a QR code, a barcode or a similarly suitable graphic code.

[0018] It may be stipulated that the final machine-readable or publishable report is only generated if a signature on the physical report has been scanned and recognized.

[0019] According to a first embodiment of the method according to the invention, the coded information comprises the raw data set of the field device's report parameters. Report data is generated by enriching the raw data set of report parameters extracted from the decoded graphical code with field device-specific information. The machine-readable report contains the report data, or the report in the publishable file format contains the report data. Thus, further field device-specific information is added to the final machine-readable or publishable report, e.g., service or maintenance information, measuring point information, application-specific information, etc., which is not present in the original report and would otherwise have to be added in a time-consuming manner.

[0020] According to a first embodiment of the method according to the invention, an operating unit reads the raw data set of report parameters from the field device, or the operating unit instructs the field device to create the raw data set of report parameters and transmit it to the operating unit, the operating unit then creating the graphical code and instructing a printer to produce the physical report. The first operating unit is, for example, an operating unit such as the "Field Xpert" distributed by the applicant, or a laptop or an (industrial) tablet. Advantageously, the first operating unit includes a framework application, in particular based on the FDT standard, which hosts at least one device driver suitable for the field device, in particular a DTM.The device driver instructs the device to create the raw data set of report parameters, for example by initiating a self-test, and performs further processing, in particular creating the graphical code and instructing the printer to create the physical report.

[0021] According to a second embodiment of the method according to the invention, the field device creates the raw data set of the report parameters, generates the graphical code, and instructs a printer, for example via Ethernet, WLAN, or Bluetooth, to produce the physical report. This process is initiated, for example, by a user. It can also be provided that the field device starts the process automatically, for example, when a specific process condition is met and / or at regular intervals.

[0022] According to a first embodiment of the method according to the invention, the field device generates the raw data set of the report parameters, the field device generates the graphic code, the field device has a display unit and visualizes the graphic code, an operating unit captures the graphic code by means of an optical detection unit, and the operating unit instructs a printer to produce the physical report. In particular, the first operating unit in the present case is a mobile device, especially a smartphone or a tablet, on which an application (app) is installed, which is configured to instruct the printer accordingly, based on the raw data set contained in the graphic code, to produce the physical report.

[0023] An advantageous embodiment of the method according to the invention provides that steps b) to e) are carried out by means of a second operating unit which includes the optical detection unit. In particular, the second operating unit in the present case is a mobile device, especially a smartphone or a tablet, on which an application (app) is installed.

[0024] An alternative embodiment of the method according to the invention is provided that step b) is carried out by means of a scanner or camera which has the optical detection unit, wherein the detected optical code and the at least one detected signature are transferred to a server and wherein the server carries out steps c) and d).

[0025] According to an advantageous embodiment of the method according to the invention, it is provided that the person makes handwritten notes on the physical report, wherein the handwritten notes are also captured like the signature and are included in the machine-readable report or the report in the publishable file format. In particular, it can be provided that the handwritten notes are recognized after capture and also made machine-readable (OCR).

[0026] According to an advantageous embodiment of the method according to the invention, the report parameters are heartbeat parameters or SIL parameters, which are generated during a diagnostic test of the field device. However, they can also be other parameters of the field device, in particular operational or application-specific parameters, or other parameters that are generated by the field device during comparable evaluation, diagnostic, and / or verification methods.

[0027] According to an advantageous further development of the method according to the invention, it is provided that the machine-readable report, or the report in the publishable format, is repeatedly created and transmitted to the server.

[0028] According to an advantageous embodiment of the method according to the invention, the server is provided that it examines the report data of the machine-readable reports for long-term changes and / or anomalies. For example, a slow drift of certain report parameters can be detected, so that the plant owner or the field device owner is alerted at an early stage to preventive or necessary (maintenance) measures.

[0029] The invention is explained in more detail with reference to the following figure. It shows Fig. 1 : a schematic representation of an embodiment of the method according to the invention.

[0030] In Fig. 1 A distinction must be made between components (in rectangles) and process steps (arrows). The process begins with field device 100.

[0031] In a first process step, report parameters of a field device 100 are queried by a first operator unit 200, or transmitted from the field device 100 to the first operator unit 200. In this case, the report parameters are generated by the field device 100 during a heartbeat self-test and provide information about the quality of various functionalities of the field device 100. Examples of field devices have been described in detail in the introductory section of this description. The first operator unit 200 is an industrial tablet on which an (FDT) frame application is installed and running. A specific device description (e.g., a DD) 210 and a device driver (e.g., a DTM) 220 are installed for the field device 100 and integrated into the (FDT) frame application.

[0032] The first operator unit 200 is connected to the field device 100 via a fieldbus, such as HART, Foundation Fieldbus, Profibus PA, but also an Ethernet-based fieldbus or a wireless fieldbus. A fieldbus master 201, which is part of the first operator unit 200, queries the report parameters from the field device 100. The queried report parameters are read by a universal parameter reading component 221 of the device driver 220. To interpret and assign the report parameters, this component accesses a device-specific parameter list 211 from the device description 210, classifies the report parameters, and combines them into a raw data set 222.

[0033] The raw data set 222 is fed to both a code generator 224 and a report formatting unit 223, both components of the device driver 220. The code generator 224 creates a graphic code, specifically a QR code, containing the raw data set 222 and passes it to the report formatting unit 223. Using a device-specific report layout 212, which is contained in the device description 210, a print layout of the report is created. This print layout is transmitted to a printer driver 202 of the first operating unit 200. The printer driver 202 instructs an external printer to produce a physical report 300 of the heartbeat self-diagnostic test of the field device 100.

[0034] The physical report 300, which contains the graphic code on the first page in addition to the printed report parameters, is checked by a service technician or a comparable operator 600 and signed after successful verification. If necessary, the physical report 200 is checked by other persons / operators who also sign it. Optionally, handwritten notes are added to the physical report 300, particularly in a designated area or field.

[0035] The signed report 300' is then scanned by a second operating unit 400. For this purpose, the second operating unit 400 has an optical capture unit 401, in particular a camera. In this case, the second operating unit 400 is a smartphone on which an app is installed, for example, the "Netilion Scanner" app published by the applicant. The app has the components described below and performs the following process steps: The optical capture unit 401 captures a digital scan 402 of the title page of the signed report 300', which contains the graphic code and at least one signature.

[0036] A code extraction unit 403 separates the graphic code from the scan 402 and decodes the raw data set 404 contained in the graphic code. The raw data set is then enriched with field device-specific information 406 to create report data 405. A machine-readable report 407 is then generated from this report data 405.

[0037] In parallel, a signature extraction unit 408 separates the at least one signature 409 in image format from the scan 408. Together with the raw data set 404, the signature 309 is transmitted to a report formatting unit, which creates report data 410 using a device-specific report layout 411. This report data 412 is converted into a report 413 by means of a document generator, which is available in a publishable format, in particular PDF or XPS.

[0038] Both types of reports 407 and 413 are transmitted by an upload component 414 via a network, for example the Internet, to a server 500, which stores both reports 407 and 413.

[0039] This process can be repeated several times at different times. As a result, Server 500 accumulates a large number of reports 407 and 413 for Field Device 100 over time. An application running on Server 500 or another device is designed to analyze at least the machine-readable Report 407 and, for example, calculate a trend for one or more of the report parameters. This allows, for instance, the detection of a slow drift in certain report parameters, enabling the plant owner or field device owner to be notified early by Server 500 of necessary preventive or maintenance measures.

[0040] The described procedure can have several alternatives: For example, the field device 100 can be configured to generate the graphic code itself and transmit it to the printer or to visualize it via a display unit. In the latter case, the graphic code is optically captured by the first or second operating unit 200, 400, and the physical report 300 is created by the printer.

[0041] It may also be provided that the second operating unit 400 does not create the machine-readable report 407, or the report in the publishable file format, but that these are created by the server 500 or another device. For this purpose, the signed report 300 is scanned by a scanner or camera. The scan 401 is then transmitted to the server 500 or to the other device. Reference symbol list

[0042] 100 Field device 200 First operator unit 201 Fieldbus master 202 Printer driver 210 Device description 211 Device-specific parameter list 212 Device-specific report layout 220 Device driver 221 Universal parameter reading component 222, 404 Raw data set 223 Report formatting unit 224 Code generator 300 Physical report 300 Signed report 400 Second operator unit 401 Optical capture unit 402 Scan 403 Code extraction unit 405, 410 Report data 406 Field device-specific information 407 Machine-readable report 408 Signature extraction unit 409 Signature 411 Device-specific report layout 412 Document generator 413 Report in publishable file format 414 Upload component 500 Server 600 Operator

Claims

1. A method for recording results of an evaluation, diagnosis and / or verification of at least one device functionality of a field device (100), wherein, within the scope of the evaluation, diagnosis or verification, the field device (100) generates at least one raw data set (222) of report parameters containing the result of the evaluation, diagnosis or verification, comprising: a) generating a physical report (300), wherein the physical report (300) comprises a graphical code having encoded information, wherein the encoded information comprises at least the raw data set (222), a device identification of the field device (100) and the date of the report, and wherein the physical report (300) is signed by at least one person with at least one signature; characterized in that the method further comprises the following steps: b) capturing a digital scan (402) of the title page of the signed report (300') by means of an optical capture unit (401), on which the graphical code and the at least one signature are located; c) separating the graphical code from the scan (402) and decoding the raw data set (404) contained in the graphical code by means of a code extraction unit (403), and, in parallel therewith, separating the at least one signature from the captured digital scan (402) in image format by means of a signature extraction unit (408), wherein report data (405, 410) are generated by enriching the raw data set (222) extracted from the decoded graphical code with field-device-specific information; d) generating a machine-readable report (407) and / or a report (413) in a publication-capable file format, in particular in a PDF format, containing the decoded information, wherein the machine-readable report (407) contains the report data (405, 410), and / or wherein the report (413) in the publication-capable file format contains the report data (405, 410), wherein the report (413) in the publication-capable file format contains the at least one separated signature; and e) transmitting the machine-readable report (407) and / or the report (413) in the publication-capable format to a server (500).

2. The method according to claim 1, wherein a first operating unit (200) reads the raw data set (222) of the report parameters from the field device (100), or wherein the first operating unit (200) instructs the field device (100) to create the raw data set (222) of the report parameters and to transmit it to the first operating unit (200), wherein the first operating unit (200) creates the graphical code and instructs a printer to generate the physical report (300).

3. The method according to claim 1, wherein the field device (100) creates the raw data set (222) of the report parameters, wherein the field device (100) creates the graphical code, and wherein the field device (100) instructs a printer to generate the physical report (300).

4. The method according to claim 1, wherein the field device (100) creates the raw data set (222) of the report parameters, wherein the field device (100) creates the graphical code, wherein the field device (100) comprises a display unit and visualizes the graphical code, wherein a first operating unit (200) captures the graphical code by means of an optical capture unit, and wherein the first operating unit (200) instructs a printer to generate the physical report (300).

5. The method according to any one of claims 1 to 4, wherein steps b) to e) are carried out by means of a second operating unit (400), which comprises the optical capture unit (401).

6. The method according to any one of claims 1 to 4, wherein step b) is carried out by means of a scanner or a camera comprising the optical capture unit (401), wherein the captured optical code and the at least one captured signature are transferred to a server, and wherein the server carries out steps c) and d).

7. The method according to any one of the preceding claims, wherein the person enters handwritten notes on the physical report (300), wherein the handwritten notes are likewise captured by means of the optical capture unit (401) and are contained in the machine-readable report (407) and / or in the report (413) in the publication-capable file format.

8. The method according to claim 7, wherein the handwritten notes are made machine-readable by means of an OCR method after capture.

9. The method according to any one of the preceding claims, wherein the report parameters are Heartbeat parameters or SIL parameters which are created in the course of a diagnostic test of the field device (100).

10. The method according to any one of the preceding claims, wherein the machine-readable report (407) and / or the report (413) in the publication-capable format is repeatedly created and transmitted to the server (500).

11. The method according to claim 10, wherein the server (500) examines the report data (405, 410) of the machine-readable reports (407) for long-term changes and / or anomalies.