Solution presentation system, solution presentation method, and program

Abstract

To appropriately present a countermeasure.SOLUTION: A countermeasure presentation system includes: a storage unit, a presentation unit, and a registration unit. The storage unit stores: one or a plurality of pieces of notification information associated with notification information from one or a plurality of monitor targets; information indicating a countermeasure corresponding to the notification information for each of the monitor targets; and one or a plurality of pieces of registration information registered by a user. The presentation units obtains, from the storage unit, and presents both the countermeasure corresponding to notification information associated with specified notification information and the one or plurality of pieces of registration information. The registration unit registers new registration information for the specified notification information.SELECTED DRAWING: Figure 2

Description

[Technical field]

[0001] The present disclosure relates to a solution suggestion system, a solution suggestion method, and a program. [Background technology]

[0002] Patent Document 1 discloses the following remote monitoring and control system. That is, in the remote monitoring and control system described in Patent Document 1, a plurality of remote monitoring and control devices are connected via a transmission line, and the remote monitoring and control system has a terminal connected to any remote monitoring and control device, and the terminal includes a failure recovery database that records known past failure details, a recovery history database that records a history of recovery responses, an input unit that inputs the failure details, a dialogue guidance unit that provides recovery procedures related to the failure details in a dialogue guidance format, and an output unit that notifies the failure state and displays the failure status. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] JP 2014-203116 A Summary of the Invention [Problem to be solved by the invention]

[0004] In the remote monitoring and control system described in Patent Document 1, the details of the fault and the associated recovery procedures are provided in a dialogue-guided manner. This has led to problems such as an inappropriate recovery procedure being presented if there is an error in the response during dialogue guidance, or the dialogue guidance taking an inappropriate amount of time.

[0005] The present disclosure has been made to solve the above-mentioned problems, and aims to provide a solution proposal system, a solution proposal method, and a program that are capable of presenting appropriate solutions. [Means for solving the problem]

[0006] In order to solve the above problems, the countermeasure presentation system of the present disclosure includes a memory unit that stores one or more notification information associated with notification information from one or more monitoring targets, information representing a countermeasure for the monitoring targets for the notification information, and one or more registered information registered by a user, a presentation unit that retrieves from the memory unit and presents the countermeasure for notification information associated with specified notification information and the one or more registered information, and a registration unit that newly registers the registered information for the specified notification information.

[0007] The method of presenting countermeasures according to the present disclosure includes a presentation step of using a memory unit that stores one or more notification information associated with notification information from one or more monitoring targets, information representing a countermeasure for the notification information for the monitoring targets, and one or more registration information registered by a user, to retrieve from the memory unit and present the countermeasures for notification information associated with specified notification information and the one or more registration information, and a registration step of newly registering the registration information for the specified notification information.

[0008] The program of the present disclosure causes a computer to execute a presentation step of retrieving from a memory unit one or more pieces of notification information associated with one or more monitoring targets, information representing a countermeasure for the notification information against the monitoring targets, and one or more pieces of registration information registered by a user, the countermeasure for notification information associated with specified notification information and the one or more pieces of registration information, and presenting the countermeasure, and a registration step of newly registering the registration information for the specified notification information. Effect of the Invention

[0009] According to the countermeasure presentation system, the countermeasure presentation method, and the program of the present disclosure, it is possible to present an appropriate countermeasure. [Brief description of the drawings]

[0010] [Figure 1] 1 is a system diagram illustrating a configuration example of a solution presentation system according to an embodiment of the present disclosure. [Diagram 2] 2 is a block diagram showing an example of the configuration of a Web server shown in FIG. 1. [Diagram 3] 3 is a schematic diagram showing an example of the configuration of a countermeasure database shown in FIG. 2; [Figure 4] 11 is a flowchart illustrating an overview of an operation example of a solution presentation system according to an embodiment of the present disclosure. [Diagram 5] 2 is a schematic diagram showing a display example on the user terminal shown in FIG. 1; [Figure 6] 2 is a schematic diagram showing a display example on the user terminal shown in FIG. 1; [Figure 7] 3 is a schematic diagram showing a search example in the countermeasure database shown in FIG. 2; [Figure 8] 11 is a flowchart illustrating an example of an operation of the solution presentation system according to the embodiment of the present disclosure. [Figure 9] 2 is a schematic diagram showing a display example on the user terminal shown in FIG. 1; [Figure 10] 10A and 10B are schematic diagrams for explaining an example of the operation of the solution presentation system according to the embodiment of the present disclosure. [Figure 11] 10A and 10B are schematic diagrams for explaining an example of the operation of the solution presentation system according to the embodiment of the present disclosure. [Figure 12] FIG. 1 is a system diagram of a solution presentation system according to an embodiment of the present disclosure. [Figure 13] FIG. 1 is a schematic block diagram illustrating a configuration of a computer according to at least one embodiment. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0011] Hereinafter, a solution suggestion system, a solution suggestion method, and a program according to an embodiment of the present disclosure will be described with reference to the drawings. Note that in each drawing, the same or corresponding components are designated by the same reference numerals and the description thereof will be omitted as appropriate.

[0012] First Embodiment FIG. 1 is a system diagram of the solution presentation system according to the first embodiment of the present disclosure. FIG. 2 is a block diagram showing a configuration example of the Web server 12 shown in FIG. 1. FIG. 3 is a schematic diagram showing a configuration example of the solution database 125 shown in FIG. 2. FIG. 4 is a flowchart showing an outline of an operation example of the solution presentation system 1 according to the first embodiment. FIGS. 5 and 6 are schematic diagrams showing a display example in the user terminal 4 shown in FIG. 1. FIG. 7 is a schematic diagram showing a search example in the solution database 125 shown in FIG. 2. FIG. 8 is a flowchart showing an operation example of the solution presentation system 1 according to the embodiment of the present disclosure. FIG. 9 is a schematic diagram showing a display example in the user terminal 4 shown in FIG. 1. FIGS. 10 and 11 are schematic diagrams for explaining an operation example of the solution presentation system 1 according to the embodiment of the present disclosure.

[0013] (Example of the configuration of a solution presentation system) 1 includes a database server 11 and a Web server 12 as a functional configuration constituted by a combination of a computer, hardware such as peripheral devices of the computer, and software such as programs executed by the computer and data processed by the computer. In this case, the countermeasure presentation system 1 is configured as one element of a remote monitoring system 100 that remotely monitors alarm / event data issued from a monitoring target such as a unit 3 installed in a plant 2 such as a power plant. The countermeasure presentation system 1 is a system that searches for and presents countermeasures for alarms / events issued by the plant 2.

[0014] The database server 11 receives the alarm / event data transmitted from the plant 2, and accumulates and manages the received alarm / event data in a database. The alarm / event data is information generated by a computer (not shown) that monitors the monitored object when a predetermined abnormality (an event indicating an abnormal state) is confirmed or a predetermined state or a predetermined state change (an event indicating a normal state, an abnormal state, etc.) is confirmed for a unit 3, an instrument, a device, a facility, or the entire plant as a monitored object, and indicates, for example, the date and time when the abnormality was confirmed, the identification information of the monitored object, the content of the abnormality, etc. The alarm / event data is notification information notified from the monitored object to the countermeasure presentation system 1, etc., including alarm data, which is information regarding an alarm generated from the monitored object, and event data, which is information regarding an event generated from the monitored object (or at least one of them).

[0015] The Web server 12 provides functions such as search, browsing, and registration to the user terminal 4 through the network on the Web system, and provides information indicating countermeasures. The user terminal 4 is, for example, a terminal such as a server, a desktop personal computer, a notebook personal computer, or a tablet terminal, and includes a display unit 4a. As shown in FIG. 2, for example, the Web server 4 includes a presentation unit 121, a registration unit 122, a database management unit 123, and a storage unit 124 as a functional configuration formed by a combination of hardware and software. The storage unit 124 also stores a countermeasure database 125. Here, an example of the configuration of the countermeasure database 125 will be described with reference to FIG. 3.

[0016] The countermeasure database 125 shown in FIG. 3 is configured as a graph database. The graph database is a database with a graph structure, and expresses the "relationship" between nodes by three elements, "node", "edge" and "property". The node represents an object, the edge represents the relationship between the nodes, and the property represents the attribute of the node and the edge. The graph database has a high speed search for tracing the connection, and is less affected by the increase in the amount of data compared to a relational database that searches the entire database thoroughly, and the search for tracing the connection is fast. In addition, it has a feature that the data definition is visually easy to understand from the viewpoint of a developer. The countermeasure database 125 shown in FIG. 3 has nodes N11 to N17 and edges E11 to E19. Note that FIG. 3 shows only one node for each type classified by label. However, the number of nodes is not limited to one, and is usually multiple.

[0017] Node N11 is a node that represents a monitored object such as a plant or a unit, etc. Node N11 is associated (or related) to node N12 by edge E11.

[0018] Node N12 is a node that represents master information of an alarm / event (alarm / event master information). This is basic data for alarm data and event data. Node N12 has properties such as an alarm name, a unit name, a device name, and an alarm category. Node N12 is associated with node N13 by an instruction edge E12, and is associated with node N14 by an occurrence edge E13.

[0019] Node N13 is a node representing first aid (countermeasures), and represents a countermeasure for the alarm / event represented by node N12. Node N13 has properties such as an alarm name, behavior, cause, and countermeasures.

[0020] Node N14 is a node that represents an alarm or event that has occurred in plant 2. Node N14 has properties such as the occurrence date and time, alarm name (event name), state, unit, and device name. Node N14 is associated with node N15 by a comment edge E15, and is associated with node N16 by an attached document edge E16. Note that node N14 does not extend a master edge E14 toward node N12, indicated by a dashed line, and instead defines a connection to node N12 by tracing back the occurrence edge E13. This can save on the amount of information, but if tracing is frequent, an edge may be defined.

[0021] Node N15 is a node representing a comment (registered information) registered by a user for the alarm / event of node N14. The comment is, for example, a sentence related to how to deal with the alarm / event. Node N15 has properties such as character information representing the content of the comment. Node N16 is a node representing document information (registered information) registered by a user for the alarm / event of node N14. The document information is, for example, a document (document, a document file that can be downloaded from the web, a web page, etc.) referenced when dealing with the alarm / event. Node N16 has properties such as the document name, the URL (Uniform Resource Locator) of the document reference, etc.

[0022] In this embodiment, the registered information is information that represents at least one of a comment related to a response to an alarm / event specified by a user or a document referenced when the specified alarm / event is responded to. The registered information is, for example, information that includes at least one of a comment and document information registered by a user. The registered information is also information that represents at least one of a comment related to a response to a monitoring target related to the notification information specified by a user or a document referenced when the monitoring target related to the notification information is responded to.

[0023] Node N17 is a node that represents a user. Node N17 has properties such as the user's years of experience and department. Node N17 is used to record the history of actions taken when a user registers or views a comment or document information, or when a user registers a "like" (or "favorite"), which is feedback that the comment or document was helpful. Node N17 is associated with node N16 by a registration / view edge E17, with node N15 by a registration / view edge E18, and with node N12 by a view / favorite edge E19.

[0024] In this embodiment, the following associations are made in the countermeasure database 125. That is, each alarm / event (data) node (for example, node N14) is associated with each alarm / event master node (for example, node N12). Moreover, the alarm / event master node (e.g., node N12) is associated with a first aid node (e.g., node N13). Moreover, the alarm / event master node (e.g., node N12) is associated with one or more alarm / event nodes (e.g., node N14 and multiple alarm / event nodes other than node N14, not shown). Moreover, the alarm / event node (e.g., node N14) is associated with a comment node (e.g., node N15) or a document information node (node ​​N16). In this case, the alarm / event node (e.g., node N14) is associated with other alarm / event nodes, and comment nodes and document information nodes associated with the other alarm / event nodes, via the alarm / event master node (e.g., node N12). In summary, these associations are stored in the countermeasure database 125, which stores one or more pieces of notification information associated in the notification information from one or more monitoring targets, information representing the countermeasure for the monitoring target for the notification information, and one or more pieces of registration information registered by the user.

[0025] 2, the presentation unit 121 refers to the countermeasure database 125, and acquires from the storage unit 124 the countermeasure associated with alarm / event master information corresponding to the alarm / event specified by the user, and one or more comments and document information (registered information) recorded in association with one or more identical or similar alarms / events that have occurred in the past and that are associated with the alarm / event master information, and presents them to the user terminal 4. That is, the presentation unit 121 acquires from the storage unit 124 the countermeasure for the notification information associated with the specified notification information, and one or more pieces of registered information.

[0026] Furthermore, the registration unit 122 associates new comments and document information (registration information) with the alarm / event designated by the user, and registers the new comments and document information (registration information) in the countermeasure database 125. That is, the registration unit 122 registers new registration information for the designated notification information.

[0027] Furthermore, the database management unit 123 searches and updates the countermeasure database 125 in accordance with instructions from the presentation unit 121, the registration unit 122, and the like.

[0028] (Example of the system's operation) Next, an example of the operation of the countermeasure presentation system 1 shown in Fig. 1 and Fig. 2 will be described with reference to Fig. 4 to Fig. 11. Fig. 4 shows the flow of processing when a user accesses a Web screen displayed by the Web server 12 from the user terminal 4 (step S1), selects, for example, an alarm / event that is currently occurring, checks detailed information and countermeasures for that alarm / event (step S2), and further registers a comment for the alarm / event (step S3).

[0029] In step S1, the Web server 12 (presentation unit 121) presents information for displaying, for example, a screen 40a shown in Fig. 5 on the user terminal 4. The screen 40a shown in Fig. 5 includes a list 41 (two items in this example) of alarm / event data that the user has displayed by specifying, for example, a plant 2, a unit 3, etc. In this case, in the list 41, each record representing the alarm / event data includes the following items: occurrence date and time, alarm name, status (whether it is continuing or not), unit, and device name.

[0030] In step S2, if the user selects, for example, the top alarm / event data ("Abnormality A") on the screen 40a, the Web server 12 (presentation unit 121) presents information for displaying, for example, a screen 40b shown in FIG. 6 on the user terminal 4. The screen 40b shown in FIG. 6 includes a list 42 of alarm / event data and a display area 43 showing information on first aid (measures) corresponding to the selected alarm / event data. Here, referring to FIG. 7, a process of searching the countermeasure database 125 for first aid corresponding to the specified alarm / event data will be described. The countermeasure database 125 shown in FIG. 7 differs from the countermeasure database 125 described referring to FIG. 3 in that the node N14 is changed to two, node N14a and node N14b. The node N14b corresponds to the node N14 shown in FIG. 3 that has been registered in the past (however, it is assumed that the node N14b represents the alarm / event B), and the node N14a represents the newly generated alarm / event A. Note that nodes N14a and N14b are alarm / event data of the same type or category, and an edge (not shown) is established from node N12 to node N14a. In the example shown in Fig. 7, as indicated by arrow S101, it is possible to search for first aid for the alarm / event data of node N14a by tracing from node N14a to node N12 and then from node N12 to node N13.

[0031] Next, in step S2, if the tag 43t displaying the alarm / event detail information is clicked on the screen 40b shown in FIG. 6, the Web server 12 (presentation unit 121) presents information for displaying the screen 40c shown in FIG. 9 on the user terminal 4, for example, in the process flow shown in FIG. 8. First, the Web server 12 (presentation unit 121) acquires alarm / event master information corresponding to the alarm / event that has just occurred (step S11). Next, the Web server 12 (presentation unit 121) acquires a list of alarms / events that have occurred in the past and are associated with the alarm / event master information (step S12). Next, the Web server 12 (presentation unit 121) acquires comment / document information associated with the acquired alarm / event list (step S13). In this case, by tracing each node as shown by the arrows S201 and S202 in FIG. 10, a list of alarms / events that have occurred in the past and are associated with the alarm / event master information can be acquired. The screen 40c shown in FIG. 9 includes, in a display area 44 related to alarm / event details, a display area 45 for alarm / event master information and a display area 46 for alarm / event occurrence history (alarm / event list) associated with the node N12 of the same alarm / event master. The display area 46 also includes the occurrence time of each alarm / event included in the list and the contents (part) of the comments registered in association with each alarm / event. The display area 44 also includes an input area 47 for the title of the document to be registered for the current alarm / event, an input area 48 for the document URL, and an input area 49 for the comment. The display area 46 also includes a ring button 50 (download button) for the document registered in association with the past alarm / event selected in the alarm / event occurrence history, a display area 51 for the entire contents of the comment, and a "Like" button 52 for the comment (or document). If a user who has viewed the comment (or document) finds it useful, it is recommended that the user click the "Like" button 52.

[0032] Next, in step S3 of Fig. 4, when the URL of a comment or document is entered on screen 40c shown in Fig. 9, the comment or document is registered for the current alarm / event. In this case, a new comment node and document information node associated with node N14a of the current alarm / event shown in Fig. 10 are generated, and further edges as shown by arrows S203 and S204 are set between the comment node and the document information node (the nodes in this case are new nodes other than nodes N15 and N16).

[0033] (Weighting is updated based on user behavior history, and reflected in display order) The Web server 12 (presentation unit 121) can acquire the following logs as a user's behavior history for comments and documents.

[0034] (1) The most recent date and time of viewing, (2) the number of times it was viewed / downloaded, (3) the viewing time (calculated per page), and (4) the number of “likes” given as feedback by users who found the content useful.

[0035] Based on these, the Web server 12 (presentation unit 121) can update the weighting of each comment / document. The Web server 12 (presentation unit 121) can also reflect the weighting in each item on the screen such as "Documents that have been referred to in the past" and display them in descending order of weight. Note that the points in the countermeasure database 125 where the weighting is updated are indicated by thick arrows in FIG. 11.

[0036] In this case, for example, the presentation unit 121 updates the weighting of each comment or document information (registered information) based on the user's behavioral history regarding the comment or document information (registered information), which is information indicating at least one of the most recent viewing date and time, the number of views, the viewing time, and the number of times feedback was given that the comment or document information was helpful, and when there are multiple comments or document information (registered information) to present, the comments or document information (registered information) can be presented in descending order of weight.

[0037] (Update weighting based on user and document attribute information, and reflect it in the display order) Furthermore, the Web server 12 (presentation unit 121) may update the weightings described above according to the attributes (years of experience, department, etc.) of the user who viewed (or registered) the first aid or document information, etc. In this way, the items on the screen, such as "Documents that have been referenced in the past," are displayed in descending order of weighting.

[0038] Also, based on the concept that "relatively new documents have higher quality information than documents with older creation dates", the weighting of documents registered for an alarm / event may be updated according to the creation date and time of the document. This allows documents to be displayed in descending order of weighting in each item on the screen, such as "Documents that have been referenced in the past".

[0039] In this case, for example, the presentation unit 121 updates the weighting of each comment or document information (registered information) based on at least one of the creation date and time of the document information (registered information) or the attributes of the user who viewed or registered the comment or document information (registered information), and when there are multiple comments or document information (registered information) to present, the comments or document information (registered information) can be presented in order of the highest weighting.

[0040] (Action and effect) According to the first embodiment, it is expected that the knowledge database will grow automatically as the system is used, and it becomes possible to provide more accurate and necessary information quickly. In other words, according to the first embodiment, it is possible to present appropriate countermeasures.

[0041] <Second embodiment> FIG. 12 is a system diagram of a countermeasure presentation system according to a second embodiment of the present disclosure. The countermeasure presentation system 1 according to the first embodiment shown in FIG. 1 monitors alarm / event data generated by the plant 2, whereas the countermeasure presentation system 1a shown in FIG. 12 is different in that alarm / event data generated by a simulator 5 that simulates the plant 2 is added to the monitoring targets. In the second embodiment, for example, by utilizing the simulator 5, a mechanism can be constructed that can accumulate and utilize knowledge about alarms that occur less frequently in actual operation (hereinafter, referred to as "rare alarms"). The Web server 12a has the same basic configuration as the Web server 12 shown in FIG. 2, and one countermeasure database 125 is shared for alarm / event data from the plant 2 and alarm / event data from the simulator 5.

[0042] The simulator 5 uses, for example, a machine learning model or a model that combines a physical model and a simplified model to simulate the operation of each unit of the plant 2 and generate alarm data. The simulator 5 is operated, for example, from a user terminal 6. In this case, it is desirable for the simulator 5 to have, for example, the following functions.

[0043] In other words, it is desirable for the simulator 5 to have functions such as plant operation control (start / stop), changing the simulation execution speed, a backtrack function (returning the simulator state to a past state and retraining), changing the settings of operating conditions (e.g., atmospheric temperature, cooling water temperature, etc.), setting accident items, and a pseudo-occurrence function.

[0044] Furthermore, the countermeasure presentation system 1a can select an "actual operation mode" or a "training mode", and can switch between an "actual plant environment" by the database server 11 and a "simulator environment" by the database server 13 depending on the mode. That is, the countermeasure presentation system 1a is newly equipped with a database server 13 that accumulates alarm data issued by the simulator 5. In addition, in the "actual operation mode", the Web server 12a presents countermeasures to the user terminal 4 and updates the countermeasure database 125 based on the alarm data issued by the plant 2, and in the "training mode", presents countermeasures to the user terminal 6 and updates the countermeasure database 125 based on the alarm data issued by the simulator 5.

[0045] In this case, knowledge on how to handle alarms can be accumulated by utilizing the training data generated by the simulator 5. When the "Training Mode" is selected, rare alarms, for example, that are simulated on the simulator side are displayed in a list on the "Alarm / Event Feed" screen 40a shown in FIG. 5. For example, if an operator wishes to conduct training on how to handle alarms, the trainee selects each rare alarm on the feed screen 40a. Then, by checking the countermeasures (hereinafter referred to as "first aid") for each alarm and recommended documents, training on how to handle alarms can be conducted.

[0046] The causes and countermeasures for rare alarms learned during training can be registered as knowledge comments so that they can be referenced when the same alarm occurs in actual operation. Note that the document and comment information obtained in each mode can be differentiated, and the document and comment information obtained in "actual operation mode" can be weighted more and displayed higher on the screen.

[0047] (Action and effect) According to the second embodiment, by aggregating knowledge of rare alarms generated pseudo-occurrences in addition to knowledge of alarms generated in actual operation into one knowledge base, it is possible to improve the accuracy of knowledge. In addition, since operators can confirm, register, and update knowledge of various alarms including rare alarms, it is expected that the operator's ability to respond to troubles can be improved.

[0048] (Other embodiments) Although the embodiments of the present disclosure have been described in detail above with reference to the drawings, the specific configuration is not limited to this embodiment, and design changes and the like that do not depart from the gist of the present disclosure are also included. In the above embodiment, only one plant 2 is monitored, but this is not limited thereto, and for example, multiple plants 2 may be monitored. Furthermore, the monitored object is not limited to the plant 2, and devices, equipment, and units that are not installed in the plant may be monitored. Furthermore, the countermeasure database 125 is not limited to a graph database, and may be a database in another format, or may be a combination of a database in another format and a graph database.

[0049] Computer Configuration FIG. 13 is a schematic block diagram illustrating a configuration of a computer according to at least one embodiment. The computer 90 comprises a processor 91, a main memory 92, a storage 93, and an interface 94. The above-mentioned countermeasure presentation systems 1 and 1a are implemented in a computer 90. The operations of the above-mentioned processing units are stored in the form of a program in a storage 93. A processor 91 reads the program from the storage 93, loads it in a main memory 92, and executes the above-mentioned processing in accordance with the program. The processor 91 also secures storage areas in the main memory 92 corresponding to the above-mentioned storage units in accordance with the program.

[0050] The program may be for realizing a part of the functions to be performed by the computer 90. For example, the program may be for realizing the functions by combining with other programs already stored in the storage or by combining with other programs implemented in other devices. In another embodiment, the computer may include a custom LSI (Large Scale Integrated Circuit) such as a PLD (Programmable Logic Device) in addition to or instead of the above configuration. Examples of PLDs include PAL (Programmable Array Logic), GAL (Generic Array Logic), CPLD (Complex Programmable Logic Device), and FPGA (Field Programmable Gate Array). In this case, some or all of the functions to be realized by the processor may be realized by the integrated circuit.

[0051] Examples of the storage 93 include a hard disk drive (HDD), a solid state drive (SSD), a magnetic disk, a magneto-optical disk, a compact disc read only memory (CD-ROM), a digital versatile disc read only memory (DVD-ROM), and a semiconductor memory. The storage 93 may be an internal medium directly connected to the bus of the computer 90, or an external medium connected to the computer 90 via an interface 94 or a communication line. In addition, when the program is distributed to the computer 90 via a communication line, the computer 90 that receives the program may load the program into the main memory 92 and execute the above-mentioned process. In at least one embodiment, the storage 93 is a non-transitory tangible storage medium.

[0052] <Additional Notes> The solution presentation systems 1 and 1a described in the respective embodiments can be understood, for example, as follows.

[0053] (1) The countermeasure presentation system 1 and 1a according to the first embodiment includes a storage unit 124 that stores one or more pieces of notification information (node ​​N14b) associated in notification information (alarm / event data, node N14a) from one or more monitored objects (plant 2, unit 3), information (node ​​N13) that indicates a countermeasure for the monitored object for the notification information, and one or more pieces of registered information (nodes N15, N16) registered by a user, a presentation unit 121 that acquires from the storage unit and presents the countermeasure and the one or more pieces of registered information for notification information (node ​​N14b) associated with designated notification information (node ​​N14a), and a registration unit 122 that newly registers the registered information for the designated notification information. According to this embodiment and each of the following embodiments, it is possible to present an appropriate countermeasure.

[0054] (2) The second aspect of the solution presentation systems 1 and 1a is the solution presentation systems 1 and 1a of (1), in which the registration information represents at least one of a comment (node ​​N15) related to the response to the monitored object related to the specified notification information or a document (node ​​N16) referenced when the response to the monitored object related to the specified notification information is addressed.

[0055] (3) The solution presentation systems 1 and 1a relating to the third aspect are the solution presentation systems 1 and 1a of (1) or (2), in which the presentation unit 121 updates the weighting of each piece of registered information based on the user's behavioral history for the registered information, which represents at least one of the most recent viewing date and time, the number of views, the viewing time, and the number of feedbacks indicating that the information was helpful, and presents the registered information in descending order of weight when there are multiple pieces of registered information to present.

[0056] (4) The solution presentation systems 1 and 1a relating to the fourth aspect are the solution presentation systems 1 and 1a according to (1) to (3), in which the presentation unit 121 updates the weighting of each piece of registered information based on at least one of the creation date and time of the registered information or the attributes of the user who viewed or registered the registered information, and when there are multiple pieces of registered information to present, presents each piece of registered information in descending order of weighting.

[0057] (5) The fifth aspect of the solution presentation system 1a is the solution presentation system 1a of any one of (1) to (4), in which the memory unit 124 further stores one or more pieces of notification information associated with the notification information from the simulator 5 and one or more pieces of registration information registered by a user for the notification information.

[0058] (6) The sixth aspect of the countermeasure presentation systems 1 and 1a is a countermeasure presentation system 1a according to any one of (1) to (5), wherein the notification information includes at least one of information regarding an event generated from the monitored object or information regarding an alarm. [Explanation of symbols]

[0059] 1, 1a…Solution suggestion system 2. Plant 3. Unit 4, 6...User terminal 11, 13...Database server 12…Web server 121…Presentation part 122…Registration Department 123…Database Management Department 124...Storage section 125...Corrective action database

Claims

1. a storage unit that stores a plurality of pieces of notification information associated with one or a plurality of notification information from a monitoring target by being identical or similar to the notification information, and for each of the plurality of pieces of notification information, information indicating a countermeasure for the monitoring target and one or a plurality of pieces of registration information registered by a user; a presentation unit that acquires from the storage unit information indicating the countermeasures for each of a plurality of pieces of notification information associated with the notification information designated by a user and the one or more pieces of registration information, and presents the information; a registration unit that newly registers the registration information for the notification information designated by the user; Equipped with The registration information includes information representing a document referenced when dealing with the monitoring target related to the specified notification information, The storage unit includes a countermeasure database, The countermeasure database has a graph database represented by nodes representing information objects, edges representing relationships between the nodes, and properties representing attributes of the nodes and edges; The graph database includes: a notification information node representing the notification information; A notification information master node representing master information of the notification information; a document information node representing information representing the document; an edge indicating a relationship between the notification information node and the notification information master node; an edge indicating a relationship between the notification information node and a document information node; Includes: The presentation unit, from the graph database, Obtain notification information master information corresponding to the notification information specified by the user, Obtaining notification information associated with the obtained notification information master information; Acquire and present information representing the document associated with each of the acquired notification information. A system that suggests solutions.

2. The registration information is information that represents the document that was referenced when dealing with the monitoring target related to the specified notification information. The method suggestion system according to claim 1 .

3. The presentation unit updates a weighting of each piece of registered information based on a user's behavior history for the registered information, which indicates at least one of the most recent viewing date and time, the number of views, the viewing time, and the number of feedbacks indicating that the information was helpful, and presents the registered information in descending order of weight when there are multiple pieces of registered information to present. The system for presenting a solution according to claim 1 .

4. The presentation unit updates a weighting of each piece of registered information based on at least one of a creation date and time of the registered information and an attribute of a user who has viewed or registered the registered information, and when there are a plurality of pieces of registered information to present, presents each piece of registered information in descending order of weight. The system according to claim 1 , wherein the countermeasure presentation system is a system for presenting a countermeasure to a problem.

5. The storage unit further stores one or more pieces of notification information associated with the notification information from the simulator, and one or more pieces of registration information registered by a user for the notification information. The system for presenting a solution according to claim 1 .

6. 6. The system according to claim 1, wherein the notification information includes at least one of information regarding an event generated from a monitoring target and information regarding an alarm.

7. using a storage unit that stores a plurality of pieces of notification information associated with one or a plurality of notification information from a monitoring target by being identical or similar to the notification information from the one or a plurality of monitoring targets, and, for each of the plurality of pieces of notification information, information representing a countermeasure for the monitoring target and one or a plurality of pieces of registration information registered by a user; a presentation step of acquiring, from the storage unit, information indicating the countermeasures for each of a plurality of pieces of notification information associated with the notification information designated by a user, and the one or more pieces of registration information, and presenting the information; a registration step of newly registering the registration information for the notification information designated by the user; Including, The registration information includes information representing a document referenced when dealing with the monitoring target related to the specified notification information, The storage unit includes a countermeasure database, The countermeasure database has a graph database represented by nodes representing information objects, edges representing relationships between the nodes, and properties representing attributes of the nodes and edges; The graph database includes: a notification information node representing the notification information; A notification information master node representing master information of the notification information; a document information node representing information representing the document; an edge indicating a relationship between the notification information node and the notification information master node; an edge indicating a relationship between the notification information node and a document information node; Includes: In the presenting step, Obtain notification information master information corresponding to the notification information specified by the user, Obtaining notification information associated with the obtained notification information master information; Acquire and present information representing the document associated with each of the acquired notification information. How to present a solution.

8. using a storage unit that stores a plurality of pieces of notification information associated with one or a plurality of notification information from a monitoring target by being identical or similar to the notification information from the one or a plurality of monitoring targets, and, for each of the plurality of pieces of notification information, information representing a countermeasure for the monitoring target and one or a plurality of pieces of registration information registered by a user; a presentation step of acquiring, from the storage unit, information indicating the countermeasures for each of a plurality of pieces of notification information associated with the notification information designated by a user, and the one or more pieces of registration information, and presenting the information; a registration step of newly registering the registration information for the notification information designated by the user; A program for causing a computer to execute the following: The registration information includes information representing a document referenced when dealing with the monitoring target related to the specified notification information, The storage unit includes a countermeasure database, The countermeasure database has a graph database represented by nodes representing information objects, edges representing relationships between the nodes, and properties representing attributes of the nodes and edges; The graph database includes: a notification information node representing the notification information; A notification information master node representing master information of the notification information; a document information node representing information representing the document; an edge indicating a relationship between the notification information node and the notification information master node; an edge indicating a relationship between the notification information node and a document information node; Includes: In the presenting step, Obtain notification information master information corresponding to the notification information specified by the user, Obtaining notification information associated with the obtained notification information master information; Acquire and present information representing the document associated with each of the acquired notification information. A program that causes a computer to do something.

Images