Information processing device, operation support method, and operation support program

Abstract

To support the execution of an operation by which a result comparable to those produced by a skilled operator is obtainable.SOLUTION: An information processing apparatus 10 comprises a storage section that stores skill data defining skill information of steps of factor identification, countermeasure determination and countermeasure execution included in an OODA loop based on each of deviant events occurring at a plant, and a providing section that, if a deviant event is detected, provides an operator terminal with the skill information of the steps of factor identification, countermeasure determination and countermeasure execution associated with the detected deviant event out of the skill data.SELECTED DRAWING: Figure 1

Description

Technical Field

[0001] The present invention relates to an information processing apparatus, an operation support method, and an operation support program.

Background Art

[0002] In a plant, operation control using process data is performed. For example, PID (Proportional Integral Differential) that brings the measured value of a process closer to a set value is executed by a control system such as DCS (Distributed Control Systems) or PLC (Programmable Logic Controller).

Prior Art Documents

Patent Documents

[0003]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0004] However, in the above PID control, it is difficult to make the set value follow the optimum value that varies due to a deviation event caused by a change in 4M (Machine, Method, Man, Material). Therefore, there is a difficult aspect in suppressing deterioration of PQCDS (Products, Quality, Cost, Delivery, Safety) corresponding to the manufacturing result of the plant.

[0005] For this reason, in the above deviation event, there is a current situation where an operator who operates the plant performs operations related to the operation of the plant by visually following the behavior of the plant, for example, a real-time trend graph, and comparing it with his or her own experience.

[0006] Such experience is operator-specific, that is, it is personal know-how, making it difficult to accurately convey to inexperienced operators. Therefore, not every operator can perform operations that yield the same results as a skilled operator. As a result, not only is it difficult to suppress the deterioration of PQCDS, but it is also difficult to suppress the variability of PQCDS.

[0007] The present invention aims to support the execution of operations that can achieve results equivalent to those of a skilled operator. [Means for solving the problem]

[0008] An information processing device according to one aspect of the present invention includes a storage unit that stores skill data in which skill information for each step of the OODA (Observe Orient Decide Act) loop—factor identification, countermeasure decision, and countermeasure execution—is defined for each deviation event occurring in a plant, and a supply unit that, when a deviation event is detected, provides the skill information for each step of the factor identification, countermeasure decision, and countermeasure execution associated with the detected deviation event from the skill data to an operator terminal.

[0009] In one aspect of the present invention, when an deviation event is detected, a computer performs a process to provide the operator terminal with the skill information for each step of the OODA (Observe Orient Decide Act) loop, which is included in the OODA loop, for each deviation event occurring in the plant. This skill information is stored in a storage unit that stores skill data, and the skill information for each step of the OODA loop is associated with the detected deviation event.

[0010] An operation support program according to one aspect of the present invention, when an deviation event is detected, causes a computer to perform a process that provides the operator terminal with the skill information for each step of the OODA (Observe Orient Decide Act) loop, which is included in the OODA loop, for each deviation event occurring in the plant, from the skill data stored in the storage unit that stores skill data defining the skill information for each step of the OODA loop, which is included in the OODA loop, for each deviation event, to the detected deviation event. [Effects of the Invention]

[0011] According to one embodiment, it is possible to support the execution of operations that can achieve results equivalent to those of a skilled operator. [Brief explanation of the drawing]

[0012] [Figure 1] This is a block diagram showing an example of the functional configuration of an information processing device. [Figure 2] This figure shows an example of a 4M event. [Figure 3] This figure shows an example of the roles for operation support functions. [Figure 4] This is a flowchart showing the processing steps for Observe. [Figure 5] This flowchart shows the processing steps for Orient. [Figure 6] This is a flowchart showing the Decide process steps. [Figure 7] The processing procedure for the Act is shown in the flowchart. [Figure 8] This figure shows an example of a support information interface. [Figure 9] This figure shows an example of a support information interface. [Figure 10] This figure shows an example of a support information interface. [Figure 11] This figure shows an example of a support information interface. [Figure 12] This figure shows an example of a support information interface. [Figure 13] It is a diagram for explaining an example of hardware configuration.

Embodiments for Carrying Out the Invention

[0013] Hereinafter, embodiments of an information processing apparatus, an operation support method, and an operation support program according to the present application will be described with reference to the accompanying drawings. Each embodiment merely shows one example or aspect, and numerical values, functional ranges, usage scenarios, etc. are not limited by such examples. And each embodiment can be appropriately combined within a range that does not conflict with the processing content.

[0014] <Overall Configuration> FIG. 1 is a block diagram showing a functional configuration example of an information processing apparatus 10. The information processing apparatus 10 shown in FIG. 1 provides an operation support function for assisting the execution of an operation that can obtain the same result as that of a skilled operator from the aspect of eliminating the personal nature of the operation corresponding to a deviation event.

[0015] As part of such an operation support function, an organization function for organizing the personal know-how of a skilled operator, a utilization function for utilizing the know-how, a utilization support function for supporting the utilization, etc. may be provided.

[0016] As shown in FIG. 1, the information processing apparatus 10 can be communicably connected to various systems 2, a staff terminal 30, and an operator terminal 50. For example, between the information processing apparatus 10 and the various systems 2, communication corresponding to an industrial wireless standard may be performed via a dedicatedly constructed control bus. Also, between the information processing apparatus 10 and the staff terminal 30 or the operator terminal 50, wired or wireless communication may be performed via a communication network such as a LAN (Local Area Network).

[0017] The various systems 2 are examples of systems that acquire data from Plant 1 by obtaining 4M information, and can be any system related to Plant 1. For example, Figure 1 shows a process control system 3 as one of the systems that acquires data, which corresponds to Method among the 4Ms. The process control system 3 is a system that controls the production process, or process, in Plant 1. As an example, the process control system 3 can be constructed as a DCS (Distributed Control System) or a PLC (Programmable Logic Controller). Taking a DCS as an example, measuring instruments such as sensors and operating instruments such as actuators are installed as field devices (not shown) in the field of Plant 1. Controllers that control such field devices are distributed and arranged for each control loop, which is the control unit of the process, such as measurement, control calculation, and operation loops. Although Figure 1 shows the process control system 3 as an example, data for the remaining 3Ms other than Method can also be acquired from other systems included in the various systems 2.

[0018] The staff terminal 30 and operator terminal 50 are implemented by a computer that functions as an HMI (Human Machine Interface) with the process control system 3, etc. Each of these staff terminals 30 and operator terminal 50 is used by either the staff or the operators. Here, "staff" refers to personnel responsible for the operational design of Plant 1, etc., and "operators" refers to personnel responsible for the operations related to the operation of Plant 1.

[0019] Figure 1 shows an example where the staff terminal 30 and the operator terminal 50 are each implemented as separate computers; however, the HMI functions provided to the staff and operators may be implemented by a single computer. In this case, the HMI functions may be implemented by a multi-user compatible computer that allows login using the respective accounts of the staff and operators. Furthermore, although Figure 1 shows an example where the above HMI functions are provided by a computer separate from the information processing device 10, the above HMI functions may also be implemented by the user interface of the information processing device 10.

[0020] <Configuration of the information processing device 10> Next, an example of the functional configuration of the information processing device 10 according to this embodiment will be described. Figure 1 schematically shows the blocks related to the operation support functions of the information processing device 10. As shown in Figure 1, the information processing device 10 has a communication control unit 11, a storage unit 13, and a control unit 14. Note that Figure 1 only shows a selection of the functional units related to the operation support functions described above, and the information processing device 10 may also be equipped with functional units other than those shown.

[0021] The communication control unit 11 is a functional unit that controls communication with other devices such as the process control system 3, staff terminals 30, and operator terminals 50. For example, the communication control unit 11 can be implemented using a network interface card. In one aspect, the communication control unit 11 can receive process data from the process control system 3 as an example of 4M information, or output commands corresponding to operations. In another aspect, the communication control unit 11 can receive information from the staff terminals 30 regarding the deviation recovery know-how of skilled operators, or provide the operator terminal 50 with an interface to support the execution of operations from the detection of deviation events to recovery.

[0022] The memory unit 13 is a functional unit that stores various types of data. For example, the memory unit 13 can be implemented by internal, external, or auxiliary storage of the information processing device 10. For instance, the memory unit 13 stores skill data 13A and framework 13B. The skill data 13A and framework 13B will be explained in conjunction with the scenes in which they are referenced, generated, or registered.

[0023] The control unit 14 is a functional unit that performs overall control of the information processing device 10. For example, the control unit 14 can be implemented by a hardware processor. As shown in Figure 1, the control unit 14 has a reception unit 15, a development support unit 16, and a provision unit 17. The control unit 14 may also be implemented by hardwired logic or the like.

[0024] The reception unit 15 is a processing unit that receives various types of information. One aspect of this is that, for each deviation event, the reception unit 15 receives know-how from a skilled operator, ranging from the detection of the deviation to its recovery, from the staff terminal 30.

[0025] In this context, "deviant events" refer to any phenomenon that has an undesirable impact on PQCDS triggered by a change in the 4Ms. Figure 2 shows an example of a classification of 4M events that can trigger such deviant events.

[0026] Figure 2 shows an example of a 4M event. As shown in Figure 2, deviations during manufacturing can be classified into raw material deviations, equipment deviations, process deviations, human deviations, and E / U (End User) deviations. Of these, raw material deviations can be further classified into variations in raw material quality and biases in raw material quality. Equipment deviations can be further classified into equipment downtime, reduced equipment performance, and reduced equipment efficiency. Furthermore, process deviations can be further classified into reduced process performance, reduced process efficiency, process side effects, and imbalances in the process. "Performance" here may include mixing, reaction, separation, molding, and conveying. "Efficiency" may include reaction and separation. Furthermore, "side effects" may include reaction and conveying. Furthermore, "balance" may include mixing, reaction, separation, molding, and conveying. Human deviations can be further classified into deviations within the department and deviations from other departments. Furthermore, E / U deviations can be further classified into expected supply-demand gaps and unexpected supply-demand gaps. If these manufacturing deviations are not addressed appropriately (recovery operations), it will lead to a deterioration of the PQCDS corresponding to the manufacturing results.

[0027] Here, the above know-how is divided into steps of the OODA (Observe Orient Decide Act) loop, with the skill information referenced in the process corresponding to each step being defined, in order to organize the know-how of skilled operators into a form that can be utilized.

[0028] Figure 3 shows an example of the roles of the operation support function. Figure 3 shows the roles of the operation support function from the perspective of staff and operators. As shown in Figure 3, the reception unit 15 receives definitions of deviation recovery know-how from skilled operators from the staff terminal 30 for each deviation incident. The "deviation recovery know-how" mentioned here is an example of skill information. Such deviation recovery know-how can be divided into eight types, (1) to (8), and each of the eight types, (1) to (8), is defined including the usage scenario.

[0029] The deviation recovery know-how in (1) and (2) corresponds to the Observe step of the OODA loop. For example, in the deviation recovery know-how in (1), the detection method may define monitoring items for process data, KPIs (Key Performance Indicators) calculated from process values ​​and their trends corresponding to the monitoring items, and thresholds such as upper and lower limits to be compared with the KPIs. Furthermore, in the deviation recovery know-how in (2), the impact on PQCDS when a deviation event is left unaddressed is defined.

[0030] The deviation recovery know-how in (3) and (4) corresponds to the Orient step of the OODA loop. For example, in the deviation recovery know-how in (3), Fault Tree Analysis (FTA), also known as failure tree analysis, can be defined to identify the factors of the deviation event. Furthermore, in the deviation recovery know-how in (4), a failure mode is defined for each factor of the deviation event.

[0031] The deviation recovery know-how in (5) and (6) corresponds to the Decide step of the OODA loop. For example, in the deviation recovery know-how in (5), a Standard Operating Procedure (SOP) used to recover from each failure mode may be defined. Furthermore, in the deviation recovery know-how in (6), a logic chart for decision support may be defined, which is referenced when narrowing down from multiple recovery SOP candidates to one.

[0032] The deviation recovery know-how in (7) and (8) corresponds to the Act step of the OODA loop. For example, the deviation recovery know-how in (7) may define a logic chart for SOP correction before the execution of the recovery SOP. Furthermore, the deviation recovery know-how in (8) may define a logic chart for SOP correction during the execution of the recovery SOP.

[0033] The deviation recovery know-how (1) to (8), defined for each deviation event, is stored in the storage unit 13 as skill data 13A by the reception unit 15. These definitions of deviation recovery know-how (1) to (8) provide the operator with support for deviation recovery operation such as (1) to (8). For example, in the Observe step of the OODA loop (capturing signs of PQCDS deterioration), (1) it supports the detection of deviation events and (2) it provides information on the impact on PQCDS if the deviation event is left unattended. In addition, in the Orient step of the OODA loop (support for analysis of deviation events), (3) it supports the identification of the cause of the deviation event and (4) it supports the extraction of the failure mode of the deviation event. Furthermore, in the Decide step of the OODA loop (support for narrowing down deviation recovery measures), (5) it supports the extraction of candidate SOPs for recovery from deviations and (6) it supports the narrowing down of candidate SOPs for recovery. Furthermore, in the Act step of the OODA loop (adjustment and support for the implementation of deviation recovery measures), (7) support for SOP correction before the implementation of recovery measures, and (8) correction of SOP support during the implementation of recovery measures.

[0034] Here, we have given an example where the definition of deviation recovery know-how is accepted for each step of the OODA loop, but it is not necessary for deviation recovery know-how to be defined for all four steps of the OODA loop. In other words, the receiving unit 15 can accept definitions of deviation recovery know-how corresponding to one or any combination of two or more of the four steps of the OODA loop.

[0035] The Development Support Unit 16 is a processing unit that supports the development of software that executes suggestions for operations to recover from deviation events. Hereinafter, the software that executes suggestions for operations to recover from deviation events may be referred to as "OPS suggestion software." As an example, the Development Support Unit 16 accepts the creation and registration of an OPS suggestion software framework in which the procedures for the corresponding steps of the Observe, Orient, Decide, and Act steps of the OODA loop are described. As a result, the OPS suggestion software framework is stored in the storage unit 13 as framework 13B.

[0036] The provisioning unit 17 is a processing unit that provides skill information regarding the operation of Plant 1 at each step of the OODA loop for each deviation event. As shown in Figure 1, the provisioning unit 17 has a software execution unit 18 that executes the above OPS proposal software in parallel for each deviation event.

[0037] The software execution unit 18 performs the following processing for each deviation event. Specifically, the software execution unit 18 retrieves the framework 13B stored in the storage unit 13. Then, the software execution unit 18 retrieves the deviation recovery know-how corresponding to the target deviation event from the skill data 13A stored in the storage unit 13. After that, the software execution unit 18 generates OPS proposal software corresponding to the deviation event by setting parameter items and parameter values ​​defined as deviation recovery know-how in the functional components other than the template part, such as libraries, modules, or parameters referenced by APIs, in each of the Observe, Orient, Decide, and Act steps of the OODA loop included in the framework.

[0038] As the OPS proposal software generated for each deviation event is executed in parallel, the processes shown in Figures 4 to 7 are executed as processes corresponding to the Observe, Orient, Decide, and Act steps of the OODA loop.

[0039] Figure 4 is a flowchart showing the processing procedure of Observe. As shown in Figure 4, the software execution unit 18 monitors whether or not a deviation event has occurred, based on the assumption that the operation will continue according to the currently running SOP, and whether or not the QMM (Quality Management Maturity) can be maintained (step S101). More specifically, the KPI set for each deviation event is calculated in real time based on process data acquired from the process control system 3, and it is determined whether or not the calculated KPI is within the threshold range set for each deviation event.

[0040] If a deviation event occurs at this time (step S101 Yes), the software execution unit 18 issues an alarm regarding the deviation event to the operator terminal 50 (step S102). Such an alarm prompts the operator to initiate deviation recovery measures in an alarm-driven manner.

[0041] Next, the software execution unit 18 collects alarm information corresponding to the deviant event currently occurring and provides it to the operator terminal 50 (step S103). In step S103, from the perspective of supporting confirmation of the current situation, the location and status of the alarm are output. Furthermore, from the perspective of supporting confirmation of the situation from the past to the present, process values ​​and KPI trends for items defined for each deviant event are output.

[0042] The software execution unit 18 then provides the operator terminal 50 with information on the impact of the deviant event occurring (step S104). In step S104, from the perspective of supporting the understanding of future situations, the impact on PQCDS defined in (2) deviation recovery know-how corresponding to the deviant event occurring in the skill data 13A is acquired.

[0043] Here, the operator decides whether or not to cancel the alarm output in step S102 based on the information provided in steps S103 and S104, the need for action, and the priority of multiple alarm outputs.

[0044] If the alarm is not cleared (step S105 No), the process proceeds to Orient. If the alarm is cleared (step S105 Yes), the process proceeds to step S101.

[0045] Figure 5 is a flowchart showing the processing procedure of Orient. As shown in Figure 5, the software execution unit 18 extracts the FTA corresponding to the deviation event detected in step S101 of Observe (step S201). In step S201, the FTA defined in the deviation recovery know-how of (3) corresponding to the deviation event currently occurring in the skill data 13A is obtained. Subsequently, the software execution unit 18 analyzes the factors of the deviation event according to the FTA extracted in step S201 (step S202).

[0046] If the cause of the deviation event is identified here (step S203 Yes), the software execution unit 18 selects a failure mode corresponding to the cause of the deviation event identified in step S202 (step S204) and proceeds to the Decide process. In this step S204, the failure mode associated with the deviation event is selected from the deviation recovery know-how (4) corresponding to the deviation event currently occurring among the skill data 13A.

[0047] Furthermore, if the cause of the deviation event cannot be identified (Step S203No), symptomatic treatment may be implemented by the operator, or the response to the deviation event may be escalated from the operator to the staff.

[0048] Figure 6 is a flowchart showing the Decide processing procedure. As shown in Figure 6, the software execution unit 18 searches for identical or similar deviation events from the history of deviation events that have occurred in the past (step S301).

[0049] Next, the software execution unit 18 extracts SOPs from among the SOPs associated with the failure mode selected in step S204 of Orient that were executed for the same or similar deviation event hit in step S301 and that were successfully recovered (step S302). In this step S302, recovery SOPs are obtained that are associated with the current failure mode using the deviation recovery know-how (5) corresponding to the current deviation event in the skill data 13A.

[0050] Then, the software execution unit 18 extracts SOPs that are currently executable from the SOP candidates extracted in step S302 (step S303). In step S303, as an example, SOP extraction is performed according to the logic chart defined in (6) Deviation Recovery Know-how, which corresponds to the deviation event currently occurring in the skill data 13A.

[0051] Subsequently, the software execution unit 18 accepts the selection of one SOP from the candidate SOPs extracted in step S303 via the operator terminal 50 (step S304). At this time, the software execution unit 18 can present SOPs that are used at a frequency above a threshold in the history of countermeasures for past deviation events, or present a logic chart defined in the deviation recovery know-how of (6) that corresponds to the deviation event currently occurring for each SOP.

[0052] Then, the software execution unit 18 displays the manufacturing conditions of the SOP selected in step S304 and the manufacturing conditions of the SOP currently being applied on the operator terminal 50 for comparison (step S305).

[0053] In step S305, the system can accept SOP corrections from the operator terminal 50 before the SOP is executed. At this time, the software execution unit 18 can present a logic chart of the SOP correction defined in the deviation recovery know-how (7) corresponding to the deviation event currently occurring in the skill data 13A. In addition, the software execution unit 18 can present the correction amount of the SOP executed in the history of countermeasures for past deviation events that successfully recovered from the deviation event, or it can automatically correct the SOP selected in step S304 according to the correction amount of the said SOP.

[0054] As a result of the execution of step S305, the recovery SOP is determined, and then the process moves on to Act.

[0055] Figure 7 is a flowchart of the Act processing procedure. As shown in Figure 7, the software execution unit 18 instructs the process control system 3 to execute the recovery SOP determined in step S305 of Decide (step S401).

[0056] Subsequently, until the SOP is completed (step S402No), the processes from step S403 to step S405 below are executed. That is, the software execution unit 18 obtains the measured trend of process values ​​measured after the instruction to execute the SOP in step S401 from the process control system 3 (step S403). For example, the software execution unit 18 can obtain the trend of process values ​​measured during the period from the time the process in step S403 is executed back to the time the SOP execution was instructed in step S401.

[0057] Next, the software execution unit 18 displays the measured trend of process values ​​obtained in step S403 and the predicted trend of process values ​​predicted during SOP execution in step S401 in a comparable manner (step S404).

[0058] Here, the operator can decide, based on the display in step S404, whether to continue executing the SOP instructed to be executed in step S401, or to correct the SOP instructed to be executed in step S401. At this time, the software execution unit 18 can present a logic chart for correcting the SOP being executed, defined in the deviation recovery know-how of (8) corresponding to the deviation event occurring in the skill data 13A, such as a logic chart for correcting the gap between the measured value and the predicted value. Here, an example is given in which the correction of the SOP is determined by the operator's judgment, but the software execution unit 18 can also automatically correct the SOP instructed to be executed in step S401 based on the gap between the measured value and the predicted value if the gap between the measured value and the predicted value exceeds a threshold.

[0059] If the SOP is corrected as a result of the operator's judgment (step S405Yes), the process proceeds to step S401. In this case, the software execution unit 18 instructs the process control system 3 to execute the corrected SOP. If the SOP is not corrected (step S405No), the process proceeds to step S402.

[0060] Subsequently, once the SOP is completed (step S402Yes), the software execution unit 18 determines whether or not recovery from the deviation event has occurred (step S406). If recovery from the deviation event has occurred (step S406Yes), the Act process is terminated. If recovery from the deviation event has not occurred (step S406No), the operator may perform symptomatic treatment, or the operator may escalate the response to the deviation event to a staff member.

[0061] Next, using Figures 8 to 12, we will explain specific examples of interfaces used when support information is provided in each step of the OODA loop: Observe, Orient, Decide, and Act.

[0062] Figures 8 to 12 show examples of support information interfaces. Figures 8 to 12 illustrate a scenario in which support information is provided from the detection to the recovery of deviation events using the OPS support software described above, specifically when a deviation event occurs in the reaction process.

[0063] For example, if an deviation event is detected in step S101 of Observe, the alarm screen shown in Figure 8 is displayed on the operator terminal 50 in step S102 of Observe. As shown in Figure 8, the alarm screen displays an alarm related to a deviation in the reaction process. The issuance of such an alarm allows the operator to understand that a deviation has occurred in the reaction process and that corrective measures to restore the deviation are required.

[0064] Furthermore, in step S103 of Observe, the system screen shown in Figure 9 is displayed on the operator terminal 50. As shown in Figure 9, the status confirmation screen displays the message "Delay in reaction suppression has occurred." This helps to confirm the current situation, where reaction suppression is performed by lowering the temperature after the reaction is complete, but the reaction suppression is delayed more than usual. Furthermore, the status confirmation screen displays the message "The product is not within the QMM range, which may result in quality deterioration and process delays." This helps to understand the future situation, where failure to address the deviation in the reaction process will negatively affect Q and D in PQCDS, and therefore the deviation in the reaction process cannot be left unaddressed.

[0065] Furthermore, in the Orient step, the system screen shown in Figure 10 is displayed on the operator terminal 50. Figure 10 illustrates, from left to right, a factor analysis screen including the FTA extracted in Orient step S201 and the analysis results of deviation events analyzed in step S202, and a failure mode confirmation screen including the failure mode selected in step S204.

[0066] The factor analysis screen shown in Figure 10 displays the FTA corresponding to the reaction deviation and the result of the factor analysis by the FTA (the thick-bordered area in the figure). By displaying the FTA and factor analysis results in this way, the operator can understand that the cause of the deviation event is the accumulation of fouling in the reactor. Furthermore, the failure mode confirmation screen displays the failure mode corresponding to the cause of the deviation event identified in step S202 of Orient shown in Figure 5. At this time, the history of identical or similar deviation events is searched from the history of past deviation events, and the history of successful recovery among the identical or similar deviation events that were found in the search is displayed. This helps in the extraction of failure modes and presents past successful cases corresponding to that failure mode.

[0067] Furthermore, in the Decide step, the system screen shown in Figure 11 is displayed on the operator terminal 50. Figure 11 illustrates, from left to right, the SOP candidate screen which displays the SOP candidates extracted in the Decide step S302, the logic chart screen which displays the logic chart used to extract executable SOPs in step S303, and the countermeasure history screen which displays a list of past countermeasures.

[0068] In the SOP candidate screen shown in Figure 11, SOPs corresponding to failure modes are displayed as candidates. When listing SOPs in this way, recovery SOPs associated with the current failure mode can be listed using the deviation recovery know-how (5) corresponding to the deviation event occurring in the skill data 13A. In addition, recovery SOPs associated with failure modes that were executed for the same or similar deviation event and that successfully recovered can be listed. By displaying such an SOP candidate screen, countermeasures against deviations in the reaction process can be presented.

[0069] Furthermore, the logic chart screen shown in Figure 11 displays a logic chart that extracts SOPs that can be executed in the current situation, along with the results of the SOP extraction in the logic chart, i.e., the thick-bordered area in the figure. By displaying such a logic chart screen, it is possible to present the SOP "Water Volume UP" which can be executed in the current situation from the SOP candidate screen, and to present the reason why this SOP "Water Volume UP" can be executed in the current situation: "There is a surplus of water volume."

[0070] Furthermore, the countermeasure history screen shown in Figure 11 displays a list of past countermeasures in chronological order. This display of the countermeasure history screen allows us to show that the SOP "Water Volume Increase" has been applied three times in a row based on past history. Additionally, the cumulative water volume increase since the last cleaning is used as a guideline for deciding whether to proceed with the SOP "Cleaning" (cumulative water volume increase of 5m³). 3Since it indicates that the amount should not exceed " / h", the operator can be made aware that applying the SOP "Increase Water Volume" to the deviation in the reaction process is sufficient without performing cleaning. Furthermore, the countermeasure history screen can recommend selecting from four candidates out of the six SOPs numbered 1 through 6: SOPs 1, 2, 3, and 6, as a result of narrowing down the candidate SOPs by the OPS support software mentioned above.

[0071] Furthermore, in the Act step, the system screen shown in Figure 12 is displayed on the operator terminal 50. Figure 12 illustrates, from left to right, the pre-execution SOP adjustment screen displayed before the execution of the SOP and the in-execution SOP adjustment screen displayed during the execution of the SOP. The display of the pre-execution SOP adjustment screen shown in Figure 12 indicates that an SOP recovered from a similar failure mode has been selected, but it does not perfectly match the current deviation event, thus providing motivation to correct the SOP before execution. In addition, the pre-execution SOP adjustment screen displays a graph of the process value trends observed in past similar deviation events and the process value trends observed in the current deviation event, allowing for suggestions such as executing with a water volume of 0.9, based on correction know-how. Furthermore, the display of the in-execution SOP adjustment screen shown in Figure 12 indicates that the temperature is dropping lower than expected, allowing for suggestions such as correcting the water volume to 0.85, based on correction know-how.

[0072] <One aspect of the effect> As described above, when an deviation event is detected, the information processing device 10 according to this embodiment provides the operator terminal with the skill information for each step of the OODA loop, which is included in the deviation detection, cause identification, countermeasure decision, and countermeasure execution steps, from the skill data 13A defined for each deviation event occurring in Plant 1, that corresponds to the detected deviation event.Therefore, the information processing device 10 according to this embodiment can support the execution of operations that can obtain results equivalent to those of a skilled operator.As a result, operations that can obtain results equivalent to those of a skilled operator are executed, and the number of times operations are trial and error is reduced, thereby reducing the processing load on the process control system.

[0073] In the above embodiment, we have given an example in which skill information for all steps of deviation detection, factor identification, countermeasure decision, and countermeasure implementation is defined in skill data 13A and skill information for all steps is provided, but we are not limited to this. For example, the skill data 13A stored in the storage unit 13 may define only the skill information for the steps corresponding to one or any combination of two or more of the four steps, and the providing unit 17 may provide only the skill information for the steps corresponding to one or any combination of two or more.

[0074] <Numerical values, etc.> The details described in the above embodiments, such as the types and number of 4M events, and specific examples such as the types and number of deviation recovery know-how, are examples and can be changed. Furthermore, the flowchart described in the embodiments can also be modified in terms of processing order, within a reasonable range.

[0075] <System> The processing procedures, control procedures, specific names, and various data and parameters shown in the above documents and drawings may be changed at will unless otherwise specified. For example, one or more of the receiving unit 15, development support unit 16, and supply unit 17 may be composed of separate devices.

[0076] Furthermore, the components of each illustrated device are functionally conceptual and do not necessarily need to be physically configured as shown. In other words, the specific forms of distribution and integration of each device are not limited to those shown. That is, all or part of them can be functionally or physically distributed and integrated in any units according to various loads and usage conditions. Note that each configuration may also be a physical configuration.

[0077] Furthermore, each processing function performed by each device may be implemented, in whole or in part, by a CPU (Central Processing Unit) and a program executed by that CPU, or by wired logic hardware.

[0078] <Hardware> Next, an example of the hardware configuration of the computer described in the embodiment will be explained. Figure 13 is a diagram illustrating an example of the hardware configuration. As shown in Figure 13, the information processing device 10 includes a communication device 10a, an HDD (Hard Disk Drive) 10b, memory 10c, and a processor 10d. Furthermore, each of the parts shown in Figure 13 is interconnected by a bus or the like.

[0079] The communication device 10a is a network interface card or the like, and communicates with other servers. The HDD 10b stores programs and databases that operate the functions shown in Figure 1.

[0080] The processor 10d operates a process that performs the functions described in Figure 1 by reading a program that performs the same processing as the processing unit shown in Figure 1 from the HDD 100b or the like and loading it into memory 100c. For example, this process performs the same functions as the processing unit of the information processing device 10. Specifically, the processor 10d reads a program that has the same functions as the reception unit 15, development support unit 16, and provision unit 17 from the HDD 10b or the like. Then, the processor 10d executes a process that performs the same processing as the reception unit 15, development support unit 16, and provision unit 17.

[0081] Thus, the information processing device 10 operates as an information processing device that performs an operation support method by reading and executing a program. Furthermore, the information processing device 10 can also achieve the same functionality as the embodiment described above by reading the program from the recording medium using a media reader and executing the read program. It should be noted that the program referred to in this other embodiment is not limited to being executed by the information processing device 10. For example, the present invention can be similarly applied when another computer or server executes the program, or when they collaborate to execute the program.

[0082] The above program can be distributed via a network such as the Internet. Furthermore, the program can be recorded on any storage medium and executed by reading it from the medium by a computer. For example, the storage medium can be a hard disk, flexible disk (FD), CD-ROM, MO (Magneto-Optical disk), DVD (Digital Versatile Disc), etc.

[0083] <Other> Some examples of the combinations of technical features that will be disclosed are listed below.

[0084] (1) A storage unit that stores skill data defining the skill information for each step of the OODA (Observe Orient Decide Act) loop, which is included in the factor identification, countermeasure decision, and countermeasure implementation for each deviation event that occurs in the plant, When a deviation event is detected, the provision unit provides the operator terminal with skill information from the skill data for each step of identifying the cause, deciding on countermeasures, and executing countermeasures, which are associated with the detected deviation event. An information processing device characterized by having the following features.

[0085] (2) The skills data further includes skills information for the deviation detection step included in the OODA loop, The aforementioned provisioning unit provides the operator terminal with skill information for each step of deviation detection, cause identification, countermeasure decision, and countermeasure implementation, which is associated with the detected deviation event from the skill data. (1) The information processing device described above.

[0086] (3) The providing unit provides skill information for each step of deviation detection, factor identification, countermeasure determination, and countermeasure execution through an interface corresponding to each step. The information processing device described in (1) or (2).

[0087] (4) The system further includes a receiving unit that receives definitions of skill information for each step of the OODA loop, including factor identification, countermeasure decision, and countermeasure implementation, for each of the aforementioned deviation events. An information processing device described in any one of (1) to (3).

[0088] (5) The receiving unit receives a definition of FTA (Fault Tree Analysis) for identifying the factors of the deviation event as skill information for the factor identification step. (4) The information processing device described above.

[0089] (6) The receiving unit receives, as skill information for the step of identifying the factor, a definition of a failure mode in the control system that controls the process in the plant for each factor of the deviation event. The information processing device described in (4) or (5).

[0090] (7) The receiving unit receives, as skill information for the steps of determining countermeasures, the definition of the SOP (Standard Operating Procedure) to be used to recover from each failure mode in the control system that controls the process in the plant. The information processing device described in (4), (5), or (6).

[0091] (8) The reception unit accepts, as skill information for the steps of determining countermeasures, the definition of decision support know-how to be used to narrow down the number of SOPs. An information processing device as described in any one of (4) to (7).

[0092] (9) When a deviation event is detected, the operator terminal is provided with the skill information for each step of the OODA (Observe Orient Decide Act) loop, which is included in the OODA loop, for each deviation event occurring in the plant, from the skill data stored in the storage unit that stores the skill information for each step of the OODA loop that is included in the OODA loop and which is associated with the detected deviation event. An operation support method characterized by having a computer perform the processing.

[0093] (10) When a deviation event is detected, the operator terminal is provided with the skill information for each step of the OODA (Observe Orient Decide Act) loop, which is included in the OODA loop, for each deviation event occurring in the plant, from the skill data stored in the storage unit that stores the skill information for each step of the OODA loop that is included in the OODA loop and which is associated with the detected deviation event. An operation support program characterized by having a computer perform the processing. [Explanation of Symbols]

[0094] 1 Plant 3. Process control system 10 Information Processing Devices 11. Communication Control Unit 13 Storage section 13A Skill Data 13B Framework 14 Control Unit 15 Reception Department 16 Development Support Department 17 Providing Department 18. Software Execution Unit 30 Staff terminals 50 Operator terminals

Claims

1. A storage unit stores skill data that defines the skill information for each step in the OODA (Observe Orient Decide Act) loop, which includes identifying the cause, deciding on countermeasures, and implementing countermeasures, for each deviation event occurring in the plant. When a deviation event is detected, the provision unit provides the operator terminal with skill information from the skill data for each step of identifying the cause, deciding on countermeasures, and executing countermeasures, which are associated with the detected deviation event. It has, The aforementioned supply unit is, In the OODA loop, as a step in identifying the cause, a failure mode corresponding to the cause analyzed according to FTA (Fault Tree Analysis) corresponding to the deviation event occurring is selected. As a step in determining the countermeasures, the system accepts selection from among the Standard Operating Procedures (SOPs) associated with the failure mode, which were executed for deviation events similar to the deviation event currently occurring, and which were successful in recovery. As a step in implementing the countermeasures, the measured value of the process value trend measured after the execution of the SOP in which the selection was accepted and the predicted value of the process value trend predicted at the time of the SOP execution are displayed on the operator terminal in a comparable manner. An information processing device characterized by the following:

2. The skills data further includes skills information for the deviation detection steps included in the OODA loop. The aforementioned provisioning unit provides the operator terminal with skill information for each step of deviation detection, cause identification, countermeasure decision, and countermeasure implementation, which is associated with the detected deviation event from the skill data. The information processing apparatus according to claim 1.

3. The providing unit provides skill information for each step of deviation detection, factor identification, countermeasure determination, and countermeasure implementation through an interface corresponding to each step. The information processing apparatus according to claim 2.

4. The system further includes a reception unit that receives definitions of skill information for each step of the OODA loop, including factor identification, countermeasure determination, and countermeasure implementation, for each of the aforementioned deviation events. The information processing apparatus according to claim 1.

5. The reception unit receives, as skill information for the factor identification step, the definition of the FTA that identifies the factors of the deviation event. The information processing apparatus according to claim 4.

6. The receiving unit receives, as skill information for the factor identification step, the definition of the failure mode in the control system that controls the process in the plant for each factor of the deviation event. The information processing apparatus according to claim 4.

7. The reception unit receives, as skill information for the step of determining countermeasures, the definition of the SOP to be used to recover from each failure mode in the control system that controls the process in the plant. The information processing apparatus according to claim 4.

8. The reception unit receives, as skill information for the steps of determining countermeasures, the definition of decision support know-how used to narrow down the number of SOPs. The information processing apparatus according to claim 4.

9. When a deviation event is detected, the system provides the operator terminal with the skill information for each step of the OODA (Observe Orient Decide Act) loop, which is included in the OODA loop, corresponding to the detected deviation event. This skill information is stored in a storage unit that stores skill data defining the skill information for each step of the OODA loop. The computer performs the process, The processing provided above is, In the OODA loop, as a step in identifying the cause, a failure mode corresponding to the cause analyzed according to FTA (Fault Tree Analysis) corresponding to the deviation event occurring is selected. As a step in determining the countermeasures, the system accepts selection from among the Standard Operating Procedures (SOPs) associated with the failure mode, which were executed for deviation events similar to the deviation event currently occurring, and which were successful in recovery. As a step in implementing the countermeasures, the measured value of the process value trend measured after the execution of the SOP in which the selection was accepted and the predicted value of the process value trend predicted at the time of the SOP execution are displayed on the operator terminal in a comparable manner. An operation support method characterized by the following:

10. When a deviation event is detected, the system provides the operator terminal with the skill information for each step of the OODA (Observe Orient Decide Act) loop, which is included in the OODA loop, corresponding to the detected deviation event. This skill information is stored in a storage unit that stores skill data defining the skill information for each step of the OODA loop. Let the computer perform the process, The processing provided above is, In the OODA loop, as a step in identifying the cause, a failure mode corresponding to the cause analyzed according to FTA (Fault Tree Analysis) corresponding to the deviation event occurring is selected. As a step in determining the countermeasures, the system accepts selection from among the Standard Operating Procedures (SOPs) associated with the failure mode, which were executed for deviation events similar to the deviation event currently occurring, and which were successful in recovery. As a step in implementing the countermeasures, the measured value of the process value trend measured after the execution of the SOP in which the selection was accepted and the predicted value of the process value trend predicted at the time of the SOP execution are displayed on the operator terminal in a comparable manner. An operation support program characterized by the following features.

Images