Information processing method, information processing program, and information processing apparatus

The information processing method and device enhance maintenance efficiency by identifying and displaying maintenance plans for multiple faults based on historical data, facilitating simultaneous maintenance planning.

JP7835191B2Active Publication Date: 2026-03-25YOKOGAWA ELECTRIC CORP
View PDF 6 Cites 0 Cited by

Patent Information

Authority / Receiving Office
JP · JP
Patent Type
Patents
Current Assignee / Owner
Filing Date
2023-03-31
Publication Date
2026-03-25

AI Technical Summary

Technical Problem

Conventional maintenance systems do not provide users with the necessary information to efficiently decide whether to perform maintenance work on multiple faults simultaneously, leading to inefficiencies in maintenance planning.

Method used

An information processing method and device that acquires defect information, identifies maintenance plans for similar defects, and displays past information related to these defects, allowing users to consider simultaneous maintenance of multiple faults based on historical data.

Benefits of technology

Improves the efficiency of maintenance work by enabling users to plan and execute maintenance tasks for multiple faults collectively, leveraging historical data and maintenance plans for similar defects.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure 0007835191000004
    Figure 0007835191000004
  • Figure 0007835191000005
    Figure 0007835191000005
  • Figure 0007835191000006
    Figure 0007835191000006
Patent Text Reader

Abstract

To improve efficiency of maintenance work of a user.SOLUTION: An information processing method allows a computer to execute processing of acquiring failure information on a failure and identifying a maintenance plan corresponding to a similar failure similar to the failure. The information processing method allows the computer to execute processing of identifying a past failure on the basis of an occurrence time of the similar failure and displaying past information on the past failure and maintenance plan information on the maintenance plan corresponding to the similar failure.SELECTED DRAWING: Figure 1
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

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

Background Art

[0002] Techniques for assisting a user's decision-making based on history are known. For example, in the field of content distribution via the Internet, a technique for recommending content that is expected to be preferred by a user based on the user's viewing history is used. Also, in the retail field, a technique for recommending products that are highly likely to be purchased by a user based on the user's purchase history is used.

[0003] Techniques for assisting a user's decision-making based on such history are also useful in the industrial field. For example, a technique for automatically generating a maintenance plan for industrial machines based on the results of inspections performed in the past is known. Also, a technique for predicting the occurrence of abnormalities from the past state of a facility is known.

Prior Art Documents

Patent Documents

[0004]

Patent Document 1

Patent Document 2

Summary of the Invention

Problems to be Solved by the Invention

[0005] The conventional technology has room for improvement from the viewpoint of performing maintenance work efficiently.

[0006] For example, in the conventional technology, for one failure, the system generates a maintenance plan for preventing or repairing the failure. In contrast, for example, it may be more efficient to perform maintenance work collectively for a plurality of failures.

[0007] However, conventional technology does not provide users with the information necessary to decide whether or not to perform maintenance work on multiple faults at once. Therefore, users are unable to determine whether or not to perform multiple maintenance work on multiple faults at once.

[0008] In one aspect, the objective is to provide an information processing method, information processing program, and information processing device that can improve the efficiency of user maintenance work. [Means for solving the problem]

[0009] The information processing method relating to one aspect is characterized in that a computer acquires defect information relating to a defect and performs a process to identify a maintenance plan corresponding to a similar defect similar to the defect. The information processing method is also characterized in that the computer identifies past defects based on the time of occurrence of the similar defect and performs a process to display past information relating to the past defect and maintenance plan information relating to the maintenance plan corresponding to the similar defect.

[0010] The information processing program relating to one aspect is characterized by causing a computer to perform a process to acquire defect information related to a defect and to identify a maintenance plan corresponding to a similar defect. The information processing program is also characterized by causing a computer to perform a process to identify past defects based on the time of occurrence of the similar defect and to display past information related to the past defect and maintenance plan information related to the maintenance plan corresponding to the similar defect.

[0011] The information processing device relating to one aspect is characterized by comprising an acquisition unit, a plan identification unit, a defect identification unit, and a display control unit. The acquisition unit acquires defect information relating to a defect. The plan identification unit identifies a maintenance plan corresponding to a similar defect similar to the defect. The defect identification unit identifies past defects based on the time of occurrence of the similar defect. The display control unit displays past information relating to the past defect and maintenance plan information relating to the maintenance plan corresponding to the similar defect. [Effects of the Invention]

[0012] According to one embodiment, the efficiency of user maintenance work can be improved. [Brief explanation of the drawing]

[0013] [Figure 1] This figure shows an example of the presentation process according to the embodiment. [Figure 2] This figure shows an example configuration of an information processing system according to the embodiment. [Figure 3] This is a block diagram showing an example configuration of an information processing device according to the embodiment. [Figure 4] This figure shows an example of past defect information accumulated in the defect database according to the embodiment. [Figure 5] This figure shows an example of a maintenance plan stored in the maintenance plan database according to the embodiment. [Figure 6] This figure shows an example of hazard information stored in the hazard information database according to the embodiment. [Figure 7] This figure shows an example of a malfunction reporting screen according to the embodiment. [Figure 8] This figure shows an example of a rating table according to the embodiment. [Figure 9] This figure shows an example of a rating table according to the embodiment. [Figure 10] This figure shows an example of a search results screen for a maintenance plan according to the embodiment. [Figure 11] This figure shows an example of a graph display screen according to the embodiment. [Figure 12] It is a flowchart showing an example of the information processing flow according to the embodiment. [Figure 13] It is a diagram for explaining an example of the hardware configuration.

Embodiments for Carrying Out the Invention

[0014] Hereinafter, embodiments of the information processing method, information processing program, and information processing apparatus disclosed in the present application will be described in detail based on the drawings. Note that the invention of the present application is not limited by the embodiments described here. Also, the same reference numerals are assigned to the same elements, and duplicate descriptions are omitted as appropriate. Further, the respective embodiments can be appropriately combined within a non - contradictory range.

[0015] [1. Outline of the Presentation Process] FIG. 1 is a diagram showing an example of the presentation process according to the embodiment. The information processing system 1 shown in FIG. 1 includes an information processing apparatus 10 and a terminal apparatus 20. The presentation process according to the embodiment is executed by the information processing apparatus 10. By executing the presentation process, the information processing apparatus 10 presents a maintenance plan for a malfunction in a facility such as a plant to a user U1 who uses the terminal apparatus 20.

[0016] As shown in FIG. 1, the information processing apparatus 10 first acquires malfunction information regarding a malfunction (hereinafter, also referred to as the first malfunction) from the user U1 via the terminal apparatus 20 (step S1). The malfunction information is, for example, information regarding a malfunction such as a failure that occurred in a facility such as a plant.

[0017] The information processing apparatus 10 specifies a maintenance plan based on malfunctions similar to the malfunction information (hereinafter, also referred to as similar malfunctions) (step S2). It is assumed that the information processing apparatus 10 has stored in advance maintenance plans corresponding to similar malfunctions.

[0018] Furthermore, the information processing device 10 identifies information about a second defect to present to user U1 from past defect information (step S3). The second defect (an example of a past defect; hereinafter also referred to as an additional defect) is a defect identified, for example, according to the time when a similar defect occurred. The second defect may or may not be related to the defect obtained from user U1.

[0019] The information processing device 10 presents the identified maintenance plan and information regarding the second defect to the user U1 via the terminal device 20 (step S4).

[0020] In this way, the information processing device 10 presents the user U1 with information regarding the maintenance plan and the second malfunction. Here, the second malfunction is a malfunction corresponding to the time when a similar malfunction occurred, as described above, for example, a malfunction that occurred within a predetermined period after the occurrence of a similar malfunction.

[0021] This allows user U1 to review the maintenance plan for the first defect and to identify a second defect that may occur after the first defect. User U1 can also consider whether the maintenance work for the first defect and the maintenance work for the second defect can be performed together, thereby improving the efficiency of maintenance work.

[0022] [2. System Configuration Example] Figure 2 shows an example of the configuration of an information processing system 1 according to an embodiment. As shown in Figure 2, the information processing system 1 comprises an information processing device 10 and a terminal device 20.

[0023] The information processing device 10 is, for example, a server device. The terminal device 20 is, for example, a stationary or portable terminal device such as a personal computer, a tablet terminal, or a smartphone.

[0024] The information processing device 10 and the terminal device 20 are connected to each other via, for example, a network N. Network N is, for example, the Internet. Alternatively, network N may be a LAN (Local Area Network) established within a facility such as a plant.

[0025] Here, information processing system 1 is a system for recommending (presenting) maintenance plans for the plant. For example, information processing system 1 presents user U1 with multiple maintenance plans for plant malfunctions. Information processing system 1 also presents user U1 with information about a second malfunction.

[0026] In this case, user U1 can actually adopt any of the presented maintenance plans. Alternatively, user U1 can adopt a maintenance plan that takes into account a second defect.

[0027] This allows the information processing system 1 to support user U1's decision-making and improve user U1's work efficiency.

[0028] In this embodiment, the plant is, for example, an oil plant, a petrochemical plant, a chemical plant, or a gas plant. When the plant is in operation, products such as LNG (liquefied natural gas), resins (plastics, nylon, etc.) and chemical products are obtained.

[0029] Furthermore, the plant includes factory facilities, machinery facilities, production facilities, power generation facilities, storage facilities, and facilities at the wellhead for extracting oil, natural gas, etc. In addition to equipment for generating products, the plant is also equipped with field instruments for acquiring information about the plant's condition.

[0030] Field devices include sensor devices, operating devices, and alarm devices. For example, sensor devices include pressure sensors, temperature sensors, pH sensors, speed sensors, and acceleration sensors. For example, operating devices include valves, pumps, and fans, which are driven by motors and actuators. For example, alarm devices include lamps and speakers.

[0031] Various malfunctions can occur in a plant. These malfunctions are abnormalities in facilities, equipment, field instruments, etc., and are events that have an adverse effect on the plant. These adverse effects include the cessation and delay of product production, and increased costs (e.g., monetary costs, human costs, time costs).

[0032] User U1 will develop a maintenance plan to resolve any malfunctions that occur. This maintenance plan may include, for example, repairing, cleaning, or replacing parts of the malfunctioning equipment. Note that maintenance plans may also be implemented to prevent malfunctions, regardless of whether a malfunction has occurred.

[0033] User U1 is, for example, a plant manager or someone who develops maintenance plans to resolve malfunctions. Here, User U1 is responsible for both inputting the malfunctions and developing the maintenance plans, but it is also possible for different users to perform these tasks.

[0034] For example, a plant engineer may input the malfunction information, while the plant manager may formulate the maintenance plan. In this case, the terminal device 20 for inputting the malfunction information and the terminal device 20 for receiving the maintenance plan and information about the second malfunction may be separate devices. For example, the information processing device 10 may receive malfunction information from the terminal device 20 operated by the engineer and transmit the maintenance plan and information about the second malfunction to the terminal device 20 operated by the plant manager.

[0035] [2-1. Example of Information Processing Device Configuration] Figure 3 is a block diagram showing an example configuration of an information processing device 10 according to an embodiment. As shown in Figure 3, the information processing device 10 comprises a communication unit 11, a storage unit 12, and a control unit 13.

[0036] (Communications Section 11) The communication unit 11 is a processing unit that communicates with other devices, and is implemented, for example, by a communication interface. For example, the communication unit 11 communicates with the terminal device 20.

[0037] (Storage unit 12) The storage unit 12 is a processing unit that stores various data and various programs executed by the control unit 13. The storage unit 12 is implemented by, for example, memory and a hard disk. This storage unit 12 stores various data generated in the processing executed by the information processing device 10, such as data obtained in the process of the control unit 13 executing various processes and processing results obtained as a result of executing various processes.

[0038] As shown in Figure 3, the memory unit 12 includes a malfunction DB 121, a maintenance plan DB 122, and a hazard information DB 123.

[0039] (Defect DB121) The defect DB121 stores past defect information related to past defects that have occurred. Figure 4 shows an example of past defect information stored by the defect DB121 according to this embodiment. As shown in Figure 4, the past defect information includes the following items: "Defect ID", "Date and Time", "Location", "Team", "Severity", "Problem", and "Detailed Information".

[0040] The "Defect ID" field is information used to identify the defect. The "Date and Time" field is the date and time the defect occurred, or the date and time the defect information was registered in Defect DB121. The "Location" field indicates the location within the plant where the defect occurred. The "Team" field indicates the team associated with the facility, equipment, or device affected by the defect.

[0041] The "Importance" field indicates the severity of the issue. For example, the "Importance" value can be expressed as "Very High," "High," "Medium," or "Low."

[0042] The "Problem" field provides an overview of the bug and is described by the user who registers (or reports) the bug. The "Details" field provides detailed information about the bug and is described by the user who registers (or reports) the bug.

[0043] For example, Figure 4 shows that the malfunction identified as "DF0151" occurred on the date and time "2022 / 4 / 1 13:01" at the location "Area_1", the team responsible for the malfunction is "Team_1", ​​and the severity is "low". Figure 4 also shows that the summary of the malfunction identified as "DF0151" is "gas leak", and the detailed information is "gas leak in Area_1".

[0044] (Maintenance Plan DB122) The maintenance plan DB122 stores information on completed maintenance plans. Figure 5 shows an example of a maintenance plan stored by the maintenance plan DB122 according to this embodiment. As shown in Figure 5, the maintenance plan includes the following items: "Maintenance Plan ID", "Date and Time", "Type of Failure", "Cause of Failure", "Solution", "Component", "Required Preparations", "Safety Requirements", "Number of Personnel", "Time Required", "Cost", and "Failure ID".

[0045] The "Maintenance Plan ID" field is information used to identify the maintenance plan. The "Date and Time" field is the date and time the maintenance plan was implemented (the start or completion date and time), or the date and time the maintenance plan information was registered in the Maintenance Plan DB122.

[0046] The item "Type of Defect" indicates the type of defect corresponding to the maintenance plan. For example, a defect corresponding to the maintenance plan is a defect that the maintenance plan aims to resolve, or a defect that is expected to be prevented from occurring by the maintenance plan. The item "Cause" indicates the cause of the defect corresponding to the maintenance plan. The item "Solution" indicates the specific solution for the defect corresponding to the maintenance plan. The item "Component" is a component that has a close relationship with the maintenance plan or the defect corresponding to the maintenance plan.

[0047] The item "Required Preparations" contains information on the items, skills, and procedures necessary for the maintenance plan. The item "Safety Requirements" contains the safety requirements that must be met in the maintenance plan. The item "Number of Personnel" is the number of personnel required to implement the maintenance plan (personnel cost). The item "Time Required" is the time required to implement the maintenance plan (time cost). The item "Cost" is the cost incurred to implement the maintenance plan (monetary cost). The item "Defect ID" is information used to associate the maintenance plan with the defect.

[0048] For example, Figure 5 shows that the maintenance plan identified as "MT0211" was implemented on the date and time "2022 / 4 / 1 14:21". Figure 5 also shows that the maintenance plan identified as "MT0211" corresponds to the malfunction identified as "DF0151".

[0049] Furthermore, Figure 5 shows that the type of malfunction corresponding to the maintenance plan identified as "MT0211" is "leakage," the cause is "aging deterioration," the solution is "repair and improvement," and the component is "valve."

[0050] Furthermore, Figure 5 shows that the preparations required for the maintenance plan identified as "MT0211" are "scaffolding installation, containers," and the safety requirements are "gas detection, harness wearing."

[0051] Furthermore, Figure 5 shows that the maintenance plan identified as "MT0211" required "5 personnel," took "6 hours," and cost "¥1,500,000."

[0052] (Hazard Information DB123) Hazard Information DB123 stores hazard information regarding risks related to the subject of the maintenance plan. Figure 6 shows an example of hazard information stored by Hazard Information DB123 according to this embodiment. As shown in Figure 6, the hazard information includes the items "Subject," "Risk Level," "Type of Hazard," and "Safety Requirements."

[0053] The "Target" item is information used to identify the object that indicates a hazard. For example, the "Target" item is information that identifies the location, facility, equipment, machinery, or component within a plant.

[0054] The "Risk Level" item indicates the magnitude of the risk involved. For example, the "Importance Level" value can be one of three options: "High," "Medium," or "Low."

[0055] The item "Type of Hazard" contains information about the types of hazards that may occur in the subject. The item "Safety Requirements" contains the safety requirements that are required depending on the type of hazard.

[0056] For example, Figure 6 shows that the risk level of "Area_1" is "medium," the type of risk that may occur is related to "height," and the safety requirement is "wearing a harness."

[0057] (Control Unit 13) The control unit 13 controls the entire information processing device 10. The control unit 13 includes an acquisition unit 131, a plan identification unit 132, a defect identification unit 133, and a display control unit 134. Here, the control unit 13 can be implemented by, for example, an electronic circuit such as a CPU (Central Processing Unit) or an MPU (Micro Processing Unit), or an integrated circuit such as an ASIC (Application Specific Integrated Circuit) or an FPGA (Field Programmable Gate Array).

[0058] (Acquisition part 131) The acquisition unit 131 acquires malfunction information, which is information about malfunctions that have occurred in the plant.

[0059] The malfunction information is the malfunction information reported to the information processing system 1. For example, the acquisition unit 131 acquires the malfunction information via the malfunction report screen 61 that the display control unit 134 displays on the terminal device 20.

[0060] Figure 7 shows an example of a malfunction reporting screen 61 according to the embodiment. The malfunction reporting screen 61 shown in Figure 7 is displayed on the terminal device 20 by the display control unit 134.

[0061] As shown in Figure 7, the bug report screen 61 displays a pull-down list 61a, a pull-down list 61b, a pull-down list 61c, a text box 61d, a text box 61e, and a button 61f.

[0062] The dropdown list displays one or more options. Furthermore, one of the options displayed by the dropdown list is selected by user U1.

[0063] The pull-down list 61a displays "Area_1", "Area_2", "Area_3", and "Area_4" as predetermined candidate locations within the plant.

[0064] The pull-down list 61b displays "Team_1", ​​"Team_2", "Team_3", and "Team_4" as predefined team candidates.

[0065] The pull-down list 61c displays "Very High," "High," "Medium," and "Low" as predetermined importance level options.

[0066] Text boxes 61d and 61e accept text input from user U1. However, the number of characters that can be entered into text box 61d is set to be less than the number of characters that can be entered into text box 61e.

[0067] When button 61f is pressed, the contents entered in each object (pull-down list and text box) of the malfunction report screen 61 are sent to the information processing device 10. This allows the acquisition unit 131 to acquire the malfunction information.

[0068] For example, if button 61f is pressed in the state shown in Figure 7, the acquisition unit 131 acquires fault information where the location is "Area_2" and the team is "Team_3". The acquisition unit 131 also acquires fault information where the severity is "medium", the problem is "gas leak", and the detailed information is "carbon dioxide leaking from the tank".

[0069] The acquisition unit 131 outputs the acquired defect information to the planning identification unit 132 and also stores it in the defect DB 121.

[0070] (Planning Specific Section 132) The planning identification unit 132 identifies maintenance plans that are similar to the defects indicated by the defect information (also referred to as similar defects) from among the maintenance plan information that has been stored in advance and associated with defects.

[0071] First, the planning identification unit 132 converts the defect information and the defect DB 121 into a rating table. Figures 8 and 9 show an example of a rating table according to this embodiment.

[0072] Here, we assume that the location of the malfunction information is "Area_2", the team is "Team_3", the severity is "Medium", the problem is "Gas leak", and the details are "Carbon dioxide leaking from the tank".

[0073] The planning unit 132 obtains the rating table shown in Figure 8 by converting the defect information. As shown in Figure 8, the rating table reflects the "location," "team," and "severity" included in the defect information.

[0074] In the rating table, items included in the defect information have a value of "5," while items not included in the defect information have a value of "1."

[0075] Since the location of the defect information is "Area_2", the values ​​for "Area_1", "Area_3", and "Area_4" in the rating table are "1", and the value for "Area_2" is "5".

[0076] Rating tables are represented as vectors. For example, the rating table shown in Figure 8 corresponds to the vector (1,5,1,1,1,1,5,1,1,1,5,1).

[0077] Furthermore, the planning identification unit 132 obtains the rating table shown in Figure 9 by converting past defect information stored in the defect DB 121. Figure 9 shows the rating tables for defects "DF0151" and "DF0152". Note that the planning identification unit 132 is not limited to converting two past defect information records. The planning identification unit 132 may convert one or three or more past defect information records.

[0078] The rating table for defect "DF0151" corresponds to the vector (5,1,1,1,5,1,1,1,1,1,1,5). The rating table for defect "DF0152" corresponds to the vector (5,1,1,1,1,1,5,1,1,1,1,5).

[0079] The planning identification unit 132 calculates the similarity between the rating table obtained by converting the defect information and the rating table obtained by converting the past defect information of the defect DB 121. At this time, the planning identification unit 132 considers the rating table as a vector and calculates the cosine similarity between the vectors using equation (1).

[0080]

number

[0081] However, A and B are vectors for which similarity is calculated. Also, for example, A i is the i-th element of vector A. n is the number of elements in the vector. In the examples in Figures 8 and 9, n = 12.

[0082] Furthermore, the planning identification unit 132 calculates the similarity between defects using TF-IDF as shown in equation (2), based on the "problem" and "detailed information" sections of past defect information included in the defect information and defect DB 121 that were not converted into a rating table. Here, the "problem" and "detailed information" for each defect are considered as documents.

[0083]

number

[0084] However, t is the number of occurrences of the target word in the "Problem" and "Detailed Information" sections of the defect information. n is the number of documents stored in the defect DB121. df is the number of documents stored in the defect DB121 that contain the target word.

[0085] Let the similarity calculated by equation (1) be Sim1, and the similarity calculated by equation (2) be Sim2. The planning unit 132 then calculates the final similarity as shown in equation (3).

[0086]

number

[0087] However, w is a pre-set weight. w is a value between 0 and 1, for example, it could be 0.5.

[0088] Furthermore, the method for calculating the similarity between defects is not limited to that described here. The planning identification unit 132 may calculate the similarity between defects using any known method for calculating the similarity between data.

[0089] The planning identification unit 132 extracts a certain number of past defects from the defect DB 121 as similar defects, in order of their similarity to the defect information. The number of similar defects (a certain number) extracted by the planning identification unit 132 may be a number predetermined in the information processing system 1, or a number specified by user U1.

[0090] Furthermore, the planning identification unit 132 identifies maintenance plans corresponding to the extracted similar defects from among the maintenance plans stored in the maintenance plan DB 122. For example, the planning identification unit 132 identifies maintenance plans corresponding to similar defects based on the "defect ID" item in the maintenance plan DB 122.

[0091] The plan identification unit 132 outputs information about the extracted similar defects to the defect identification unit 133. The plan identification unit 132 also outputs information about the identified maintenance plan to the display control unit 134.

[0092] (Defect Identification Section 133) The defect identification unit 133 identifies a second defect from past defects based on the occurrence time of similar defects extracted by the planning identification unit 132. The second defect is, for example, a defect that occurred within a predetermined period after the occurrence of a similar defect.

[0093] The second defect is not necessarily limited to defects that occurred in relation to similar defects. The second defect may be any past defect identified based on the time of occurrence, and may not be related (e.g., causally related) to similar defects.

[0094] The defect identification unit 133 identifies a second defect based on the occurrence time of the most similar defect among the similar defects extracted by the planning identification unit 132.

[0095] The defect identification unit 133 identifies, for example, past defects that occurred within six months of the time of occurrence of the most similar defect from the defect database 121 as a second defect. In this case, the defect identification unit 133 may also identify past defects as a second defect that have the same location and characteristics as the most similar defect. In this case, the defect identification unit 133 identifies the second defect by referring to the maintenance plan database 122 in addition to the defect database 121.

[0096] For example, the defect identification unit 133 may identify a past defect as a second defect if its occurrence location is the same as that of the most similar defect. In addition to identifying the occurrence location of the defect, the defect identification unit 133 may also identify a past defect as a second defect if the component included in the maintenance plan is the same as that of the most similar defect.

[0097] The defect identification unit 133 outputs second defect information relating to the identified second defect to the display control unit 134.

[0098] In this example, the defect identification unit 133 identifies a second defect based on the occurrence time of the most similar defect; however, the method by which the defect identification unit 133 identifies the second defect is not limited to this.

[0099] For example, the defect identification unit 133 may identify a second defect based on the occurrence time of a similar defect specified by user U1. Alternatively, the defect identification unit 133 may identify a second defect based on the occurrence times of all similar defects extracted by the planning identification unit 132.

[0100] (Display control unit 134) The display control unit 134 controls the display of the screen. The display control unit 134 causes the terminal device 20 to display the screen.

[0101] For example, the display control unit 134 functions as a web server. That is, the display control unit 134 generates data (for example, an HTML file) for displaying the screen. The display control unit 134 then transmits the generated data to the terminal device 20. The terminal device 20 displays the screen based on the data received from the display control unit 134 in a web browser or the like.

[0102] The terminal device 20 may display the screen using a dedicated application of the information processing system 1 instead of a web browser. In this case, the display control unit 134 transmits data in a format compatible with the application.

[0103] The display control unit 134, for example, displays the aforementioned malfunction report screen 61 on the terminal device 20. The display control unit 134 also displays the maintenance plan search results screen 62 on the terminal device 20.

[0104] Figure 10 shows an example of a search results screen 62 of a maintenance plan according to an embodiment. As shown in Figure 10, the search results screen 62 includes a display area 62a, a search results area 62b, a button 62c, and a defect display area 62d.

[0105] As shown in Figure 10, the display area 62a displays defect information related to the defect being searched for (reported defect). Here, the defect that occurred in "Area_2", was assigned to "Team_3", had a severity level of "Medium", was a "gas leak", and had detailed information that "carbon dioxide is leaking from the tank" is displayed in the display area 62a.

[0106] The search results area 62b displays planning information (an example of maintenance plan information) related to the maintenance plan identified by the planning identification unit 132 based on the defects displayed in the display area 62a. Here, for example, the planning information is displayed in order of the similarity calculated by the planning identification unit 132.

[0107] The display control unit 134 displays, for example, the following information as maintenance plan information in the search results area 62b: "Defect ID," "Maintenance Plan ID," "Type of Defect," "Cause of Defect," "Solution," "Component," "Required Preparations," "Safety Requirements," "Number of Personnel," "Required Time," and "Cost."

[0108] In the example shown in Figure 10, the plan information is displayed when the plan identification unit 132 identifies the maintenance plans "MT0213", "MT0211", and "MT0215".

[0109] Button 62c is a button that switches the display of search results. When user U1 presses button 62c, the display control unit 134 switches the display of search results from a list view to a graph view. For example, in response to the press of button 62c, the display control unit 134 displays the graph display screen 63.

[0110] Figure 11 shows an example of a graph display screen 63 according to the embodiment. As shown in Figure 11, in the graph display screen 63, shapes representing maintenance plans such as "MT0211", "MT0213", and "MT0215" are arranged on a coordinate plane represented by two axes.

[0111] The horizontal axis in the graph display screen 63 represents the cost of the maintenance plan. The vertical axis in the graph display screen 63 represents the man-hours obtained by multiplying the number of personnel and the required time for the maintenance plan. The tolerance value is a value specified by, for example, user U1. The display control unit 134 may, for example, use a specified value (not shown) entered in the maintenance plan search results screen 62 as the tolerance value, or it may use a value calculated from the specified value as the tolerance value.

[0112] Furthermore, the density of the patterns in each figure representing the maintenance plan indicates the degree of risk. The display control unit 134 displays a higher density of patterns for maintenance plans with a greater degree of risk, based on the risk information DB 123.

[0113] Returning to Figure 10, the display control unit 134 displays, for example, second defect information (an example of past information) related to the second defect in the defect display area 62d below the search result area 62b. Here, it is assumed that the defect identification unit 133 has identified defects identified as defect IDs "DF0157" and "DF0168" as second defects based on a similar defect identified as defect ID "DF0153".

[0114] In this case, the display control unit 134 displays second defect information relating to the second defect identified by defect IDs "DF0157" and "DF0168" in the defect display area 62d. The display control unit 134 displays, for example, at least one of the following as second defect information: the content of the second defect (e.g., "type of defect" and "cause of occurrence"), the location where the defect occurred (e.g., "location" and "component"), and the action taken for the second defect (e.g., "solution"). Alternatively, the display control unit 134 displays, for example, information relating to the maintenance plan corresponding to the second defect (an example of past maintenance plan information) as second defect information.

[0115] In the example shown in Figure 10, the display control unit 134 displays, for example, "occurrence time," "defect ID," "maintenance plan ID," "defect type," "cause," "solution," "component," "necessary preparations," "safety requirements," "number of personnel," "time required," and "cost" in the search results area 62b.

[0116] "Occurrence time" indicates when the second defect occurred. In the example in Figure 8, it is shown that the second defect, defect ID "DF0157," occurred "13 days" after a similar defect, defect ID "DF0153," occurred.

[0117] The display control unit 134 retrieves, for example, a maintenance plan corresponding to the second defect from the maintenance plans stored in the maintenance plan DB 122. From the retrieved maintenance plan, the display control unit 134 extracts the "maintenance plan ID," "type of defect," "cause," "solution," "component," "required preparations," "safety requirements," "number of personnel," "required time," and "cost" of the second defect information. The display control unit 134 displays the extracted second defect information in the defect display area 62d.

[0118] In this way, the display control unit 134 presents user U1 with at least a portion of the maintenance plan corresponding to the second malfunction, allowing user U1 to confirm whether there are any maintenance tasks that can be performed simultaneously with the maintenance work for the reported malfunction. This enables user U1 to plan maintenance tasks that can address not only the reported malfunction but also any potential second malfunctions that may occur later, thereby improving the efficiency of maintenance work.

[0119] In this example, the display control unit 134 displays the second defect information, including the maintenance plan corresponding to the second defect, on the search results screen 62. However, the information that the display control unit 134 displays on the search results screen 62 is not limited to this.

[0120] For example, the display control unit 134 may display second planning information relating to maintenance plans that address both similar defects and the second defect. This second planning information may be generated, for example, by the defect identification unit 133.

[0121] The defect identification unit 133 generates second plan information by combining, for example, a maintenance plan for a similar defect and a maintenance plan for a second defect. The defect identification unit 133 can estimate the number of personnel, required time, and costs for the second plan information by combining processes common to the maintenance plan for the similar defect and the maintenance plan for the second defect (for example, scaffolding installation) into a single process.

[0122] [3. Examples of Information Processing] Figure 12 is a flowchart showing an example of the information processing flow according to the embodiment. The information processing shown in Figure 12 is performed by the information processing device 10.

[0123] As shown in Figure 12, the information processing device 10 first acquires defect information (step S101). For example, the information processing device 10 acquires defect information from user U1 via terminal device 20.

[0124] Next, the information processing device 10 converts the acquired defect information and past defect information into a rating table (step S102).

[0125] The information processing device 10 extracts similar defects based on the rating table and identifies a maintenance plan (step S103).

[0126] The information processing device 10 identifies a second malfunction based on the time of occurrence of a similar malfunction (step S104). For example, the information processing device 10 identifies a past malfunction that occurred within a predetermined period from the time of occurrence of a similar malfunction as the second malfunction.

[0127] The information processing device 10 presents the user U1 with information regarding the maintenance plan and the second malfunction (step S105).

[0128] [4. Effects] As described above, the information processing method of the embodiment is characterized in that the computer (information processing device 10) acquires defect information related to a defect, identifies maintenance plans corresponding to similar defects similar to the defect, and performs a process to identify past defects based on the time of occurrence of similar defects. Furthermore, the information processing method of the embodiment is characterized in that the computer (information processing device 10) performs a process to display past information related to past defects and maintenance plan information related to maintenance plans corresponding to similar defects.

[0129] In this way, the information processing device 10 can present user U1 with past information regarding past malfunctions in addition to maintenance plan information, depending on the information processing method. As a result, according to this embodiment, the efficiency of user U1's maintenance work is improved.

[0130] Furthermore, past malfunctions are those that occurred within a predetermined period from the time of occurrence of a similar malfunction. This allows the information processing device 10 to present to user U1 malfunctions that occurred within a predetermined period from the time of occurrence of a similar malfunction.

[0131] The past information includes information on the details of past malfunctions, the locations where past malfunctions occurred, and at least one of the actions taken in response to past malfunctions. This allows the information processing device 10 to present to user U1 information on the details of past malfunctions, the locations where past malfunctions occurred, and at least one of the actions taken in response to past malfunctions.

[0132] The historical information includes past maintenance plan information relating to maintenance plans for past malfunctions. This allows the information processing device 10 to present the user U1 with maintenance plans for past malfunctions.

[0133] The process for identifying past defects includes the process for identifying past defects according to at least one of the content of similar defects and the location where similar defects occurred. This allows the information processing device 10 to present user U1 with past information regarding past defects according to at least one of the content of similar defects and the location where similar defects occurred.

[0134] The process for acquiring malfunction information includes the process for acquiring malfunction information related to malfunctions that have occurred at the plant facilities. This allows the information processing device 10 to acquire malfunction information related to malfunctions that have occurred at the plant facilities.

[0135] The information processing program of this embodiment is characterized by causing the computer (information processing device 10) to acquire defect information related to a defect, identify maintenance plans corresponding to similar defects similar to the defect, and execute a process to identify past defects based on the time of occurrence of similar defects. Furthermore, the information processing program of this embodiment is characterized by causing the computer (information processing device 10) to execute a process to display past information related to past defects and maintenance plan information related to maintenance plans corresponding to similar defects.

[0136] In this way, the information processing device 10 can present user U1 with past information regarding past malfunctions, in addition to maintenance plan information, through the information processing program. As a result, according to this embodiment, the efficiency of maintenance work by user U1 is improved.

[0137] The information processing device 10 of this embodiment is characterized by comprising an acquisition unit 131, a plan identification unit 132, a defect identification unit 133, and a display control unit 134. The acquisition unit 131 acquires defect information related to defects. The plan identification unit 132 identifies maintenance plans corresponding to similar defects similar to the current defect. The defect identification unit 133 identifies past defects based on the time of occurrence of similar defects. The display control unit 134 displays past information related to past defects and maintenance plan information related to maintenance plans corresponding to similar defects.

[0138] [5. System] Unless otherwise specified, the processing procedures, control procedures, specific names, and various data and parameters shown in the above documents and drawings may be changed at will.

[0139] 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 unit according to various loads, usage conditions, etc.

[0140] Furthermore, each processing function performed by each device may be implemented, in whole or in part, by a CPU and a program executed for analysis by that CPU, or by wired logic hardware.

[0141] [6. Hardware] Next, an example of the hardware configuration of the information processing device 10 will be described. 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.

[0142] 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 3.

[0143] The processor 10d operates a process that performs the functions described in Figure 1 by reading a program that performs the same processing as each processing unit shown in Figure 3 from the HDD 10b or the like and loading it into memory 10c. For example, this process performs the same functions as each processing unit of the information processing device 10. Specifically, the processor 10d reads a program that has the same functions as the acquisition unit 131, the plan identification unit 132, the defect identification unit 133, and the display control unit 134 from the HDD 10b or the like. Then, the processor 10d executes a process that performs the same processing as the acquisition unit 131, the plan identification unit 132, the defect identification unit 133, and the display control unit 134.

[0144] Thus, the information processing device 10 operates as an information processing device that executes an information processing method by reading and executing an information processing program. Furthermore, the information processing device 10 can also achieve the same functionality as the embodiment described above by reading the information processing program from a recording medium using a media reader and executing the read information processing program. It should be noted that the information processing 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 information processing program, or when they cooperate to execute the information processing program.

[0145] This information processing program can be distributed via networks such as the Internet. Furthermore, this information processing program can be recorded on computer-readable recording media such as hard disks, flexible disks (FDs), CD-ROMs, MOs (Magneto-Optical disks), and DVDs (Digital Versatile Discs), and executed by reading it from the recording media using a computer.

[0146] Some examples of the combinations of technical features that will be disclosed are listed below.

[0147] (1) Computers Obtain information about the malfunction, Identify maintenance plans to address similar defects that are similar to the aforementioned defects, Based on the time of occurrence of the aforementioned similar malfunction, past malfunctions are identified. Display past information regarding the aforementioned past malfunctions, and maintenance plan information regarding the maintenance plan corresponding to the aforementioned similar malfunctions. An information processing method characterized by performing a process. (2) The information processing method according to (1), characterized in that the past malfunction is a malfunction that occurred within a predetermined period from the time of occurrence of the similar malfunction. (3) The information processing method according to (1) or (2), characterized in that the past information includes information relating to the content of the past malfunction, the location where the past malfunction occurred, and at least one of the measures taken in response to the past malfunction. (4) The information processing method according to (3), characterized in that the past information includes past maintenance plan information relating to the maintenance plan corresponding to the past malfunction. (5) The information processing method according to any one of (1) to (4), characterized in that the process for identifying past defects includes a process for identifying past defects according to at least one of the content of similar defects and the location where similar defects occur. (6) The information processing method according to any one of (1) to (5), characterized in that the process for acquiring the aforementioned defect information includes a process for acquiring the aforementioned defect information relating to the defect that occurred at the plant facility. (7) On the computer, Obtain information about the malfunction, Identify maintenance plans to address similar defects that are similar to the aforementioned defects, Based on the time of occurrence of the aforementioned similar malfunction, past malfunctions are identified. Display past information regarding the aforementioned past malfunctions, and maintenance plan information regarding the maintenance plan corresponding to the aforementioned similar malfunctions. An information processing program characterized by executing a process. (8) An acquisition unit that acquires defect information related to defects, A planning identification unit identifies maintenance plans that correspond to similar defects similar to the aforementioned defects, A defect identification unit identifies past defects based on the time of occurrence of the aforementioned similar defects, A display control unit that displays past information regarding the aforementioned past malfunctions and maintenance plan information regarding the maintenance plan corresponding to the aforementioned similar malfunctions, An information processing device characterized by having the following features. [Explanation of Symbols]

[0148] 1. Information Processing System 10 Information Processing Devices 20 Terminal devices 121 Defective Database 122 Conservation Plan Database 123 Hazard Information Database 131 Acquisition Department 132 Planning Department 133 Defect Identification Department 134 Display Control Unit

Claims

1. Computers Obtain information about the malfunction, Based on the aforementioned defect information, the database storing the aforementioned defects is referenced to extract or identify defect information relating to similar defects that are similar to the aforementioned defect. By referring to a database containing maintenance plans, the maintenance plan corresponding to the similar malfunction is identified. From the defect information relating to the aforementioned similar defect, the time of occurrence of the similar defect is obtained. Based on the acquired occurrence time, past malfunctions are identified, and historical information regarding those past malfunctions and maintenance plan information regarding the maintenance plan corresponding to similar malfunctions are acquired. Displaying the aforementioned past information and the aforementioned maintenance plan information, An information processing method characterized by performing a process.

2. The information processing method according to claim 1, characterized in that the aforementioned past malfunction is a malfunction that occurred within a predetermined period from the time of occurrence of the aforementioned similar malfunction.

3. The information processing method according to claim 1, characterized in that the past information includes information relating to the content of the past malfunction, the location where the past malfunction occurred, and at least one of the measures taken in response to the past malfunction.

4. The information processing method according to claim 3, characterized in that the past information includes past maintenance plan information relating to the maintenance plan corresponding to the past malfunction.

5. The information processing method according to claim 1, characterized in that the process for identifying past defects includes a process for identifying past defects according to at least one of the content of similar defects and the location where similar defects occur.

6. The information processing method according to claim 1, characterized in that the process for acquiring the aforementioned defect information includes a process for acquiring the aforementioned defect information relating to the defect that occurred at the plant facility.

7. On the computer, Obtain information about the malfunction, Based on the aforementioned defect information, the database storing the aforementioned defects is referenced to extract or identify defect information relating to similar defects that are similar to the aforementioned defect. By referring to a database containing maintenance plans, the maintenance plan corresponding to the similar malfunction is identified. From the defect information relating to the aforementioned similar defect, the time of occurrence of the similar defect is obtained. Based on the acquired occurrence time, past malfunctions are identified, and historical information regarding those past malfunctions and maintenance plan information regarding the maintenance plan corresponding to similar malfunctions are acquired. Displaying the aforementioned past information and the aforementioned maintenance plan information, An information processing program characterized by executing a process.

8. An acquisition unit that acquires defect information related to defects, Based on the aforementioned defect information, the database storing the aforementioned defects is referenced to extract or identify defect information relating to similar defects that are similar to the aforementioned defect. A plan identification unit identifies the maintenance plan corresponding to the similar malfunction by referring to a database that stores maintenance plans, From the defect information relating to the aforementioned similar defect, the time of occurrence of the similar defect is obtained. A defect identification unit identifies past defects based on the acquired occurrence time, and acquires past information regarding said past defects and maintenance plan information regarding the maintenance plan corresponding to similar defects. A display control unit that displays the aforementioned past information and the aforementioned maintenance plan information, An information processing device characterized by having the following features.

Citation Information

Patent Citations

  • Information processing device, failure prediction method, and failure prediction program

    JP2021125069A

  • Maintenance business support system and maintenance business support method

    JP2022019230A

  • Diagnostic method and device for plant facility

    JP2022034688A

  • Work support device, work support method and work support program

    JP2023006708A

  • Apparatus and method for monitoring and maintaining plant equipment

    US20030004656A1