Inspection Support System

Abstract

To provide an inspection assisting system that is able to improve the reliability of a failure probability.SOLUTION: An inspection assisting system 1 comprises a hydraulic excavator 10, a server 20, and a portable terminal 30. The server 20 includes: a failure probability calculation unit 202 that calculates a failure model and a failure probability for each part of the hydraulic excavator 10, based on operation information of the hydraulic excavator 10; a probability reason calculation unit 203 that calculates a probability reason, based on the failure model; and a reason-explanation generating unit 204 that generates a reason explanation of the failure probability, based on the failure probability and the probability reason. The portable terminal 30 displays the failure probability and the probability explanation.SELECTED DRAWING: Figure 2

Description

[Technical field]

[0001] The present invention relates to an inspection support system that supports the inspection of a work machine such as a hydraulic excavator. [Background technology]

[0002] Conventionally, examples of such technical fields include those described in the following patent documents. Patent document 1 describes an inspection support system that includes a server and a mobile terminal carried by a maintenance worker of a work machine. In this inspection support system, the server calculates the failure probability for each part of the work machine, and in response to a request from the mobile terminal, transmits the calculated failure probability to the mobile terminal and displays it, thereby supporting the maintenance and inspection plan of the work machine. Furthermore, Patent document 2 describes a technology in which explanatory variables are extracted in descending order of contribution to the failure probability. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] JP 2019-121052 A [Patent Document 2] JP 2018-147280 A Summary of the Invention [Problem to be solved by the invention]

[0004] When inspecting a work machine, a maintenance worker may recommend the contents of the inspection while showing the failure probability displayed on a mobile device to the user (e.g., the owner, the user, etc.) of the work machine. In addition, the user of the work machine may consider whether to carry out an inspection by looking at the failure probability displayed on the mobile device. However, even if the failure probability described in Patent Document 1 is shown, it is not clear what cause it is based on. In addition, the failure probability is merely a number, and users differ in their understanding of the urgency of the failure. For this reason, there is a problem that the failure probability is not persuasive or convincing, and the reliability of the failure probability is lacking. Such problems also occur in the technology described in Patent Document 2.

[0005] The present invention has been made to solve such technical problems, and has an object to provide an inspection support system that can improve reliability with respect to failure probability. [Means for solving the problem]

[0006] The inspection support system of the present invention is an inspection support system that supports the inspection of a work machine, and is characterized in that it comprises a failure probability calculation unit that calculates a failure model and failure probability for each part of the work machine based on operation information of the work machine, a probability basis calculation unit that calculates a probability basis based on the failure model calculated by the failure probability calculation unit, and a basis explanation generation unit that generates a basis explanation for the failure probability based on the failure probability calculated by the failure probability calculation unit and the probability basis calculated by the probability basis calculation unit, and displays the basis explanation generated by the basis explanation generation unit on a display device.

[0007] In the inspection support system according to the present invention, since the reason explanation generating unit generates the reason explanation of the failure probability, the reason explanation can be displayed on the display device together with the failure probability. Therefore, it is possible to increase the persuasiveness and acceptability of the user compared to a case where the reason explanation is not shown, and to improve the reliability of the failure probability. Effect of the Invention

[0008] According to the present invention, it is possible to improve reliability against failure probability. [Brief description of the drawings]

[0009] [Figure 1] 1 is a schematic configuration diagram showing an inspection support system according to an embodiment. [Diagram 2] 1 is a block diagram showing an inspection support system according to an embodiment; [Diagram 3] FIG. 13 is a diagram illustrating an example of failure probability data. [Figure 4] FIG. 11 is a diagram showing an example of inspection item data. [Diagram 5] FIG. 11 is a diagram showing an example of main part data. [Figure 6] 13 is a flowchart showing a control process of the server. [Figure 7] 10 is a flowchart showing a control process relating to an inspection item screen of a mobile terminal. [Figure 8] 13 is a flowchart showing a control process relating to a main component screen of the mobile terminal. [Figure 9] 13 is a flowchart showing a control process relating to a failure probability screen of a mobile terminal. [Figure 10] 13 is a flowchart showing a control process relating to a reason explanation screen of a mobile terminal. [Figure 11] FIG. 13 is a diagram showing an example of an inspection item screen of the mobile terminal. [Figure 12] FIG. 13 is a diagram showing an example of a main component screen of the mobile terminal. [Figure 13] FIG. 13 is a diagram showing an example of a failure probability screen of the mobile terminal. [Figure 14] FIG. 13 is a diagram showing an example of a grounds explanation screen of the mobile terminal. [Figure 15] FIG. 13 is a schematic configuration diagram showing a modified example of the inspection support system. [Figure 16] FIG. 13 is a schematic configuration diagram showing a modified example of the inspection support system. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0010] Hereinafter, an embodiment of the inspection support system according to the present invention will be described with reference to the drawings. In the description of the drawings, the same elements are given the same reference numerals, and duplicated description will be omitted. In addition, in the following, a hydraulic excavator will be taken as an example of a work machine to be inspected, but the work machine is not limited to a hydraulic excavator and may be a wheel loader or other work machines.

[0011] Furthermore, in the following explanation, the terms "part" and "component" are used. A "part" generally has a broader scope than a "component". For example, the part "front" is made up of parts such as a boom, arm, and bucket. However, in the case of an "engine", it may be referred to as either a part or a component. Therefore, depending on the content, a part and a component may refer to the same thing.

[0012] Fig. 1 is a schematic configuration diagram showing an inspection support system according to an embodiment, and Fig. 2 is a block diagram showing the inspection support system according to an embodiment. The inspection support system 1 according to this embodiment includes a plurality of hydraulic excavators 10, a server 20 configured to be able to communicate with each of the hydraulic excavators 10 via a network 40, and a mobile terminal 30 capable of communicating with each of the server 20 and the hydraulic excavators 10 via the network 40.

[0013] [About hydraulic excavators] The hydraulic excavator 10 is shipped from the manufacturer's factory and is used by a predetermined user (for example, the owner or user of the hydraulic excavator) at a work site where civil engineering work, construction work, demolition work, dredging work, etc. are performed. The hydraulic excavator 10 is provided with an operation data collection unit 101. The operation data collection unit 101 is composed of, for example, a part of a control unit that controls the entire hydraulic excavator 10, and transmits operation data of the hydraulic excavator 10 together with its own identification number to the server 20 or the mobile terminal 30. Note that transmission to the server 20 or the mobile terminal 30 is performed periodically (for example, once a day).

[0014] [About mobile devices] The mobile terminal 30 is, for example, a smartphone, a tablet terminal, a mobile phone, a PDA (Personal Data Assistant), or the like, and is carried by a maintenance worker or a user of the hydraulic excavator 10. The maintenance worker or user can obtain inspection information and the like of the hydraulic excavator 10 periodically transmitted from the server 20 via the mobile terminal 30. In addition, the maintenance worker can recommend an inspection while showing the inspection information displayed on the mobile terminal 30 to the user of the hydraulic excavator 10.

[0015] Furthermore, a maintenance worker or a user can request inspection information on a specific hydraulic excavator 10, for example, via the mobile terminal 30. Specifically, when a maintenance worker or a user desires inspection information on a specific hydraulic excavator 10, the maintenance worker or the user makes a request to the server 20 via the mobile terminal 30, for example, by inputting the identification number of the specific hydraulic excavator 10 into the mobile terminal 30 or by selecting the identification number of the specific hydraulic excavator 10 displayed on the mobile terminal 30.

[0016] 2, the mobile terminal 30 has an inspection item screen 301, a main component screen 302, a failure probability screen 303, and a reason explanation screen (display device) 304. These screens can be switched by the selection of a maintenance worker or a user. Details of the inspection item screen 301, the main component screen 302, the failure probability screen 303, and the reason explanation screen 304 will be described later.

[0017] [About the server] The server 20 is a main computer constituting the inspection support system 1, and is installed in the head office, branch office, factory, or management center of the manufacturer of the hydraulic excavator 10, periodically collects operation data and the like transmitted from a plurality of hydraulic excavators 10, and centrally manages these hydraulic excavators 10. The server 20 is configured by a microcomputer that combines, for example, a CPU (Central Processing Unit) that executes calculations, a ROM (Read Only Memory) as a secondary storage device that stores programs for the calculations, and a RAM (Random Access Memory) as a temporary storage device that saves the calculation progress and temporary control variables, and performs processes such as calculations and judgments by executing the stored programs.

[0018] In this embodiment, the server 20 calculates the failure probability of each part of the hydraulic excavator 10 based on the operation data of the hydraulic excavator 10 to be managed, and generates a grounds explanation for the failure probability. To achieve this, the server 20 in this embodiment includes an operation data receiving unit 201, a failure probability calculation unit 202, a probability grounds calculation unit 203, a grounds explanation generation unit 204, an inspection item acquisition unit 205, a main part acquisition unit 206, and a data storage unit 210.

[0019] The operation data receiving unit 201 receives operation data transmitted from the hydraulic excavator 10, and stores and accumulates the received operation data in the data storage unit 210 together with the identification number of the hydraulic excavator 10. Operation data history 211 in Fig. 2 is operation data of the hydraulic excavator 10 accumulated over a predetermined period (e.g., the period from shipment from the factory to the present), and is stored in the data storage unit 210. This operation data is data related to operation information, such as the operation start time and operation end time of the hydraulic excavator 10, position information, information detected by each sensor, etc.

[0020] The failure probability calculation unit 202 calculates the failure probability for each part of the hydraulic excavator 10 based on the operation data history of the hydraulic excavator 10, and stores the calculated results as failure probability data 212 in the data storage unit 210 together with the identification number of the hydraulic excavator 10. The failure probability data 212 is classified by model, unit number, main part, and type, for example, as shown in Fig. 3. The calculated failure probability is expressed as a percentage, and the larger the number, the higher the probability of failure.

[0021] In addition, the failure probability calculation unit 202 calculates a failure model for each part of the hydraulic excavator 10 based on the operating data history of the hydraulic excavator 10, and stores the calculated results as failure model data 213 in the data memory unit 210 together with the identification number of the hydraulic excavator 10.

[0022] The probability basis calculation unit 203 calculates the probability basis for each part based on the failure model calculated by the failure probability calculation unit 202 and the operating data history of the hydraulic excavator 10, and stores the calculated result as probability basis data 214 in the data memory unit 210 together with the identification number of the hydraulic excavator 10.

[0023] The basis explanation generating unit 204 generates a basis explanation for the failure probability based on the operation data history of the hydraulic excavator 10, the failure probability calculated by the failure probability calculation unit 202, and the probability basis calculated by the probability basis calculation unit 203. Specifically, the basis explanation generating unit 204 generates a basis explanation for the failure probability based on the operation data history, the failure probability, and the probability basis, using a basis explanation template stored in advance in the data storage unit 210. The basis explanation generating unit 204 stores the generated result in the data storage unit 210 as basis explanation data 215.

[0024] The rationale explanation template is a standard format showing the content of the rationale explanation, and can be changed according to various histories, failure probability, and probability rationale. In addition, this rationale explanation template can be changed according to the person to be explained (maintenance personnel or user). More specifically, when the person to be explained is a maintenance personnel, technical terms, etc. are used in the rationale explanation. On the other hand, when the person to be explained is a user, easy-to-understand sentences are used in the rationale explanation, avoiding technical terms and terms.

[0025] The basis explanation generating unit 204 can generate a basis explanation for a maintenance person and a basis explanation for a user based on such a basis explanation template. That is, different standard phrases of basis explanations are generated for the same failure probability for a maintenance person and a user. In this way, it becomes possible to provide a basis explanation for a maintenance person or a basis explanation for a user depending on the person to be explained, thereby increasing the reliability of the failure probability.

[0026] In response to a request from the mobile terminal 30, the inspection item acquisition unit 205 acquires inspection item data 216 of the hydraulic excavator 10 stored in the data storage unit 210 and transmits it to the mobile terminal 30. Examples of the inspection item data 216 include an exhaust pipe, a turbocharger, a fuel filter, a boom, etc., as shown in Fig. 4, and these inspection items are classified by model.

[0027] In response to a request from the mobile terminal 30, the main parts acquisition unit 206 acquires main parts data 217 of the hydraulic excavator 10 stored in the data storage unit 210 and transmits it to the mobile terminal 30. As an example of the main parts data 217, for example, as shown in Fig. 5, the data is classified by model and inspection item.

[0028] [Server control process] The control process of the server 20 will be described below with reference to Fig. 6. The control process shown in Fig. 6 is executed repeatedly at a predetermined cycle, for example.

[0029] First, in step S101, operation data is collected. Specifically, the operation data receiving unit 201 receives the operation data collected and transmitted by the operation data collecting unit 101 of each hydraulic excavator 10. Since the transmitted operation data also includes the identification number of the hydraulic excavator 10, the operation data receiving unit 201 stores the received operation data in the data storage unit 210 together with the identification number of the hydraulic excavator 10. Then, the data storage unit 210 stores the received operation data in the operation data history 211.

[0030] In step S102 following step S101, a failure model and a failure probability are calculated. At this time, the failure probability calculation unit 202 calculates the failure model and the failure probability based on the operation data history of the hydraulic excavator 10. As a method for calculating the failure model and the failure probability based on the operation data history is an already well-known technique, a detailed description thereof will be omitted. Also, in this step S102, the failure model and the failure probability may be calculated using maintenance data such as parts serial number history and order history instead of the operation data history.

[0031] In step S103 following step S102, the probability basis is calculated. At this time, the probability basis calculation unit 203 calculates the probability basis based on the operation data history of the hydraulic excavator 10 and the failure model calculated in step S102. As a method for calculating the probability basis based on the operation data history and the failure model is an already well-known technique, a detailed description thereof will be omitted.

[0032] In step S104 following step S103, a basis explanation is generated. At this time, the basis explanation generating unit 204 generates a basis explanation of the failure probability based on the operation data history of the hydraulic excavator 10, the failure probability calculated in step S102, and the probability basis calculated in step S103, using a basis explanation template stored in advance in the data storage unit 210. The basis explanation generating unit 204 stores the generated result in the data storage unit 210 together with the identification number of the hydraulic excavator 10.

[0033] When step S104 ends, the series of control processes ends.

[0034] Next, a control process for each screen of the mobile terminal 30 will be described with reference to FIGS.

[0035] [About the inspection item screen] First, the inspection item screen 301 of the mobile terminal 30 will be described with reference to Fig. 7. Fig. 7 is a flowchart showing a control process related to the inspection item screen of the mobile terminal. The control process shown in Fig. 7 is executed by cooperation between the mobile terminal 30 and the server 20, and more specifically, part of step S201 and steps S204 to S209 are processes executed by the server 20, and the other steps are processes executed by the mobile terminal 30.

[0036] 7 is started by, for example, a maintenance worker or a user selecting the inspection item screen 301 displayed on the mobile terminal 30. First, in step S201, an inspection item list is acquired. At this time, for example, the maintenance worker or the user selects (e.g., taps) the inspection item screen 301 to request the inspection item list for the hydraulic excavator 10 from the server 20. In response to the request, the inspection item acquisition unit 205 of the server 20 acquires the inspection item list from the inspection item data 216 and transmits it to the mobile terminal 30.

[0037] Then, the mobile terminal 30 receives the inspection item list transmitted from the server 20, and displays the received contents on the inspection item screen 301. The contents displayed on the inspection item screen 301 include inspection items listed such as "engine," "upper rotating body," and "lower running body," as shown in FIG.

[0038] Next, a loop process for the inspection items shown in steps S202 to S210 is performed. Specifically, for example, when a maintenance worker or a user selects one of the inspection items (for example, "lower carrier" shown in FIG. 11) from the list of multiple inspection items displayed on the inspection item screen 301, the mobile terminal 30 transmits the selected inspection item to the server 20 and requests the server 20 to perform the inspection (see step S203).

[0039] In step S204 following step S203, the main parts acquisition unit 206 of the server 20 acquires a main parts list from the main parts data 217 in response to the request. For example, when the "lower running body" is selected as shown in Fig. 11, the main parts acquisition unit 206 acquires a main parts list such as a sprocket, a center joint, a track frame, a side frame, and a track link related to the "lower running body".

[0040] Next, for these acquired main parts, a loop process of acquiring failure probabilities shown in steps S205 to S207 is performed. That is, the failure probabilities of the main parts acquired in step S205 are acquired sequentially (see step S206). The failure probabilities of the main parts are calculated by the failure probability calculation unit 202 and stored in the data storage unit 210 as failure probability data 212.

[0041] In step S208 following step S207, the failure probability calculation unit 202 calculates the failure probability of the selected inspection item based on the failure probabilities of the main components acquired in steps S205 to S207. In step S209 following step S208, the server 20 returns (in other words, transmits) the failure probabilities of the inspection items calculated in step S208 to the mobile terminal 30.

[0042] The loop process for the inspection items shown in steps S202 to S210 is performed for each selected inspection item. For example, if "upper rotating body" and "engine" are selected after "lower traveling body", steps S203 to S209 are repeated for "upper rotating body" and "engine" in that order.

[0043] In step S211 following step S210, the mobile terminal 30 displays the received inspection item list together with the failure probability of each inspection item on the inspection item screen 301. This ends a series of control processes related to the inspection item screen.

[0044] [About the main parts screen] Next, the main component screen of the mobile terminal will be described with reference to Fig. 8. Fig. 8 is a flowchart showing a control process related to the main component screen of the mobile terminal. The control process shown in Fig. 8 is executed by cooperation between the mobile terminal 30 and the server 20, and more specifically, steps S303 to S307 are processes executed by the server 20, and the other steps are processes executed by the mobile terminal 30.

[0045] The control process shown in Fig. 8 is started, for example, when a maintenance person or a user selects the main parts screen 302 displayed on the mobile terminal 30. First, in step S301, an inspection item is selected. At this time, when the maintenance person or the user selects an inspection item such as "front desk" as shown in Fig. 12, the mobile terminal 30 transmits the selected inspection item to the server 20 and makes a request to the server 20 (see step S302).

[0046] In step S303 following step S302, the main parts acquisition unit 206 of the server 20 responds to the request by acquiring a list of main parts related to the inspection item from the main parts data 217. Here, since "front" has been selected, the main parts acquisition unit 206 acquires a list of main parts such as buckets and links related to "front."

[0047] Next, for these acquired main parts, a loop process of acquiring failure probabilities of the main parts shown in steps S304 to S306 is performed. That is, the failure probabilities of the main parts acquired in step S303 are acquired sequentially (see step S305). The failure probabilities of the main parts are calculated by failure probability calculation unit 202 and stored in data storage unit 210 as failure probability data 212.

[0048] In step S307 following step S306, the server 20 returns (in other words, transmits) to the mobile terminal 30 the main parts list linked with the failure probabilities.

[0049] In step S308 following step S307, the mobile terminal 30 displays the received main parts list together with the failure probability of each part on the main parts screen 302. At this time, the failure probability is displayed for each target link, for example, as shown in Fig. 12. Then, when step S308 ends, the series of control processes related to the main parts screen ends.

[0050] [About the failure probability screen] Next, the failure probability screen of the mobile terminal will be described with reference to Fig. 9. Fig. 9 is a flowchart showing a control process related to the failure probability screen of the mobile terminal. The control process shown in Fig. 9 is executed by cooperation between the mobile terminal 30 and the server 20, and more specifically, steps S402 to S405 and steps S408 to S412 are processes executed by the server 20, and the other steps are processes executed by the mobile terminal 30.

[0051] First, in step S401, information on a target hydraulic excavator is transmitted. At this time, for example, a maintenance worker or a user makes a request to the server 20 by inputting the identification number of the hydraulic excavator 10 for which a failure probability is to be checked into the mobile terminal 30 or by selecting the identification number of the hydraulic excavator 10 displayed on the mobile terminal 30.

[0052] In step S402 following step S401, it is determined whether or not there is a target hydraulic excavator. At this time, the server 20 determines, based on the transmitted hydraulic excavator identification number, whether or not the hydraulic excavator corresponding to the identification number is among the multiple hydraulic excavators it manages. If it is determined that there is no target hydraulic excavator, the control process ends. On the other hand, if it is determined that there is a target hydraulic excavator, the control process proceeds to step S403.

[0053] In step S403, the server 20 judges whether or not there is operation data for the target hydraulic excavator. For example, if the target hydraulic excavator is out of service (i.e., has not been in operation for a while), no operation data is transmitted, and therefore no calculation of failure probability is performed. For this reason, it is judged that there is no operation data, and the control process ends. On the other hand, if it is judged that there is operation data, the control process proceeds to step S404.

[0054] In step S404, the server 20 judges whether or not the target hydraulic excavator has a repair or replacement history. For example, if the target hydraulic excavator has no repair or replacement history, the failure probability is not calculated. For this reason, it is judged that the target hydraulic excavator has no repair or replacement history, and the control process ends. On the other hand, if it is judged that the target hydraulic excavator has a repair or replacement history, the control process proceeds to step S405.

[0055] In step S405, the server 20 judges whether or not there is failure probability data for the target hydraulic excavator. At this time, the server 20 checks whether or not there is failure probability data for the target hydraulic excavator among the failure probability data 212 stored in the data storage unit 210, based on the identification number of the target hydraulic excavator. If it is judged that there is no failure probability data for the target hydraulic excavator, the control process ends. On the other hand, if it is judged that there is failure probability data for the target hydraulic excavator, the control process proceeds to step S406.

[0056] In step S406, a major part is selected. At this time, when the maintenance person or the user selects a major part displayed on the mobile terminal 30, the mobile terminal 30 transmits the selected major part to the server 20 and requests the server 20 (see step S407).

[0057] In step S408 following step S407, the server 20 acquires a failure probability list of major parts from the failure probability data 212 in response to the request. Next, for these acquired major parts, a loop process of checking whether or not there is a basis explanation for the failure probability shown in steps S409 to S411 is performed. At this time, the server 20 checks whether or not there is a basis explanation for the failure probability of the major part in the basis explanation data 215 stored in the data storage unit 210, based on the identification number of the hydraulic excavator 10. Note that the generation of the basis explanation by the basis explanation generating unit 204 may be performed in this step.

[0058] In step S412 following step S411, the server 20 returns (in other words, transmits) to the mobile terminal 30 the failure probability list linked with the presence or absence of a reason explanation.

[0059] In step S413 following step S412, the mobile terminal 30 displays the received failure probability list, together with the presence or absence of an explanation basis, on the failure probability screen 303. This ends a series of control processes related to the failure probability screen.

[0060] [About the explanation screen] Next, the grounds explanation screen of the mobile terminal will be described with reference to Fig. 10. Fig. 10 is a flowchart showing a control process related to the grounds explanation of the mobile terminal. First, in step S501, a part inspection screen is displayed. At this time, for example, a maintenance worker or a user selects the inspection item screen 301 displayed on the mobile terminal 30, and the part inspection screen is displayed.

[0061] In step S502 following step S501, it is determined whether or not there is an indication of the inspection recommendation level for parts. Here, the inspection recommendation level is displayed for parts with a medium to high failure probability. The indication of the inspection recommendation level is visually displayed for each part. For example, if the inspection recommendation level is high, a red icon is displayed (for convenience, it is shown as a bell mark in the figure), and if the inspection recommendation level is medium, a yellow icon is displayed. If it is determined in step S502 that there is an indication of the inspection recommendation level for at least one part, the part for which the failure probability is desired is specified. If it is determined that there is no indication of the inspection recommendation level, the process returns to step 501.

[0062] In step S503 following step S502, it is determined whether or not a part has been specified. The maintenance person or user selects and specifies the part for which they wish to check the failure probability (for example, the part "front"). At that time, the designation is made by tapping the bell icon displayed next to the target part. If it is determined that a part has been specified, a part inspection screen is displayed that displays parts related to that part. If it is determined that no part has been specified, the process returns to step 501.

[0063] In step S504 following step S503, a part inspection screen is displayed. In step S505 following step S504, it is determined whether or not a part inspection recommendation level is displayed. Here, the inspection recommendation level is displayed for parts with a medium to high failure probability. If it is determined in step S505 that an inspection recommendation level is displayed for at least one part, the part whose failure probability the user wishes to know is specified. If it is determined that an inspection recommendation level is not displayed, the process returns to step S501.

[0064] In step S506 following step S505, it is determined whether or not a part has been specified. The maintenance person or user selects and specifies the part for which they wish to check the failure probability. In doing so, they do so by tapping the bell icon displayed next to the target part. If it is determined that a part has been specified, a failure probability screen is displayed. If it is determined that no part has been specified, the process returns to step 501. For example, the maintenance person or user selects and specifies "buckets, links" related to "front" as shown in FIG. 12.

[0065] In step S507 following step S506, the mobile terminal 30 displays on the failure probability screen 303 the failure probability of the specified part.

[0066] The failure probability screen 303 displays the inspection recommendation level for each type (i.e., "overall," "ageing," and "sudden") as shown in FIG. 13. Here, "ageing" indicates the possibility of a time-related failure such as aging deterioration or wear. "Sudden" indicates the possibility that a sign of failure has appeared from the recent operating status. On the other hand, "overall" indicates a failure probability taking into account both "ageing" and "sudden." The display of the types may be arbitrarily set to display only "overall" or only "sudden." In addition, the timing of each display may be arbitrarily set. For example, only "sudden" may be displayed when an investigation is desired, and other types may be displayed after a certain period of time, such as three months after the last investigation.

[0067] In addition, a tab called "Explanation" is displayed next to each inspection recommendation level, as shown in Fig. 13. When a maintenance technician or user wants to know the reason for the inspection recommendation level for each type, the maintenance technician or user can select the "Explanation" tab.

[0068] In step S508 following step S507, the mobile terminal 30 judges whether or not an explanation has been selected. The explanation here is, in other words, an explanation of the basis for the failure probability. If the maintenance person or user desires an explanation, he or she selects the "Explanation" tab shown in FIG. 13. This causes the mobile terminal 30 to judge that an explanation has been selected, and transmits information on the main parts, type, and other party to the server 20 (see step S509).

[0069] The other party here refers to the maintenance staff or the user who is the other party to whom the rationale explanation is to be given. As described above, the rationale explanation generating unit 204 generates a rationale explanation for the maintenance staff and a rationale explanation for the user based on the rationale explanation template, respectively, and therefore, by transmitting the other party information, it is possible to obtain a rationale explanation according to the other party to be explained.

[0070] If it is determined in step S508 that the explanation has not been selected (for example, if the "Close" tab on the screen in FIG. 13 is selected), the control process ends.

[0071] In step S510 following step S509, the server 20 acquires a basis explanation of the failure probability corresponding to the main part, type, and other party information from the basis explanation data 215 stored in the data storage unit 210. In step S511 following step S510, the server 20 replies (in other words, transmits) the acquired basis explanation of the failure probability to the mobile terminal 30.

[0072] In step S512 following step S511, the mobile terminal 30 receives the explanation of the basis for the failure probability transmitted from the server 20, and displays it on the basis explanation screen 304. For example, when "Explanation" regarding the inspection recommendation level for "Aging" is selected in Fig. 13, the explanation content as shown in Fig. 14 is displayed on the basis explanation screen 304. The maintenance worker or the user can understand the reason for the inspection recommendation level by looking at the displayed explanation content.

[0073] When step S512 is completed, a series of control processes relating to the failure probability screen is completed.

[0074] In the inspection support system 1 configured as above, the basis explanation generating unit 204 generates a basis explanation for the failure probability, so that the failure probability and the related basis explanation can be displayed on the basis explanation screen 304. This makes it possible to increase the persuasiveness and acceptability of the user compared to a case where the basis explanation is not displayed, and improve the reliability of the failure probability. This makes it possible to appropriately take measures such as part replacement or repair, and thus realizes stable operation of the hydraulic excavator 10.

[0075] In the present embodiment, the failure probability calculation unit 202, the probability basis calculation unit 203, and the basis explanation generation unit 204 have been described as being provided in the server 20, but they may be provided in the hydraulic excavator 10, as shown in Fig. 15. For example, the failure probability calculation unit 202, the probability basis calculation unit 203, and the basis explanation generation unit 204 may be provided in a control unit of the hydraulic excavator 10 together with a data storage unit 218 that stores failure probability data 212, failure model data 213, probability basis data 214, and basis explanation data 215. In this way, the processing of the server 20 can be reduced, and the variety of the inspection support system 1 can be increased.

[0076] 16, the failure probability calculation unit 202, the probability basis calculation unit 203, and the basis explanation generation unit 204 may be provided in the mobile terminal 30 together with a data storage unit 219 that stores failure probability data 212, failure model data 213, probability basis data 214, and basis explanation data 215. In this case, the mobile terminal 30 directly receives operation data from the hydraulic excavator 10 and performs the above-mentioned calculations and judgments. In this way, the processing of the server 20 can be reduced and the variety of the inspection support system 1 can be increased.

[0077] Although the embodiments of the present invention have been described in detail above, the present invention is not limited to the above-described embodiments, and various design modifications can be made without departing from the spirit of the present invention as described in the claims. [Explanation of symbols]

[0078] 1. Inspection support system 10. Hydraulic Excavator 20 Servers 30 Mobile Devices 40 Network 101 Operational Data Collection Unit 201 Operation data receiver 202 Failure Probability Calculation Unit 203 Probability Basis Calculation Unit 204 Reason Explanation Generation Unit 205 Inspection Item Acquisition Department 206 Main parts acquisition department 210,218,219 Data storage unit 211 Operational Data History 212 Failure Probability Data 213 Failure Model Data 214 Probability-Based Data 215 Data for explanation of reasons 216 Inspection item data 217 Main parts data 301 Inspection item screen 302 Main parts screen 303 Failure Probability Screen 304 Reason explanation screen (display device)

Claims

1. An inspection support system that supports inspection of a work machine, a failure probability calculation unit that calculates a failure model and a failure probability for each part of the work machine based on operation information of the work machine; a probability basis calculation unit that calculates probability basis data for each part based on the failure model calculated by the failure probability calculation unit and operation data of the work machine; a basis explanation generating unit that generates a basis explanation of the failure probability based on the failure probability calculated by the failure probability calculating unit and the probability basis data calculated by the probability basis calculating unit; a display device that displays the reason explanation generated by the reason explanation generating unit, The inspection support system is characterized in that the basis explanation generation unit generates a basis explanation for the failure probability based on a basis explanation template corresponding to the explanation recipient.

2. Further comprising: a server capable of communicating with the work machine; and a mobile terminal capable of communicating with the server, the failure probability calculation unit, the probability basis calculation unit, and the basis explanation generation unit are provided in the server, The inspection support system according to claim 1 , wherein the display device is provided in the mobile terminal.

3. The work machine further includes a portable terminal capable of communicating with the work machine, The inspection support system according to claim 1 , wherein the failure probability calculation unit, the probability basis calculation unit, the basis explanation generation unit and the display device are provided in the mobile terminal.

4. The work machine further includes a portable terminal capable of communicating with the work machine, the failure probability calculation unit, the probability basis calculation unit, and the basis explanation generation unit are provided in the work machine, The inspection support system according to claim 1 , wherein the display device is provided in the mobile terminal.

Images