Water management system, water management server, water management gateway device, and water management method

Abstract

To provide a water management system that realizes transition to a cloud environment without generating improvement of PLC or the like.SOLUTION: A water management system of an embodiment includes a water management facility control device, a water management server, and a water management gateway device. The water management gateway device transmits output data of the water management facility control device to the water management server, and receives input data to the water management facility control device from the water management server, and supplies the data to the water management facility control device. A data relay processing part of the water management gateway device converts the output data from the water management facility control device into character string data, creates a data structure including the character string data and corresponding to a format which conforms to a protocol applied to communication with the water management server, and transmits the structure to the water management server. A decoding processing part of the water management server extracts the character string data from the data structure received from the water management gateway device, and re-converts the data into a state of the output data.SELECTED DRAWING: Figure 2

Description

Technical Field

[0001] Embodiments of the present invention relate to a water management system, a water management server, a water management gateway device, and a water management method.

Background Art

[0002] There is a water management system for distributing water (such as agricultural water) taken from a river or the like to each field (such as a paddy field or a dry field) via a water channel. In the water management system, water management facilities (mainly pump stations and gates) are provided in each field, and a water distribution facility control device (hereinafter referred to as a PLC [Programable Logic Controller]) is provided in each water distribution facility, and each water distribution facility is controlled from a central monitoring device through the PLC. Many water management systems are built on-premises.

[0003] In recent years, cases of constructing a water management system that has been built on-premises in a cloud environment for the purpose of cost reduction have also been considered. At that time, considering costs and system reliability, it is considered to migrate only the upper-level device to the cloud environment while leaving the PLC.

[0004] In an on-premises water management system, in order to smoothly perform monitoring and control, a dedicated protocol is defined, and communication is performed between the central monitoring device and the PLC according to the dedicated protocol. On the other hand, when transmitting and receiving data between the cloud and the PLC, for example, it is necessary to communicate according to a general-purpose protocol applied by the cloud with a gateway device interposed.

[0005] However, when migrating to a cloud environment, it is not preferable in terms of cost or the like to have the gateway device hold management information regarding the format of data output by the PLC, or to modify the output format of the PLC to conform to the transmission format compliant with the protocol applied by the gateway device for communication with the cloud.

Prior Art Documents

Patent Documents

[0006]

Patent Document 1

Patent Document 2

Patent Document 3

Patent Document 4

Patent Document 5

Patent Document 6

Patent Document 7

Summary of the Invention

Problems to be Solved by the Invention

[0007] Therefore, the problem to be solved by the present invention is to provide a water management system, a water management server, a water management gateway device, and a water management method that enable migration to a cloud environment without causing improvements to the PLC or the like.

Means for Solving the Problems

[0008] The water management system of the embodiment includes a water management facility control device, a water management server, and a water management gateway device. The water management facility control device controls the water management facility. The water management server executes information processing for controlling the water management facility via the water management facility control device. The water management gateway device transmits the data output by the water management facility control device to the water management server via the network, and receives the data to be input to the water management facility control device from the water management server via the network and supplies it to the water management facility control device. The water management gateway device has a data relay processing unit. The data relay processing unit converts the output data from the water management facility control device into string data, creates a data structure corresponding to a format compliant with a protocol applied to communication with the water management server via the network including the string data, and transmits it to the water management server according to the protocol. The water management server has a decoding processing unit. The decoding processing unit extracts the string data from the data structure received from the water management gateway device and reconverts it to the state of the output data.

Brief Description of Drawings

[0009]

Figure 1

Figure 2

Figure 3

Figure 4

Figure 5

Figure 6

Figure 7

Figure 8

Figure 9

Figure 10

Figure 11

Figure 12

Figure 13

Mode for Carrying Out the Invention

[0010] Hereinafter, each embodiment will be described with reference to the drawings. Note that the disclosure is merely an example, and the invention is not limited by the content described in the following embodiments. Modifications that can be easily conceived by those skilled in the art are naturally included in the scope of the disclosure. For the sake of clarity, in the drawings, the size, shape, etc. of each part may be changed and schematically represented with respect to the actual embodiment. In a plurality of drawings, the same reference numerals may be assigned to corresponding elements, and detailed descriptions may be omitted.

[0011] (First Embodiment) First, the first embodiment will be described. FIG. 1 is a schematic diagram showing an example of the overall configuration of the water management system.

[0012] The water management system according to the first embodiment, for example, takes water from the main river 1 which is a water source, divides the taken water for use (for example, agricultural water), and properly distributes and delivers it to a plurality of fields such as paddy fields and farmlands.

[0013] As shown in FIG. 1, the water management system according to the first embodiment includes a main river 1, a water channel 2, a central control station 3, a water intake facility 4 for managing the water intake volume at the water intake, a plurality of farms 5a to 5c to which water is supplied, a drainage channel 6 for returning water from each farm 5a to 5c, and a drainage facility 7 for controlling a drainage outlet for returning the water collected via the drainage channel 6 to the main river 1.

[0014] The central control station 3 is a control station that controls the water intake facility 4 that takes water from the main river 1 which is the water source, the water supply facilities 51a to 51c and the drainage facilities 52a to 52c of each farm 5a to 5c, and the drainage facility 7.

[0015] The water channel 2 is a water channel that distributes the water taken from the main river 1 to each farm 5a to 5c. Note that the flow rate of the water taken from the main river 1 at the water intake is controlled by the central control station 3. The water sent to the water channel 2 is divided by a water diversion structure or the like and supplied to each farm 5a to 5c.

[0016] Each farm 5a to 5c is provided with water supply facilities 51a to 51c and drainage facilities 52a to 52c.

[0017] The water supply facilities 51a to 51c are facilities for taking in the water supplied from the water channel 2 into the farms 5a to 5c. Also, the drainage facilities 52a to 52c are facilities for draining the water in the farms 5a to 5c into the drainage channel 6.

[0018] The water supply facilities 51a to 51c and the drainage facilities 52a to 52c are facilities such as gates, valves (cocks), and pumps. The water supply facilities 51a to 51c and the drainage facilities 52a to 52c supply water to the farms 5a to 5c or drain water from the farms 5a to 5c, and measure each value such as the water supply volume and water level of the water in the farms 5a to 5c. The water supply facilities 51a to 51c and the drainage facilities 52a to 52c can control the water level and flow rate of the water in the farms 5a to 5c based on instructions from the central control station 3.

[0019] The drainage channel 6 is a waterway for discharging water from each farmland 5a to 5c to the main river 1 or the like.

[0020] In addition, in FIG. 1, as an example, an example of supplying water from the water supply channel 2 to the three farmlands 5a to 5c is shown, but it may be any number of one or more farmlands. Also, the water supply channel 2 may also be a waterway with multiple separated water intake ports.

[0021] FIG. 2 is a block diagram showing the system configuration of the water management system according to the first embodiment.

[0022] As shown in FIG. 2, the water management system includes a water management server (cloud) 20 provided on the cloud, a network 8, a water intake facility 4, farmlands 5a to 5c, a drainage facility 7, and a monitoring device 13.

[0023] The water intake facility 4 includes a water management facility 40 having a water intake port 401, a PLC 41 for controlling the water management facility 40, and an IoT-GW 42 interposed between the network 8 and the PLC 41.

[0024] The farmland 5a includes a water management facility 10a having a water supply facility 51a and a drainage facility 52a, a PLC 11a for controlling the water management facility 10a, and an IoT-GW 12a interposed between the network 8 and the PLC 11a. Here, the configuration of the farmland 5a has been described, but since the farmlands 5b and 5c also have the same configuration, the description is omitted.

[0025] The drainage facility 7 includes a water management facility 70 having a drainage port 701, a PLC 71 for controlling the water management facility 70, and an IoT-GW 72 interposed between the network 8 and the PLC 71.

[0026] In addition, hereinafter, when the water management facilities 10a to 10c, 40, and 70 are not particularly distinguished, they will be described collectively as the water management facility 10. The PLCs 11a to 11c, 41, and 71, and the IoT-GWs 12a to 12c, 42, and 72 may also be referred to as the PLC 11 and the IoT-GW 12 in the same way.

[0027] The water management server 20 is composed of a standard platform 21, a hosting service 22, a water management program (container) 23, and an RDB 24. Although it is illustrated as one server for convenience of explanation in FIG. 2, since it is on the cloud, it may be configured by a plurality of scattered server groups at multiple points. The internal configuration of the water management server 20 will be described later.

[0028] The IoT-GW12 is a gateway device that transmits the data output by the PLC11 to the water management server 20 via the network (Internet line) 8, and receives the data to be input to the PLC11 from the water management server 20 via the network 8 and supplies it to the PLC11. The IoT-GW12 includes a data relay processing unit 121.

[0029] The data relay processing unit 121 transmits the data received from the PLC11 to the water management server 20 according to a general-purpose protocol applied by the water management server 20 for communication via the network 8. At that time, the data relay processing unit 121 converts the data output from the PLC11 in a dedicated transmission format by the method unique to the water management system of this embodiment, and creates a data structure corresponding to the transmission format compliant with the general-purpose protocol including the converted data. The detailed process of converting the data will be described later.

[0030] The water management facilities 10a to 10c are facilities for managing water use such as the water supply facilities 51a to 51c and the drainage facilities 52a to 52c of the respective farms 5a to 5c shown in FIG. 1. The water management facility 40 is a facility for managing the water intake port 401 of the water intake facility 4 shown in FIG. 1. The water management facility 70 is a facility for managing the drainage port 701 of the drainage facility 7 shown in FIG. 1. The PLC11 controls the water management facility 10 by exchanging signals and various data with the water management facility 10 (10a to 10c, 40, 70).

[0031] The monitoring device 13 is a device used for monitoring the water management facility 10 via the water management server 20. The monitoring device 13 is composed of, for example, a personal computer (PC) installed with applications such as a browser and a mailer, a smartphone, and a communication device. The display screen information created by the water management server 20 is displayed on the browser. In addition, the monitoring device 13 accepts changes in setting values and operations for controlling the water management facility 10. The instruction data including the changes in setting values and operations is transmitted to the water management server 20.

[0032] Here, as a comparative example, the system configuration of an on-premises water management system will be described with reference to FIG. 3.

[0033] FIG. 3 is a block diagram showing the system configuration of an on-premises water management system. As shown in FIG. 3, the on-premises water management system includes a PLC 11 that controls the water management facility 10, a central monitoring device 30 that communicates with the PLC 11 via a dedicated line (for example, a VPN line or an LTE line) 8a, and routers 14 (14a to 14c, 44, 74) provided in pairs with the PLC 11 to be interposed between the PLC 11 and the central monitoring device 30.

[0034] Since the water management facility 10 and the PLC 11 are the same as those of the water management system of the present embodiment, the description thereof is omitted.

[0035] The central monitoring device 30 is installed in the central management office 3 or the like, and executes various information processes for controlling the water management facility 10 via the PLC 11. The central monitoring device 30 includes a router 31, a parent control device 32, a data processing device 33, a mail transmission device 34, and an operation device 35 (35a, 35b).

[0036] The router 31 transmits and receives transmission data corresponding to the dedicated transmission format described above via the dedicated line 8a to and from the router 14 on the PLC 11 side.

[0037] The master control device 32 transmits the transmission data received by the router 31 to the data processing device 33, the mail transmission device 34, and the operation device 35. Further, when the master control device 32 receives control data for controlling the water management facility 10 from the operation device 35, it transmits the data to the target PLC 11 via the router 31 in the aforementioned dedicated transmission format.

[0038] The data processing device 33 analyzes the signal information of the water management facility 10 included in the transmission data received by the master control device 32, and performs processing such as statistical processing for management.

[0039] The mail transmission device 34 analyzes the signal information of the water management facility 10 included in the transmission data received by the master control device 32, and performs monitoring processing such as alarm determination. The mail transmission device 34 sends an alarm mail according to the result of the alarm determination.

[0040] The operation device 35 analyzes the signal information of the water management facility 10 included in the transmission data received by the master control device 32, creates and displays monitoring screen information. Further, when an operation for controlling the water management facility 10 is input, the operation device 35 creates control data corresponding to the operation and transmits it to the master control device 32.

[0041] Next, the configuration on each farm side will be described. The router 14 transmits the data output by the PLC 11 to the central monitoring device 30 via the dedicated line 8a. Further, the router 14 receives the data to be input to the PLC 11 from the central monitoring device 30 via the dedicated line 8a and supplies it to the PLC 11.

[0042] Incidentally, the PLC 11 and the central monitoring device 30 communicate by defining a dedicated protocol (dedicated transmission format) in order to smoothly monitor and control the water management facility 10. Therefore, when communicating with the central monitoring device 30, the PLC 11 creates transmission data corresponding to the dedicated transmission format.

[0043] An on-premises water management system, such as that shown in FIG. 3, can control the water management facility 10 by transmitting transmission data in a dedicated transmission format, including control data created according to the operation of the operation device 35, to the PLC 11. In this way, in the on-premises water management system, the PLC 11 and the central monitoring device 30 realize their functions while analyzing various information contained in the transmission data with each other.

[0044] As described with reference to FIG. 3, when migrating an on-premises water management system to the cloud, there are several issues that need to be addressed. In the on-premises case, the PLC 11 and the central monitoring device 30 communicate according to a dedicated protocol. On the other hand, in the cloud, generally, communication is performed according to a general-purpose protocol. For communication in the cloud, a protocol generally called REST (REpresentational State Transfer) is used. When communicating according to this protocol, communication is often performed using data in JSON format.

[0045] However, in order to transmit JSON-formatted data from the PLC 11 to the cloud, it is necessary to update the PLC 11, such as improving the PLC 11 or replacing it with a corresponding PLC 11. Furthermore, when communicating with REST, it is also necessary to define the ID of the target water management facility and signal information.

[0046] Based on the above, returning to FIG. 2, the description of the water management system of this embodiment will be continued.

[0047] Here, the internal configuration of the water management server 20 will be described. The standard platform 21 is configured to include a web server unit 21a, an IoT data management unit 21b, and a standard DB 21c.

[0048] The Web server unit 21a transmits and receives various data to and from the IoT-GW 12 via the network 8. The IoT data management unit 21b manages various data transmitted and received to and from the IoT-GW 12 through the Web server unit 21a. The IoT data management unit 21b performs buffering to temporarily store the transmitted and received data between the IoT-GW 12 in the standard DB 21c.

[0049] The hosting service 22 is a processing unit that realizes a function of providing a service for lending out the water management server 20, and mediates between the water management program 23 operating on the water management server 20 as a container and the standard platform 21.

[0050] The water management program 23 is a program installed on the water management server 20 as a container under the control of the hosting service 22. The water management program 23 includes a decoding processing unit 23a, an encoding processing unit 23b, a data analysis processing unit 23c, a data processing unit 23d, a mail transmission unit 23e, and a monitoring / operation screen unit 23f.

[0051] As described above, the data output from the PLC 11 in a dedicated transmission format is converted by the data relay processing unit 121 of the IoT-GW 12 in a method unique to the water management system of the present embodiment, and is transmitted to the water management server 20 as a component of a data structure corresponding to a general-purpose protocol applicable to communication via the network 8. The data (data structure) transmitted from the IoT-GW 12 to the water management server 20 is received by the Web server unit 21a in the standard platform 21 and buffered in the standard DB 21c by the IoT data management unit 21b.

[0052] The decoding processing unit 23a extracts the data from the IoT-GW 12 buffered in the standard DB 21c and reconverts (decodes) it into the transmission data of the state output from the PLC 11. The decoding processing unit 23a transmits the reconverted transmission data to the data analysis processing unit 23c.

[0053] The encoding processing unit 23b converts (encodes) the transmission data in the dedicated transmission format defined for the communication between the PLC 11 and the central monitoring device 30 in the on-premises water management system, which is transmitted from the data processing unit 23d, into transmission data in the transmission format compliant with the general-purpose protocol applied by the water management server 20. The data transmitted from the data processing unit 23d will be described later.

[0054] As described above, the water management program 23 is a program installed in the water management server 20 as a container under the control of the hosting service 22. The data analysis processing unit 23c, the data processing unit 23d, the mail transmission unit 23e, and the monitoring / operation screen unit 23f are functions migrated from the central monitoring device 30 in the on-premises water management system.

[0055] The data analysis processing unit 23c refers to the transmission data transmitted from the decoding processing unit 23a, that is, the signal information of the water management facility 10 included in the output data of the PLC 11, and extracts the current value so that it can be managed as a water management system. The data analysis processing unit 23c performs a series of monitoring processes such as alarm determination based on the extracted current value.

[0056] Based on the current value extracted by the data analysis processing unit 23c, the data processing unit 23d performs arithmetic processing and processing of time-series data, creates form data such as daily reports and monthly reports, and stores them in the RDB (relational database) 24.

[0057] Based on the instruction from the data analysis processing unit 23c, the mail transmission unit 23e sends out alarm mails. Depending on the result of the above-mentioned monitoring process, the data analysis processing unit 23c performs emergency processes such as causing the mail transmission unit 23e to send out alarm mails as necessary.

[0058] The monitoring / operation screen unit 23f receives operations from the operator via the browser operating on the monitoring device 13, retrieves the necessary data for the operation from the RDB 24, creates the screens necessary for monitoring, and executes the processes for displaying them on the browser operating on the monitoring device 13. The monitoring / operation screen unit 23f also has functions for operating the water management facility 10 and setting / modifying data.

[0059] FIG. 4 is a diagram for explaining an example of the definition of the structure of transmission data in the water management system according to the first embodiment.

[0060] FIG. 4(a) is a diagram showing the transmission format of the PLC 11. This transmission format continues to be applied to the PLC 11 in the on-premises type water management system. That is, no improvement or the like of the PLC 11 occurs due to the migration from on-premises to the cloud environment.

[0061] There are, for example, three types of data output from the PLC 11: for measured values, for integrated values, and for state changes. Note that there are, for example, two types of data input to the PLC 11: for set values and for operation commands. The data for set values and the data for operation commands will be described later.

[0062] The data for measured values includes a data number, a data size, communication status information, and measured data. The measured data includes, for example, measured values of water intake volume, rotation speed of the intake pump, water level for water use, water level of the downstream water for water distribution, and gate opening.

[0063] The data for integrated values includes a data number, a data size, communication status information, and integrated data. The integrated data includes, for example, water inflow volume for water use, water discharge volume for water distribution, and received power amount.

[0064] The data for state changes includes a data number, a data size, communication status information, and state change data. The state change data includes, for example, status information of the water management facility including gates, pumps, and valves (valves), and power reception information of the water management facility.

[0065] FIG. 4(b) shows an example of the state indicated by each value of a certain state change data (state change data 0 to 15) when the state change data is represented by hexadecimal numbers.

[0066] In this state change data, when the bit state of the reference destination is ON (1), it indicates the state shown in the figure, and when it is OFF (0), it represents that it is not in that state.

[0067] When the 0th bit is ON (1), it indicates that the water management facility is in the operating state. When the 1st bit is ON (1), it indicates that the water management facility is in the stopped state. When the 4th bit is ON (1), it indicates a failure state. When the 5th bit is ON (1), it indicates an overcurrent state. When the 6th bit is ON (1), it indicates a ground fault state. When the 8th bit is ON (1), it indicates an emergency stop state. When the 9th bit is ON (1), it indicates an automatic operation state. When the 10th bit is ON (1), it indicates a manual operation state. The 2nd, 3rd, 7th, and 11th to 15th bits are defined as reserved.

[0068] The PLC 11 that controls the water management facility 10 periodically outputs data in the transmission format shown in FIGS. 4(a) and 4(b).

[0069] FIG. 4(c) shows a data structure corresponding to the transmission format conforming to the protocol defined for the water management server 20 to transmit and receive the data in the transmission format shown in FIGS. 4(a) and 4(b) using a general-purpose protocol. Here, it is assumed that the transmission data is created in JSON format.

[0070] JSON format data is described as a pair of a key and a value. A ":" is inserted between the key and the value. Also, the JSON format can describe a nested structure by using "{", "}".

[0071] In the example of FIG. 4(c), first, two keys, namely Station and TransDataInf, are described. Station is a key corresponding to the identification information of the water management facility 10 controlled by the PLC 11. TransDataInf is a key corresponding to the entire data to be transmitted.

[0072] Second, four keys, namely RecvKind, RecvData, Data, and Status, are described as the keys of the components of TransDataInf. RecvKind is a key corresponding to the received data type. RecvData is a key corresponding to the reception date and time. Data is a key corresponding to the received transmission data. Status is a key corresponding to the processing status.

[0073] When the data relay processing unit 121 of the IoT-GW 12 receives data from the PLC 11, it converts the reception date and time data and the received data into hexadecimal character strings. The IoT-GW 12 describes the converted reception date and time data in association with RecvData and the converted received data in association with Data.

[0074] Note that the data relay processing unit 121 previously holds the identification information of the water management facility 10 controlled by each PLC 11 and describes the identification information of the water management facility 10 in association with Station. Also, the data relay processing unit 121 extracts the data type from the output data of the PLC 11 and describes it in association with RecvKind.

[0075] That is, in the water management system of this embodiment, the data relay processing unit 121 of the Iot-GW12 only extracts the data type from the output data of the PLC11, converts the output data into a character string, and sets it as a component of the data to be transmitted. Then, according to a general-purpose protocol such as REST applied by the water management server 20, the data output by the PLC11 in a dedicated transmission format can be transmitted to the water management server 20. Also, the Iot-GW12 only needs to have a function of extracting the data type from the output data of the PLC11, and there is no need to hold management information related to the dedicated transmission format and the like.

[0076] Also, the decoding processing unit 23a of the water management program 23 operating as a container on the water management server 20 described above only needs to extract the character string data corresponding to the transmission data of the PLC11 from the data transmitted from the Iot-GW12 using the key and convert it back to the transmission data of the PLC11.

[0077] FIG. 5 is a diagram showing an example in which received transmission data is created based on measurement data which is one of the transmission data. Hereinafter, the data transmitted and received by the PLC11 may be referred to as transmission data, and the data transmitted from the IoT-GW12 to the water management server 20 including the character string data obtained by converting the transmission data may be referred to as received transmission data. Also, the data transmitted from the water management server 20 to the IoT-GW12 including the character string data obtained by converting the transmission data may be referred to as transmitted transmission data.

[0078] FIG. 5(a) shows an example of the measurement data output from the PLC11. In the example of FIG. 5(a), the measurement data includes "0102" indicating that it is measurement data, the transmission packet number "1", the packet size "200", the communication state "0x0A02", the measured value of the water level for water use "1234mm", the measured value of the downstream water level for water diversion "2421mm", and the measured value of the opening degree of the water diversion weir gate "80%".

[0079] FIG. 5(b) is an example in which the measurement data in FIG. 5(a) is converted into transmission data in the form of a character string by the data relay processing unit 121 of the IoT-GW 12. In the example of FIG. 5(b), each piece of measurement data in the transmission data is converted into a hexadecimal character string, and in order from the beginning, it includes "0x0102" (type (for measurement)), "0x0001" (data NO), "0x00C8" (data size), "0x0A02" (communication status information), "0x04D2" (measurement data 1), "0x0975" (measurement data 2), "0x0050" (measurement data 3), …, "0x8000" (measurement data 100).

[0080] FIG. 5(c) is an example of a data structure (received transmission data) corresponding to a transmission format compliant with a general protocol applied by the water management server 20, including the transmission data in FIG. 5(b), created by the data relay processing unit 121. As described above, the transmission data (FIG. 5(b)) converted into a character string is described in association with Data (key) as a component of a data structure in JSON format, for example.

[0081] In the example of FIG. 5(c), the data relay processing unit 121 describes the identification information "10" of the water management facility 10 held in advance in association with Station. Also, the data relay processing unit 121 describes the type (for measurement) "0102" extracted from the received measurement data (FIG. 5(a)) in association with RecvKind, the reception date and time "2023-08-01T11:48:00Z" of the measurement data in association with RecvDate, and the processing status "Normal" in association with Status.

[0082] FIG. 6 is a diagram showing an example in which received transmission data is created based on state change data, which is one of the transmission data. Fig. 6(a) shows an example of the state change data output from PLC11. In the example of Fig. 6(a), the state change data includes "0103" indicating that it is state change data, the transmission packet number "1", the packet size "20", the communication state "0x0A02", "0x8040" indicating the state of Pump No. 1, "0x4240" indicating the state of Pump No. 1, and "0x0101" indicating the power reception state.

[0083] Fig. 6(b) is an example in which the state change data in Fig. 6(a) is converted into string transmission data by the data relay processing unit 121 of IoT-GW12. In the example of Fig. 6(b), each data of the state change data in the transmission data is converted into a hexadecimal string, and in order from the beginning, it includes "0x0103" (type (for state change)), "0x0001" (data NO), "0x0014" (data size), "0x0A02" (communication state information), "0x8040" (state change data 0 to 15), "0x4240" (state change data 16 to 31), "0x0101" (state change data 32 to 47), …, "0x0000" (state change data 143 to 159).

[0084] Fig. 6(c) is an example of a data structure corresponding to a transmission format compliant with a general protocol applied by the water management server 20, including the transmission data in Fig. 6(b), generated by the data relay processing unit 121. As described above, the transmission data converted into a string (Fig. 6(b)) is described in association with Data (key) as a component of a data structure in JSON format, for example.

[0085] Note that in the example of Fig. 6(c), the data relay processing unit 121 describes the identification information "10" of the water management facility 10 held in advance in association with Station. Also, the data relay processing unit 121 describes the type (for state change) "0103" extracted from the received state change data (Fig. 6(a)) in association with RecvKind, and describes the reception date and time "2023-08-01T11:50:10Z" of the state change data in association with RecvDate.

[0086] FIG. 7 is a diagram showing an example in which received transmission data is created based on integration data which is one of the transmission data.

[0087] FIG. 7(a) shows an example of the integration data output from PLC11. In the example of FIG. 7(a), the integration data including "0104" indicating that it is state change data, transmission packet number "1", packet size "200", communication state "0x0A02", water inflow rate "3200 m3", water diversion discharge rate "2800 m3", and received power amount "120 kwh" is shown.

[0088] FIG. 7(b) is an example in which the integration data of FIG. 7(a) is converted into transmission data in string form by the data relay processing unit 121 of IoT-GW12. In the example of FIG. 7(b), the transmission data is such that each data of the integration data is converted into an octal string, and in order from the beginning, it includes "(000402)8" (type (for integration)), "(000001)8" (data NO), "(000310)8" (data size), "(005002)8" (communication state information), "(002322)8" (integration data 1), "(004565)8" (integration data 2), "(000350)8" (integration data 3), …, "(100000)8" (integration data 100).

[0089] FIG. 7(c) is an example of a data structure corresponding to a transmission format compliant with a general protocol applied by the water management server 20, including the transmission data of FIG. 7(b), created by the data relay processing unit 121. As described above, the transmission data (FIG. 7(b)) converted into a string is described in association with Data (key) as one component of a data structure in, for example, JSON format.

[0090] In the example of Fig. 7(c), the data relay processing unit 121 describes the identification information "10" of the water management facility 10 held in advance in association with Station. Also, the data relay processing unit 121 describes the type (for integration) "0104" extracted from the received integration data (Fig. 7(a)) in association with RecvKind, and describes the reception date and time "2023-08-01T11:54:10Z" of the integration data in association with RecvDate.

[0091] Subsequently, an example of the generation of a data structure (transmission transmission data) transmitted from the water management server 20 to the IoT-GW12, which includes the character string data obtained by converting the transmission data (data for controlling the water management facility 10 via the PLC11, generated by the cooperation of the monitoring / operation screen unit 23f and the data processing unit 23d) to be input to the PLC11, will be described.

[0092] Fig. 8 is a diagram showing an example in which transmission transmission data is generated based on the set value data, which is one of the transmission data.

[0093] The set value data is the data transmitted from the central monitoring device 30 to the PLC11 in an on-premises water management system. That is, in the water management system of the present embodiment, it is the data created and output by the data processing unit 23d of the water management program 23. The transmission format of the PLC11 is also applied to the set value data. The set value data is used by the operator to control the water management facility 10 via the PLC11 by operating the monitoring device 13.

[0094] Fig. 8(a) shows an example of the set value data output from the data processing unit 23d. In the example of Fig. 8(a), the set value data including "0201" indicating that it is the set value data, the transmission packet number "1", the packet size "4", the spare data "0x0000", and the water intake target value "2.1 m3 / s" is shown.

[0095] FIG. 8(b) shows an example in which the data for setting values in FIG. 8(a) is converted into transmission data in the form of a character string by the encoding processing unit 23b of the water management server 20. In the example of FIG. 8(b), the transmission data is such that each piece of data for setting values is converted into a hexadecimal character string, and in order from the beginning, it includes "0x0201" (type (for setting values)), "0x0001" (data number), "0x0004" (data size), "0x6666", and "0x0640" (water intake target value).

[0096] FIG. 8(c) shows an example of a data structure (transmission data for transmission) corresponding to a transmission format compliant with a general protocol applied by the water management server 20, which includes the transmission data in FIG. 8(b) and is created by the encoding processing unit 23b. As described above, the transmission data (FIG. 8(b)) converted into a character string is described in association with Data (key), for example, as one component of a data structure in JSON format.

[0097] In the example of FIG. 8(c), first, two keys, Station and TransSendInf, are described. Station is a key corresponding to the identification information of the PLC 11. TransSendInf is a key corresponding to the entire data to be transmitted.

[0098] Second, as keys for the components of TransSendInf, four keys, SendKind, SendData, Data, and Status, are described. SendKind is a key corresponding to the type of transmission data. SendData is a key corresponding to the transmission date and time. Data is a key corresponding to the transmission data for transmission. Status is a key corresponding to the processing status.

[0099] The encoding processing unit 23b describes, for example, associating the identification information "01" of the water management facility 10 stored in the RDB 24 with "Station". Further, the encoding processing unit 23b describes associating the type (for set value) "0201" extracted from the set value data (Fig. 8(a)) output from the data processing unit 23d with "SendKind", associating the transmission date and time "2023-08-24 18:01:10" of the set value data with "SendDate", and associating the processing status "Normal" with "Status".

[0100] Fig. 9 is a sequence chart showing the processing flow when data is transmitted from the PLC 11 of the water management system of the first embodiment to the water management server 20.

[0101] In step S1, when the PLC 11 receives a signal output from the water management facility 10, it creates transmission data in an existing dedicated transmission format based on the information contained in the signal. For example, when the signal output from the water management facility 10 is measurement data, the PLC 11 creates transmission data as shown in Fig. 5(a).

[0102] Next, in step S2, the PLC 11 transmits the created transmission data to the IoT-GW 12.

[0103] In step S3, the data relay processing unit 121 of the IoT-GW 12 receives the transmission data from the PLC 11.

[0104] In step S4, the transmission data is converted into hexadecimal string data (). When the data relay processing unit 121 receives the transmission data in Fig. 5(a), it converts it into hexadecimal string data as shown in Fig. 5(b).

[0105] The data relay processing unit 121 creates received transmission data including the data type of the transmission data, the reception date and time, and the string data as a data structure corresponding to the transmission format compliant with the general protocol applied by the water management server 20.

[0106] When the received transmission data is successfully created, "0" (Normal) is set as the processing status in the received transmission data. In this way, the data relay processing unit 121 creates the received transmission data shown in Fig. 5(c).

[0107] Then, in step S5, the data relay processing unit 121 transmits the created received transmission data to the water management server 20.

[0108] The water management server 20 receives the received transmission data transmitted from the IoT-GW12 by the Web server unit 21a.

[0109] In step S6, the IoT data management unit 21b stores the received transmission data in the standard DB21c. The standard DB21c is a buffer area, and the received transmission data is buffered in the standard DB21c.

[0110] The decode processing unit 23a retrieves the received transmission data from the standard DB21c at regular intervals or when an event occurs (when receiving the received transmission data).

[0111] Then, in step S7, the decode processing unit 23a reconverts the string data included in the retrieved received transmission data into transmission data corresponding to the aforementioned dedicated transmission format of the PLC11. At this time, if the format of the transmission data is hexadecimal, it is converted into hexadecimal data, and if it is octal, it is converted into octal data. For example, if the buffered received transmission data is as shown in Fig. 5(c), the decode processing unit 23a reconverts it into the hexadecimal data shown in Fig. 5(b).

[0112] In step S8, the data analysis processing unit 23c analyzes the transmission data reconverted by the decode processing unit 23a based on the predefined data types included in the transmission data, and extracts the current value of the water management facility 10. The data analysis processing unit 23c transmits the extracted current value to the data processing unit 23d.

[0113] In step S9, the data processing unit 23d performs arithmetic processing and statistical processing on each current value retrieved by the data analysis processing unit 23c and stores the results in the RDB.

[0114] In step S10, the monitoring / operation screen unit 23f creates screen information based on the current values stored in the RDB24. At this time, the monitoring / operation screen unit 23f creates screen information from screen layout information, image files, etc. The display screen information is displayed, for example, on a browser operating on the monitoring device 13.

[0115] Here, referring again to FIG. 5, a specific example of the case where the measurement signal is transmitted from the water management facility 10 to the PLC11 will be described.

[0116] The PLC11 creates and outputs transmission data (measurement data) in the format of FIG. 5(a). The data relay processing unit 121 of the IoT-GW12 that receives this transmission data first performs conversion into character string data as shown in FIG. 5(b). The converted character string data is set in JSON format data together with the data type of the transmission data and information indicating the reception date and time. Thereby, reception transmission data as shown in FIG. 5(c) is created based on the transmission data. The created reception transmission data is transmitted from the IoT-GW12 to the water management server 20.

[0117] The reception transmission data transmitted to the water management server 20 is buffered in the standard DB21c by the IoT data management unit 21b of the water management server 20. The reception transmission data buffered in the standard DB21c of the standard platform 21 is retrieved by the decode processing unit 23a of the water management program 23 under the control of the hosting service 22. The decode processing unit 23a re-converts the retrieved data into transmission data in the transmission format output by the PLC11 as shown in FIG. 5(a) based on the data type. The re-converted transmission data has the current value retrieved in the same manner as before by the data analysis processing unit 23c.

[0118] FIG. 10 is a sequence chart showing the processing flow when data is transmitted from the water management server 20 of the water management system according to the first embodiment to the PLC 11.

[0119] When an operation such as a change in the target value or set value or an operation instruction is input on the monitoring device 13 (browser operating on the monitoring device 13), the monitoring device 13 transmits operation data indicating the operation instruction, change in the target value or set value to the water management server 20 via the network 8.

[0120] In step S21, the monitoring / operation screen unit 23f of the water management server 20 transmits the received operation data to the data processing unit 23d.

[0121] The data processing unit 23d creates transmission data in an existing dedicated transmission format that can be transmitted and received by the PLC 11 based on the operation data. For example, when the operation data is data for a set value, the data processing unit 23d creates transmission data as shown in FIG. 8(a).

[0122] In step S22, the data processing unit 23d transmits the created transmission data to the encoding processing unit 23b.

[0123] In step S23, the encoding processing unit 23b converts the transmission data into hexadecimal string data. When the encoding processing unit 23b receives the transmission data in FIG. 8(a), it converts it into hexadecimal string data as shown in FIG. 8(b).

[0124] In step S24, the encoding processing unit 23b creates transmission data including the data type of the transmission data, the requested date and time, and the converted string data as a data structure corresponding to the transmission format compliant with the general protocol applied by the water management server 20.

[0125] When the transmission data is successfully created, the encoding processing unit 23b sets "0" (Normal) as the processing status in the transmission data. In this way, the encoding processing unit 23b creates the transmission data shown in Fig. 8(c). The created transmission data is passed to the standard platform 21 under the control of the hosting service 22.

[0126] Then, in step S25, it is stored in the standard DB21c by the IoT data management unit 21b.

[0127] The data relay processing unit 121 of the IoT-GW12 periodically sends a request to obtain transmission data (GET of the HTTP method). At this time, the data relay processing unit 121 sends a request to obtain transmission data to the water management server 20 using the previous confirmation date and time as the key. For example, when the previous confirmation date and time is 18:01:05 on August 24, 2023 and the current confirmation date and time is 18:01:15 on August 24, 2023, the request data confirmation period is specified as 18:01:05 on August 24, 2023 to 18:01:15 on August 24, 2023, and a GET is sent to the water management server 20 for inquiry.

[0128] As a result, the corresponding transmission data is sent from the water management server 20 to the IoT-GW12.

[0129] In step S26, in this way, the IoT-GW12 can obtain the transmission data. If there is no requested data, a notification indicating that there is no data or blank data such as "{}" is sent.

[0130] In step S27, the data relay processing unit 121 of IoT-GW12 reconverts the acquired transmission data into the transmission data of PLC11. Specifically, the data relay processing unit 121 reconverts the string data included in the transmission data into transmission data corresponding to the transmission format of PLC11. For example, when the acquired transmission data is as shown in Fig. 8(c), the data relay processing unit 121 extracts the hexadecimal string data of Fig. 8(b) and reconverts it into the transmission data of Fig. 8(a).

[0131] In step S28, the data relay processing unit 121 transmits the transmission data to PLC11.

[0132] In this way, the data relay processing unit 121 of IoT-GW12 has both a function corresponding to the decode processing unit 23a of the water management program 23 operating under the control of the hosting service 22 on the water management server 20 and a function corresponding to the encode processing unit 23b.

[0133] In step S29, PLC11 receives the transmission data.

[0134] In step S30, PLC11 controls the target water management facility 10 according to the transmission data. PLC11 writes the received transmission data as setting information to the address and bit that have been assigned in advance in order as an operation command, and outputs it to the digital output board. Thereby, setting value changes and operation instructions can be executed on the water management facility 10 via PLC11.

[0135] Here, referring to Fig. 8 again, a specific example when data for setting values is transmitted from the water management server 20 to IoT-GW12 will be described.

[0136] The monitoring and operation screen section 23f of the water management server 20 transmits operation data including the setting value change from the monitoring device 13 to the data processing section 23d. Here, operation data indicating an operation to change the water intake target value to 2.1 m3 / s is transmitted to the data processing section 23d. The data processing section 23d that has received this operation data generates transmission data (data for setting values) in the form of Fig. 8(a). The data processing section 23d transmits the generated transmission data to the encoding processing section 23b.

[0137] The encoding processing section 23b that has received the transmission data performs conversion to string data as shown in Fig. 8(b). The converted string data is set in JSON format data together with the data type of the transmission data and information indicating the transmission date and time. Thereby, transmission transmission data as shown in Fig. 8(c) is generated based on the transmission data. The generated transmission transmission data is buffered in the standard DB 21c by the IoT data management section 21b. When the IoT data management section 21b receives a GET periodically transmitted from the IoT-GW 12, it transmits the corresponding transmission transmission data to the IoT-GW 12.

[0138] The data relay processing section 121 of the IoT-GW 12 reconverts the string data included in the received transmission transmission data into transmission data as shown in Fig. 8(a). The reconverted transmission data is transmitted to the PLC 11. The PLC 11 outputs the information included in the transmission data to the water management facility 10. Thereby, the water intake target value of the water management facility 10 can be changed to 2.1 m3 / s.

[0139] As described above, in the water management system of the first embodiment, the data in the dedicated transmission format output by the PLC 11 is converted into character string data by the data relay processing unit 121 of the IoT-GW 12, and is included in a data structure corresponding to the transmission format compliant with the protocol applied to the communication via the network 8 by the water management server 20. Then, the data structure is transmitted to the water management server 20 via the network 8. On the other hand, in the water management server 20 that has received this data structure, the decoding processing unit 23a extracts the character string data from the data structure and reconverts it into the data in the dedicated transmission format output by the PLC 11, and supplies it to the data analysis processing unit 23c.

[0140] Also, the data (in the dedicated transmission format) to be input to the PLC 11 generated by the cooperation between the monitoring / operation screen unit 23f and the data processing unit 23d of the water management server 20 is converted into character string data by the encoding processing unit 23b and included in a data structure corresponding to the transmission format compliant with the protocol applied to the communication via the network 8 by the water management server 20. The data structure is buffered in the standard DB 21c of the standard platform 21 and acquired by the IoT-GW 12. The data relay processing unit 121 of the IoT-GW 12 extracts the character string data from the data structure and reconverts it into the data in the dedicated transmission format to be input to the PLC 11, and supplies it to the PLC 11.

[0141] Thereby, the water management system of the first embodiment realizes the migration from the on-premises to the cloud environment without causing improvements to the PLC 11 or the like. Also, there is no need to have the IoT-GW 12 hold management information or the like regarding the transmission format of the PLC 11.

[0142] Furthermore, software resources used on the on-premises (such as the data processing device 33 and the mail transmission device 34 of the central monitoring device 30) can be utilized when migrating to the cloud environment.

[0143] (Modification Example of the First Embodiment) Next, a modification example of the water management system according to the first embodiment will be described. In the description of the water management system according to the first embodiment above, the data relay processing unit 121 of the IoT-GW12 acquires the buffered transmission data by periodically transmitting a GET. In this case, a delay occurs for the time of the transmission cycle of the GET transmitted by the data relay processing unit 121. Although there is a method of minimizing this delay by accelerating the transmission cycle of the GET, it leads to an increase in the running cost because the load on the CPU of the IoT-GW12 increases and the number of unnecessary GET transmissions increases.

[0144] Therefore, in order to avoid this, a method of performing setting value changes and operation processing using WebSocket can be considered.

[0145] FIG. 11 is a sequence chart showing an example of processing when the water management system according to the first embodiment performs setting value changes and operation instructions using WebSocket. Here, only the parts where different processing is performed from FIG. 10 will be described, and the parts described above will be omitted.

[0146] The IoT-GW12 creates a communication channel using WebSocket with the water management server 20 in advance according to the procedure provided by the IoT data management unit 21b of the water management server 20 in advance.

[0147] In step S25, the IoT data management unit 21b stores the transmission data in the standard DB 21c.

[0148] Then, in step S25a, it is notified to the IoT-GW12 via WebSocket that the transmission data has been stored in the standard DB 21c. When a GET corresponding to the notification is transmitted from the IoT-GW12, the IoT data management unit 21b transmits the transmission data to the IoT-GW12.

[0149] Thus, in this modified example, instead of periodically sending a GET to the water management server 20 to obtain transmission data, the IoT-GW12 obtains the transmission data by sending a GET in response to a notification from the water management server 20. As a result, the IoT-GW12 can obtain the transmission data without delay.

[0150] Note that in this modified example, when the transmission data is stored in the standard DB21c, the water management server 20 sends a notification to the IoT-GW12 via WebSocket. However, the water management server 20 may directly send the transmission data or the transmission data via WebSocket. In this case, the IoT-GW12 waits for data from the created channel and can receive the transmission data at the timing when the transmission data including the instruction data is sent from the water management server 20 side. By directly sending the received transmission data to the PLC11, the setting value change and operation instruction can be realized.

[0151] Here, an example of communicating with the cloud using JSON format data is shown. However, for example, CSV format data may also be used. The data format may be any data format that can communicate according to the communication protocol with the cloud.

[0152] (Second Embodiment) Next, the second embodiment will be described. In the first embodiment, a cloud-based water management system was described. However, it is difficult to migrate all on-premises water management systems to the cloud due to operational constraints and reliability issues. For example, when the central control station 3 withdraws water from the main river 1, it withdraws water by controlling the water intake 401 such as the headworks. Since the water withdrawn from the water intake 401 is supplied to the farmland as water for use, the water intake 401 can be said to be important among the water management facilities 10. It is desirable that important water management facilities 10 such as the water intake 401 be managed in an on-premises type with high security.

[0153] Therefore, in the second embodiment, a water management system that operates an on-premises system and a cloud system in parallel will be described.

[0154] FIG. 12 shows an example of the configuration of the water management system according to the second embodiment. Here, descriptions of the parts described in the first embodiment will be omitted, and different parts will be described.

[0155] The second embodiment is an embodiment in which a hybrid configuration is achieved by adding an on-premises central monitoring device 30 to the water management system of the first embodiment. Note that the hybridization of the water management system may be applied to all water management facilities 10, or may be applied only to some of the water management facilities 10 from the perspective of cost. When only some are hybridized, water management facilities 10 with high importance may be selected to form a hybrid configuration. For example, a facility such as a water intake 401 is considered an important facility because if it fails, the supply of water to the entire water management system will be interrupted. Therefore, a configuration may be adopted in which only the control of the water intake 401, which is important in the water management system, is hybridized.

[0156] Compared with the water management system of the first embodiment shown in FIG. 1, the water management system of the second embodiment shown in FIG. 12 has an additional on-premises central monitoring device 30, dedicated lines 8a, and routers 14a and 14b.

[0157] The PLC 11a communicates with the central monitoring device 30 via the dedicated line 8a through the router 14a. Furthermore, the PLC 11a communicates with the water management server 20 via the network 8 through the IoT-GW 12a.

[0158] Similarly, the PCL 11b communicates with the central monitoring device 30 via the dedicated line 8a through the router 14b. Furthermore, the PLC 11b communicates with the water management server 20 via the network 8 through the IoT-GW 12b.

[0159] The operation device 35 of the on-premises central monitoring device 30 has a data analysis processing unit 36. The data analysis processing unit 36 analyzes the signal information of the water management facility 10 included in the transmission data and extracts the current value. That is, the data analysis processing unit 23c of the water management server 20 of the cloud system described above is a transplantation of the function of the existing data analysis processing unit 36.

[0160] In the water management system according to the second embodiment, transmission data corresponding to the transmission format of the PLC 11 is transmitted to the router 14 and the IoT-GW 12.

[0161] The transmission data transmitted to the router 14 is transmitted to the operation device 35 via the dedicated line 8a, the router 31 of the central monitoring device 30, and the parent control device 32. The data analysis processing unit 36 of the operation device 35 extracts the current value by analyzing the transmission data. The operation device 35 performs various processes using the extracted current value.

[0162] In addition, the transmission data transmitted to the IoT-GW 12 is converted into character string data by the data relay processing unit 121 of the IoT-GW 12 and encapsulated in the received transmission data in JSON format. The received transmission data is transmitted to the water management server 20 via the network 8. The received transmission data transmitted to the water management server 20 has the character string data extracted by the decoding processing unit 23a of the water management server 20 and is reconverted into transmission data, and then transmitted to the data analysis processing unit 23c. The data analysis processing unit 23c extracts the current value by analyzing the transmission data. The water management program 23 of the water management server 20 performs various processes using the analyzed current value.

[0163] In this way, the transmission data transmitted to the IoT-GW 12 and the router 14 is finally analyzed by the data analysis processing unit 23c or the data analysis processing unit 36, and the current value is extracted. That is, even when data corresponding to the same transmission format is transmitted to the on-premises and the cloud respectively, the same processing can be performed for both.

[0164] Therefore, even in the water management system that operates the on-premises and cloud systems in parallel in the second embodiment, by transmitting the conventional transmission data without making improvements to the PLC 11 or the like, the processing performed by the central monitoring device 30 of the on-premises water management system can also be performed by the cloud water management server 20.

[0165] (Modification Example of the Second Embodiment) Next, a modification example of the second embodiment will be described. In the second embodiment, the management of all the water management node facilities 10 was in a hybrid configuration. However, considering the cost, it may be configured as a hybrid by selecting the water management facilities 10 with high importance. For example, the intake port 401 facility is considered an important facility because if it fails, the water supply to the entire water management system will be interrupted. Therefore, it may be configured such that only the control of the intake port 401, which is important in the water management system, is hybrid.

[0166] FIG. 13 is a diagram showing the configuration of the water management system according to the modification example of the second embodiment. In the modification example of the second embodiment, only a part of the water management facilities 10 is in a hybrid form.

[0167] The water management system according to the modification example of the second embodiment shown in FIG. 13, when compared with the water management system of the second embodiment shown in FIG. 12, has the above-described hybrid configuration in which only the PLC 41 of the water management facility 40 communicates with the central monitoring device 30 via the router 44 and with the water management server 20 via the IoT-GW 42.

[0168] On the other hand, the PCL 11a of the water management facility 10a and the PLC 11b of the water management facility 10b communicate only with the water management server 20 via the IoT-GW 12a and 12b and via the network 8.

[0169] The water management facility 40 having a hybrid configuration can be controlled by both the central monitoring device 30 and the water management server 20.

[0170] In this way, by making only some important water management facilities 40 hybrid, the reliability of the important water management facilities 10 can be enhanced.

[0171] Also, since a router 14 is not installed in the water management facilities 10 that are not made hybrid, the cost can be reduced as compared with the case where all the water management facilities 10 are configured in a hybrid manner.

[0172] According to at least one embodiment described above, the water management system creates a data structure corresponding to a transmission format compliant with a protocol applied to communication with the water management server 20 via the network 8, which includes converting the output data from the PLC 11 into string data and includes the data type of the output data and the string data, and transmits it to the water management server 20 according to the protocol. It has a data relay processing unit 121 of the IoT-GW 12 and a decoding processing unit 23a of the water management server 20 that reconverts the string data included in the data structure received from the IoT-GW 12 into the state of the output data. With this configuration, it is possible to realize migration to a cloud environment without causing improvements to the PLC 11 and the like.

[0173] Also, according to at least one embodiment described above, the encoding processing unit 23b of the water management server 20 converts the instruction data indicating the operation instruction of the PLC 11 output by the water management program 23 into string data, and includes the data type of the instruction data and the string data, and creates a data structure corresponding to the transmission format compliant with the protocol for transmitting to the IoT-GW 12 via the network 8. The data relay processing unit 121 of the IoT-GW 12 reconverts the string data included in the data structure received from the water management server 20 into the state of the instruction data and transmits the instruction data to the PLC 11. With this configuration, the processing for controlling the water management facilities 10 that has been performed by the central monitoring device 30 can also be performed in the water management server 20.

[0174] Also, according to at least one of the embodiments described above, the data relay processing unit 121 of the IoT-GW 12 converts the transmission data from the PLC 11 into character string data, includes it in the received transmission data, and transmits it to the water management server 20. Also, by extracting the character string data from the transmission data transmitted from the water management server 20 and re-converting it into transmission data and transmitting it to the PLC 11, for example, without defining the ID of the water management facility 10 and signal information required when communicating via REST in the PLC 11, communication with the water management server 20 can be achieved. In addition, it is not necessary to have the IoT-GW 12 hold data regarding the transmission format of the PLC 11, and a water management system can be realized without adding a function for data analysis or the like.

[0175] Also, according to at least one of the embodiments described above, by using WebSocket for communication between the water management server 20 and the IoT-GW 12, it is possible to minimize the delay time without causing a delay due to a periodic GET process or an increase in the load on the CPU, and it becomes possible to perform timely request processing.

[0176] Although some embodiments of the present invention have been described, these embodiments are presented as examples and are not intended to limit the scope of the invention. These embodiments can be implemented in various other forms, and various omissions, replacements, and changes can be made without departing from the gist of the invention. These embodiments and their modifications are included in the scope and gist of the invention, as well as in the invention described in the claims and its equivalent scope.

Explanation of Reference Numerals

[0177] 8… Network (Internet line), 8a… Dedicated line, 10… Water management equipment, 11… Control device (PLC), 12… IoT-GW, 121… Data relay processing unit, 13… Monitoring device, 20… Water management server (cloud), Standard platform… 21, Hosting service… 22, Water management program (container)… 23, 23a… Decoding processing unit, 23b… Encoding processing unit, 23c… Data analysis processing unit, 23d… Data processing unit, 23e… Mail sending unit, 23f… Monitoring / operation screen unit, 24… RDB, 30… Central monitoring device, 31… Router, 32… Parent control device, 33… Data processing device, 34… Mail sending device, 35… Operating device, 36… Data analysis processing unit, 401… Water intake point.

Claims

1. A water management equipment control device for controlling water management equipment, A water management server for controlling the water management equipment via the water management equipment control device, A water management gateway device that transmits data output by the water management equipment control device to the water management server via a network, and receives data to be input to the water management equipment control device from the water management server via the network and supplies it to the water management equipment control device, The water management gateway device has a data relay processing unit that converts output data from the water management equipment control device into character string data, creates a data structure corresponding to a format compliant with a protocol applied to communication with the water management server via the network including the character string data, and transmits the data to the water management server according to the protocol, The water management server has a decoding processing unit that extracts the character string data from the data structure received from the water management gateway device and reconverts it to the state of the output data, A water management system.

2. The water management system according to claim 1, wherein the water management server is a server provided on the cloud.

3. The water management server, further includes an encoding processing unit that converts instruction data indicating an operation instruction of the water management equipment for the water management equipment control device into character string data, creates a data structure corresponding to the format compliant with the protocol for transmitting the character string data to the water management gateway device via the network, The data relay processing unit of the water management gateway device extracts the character string data from the data structure received from the water management server, reconverts it to the state of the instruction data, and transmits the instruction data to the water management equipment control device. The water management system according to claim 1.

4. The water management server has a database for storing the data structure created by the encoding processing unit, The data relay processing unit of the water management gateway device periodically transmits an acquisition request for the data structure to the water management server. The water management system according to claim 3.

5. When the data structure is created by the encoding processing unit, the water management server uses WebSocket to transmit the data structure to the water management gateway device. The water management system according to claim 3.

6. The water management server has a database for storing the data structure created by the encoding processing unit, when the data structure is stored in the database, notifies the water management gateway device that the data structure exists using WebSocket, when the data relay processing unit of the water management gateway device receives the notification, transmits a request for acquisition of the data structure to the water management server. The water management system according to claim 3.

7. further includes a central monitoring device, the central monitoring device receives output data from the water management facility control device according to a dedicated protocol applied to communication with the water management facility control device, and transmits instruction data indicating an operation instruction for the water management facility to the water management facility control device according to the dedicated protocol in response to an operation on the central monitoring device. The water management system according to claim 1.

8. at least one of the water management facilities is a water intake, data output from the water management facility control device that controls the water management facility that is the water intake is transmitted by the water management gateway device to the water management server via the network and is transmitted from the water management facility to the central monitoring device according to the dedicated protocol. The water management system according to claim 7.

9. A water management server that executes information processing for controlling the water management facility via a control device that controls the water management facility, a water management server unit that receives, according to the protocol, a data structure corresponding to a format compliant with a protocol applied to communication with a water management gateway device via a network, the data structure including string data obtained by converting the output data of the control device; a decoding processing unit that extracts the string data from the data structure received from the water management gateway device and reconverts it to the state of the output data; A water management server having the above.

10. Convert the instruction data indicating the operation instruction of the water management facility for the control device created by the information processing into character string data, and create a data structure corresponding to the format compliant with the protocol for transmitting to the water management gateway device via the network including the character string data, and further include an encoding processing unit. The water management server according to claim 9.

11. When the data structure is created by the encoding processing unit, transmit the data structure to the water management gateway device using WebSocket. The water management server according to claim 10.

12. Further include a database for storing the data structure created by the encoding processing unit. When the data structure is stored in the database, notify the water management gateway device that the data structure exists using WebSocket. The water management server according to claim 10.

13. A water management gateway device that transmits data output from the control device via a network and supplies data to be input to the control device received from the water management server via the network to the control device for executing information processing for controlling the water management facility via a control device for controlling the water management facility, having a data relay processing unit that converts the output data from the control device into character string data, creates a data structure corresponding to a format compliant with a protocol adapted to communication with the water management server via the network including the character string data, and transmits the data to the water management server according to the protocol. Water management gateway device.

14. The water management gateway device according to claim 13, wherein the data relay processing unit extracts the character string data from the data structure received from the water management server, reconverts it into the state of the instruction data, and transmits the instruction data to the control device.

15. The data relay processing unit periodically transmits an acquisition request for the data structure to the water management server. The water management gateway device according to claim 14.

16. The water management gateway device according to claim 14, wherein the data relay processing unit transmits a request for acquisition of the data structure to the water management server when receiving, via WebSocket, a notification from the water management server that the data structure exists.

17. A water management method for a water management server that executes information processing for controlling the water management facility via a control device that controls the water management facility, the water management server receives, according to the protocol, a data structure corresponding to a format compliant with a protocol applied to communication with a water management gateway device via a network, the data structure including string data obtained by converting output data of the control device; the water management server extracts the string data from the data structure received from the water management gateway device and reconverts it into the state of the output data; the water management server converts instruction data indicating an operation instruction for the water management facility for the control device created by the information processing into string data, and creates a data structure corresponding to the format compliant with the protocol for transmitting the string data to the water management gateway device via the network. Water management method.

Images