Maintenance knowledge management method, maintenance knowledge management system, and program
The maintenance knowledge management system classifies and evaluates maintenance information to enhance data accuracy and predict vehicle failures, addressing inefficiencies in existing methods.
Patent Information
- Authority / Receiving Office
- JP · JP
- Patent Type
- Applications
- Current Assignee / Owner
- LOGISTEED LTD
- Filing Date
- 2024-10-25
- Publication Date
- 2026-05-13
AI Technical Summary
Existing methods fail to efficiently accumulate maintenance knowledge data, leading to potential inaccuracies in vehicle maintenance, which can result in either inadequate or excessive maintenance, and lack a systematic approach to enhance the reliability of such data.
A maintenance knowledge management system that classifies maintenance information into three categories: first-class (following manuals), second-class (for abnormalities not in manuals), and third-class (using alternative methods), and evaluates their suitability for updating maintenance knowledge data, enabling accurate accumulation and prediction of vehicle failures.
The system enhances the accuracy of maintenance knowledge data, allowing for efficient accumulation and future prediction of vehicle failures, thereby improving maintenance quality.
Smart Images

Figure 2026077381000001_ABST
Abstract
Description
Technical Field
[0001] The present invention relates to a technique effective for maintenance knowledge management for managing the knowledge of engineers such as maintenance technicians.
Background Art
[0002] Conventionally, while the number of maintenance technicians responsible for maintenance work has been on a decreasing trend, there is concern about a shortage of maintenance technicians who can handle new technologies related to the vehicle itself, such as electric vehicles. To address this, a vehicle management system that can reduce the work performed by maintenance technicians is disclosed in Patent Document 1. According to the technique described in this document, among the work related to vehicle maintenance, by enabling non-maintenance technicians to handle predetermined work that can be performed by non-vehicle maintenance technicians, the work performed by maintenance technicians can be reduced.
Prior Art Documents
Patent Documents
[0003]
Patent Document 1
Summary of the Invention
Problems to be Solved by the Invention
[0004] By the way, actual daily inspections and repairs when maintenance occurs are often carried out based on the knowledge and experience of maintenance technicians, and it is said that the quality of vehicle maintenance may vary depending on the skills of the maintenance technicians. Such knowledge regarding maintenance is expected to be knowledge that can be used for predicting vehicle failures in the future, and the management of knowledge data of engineers such as maintenance technicians is expected. However, if the accuracy of the knowledge data itself is low, maintenance to prevent vehicle failures may not be possible, or even if it is not related to failures, over-maintenance may occur. However, a method for efficiently accumulating knowledge data regarding vehicle maintenance has not yet been fully established.
[0005] Therefore, the present invention aims to provide a maintenance knowledge management method, a maintenance knowledge management system, and a program for accumulating maintenance information knowledge data that can enhance the reliability of knowledge data and efficiently accumulate maintenance-related knowledge data. [Means for solving the problem]
[0006] The present invention relates to a maintenance knowledge management method executed by a computer that acquires maintenance information performed by a mechanic and manages the updating of maintenance knowledge data, A step of obtaining information on the vehicle to be serviced and information on the service performed on the said vehicle, A classification step of classifying and registering the aforementioned maintenance information into: first maintenance information consisting of maintenance performed according to the maintenance manual information or previously registered maintenance knowledge; second maintenance information consisting of maintenance performed for abnormalities not found in the maintenance manual information or previously registered maintenance knowledge data; and third maintenance information consisting of maintenance performed according to standards or methods other than those found in the maintenance manual information or previously registered knowledge data. A receiving step to receive an evaluation of whether the second maintenance information and the third maintenance information are suitable as maintenance knowledge data for the vehicle subject to maintenance, We provide a maintenance knowledge management method that includes the following features.
[0007] According to the present invention, by accepting evaluations of whether the second maintenance information, consisting of information on maintenance performed for abnormalities not found in the maintenance manual information and previously registered maintenance knowledge data, and the third maintenance information, consisting of information on maintenance performed using standards or methods not found in the maintenance manual information and previously registered knowledge data, are suitable as maintenance knowledge data for the vehicle being maintained, it becomes possible to improve the accuracy of the knowledge data and accumulate maintenance knowledge data. Furthermore, the maintenance knowledge data accumulated in this way allows for the quantification and extraction of vehicle type, parts, preconditions, and judgment conditions, making it highly likely to be used for predicting vehicle failures in the future.
[0008] Although this invention falls under the category of methods, systems and programs can also achieve similar actions and effects specific to their respective categories. [Effects of the Invention]
[0009] According to the present invention, it is possible to increase the accuracy of maintenance knowledge data and to accumulate maintenance knowledge data efficiently. [Brief explanation of the drawing]
[0010] [Figure 1] This diagram illustrates the overview of the maintenance knowledge management system 1. 1(a) is an overview diagram of the entire system, and 1(b) is a diagram showing computer 10 separately. [Figure 2] This diagram shows the instruction configuration of the maintenance knowledge management system 1. [Figure 3] This diagram shows a flowchart of the threshold update process performed by computer 10. [Figure 4] This diagram schematically illustrates an example of vehicle maintenance information referenced by administrators. [Figure 5] This diagram schematically illustrates an example of maintenance information that administrators refer to. [Figure 6] This diagram schematically illustrates an example of the content of updates to maintenance knowledge data. [Figure 7] This diagram schematically illustrates an example of maintenance knowledge data. [Figure 8] This diagram schematically shows an example of the updated maintenance knowledge data. [Figure 9] This diagram illustrates another overview of the maintenance knowledge management system 1, where 9(a) is an overview diagram of the entire system, and 9(b) is a diagram showing computer 10 separately. [Figure 10] This diagram shows a flowchart of the threshold update process performed by computer 10. [Modes for carrying out the invention]
[0011] Hereinafter, with reference to the accompanying drawings, embodiments for implementing the present invention (hereinafter referred to as embodiments) will be described in detail. In the following figures, the same elements are denoted by the same numbers or symbols throughout the description of the embodiments.
[0012] [Overview of Maintenance Knowledge Management System 1] FIG. 1(a) is a block diagram for explaining the overview of the maintenance knowledge management system 1, and FIG. 1(b) is a diagram for explaining the computer 10. FIG. 2 is a diagram for explaining the instruction configuration of the maintenance knowledge management system 1. Referring to FIGS. 1 and 2, the components of the maintenance knowledge management system 1 will be described. The maintenance knowledge management system 1 is a system that updates maintenance knowledge data based on maintenance information, and includes at least a computer 10 and a database M. This computer 10 includes, for example, a processor 11, an acquisition unit 12, a reception unit 13, an output unit 14, and an update unit 15. The acquisition unit 12 acquires maintenance information regarding the vehicle to be maintained. The reception unit 13 receives an evaluation as to whether the vehicle information and the maintenance information should be reflected in the update from past maintenance knowledge data. The output unit 14 outputs the maintenance information to be evaluated. The update unit 15 updates the maintenance knowledge data of vehicles of the same type as the maintained vehicle based on the evaluation.
[0013] Also, the maintenance knowledge management system 1 may be implemented by one computer, or may be implemented by a plurality of computers such as a cloud computer. Note that the cloud computer in this specification may be any one that uses any computer in a scalable manner when performing a specific function, or includes a plurality of functional modules to realize a certain system and freely combines and uses its functions.
[0014] Database M is a database that stores vehicle information for registering maintenance knowledge data and the maintenance knowledge data. The maintenance knowledge data includes vehicle information maintained in the past, the abnormal state of the vehicle, the prerequisite conditions when an abnormality is determined, the method of maintenance for the abnormal state, part information for which replacement is recommended, etc. Note that the library of Database M may store maintenance manuals by vehicle manufacturers, replacement part information, abnormal value information, etc.
[0015] This computer 10 executes each process executed by the maintenance knowledge management system 1. As a processor 11, the computer 10 includes various devices for executing various processes. As a recording unit, the computer 10 includes a data storage unit such as a hard disk, a semiconductor memory, a recording medium, a memory card, etc. The computer 10 is connected to the maintenance technician terminal 2 and the administrator terminal 3 via a network such as a public line network or the Internet.
[0016] The maintenance technician terminal 2 is a terminal device managed by a maintenance technician who performs vehicle maintenance. For example, it is a terminal device such as a mobile phone, a smartphone, a tablet terminal, a personal computer, a laptop computer, etc., or a wearable terminal such as an HMD (Head Mounted Display), smart glasses, a smartwatch, etc. Note that the number, type, functions, etc. of the maintenance technician terminal 2 are not particularly limited.
[0017] The administrator terminal 3 is an administrator of the maintenance knowledge management system 1 and is a terminal device of an administrator who manages the maintenance knowledge registered in this system. For example, it is a terminal device such as a mobile phone, a smartphone, a tablet terminal, a personal computer, a laptop computer, etc., or a wearable terminal such as an HMD, smart glasses, a smartwatch, etc. Note that the number, type, functions, etc. of the administrator terminal 3 are not particularly limited.
[0018] [Device Configuration] As shown in Figure 1, the maintenance knowledge management system 1 is a system that updates knowledge data based on maintenance information when a vehicle is newly serviced, and at least the computer 10 is connected to the mechanic terminal 2 and the administrator terminal 3 via a network such as a public telephone network or intranet, enabling data communication. Please note that the components of Maintenance Knowledge Management System 1 are merely an example, and the number, types, and functions of terminals, devices, and other equipment not shown in the diagram can be changed as appropriate.
[0019] Computer 10 includes a processor consisting of a CPU (Central Processing Unit), a GPU (Graphics Processing Unit), RAM (Random Access Memory), ROM (Read Only Memory), etc., and a communication unit consisting of a device for communicating with other terminals and devices, an acquisition unit 12 for acquiring vehicle information related to vehicle maintenance and maintenance information of the vehicle that has been maintained, a reception unit 13 for receiving evaluations of the appropriateness of the maintenance content based on the vehicle information and maintenance information, and an output unit 14 for outputting maintenance information that has not yet been evaluated as to whether or not to be registered as knowledge data. Furthermore, computer 10 includes a processing unit consisting of a device for executing various processes, an update unit 15 for updating maintenance knowledge data of the same type of vehicle as the maintained vehicle based on the evaluation.
[0020] The processing steps involved in the maintenance knowledge management system 1 updating vehicle maintenance prerequisites or maintenance methods based on maintenance information will be explained with reference to Figure 2.
[0021] Computer 10 obtains vehicle information regarding the vehicle's maintenance and maintenance information regarding the vehicle's maintenance (step S1). The mechanic's terminal 2 receives vehicle information and maintenance information from the mechanic. The mechanic's terminal 2 transmits this vehicle information and maintenance information to the computer 10. Computer 10 receives vehicle information and maintenance information from the mechanic's terminal 2 and acquires them.
[0022] Computer 10 accepts an evaluation (step S2) to determine whether the vehicle information and maintenance information should be used to update the maintenance knowledge data for the serviced vehicle. Computer 10 transmits the acquired vehicle information and maintenance information to the administrator terminal 3. Administrator terminal 3 receives this vehicle information and maintenance information and displays it on its own display unit, etc. Administrator terminal 3 receives input from the administrator regarding evaluations of the displayed vehicle information and maintenance information. Administrator terminal 3 transmits the received evaluations to computer 10. Computer 10 receives and accepts this evaluation.
[0023] Based on the evaluation, the computer 10 updates the predetermined conditions of the maintenance knowledge data for vehicles of the same type as the vehicle that has been serviced (step S3). If the received evaluation is positive, computer 10 updates the threshold or item of the prerequisite, or the item or threshold of the maintenance method, in the knowledge data to reflect the content based on the maintenance information for which the evaluation was received.
[0024] The overview of the processing steps in which the maintenance knowledge management system 1 updates vehicle maintenance conditions based on maintenance information in steps S1 to S3 will be explained with reference to Figure 3. Figure 3 is a flowchart of the threshold update process executed by the computer 10.
[0025] Computer 10 acquires information about the vehicle to be serviced and information about the service performed on this vehicle (step S10). The maintenance vehicle information is a record that associates information about the vehicle that was serviced (hereinafter also referred to as the serviced vehicle) with information about the parts that were serviced (hereinafter also referred to as the serviced parts). The serviced vehicle information includes information about the vehicle itself, such as the make (manufacturer, model name, body type, model number, etc.), year of manufacture, and engine type. The serviced parts information includes information about the parts that make up the serviced system (cooling system, electrical system, fuel supply system, exhaust gas recirculation system, DPF (Diesel particulate filter) system, SCR (Selective Catalytic Reduction) system, etc.).
[0026] Maintenance information refers to information about the maintenance performed on a vehicle by a designated mechanic. Information about the maintenance includes, for example, the mechanic's mechanic identifier (ID, management number, name, etc.), the vehicle being serviced (vehicle type, part being serviced, etc.), the reason for the maintenance (abnormal coolant temperature, abnormal battery voltage, abnormal common rail pressure, abnormal EGR opening, abnormal DPF deposit amount, abnormal DPF exhaust temperature (IN), abnormal DPF exhaust temperature (OUT), abnormal DPF differential pressure, abnormal urea water tank level, abnormal urea water quality, etc.), the details of the maintenance, the location of the maintenance (ID, management number, name, etc.), the status of the maintenance, and the codes of the parts that were serviced. Computer 10 obtains this vehicle information and maintenance information from the mechanic's terminal 2. Computer 10 may obtain the vehicle information and maintenance information for any one vehicle being serviced, or it may obtain the vehicle information and maintenance information for multiple vehicles being serviced.
[0027] The mechanic terminal 2 receives predetermined input from the mechanic (such as input via a virtual keyboard) and accepts input of vehicle information and maintenance information for the vehicle that the mechanic has serviced. However, the vehicle information and maintenance information may be pre-configured without the need to receive input from the mechanic. The mechanic's terminal 2 transmits vehicle maintenance information and maintenance information to the computer 10 based on requests from the computer 10, input from the mechanic, etc.
[0028] Computer 10 receives the vehicle information and maintenance information, and obtains the vehicle information and maintenance information related to the vehicle's maintenance. If a mechanic refers to the manual or existing knowledge data registered in the maintenance knowledge management system 1 and performs the maintenance according to the instructions, the manual or existing knowledge data will be retrieved with those details.
[0029] If a mechanic performs maintenance on an anomaly not covered in the maintenance manual information or previously registered maintenance knowledge data, while referring to the manuals and existing knowledge data registered in this maintenance knowledge management system 1, the preconditions under which the anomaly was detected, the vehicle's anomaly value, and the maintenance method performed at that time will be acquired. If a mechanic evaluates or makes a judgment based on criteria different from the judgment criteria (thresholds, conditions) in the maintenance manual information and previously registered knowledge data, or performs maintenance using a method different from the prescribed method, even if the anomaly was previously registered, the details of that maintenance method will be acquired.
[0030] Computer 10 can also be configured to perform data cleansing when acquiring the vehicle information to be serviced and the service information. This data cleansing is performed to ensure consistency between the acquired vehicle information to be serviced and the service information and the data registered in pre-set items. The method by which computer 10 performs data cleansing on the vehicle information to be serviced and the service information may, for example, refer to a database in which the types and contents of pre-registered data are registered, or perform a conversion based on a predetermined conversion method, or perform any other method as appropriate.
[0031] Computer 10 outputs information about the vehicle to be serviced and service information (step S11). Second-class maintenance information refers to maintenance performed for abnormalities not covered in the maintenance manual or previously registered maintenance knowledge data. Third-class maintenance information refers to maintenance performed using standards or methods other than those found in the maintenance manual or previously registered knowledge data. First-class maintenance information refers to maintenance performed according to the maintenance manual or previously registered maintenance knowledge.
[0032] Computer 10 transmits the acquired vehicle maintenance information and maintenance information to the administrator terminal 3. Administrator terminal 3 displays the vehicle information to be serviced and the service information on its own display unit via a predetermined UI (User Interface). The vehicle information to be serviced displayed by administrator terminal 3 includes the vehicle make, model, year, engine type, and serviced parts (see Figure 4). The service information displayed by administrator terminal 3 includes the serviced item, reference item, abnormality details, reason for service, reason for change from reference information, and service location (see Figure 5). Computer 10 outputs the vehicle information to be serviced and the service information by displaying them on the administrator terminal 3.
[0033] Based on Figure 4, the information of vehicles to be serviced will be explained. Figure 4 is a schematic diagram showing an example of information of vehicles to be serviced. In Figure 4, information of vehicles to be serviced 20 is shown. In the maintenance target vehicle information 20, the maintenance ID, the vehicle ID of the vehicle being maintained, the mechanic ID of the mechanic who performed the maintenance, the name of the part that was maintained, the date and time of maintenance, the maintenance manual information, and whether or not a flag was generated when maintenance was performed for an abnormality not found in the previously registered maintenance knowledge data, or when evaluation and judgment were made based on criteria different from the judgment criteria (thresholds, conditions) in the maintenance manual information and previously registered knowledge data, or when maintenance was performed in a way different from the default method.
[0034] The maintenance information will be explained based on Figure 5. Figure 5 is a schematic diagram showing an example of maintenance information. In Figure 5, maintenance information 30 is shown. In maintenance information 30, the maintenance ID, vehicle ID of the vehicle being maintained, vehicle type, vehicle model, engine type, name of the part being maintained, abnormality ID of the abnormality that caused the maintenance, reference, content of the change target flag indicating the update content of the maintenance knowledge data (see Figure 6), and changes when maintenance is performed for an abnormality not found in the maintenance manual information or previously registered maintenance knowledge data, or when evaluation and judgment are performed based on criteria different from the judgment criteria (thresholds, conditions) in the maintenance manual information or previously registered knowledge data, or when maintenance is performed in a way different from the default method.
[0035] Based on Figure 6, the update contents of the maintenance knowledge data will be explained. Figure 6 is a schematic diagram illustrating an example of the update contents of the maintenance knowledge data. In Figure 6, the list of update contents 40 is shown. In the update list 40, a predetermined code is registered for each update. Of these codes, those that correspond to the content of the change target flag in the maintenance information 30 are registered as change target flags.
[0036] Computer 10 accepts an evaluation of whether the vehicle information to be serviced and the service information should be used to update the service conditions for the serviced vehicle (step S12). The evaluation can be simply good (e.g., ○) or bad (e.g., ×), or it can be on a multi-level scale (e.g., 1 to 5 levels). If there are multiple levels, higher numbers may indicate a better evaluation, and conversely, lower numbers may indicate a better evaluation. The evaluation is not limited to the examples above; it may also be represented by symbols (e.g., the number of stars), points, or other methods.
[0037] Here, we will specifically explain the method for evaluating maintenance information. For example, suppose the maintenance knowledge data referenced by computer 10 states that, "As a prerequisite, if the engine speed is 1000 rpm, a coolant temperature of 105°C or lower is considered within the normal range." On the other hand, suppose the abnormality history information of past vehicles reports that in similar vehicles, under the same prerequisites, the temperature reaches 105°C after exceeding 103°C multiple times, and that in other vehicles, under the same conditions, the temperature reaches 105°C after exceeding 103°C multiple times. Here, we will explain below an example where a mechanic in charge of vehicle maintenance looks at the engine speed and coolant temperature data, and based on the fact (frequency) that the coolant temperature has exceeded 103°C multiple times, predicts the possibility of the coolant reaching 105°C and replaces the cooling system.
[0038] The administrator reviews the maintenance information of the vehicle being evaluated and confirms that the vehicle's cooling system has been replaced. Reviewing the vehicle information at the time of the replacement, the administrator confirms that the vehicle's coolant temperature, under specified conditions (engine speed of 1000 rpm), was 103°C, not reaching 105°C, but had reached 103°C multiple times within the specified time. In other words, the administrator confirms that the coolant temperature was below the judgment criterion (threshold) under the specified preconditions in the knowledge data. Normally, this would be judged as excessive and deviating from the regulations, as the cooling system was replaced while the temperature had not reached the specified level. However, if past abnormality history information for similar vehicles shows that the temperature repeatedly exceeded 103°C under the same conditions before reaching 105°C, then this maintenance is considered appropriate, and the mechanic who foresaw this and performed the maintenance is judged to be excellent. The administrator then comprehensively evaluates the acquired vehicle information, abnormality history information, and maintenance information to determine a higher-than-standard evaluation score (good, level 4 or 5 on a 5-point scale, etc.).
[0039] Previously, registered knowledge data had a criterion of 105°C under predetermined conditions (engine speed of 1000 rpm). However, the mechanic's criterion for the maintenance performed was 103°C. In this case, based on the administrator's review or the evaluation or judgment of computer 10, a flag is created indicating that the criterion "reached 103°C a predetermined number of times within one hour" is to be added as new maintenance knowledge data. In this way, maintenance knowledge data with a different criterion is added, and the database for maintenance knowledge data is updated.
[0040] Furthermore, when updating maintenance conditions, the computer 10 accepts new threshold items and corresponding thresholds, not only for evaluation but also for updating maintenance conditions. In other words, it performs a process to add maintenance knowledge data to maintenance information consisting of maintenance information for abnormalities not found in the maintenance manual information or previously registered maintenance knowledge data. Let me explain this case. Administrator terminal 3 accepts input of new threshold items via a predetermined UI. For example, it accepts input of new threshold items when the vehicle being serviced is a new vehicle. Administrator terminal 3 accepts input of the name, variable name, etc. of the threshold item. Administrator terminal 3 accepts input of the threshold corresponding to the accepted new threshold item via a predetermined UI. Administrator terminal 3 accepts input of the threshold condition value, normal value, expressed value, etc.
[0041] Furthermore, administrator terminal 3 accepts input for other information, such as the default description for when an anomaly occurs corresponding to this threshold item, in the same manner as the threshold item and the threshold itself. Alternatively, administrator terminal 3 may input the threshold based on the maintenance target vehicle information and maintenance information output in this instance. Administrator terminal 3 sends the newly received threshold item and the corresponding threshold to computer 10. Computer 10 receives these and accepts a new threshold item and the threshold corresponding to this threshold item.
[0042] Furthermore, the process in step S12 may be performed by the computer 10 itself, or by using a predetermined AI (Artificial Intelligence), rather than accepting input from an administrator. If the computer 10 itself performs the processing, for example, it can evaluate the vehicle information and maintenance information based on the contents of the vehicle information to be serviced, the maintenance details in the mechanic information, and the mechanic who performed the maintenance based on the mechanic identifier.
[0043] Furthermore, if the computer 10 uses a predetermined AI, it can evaluate the acquired vehicle information and maintenance information using a pre-trained model that has learned in advance the contents of the vehicle information to be serviced, the maintenance details in the mechanic information, and the mechanic who performed the maintenance based on the mechanic identifier.
[0044] Computer 10 determines whether the received evaluation is above a predetermined level (step S13). Computer 10 determines whether the received evaluation is above a certain level (good, level 4 or higher on a 5-point scale, etc.). If computer 10 determines that the received evaluation is not above a predetermined level (e.g., poor, level 1-3 on a 5-point scale) (step S13 NO), computer 10 terminates the threshold update process.
[0045] On the other hand, if the computer 10 determines that the received evaluation is above a predetermined level (step S13 YES), the computer 10 updates the maintenance conditions (new threshold items or thresholds) for vehicles of the same type as the vehicle that has been serviced based on the evaluation (step S14). A vehicle of the same type as the serviced vehicle may be a vehicle that is of the same make and model (same manufacturer, same model name, same body type, same model number, etc.), same year of manufacture, same engine type, and has the same type of parts as the serviced vehicle.
[0046] Computer 10 updates the threshold items and thresholds that were originally stored as knowledge data, specifically those corresponding to the vehicle information and maintenance information that received a high evaluation, based on the maintenance parts in the vehicle information and the maintenance targets and reasons in the maintenance information (see Figures 7 and 8). Furthermore, if computer 10 has received a new threshold item and a corresponding threshold, it adds the received threshold item and threshold to the knowledge data. Furthermore, when updating the threshold, the computer 10 may update only the statistically high thresholds among the maintenance vehicle information that received a good evaluation and the maintenance information.
[0047] Knowledge data will be explained based on Figures 7 and 8. Figure 7 is a schematic diagram showing an example of knowledge data. Knowledge data 50 is shown in Figure 7. Figure 8 is a schematic diagram showing a partial example of updated knowledge data. Knowledge data 60 is shown in Figure 8. Knowledge data 60 shows only the threshold item for cooling water temperature from knowledge data 50.
[0048] In Knowledge Data 50, threshold items include the service item name, variable name (bundle number), output value, and default description to be output when an abnormality occurs. For each item, the items and variables used for maintenance are registered. In addition, Knowledge Data 50 also registers condition values (vehicle speed, engine speed, accelerator opening, coolant temperature) and threshold (normal) (the threshold value in the normal case) as thresholds. In this case, as explained in the example above, the mechanic has received high praise for replacing the cooling system because the temperature reached 103°C multiple times. Therefore, the computer 10 updates the knowledge data 50 to include threshold items and thresholds where the coolant temperature threshold (normal) is 105°C or lower. As a result, computer 10 updates the coolant temperature threshold (normal) value to 103°C or less as updated knowledge data 60.
[0049] [Overview of another embodiment of the maintenance knowledge management system 1] Figure 9(a) is a block diagram illustrating an overview of another embodiment of the maintenance knowledge management system 1, and Figure 9(b) is a diagram illustrating the computer 10. The instruction configuration of the maintenance knowledge management system 1 is the same as that shown in Figure 2. The maintenance knowledge management system 1 is substantially the same as the configuration shown in Figure 1 above, but the difference is that the computer 10 further includes a reference unit 16. The reference unit 16 compares new maintenance information with maintenance manual information and previously registered maintenance knowledge data, extracts identical or similar reference information, and generates an update flag.
[0050] The overview of the processing steps in which the maintenance knowledge management system 1 updates vehicle maintenance conditions based on maintenance information in steps S1 to S3 will be explained with reference to Figure 10. Figure 10 is a flowchart of the threshold update process in another embodiment executed by the computer 10. Detailed explanations of processes similar to those described above will be omitted.
[0051] Computer 10 acquires information about the vehicle to be serviced and information about the service performed on that vehicle (step S20). The process in step S20 is the same as the process in step S10 described above.
[0052] Computer 10 outputs the maintenance information to be evaluated (step S21). Computer 10 outputs the maintenance information that has the update target flag turned on from the acquired maintenance information.
[0053] Computer 10 compares new maintenance information with maintenance manual information and previously registered maintenance knowledge data, extracts identical or similar reference information, and generates an update flag (step S22). Computer 10 compares new maintenance information with the update target flag turned on, with maintenance manual information and previously registered maintenance knowledge data. Computer 10 extracts reference information for maintenance manual information and previously registered maintenance knowledge data that is identical or similar to the new maintenance information. Computer 10 generates an update flag for the extracted reference information.
[0054] Computer 10 outputs vehicle maintenance information, second maintenance information, and / or third maintenance information (step S23). Second-class maintenance information refers to maintenance performed for abnormalities not covered in the maintenance manual or previously registered maintenance knowledge data. Third-class maintenance information refers to maintenance performed using standards or methods other than those found in the maintenance manual or previously registered knowledge data. First-class maintenance information refers to maintenance performed according to the maintenance manual or previously registered maintenance knowledge.
[0055] Computer 10 transmits the vehicle information to be serviced, along with the second and / or third service information, to the administrator terminal 3. Administrator terminal 3 displays the vehicle information to be serviced, along with the second and / or third service information, on its display unit via a predetermined UI. Computer 10 outputs the vehicle information to be serviced, the second maintenance information, and / or the third maintenance information by displaying them on the administrator terminal 3.
[0056] Computer 10 receives an evaluation (step S24) on whether the vehicle information to be serviced, the second service information, and / or the third service information should be used to update the service conditions for the serviced vehicle. The content of the evaluation is the same as that of the process in step S12 described above. Similarly, the method for receiving the evaluation is also the same as that of the process in step S12 described above.
[0057] Computer 10 determines whether the received evaluation is above a predetermined level (step S25). The process in step S25 is the same as the process in step S13 described above. If computer 10 determines that the received evaluation is not above a predetermined level (e.g., poor, level 1-3 on a 5-point scale) (step S25 NO), computer 10 terminates the threshold update process.
[0058] On the other hand, if the computer 10 determines that the received evaluation is above a predetermined level (step S25 YES), the computer 10 updates the maintenance conditions (new threshold items or thresholds) for vehicles of the same type as the vehicle that has been serviced based on the evaluation (step S26). The process in step S26 is the same as the process in step S14 described above.
[0059] The above is an overview of the maintenance knowledge management system 1. This maintenance knowledge management system 1 makes it possible to accumulate knowledge data of maintenance information that enables highly accurate maintenance prediction. The maintenance knowledge management system 1 will use the updated knowledge data resulting from the above-described process to predict vehicle maintenance in subsequent maintenance predictions.
[0060] The means and functions described above are realized by a computer (including the CPU, information processing unit, and various terminals) reading and executing a predetermined program. The program may be provided, for example, via a network from the computer (SaaS: Software as a Service) or as a cloud service. Alternatively, the program may be provided in a form recorded on a computer-readable recording medium. In this case, the computer reads the program from the recording medium, transfers it to an internal or external recording device, records it, and executes it. Alternatively, the program may be pre-recorded on a recording device (recording medium) and provided to the computer from that recording device via a communication line.
[0061] Although embodiments of the present invention have been described above, the present invention is not limited to the embodiments described above. Furthermore, the effects described in the embodiments of the present invention are merely a list of the most preferred effects arising from the present invention, and the effects of the present invention are not limited to those described in the embodiments of the present invention.
[0062] According to the present invention, it becomes possible to accumulate knowledge data of maintenance information that enables highly accurate maintenance prediction.
[0063] A first aspect disclosed in this embodiment is a maintenance knowledge management method performed by a computer that acquires maintenance information performed by a mechanic and manages updates to maintenance knowledge data, A step of obtaining information on the vehicle to be serviced and information on the service performed on the said vehicle, A classification step of classifying and registering the aforementioned maintenance information into: first maintenance information consisting of maintenance performed according to the maintenance manual information or previously registered maintenance knowledge; second maintenance information consisting of maintenance performed for abnormalities not found in the maintenance manual information or previously registered maintenance knowledge data; and third maintenance information consisting of maintenance performed according to standards or methods other than those found in the maintenance manual information or previously registered knowledge data. A receiving step to receive an evaluation of whether the second maintenance information and the third maintenance information are suitable as maintenance knowledge data for the vehicle subject to maintenance, We provide a maintenance knowledge management method that includes the following features.
[0064] A second aspect disclosed in this embodiment is an update step in which maintenance knowledge data for vehicles of the same type as the vehicle to be maintained is updated based on the evaluation, The present invention provides a maintenance knowledge management method according to claim 1, further comprising the above.
[0065] A third aspect disclosed in this embodiment is an output step in which, when receiving the evaluation, a mechanic identifier associated with the maintenance information is output, The present invention provides a maintenance knowledge management method according to the first embodiment, further comprising the above.
[0066] A fourth aspect disclosed in this embodiment is that in the reception step, a new threshold item to be added to the maintenance knowledge data and a threshold corresponding to the threshold item are received. The present invention provides a maintenance knowledge management method as described in the first embodiment. [Explanation of Symbols]
[0067] 1. Maintenance Knowledge Management System 2. Technician's Terminal 3. Administrator terminal 10 Computers 11 processors 12 Acquisition Department 13 Reception Department 14 Output section 15 Update section 16 Reference section 20. Information on vehicles subject to maintenance 30 Maintenance Information 40 List of Updates 50 Maintenance Knowledge Data 60 Maintenance Knowledge Data
Claims
1. A maintenance knowledge management method that is performed by a computer that acquires maintenance information from mechanics and manages updates to maintenance knowledge data, A step of obtaining information on the vehicle to be serviced and information on the service performed on the said vehicle, A classification step of classifying and registering the aforementioned maintenance information into: first maintenance information consisting of maintenance information performed according to the maintenance manual information or previously registered maintenance knowledge; second maintenance information consisting of maintenance performed for abnormalities not found in the maintenance manual information or previously registered maintenance knowledge data; and third maintenance information consisting of maintenance performed using standards or methods other than those found in the maintenance manual information or previously registered knowledge data. A receiving step to receive an evaluation of whether the second maintenance information and the third maintenance information are suitable as maintenance knowledge data for the vehicle subject to maintenance, A maintenance knowledge management method that includes the following features.
2. Based on the above evaluation, an update step is performed to update the maintenance knowledge data for vehicles of the same type as the vehicle to be maintained. The maintenance knowledge management method according to claim 1, further comprising:
3. When receiving the aforementioned evaluation, an output step outputs a mechanic identifier associated with the maintenance information. The maintenance knowledge management method according to claim 1, further comprising:
4. In the aforementioned reception step, a new threshold item to be added to the maintenance knowledge data and a threshold corresponding to said threshold item are received. The maintenance knowledge management method according to claim 1.
5. A maintenance knowledge management system that acquires maintenance information performed by mechanics and manages updates to maintenance knowledge data, An acquisition unit that acquires information on the vehicle to be serviced and information on the service performed on the said vehicle, A classification unit that classifies and registers the aforementioned maintenance information into: first maintenance information consisting of maintenance information or information prepared according to previously registered maintenance knowledge; second maintenance information consisting of maintenance information for abnormalities not found in the maintenance manual information or previously registered maintenance knowledge data; and third maintenance information consisting of maintenance information prepared using standards or methods other than those found in the maintenance manual information or previously registered knowledge data. Regarding the second maintenance information and the third maintenance information, there is a reception unit that accepts evaluations on whether they are suitable as maintenance knowledge data for the vehicle subject to maintenance, A maintenance knowledge management system equipped with [features / equipment].
6. The computer that acquires maintenance information from mechanics and manages updates to the maintenance knowledge data, A step of obtaining information on the vehicle to be serviced and information on the service performed on the said vehicle. A classification step that classifies and registers the aforementioned maintenance information into: first maintenance information consisting of maintenance performed according to the maintenance manual information or previously registered maintenance knowledge; second maintenance information consisting of maintenance performed for abnormalities not found in the maintenance manual information or previously registered maintenance knowledge data; and third maintenance information consisting of maintenance performed according to standards or methods other than those found in the maintenance manual information or previously registered knowledge data. A reception step is taken to receive an evaluation of whether the second maintenance information and the third maintenance information are suitable as maintenance knowledge data for the vehicle subject to maintenance. A computer-readable program for executing a command.