JP2013161309A - Simulator software replacement device, method, and program - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide a simulator software replacement technique reducing workload caused by replacement and easily checking the soundness of the entire system after the replacement.SOLUTION: A simulator software replacement device includes: an acquiring unit 21 for acquiring real machine control software after a change; an acquiring unit 23 for acquiring simulation software before the change; dividing units 22 and 24 for dividing them for every execution block; a block comparing unit 25 for comparing the execution blocks for every unit; a block extraction unit 26 for extracting execution blocks in which differences are detected by the comparison; a block change unit 27 for changing the format of the extracted execution blocks into format for simulation software; and a block supply unit 28 for supplying the simulation software before the change with the format-changed execution block to generate simulation software after the change.

Description

  The present invention relates to a simulator soft replacement technique for training an operator.

A simulator is a training device that simulates operation control of a power plant, etc., and process signals for boilers, turbines, generators, etc. are virtually realized by a data processor so that training can be performed with the same feeling as operating an actual power plant. Designed to.
By using this simulator, training corresponding to accidents that can hardly be experienced in actual driving can be repeated, so that operators can be trained effectively in a short period of time.

  In many cases, such a simulator is obtained by diverting control software for a power plant (actual machine), and is constructed by converting the actual machine control software. When the actual machine control software is changed, the simulation software needs to be changed (replaced) following the change.

Such replacement work is required to be carried out reliably and simply.
As a conventional technique pursuing the realization of such a requirement, there is disclosed a technique for reducing adjustment impact at the time of replacement using a signal path bypass means when replacing an existing computer with a new computer in an analysis system (for example, Patent Document 1).

JP 2004-102901 A

  However, the above-described conventional technique only guarantees the soundness of the operation outside the change target before and after the replacement, and does not simplify the replacement work itself. In addition, the soundness of the entire system after replacement cannot be confirmed.

  The present invention has been made in view of such circumstances, and an object thereof is to provide a software replacement technology for a simulator that can reduce the amount of work involved in replacement and easily check the soundness of the entire system after replacement. To do.

  The simulator software replacement apparatus according to the present invention includes an acquisition unit that acquires the actual machine control software after the change, an acquisition unit that acquires simulation software before the change corresponding to the actual machine control software before the change, and the actual machine control software after the change. And a dividing unit that divides each of the simulation software before change into execution blocks, a block comparison unit that compares the execution blocks between the actual machine control software after change and the simulation software before change, and the comparison A block extracting unit for extracting an execution block of the changed actual machine control software in which a difference is detected; a changing unit for changing the format of the extracted execution block for simulation software; and the format changed execution block To the pre-change simulation software. Characterized in that it comprises a and a feeding section for generating a change after the simulation software corresponding to the actual control software after the changes.

  According to the present invention, there is provided a software replacement technique for a simulator that can reduce the amount of work involved in replacement and can easily check the soundness of the entire system after replacement.

1 is an overall block diagram showing an embodiment of a simulator software replacement apparatus according to the present invention. (A) The circuit diagram of the execution block which comprises simulation software, (B) The figure which shows the state value (ON, OFF) which each circuit has. The detailed block diagram of the software replacement apparatus of the simulator which concerns on embodiment. The detailed block diagram of the software replacement apparatus of the simulator which concerns on embodiment.

Hereinafter, embodiments of the present invention will be described with reference to the accompanying drawings.
As shown in FIG. 1, a plant simulator software replacement apparatus 10 (hereinafter simply referred to as “apparatus 10”) controls a storage unit 11 for storing modified actual machine control software such as a plant, and a plant simulator. Holding unit 13 that holds the simulation software before change (corresponding to the actual machine control software before change) and holding that holds the simulation software after change (corresponding to the actual machine control software after change) Change the changed range (execution block) of the real machine control software after the change to the simulation software format and change the other range to the simulation software after the change by using the simulation software before the change Operation history created by range converter 15 and pre-change simulation software An operation confirmation unit 16 that confirms the operation of the simulation software after the change based on the information, a behavior comparison unit 17 that compares the behavior simulated based on the common operation history information (operation information) before and after the change, The modification evaluation unit 18 compares the behavior before and after the change and evaluates the modification point of the simulation software after the change.

When the plant operation simulator is generated by diverting (converting) the actual machine control software of the plant, it is necessary to change the simulation software following the change of the actual machine control software.
By configuring the apparatus 10 in this way, the amount of replacement (change) work is reduced in simulation software having a format different from that of the actual machine control software.
In addition, it is possible to easily and surely evaluate the operational soundness of the simulation software after the change.

  As shown in FIG. 1, the simulation software is configured by a plurality of execution blocks as execution units. The actual machine control software is also composed of an assembly (not shown) of a plurality of execution blocks having a corresponding relationship with the execution blocks of the simulation software.

  As shown in FIG. 2A, one execution block is composed of a plurality of logic circuits. The format of this execution block is the type of circuit (OR circuit, AND circuit, NOT circuit) constituting this execution block, the connection information between these circuits, and the execution number of these circuits (notations (1) to ( 7)).

  The execution block program is, for example, “circuit type AND, execution number (5); the first input of the circuit type NOT of the execution number (4) is connected to the first input, and the execution number (2) is input to the third input. The first output of the circuit type OR is connected, and the first output of the circuit type AND of the execution number (3) is connected to the fifth input.

  As shown in FIG. 2B, the state value (ON, OFF) of each circuit is uniquely determined according to the state value input to the execution block depending on the connection relation of the circuit. . The simulation software is designed such that the state values for all the circuits are initially registered in order to set the initial state of the plant simulator.

As shown in FIG. 1, the change range conversion unit 15 compares the simulation software before change with the actual machine control software after change for each execution block, and extracts an execution block having a difference in circuit configuration. In addition, in the execution block in which the difference occurs in this way, the state value difference extraction unit 30 that initially registers the usable state value among the state values before the change as the state value after the change is configured.
Thereby, the correction range after the change can be reduced by effectively using the initial value of the state value lost when the actual machine control software is used as simulation software.

The operation confirming unit 16 reshapes the operation history information created by the simulation software before the change for the operation confirmation of the simulation software after the change, and the operation history information thus shaped after the change. The operation history test execution unit 50 executes the operation check of the simulation software.
By comparing the monitoring information obtained in this way with the monitoring information of the operation history information before the change, it is possible to easily check the soundness of the entire simulation software after the change.

  The behavior comparison unit 17 includes a driving history difference evaluation unit 60 that evaluates a difference in information related to the driving operation of the device among the monitoring information reproduced by the simulation software after the change based on the driving history information, and a process of the monitoring information. It is comprised from the driving | operation trend difference evaluation part 70 which evaluates the difference of the trend information regarding a behavior.

  And finally, in the correction evaluation part 18, the correction location in the simulation software after a change is specified based on the evaluation result of the driving history difference evaluation part 60 and the driving trend difference evaluation part 70. This shortens the lead time associated with soft replacement.

  As illustrated in FIG. 3, the circuit difference extraction unit 20 includes an acquisition unit 21 that acquires the actual machine control software (file X) after the change, an acquisition unit 23 that acquires simulation software (file Y) before the change, and the post-change The actual machine control software (file X) and the simulation software before change (file Y) are divided into execution blocks (files X1... Xn, Y1... Yn), and the actual machine control software after change (file X) and the block comparison unit 25 for comparing execution blocks (files X1... Xn, Y1... Yn) between the simulation software before change (file Y) and the actual machine control after change in which a difference is detected by this comparison. A block extraction unit 26 for extracting a software execution block (file X4), and the extracted execution block (file X4) The block changing unit 27 for changing the format to the simulation software (file Y′4) and the execution block (file Y′4) whose format has been changed are input to the simulation software before change and the simulation software after change (file Y) And a block input unit 28 for generating ').

  Here, the block comparison unit 25 can perform comparison by shaping the compared execution blocks (files Xn, Yn) into text items having “circuit type”, “execution number”, and “connection information” as keys, respectively. To do. Then, the execution block (file X4) of the actual machine control software having an inconsistent item is extracted by the block extraction unit 26.

  The state value difference extraction unit 30 executes a state value extraction unit 31 that extracts a circuit state value (file Z) from the pre-change simulation software (file Y), and the actual machine control software in which a difference is detected by the block extraction unit 26 The circuit comparison unit 32 that compares the circuits in units between the block (file X4) and the execution block (file Y4) of the simulation software before change is extracted by the state value extraction unit 31 for circuits that have not been changed in this comparison. A circuit-state value correspondence unit 33 that associates state values, and a state value input unit 34 that inputs the corresponding state values (file Z ′) to the simulation software after the change are provided.

Here, the circuit comparison unit 32 confirms whether or not the execution blocks (files X4 and Y4) to be compared match or do not match in the order of execution numbers, using “circuit type”, “execution number”, and “connection information” as keys. . Then, the circuit-state value corresponding unit 33 adopts the state value of the file Z, regarding the circuit before the execution number where the mismatched item is detected as being unchanged, and the circuit after this execution number is changed. Assuming that the status value is blank, the file Z ′ is created.
The state value input unit 34 overwrites the file Z ′ with the file Z to generate post-change simulation software (file Y ′).

  As a result, when starting the simulation software (file Y ′) after the change, it is not necessary to perform the initial registration of the state value from the zero state, so the lead time at the time of replacement is shortened.

  As shown in FIG. 4, the history information shaping unit 40 acquires the pre-change operation history information (file P) from the pre-change simulation software (file Y), and the acquired pre-change operation history information (file P) information extraction unit 42 for extracting device operation information (file Q) and monitoring information (file R) from the extracted operation information (file Q) based on the extracted operation information (file Q), operation history test execution unit And a creation unit 43 that creates a test file (file Q ′) to be executed by 50.

Here, the monitoring information (file R) includes information (file R1) related to the operation operation of the device or trend information (file R2) related to the process behavior.
Information related to the operation of the equipment (file R1) is information such as the open / closed state, rotation speed, and output of equipment (eg, valves, motors, etc.) constituting the plant. Trend information (file R2) is the plant information. Information such as a measurement value of a measuring instrument (for example, a thermometer, a pressure gauge, or a flow meter) disposed in

  The operation history difference evaluation unit 60 and the operation trend difference evaluation unit 70 are each changed operation history information (file P ′) generated by the changed simulation software (file Y ′) executing the test file (file Q ′). Are acquired by the acquisition units 62 and 72, and the monitoring information (file R ′) of the device is extracted from the operation history information after change (file P ′) acquired by the acquisition units 62 and 72. The detection units 63 and 73 that detect the difference between the monitoring history information (file R) of the pre-change operation history information (file P) and the creation units 64 and 74 that create reports on the detected difference. I have.

  The operation history difference evaluation unit 60 performs evaluation based on information (files R1, R'1) relating to the operation operation of the device among the monitoring information (files R, R '). The driving trend difference evaluation unit 70 performs evaluation based on trend information (files R2, R'2) regarding process behavior in the monitoring information (files R, R ').

  Here, the detection units 63 and 73 use the monitoring information (files R and R ′) to be compared as information (files R1 and R′1) regarding the operation of the device using “time axis” and “time width” as keys, respectively. ) And the response state of trend information (files R2, R′2) relating to process behavior. And the report preparation parts 64 and 74 record the difference before and after a change as a comparison result irrespective of the presence or absence of the obstruction | occlusion requirement of training operation | movement.

  The correction evaluation unit 18 evaluates and estimates the correction point of the execution block (file Y′4) whose format has been changed for the simulation software based on the differences detected by the detection units 63 and 73. And this correction evaluation part 18 is provided with the preparation part (illustration omitted) which produces the report about this evaluated correction point.

  Based on the evaluation report (not shown) obtained from the driving history difference evaluation unit 60 and the driving trend difference evaluation unit 70, the correction evaluation unit 18 determines the causal relationship between the operation and the behavior in the different parts before and after the software change. "Execution time" and "Plant behavior tendency after operation" are estimated as keys and output as a report This shortens the lead time associated with soft replacement.

The present invention is not limited to the above-described embodiments, and can be appropriately modified and implemented within the scope of the common technical idea.
For example, the simulator soft replacement device is exemplified by a software replacement device of a training device (simulator) that simulates plant operation control. However, the present invention is not limited to this, and the present invention can be widely applied to software correction that involves changing the file format.
Further, each means can be realized as each function program by a computer, and can be operated as a software replacement program of a simulator in which each function program is combined.

  DESCRIPTION OF SYMBOLS 10 ... Software replacement apparatus, 11 ... Storage part of machine control software after actual change, 13 ... Holding part of simulation software before change, 14 ... Holding part of simulation software after change, 15 ... Change range conversion part, 16 ... Operation check part , 17 ... Behavior comparison unit, 18 ... Correction evaluation unit, 20 ... Circuit difference extraction unit, 21 ... Actual software acquisition unit (acquisition unit), 22, 24 ... Block division unit (division unit), 23 ... Simulation software acquisition unit ( Acquisition unit), 25 ... block comparison unit, 26 ... block extraction unit, 27 ... block change unit (change unit), 28 ... block input unit, 30 ... state value difference extraction unit, 31 ... state value extraction unit, 32 ... circuit Comparison unit 33 ... Circuit-state value correspondence unit (corresponding unit) 34 ... State value input unit 40 ... History information shaping unit 41, 61, 71 ... Pre-change history information acquisition unit (acquisition unit) 42 Operation Monitoring information extraction unit (information extraction unit), 43 ... test file creation unit, 50 ... operation history test execution unit, 60 ... operation history difference evaluation unit, 62, 72 ... history information acquisition unit after change (acquisition unit), 63 ... Operational operation difference detection unit (detection unit), 64, 74 ... report creation unit, 70 ... operation trend difference evaluation unit, 73 ... process behavior difference detection unit, X ... actual machine control software after change, X1-Xn ... change Execution block of subsequent real machine control software, Y: simulation software before change, Y1 to Yn: execution block of simulation software before change, Y ′: simulation software after change, Z: state value of simulation software before change, P: before change Operation history information, Q ... equipment operation information, Q '... test file, R ... monitoring information of simulation software before change, R' ... simulation software after change Monitoring information, R1 (R'1) ... information related to the operation of the device, R2 (R'2) ... trend information related to the process behavior.

Claims (9)

An acquisition unit that acquires the actual machine control software after the change,
An acquisition unit for acquiring simulation software before change corresponding to the actual machine control software before change;
A dividing unit that divides each of the real machine control software after the change and the simulation software before the change into execution blocks;
A block comparison unit for comparing the execution block between the actual machine control software after the change and the simulation software before the change;
A block extraction unit that extracts an execution block of the actual machine control software after the change in which a difference is detected by the comparison;
A change unit for changing the format of the extracted execution block for simulation software;
A plant simulator software, comprising: a block input unit that inputs the execution block whose format has been changed to the simulation software before change and generates post-change simulation software corresponding to the actual control software after change Replace device. In the plant simulator soft replacement device according to claim 1,
A state value extraction unit for extracting a circuit state value from the pre-change simulation software;
A circuit comparison unit that compares circuits in units between the execution block of the actual machine control software after the change in which the difference is detected and the execution block of the simulation software before the change,
For a circuit that has not been changed in the comparison, a corresponding unit that corresponds to the extracted state value;
A plant simulator software replacement device comprising: a state value input unit that inputs the corresponding state value to the simulation software after change. In the plant simulator soft replacement device according to claim 1 or 2,
An acquisition unit that acquires operation history information before change from the simulation software before change;
An information extraction unit for extracting device operation information and monitoring information from the acquired pre-change operation history information;
A plant simulator software replacement device, comprising: a test file creation unit that creates a test file for executing the simulation software after change based on the extracted operation information. In the plant simulator soft replacement device according to claim 3,
The plant replacement software replacement apparatus characterized in that the monitoring information is information relating to operation of the equipment or trend information relating to process behavior. In the plant simulator soft replacement device according to claim 3 or 4,
An acquisition unit for acquiring post-change operation history information generated by executing the test file by the post-change simulation software;
A plant simulator soft replacement device, comprising: a detection unit that extracts equipment monitoring information from the acquired post-change operation history information and detects differences from the pre-change operation history information. In the plant simulator soft replacement device according to claim 5,
A plant simulator soft replacement apparatus comprising: a correction evaluation unit that evaluates a correction point of the execution block whose format has been changed based on the detected difference. In the plant simulator soft replacement device according to claim 5 or 6,
A plant simulator soft replacement device, comprising: a report creation unit that creates a report for the detected difference or the evaluated correction point. A step of acquiring the actual machine control software after the change;
Obtaining pre-change simulation software corresponding to the actual machine control software before change;
Dividing the actual control software after the change and the simulation software before the change into execution blocks;
Comparing the execution block in units between the actual machine control software after the change and the simulation software before the change;
Extracting an execution block of the changed real machine control software in which a difference is detected by the comparison;
Reformatting the extracted execution block format for simulation software;
And a step of generating the post-change simulation software corresponding to the post-change actual machine control software by inputting the format-changed execution block into the pre-change simulation software, and a plant simulator software replacement method comprising: . Computer
Means to obtain the actual machine control software after the change,
Means for obtaining pre-change simulation software corresponding to the actual machine control software before change,
Means for dividing each of the real machine control software after the change and the simulation software before the change into execution blocks;
Means for comparing the execution block in units between the actual machine control software after the change and the simulation software before the change;
Means for extracting an execution block of the actual machine control software after the change in which a difference is detected by the comparison;
Means for changing the format of the extracted execution block for simulation software;
A plant simulator software replacement program which functions as means for generating the post-change simulation software corresponding to the post-change actual machine control software by inputting the execution block whose format has been changed to the pre-change simulation software .

Images