JP2018025854A - Power generation control system, maintenance device and control device - Google Patents

Abstract

PROBLEM TO BE SOLVED: To secure security of a network to which a control device is connected and allow a user to refer to a maintenance history and process data in the control device by a different network.SOLUTION: A power generation control system has a transmission device for allowing data transmission from a first network to a second network and blocking data transmission from the second network to the first network; a control device connected to the first network for controlling a power generation plant; and a maintenance device connected to the first network for acquiring a maintenance history of the control device from the control device and registering it with a maintenance history registration part. The control device transmits update information which allows identification of presence/absence of updating of the maintenance history. The maintenance device transmits a reading command of the maintenance history according to the update information. The control device transmits the maintenance history in response to the reading command and the maintenance device registers the maintenance history with the maintenance history registration part.SELECTED DRAWING: Figure 1

Description

  Embodiments described herein relate generally to a power generation control system, a maintenance device, and a control device.

  The power generation control network of the power plant is separated into a secure network (security network) and a non-security network (non-security network) by a data diode or the like.

  The security network includes a control device that controls the operation of the power plant, a maintenance tool that maintains the control device, an OPS (Operating Station) that provides a user interface, and a monitoring device that monitors the operation of the power plant via the control device. It is connected. On the other hand, the non-security network is connected to a monitoring device that monitors the operation of the power plant via a control device, a VPN (Virtual Private Network) device for connecting to a remote network via the Internet, and the like.

  In a power generation control network having a data diode, data transmission from the security network to the non-security network is allowed, but data transmission from the non-security network to the security network is blocked. This prevents intrusion into the security network and data tampering using the security network. Data in the control device on the security network (for example, data in the process of creating process data in the control device) can be referenced only by a human operation from a maintenance tool on the same security network.

JP 2014-146087 A

  In a power generation control network having a data diode, even if a monitoring device on a non-security network attempts to access a control device on the security network, a read instruction from the monitoring device to the control device is blocked. Therefore, the monitoring device on the non-security network cannot read the maintenance history and process data from the control device on the security network. Therefore, there is a problem that the maintenance history and process data in the control device cannot be referred to from a device on the remote network via the Internet.

  Therefore, an embodiment of the present invention provides a power generation control system and maintenance that enables maintenance history and process data in a control device to be referred to by devices on another network while ensuring the security of the network to which the control device is connected. It is an object to provide a device and a control device.

  A power generation control system according to an embodiment includes a transmission device that allows data transmission from a first network to a second network and blocks data transmission from the second network to the first network. The system further includes a control device that is connected to the first network and controls operation of the power plant. The system further includes a maintenance device connected to the first network and acquiring a maintenance history of the control device from the control device and registering the maintenance history in a maintenance history registration unit. The control device transmits update information that can specify whether or not the maintenance history is updated, and the maintenance device transmits an instruction to read the maintenance history in accordance with the update information. The control device transmits the maintenance history in response to the read instruction, and the maintenance device registers the maintenance history from the control device in the maintenance history registration unit.

  A power generation control system according to another embodiment includes a transmission device that allows data transmission from the first network to the second network and blocks data transmission from the second network to the first network. The system further includes a control device that is connected to the first network and controls operation of the power plant. The system further includes a maintenance device connected to the first network and acquiring a maintenance history of the control device from the control device and registering the maintenance history in a maintenance history registration unit. The control device transmits the maintenance history using the update of the maintenance history as a trigger. The maintenance device registers the maintenance history from the control device in the maintenance history registration unit.

  A power generation control system according to another embodiment includes a transmission device that allows data transmission from the first network to the second network and blocks data transmission from the second network to the first network. The system further includes a control device connected to the first network, collecting process data of a power plant, and registering the process data in a process data registration unit. The control device holds storage information indicating a storage location of the process data and a trigger condition for acquiring the process data from the storage location. When the trigger condition is satisfied, the control device acquires the process data from the storage location indicated by the storage information and registers the process data in the process data registration unit.

  A maintenance device according to another embodiment is used by being connected to a first network that allows data transmission to the second network and blocks data transmission from the second network. The maintenance device includes an update information receiving unit that receives update information that can specify whether or not the maintenance history of the control device is updated, from the control device connected to the first network, and according to the update information, A read instruction transmission unit that transmits a maintenance history read instruction to the control device. The maintenance device further includes a maintenance history receiving unit that receives the maintenance history from the control device and registers the maintenance history in a maintenance history registration unit in response to the read instruction.

  In addition, a control device according to another embodiment is used by being connected to a first network that allows data transmission to the second network and blocks data transmission from the second network. The control device, to the maintenance device connected to the first network, an update information transmission unit that transmits update information that can specify whether or not the maintenance history of the control device is updated, and according to the update information, And a read instruction receiving unit for receiving a maintenance history read instruction from the maintenance device. The control device further includes a maintenance history transmission unit that transmits the maintenance history to the maintenance device and registers the maintenance history in a maintenance history registration unit in response to the read instruction.

  In addition, a control device according to another embodiment is used by being connected to a first network that allows data transmission to the second network and blocks data transmission from the second network. The said control apparatus is provided with the holding | maintenance part which hold | maintains the storage information which shows the storage location of the process data of a power plant, and the trigger condition which acquires the said process data from the said storage location. The control device further includes a registration processing unit that acquires the process data from the storage location indicated by the storage information and registers the process data in a process data registration unit when the trigger condition is satisfied.

  According to the embodiment of the present invention, it is possible to make it possible to refer to the maintenance history and process data in the control device by a device on another network while ensuring the security of the network to which the control device is connected.

It is a schematic diagram which shows the structure of the electric power generation control system of 1st Embodiment. It is a figure for demonstrating the holding | maintenance data of the control apparatus of 1st Embodiment. It is a figure for demonstrating the data structure of the maintenance log | history of 1st Embodiment. It is a schematic diagram for demonstrating operation | movement of the electric power generation control system of 1st Embodiment. It is a schematic diagram for demonstrating operation | movement of the electric power generation control system of 2nd Embodiment. It is a schematic diagram for demonstrating operation | movement of the electric power generation control system of 3rd Embodiment. It is a flowchart which shows operation | movement of the control apparatus of 4th Embodiment. It is a figure for demonstrating operation | movement of the control apparatus of 4th Embodiment. It is a figure for demonstrating the holding | maintenance data of the control apparatus of 4th Embodiment. It is a schematic diagram for demonstrating operation | movement of the electric power generation control system of 5th Embodiment.

  Embodiments of the present invention will be described below with reference to the drawings. 1 to 10, the same or similar components are denoted by the same reference numerals, and redundant description is omitted.

(First embodiment)
Drawing 1 is a mimetic diagram showing the composition of power generation control system 1 of a 1st embodiment.

  FIG. 1 shows a power generation control system 1 that controls a power plant and a remote system 2 that can communicate with the power generation control system 1 via the Internet 3.

  The power generation control system 1 includes a security network 11 and a non-security network 12 as a power generation control network. The security network 11 is an example of a first network. The non-security network 12 is an example of a second network.

  The power generation control system 1 further includes a data diode 13 that separates the security network 11 and the non-security network 12. The data diode 13 is an example of a transmission device.

The power generation control system 1 further includes a plurality of control devices 14 _{1 to} 14 _N connected to the security network 11, a plurality of monitoring devices 15 ₁ to 15 _M , a plurality of OPS 16 _{1 to} 16 _L , a maintenance tool 17, and a non-security A monitoring device 18 and a VPN device 19 connected to the network 12 are provided. The maintenance tool 17 is an example of a maintenance device.

  On the other hand, the remote location system 2 includes a remote location network 21, a monitoring device 22 and a VPN device 23 connected to the remote location network 21.

Reference numerals N, M, and L represent the number of control devices 14 _{1 to} 14 _N , the number of monitoring devices 15 ₁ to 15 _M , and the number of OPS 16 _{1 to} 16 _L , respectively. Hereinafter, any _{one of} the control devices 14 _{1 to} 14 _N will be referred to as “control device 14” as appropriate. Similarly, any _one of the monitoring devices 15 ₁ to 15 _M is appropriately described as “monitoring device 15”, and any one of the OPS 16 _{1 to} 16 _L is appropriately described as “OPS 16”. . The same applies to other devices and device parts described later.

  The data diode 13 includes a transmission-only device 13a, a reception-only device 13b, and an optical communication cable 13c. The dedicated transmission device 13a is connected to the security network 11 and has only a transmission function as an optical communication function using the optical communication cable 13c. The reception-only device 13b is connected to the non-security network 12 and has only a reception function as an optical communication function using the optical communication cable 13c. The transmission-only device 13a and the reception-only device 13b are connected to each other by an optical communication cable 13c.

  Therefore, the data diode 13 allows data transmission from the security network 11 to the non-security network 12 and blocks data transmission from the non-security network 12 to the security network. Therefore, intrusion into the security network 11 and data tampering using the security network 11 can be prevented.

The control devices 14 _{1 to} 14 _N control the operation of the power plant, and control, for example, the state of equipment installed in the power plant and the process value of the fluid used in the power plant. The monitoring devices 15 ₁ to 15 _M monitor the operation of the power plant through the control devices 14 _{1 to} 14 _N. The OPS 16 _{1 to} 16 _L provide a user interface for issuing commands to the control devices 14 _{1 to} 14 _N. The maintenance tool 17 has a function of maintaining the control devices 14 _{1 to} 14 _N. Examples of the OPS 16 _{1 to} 16 _L and the maintenance tool 17 are computers such as a PC (Personal Computer).

The monitoring devices 18 and 22 monitor the operation of the power plant through the control devices 14 _{1 to} 14 _N , similarly to the monitoring devices 15 ₁ to 15 _M. The monitoring devices 18 and 22 can exchange data with each other via the VPN devices 19 and 23. However, although the monitoring devices 18 and 22 can receive data from the security network 11, they cannot transmit data to the security network 11.

FIG. 2 is a diagram for explaining data held in the control device 141 according to the _first embodiment. In the description of FIG. 2, description of the control device 14 ₁ apply equally to the other control units ₁₄ 2 to 14 _N. The same applies to the description of other figures described later.

The control device 14 ₁ can hold the user code 31 ₁ , user data 32 ₁ , setting value data 33 ₁ , and maintenance history 34 ₁ in the memory. User code 31 ₁ is a calculation program stored in the control device 14 ₁ by a command of the user. User data 32 ₁ is a data input and output in conjunction with this operation. Set value data 33 ₁ is data for setting values used in the calculation (constant). The maintenance history 34 ₁ is history information related to maintenance of the control device 14 ₁ .

FIG. 3 is a diagram for explaining the data structure of the maintenance history 341 according to the _first embodiment.

The maintenance history 34 ₁ in the memory of the control device 14 ₁ includes a final registration time 41 ₁ , a failure history 42 ₁ , a mode history 43 _1, and an operation history 44 ₁ .

The last registration time 41 ₁ represents the time when the maintenance history 34 ₁ was updated, that is, the time when the history information was last registered in the maintenance history 34 ₁ . The failure history 42 ₁ is history information regarding the abnormality detected by the diagnosis of the control device 14 ₁ . Mode history 43 ₁ is a history information recording upon detection of transition of the operation mode. The operation history 44 ₁ is history information regarding operations such as turning on / off the power of the control device 14 ₁ and changing the set value data 33 ₁ by the maintenance tool 17.

The failure history 42 ₁ , the mode history 43 ₁ , and the operation history 44 ₁ are stored in a cyclic list format in time series. In FIG. 3, the failure history 42 ₁ is stored in the form of circulating blocks 0 to α, the mode history 43 ₁ is stored in the form of circulating blocks 0 to β, and the operation history 44 ₁ is stored in the circulating block 0. It shows how it is stored in the form of γ.

  FIG. 4 is a schematic diagram for explaining the operation of the power generation control system 1 of the first embodiment.

The control devices 14 _{1 to} 14 _N periodically transmit final registration time notifications S _{1A to} S _NA for notifying their own final registration times 41 _{1 to} 41 _N to the maintenance tool 17. The maintenance tool 17 receives the last registration time notifications S _{1A to} S _NA from the security network 11.

Maintenance tools 17, when receiving the notification _S 1A _{to S NA,} notification received this time _S 1A _{to S NA} indicates the last registration time ₄₁ 1 to 41 _N is indicated by the notification _S 1A _{to S NA} previously received final It is confirmed whether or not the registration times 41 _{1 to} 41 _N are the same. For example, the last registration time 41 ₁ indicated by the notification _{S 1A} which received this time is different from the last registration time 41 ₁ indicated by the notification _{S 1A} previously received the service tool 17, maintenance control unit 14 ₁ History 34 ₁ Read instruction _S1B . The same applies to the other control devices 14 _{2 to} 14 _N. Further, even when starting the maintenance tools 17, maintenance tools 17 transmits a read instruction _S 1B _{to S NB} maintenance history ₃₄ 1 to 34C _N to the control device ₁₄ 1 to 14 _N.

For example, the control unit 14 _1, when updating the maintenance history ₃₄₁ before sending the current notification _{S 1A,} the last registration time 41 ₁ indicated by this notification _{S 1A} indicates the previous notice _{S 1A} to change from the last registration time 41 _1. Therefore, the maintenance tool 17 can specify whether or not the maintenance history 34 ₁ is updated from the notification S _1A . The final registration time 41 ₁ is an example of the update information. The function in which the control device 14 ₁ transmits the notification S _1A is an example of an update information transmission unit. The function in which the maintenance tool 17 receives the notification _S1A is an example of an update information receiving unit.

Therefore, the maintenance tool 17, the last registration time 41 ₁ indicated by the notification _{S 1A} which received this time is different from the last registration time 41 ₁ indicated by the notification _{S 1A} previously received, the control unit 14 ₁ of the maintenance history 34 ₁ There is judged to have been updated, and transmits the read instruction _{S 1B} maintenance history 34 ₁ to the controller 14 _1. The control device 14 ₁ receives the read instruction S _1B of the maintenance history 34 ₁ from the security network 11. Function maintenance tools 17 transmits a read instruction S _1B is an example of a read instruction transmission unit. Functions of the control unit 14 ₁ receives the read instruction S _1B is an example of a read instruction receiving unit.

When the control device 14 ₁ receives the reading instruction S _1B for the maintenance history 34 ₁ , the control device 14 ₁ reads the maintenance history 34 ₁ registered in the control device 14 ₁ , and sends the maintenance history notification S _1C to notify the maintenance history 34 ₁ to the maintenance tool. 17 to send. The maintenance tool 17 receives the maintenance history notification S _1C from the security network 11. Functions of the control unit 14 ₁ transmits a notification S _1C is an example of a maintenance history transmission unit. The function that the maintenance tool 17 receives the notification _S1C is an example of a maintenance history receiving unit.

Maintenance tools 17, when receiving the notification _{S 1C,} extracted with maintenance history ₃₄₁ indicated by the notification _{S 1C} received this time, the difference between the maintenance history ₃₄₁ indicated by the notification _{S 1C} previously received. This corresponds to the difference between the pre-update maintenance history 34 ₁ and the maintenance history 34 ₁ after the update. Then, the maintenance tool 17 registers the extracted difference in the maintenance history database 17a in the maintenance tool 17 as indicated by reference numeral _S1D . Thus, maintenance history 34 ₁ maintenance history database 17a is updated by the difference. The maintenance history database 17a is an example of a maintenance history registration unit.

Maintenance tool 17 holds the maintenance history ₃₄ 1 to 34C _N of the control unit ₁₄ 1 to 14 _N in the maintenance history database 17a. For example, the maintenance tool 17, when receiving the maintenance history notice S _1C from the control unit 14 _1, as described above, the maintenance history 34 ₁ maintenance history database 17a is updated by the difference. At this time, the last registration time 41 ₁ constituting the maintenance history 34 ₁ in the maintenance history database 17a is also updated to the latest time by the difference.

The maintenance tool 17 continuously monitors the reception status of the last registration time notifications S _{1A to} S _NA . For example, when the reception of the last registration time notification S _1A is not performed for a certain period, the maintenance tool 17 registers the abnormality of the control device 14 ₁ to the fault history 42 ₁ maintenance history database 17a.

  As described above, in this embodiment, the security network 11 and the non-security network 12 are separated by the data diode 13, and the control device 14 and the maintenance tool 17 are connected to the security network 11. Then, the control device 14 transmits a final registration time 41 that can specify whether or not the maintenance history 34 has been updated, and the maintenance tool 17 transmits an instruction to read the maintenance history 34 according to the final registration time 41. Further, the control device 14 transmits a maintenance history 34 in response to the reading instruction, and the maintenance tool 17 registers the maintenance history 34 from the control device 14 in the maintenance history database 17a.

  Therefore, according to the present embodiment, the maintenance history 34 of all the control devices 14 can be collectively managed by the maintenance tool 17 by using the last registration time 41. If the maintenance tool 17 continues to collect the maintenance history 34 without using the last registration time 41, the amount of data collected in the maintenance history 34 becomes enormous and it becomes difficult to continue the collection. However, since the maintenance tool 17 of the present embodiment can collect only the updated maintenance history 34 by using the last registration time 41, the amount of data collected in the maintenance history 34 can be reduced.

  Devices on the non-security network 12 cannot access the control device 14 or the maintenance tool 17. However, the maintenance tool 17 can transmit the maintenance history 34 collected in the maintenance history database 17 a to devices on the non-security network 12. Therefore, according to the present embodiment, the maintenance history 34 in the control device 14 can be referred to by devices on the non-security network 12 while securing the security network 11.

(Second Embodiment)
FIG. 5 is a schematic diagram for explaining the operation of the power generation control system 1 of the second embodiment.

Controller 14 ₁ of the first embodiment, when receiving the read instruction S _1B depending on the final registration time notification S _1A, triggered by reception of a read instruction S _1B, maintenance history registered in the control device 14 ₁ 34 ₁ is read (FIG. 4). Then, the control unit 14 ₁ of the first embodiment transmits the maintenance history notice _{S 1C} for notifying the maintenance history 34 ₁ to the maintenance tool 17 (FIG. 4).

On the other hand, the control device 14 of _the present embodiment, as the sign _{S 1E,} when the registered update the maintenance history 34 ₁ to the log information ₃₅₁ of the control unit 14 ₁ maintenance history 34 _1, maintenance history 34 as a trigger ₁ update, the controller 14 reads out the maintenance history ₃₄₁ registered in the ₁ (Figure 5). Then, the control device 14 of _the present embodiment transmits the maintenance history notice _{S 1C} for notifying the maintenance history 34 ₁ to the maintenance tool 17 (FIG. 5). In this way, maintenance tools 17 of this embodiment can be similar to the first embodiment, it collects maintenance history ₃₄ 1 to 34C _N of the control unit ₁₄ 1 to 14 _N.

When the notification S _1C is received, the maintenance tool 17 of the present embodiment, like the first embodiment, maintains the maintenance history 34 ₁ indicated by the notification S _1C received this time and the maintenance history indicated by the notification S _1C received last time. The difference from 34 ₁ is extracted. Then, the maintenance tool 17 of this embodiment registers the extracted difference in the maintenance history database 17a in the maintenance tool 17 as indicated by reference numeral _S1D .

According to this embodiment, as in the first embodiment, while ensuring the security of the security network 11, a maintenance history ₃₄ 1 to 34C _N of the control unit ₁₄ within one to 14 _N to the device on the non-security network 12 Can be referenced.

(Third embodiment)
FIG. 6 is a schematic diagram for explaining the operation of the power generation control system 1 of the third embodiment.

The maintenance tool 17 of this embodiment holds the maintenance histories 34 _{1 to} 34 _N registered by the method of the first or second embodiment in the maintenance history database 17a. Then, the maintenance tool 17 duplicates the maintenance histories 34 _{1 to} 34 _N in the maintenance history database 17 a to be copied to the maintenance history database 18 a in the monitoring device 18 as indicated by reference numeral MR. Specifically, the maintenance histories 34 _{1 to} 34 _N read from the maintenance history database 17a are transmitted from the security network 11 to the non-security network 12 via the data diode 13 and stored in the maintenance history database 18a. .

  Communication networks that require delivery confirmation such as TCP / IP (Transmission Control Protocol / Internet Protocol) cannot be used between networks separated by the data diode 13. Therefore, communication is performed between the maintenance tool 17 of the present embodiment and the monitoring device 18 using UDP / IP (User Datagram Protocol / Internet Protocol) that does not require delivery confirmation.

  Further, in communication between networks separated by the data diode 13, a destination MAC (Media Access Control) address cannot be acquired using ARP (Address Resolution Protocol). Therefore, duplication is performed by multicast communication between the maintenance tool 17 and the monitoring device 18 of the present embodiment.

  Note that the duplication of the present embodiment is executed using difference extraction, as in the case of registering the maintenance history 34 in the maintenance history database 17a. Specifically, when the maintenance tool 17 duplicates the maintenance history 34, the maintenance tool 17 extracts a difference between the maintenance history 34 transmitted this time and the maintenance history 34 transmitted last time, and the extracted difference is multicast communication. Send by. Further, the maintenance tool 17 can reflect the change in the maintenance history 34 in the maintenance history database 18a of the monitoring device 18 without missing by transmitting the difference a plurality of times (for example, twice).

  As described above, according to the present embodiment, the monitoring device 18 on the non-security network 12 can collect the maintenance history 34 of all the control devices 14 on the security network 11. Therefore, the monitoring device 22 on the remote network 21 can refer to the maintenance history 34 in the monitoring device 18 via the Internet 3.

(Fourth embodiment)
Figure 7 is a flowchart showing the operation of the control apparatus 14 ₁ of the fourth embodiment.

In the first to third embodiments, the maintenance histories 34 _{1 to} 34 _N of the control devices 14 _{1 to} 14 _N are registered or referred to. On the other hand, in the fourth and fifth embodiments, the process data of the power plant collected by the control devices 14 _{1 to} 14 _N is set as a registration or reference target. Examples of process data include time series data regarding the state of equipment installed in the power plant, time series data of process values of fluids used in the power plant, and the like. The process data is used, for example, to display the operation status of the power plant in a graph.

Figure 7 shows the flow of process data processing by the control unit 14 _1. Configuration of the control device 14 ₁ is installed power generation control system is as shown in FIG.

First, when the user inputs data for the control device 14 ₁ in any of the OPS 16 _{1 to} 16 _L , this data is stored in the user data 32 ₁ (see FIG. 2) of the control device 14 ₁ (step S1, input). processing).

Next, the control device 14 ₁ performs an operation based on the user code 31 ₁ using the user data 32 ₁ and the setting data 33 ₁ for the data acquired from the power plant, and calculates process data as the operation result (step S2). , Arithmetic processing).

The control device 14 ₁ stores this process data in the user data 32 ₁ . On the other hand, the control device 14 ₁ performs a collection process for collecting predetermined process data from the user data 32 ₁ (step S3, collection process). Details of the collection process will be described later.

Next, the control device 14 ₁ outputs the process data stored in the user data 32 ₁ to the above OPS 16 _{1 to} 16 _L (step S4, output processing).

Thereafter, the control device 14 ₁ repeats the processing in steps S1 to S4 (step S11, S12).

Figure 8 is a diagram for explaining a control apparatus 14 ₁ of the operation of the fourth embodiment.

Controller 14 ₁ of the present embodiment includes the process data database (DB) 14a ₁ for registering the process data. The same applies to the other control devices 14 _{2 to} 14 _N. The process data DB 14a ₁ is an example of a process data registration unit.

In the collection process, the control unit 14 ₁ collects a predetermined process data from the user data 32 _1, as shown at _{S 1F,} registers the collected process data to the process data DB 14 a _1. The reason is that if all process data is transmitted to the outside of the security network 11, the amount of process data transmitted becomes enormous, so that the process data to be transmitted is limited. Details of the process data transmission processing will be described later.

Figure 9 is a diagram for explaining the data held in the control unit 14 ₁ of the fourth embodiment.

Controller 14 ₁ of the present embodiment, as data for collection process, and a collection point information 51 and the trigger condition information 52 can be held in memory. The collection point information 51 and the trigger condition information 52 are set in advance by the maintenance tool 17 or the OPS 16 _{1 to} 16 _L. In the description of FIG. 9, for convenience of description, the symbols of the collection point information 51 and the trigger condition information 52 are simply abbreviated as “51” and “52” instead of “51 ₁ ” and “52 ₁ ”. The same applies to other codes related to the collection point information 51 and the trigger condition information 52.

Collection point information 51 is information about the location (point) of the control device 14 ₁ comes to collect process data during the collection process. The collection point information 51 includes a digital collection point number 61 that holds the number X of digital process data collection locations, an analog (integer) collection point number 62 that holds a number Y of analog (integer) process data collection locations, And an analog (real number) collection point 63 that holds the number Z of analog (real number) process data collection locations. The collection point information 51 further includes a digital collection point 64 indicating X collection locations of digital process data, an analog (integer) collection point 65 indicating Y collection locations of analog (integer) process data, and an analog. And an analog (real number) collection point 66 indicating Z collection locations of (real number) process data.

In the arithmetic processing of the present embodiment, the operation process data is stored in the control device 14 ₁ in the predetermined register. The collection points 64, 65, and 66 hold pointers that point to registers that collect process data. The register is an example of a storage location of process data, and the pointer is an example of storage information indicating the storage location of process data.

Trigger condition information 52 is information about the trigger condition controller 14 ₁ acquires the process data from the register during the collection process. Controller 14 _1, if the trigger condition is satisfied, and registers the process data DB 14 a ₁ acquires the process data from the register indicated by the pointer. The trigger condition information 52 includes a trigger condition 71, a trigger point 72, trigger data 73, and a collection duration 74 after the trigger.

  The trigger condition 71 indicates conditions such as “ON”, “OFF”, “process data> threshold”, and “process data ≦ threshold”. A trigger point 72 indicates a point to which the trigger condition 71 is applied. The trigger data 73 indicates data to be applied to the trigger condition 71 such as the above threshold value. The post-trigger collection continuation time 74 indicates a time during which the collection process is continued after the trigger condition 71 is satisfied. The trigger condition information 52 is set for each of the collection points 64, 65, 66, for example.

For example, if the trigger condition 71 is "ON", the process data in the register is the trigger point 72 points is stored, the control unit 14 ₁ is registered in the process data DB 14 a ₁ acquires the process data from the register. This registration process is continued for the time indicated by the post-trigger collection continuation time 74. On the other hand, if the trigger condition 71 of "OFF", be stored process data in the register is the trigger point 72 points, the controller 14 ₁ does not obtain the process data from the register.

Also, if the trigger condition 71 is "Process Data>threshold", the process data in the register in which the trigger point 72 points exceeds a threshold value, the control unit 14 _1, the process data DB 14 a ₁ acquires the process data from the register sign up. As the threshold value, the value of the trigger data 73 is used. This registration process is continued for the time indicated by the post-trigger collection continuation time 74. The inequality sign “>” may be replaced with other equal signs or inequality signs (=, <, ≧, ≦).

  The trigger condition 71 may be a combination of a plurality of conditions. The trigger condition 71 may be, for example, ““ process data> first threshold ”AND“ process data <second threshold ”” or ““ process data> first threshold ”OR“ process data <second threshold ””.

  As described above, in this embodiment, the security network 11 and the non-security network 12 are separated by the data diode 13, and the control device 14 is connected to the security network 11. And the control apparatus 14 hold | maintains the collection point information 51 and the trigger condition information 52, and when a trigger condition is satisfied, acquires process data from a register and registers it in process data DB14a. The former function of the control device 14 is an example of a holding unit, and the latter function of the control device 14 is an example of a registration processing unit.

  Therefore, according to the present embodiment, by using the collection point information 51 and the trigger condition information 52, it becomes possible to register predetermined data of the process data of the control device 14 in the process data DB 14a. If the control device 14 continues to register the process data in the process data DB 14a without using the collection point information 51 and the trigger condition information 52, the registration amount of the process data becomes enormous and registration is difficult. However, since the control device 17 of the present embodiment can register only predetermined process data in the process data DB 14a by using the collection point information 51 and the trigger condition information 52, the registration amount of the process data is reduced. Can be reduced.

  Devices on the non-security network 12 cannot access the control device 14. However, the control device 14 can transmit the process data registered in the process data DB 14a to a device on the non-security network 12. Therefore, according to the present embodiment, the process data in the control device 14 can be referred to by devices on the non-security network 12 while ensuring the security of the security network 11.

  Moreover, according to this embodiment, the control apparatus 14 can collect and register process data for every control period of FIG. That is, the control device 14 can collect and register process data in step S3 every time the process data is calculated once in step S2. Therefore, according to the present embodiment, process data that is more detailed than the maintenance history 34 can be provided to devices on the non-security network 12. For example, devices on the non-security network 12 can display the operation status of the power plant in a graph using process data.

(Fifth embodiment)
FIG. 10 is a schematic diagram for explaining the operation of the power generation control system 1 of the fifth embodiment.

Each controller ₁₄ 1 to 14 _N of the present embodiment holds a process data registered by the method of the fourth embodiment in the process data DB14a within ₁ to 14A _N. Then, the control unit ₁₄ 1 to 14 _N copies as indicated at _MR 1 _{~MR N,} the process data in the process data DB 14 a ₁ to 14A _N to process data DB18b ₁ ~18b _N in the monitoring apparatus 18 duplicates I do. Specifically, the process data read from the process data DBs 14a _{1 to} 14a _N is transmitted from the security network 11 to the non-security network 12 via the data diode 13 and stored in the process data DBs 18b _{1 to} 18b _N. .

  The duplicating method of this embodiment is the same as that of the third embodiment. In the duplicate of this embodiment, UDP / IP and multicast communication can be applied as in the third embodiment.

  As described above, according to the present embodiment, the monitoring device 18 on the non-security network 12 can collect the process data of all the control devices 14 on the security network 11. Therefore, the monitoring device 22 on the remote network 21 can refer to the process data in the monitoring device 18 via the Internet 3.

  Although several embodiments have been described above, these embodiments are presented as examples only and are not intended to limit the scope of the invention. The novel systems and devices described herein can be implemented in a variety of other forms. In addition, various omissions, substitutions, and changes can be made to the system and apparatus modes described in the present specification without departing from the scope of the invention. The appended claims and their equivalents are intended to include such forms and modifications as fall within the scope and spirit of the invention.

1: Power generation control system, 2: Remote system, 3: Internet
11: Security network, 12: Non-security network,
13: data diode, 13a: dedicated device for transmission, 13b: dedicated device for reception,
13c: optical communication cable, 14: control device, 14a: process data database,
15: Monitoring device, 16: OPS, 17: Maintenance tool,
17a: maintenance history database, 18: monitoring device, 18a: maintenance history database,
18b: Process data database, 19: VPN device,
21: Remote network, 22: Monitoring device, 23: VPN device,
31: User code, 32: User data,
33: set value data, 34: maintenance history, 35: log information,
41: last registration time, 42: failure history, 43: mode history, 44: operation history,
51: Collection point information, 52: Trigger condition information,
61: Number of digital collection points, 62: Number of analog (integer) collection points,
63: Analog (real number) collection points, 64: Digital collection points,
65: Analog (integer) collection point, 66: Analog (real) collection point,
71: Trigger condition, 72: Trigger point,
73: Trigger data, 74: Collection duration after trigger

Claims (10)

A transmission device that allows data transmission from the first network to the second network and blocks data transmission from the second network to the first network;
A controller connected to the first network for controlling the operation of the power plant;
A maintenance device connected to the first network and acquiring a maintenance history of the control device from the control device and registering it in a maintenance history registration unit;
The control device transmits update information that can specify whether or not the maintenance history is updated,
The maintenance device transmits an instruction to read the maintenance history according to the update information,
The control device transmits the maintenance history in response to the read instruction,
The maintenance device registers the maintenance history from the control device in the maintenance history registration unit;
Power generation control system.   The power generation control system according to claim 1, wherein the update information indicates a time when the maintenance history is updated by the control device. A transmission device that allows data transmission from the first network to the second network and blocks data transmission from the second network to the first network;
A controller connected to the first network for controlling the operation of the power plant;
A maintenance device connected to the first network and acquiring a maintenance history of the control device from the control device and registering it in a maintenance history registration unit;
The control device transmits the maintenance history triggered by the update of the maintenance history,
The maintenance device registers the maintenance history from the control device in the maintenance history registration unit;
Power generation control system.   The power generation control system according to any one of claims 1 to 3, wherein the maintenance device registers a difference between the maintenance history before update and the maintenance history after update in the maintenance history registration unit. And a monitoring device connected to the second network for storing the maintenance history in a maintenance history storage unit,
The maintenance device transmits the maintenance history in the maintenance history registration unit from the first network to the second network;
The monitoring device stores the maintenance history received from the maintenance device in the maintenance history storage unit;
The power generation control system according to any one of claims 1 to 4. A transmission device that allows data transmission from the first network to the second network and blocks data transmission from the second network to the first network;
A control device connected to the first network, collecting power plant process data, and registering the process data in a process data registration unit;
The control device holds storage information indicating a storage location of the process data, and a trigger condition for acquiring the process data from the storage location,
The control device acquires the process data from the storage location indicated by the storage information and registers it in the process data registration unit when the trigger condition is satisfied,
Power generation control system. And a monitoring device connected to the second network and storing the process data in a process data storage unit,
The control device transmits the process data in the process data registration unit from the first network to the second network,
The monitoring device stores the process data received from the control device in the process data storage unit.
The power generation control system according to claim 6. A maintenance device used by being connected to a first network that allows data transmission to a second network and blocks data transmission from the second network,
An update information receiving unit for receiving update information capable of specifying whether or not the maintenance history of the control device is updated from the control device connected to the first network;
In response to the update information, a read instruction transmission unit that transmits a read instruction for the maintenance history to the control device;
In response to the read instruction, a maintenance history receiving unit that receives the maintenance history from the control device and registers the maintenance history in a maintenance history registration unit;
A maintenance device comprising: A control device used by being connected to a first network in which data transmission to a second network is permitted and data transmission from the second network is blocked;
An update information transmitting unit that transmits update information that can specify whether or not the maintenance history of the control device is updated to the maintenance device connected to the first network;
A read instruction receiving unit that receives a read instruction of the maintenance history from the maintenance device according to the update information;
A maintenance history transmission unit that transmits the maintenance history to the maintenance device and registers the maintenance history in a maintenance history registration unit in response to the read instruction;
A control device comprising: A control device used by being connected to a first network in which data transmission to a second network is permitted and data transmission from the second network is blocked;
A storage unit for storing storage information indicating a storage location of the process data of the power plant, and a trigger condition for acquiring the process data from the storage location;
A registration processing unit that acquires the process data from the storage location indicated by the storage information and registers it in a process data registration unit when the trigger condition is satisfied;
A control device comprising:

Images