Monitoring device, monitoring screen verification method, and monitoring screen verification program

Abstract

To provide a monitoring device capable of verifying a monitoring screen on the basis of optional test data.SOLUTION: A monitoring device comprises: a display processing section 14 for creating and outputting data of a monitoring screen including display components corresponding to an output value by acquiring the output value from each of multiple devices; a test data output section 16 for outputting a tag corresponding to each device, a component ID of display components, and information on a test data list including an initial value of test data regarding all the devices; and a test data acquisition section 18 for acquiring an edited test data list including edited test data that are results of editing of test data of a test data list. The display processing section 14 creates data of a monitoring screen from edited test data corresponding to each device of an edited test data list, and outputs the created data of the monitoring screen as data of a verification monitoring screen.SELECTED DRAWING: Figure 2

Description

[Technical Field]

[0001] The present disclosure relates to a monitoring device, a monitoring screen verification method, and a monitoring screen verification program. [Background technology]

[0002] Conventionally, a technique for displaying the status of each device on a display unit in a monitoring device that remotely monitors target devices via a monitoring network has been known. Also, a method has been proposed in which test data is generated based on data acquired from each device, and a monitoring screen displayed on the display unit is verified based on the generated test data (see, for example, Patent Document 1). [Prior art documents] [Patent documents]

[0003] [Patent Document 1] Japanese Patent Application Laid-Open No. 2003-91310 Summary of the Invention [Problem to be solved by the invention]

[0004] The monitoring device disclosed in Patent Document 1 has the problem that test data is generated based on data acquired from each device, making it impossible to freely set test data for verifying the monitoring screen.

[0005] The present disclosure discloses technology for solving the above-mentioned problems, and aims to provide a monitoring device, a monitoring screen verification method, and a monitoring screen verification program that can verify a monitoring screen based on arbitrary test data. [Means for solving the problem]

[0006] The monitoring device disclosed herein includes a display processing unit that acquires output values ​​from each of a plurality of devices and creates and outputs monitoring screen data including display components corresponding to the output values; a test data output unit that outputs, for all devices, information on a test data list including tags corresponding to each device, component IDs of the display components corresponding to each device, and initial values ​​of the test data corresponding to each device; and a test data acquisition unit that acquires an edited test data list including edited test data that is the result of editing the test data in the test data list, and is characterized in that the display processing unit processes the edited test data corresponding to each device in the edited test data list as output values ​​acquired from the devices to create monitoring screen data, and outputs the created monitoring screen data as verification monitoring screen data. [Effects of the Invention]

[0007] The monitoring device of the present disclosure includes a display processing unit that acquires output values ​​from each of a plurality of devices and creates and outputs monitoring screen data including display components corresponding to the output values; a test data output unit that outputs, for all devices, information on a test data list including tags corresponding to each device, component IDs of the display components corresponding to each device, and initial values ​​of the test data corresponding to each device; and a test data acquisition unit that acquires an edited test data list including edited test data that is the result of editing the test data in the test data list.The display processing unit processes the edited test data corresponding to each device in the edited test data list as output values ​​acquired from the devices to create monitoring screen data, and outputs the created monitoring screen data as verification monitoring screen data, so that the monitoring screen can be verified based on any test data. [Brief explanation of the drawings]

[0008] [Figure 1] 1 is a diagram illustrating an example of a configuration of a remote monitoring system according to a first embodiment. [Figure 2] 1 is a diagram illustrating an example of a configuration of a monitoring device according to a first embodiment. [Figure 3] FIG. 3 is a diagram showing an example of a monitoring screen created by a display processing unit in the first embodiment. [Figure 4] 5 is a diagram showing an example of a part ID, a tag, and an output value according to the first embodiment. FIG. [Figure 5] 4 is a flowchart illustrating the operation of the remote monitoring system according to the first embodiment. [Figure 6] FIG. 3 is a diagram showing an example of a test data list according to the first embodiment. [Figure 7] FIG. 2 is a diagram showing the upper and lower limits of the output values ​​of each device together with a test data list according to the first embodiment. [Figure 8] FIG. 2 is a diagram showing an example of a monitoring screen created from information in a test data list in the first embodiment. [Figure 9] FIG. 10 is a diagram showing an example of an edited test data list according to the first embodiment. [Figure 10] FIG. 10 is a diagram showing an example of a verification monitoring screen created from information in an edited test data list in the first embodiment. [Figure 11] 10 is a flowchart illustrating the operation of the remote monitoring system according to the second embodiment. [Figure 12] FIG. 11 is a diagram showing an example of an edited test data list in the second embodiment. [Figure 13] FIG. 11 is a diagram showing an example of a verification monitoring screen created from information in an edited test data list in the second embodiment. [Figure 14] FIG. 11 is a diagram showing an example of a verification monitoring screen created from information in an edited test data list in the second embodiment. [Figure 15] 11 is a flowchart illustrating the operation of the remote monitoring system according to the third embodiment. [Figure 16] 10 is a flowchart illustrating the operation of the remote monitoring system according to the fourth embodiment. [Figure 17] FIG. 13 is a diagram showing an example of an initial editing screen in the fourth embodiment. [Figure 18] FIG. 13 is a diagram showing an example of an editing screen in the fourth embodiment. [Figure 19] FIG. 13 is a diagram showing an example of an editing screen in the fourth embodiment. [Figure 20] FIG. 13 is a diagram showing an example of an editing screen in the fourth embodiment. [Figure 21] FIG. 2 is a schematic diagram illustrating an example of a hardware configuration of a monitoring device according to an embodiment. [Figure 22] FIG. 10 is a schematic diagram illustrating another example of a hardware configuration of a monitoring device according to an embodiment. DETAILED DESCRIPTION OF THE INVENTION

[0009] A monitoring device according to an embodiment will be described in detail below with reference to the drawings. In the drawings, the same reference numerals denote the same or corresponding parts.

[0010] Embodiment 1 FIG. 1 illustrates an example of the configuration of a remote monitoring system according to the first embodiment. The remote monitoring system 100 according to the first embodiment includes a monitoring device 1, a monitoring control terminal 2, gateways 5a and 5b, and devices 6a, 6b, 6c, 6d, 6e, 6f, 6g, and 6h. Devices 6a to 6e are connected to the gateway 5a, and devices 6f to 6h are connected to the gateway 5b. The gateways 5a and 5b are connected to the monitoring device 1 via a monitoring network 4. The monitoring network 4 is, for example, the Internet, but may also be a local area network (LAN). The remote monitoring system 100 is also called a supervisory control and data acquisition (SCADA) system and monitors multiple devices that make up a facility or infrastructure. The remote monitoring system 100 performs, for example, river monitoring and road monitoring. The monitoring device 1 is configured, for example, by one or more cloud servers. A cloud server is a server built in a cloud environment that includes computer resources provided by a cloud service platform. Note that the monitoring device 1 may be a server other than a cloud server.

[0011] In the example shown in FIG. 1, the remote monitoring system 100 monitors devices 6a to 6h. In the following description, when devices 6a, 6b, 6c, 6d, 6e, 6f, 6g, and 6h are referred to without being individually distinguished, they will be referred to as devices 6. Also, FIG. 1 shows two gateways, gateway 5a and gateway 5b, with five devices 6 connected to gateway 5a and three devices 6 connected to gateway 5b, but the number of gateways and the number of devices 6 connected to one gateway are not limited to this. Device 6 may be, for example, a sensor that detects the opening / closing degree of a valve, a sensor that detects the rotation speed of a motor, a water level gauge, a flow meter, a thermometer, a voltmeter, an ammeter, or the like.

[0012] The monitoring control terminal 2 is connected to the monitoring device 1 via a general-purpose network 3. The monitoring control terminal 2 includes a terminal display unit 21, a terminal input unit 22, a device processing unit 23, and a device communication unit 24. The device communication unit 24 is connected to the monitoring device 1 via the general-purpose network 3 and transmits and receives information to and from the monitoring device 1. The general-purpose network 3 is, for example, the Internet, but may also be a LAN. The terminal input unit 22 is, for example, a keyboard, mouse, keypad, touch panel, or the like, and is operated by a user. The terminal display unit 21 is, for example, a display. Based on a user's operation on the terminal input unit 22, the device processing unit 23 transmits operation information indicating the user's operation or an input value entered by the user to the monitoring device 1 via the terminal communication unit 24 and the general-purpose network 3. The device processing unit 23 also receives information transmitted from the monitoring device 1 via the general-purpose network 3 and the terminal communication unit 24 and controls the display on the terminal display unit 21 based on the received information. The monitoring control terminal 2 may be, for example, a computer equipped with a keyboard, mouse, and display, or a tablet.

[0013] 2 is a diagram showing an example of the configuration of the monitoring device 1 according to the first embodiment. The monitoring device 1 includes a monitoring device communication unit 11, a monitoring data acquisition unit 12, a monitoring data storage unit 13, a display processing unit 14, a graphic data storage unit 15, a test data output unit 16, a test data storage unit 17, and a test data acquisition unit 18. The monitoring device communication unit 11 is connected to the general-purpose network 3 and the monitoring network 4, and transmits and receives information to and from the terminal communication unit 24 via the general-purpose network 3, and transmits and receives information to and from the gateways 5a and 5b via the monitoring network 4.

[0014] The monitoring data acquisition unit 12 acquires the output values ​​of each of the devices 6a to 6e via the gateway 5a, the monitoring network 4, and the monitoring device communication unit 11, and acquires the output values ​​of each of the devices 6f to 6h via the gateway 5b, the monitoring network 4, and the monitoring device communication unit 11, and stores the output values ​​acquired from each of the devices in the monitoring data storage unit 13. The monitoring data acquisition unit 12 also outputs the output values ​​acquired from each of the devices to the display processing unit 14. The display processing unit 14 acquires the output values ​​of each device from the monitoring data acquisition unit 12, and for each device, acquires display data of display components corresponding to the combination of each device and output value from the graphic data storage unit 15, and creates monitoring screen data.

[0015] FIG. 3 is a diagram showing an example of a monitoring screen 30 created by the display processing unit 14 in the first embodiment. FIG. 4 is a diagram showing an example of component IDs, tags, and output values ​​in the first embodiment. In FIG. 3, each display component corresponds to a device, with display component 31a corresponding to device 6a, display component 31b corresponding to device 6b, display component 31c corresponding to device 6c, display component 31d corresponding to device 6d, display component 31e corresponding to device 6e, display component 31f corresponding to device 6f, display component 31g corresponding to device 6g, and display component 31h corresponding to device 6h. In the example shown in FIGS. 3 and 4, devices 6a to 6e corresponding to display components 31a to 31e are valves including sensors that detect the degree of opening or closing, and the output value output from each of devices 6a to 6e is the degree of opening or closing of the respective valves, and is a value ranging from 0% to 100%. Devices 6f to 6h corresponding to display elements 31f to 31h are motors including sensors that detect the rotation speed, and the output value output from each of devices 6f to 6h is the rotation speed of each motor, ranging from 0 [revolutions / minute] to 1000 [revolutions / minute].

[0016] The component IDs in FIG. 4 are IDs assigned to each display component on the monitoring screen 30. In the example shown in FIGS. 3 and 4, the component ID of the display component 31a corresponding to the device 6a is 0001, the component ID of the display component 31b corresponding to the device 6b is 0002, the component ID of the display component 31c corresponding to the device 6c is 0003, the component ID of the display component 31d corresponding to the device 6d is 0004, the component ID of the display component 31e corresponding to the device 6e is 0005, the component ID of the display component 31f corresponding to the device 6f is 0006, the component ID of the display component 31g corresponding to the device 6g is 0007, and the component ID of the display component 31h corresponding to the device 6h is 0008. The correspondence between each device and its component ID is stored in the graphic data storage unit 15. The tag is a code indicating the source of the output value and is information assigned to each device. In the example shown in FIG. 4, "XXXX01-AI" indicates the device 6a, and indicates that the output value acquired from the device 6a is 0.

[0017] FIG. 3 shows an example of the monitoring screen 30 when the output values ​​acquired from each device are the values ​​shown in FIG. 4. Each display component changes its design, e.g., its shape, color, size, etc., according to the output value acquired from the corresponding device. For example, each display component changes its shape, color, or size when the output value acquired from the corresponding device exceeds a predetermined threshold. Information regarding the design of each display component for a given output value is stored in the graphic data storage unit 15. In the example shown in FIGS. 3 and 4, the display processing unit 14 acquires from the graphic data storage unit 15 graphic data of the design of the display component 31a when the output value of the device 6a is "0" and displays it on the monitoring screen 30 shown in FIG. 3. Similarly, the display processing unit 14 acquires from the graphic data storage unit 15 image data of the design of each display component when the output value of each device is the value shown in FIG. 4 and displays it on the monitoring screen 30 shown in FIG. 3.

[0018] As shown in FIG. 3 , the monitoring screen 30 may display display elements 32a, 32b, 32c, 32d, and 32e, which numerically indicate the valve opening / closing degree of each of the valves 6a to 6e. Display elements 33f, 33g, and 33h may also display text indicating whether the motors of each of the devices 6f to 6h are "centrally controlled" or "locally controlled." Display elements 34f, 34g, and 34h may also display text indicating whether the motors of each of the devices 6f to 6h are "manually" or "automatically" controlled. Furthermore, if the output values ​​of a device are limited to a certain number of values, such as "0" or "1," the monitoring screen 30 may display display elements with designs corresponding to the respective output values. If the output values ​​of a device are textual information, the monitoring screen 30 may display display elements with designs corresponding to the textual information, or display elements showing the information acquired as the output value as a string of characters. In the monitoring screen 30 of the first embodiment, the display components 31a, 31b, 31c, 31d, and 31e are described as having their design changed when the output from the corresponding device exceeds a predetermined threshold value of "80", and the display components 31f, 31g, and 31h are described as having their design changed when the output from the corresponding device exceeds a predetermined threshold value of "800".

[0019] The created data of the monitoring screen 30 is sent from the display processing unit 14 to the terminal communication unit 24 via the monitoring device communication unit 11 and the general-purpose network 3. The terminal communication unit 24 outputs the acquired data of the monitoring screen 30 to the device processing unit 23. The device processing unit 23 converts the acquired data of the monitoring screen 30 into data for display on the terminal display unit 21 and outputs it to the terminal display unit 21, and the terminal display unit 21 displays the monitoring screen 30 shown in FIG.

[0020] Next, verification of the monitoring screen using test data in the remote monitoring system 100 of the first embodiment will be described. Fig. 5 is a flowchart for explaining the operation of the remote monitoring system of the first embodiment, and is a diagram for explaining the operation of the monitoring device 1 and the monitoring control terminal 2 when verifying the monitoring screen using test data. Step S01 is a test data output step for performing test data output processing, step S02 is an initial screen output step for performing initial screen output processing, step S03 is an initial screen display step for performing initial screen display processing, step S04 is a test data editing step for performing test data editing processing, step S05 is a test data acquisition step for performing test data acquisition processing, step S06 is a verification start instruction step for performing verification start instruction processing, step S07 is a verification screen output step for performing verification screen output processing, and step S08 is a verification screen display step for performing verification screen display processing.

[0021] In step S01, the test data output unit 16 in FIG. 2 acquires, for all devices, information regarding the correspondence between tags corresponding to each device and the component IDs of the display components corresponding to each device from the graphic data storage unit 15, acquires information regarding the upper and lower limit values ​​of the output values ​​from each device from the test data storage unit 17, and creates initial values ​​of test data based on the upper and lower limit values. The created initial values ​​of test data are stored in the test data storage unit 17. Then, the test data output unit 16 creates, for all devices, a test data list including tags corresponding to each device, component IDs of the display components corresponding to each device, and initial values ​​of test data corresponding to each device, and outputs information about the created test data list to the monitoring device communication unit 11 and the display processing unit 14. The monitoring device communication unit 11 sends the acquired information about the test data list to the terminal communication unit 24 via the general-purpose network 3. When the processing of step S01 is completed, the process proceeds to step S02.

[0022] FIG. 6 is a diagram showing an example of a test data list. For all devices from device 6a to device 6h, the test data list includes tags corresponding to each device, component IDs of display components corresponding to each device, and initial values ​​of test data corresponding to each device. In the example shown in FIG. 6, the initial values ​​of the test data are shown in the column labeled "First Test Data." Here, the initial values ​​of the test data are calculated from the upper and lower limits of the output value of the corresponding device. The test data output unit 16 outputs the information of the test data list as a file displaying tabular data as shown in FIG. 6, for example. FIG. 7 is a diagram showing the test data list along with the upper and lower limits of the output value of each device. The initial values ​​of the test data for each device are calculated from the upper and lower limits of the output of each device, for example, the average value of the upper and lower limits of the output of each device. For example, the lower limit of the output of device 6a indicated by the tag "XXXX01-AI" is "0" and the upper limit is "100." Therefore, the initial value of the test data, which is the average value of the upper and lower limits, is "50." The upper and lower limits of the output of each device are assumed to be stored in the test data storage unit 17 as predetermined values.

[0023] The initial value of the test data may be an attribute initial value, which is a value selected from the values ​​output from each device. For example, if the output value output from a device is "0" or "1", "0" may be stored in the test data storage unit 17 as the attribute initial value. For example, if the output values ​​output from a device are character information and one of the output character information is a blank character (space), character information indicating the blank character may be stored in the test data storage unit 17 as the attribute initial value. If the output value output from a device is character information, the attribute initial value may be a blank (null character), which is a character with a length of zero.

[0024] In step S02, the display processing unit 14 acquires information about the test data list from the test data output unit 16, processes the initial values ​​of the test data in the test data list as output values ​​acquired from each device, creates a monitoring screen, and outputs the created monitoring screen data to the monitoring device communication unit 11 as data for the initial screen. FIG. 8 is a diagram showing an example of an initial screen 40, which is a monitoring screen created from the information about the test data list shown in FIG. 6. The initial screen 40 in FIG. 8 is created by processing the initial values ​​of the test data in FIG. 6 as output values ​​from the devices indicated by the respective tags, and the number displayed in display components 32a to 32e is "50." The initial screen may also include a verification start / end button 35 for instructing the start and end of verification. The data of the initial screen 40 created in this manner is output to the monitoring device communication unit 11, which then transmits the data of the initial screen 40 to the terminal communication unit 24 via the general-purpose network 3. After the processing in step S02 is completed, the process proceeds to step S03.

[0025] In step S03, the device communication unit 24 outputs the acquired data of the initial screen 40 to the device processing unit 23, the device processing unit 23 converts the acquired data of the initial screen 40 into data to be displayed on the terminal display unit 21, and outputs it to the terminal display unit 21, and the terminal display unit 21 displays the initial screen 40. For example, the initial screen 40 of the monitoring screen shown in Fig. 8 is displayed on the terminal display unit 21. When the processing of step S03 is completed, the process proceeds to step S04.

[0026] In step S04, the terminal communication unit 24 outputs the acquired information of the test data list to the terminal processing unit 23, the device processing unit 23 converts the acquired information of the test data list into tabular data as shown in Figure 6 and outputs it to the terminal display unit 21, and the terminal display unit 21 displays the information of the test data list in tabular format.

[0027] The terminal display unit 21 displays the initial screen 40 in step S03 and displays the information of the test data list in table form in step S04, but the initial screen 40 and the table of the test data list may be switched and displayed according to instructions input from the terminal input unit 22, or the initial screen 40 and the table of the test data list may be displayed in different display windows. By checking both the information of the test data list and the initial screen 40 of the monitoring screen, the user can confirm what kind of monitoring screen will be created from the information of the test data list.

[0028] The terminal input unit 22 acquires information on which test data has been selected from the tabular data shown in FIG. 6 and transmits it to the device processing unit 23. The device processing unit 23 then accepts new values ​​for the selected test data and transmits them to the device processing unit 23. Based on the acquired information and values, the device processing unit 23 edits the test data in the test data list, creates an edited test data list, and transmits the edited test data list to the monitoring device communication unit 11 via the device communication unit 24 and the general-purpose network 3. For example, if the terminal input unit 22 is a mouse and keyboard, when tabular data such as that shown in FIG. 6 is displayed on the terminal display unit 21, the user may select one piece of test data with the mouse and input a new value for the selected test data from the keyboard. A value for the test data may be added in response to an instruction from the terminal input unit 22. FIG. 9 is a diagram showing an example of an edited test data list, with the edited test data listed in the "First Test Data" column. The edited test data list is the result of editing the test data in the test data list. In the example shown in Fig. 9, the test data in the test data list shown in Fig. 6 has been edited, and the test data for the "first test data" with component IDs 0001, 0006, and 0008 has been changed. The device processing unit 23 outputs, for example, information on the edited test data list as a file showing data in a tabular format as shown in Fig. 9. When the processing of step S04 is completed, the process proceeds to step S05.

[0029] In step S05, the monitoring device communication unit 11 outputs the acquired information of the edited test data list to the test data acquisition unit 18, and the test data acquisition unit 18 acquires the information of the edited test data list output by the monitoring device communication unit 11. The test data acquisition unit 18 acquires the information of the edited test data list as a file showing data in a tabular format as shown in Fig. 9, for example. The test data acquisition unit 18 stores the acquired information of the edited test data list in the test data storage unit 17 and outputs the information of the edited test data list to the display processing unit 14. When the processing of step S05 is completed, the process proceeds to step S06.

[0030] In step S06, when the device processing unit 23 acquires from the terminal input unit 22 information that the verification start / end button 35 has been selected or pressed on the initial screen 40 shown in Fig. 8, the device processing unit 23 sends verification start instruction information to the monitoring device communication unit 11 via the terminal communication unit 24 and the general-purpose network 3. The monitoring device communication unit 11 outputs the acquired verification start instruction information to the display processing unit 14. When the processing of step S06 ends, the process proceeds to step S07.

[0031] In step S07, the display processing unit 14, which has acquired the verification start instruction information, processes the edited test data corresponding to each device in the acquired edited test data list as output values ​​acquired from the device to create a monitoring screen, and outputs the created monitoring screen data to the monitoring device communication unit 11 as verification monitoring screen data. FIG. 10 is a diagram showing an example of a verification monitoring screen 50 created from the information in the edited test data list shown in FIG. 9. The verification monitoring screen 50 in FIG. 10 was created by processing the edited test data shown in the "First Test Data Item" column in FIG. 9 as output values ​​from the devices indicated by the respective tags. In the verification monitoring screen 50 in FIG. 10, the value of the edited test data for component ID "0008" in the edited test data list shown in FIG. 9 is "999," which exceeds the predetermined threshold value of "800." Therefore, the design of the display component 31h has been changed and hatched. The data of the verification monitoring screen 50 created in this manner is output to the monitoring device communication unit 11, which then sends the data of the verification monitoring screen 50 to the terminal communication unit 24 via the general-purpose network 3. When the processing of step S07 is completed, the process proceeds to step S08.

[0032] In step S08, the terminal communication unit 24 outputs the acquired data of the verification monitoring screen 50 to the device processing unit 23, the device processing unit 23 converts the acquired data of the verification monitoring screen 50 into data to be displayed on the terminal display unit 21, and outputs the converted data to the terminal display unit 21, and the terminal display unit 21 displays the verification monitoring screen 50. For example, the verification monitoring screen 50 shown in FIG. 10 is displayed on the terminal display unit 21, and the verification of the monitoring screen using the test data is completed. In step S03, the device processing unit 23 of the monitoring control terminal 2 saves the data of the initial screen 40, and when information that the verification start / end button 35 has been selected or pressed is acquired from the terminal input unit 22 while the verification monitoring screen 50 of FIG. 10 is displayed on the terminal display unit 21 in step S08, the initial screen 40 shown in FIG. 8 may be displayed on the terminal display unit 21.

[0033] In step S07, if the value of the edited test data corresponding to any device in the acquired edited test data list is greater than the upper limit of the output value from the corresponding device or less than the lower limit of the output value from the corresponding device, the display processing unit 14 may display an error message on the verification monitoring screen 50 indicating that the value of the edited test data exceeds the range of the output value from the corresponding device, or may change the design of the display component indicating the corresponding device to indicate that the value of the edited test data exceeds the range of the output value from the corresponding device.

[0034] As described above, the monitoring device 1 according to embodiment 1 comprises a display processing unit 14 that acquires output values ​​from each of a plurality of devices and creates and outputs data for the monitoring screen 30 including display components corresponding to the output values; a test data output unit 16 that outputs, for all devices, information on a test data list including tags corresponding to each device, component IDs of the display components corresponding to each device, and initial values ​​of the test data corresponding to each device; and a test data acquisition unit 18 that acquires an edited test data list including edited test data that is the result of editing the test data in the test data list.The display processing unit 14 processes the edited test data corresponding to each device in the edited test data list as output values ​​acquired from the devices and creates and outputs data for the verification monitoring screen 50, so that the monitoring screen can be verified based on any test data.

[0035] Embodiment 2 In the second embodiment, the configuration of the remote monitoring system is the same as that of the remote monitoring system according to the first embodiment shown in Figures 1 and 2, but the processing content is different. Figure 11 is a flowchart for explaining the operation of the remote monitoring system according to the second embodiment. Comparing the flowchart shown in Figure 11 with the flowchart according to the first embodiment shown in Figure 5, step S04 has been changed to step S04a, step S07 has been changed to step S07a, step S08 has been changed to step S08a, and step S09 has been added, with the other steps remaining the same. Step S09 is an additional test data confirmation step that performs additional test data confirmation processing.

[0036] In step S04a, the device processing unit 23 adds additional test data as new test data to the test data list based on the information and values ​​acquired from the terminal input unit 22, thereby creating data in the edited test data list. Figure 12 is a diagram showing an example of the edited test data list, in which the edited test data corresponding to each device is shown in the column "First Test Data Item," and the additional test data corresponding to each device is shown in the column "Second Test Data Item." The set of test data shown in the column "First Test Data Item" is the first test data set, and the set of test data shown in the column "Second Test Data Item" is the second test data set. The test data sets are made up of test data corresponding to each device and include test data for all devices. In the example shown in Figure 12, the test data in the test data list shown in Figure 6 has been edited, and the test data in the "First Test Data" column with component IDs 0001, 0006, and 0008 in the edited test data has been changed. Additional test data, in which the data in the "First Test Data" column with component IDs 005 and 0006 has been further changed, has been added to the "Second Test Data" column. Figure 12 shows an example of an edited test data list to which one set of additional test data has been added. The edited test data list includes one test data set consisting of edited test data and one test data set consisting of additional test data corresponding to all devices. However, it is sufficient for the edited test data list to include one or more test data sets consisting of additional test data corresponding to all devices. Therefore, the edited test data list includes two or more test data sets.

[0037] In step S07a, the display processing unit 14, having acquired the verification start instruction information, processes the edited test data corresponding to each device in the acquired edited test data list as output values ​​acquired from the device to create a monitoring screen, outputs the created monitoring screen data to the monitoring device communication unit 11 as data for a verification monitoring screen, and then proceeds to step S08a. FIG. 13 is a diagram showing an example of a verification monitoring screen 50a created from the information in the edited test data list shown in FIG. 12. The verification monitoring screen 50a was created by processing the edited test data shown in the "First Test Data" column in FIG. 12 as output values ​​from the devices indicated by the respective tags, i.e., it was created from the information for the first test data set. In the verification monitoring screen 50a in FIG. 13, the value of the edited test data for component ID "0008" in the edited test data list shown in FIG. 12 is "999," which exceeds the predetermined threshold value of "800." Therefore, the design of the display component 31h has been changed and hatched. Also, on the verification monitoring screen 50a of FIG. 13, "01" may be displayed in the test number display window 37 to indicate that it was created using the first test data set in the edited test data list shown in FIG. 12.

[0038] In step S08a, device communication unit 24 outputs the acquired data of verification monitoring screen 50a shown in Fig. 13 to device processing unit 23, and device processing unit 23 converts the acquired data of verification monitoring screen 50a shown in Fig. 13 into data to be displayed on terminal display unit 21 and outputs the data to terminal display unit 21. Verification monitoring screen 50a created using the first test data set shown in Fig. 13 is displayed on terminal display unit 21.

[0039] In step S09, the display processing unit 14 checks whether there is any additional test data in the acquired edited test data list for which a verification monitoring screen has not been created, and if there is any additional test data for which a verification monitoring screen has not been created, proceeds to step S07a, and if there is no additional test data for which a verification monitoring screen has not been created, terminates the processing.

[0040] In step S07a from the second time onward, the acquired display processing unit 14 processes the additional test data corresponding to each device in the acquired edited test data list, for which no monitoring screen has been created, as output values ​​acquired from the device to create a monitoring screen, outputs the data of the created monitoring screen to the monitoring device communication unit 11 as data of a verification monitoring screen, and proceeds to step S08a. In step S07a for the second time, for example, the display processing unit 14 checks the columns in which test data is shown in the edited test data list shown in Fig. 12 in order from left to right, and since a monitoring screen has not been created for the additional test data shown in the column of "Second Test Data" in the edited test data list shown in Fig. 12, the display processing unit 14 processes the additional test data shown in the column of "Second Test Data" as output values ​​acquired from the device to create a monitoring screen, and outputs the data of the created monitoring screen to the monitoring device communication unit 11 as data of a verification monitoring screen.

[0041] Fig. 14 is a diagram showing an example of a verification monitoring screen 50b created from the information in the edited test data list shown in Fig. 12, and was created by processing the edited test data shown in the "Second Test Data" column in Fig. 12 as output values ​​from the devices indicated by the respective tags. Compared to the verification monitoring screen 50a in Fig. 13, the verification monitoring screen 50b in Fig. 14 has the following characteristics: the value of the additional test data for component ID "0005" in the edited test data list shown in Fig. 12 is "90," which exceeds the predetermined threshold value of "80," so the design of the display component 31e has been changed and hatched; and the value of the additional test data for component ID "0006" in the edited test data list shown in Fig. 12 is "900," which exceeds the predetermined threshold value of "800," so the design of the display component 31f has also been changed and hatched. Also, on the verification monitoring screen 50b of FIG. 14, "02" may be displayed in the test number display window 37 to indicate that the test data was created using additional test data, which is the second test data set in the edited test data list shown in FIG. 12.

[0042] In the second step S08a, the device communication unit 24 outputs the acquired data of the verification monitoring screen 50b shown in Fig. 14 to the device processing unit 23, and the device processing unit 23 converts the acquired data of the verification monitoring screen 50b shown in Fig. 14 into data to be displayed on the terminal display unit 21 and outputs the data to the terminal display unit 21. The terminal display unit 21 displays the verification monitoring screen 50b created using the second test data set shown in Fig. 14.

[0043] In the second step S09, since there is no additional test data for which a verification monitor screen has not been created in the edited test data list shown in FIG. 12, the process ends.

[0044] The verification monitoring screens shown in FIGS. 13 and 14 may display a display interval display window 36 that displays the display interval. The display interval may be preset to, for example, "1 second" and stored in the test data storage unit 17. The display processing unit 14 acquires information about the display interval from the test data storage unit 17. In step S07a from the second time onward, the display processing unit 14 may create a monitoring screen after the display interval of "1 second" has elapsed and output data of the created monitoring screen to the monitoring device communication unit 11 as data for the verification monitoring screen. The display processing unit 14 may output verification monitoring screens created from information on each test data set in sequence at a predetermined display interval. As a result, the terminal display unit 21 displays the verification monitoring screen 50a created using the first test data set shown in FIG. 13, and after the display interval of "1 second" has elapsed, the verification monitoring screen 50b created using the second test data set shown in FIG. 14 is displayed.

[0045] The verification monitoring screens shown in FIGS. 13 and 14 may display a pause button 38 that instructs the user to pause the verification monitoring screen. For example, when display processing unit 14 initially outputs the data for the verification monitoring screen shown in FIG. 13 and verification monitoring screen 50a shown in FIG. 13 is displayed on terminal display unit 21, if device processing unit 23 receives from terminal input unit 22 information that pause button 38 on verification monitoring screen 50a has been selected or pressed, device processing unit 23 transmits pause command information to monitoring device communication unit 11 via device processing unit 23, terminal communication unit 24, and general-purpose network 3. When display processing unit 14 receives the pause command information from monitoring device communication unit 11, it may temporarily stop the process of outputting the verification monitoring screen data and not create or output verification monitoring screen 50b created using the second test data set shown in FIG. 14. In this case, the display of verification monitoring screen 50a shown in FIG. 13 on terminal display unit 21 is maintained. When the display processing unit 14 stops processing and the display of the verification monitoring screen 50a shown in Figure 13 on the terminal display unit 21 is maintained, and the device processing unit 23 obtains information from the terminal input unit 22 that the pause button 38 on the verification monitoring screen 50a has been selected or pressed, the device processing unit 23 transmits pause release command information to the monitoring device communication unit 11 via the device processing unit 23, the terminal communication unit 24 and the general-purpose network 3, and the display processing unit 14 may resume processing when it obtains the pause release command information from the monitoring device communication unit 11.

[0046] 13 on the terminal display unit 21, when the user selects one number to be verified from among a plurality of test data sets and inputs information on the verification desired number, which is a number indicating the test data set to be verified, into the test number display window 37 of the verification monitoring screen 50a from the terminal input unit 22, the device processing unit 23 acquires the information on the verification desired number from the terminal input unit 22 and transmits the information on the verification desired number to the monitoring device communication unit 11 through the device processing unit 23, the terminal communication unit 24, the general-purpose network 3, and the monitoring device communication unit 11. The monitoring device communication unit 11 outputs the information on the verification desired number to the display processing unit 14, and when the display processing unit 14 acquires the information on the verification desired number, the display processing unit 14 processes the test data of the test data set indicated by the verification desired number as output values ​​from the devices indicated by the respective tags to create a monitoring screen, and may output the data of the created monitoring screen as data for the verification monitoring screen. For example, when "2" is acquired as the desired verification number, the edited test data shown in the "Second Test Data" column in Figure 12 is processed as the output value from the device indicated by each tag to create a monitoring screen, and the data of the created monitoring screen shown in Figure 14 is output as data for the verification monitoring screen.

[0047] By the above process, it is possible to set a plurality of test data sets, and to check the verification monitor screen for each test data set.

[0048] Embodiment 3 In the third embodiment, the configuration of the remote monitoring system is the same as that of the remote monitoring systems according to the first and second embodiments shown in FIGS. 1 and 2, but the processing content is different. FIG. 15 is a flowchart for explaining the operation of the remote monitoring system in the third embodiment. Comparing the flowchart shown in FIG. 15 with the flowchart of the first embodiment shown in FIG. 5, step S04 has been changed to step S04a, step S07 has been changed to step S07b, and step S08 has been changed to step S08b, with the other steps remaining the same. Step S04a in FIG. 15 is the same as step S04a in the flowchart of the second embodiment shown in FIG. 11, and the processing content is also the same as step S04a in the second embodiment.

[0049] In step S07b, the display processing unit 14 collectively outputs the data of the two verification monitoring screens shown in Figures 13 and 14. Furthermore, the display processing unit 14 sends the display interval information acquired from the test data storage unit 17 to the terminal communication unit 24 via the monitoring device communication unit 11 and the general-purpose network.

[0050] In step S08a, device processing unit 23 collectively acquires data for the two verification monitoring screens shown in Figures 13 and 14. Furthermore, device processing unit 23 acquires display interval information from device communication unit 24. Device processing unit 23 outputs data for verification monitoring screen 50a created using the first test data set shown in Figure 13 to terminal display unit 21, verification monitoring screen 50a of Figure 13 is displayed on terminal display unit 21, and after the display interval of "1 second" has elapsed, device processing unit 23 outputs data for verification monitoring screen 50b created using the second test data set shown in Figure 14 to terminal display unit 21, and verification monitoring screen 50b of Figure 14 is displayed on terminal display unit 21. When the verification monitoring screen 50a shown in Figure 13 is displayed on the terminal display unit 21 and the device processing unit 23 obtains information from the terminal input unit 22 that the pause button 38 on the verification monitoring screen 50a has been selected or pressed, the device processing unit 23 may maintain the display of the verification monitoring screen 50a shown in Figure 13 on the terminal display unit 21 without outputting the data of the verification monitoring screen 50b shown in Figure 14 to the terminal display unit.

[0051] Embodiment 4 In the fourth embodiment, the configuration of the remote monitoring system is the same as that of the remote monitoring systems according to the first and second embodiments shown in FIGS. 1 and 2, but the processing content is different. FIG. 16 is a flowchart for explaining the operation of the remote monitoring system according to the fourth embodiment. Comparing the flowchart shown in FIG. 16 with the flowchart according to the second embodiment shown in FIG. 11, steps S10 to S17 have been added, but the other steps are the same. Step S10 is a pause determination step that performs pause determination processing, step S11 is an edit screen output step that performs edit screen output processing, step S12 is an edit screen display step that performs edit screen display processing, step S13 is a test data re-editing step that performs test data re-editing processing, step S14 is an edit data acquisition step that performs edit data acquisition processing, step S15 is an edit screen output step that performs edit screen output processing, step S16 is an edit screen display step that performs edit screen display processing, and step S17 is a verification start determination step that performs verification start determination processing.

[0052] When the device processing unit 23 acquires information from the terminal input unit 22 that the pause button 38 on the verification monitoring screen has been selected or pressed, the device processing unit 23 transmits pause command information to the display processing unit 14 via the device processing unit 23, the terminal communication unit 24, the general-purpose network 3, and the monitoring device communication unit 11. In step S10, the display processing unit 14 determines whether or not the pause command information has been acquired, and if the pause command information has been acquired, it determines that a pause has been instructed, and proceeds to step S11. If the display processing unit 14 has not acquired the pause command information, it proceeds to step S09.

[0053] In step S11, the display processing unit 14 creates a monitoring screen to which the edited test data list displayed on the verification monitoring screen output immediately before acquiring the pause command information has been added, outputs the created monitoring screen as data for an initial editing screen, and sends it to the terminal communication unit 24 via the monitoring device communication unit 11 and the general-purpose network 3, and proceeds to step S12. In step S12, the terminal communication unit 24 outputs the acquired data for the initial editing screen to the device processing unit 23, which converts the acquired data for the initial editing screen into data for display on the terminal display unit 21 and outputs it to the terminal display unit 21, and the terminal display unit 21 displays the initial editing screen. FIG. 17 is a diagram showing an example of an initial editing screen 60, which is created by the display processing unit 14 when the pause button 38 is selected or pressed while the verification monitoring screen 50a shown in FIG. 13 is displayed on the terminal display unit 21. The initial editing screen 60 of Fig. 17 includes the information shown on the verification monitoring screen 50a of Fig. 13 as well as the information of the test data list shown in Fig. 12, and the information of the test data list shown in Fig. 12 is displayed in the test data display window 39. This allows the values ​​of the test data in the test data list and the monitoring screen created from the information of the test data list to be confirmed on a single screen. When the processing of step S12 is completed, the process proceeds to step S13.

[0054] In step S13, the terminal input unit 22 acquires information about which test data was selected in the test data display window 39 on the initial editing screen 60 of FIG. 17 and sends it to the monitoring device communication unit 11 via the device processing unit 23, the terminal communication unit 24, and the general-purpose network 3. The terminal input unit 22 transmits information about which test data of which component ID was selected. For example, if test data "30" is selected on the initial editing screen 60 of FIG. 17, the test data of the "first test data" with the component ID "0001" is set as the selected test data, and "0001" is transmitted as the selected component ID corresponding to the selected test data, and "1" is transmitted as information about the selected test data set, which is the test data set that includes the selected test data. If a new value is input for the selected test data from the terminal input unit 22, the input value is transmitted to the device processing unit 23. For example, if a new value of "20" is input to the selected test data, the input value may be sent as input test data, together with information on the selected component ID and the selected test data set, to the monitoring device communication unit 11 via the terminal processing unit 23, the terminal communication unit 24, and the general-purpose network 3. When the processing of step S13 is completed, the process proceeds to step S14.

[0055] In step S14, the display processing unit 14 acquires information on the selected component ID and the selected test data set from the monitoring device communication unit 11. If the monitoring device communication unit 11 has acquired the value of the input test data, the display processing unit 14 acquires the value of the input test data. When the processing of step S14 is completed, the process proceeds to step S15.

[0056] In step S15, the display processing unit 14 highlights the design of the display component indicated by the selected component ID on the initial editing screen created in step S11, creates an editing screen in which the design of the position of the test data indicated by the selected component ID and the information of the selected test data set is changed in the test data display window 39 displaying the edited test data list, and outputs the data of the created editing screen to the monitoring device communication unit 11 and the terminal communication unit 24 via the general-purpose network 3. FIG. 18 is a diagram showing an example of an editing screen 61 created in step S15. In the editing screen 61 shown in FIG. 18, the design of the display component 31a whose component ID is "0001" shown as the selected component ID is highlighted and shown with a thick line, and the design of the square marked "30" whose selected component ID is "0001" and whose selected test data set is "1" is highlighted and shown with a thick line. When the display processing unit 14 acquires the information on the input test data, the display processing unit 14 creates a new editing screen in which the values ​​of the test data in the test data display window 39 indicated by the information on the selected component ID and the selected test data set on the editing screen 61 are rewritten with the values ​​of the input test data, and outputs the data of the created editing screen to the monitoring device communication unit 11 and the terminal communication unit 24 via the general-purpose network 3. When the display processing unit 14 acquires the information on the input test data, the display processing unit 14 rewrites the values ​​of the test data indicated by the information on the selected component ID and the selected test data set in the edited test data list with the values ​​of the input test data, to create a new edited test data list, and stores the information of the created edited test data list in the test data storage unit 17 via the test data acquisition unit 18. FIG. 19 is a diagram showing an example of the editing screen 61a created in step S15. Compared to the editing screen 61 shown in FIG. 18, the value of the test data for which the selected component ID is “0001” and the selected test data set is “1” has been rewritten to “20,” which is the value of the input test data.

[0057] Furthermore, when the display processing unit 14 acquires the information on the selected component ID, the selected test data set, and the input test data, the display processing unit 14 may create an editing screen including display components from the test data of the test data set indicated by the selected test data set in a new edited test data list in which the values ​​of the test data indicated by the information on the selected component ID and the selected test data set in the edited test data list have been rewritten with the values ​​of the input test data, change the design of the display component indicated by the selected component ID to a highlighted display, create an editing screen in which the design of the position of the test data indicated by the information on the selected component ID and the selected test data set in the test data display window 39 in which the edited test data list is displayed as a list has been changed, and output the data of the created editing screen. Figure 20 is a diagram showing an example of the editing screen 61b created in step S15, and shows the editing screen when "0004" is acquired as the selected component ID, "2" is acquired as the selected test data set, and "90" is acquired as the input test data. 17, the display components have been changed to correspond to the information of the test data set shown in the column "Second Test Data," and the value of the test data having a selected component ID of "0004" and a selected test data set of "2" has been rewritten to "90," which is the value of the input test data. Furthermore, the design of the display component 31d having a component ID of "0004" shown as the selected component ID has been highlighted and shown with a thick line, and the design of the square showing "90" having a selected component ID of "0004" and a selected test data set of "2" has been highlighted and shown with a thick line. When the processing of step S15 is completed, the process proceeds to step S16.

[0058] In step S16, the device communication unit 24 outputs the acquired editing screen data to the device processing unit 23, the device processing unit 23 converts the acquired editing screen data into data for display on the terminal display unit 21, and outputs the converted data to the terminal display unit 21, and the terminal display unit 21 displays the editing screen. The terminal display unit 21 displays, for example, an editing screen shown in FIG. 18, FIG. 19, or FIG. 20. By displaying the editing screen 61 shown in FIG. 18 on the terminal display unit 21, the user can confirm which test data he or she has selected for editing and can further confirm which display component the selected test data is for. By displaying the editing screen 61a shown in FIG. 19 on the terminal display unit 21, the user can confirm which test data he or she has selected for editing and can confirm which display component the selected test data is for, as well as the value of the input test data he or she has entered. 20 is displayed on the terminal display unit 21, the user can confirm which test data he / she has selected for editing, can confirm which display component the selected test data is for, can confirm the value of the input test data he / she has input, and can confirm the monitoring screen reflecting the value of the input test data he / she has input. When the processing of step S16 is completed, the process proceeds to step S17.

[0059] In step S17, the device processing unit 23 determines whether information indicating that the verification start / end button 35 on the editing screen has been selected or pressed has been acquired from the terminal input unit 22, and if information indicating that the verification start / end button 35 has been selected or pressed has been acquired and an instruction to start verification has been issued, the device processing unit 23 sends information indicating the verification start instruction to the monitoring device communication unit 11 via the terminal communication unit 24 and the general-purpose network 3. The monitoring device communication unit 11 outputs the acquired information indicating the verification start instruction to the display processing unit 14, and the process proceeds to step S07a. If the device processing unit 23 has not acquired information indicating that the verification start / end button 35 has been selected or pressed and an instruction to start verification has not been issued, the process proceeds to step S13.

[0060] When the process proceeds from step S17 to step S07a, the display processing unit 14 creates a monitoring screen from the edited test data list rewritten with the input test data, outputs the created monitoring screen data as verification monitoring screen data, and proceeds with the process. Through the above process, the user can check the verification monitoring screen created from the edited test data list rewritten with the input test data.

[0061] FIG. 21 is a schematic diagram illustrating an example of the hardware configuration of a monitoring device 1 according to an embodiment. The monitoring data acquisition unit 12, the display processing unit 14, the test data output unit 16, and the test data acquisition unit 18 are implemented by a processor 201, such as a CPU (Central Processing Unit), that executes a program stored in a memory 202. The program stored in the memory 202 may be, for example, a program 205 stored on a recording medium 204. In other words, this program can be said to cause a computer to execute the operational procedures of the components of the monitoring device 1 and the monitoring screen verification method. The memory 202 is also used as a temporary storage device for each process executed by the processor 201. The memory 202 may be, for example, a non-volatile or volatile semiconductor memory such as RAM, ROM, flash memory, or EPROM, a magnetic disk, an optical disk, or a combination thereof. The monitoring data storage unit 13, the graphic data storage unit 15, and the test data storage unit 17 are implemented by the memory 202. The processor 201 and the memory 202 are connected to a bus 203. The monitoring device communication unit 11 is realized by a monitoring communication device 206. The monitoring communication device 206 is connected to the bus 203, and is also connected to the general-purpose network 3 and the monitoring network 4.

[0062] FIG. 22 is a schematic diagram showing another example of the hardware configuration of the monitoring device 1 according to the embodiment. In FIG. 22, the processing circuit 207 is connected to the bus 203, and the monitoring communication device 206 is connected to the bus 203 as well as to the general-purpose network 3 and the monitoring network 4. When the processing circuit 207 is dedicated hardware, it may be, for example, a single circuit, a composite circuit, a programmed processor, an ASIC (Application Specific Integrated Circuit), an FPGA (Field Programmable Gate Array), or a combination thereof. Each of the functions of the monitoring device 1 may be realized by the processing circuit 207, or the functions may be realized collectively by the processing circuit 207. Furthermore, some of the functions of the monitoring device 1 may be realized by dedicated hardware, and other parts may be realized by software or firmware.

[0063] While the present disclosure describes various exemplary embodiments, the various features, aspects, and functions described in one or more embodiments are not limited to application to a particular embodiment, but may be applied to the embodiments alone or in various combinations. Therefore, countless variations not exemplified are conceivable within the scope of the technology disclosed in this specification, including, for example, cases where at least one component is modified, added, or omitted, and cases where at least one component is extracted and combined with components of another embodiment.

[0064] The above describes in detail preferred embodiments, but the present invention is not limited to the above-described embodiments, and various modifications and substitutions can be made to the above-described embodiments without departing from the scope of the claims.

[0065] Various aspects of the present disclosure are summarized below as appendices.

[0066] (Appendix 1) a display processing unit that acquires output values ​​from each of a plurality of devices, creates monitoring screen data including display components corresponding to the output values, and outputs the data; a test data output unit that outputs, for all of the devices, information on a test data list including tags corresponding to the respective devices, component IDs of the display components corresponding to the respective devices, and initial values ​​of test data corresponding to the respective devices; a test data acquisition unit that acquires an edited test data list including edited test data that is a result of editing the test data in the test data list, The display processing unit processes the edited test data corresponding to each device in the edited test data list as the output value obtained from the device to create data for the monitoring screen, and outputs the created data for the monitoring screen as data for a verification monitoring screen. (Appendix 2) The monitoring device according to claim 1, wherein the initial value of the test data is determined from an upper limit value and a lower limit value of the output value of the corresponding device. (Appendix 3) The monitoring device according to claim 2, wherein the initial value of the test data is an average value of the upper limit and the lower limit of the output value of the corresponding device. (Appendix 4) The monitoring device described in Appendix 2 or 3, characterized in that the display processing unit outputs data on the verification monitoring screen including an error message when the value of the edited test data is greater than the upper limit value of the output value of the corresponding device or less than the lower limit value of the output value of the corresponding device. (Appendix 5) The monitoring device according to claim 1, wherein the initial value of the test data is an attribute initial value selected from values ​​output by the corresponding device. (Appendix 6) the test data output unit outputs the test data list as a table-format file; 6. The monitoring device according to claim 1, wherein the test data acquisition unit acquires the edited test data list as a table-format file. (Appendix 7) the edited test data list includes one test data set including the edited test data, which is made up of test data corresponding to each of the devices, and one or more test data sets including additional test data corresponding to all of the devices; The monitoring device according to any one of appendices 1 to 6, wherein the display processing unit outputs the verification monitoring screen created from information on each of the test data sets. (Appendix 8) The monitoring device described in Appendix 7, characterized in that the display processing unit outputs the verification monitoring screen created from the information of each of the test data sets in sequence at a predetermined display interval. (Appendix 9) The monitoring device described in Appendix 7 is characterized in that, when the display processing unit obtains a verification request number indicating one of the test data sets, it creates and outputs the verification monitoring screen from the test data of the test data set indicated by the verification request number. (Appendix 10) The monitoring device described in Appendix 8 is characterized in that, when the display processing unit acquires pause command information, it creates data for an initial editing screen to which the edited test data list displayed on the verification monitoring screen output immediately before acquiring the pause command information has been added, and outputs the data for the initial editing screen. (Appendix 11) The monitoring device described in Appendix 10 is characterized in that, after outputting the data of the initial editing screen, when the display processing unit acquires information on a selected component ID, which is the component ID corresponding to selected test data, which is the test data selected in the edited test data list, and information on a selected test data set indicating the test data set including the selected test data, it changes the design of the display component indicated by the selected component ID on the initial editing screen, creates an editing screen in which the design of the position indicating the test data indicated by the selected component ID and information on the selected test data set in the edited test data list displayed in a list is changed, and outputs the data of the editing screen. (Appendix 12) The monitoring device described in Appendix 11 is characterized in that, after outputting the data of the initial editing screen, when the display processing unit acquires information on input test data that is a new value for the selected test data, it rewrites the value of the test data indicated by the selected component ID and the information on the selected test data set in the edited test data list to the value of the input test data, and creates and outputs the editing screen from the test data of the test data set indicated by the selected test data set in the rewritten edited test data list. (Appendix 13) A monitoring screen verification method for a monitoring device that acquires output values ​​from a plurality of devices and creates and displays a monitoring screen including display components corresponding to the output values, comprising: a test data output step of outputting, for all the devices, information on a test data list including tags corresponding to the respective devices, component IDs of the display components corresponding to the respective devices, and initial values ​​of test data corresponding to the respective devices; a test data acquisition step of acquiring an edited test data list including edited test data resulting from editing the test data in the test data list; a verification screen output step of processing the edited test data corresponding to each device in the edited test data list as the output value obtained from the device to create data for the monitoring screen, and outputting the created monitoring screen data as data for a verification monitoring screen. (Appendix 14) A monitoring screen verification program that causes a computer to execute the monitoring screen verification method described in Appendix 13. [Explanation of symbols]

[0067] 1 monitoring device, 2 monitoring control terminal, 3 general-purpose network, 4 monitoring network, 5a, 5b gateway, 6, 6a, 6b, 6c, 6d, 6e, 6f, 6g, 6h equipment, 11 monitoring device communication unit, 12 monitoring data acquisition unit, 13 monitoring data storage unit, 14 display processing unit, 15 graphic data storage unit, 16 test data output unit, 17 test data storage unit, 18 test data acquisition unit, 21 terminal display unit, 22 terminal input unit, 23 terminal processing unit, 24 terminal communication unit, 30 monitoring screen, 31a, 31b, 31c, 31d, 31e, 31f, 31g, 31h display components, 32a, 32b, 32c, 32d, 32e display components, 33f, 33g, 33h display components, 34f, 34g, 34h display components, 35 Verification start / end button, 36 display interval display window, 37 test number display window, 38 pause button, 39 test data display window, 40 initial screen, 50, 50a, 50b verification monitoring screen, 60 editing initial screen, 61, 61a, 61b editing screen, 100 remote monitoring system, 201 processor, 202 memory, 203 bus, 204 recording medium, 205 program, 206 monitoring communication device, 207 processing circuit.

Claims

1. a display processing unit that acquires output values ​​from each of a plurality of devices, creates monitoring screen data including display components corresponding to the output values, and outputs the data; a test data output unit that outputs, for all of the devices, information on a test data list including tags corresponding to the respective devices, component IDs of the display components corresponding to the respective devices, and initial values ​​of test data corresponding to the respective devices; a test data acquisition unit that acquires an edited test data list including edited test data that is a result of editing the test data in the test data list, The display processing unit processes the edited test data corresponding to each device in the edited test data list as the output value obtained from the device to create data for the monitoring screen, and outputs the created data for the monitoring screen as data for a verification monitoring screen.

2. The monitoring device according to claim 1 , wherein the initial value of the test data is determined from an upper limit and a lower limit of the output value of the corresponding device.

3. 3. The monitoring device according to claim 2, wherein the initial value of the test data is an average value of the upper limit and the lower limit of the output value of the corresponding device.

4. The monitoring device described in claim 2 or 3, characterized in that the display processing unit outputs data on the verification monitoring screen including an error message when the value of the edited test data is greater than the upper limit value of the output value of the corresponding device or less than the lower limit value of the output value of the corresponding device.

5. 2. The monitoring device according to claim 1, wherein the initial value of the test data is an attribute initial value selected from values ​​output by the corresponding device.

6. the test data output unit outputs the test data list as a table-format file; 4. The monitoring device according to claim 1, wherein the test data acquisition unit acquires the edited test data list as a table-format file.

7. the edited test data list includes one test data set including the edited test data, which is made up of test data corresponding to each of the devices, and one or more test data sets including additional test data corresponding to all of the devices; 4. The monitoring device according to claim 1, wherein the display processing unit outputs the verification monitoring screen created from information on each of the test data sets.

8. 8. The monitoring device according to claim 7, wherein the display processing unit outputs the verification monitoring screens created from the information of the respective test data sets in sequence at a predetermined display interval.

9. The monitoring device described in claim 7, characterized in that when the display processing unit obtains a verification request number indicating one of the test data sets, it creates and outputs the verification monitoring screen from the test data of the test data set indicated by the verification request number.

10. The monitoring device described in claim 8, characterized in that when the display processing unit acquires pause command information, it creates data for an initial editing screen to which the edited test data list displayed on the verification monitoring screen output immediately before acquiring the pause command information has been added, and outputs the data for the initial editing screen.

11. The monitoring device described in claim 10, characterized in that after outputting the data of the initial editing screen, when the display processing unit acquires information on a selected component ID, which is the component ID corresponding to selected test data, which is the test data selected in the edited test data list, and information on a selected test data set indicating the test data set including the selected test data, the display processing unit changes the design of the display component indicated by the selected component ID on the initial editing screen, creates an editing screen in which the design of the position indicating the test data indicated by the selected component ID and information on the selected test data set in the edited test data list displayed in a list is changed, and outputs the data of the editing screen.

12. The monitoring device described in claim 11, characterized in that after outputting the data of the initial editing screen, when the display processing unit acquires information on input test data that is a new value for the selected test data, it rewrites the value of the test data indicated by the selected component ID and the information on the selected test data set in the edited test data list to the value of the input test data, and creates and outputs the editing screen from the test data of the test data set indicated by the selected test data set in the rewritten edited test data list.

13. A monitoring screen verification method for a monitoring device that acquires output values ​​from a plurality of devices and creates and displays a monitoring screen including display components corresponding to the output values, comprising: a test data output step of outputting, for all the devices, information on a test data list including tags corresponding to the respective devices, component IDs of the display components corresponding to the respective devices, and initial values ​​of test data corresponding to the respective devices; a test data acquisition step of acquiring an edited test data list including edited test data resulting from editing the test data in the test data list; a verification screen output step of processing the edited test data corresponding to each device in the edited test data list as the output value obtained from the device to create data for the monitoring screen, and outputting the created monitoring screen data as data for a verification monitoring screen.

14. A monitoring screen verification program that causes a computer to execute the monitoring screen verification method according to claim 13.

Images