JPH04352002A - Operation supporting device - Google Patents

Abstract

PURPOSE:To make it possible to restart an original procedure even after completion of abnormality occurrence and to output peoper guidance in an operation supporting device. CONSTITUTION:An operation supporting device for inferring a scenario being a procedure sequence necessary for the execution of an applied operation target and outputting the scenario to guide an operation procedure to an operator is provided with the 1st memory 1 for storing the 1st knowledge base for inferring the scenario and the 2nd memory 2 for storing the 2nd knowledge base for inferring an operation target appropriate for a current state, the operation target appropriate for the current state is selected based upon the 2nd knowledge base and the scenario is inferred under the operation target selected based upon the 1st knowledge base.

Description

[Detailed description of the invention]

0001

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to an operation support device which is applied to support the operation of a plant, and which not only outputs operation guides to operators, but also outputs the operation itself as a plant operation signal via an actuator.

0002

2. Description of the Related Art In large-scale plants such as power plants and chemical plants, manuals are prepared for operating the plant in normal and abnormal situations, and standard operations are possible. However, what is written in the operating manual is only the standard operating procedure for typical cases, and operators deal with each individual case while considering the meaning and effects of the operation. That is, it is human ability to perform appropriate driving operations according to the momentary situation, such as changing the execution order of a series of driving operation items, adding or omitting them, etc.

[0003] Therefore, a system has been developed that computerizes the driving instructions and outputs a driving guide according to the situation.In addition to a series of standard driving operations, driving operation items are hierarchized by purpose and function, In some cases, improvements have been made to enable output of a certain degree of flexible driving guidance by allowing for conditional branching and conditional cancellation.

[0004] Patent relating to improved example
034, Japanese Patent Application No. 63-163913), an overview of the prior art will be explained. In the following, we will refer to "fulfillment of operational objectives" such as "starting up the plant", "achievement of functions" such as "establishment of filling/extraction flows", and "execution of operational operations" such as "adjustment of filling/extraction source valves". collectively referred to as "execution of procedures".

FIG. 6 is an explanatory diagram of a flexible operation procedure. In other words, the startup operation procedure for a PWR plant is as follows:
Step A: Plant start-up is placed at the top, and this is performed by executing steps A1: Establishment of filling/extraction flow, A2: Start-up of primary coolant pump, etc., which are one step lower. Procedure A
1: To establish the filling/extraction flow, the specific operating steps a: Adjust the filling/extraction flow source valve, b: Open the filling high pressure injection pump source valve, c.
This is accomplished by: starting the filling high-pressure pump, d: adjusting the filling flow rate, and e: adjusting the extraction line pressure. A2: The primary coolant pump is achieved by performing f: startup check, g: sequential startup of the primary coolant pump, and h: extraction line pressure adjustment.

However, at this time, the most standard method is to perform in the order of abcdefgh, but depending on the case, it may be performed in the order of basedfgh, or e
As a result of the extraction line pressure adjustment in h, if that state is maintained, the extraction line pressure adjustment in h may be omitted. In Figure 6, the symbol "→" indicates something that must be executed in the order of execution, such as A1→A2 or f→g.
The symbol "=" is used to indicate that either one can be executed first, such as a=b or d=e. What is shown in FIG. 7 is an example of a data format when the driving operation procedure illustrated in FIG. 6 is expressed as knowledge data to be handled by a computer. (1) The procedure name is the name of the procedure enclosed in a rectangle in FIG. (2) The start condition is data for determining the situation in which execution of the procedure should be started. (3) Cancellation conditions are data for determining the situation in which execution of the procedure should be canceled. (4) Completion conditions are data for determining that execution of the procedure has been completed. (5) The upper procedure is the name of a procedure one level higher than the procedure. (6) A lower procedure is the name of a procedure one level lower than that procedure. However, the lower steps can be selected according to the situation using branch conditions. However, *() indicates that the data may be omitted.
()+ indicates that any number of the data may be written. The inference algorithm used to perform inference using the data format shown in FIG. 7 is as follows. (a) Set driving goals. The settings may be input by an operator, or may be automatically set by another operating state grasping device or abnormality diagnosis device, and any method may be used. (b) Select a knowledge base. From a plurality of knowledge bases created for each purpose, one that matches the driving objective set in (a) is searched and set as the top level. (c) Retrieve sub-procedures.

[0007] Find a branching condition that holds true in that situation,
Retrieve the substeps and write them into working memory. At this point, only candidates for sub-procedures for achieving a certain procedure have been extracted, and the procedure is marked with status information of "waiting for execution". (d) Determine starting conditions. If the start condition is met, the status information for that procedure is changed to "waiting for completion" in the working memory, and guidance is output to the operator to execute the procedure. (e) Determine cancellation conditions. If the start condition is met, the status information of that procedure and all sub-procedures derived from it in the working memory is changed to "canceled". (f) Determine completion conditions. If the completion condition is met, the status information for that procedure in the working memory is changed to "completed". (g) Return to (a) above.

FIG. 8 shows an example of the contents of the working memory when inference is made using the above knowledge base and inference algorithm. An example of this is the plant start-up shown in Figure 6.
This is the state when step d has been completed. The reason why A and A1 are waiting for completion is because lower procedures A2 and e have not been completed, respectively. Furthermore, f, g, and h are not extracted because of the start condition (=A1
This is because the requirements (completion of

[0009] In reality, there are cases where the scenario must be dynamically changed depending on the plant state, circumstances, and the like. For example, ``While the startup operation scenario is being executed, the plant abnormality diagnosis device has notified that an abnormality has occurred, so we will switch to a scenario for abnormality convergence.'' or ``As the diagnosis results have become more detailed as the abnormality diagnosis progresses, we will change the scenario to a more appropriate scenario.'' (For example, as the reliability of the diagnosis increases, the scenario changes from "scenario to call attention" to "scenario to prepare for abnormal state convergence operation" to "scenario for actually performing abnormal state convergence operation"). step-by-step selection), etc.

Specifically speaking, changing the scenario means canceling the contents of the working memory and reselecting the knowledge base. Conventionally, this has been dealt with by preparing a knowledge base for selecting an appropriate scenario for a given situation and introducing processing to monitor scenario changes. FIG. 9 shows an example of a format in which knowledge data for selecting a currently required scenario is handled by a computer. The data in FIG. 9 is referred to as driving target selection knowledge. In FIG. 9, the driving target name is the driving target name to be achieved in the scenario to be selected. Further, the driving target selection data is data for determining the situation in which the driving target should be selected. The following processes (x) and (y) are newly added before process (a), and the process shown in FIG.
The scenario is switched using the knowledge data shown in . (x) Erase all contents of the initial setting working memory. (y) Driving target selection process

[0011] The driving target selection knowledge stored in the knowledge base is evaluated in the order of storage, and the driving target name corresponding to the first one that becomes true after evaluating the driving target selection data is extracted. If the extracted driving target name is (a) different from the driving target name already stored in the working memory or if no driving target name is currently stored in the working memory, go to (a). (b) If it is the same as the driving target name stored in the working memory, go to (c). Corresponding to this, (a) of the above processes (a) to (f)
, (b), and (g) are changed as follows. (a) Set driving goals. (a) Rewrite the driving target name stored in the working memory with the extracted driving target name. If it is not stored, the newly extracted driving target name is stored. (b) Delete all procedure names in the working memory that have status information of "waiting for execution" or "waiting for completion." (b) Select a knowledge base.

[0012] From a plurality of knowledge bases created for each purpose, one that matches the driving target name stored in the working memory is searched and set as the topmost procedure for that situation. (g) Return to (y) above.

[0013]

[Problem to be solved by the invention] An abnormality occurs during normal operation, so the execution of the current procedure is interrupted, the abnormality is brought to an end by switching to a scenario for converging this, and the original scenario is restarted again. In some cases, the plant state is different from when execution of the procedure was interrupted, and it is not possible to simply restart the procedure from where it was interrupted.

For example, in the scenario "startup operation", there was some abnormality in the main water supply control valve during the load increase, so the scenario was switched to "main water supply control valve repair", the load was reduced to an output that could be controlled by the water supply bypass valve, and the main After repairing the water supply control valve, the scenario was returned to ``startup operation''.''
In some cases, the plant state has returned to the state before the "normal startup" was interrupted, such as when the load has been lowered due to "main water supply control valve repair." In other words, when restarting a scenario, it is necessary to (1) determine the procedure that should be used as the restart point from the point of interruption;

[0015] It is necessary to take this into consideration. In principle, the procedure that should be the restart point can be detected by going back through the steps in the scenario for which the completion condition is not met, but in reality, in addition to this, (2) the completion condition is not met. However, it must also be noted that there are steps that may be omitted depending on the main objective being achieved.

For example, as part of the preparation for starting the charging high-pressure injection pump in the plant start-up procedure, the procedure ``close water sealing injection flow rate control valve'' is performed. Seal water injection starts after the step "Start filling high pressure injection pump", but at this time, the step "Seal water injection flow control valve opens" which has the opposite effect of the previous step is performed, so the conditions for completing the previous step are not met. It becomes unsuccessful. Now, if the scenario is interrupted due to an abnormality after "starting the filling high-pressure injection pump" and restarted, the completion condition for "water sealing injection flow rate control valve closed" will not be satisfied, but this procedure will be "
The main purpose of "starting the filling high-pressure injection pump" has already been achieved and should not be repeated. Hereinafter, a certain procedure will be referred to as a procedure that has a main purpose, and once that procedure is completed, the procedures that will not be performed will be referred to as a procedure, and a procedure that is the main purpose will be referred to as a main procedure. In this case, the procedure "close water sealing injection flow rate control valve" is a subprocedure of the main procedure "start filling high pressure injection pump". When restarting the scenario, if the main step has been completed, its sub-steps shall be omitted.

[0017] Conventionally, the above (1) and (2) have not been taken into account at all, and once an abnormality occurs, the original procedure cannot be resumed after the abnormality has been resolved, making it impossible to output appropriate guidance. There wasn't. For this reason, the mental burden on operators involved in monitoring and making judgments is high, or operators with little experience may perform redundant operations or standby, or in extreme cases may cause unnecessary plant shutdowns, resulting in lower plant utilization rates. sometimes lowered.

The present invention has been developed in view of the above points, and allows the original procedure to be resumed even after an abnormality occurs and is resolved.
The purpose of the present invention is to provide a driving support device that can output appropriate guidance.

[0019]

[Means for Solving the Problems] The present invention provides driving support that guides the operator to driving procedures by inferring a scenario that is a sequence of procedures that need to be carried out for a given driving goal and outputting the scenario. In the apparatus, a first memory means for storing a first knowledge base for inferring said scenario and a second memory means for inferring a driving goal appropriate to the current situation.
a second memory means for storing a knowledge base of said second memory means;
selecting a driving objective suitable for the current situation based on a second knowledge base stored in the memory means of the invention, and selecting said driving objective based on the first knowledge base stored in said first memory means. and an inference means for inferring the above scenario under a target.

[0020]

[Operation] According to the above configuration, a driving goal suitable for the current situation can be selected using the second knowledge base, and a scenario is inferred using the first knowledge base under this selected driving goal. This allows the original procedure to be resumed even after an abnormality occurs and is resolved, and appropriate guidance can be output.

[0021]

DESCRIPTION OF THE PREFERRED EMBODIMENTS A driving support system according to an embodiment of the present invention will be described below with reference to the drawings. (1) Equipment configuration

FIG. 1 shows an example of the device configuration of the present invention. In FIG. 1, the inference mechanism 4 includes an input device 20 from a plant 10.
In addition to inputting the plant amount via the abnormality diagnosis device 4
Input an output of 0. This inference mechanism 4 includes an input device 20
Using the input data from and each knowledge data stored in the first memory 1 and the second memory 2, inferences are made regarding the procedure that requires selection and implementation of driving goals, and the results are output to the working memory 3. do. Working memory 3 is
This is memory for storing data temporarily required for processing. The output device 30 provides driving guidance to the operator by outputting the contents of the working memory 3. (2) Contents of first memory 1

[0023] The first memory 2 stores knowledge data for expressing the driving operation procedure described above as the prior art. However, in the present invention, the main procedure name of the procedure represented by the knowledge data is newly added and stored. Figure 2 shows an example of the storage format of knowledge data. The storage example in FIG. 2 is the data storage example in FIG. 7 with the main procedure name newly added as data.

FIG. 3 shows an example of knowledge data. In the storage format example shown in FIG. 2, in addition to the conventional knowledge data structure, a new main procedure slot is added for describing the main procedure of the procedure. In the example of Figure 3, the step "Prepare Fill High Pressure Injection Pump Mini Flow Line" can be started unconditionally and may be completed if the Fill High Pressure Injection Pump Mini Flow Valve and the Fill High Pressure Injection Pump Mini Flow Source Valve are open. , the main step of this procedure is "starting the filling high-pressure injection pump", and the upper step of this procedure is "preparation before starting the filling high-pressure injection pump". (3) Contents of second memory 2

The second memory 2 stores a driving goal selection knowledge base for selecting a scenario appropriate for a given situation. An example of the data format of the driving target selection knowledge base is shown in FIG. In the data format example of FIG. 9, (a) Driving target name is the driving target name of the scenario selected by this knowledge data. (a) Driving target data is data for determining the situation in which the driving target name in (a) is selected.

FIG. 10 shows an example of driving target knowledge. Figure 10
The example shows that the operation target "main water supply control valve repair" is selected when the diagnostic device outputs the abnormality "main water supply control valve abnormality". (4) Working Memory 3 The working memory 3 stores the current driving goal and the name of the procedure under the driving goal. The procedure name is stored along with the following status information. "Waiting for execution": A state in which the start conditions are not met. "Waiting for completion": A state in which guidance is output to the operator when the start condition is met, and the system is waiting for the completion of the procedure to be met. "Completed": A state in which the completion conditions for the procedure are met and completion is confirmed. "Cancelled": The cancellation condition has been met and the execution of the procedure has been canceled. "Pending": Information indicating that the procedure with this status information was completed when the scenario was interrupted. "No processing required": Information indicating that the procedure with this status information cannot be processed when the scenario is restarted. Furthermore, the area of the working memory 3 that stores the driving goals will be particularly referred to as "driving goals."

An example of storage in the working memory 3 is shown in FIG. In the example of FIG. 4, a new area "operation target" is added to the example of FIG. 7, and the operation target name "plant startup" is stored. (5) Inference Algorithm The processing flow in the inference mechanism 4 of the present invention is shown in FIG. Details of the processing are shown below. (Step S1): All contents of the initial setting working memory 3 are erased. (Step S2): Driving target selection process

The knowledge stored in the second memory 2 is evaluated in the order of storage, the driving target selection data is evaluated, and the driving target name corresponding to the first one that becomes true is extracted. The extracted driving target name is

(a) If the driving target name is different from the driving target name stored in the area "driving target" in the working memory 3, or if the driving target name is not stored in the "driving target" area, "
Rewrite the driving target name stored in the area ``driving target'' with the extracted driving target name (or add a new one), and proceed to step S3. (b) Driving target name stored in the area ``driving target'' in the working memory 3 If it is the same as the target name, do nothing and proceed to step S6. (Step S3) Clearing the working memory (a) All procedure names in the working memory 3 that have status information of "waiting for execution" and "waiting for completion" are deleted. (b) For all procedures that have status information of "Completed" in the working memory 3, change the status information to "Pending". (Step S4) Unnecessary procedure extraction process

(a) Search for a procedure whose status information is "pending" in the working memory 3, and perform (b) for the first one found. If there is no procedure that is "on hold", the process advances to step S5. (b) Regarding the procedure, if it is true, change the status information of the procedure name from "Pending" to "No processing required", and (a)
fart. On the other hand, if it is false, search the working memory 3 for the procedure name written in the main procedure slot, and (a) if the status information is "no processing required", set the procedure to "no processing required". Go to (a). (b) If the status information is "pending", do nothing (a)
fart.

(c) If the main purpose procedure slot does not exist for the procedure in question, or if there is no main purpose procedure in the working memory 4, delete the name of the procedure in question from the working memory 3 together with the status information and go to (a). (Step S5) A knowledge base that matches the "driving goal" in the working memory 3 is searched out from a plurality of knowledge bases created for each selected purpose, and is set as the topmost procedure for that situation. (Step S6) Required procedure inference processing Regarding the knowledge data stored in the first memory 1,
(a) Extract the sub-procedure.

[0032] Find a branching condition that holds true in that situation,
The lower steps are taken out and written into the working memory 3. At this point, only candidates for sub-procedures for achieving a certain procedure have been extracted, and the procedure is marked with status information of "waiting for execution". (b) Determine completion conditions.

[0033] If the completion condition is satisfied for a procedure to which status information of "waiting for execution" or "waiting for completion" is attached in the working memory 3, that procedure in the working memory 3 and all subordinates derived from them Change the status information of the step to "Completed". (c) Judgment of “no processing required”

Regarding a procedure to which "waiting to execute" status information is attached, if a procedure with the same procedure name and "no processing required" exists in the working memory 3, the status information of "waiting to execute" is changed to "waiting to execute". The procedure name with status information of ``Completed'' and ``No processing required'' is deleted from the working memory 3 along with the status information. (d) Determine starting conditions.

Regarding a procedure to which status information of "waiting for execution" is attached, if the start condition is satisfied, the working memory 3
The status information of the procedure is changed to "Waiting for completion" within the same period, and guidance is output to the operator to execute the procedure. (e) Determine cancellation conditions. If the cancellation condition is satisfied, the status information of that procedure and all sub-procedures generated from it in the working memory 3 is changed to "cancelled". (f) Return to step S2 above.

[0036]

As described above, according to the present invention, even after an abnormality occurs and is resolved, the original procedure can be resumed, and appropriate guidance can be output. This reduces the mental burden on operators involved in monitoring, making decisions, etc., and reduces the possibility of lowering the plant's operating rate due to redundant operations, standby, or unnecessary plant shutdowns.

[Brief explanation of the drawing]

FIG. 1 is a block diagram showing a configuration according to an embodiment of the present invention.

FIG. 2 is a diagram showing an example of the knowledge data expression format of the embodiment.

FIG. 3 is a diagram showing an example of knowledge data storage in the same embodiment.

FIG. 4 is a diagram showing the contents of working memory in the same embodiment.

FIG. 5 is a flowchart for explaining the operation of the embodiment.

FIG. 6 is a diagram for explaining a conventional driving operation procedure.

FIG. 7 is a diagram showing an example of a conventional knowledge data expression format.

FIG. 8 is a diagram showing the contents of a conventional working memory.

FIG. 9 is a diagram showing an example of an expression format of driving target selection knowledge data.

FIG. 10 is a diagram showing an example of driving target selection knowledge.

[Explanation of symbols]

DESCRIPTION OF SYMBOLS 1... First memory, 2... Second memory, 3... Working memory, 4... Reasoning mechanism, 10... Plant, 20... Abnormality diagnosis device, 30... Output device, 40... Abnormality diagnosis device.

Claims (1)

[Claims] [Claim 1] A driving support device that infers a scenario, which is a sequence of procedures that need to be carried out for a given driving goal, and outputs the scenario to guide the driving procedure to an operator. a first memory means for storing a first knowledge base for inferring a driving goal suitable for the current situation; a second memory means for storing a second knowledge base for inferring a driving goal suitable for the current situation; selecting a driving goal appropriate to the current situation based on a second knowledge base stored in said first memory means;
and inference means for inferring the scenario under the selected driving goal based on the knowledge base of.