JP6091449B2 - Control system - Google Patents

Description

  The present invention manages and maintains consistency in a plurality of maintenance tools in a control system for controlling a plant or the like even when the management server changes the setting data held by the maintenance tools when performing maintenance. It relates to a control system that can.

  In the conventional control system, the manager's management node determination unit determines what can become a manager from among a plurality of agents before the manager itself fails, and stores it in the management node storage unit of the current agent. When the manager monitoring unit detects a failure of the manager, the management request unit requests the agent to shift to the manager (see, for example, Patent Document 1).

JP 2009-128987 A

  In a general conventional control system, a plurality of control devices are installed, and maintenance tools for installing and setting programs are prepared for each control device. Then, the maintenance tool holds the program installed in the control device and various settings as management data. When maintenance work is performed with a plurality of maintenance tools, the management data of the control device held by each maintenance tool needs to maintain consistency.

  Usually, one maintenance tool is used as a management server, and other maintenance tools take a method of referring management data to a maintenance tool that is a management server as necessary. However, this method has a problem that maintenance by another maintenance tool cannot be performed when the maintenance tool as the management server is stopped.

  In addition, as in the control system disclosed in Patent Document 1, when a failure occurs in the manager to be managed, even if the manager is switched to a new manager at an early stage, if the management data is not taken over, the maintenance work is continued. There was a problem that could not be done.

  In addition, since the management data is centrally managed by the maintenance tool that is the management server, there is a problem that the management data is destroyed when the maintenance tool that is the management server fails.

  The present invention has been made to solve the above-described problems, and an object thereof is to provide a control system capable of preventing the loss of setting data in response to a change in the management server.

A control system according to the present invention is a control system including a plurality of maintenance tools for performing maintenance on a plurality of control devices.
The plurality of maintenance tools are connected via a maintenance network,
The plurality of maintenance tools have a function of autonomously becoming a management server,
One of the plurality of maintenance tools serves as the management server,
The management server manages a plurality of setting data for maintaining the plurality of control devices, and distributes the plurality of setting data to the other maintenance tools,
The other maintenance tool stores a plurality of the setting data ,
When the management server receives that the setting data of the other maintenance tool has been changed, the management server distributes the setting data to the other maintenance tool, and the other maintenance tool receives the changed setting. The data is updated.
The control system of the present invention is a control system including a plurality of maintenance tools for performing maintenance on a plurality of control devices.
The plurality of maintenance tools are connected via a maintenance network,
The plurality of maintenance tools have a function of autonomously becoming a management server,
One of the plurality of maintenance tools serves as the management server,
The management server manages a plurality of setting data for maintaining the plurality of control devices, and distributes the plurality of setting data to the other maintenance tools,
The other maintenance tool stores a plurality of the setting data,
The maintenance tool distributes the setting data changed by itself to the other maintenance tool and the management server,
The other maintenance tool and the management server update the changed setting data.
The control system of the present invention is a control system including a plurality of maintenance tools for performing maintenance on a plurality of control devices.
The plurality of maintenance tools are connected via a maintenance network,
The plurality of maintenance tools have a function of autonomously becoming a management server,
One of the plurality of maintenance tools serves as the management server,
The management server manages a plurality of setting data for maintaining the plurality of control devices, and distributes the plurality of setting data to the other maintenance tools,
The other maintenance tool stores a plurality of the setting data,
The management server sets the occupation of the setting data of the maintenance tool during maintenance of the control device.

  Since the control system of the present invention is configured as described above, it is possible to prevent the setting data from being lost when the management server is changed.

It is a figure which shows the structure of the control system of Embodiment 1 of this invention. It is a figure which shows the structure of the management data of the control system shown in FIG. It is a figure which shows the procedure of the control system shown in FIG. It is a figure which shows the procedure of the control system shown in FIG. It is a figure which shows the procedure of the control system shown in FIG. It is a figure which shows the procedure of the control system shown in FIG. It is a figure which shows the procedure of the control system shown in FIG. It is a figure which shows the procedure of the control system shown in FIG. It is a figure which shows the procedure of the control system shown in FIG. It is a flowchart which shows operation | movement of the control system shown in FIG. It is a flowchart which shows operation | movement of the control system shown in FIG. It is a flowchart which shows operation | movement of the control system shown in FIG. It is a flowchart which shows operation | movement of the control system shown in FIG. It is a flowchart which shows operation | movement of the control system shown in FIG. It is a figure which shows the structure of the management table of the control system shown in FIG. It is a figure which shows the structure of the management table of the control system shown in FIG. It is a figure which shows the structure of the data used with the control system shown in FIG. It is a figure which shows the structure of the data used with the control system shown in FIG. It is a figure which shows the structure of the data used with the control system shown in FIG. It is a figure which shows the structure of the data used with the control system shown in FIG. It is a figure which shows the structure of the data used with the control system shown in FIG. It is a figure which shows the structure of the data used with the control system shown in FIG. It is a figure which shows the structure of the data used with the control system shown in FIG. It is a figure which shows the structure of the data used with the control system shown in FIG. It is a figure which shows the structure of the data used with the control system shown in FIG. It is a figure which shows the structure of the data used with the control system shown in FIG. It is a figure which shows the structure of the data used with the control system shown in FIG. It is a figure which shows the structure of the data used with the control system shown in FIG. It is a figure which shows the procedure of the control system of Embodiment 2 of this invention. 30 is a flowchart showing an operation of the control system shown in FIG. 29. 30 is a flowchart showing an operation of the control system shown in FIG. 29. It is a figure which shows the structure of the data used with the control system shown in FIG. It is a figure which shows the structure of the data used with the control system shown in FIG. It is a figure which shows the structure of the management table of the control system in Embodiment 3 of this invention. It is a flowchart which shows operation | movement of the control system in Embodiment 3 of this invention. It is a figure which shows the structure of the management table of the control system in Embodiment 4 of this invention. It is a flowchart which shows operation | movement of the control system in Embodiment 4 of this invention. It is a flowchart which shows operation | movement of the control system in Embodiment 5 of this invention.

Embodiment 1 FIG.
Embodiments of the present invention will be described below. 1 is a diagram showing a configuration of a control system according to Embodiment 1 of the present invention. FIG. 2 is a diagram showing a configuration of management data of the control system shown in FIG. 3 to 9 are diagrams showing a procedure of the control system shown in FIG. 10 to 14 are flowcharts showing the operation of the control system shown in FIG. 15 and 16 are diagrams showing the configuration of the management table of the control system shown in FIG. 17 to 28 are diagrams showing the structure of data used in the control system shown in FIG.

  In the figure, the control system controls the plant 10. And the control apparatus 111-11n which controls the plant 10 is provided. These control devices 111 to 11n are connected by a network 11 for plant monitoring / control. And maintenance tools 120-12n which perform maintenance and operation of these control devices 111-11n are formed. The control devices 111 to 11n and the maintenance tools 120 and 121 to 12n are connected by a maintenance network 12.

  The maintenance tools 120 and 121 to 12n respectively have management data 130 and 131 to 13n in which data necessary for performing maintenance of the system and the control devices 111 to 11n is stored. One of the maintenance tools 120 and 121 to 12n is a management server that manages the versions of the management data 130 and 131 to 13n, and the other is a normal maintenance tool that performs only maintenance.

The management data 130 and 131 to 13n of the maintenance tools 120 and 121 to 12n are configured as shown in FIG. The management data 130 and 131 to 13n are composed of common setting data 300 that holds common setting data of the control system, and setting data 301 to 30n of the control devices 111 to 11n that hold maintenance data for each of the control devices 111 to 11n. Is done.
The common setting data 300 includes an ID 3001, a version 3002, and a plurality of common data 1 to m3003 to 3003m. The control device 111 setting data 301 includes an ID 3011, a version 3012, programs 1 to x3013 to 3013x, and setting data 3014.

  In this control system, there are a normal maintenance tool and a maintenance tool functioning as a management server among a plurality of maintenance tools. However, which of the plurality of maintenance tools is a management server or a normal maintenance tool is described by appropriately setting in the description of the operation, but is not limited to the setting. Since this is the same in the following embodiments, the description thereof will be omitted as appropriate.

  Next, the operation of the control system of the first embodiment configured as described above will be described. First, the operation for determining the management server when the maintenance tool 120 is connected to the maintenance network 12 and activated will be described with reference to FIG. As shown in FIG. 3, the maintenance tool 120 is connected to the maintenance network 12 and activated (step S200 in FIG. 10). Next, the activated maintenance tool 120 has “management server inquiry 20” data with its own IP address attached as shown in FIG. 17 to all the maintenance tools 121 to 12m to 12n other than itself. Is broadcast (step S201 in FIG. 10).

  As shown in FIG. 4, when the maintenance tool (management server) 12m already exists, the maintenance tool (management server) 12m that is being activated is in operation. Whether or not there is (step S210 in FIG. 10), it becomes YES, and “management server inquiry 20” is received (step S212 in FIG. 10). Next, the maintenance tool (management server) 12m determines whether or not it is a management server (step S213 in FIG. 10). Here, the determination of the maintenance tool (management server) 12m is YES, and the activation state of the corresponding part of the inquiry source maintenance tool 120 in the management table 40 as shown in FIG. Step S214 in FIG.

  Next, “management server response 21” data attached with its own IP address as shown in FIG. 19 is returned to the inquiry source maintenance tool 120 (step S215 in FIG. 10). Next, the maintenance tool 120 determines whether or not the “management server response 21” is received within a predetermined time (step S202 in FIG. 10). When the returned “management server response 21” is received (YES), the IP address of the maintenance tool (management server) 12m of the transmission source included in the received “management server response 21” is used as the management server. Setting is made (step S203 in FIG. 10). Then, the maintenance tool 120 is activated as a normal maintenance tool (step S204 in FIG. 10).

  Also, as shown in FIG. 5, when there is no maintenance tool (management server), the active maintenance tools 121 to 12n indicate whether or not the maintenance tools 121 to 12n are operating (FIG. 10). In step S210), the answer is YES. At this time, if there is a maintenance tool that is stopped, the determination is NO, and the “management server response 21” cannot be transmitted (step S211 in FIG. 10).

  Next, “management server inquiry 20” is received (step S212 in FIG. 10). Next, when the maintenance tools 121 to 12n determine whether or not they are management servers (step S213 in FIG. 10), the process is terminated because the result is NO (step S216 in FIG. 10). "Management server response 21" is not returned. Therefore, since the maintenance tool 120 does not receive the “management server response 21” after waiting for the “management server response 21” for a certain time (step S202 in FIG. 10) (NO), the maintenance tool (management server) 120 is the management server. The function is activated (step S205 in FIG. 10).

  Next, as shown in FIG. 18, the data of “management server declaration notification 22” with its own IP address attached is broadcast to all the maintenance tools 121 to 12n (step S206 in FIG. 10). The maintenance tool (management server) 120 operates as a management server.

  Next, a case where the control system is operating normally will be described with reference to FIG. Here, a case where the maintenance tool (management server) 12m operates as a management server will be described with reference to FIG. Normally, as shown in FIG. 6, the maintenance tool (management server) 12m is periodically attached with its own IP address as shown in FIG. 20 to the other maintenance tools 120, 121 to 12n. Data of “management server existence notification 23” is transmitted by broadcast.

  As shown in FIG. 20, the “management server survival notification 23” indicates the priority of transfer of the active maintenance tools 120 and 121 to 12n managed by the maintenance tool (management server) 12m to the management server. And a management data table 2302 including version information of setting data stored in the maintenance tools 120 and 121 to 12n.

  Then, another maintenance tool, for example, the maintenance tool 120, determines whether or not the “management server existence notification 23” is received within a predetermined time (step S240 in FIG. 12). Next, when the maintenance tool 120 receives the “management server survival notification 23” (YES), the maintenance tool 120 sets the “management server transfer priority” of each maintenance tool in the “management server survival notification 23” in FIG. As shown, it is stored in the management table 50 (step S241 in FIG. 12).

  Then, the maintenance tool 120 transmits to the maintenance tool (management server) 12m “management server existence notification response 24” including its version information and attached with its own IP address as shown in FIG. (Step S242 in FIG. 12). Then, the maintenance tool 120 waits for reception of the “management server existence notification 23” again (step S240 in FIG. 12). On the other hand, when the maintenance tool (management server) 12m receives the “management server existence notification response 24” as shown in FIG. 21 from other maintenance tools, each maintenance in the management table 50 shown in FIG. Update the tool activation status.

  Next, a case where the maintenance tool (management server) 12m is stopped will be described with reference to FIG. First, as shown in FIG. 7, the maintenance tool (management server) 12m is requested to stop, and the stop process is started (step S220 in FIG. 11). Next, the maintenance tool (management server) 12m searches the management table 40 shown in FIG. 15A for the maintenance tool with the highest “management server transfer priority” (step S222 in FIG. 11).

  The searched maintenance tool becomes the maintenance tool 121. Next, as shown in FIG. 7, the maintenance tool (management server) 12m transmits data of “management server authority transfer 25” attached with its own IP address as shown in FIG. 22 (FIG. 11). Step S223). At this time, as is apparent from FIG. 22, version information of each setting data is attached together.

  Next, the maintenance tool 121 that has received the “management server authority transfer 25” data determines whether or not it is operating (step S230 in FIG. 11). If it is not in operation (NO), the “management server authority transfer response 26” cannot be transmitted (step S231 in FIG. 11). If it is in operation (YES), “management server authority transfer 25” is received (step S232 in FIG. 11). Next, the version information of the setting data of the management data 132 held by itself, the version information of the setting data of the management data 13m managed by the management server, transmitted by “management server authority transfer 25”, Are compared (step S233 in FIG. 11).

  Next, it is determined whether or not the version of the setting data is correct (step S234 in FIG. 11). If they do not match (NO), the setting data corresponding to the version not matching is acquired from the maintenance tool (management server) 12m (step S237 in FIG. 11). Then, when the version of the setting data is correct (YES) and after step S237, the maintenance tool 121 activates the function as the management server (step S235 in FIG. 11).

  Next, the maintenance tool 121 notifies the maintenance tool (management server) 12m of “management server authority transfer response 26” data with its own IP address as shown in FIG. 23 (step in FIG. 11). S236). Then, the maintenance tool (management server) 12m determines whether or not the “management server authority transfer response 26” is received within a predetermined time (step S224 in FIG. 11). Therefore, when the “management server authority transfer response 26” is received from the maintenance tool 121, this determination is YES, and the maintenance tool (management server) 12m performs a stop process (step S225 in FIG. 11).

  If the “management server authority transfer response 26” is not transmitted as in step S231, the maintenance tool (management server) 12m waits for a response for a certain time in step S224 (NO in step S224 in FIG. 11). Next, a maintenance tool having a higher management server transfer priority is searched (step S226 in FIG. 11), and the above-described operation is repeated. As a result, even when the maintenance tool for transferring the authority of the management server is stopped, the authority of the management server can be transferred to another maintenance tool.

  Next, a case where the maintenance tool (management server) 12m cannot execute the stop process as described above due to a failure or the like will be described with reference to FIG. First, as shown in FIG. 8, when the maintenance tool (management server) 12m stops due to a failure or the like, the maintenance tool (management server) 12m stops. Therefore, the transmission of the “management server existence notification 23” of the maintenance tool (management server) 12m is stopped.

  Then, the other maintenance tools do not receive the “management server existence notification 23” for a certain period of time (NO in step S240 in FIG. 12). Next, each of the other maintenance tools determines that the management server has stopped, and determines whether or not its “management server transfer priority” is the highest (step S243 in FIG. 12). Next, the “management server transfer priority” is the highest. Here, since the maintenance tool 121 is No. 1, it is determined to be YES. The other maintenance tools 120 to 12n are determined as NO because they are not the first.

  Then, the maintenance tool 121 activates the management server function (step S244 in FIG. 12). Next, the maintenance tool 121 broadcasts the data of the “management server declaration notification 22” attached with its own IP address as shown in FIG. 18 to all the other maintenance tools 120, 12m to 12n. (Step S245 in FIG. 12). In addition, the maintenance tool whose “management server transfer priority” is the second or later becomes NO in step S243, and enters into a determination waiting state whether or not the “management server declaration notification 22” has been received within a certain period of time. (Step S246 in FIG. 12).

  When the “management server declaration notification 22” is received from the maintenance tool 121 (YES), the maintenance tool 121 that is the transmission source of the “management server declaration notification 22” is set as the management server (step S248 in FIG. 12). Then, the process ends (step S249 in FIG. 12). If “management server declaration notification 22” is not received for a certain period of time (NO in step S246 in FIG. 12), each maintenance tool increments “management server transfer priority” one by one (step S247 in FIG. 12). ). And the operation | movement after step S243 shown above is repeated.

  Next, a process for keeping the management data in the same content in all the maintenance tools will be described with reference to FIGS. Here, as shown in FIG. 9, the management server is assumed to be a maintenance tool (management server) 120, and the maintenance work of the maintenance tool 12m will be described as an example. First, in order to request the maintenance tool (management server) 120 to occupy the setting data to be subjected to the maintenance work before performing the maintenance work, as shown in FIG. Request 30 "is transmitted (step S300 in FIG. 13). As shown in FIG. 24, the version information of the setting data held by itself is added to the data of “setting data occupation request 30”.

  Next, the maintenance tool (management server) 120 receives the “setting data occupation request 30” (step S310 in FIG. 13). Next, the maintenance tool (management server) 120 checks the occupation state of the setting data in the management table 41 as shown in FIG. 15B (step S311 in FIG. 13). Next, if the setting data to be requested is already in the occupied state, it is determined that it is already occupied, and an occupation non-permission is transmitted to the maintenance tool 12m (step S312 in FIG. 13). Next, since the maintenance tool 12m determines whether or not occupancy is permitted (step S302 in FIG. 13), if occupancy is not permitted, the determination is NO and the maintenance operation is terminated (step S303 in FIG. 13). ).

  If the setting data to be requested is not in the occupied state, it is determined that the setting data is not occupied and notified from the maintenance tool 12m of the data of “setting data occupation request 30” transmitted as shown in FIG. The version of the set data and the version of the set data stored in the maintenance tool (management server) 120 is confirmed (step S313 in FIG. 13). If the versions do not match, the management server setting data is transmitted to the maintenance tool 12m (step S315 in FIG. 13).

  If the versions match or if step S315 is performed, the control device 111 setting data of the management table 41 is set to the occupied state by the maintenance tool 12m as shown in FIG. As shown in FIG. 25, “setting data occupation permission 31” is transmitted with its own IP address attached (step S314 in FIG. 13). Next, since the maintenance tool 12m determines whether or not occupancy is permitted (step S302 in FIG. 13), if occupancy is permitted (YES), the maintenance work of the control device 111 for the permitted setting data is performed. Is implemented (step S304 in FIG. 13).

  Next, when the maintenance tool 12m finishes the maintenance work, the version of the setting data changed by the maintenance work and the setting data version of the “setting data occupation permission 31” received from the maintenance tool (management server) 120 are displayed. Check. If they are different, the setting data and version information of the setting data are attached with their own IP addresses as shown in FIG. 26, and “setting data transmission 32” is sent to the maintenance tool (management server) 120. Transmit (step S306 in FIG. 13). Then, the maintenance work of the maintenance tool 12m ends (step S307 in FIG. 13).

  Then, the maintenance tool (management server) 120 receives “setting data transmission 32” (step S320 in FIG. 13). Next, the setting data managed by itself is updated to the setting data of the “setting data transmission 32” received (step S321 in FIG. 13). Next, as shown in FIG. 15B, the occupation of the corresponding portion of the setting data in the management table 41 is released (step S322 in FIG. 13). Next, the maintenance tool (management server) 120 attaches its own IP address to the updated version information of the setting data, as shown in FIG. 27, and sends “setting data version notification 33” to all the maintenance tools. 121, 12m to 12n (step S323 in FIGS. 13 and 14).

  Next, for example, the maintenance tool 12n receives the “setting data version notification 33” (step S330 in FIG. 14). Next, the maintenance tool 12n compares the setting data version in the management data 13n held by the maintenance tool 12n with the setting data version of the “setting data version notification 33” (step S331 in FIG. 14). Next, it is determined whether or not the versions are different (step S332 in FIG. 14). If it is determined that they are not different (NO), the process ends (step S334 in FIG. 14). Here, the case where it is determined that there is no difference is a process that can be considered in the maintenance tool 12m that has performed the maintenance work.

  If it is determined that they are different (YES), the “setting data request 34” data attached with its own IP address as shown in FIG. 28 is transmitted to the maintenance tool (management server) 120 (FIG. 28). 14 step S333). Next, the maintenance tool (management server) 120 receives this “setting data request 34” (step S324 in FIG. 14). Next, as shown in FIG. 26, the requested setting data is attached to the requesting maintenance tool 12n, the version information of the setting data and the setting data is attached, and the “setting data transmission 32” is attached. It transmits as data (step S325 of FIG. 14).

  Next, the maintenance tool 12n as the request source receives “setting data transmission 32” as shown in FIG. 26 (step S335 in FIG. 14). Next, the maintenance tool 12n updates the setting data in the management data 13n held by itself to the received setting data (step S336 in FIG. 14). By performing as described above, the management data can be centrally managed and the same management data can be held in all the maintenance tools.

  The control system according to the first embodiment configured as described above has a plurality of control devices and maintenance tools as components, and each maintenance tool performs the maintenance of the control device. Since it has a function to hold data and determine the management server autonomously, maintenance is performed without depending on a specific maintenance tool, and management data is also detected due to a failure of the management server or a specific maintenance tool. Can be prevented from being lost.

  In addition, since the management server that centrally manages the management data held by the maintenance tool is installed, it has the function of determining the management server autonomously without giving the management server a specific maintenance tool. Because the management server's management data is centrally managed on the management server, the same setting data is held in all maintenance tools, so that maintenance can be performed and specific maintenance can be performed without depending on the specific maintenance tool. It is possible to prevent the setting data from being lost due to the failure of the tool.

  In addition, since the changed setting data is updated in the setting data of other maintenance tools in the management server, the same setting data can be reliably held in all the maintenance tools.

Further, since the management server is changed depending on the priority, the management server is set as appropriate.
In addition, the management server occupies the setting data of the maintenance tool that performs maintenance of the control device, and the maintenance of the control device is exclusively controlled by the maintenance tool. Can be prevented.

Embodiment 2. FIG.
In the first embodiment, after the maintenance tool performs maintenance work, the maintenance tool transmits the setting data difference information to the management server, and distributes the setting data difference information to the other maintenance tools via the management server. However, the present invention is not limited to this, and in the second embodiment, after the maintenance work is performed, the maintenance tool distributes the changed setting data directly to another maintenance tool after performing the maintenance work. The management data can be synchronized without going through the management server.

  FIG. 29 is a diagram for explaining the operation of the control system according to the second embodiment of the present invention. 30 and 31 are flowcharts for explaining the operation of the control system according to the second embodiment of the present invention. 32 and 33 are diagrams showing the structure of data used in the second embodiment of the present invention. Since the configuration of the control system is the same as that of the first embodiment, description thereof will be omitted as appropriate, and description will be made using the same configuration as that of the first embodiment.

  Next, in the second embodiment, the operation after the maintenance tool performs maintenance work, which is different from the first embodiment, will be described with reference to FIGS. Since other operations are the same as those in the first embodiment, description thereof will be omitted as appropriate. First, as shown in FIG. 29, through the same process as in the first embodiment, the maintenance tool (management server) performs the data transmission of “setting data occupation permission 31” (step S314 in FIG. 30). Further, through the same process as in the first embodiment, the maintenance tool in maintenance work confirms the version of the setting data (step S340 in FIG. 30).

  Next, as shown in FIG. 27, the maintenance tool under maintenance work attaches its own IP address and transmits the “setting data version notification 33” data to all maintenance tools (step of FIG. 30). S341). Next, as shown in FIG. 32, the data of “setting data occupation release request 35” is transmitted to the maintenance tool (management server) with its own IP address attached (step S342 in FIG. 30). The maintenance tool (management server) receives this “setting data occupation release request 35” (step S350 in FIG. 30).

  Next, the maintenance tool (management server) releases the occupation of the setting data corresponding to the “setting data occupation release request 35” in the management table 41 as shown in FIG. 15B (step S351 in FIG. 30). ). Next, the maintenance tool (management server) attaches its own IP address and transmits the “setting data occupation release notification 36” data to the maintenance tool as shown in FIG. 32 (step S352 in FIG. 30). ), The process is terminated (step S353 in FIG. 30).

  Next, the maintenance tool in maintenance work receives “setting data occupation release notification 36” (step S343 in FIG. 30) and ends the maintenance work (step S344 in FIG. 30). Then, the maintenance tool in maintenance work goes through the previous step S344, and the other maintenance tools go through the same steps as in the first embodiment, so the description thereof is omitted.

  Further, when the maintenance tool in maintenance operation receives “setting data request 34” from another maintenance tool (step S347 in FIG. 31), the requested setting data is extracted (step S348 in FIG. 31). Next, the extracted setting data and the version information of the setting data are attached with their own IP addresses and transmitted as “setting data transmission 32” data as shown in FIG. 26 (step S349 in FIG. 30). .

  According to the control system of the second embodiment configured as described above, the maintenance work is performed by synchronizing the management data after performing the maintenance work as well as the same effects as the first embodiment. Since the maintenance tool performs, the load on the management server can be reduced, and the management data can be synchronized even when the management server becomes temporarily unavailable.

Embodiment 3 FIG.
In each of the above embodiments, an example has been shown in which all maintenance tools can be migrated to the management server. However, in this case, depending on the type and operation of the maintenance tool, the power may be turned on when not in use. There may be a maintenance tool that has a specification of failure when it becomes a management server, such as blocking. Therefore, in the third embodiment, by registering in advance maintenance tools that can be transferred to the management server, maintenance tools that are not suitable for the management server are prevented from moving to the management server. Is.

  FIG. 34 is a diagram showing the configuration of the management server transfer priority management table in each maintenance tool according to Embodiment 3 of the present invention. FIG. 35 is a flowchart showing the operation of the control system in the third embodiment of the present invention. Since the configuration of the control system is the same as that of the first embodiment, description thereof will be omitted as appropriate, and description will be made using the same configuration as that of the first embodiment. In the third embodiment, only the operation of starting the maintenance tool, which is different from the first embodiment, will be described. Since other operations are the same as those in the first embodiment, description thereof will be omitted as appropriate.

Next, in the third embodiment, the operation of starting the maintenance tool, which is different from the first embodiment, will be described with reference to FIG. Since other operations are the same as those in the first embodiment, description thereof will be omitted as appropriate. First, as in the above embodiments, when the maintenance tool is activated (step S200 in FIG. 35), it is determined whether or not the management table 51 can be transferred to the management server (step S207 in FIG. 35). If it is determined that the management server can be migrated (YES), the operations after step S201 are performed in the same manner as in the above embodiments.
If it is determined that the management server cannot be migrated (NO), it is activated as a normal maintenance tool (step S208 in FIG. 35).

  According to the control system of the third embodiment configured as described above, the same effects as those of the above-described embodiments can be obtained, and maintenance tools that can be migrated to the management server are registered in advance. Therefore, it is possible to prevent a maintenance tool that is not suitable for the management server from being activated as the management server.

Embodiment 4 FIG.
In each of the above embodiments, each maintenance tool shows an example in which maintenance work of an arbitrary control device can be performed, and exclusive control of maintenance work of the control device is realized by occupying the management server. It was. However, if the management server stops during the maintenance work, the exclusive control cannot be performed, and the maintenance work may not be performed. In the fourth embodiment, a maintenance tool for performing maintenance for each control device is uniquely determined, thereby eliminating the need for exclusive control by occupation on the management server.

  FIG. 36 is a diagram showing the configuration of the management table showing the relationship between each control device and the maintenance tool in the fourth embodiment of the present invention. FIG. 37 is a flowchart showing the operation of the control system in the fourth embodiment of the present invention. Since the configuration of the control system is the same as that of the first embodiment, description thereof will be omitted as appropriate, and description will be made using the same configuration as that of the first embodiment. In the fourth embodiment, only the operation of maintenance work in the maintenance tool, which is different from the first embodiment, will be described. Since other operations are the same as those in the first embodiment, description thereof will be omitted as appropriate.

  Next, in the fourth embodiment, the operation of the maintenance work of the maintenance tool, which is different from the first embodiment, will be described with reference to FIG. Since other operations are the same as those in the first embodiment, description thereof will be omitted as appropriate. First, before performing maintenance work, the maintenance tool checks the control device that can be maintained by the management table 52 shown in FIG. 36 (step S400 in FIG. 37). Next, maintenance work is performed on the confirmed control device (step S401 in FIG. 37). Subsequent processes are the same as the processes from step S341 of the second embodiment, and thus description thereof is omitted as appropriate.

  According to the control system of the fourth embodiment configured as described above, the same effects as those of the above-described embodiments can be obtained, and any maintenance tool can be installed without performing exclusive control in the management server. By performing maintenance of the control device that is managed by the user, exclusive control of the management server becomes unnecessary, and the load on the management server can be reduced.

Embodiment 5. FIG.
In each of the above embodiments, an example in which the maintenance work of the maintenance tool is managed by the management server has been described. However, the present invention is not limited to this, and in the fifth embodiment, the maintenance work of the maintenance tool is controlled by the control device. A case where management is performed will be described.

  FIG. 38 is a flowchart showing operations of the maintenance tool and the control device according to the fifth embodiment of the present invention. Since the configuration of the control system is the same as that of the first embodiment, description thereof will be omitted as appropriate, and description will be made using the same configuration as that of the first embodiment. In the fifth embodiment, only the operation of the maintenance tool and the control device, which is different from the first embodiment, will be described. Since other operations are the same as those in the first embodiment, description thereof will be omitted as appropriate.

  Next, in the fifth embodiment, the operation when the maintenance tool of the control system performs the maintenance work of the control device, which is different from the first embodiment, will be described with reference to FIG. Since other operations are the same as those in the first embodiment, description thereof will be omitted as appropriate. First, the maintenance tool transmits a maintenance work start notification to the control device (step S500 in FIG. 38). Then, it waits for reception of maintenance work permission (step S501 in FIG. 38).

  Next, the control device receives a maintenance work start notification from the maintenance tool (step S510 in FIG. 38). Next, the control device determines whether another maintenance tool is already undergoing maintenance work (step S511 in FIG. 38). If another maintenance tool is performing maintenance work (YES), a maintenance work disapproval is transmitted to the maintenance tool (step S512 in FIG. 38). If no other maintenance tool is performing maintenance work (NO), the status is set to maintenance work, and maintenance work permission is transmitted to the maintenance tool (step S513 in FIG. 38).

  Then, the maintenance tool determines whether or not maintenance work is permitted (step S502 in FIG. 38). If the maintenance work is not permitted (NO), the maintenance work is terminated (step S503 in FIG. 38). If the maintenance work is permitted (YES), the maintenance work is performed (step S504 in FIG. 38). Next, the setting data is updated and the version information of the setting data is confirmed (step S505 in FIG. 38). Next, as shown in FIG. 27, the data of “setting data version notification 33” is transmitted with its own IP address attached (step S506 in FIG. 38).

  Next, the end of the maintenance work is transmitted to the control apparatus that has been performing the maintenance (step S507 in FIG. 38). Next, the control device receives the end of the maintenance work (step S514 in FIG. 38). Next, the state is cleared (not under maintenance work), a maintenance work end confirmation is transmitted to the maintenance tool (step S515 in FIG. 38), and the process is ended (step S516 in FIG. 38). Then, the maintenance tool receives the confirmation of the completion of the maintenance work (step S508 in FIG. 38) and ends the processing (step S508 in FIG. 38).

  According to the control system of the fifth embodiment configured as described above, the same effects as those of the above-described embodiments can be obtained, and even if the management server is temporarily disabled during maintenance work, Maintenance work can be performed from any maintenance tool.

  It should be noted that the present invention can be freely combined with each other within the scope of the invention, and each embodiment can be appropriately modified or omitted.

10 plant, 11 plant monitoring and control network,
12 maintenance network, 111 control device, 11n control device,
120 maintenance tools, 121 maintenance tools, 12m maintenance tools, 12n maintenance tools, 130 management data, 131 management data, 13m management data, 13n management data, 300 shared setting data, 301 control device 111 setting data,
30n Control device 11n setting data.

Claims (8)

In a control system having a plurality of maintenance tools for performing maintenance on a plurality of control devices,
The plurality of maintenance tools are connected via a maintenance network,
The plurality of maintenance tools have a function of autonomously becoming a management server,
One of the plurality of maintenance tools serves as the management server,
The management server manages a plurality of setting data for maintaining the plurality of control devices, and distributes the plurality of setting data to the other maintenance tools,
The other maintenance tool stores a plurality of the setting data ,
When the management server receives that the setting data of the other maintenance tool has been changed, the management server distributes the setting data to the other maintenance tool, and the other maintenance tool receives the changed setting. A control system that updates data. In a control system having a plurality of maintenance tools for performing maintenance on a plurality of control devices,
The plurality of maintenance tools are connected via a maintenance network,
The plurality of maintenance tools have a function of autonomously becoming a management server,
One of the plurality of maintenance tools serves as the management server,
The management server manages a plurality of setting data for maintaining the plurality of control devices, and distributes the plurality of setting data to the other maintenance tools,
The other maintenance tool stores a plurality of the setting data ,
The maintenance tool distributes the setting data changed by itself to the other maintenance tool and the management server,
The other maintenance tool and the management server are control systems that update the changed setting data. The control system according to claim 1 or 2, wherein when the management server is changed to another maintenance tool, the management server is changed based on a priority of the other maintenance tool. The plurality of the maintenance tool, the control system according to any one of claims 1 to 3, whether or not it is possible to change to the management server is configured. The management server, the control system according to any one of claims 1 to 4 to set the setting data occupancy of the maintenance tool while performing maintenance of the control device. The control system according to any one of claims 1 to 4 , wherein which of the plurality of maintenance tools is set as to which of the control devices is to be maintained. The plurality of the maintenance tool, the maintenance work of the controller, any of claims 1 to 4 in which the other of the maintenance tool from the control unit receives that are servicing work is not performed the maintenance The control system according to claim 1. In a control system having a plurality of maintenance tools for performing maintenance on a plurality of control devices,
The plurality of maintenance tools are connected via a maintenance network,
The plurality of maintenance tools have a function of autonomously becoming a management server,
One of the plurality of maintenance tools serves as the management server,
The management server manages a plurality of setting data for maintaining the plurality of control devices, and distributes the plurality of setting data to the other maintenance tools,
The other maintenance tool stores a plurality of the setting data,
The management server is a control system for setting an occupation of the setting data of the maintenance tool during maintenance of the control device.

Images