Maintenance assistance system and maintenance assistance method

Abstract

This maintenance assistance system comprises: a failure component estimation unit that estimates, on the basis of diagnostic data for diagnosing a device to be diagnosed, a failure component of the device to be diagnosed, the diagnostic data including data of a plurality of data items including a problem symptom; an information provision unit that provides, on the basis of the diagnostic data and the estimation result estimated by the failure component estimation unit, assistance information for maintenance of the device to be diagnosed; and an output information generation unit that generates output information on the basis of the estimation result and the assistance information provided from the information provision unit.

Description

Maintenance support system and maintenance support method

[0001] The present disclosure relates to a maintenance support system and a maintenance support method.

[0002] In recent years, a maintenance support system has become known that uses accumulated data including past malfunctions and parts replaced when responding to malfunctions to present candidate faulty parts (see, for example, Patent Document 1).

[0003] Japanese Patent Application Laid-Open No. 2020-009068

[0004] In the conventional maintenance support system described above, for example, when outputting the faulty parts and maintenance contents, the information on the phenomenon occurring in the equipment to be diagnosed and the model information are used as search keys. However, in the equipment to be diagnosed, such as an air conditioner, a single phenomenon may contain various causes, and it is difficult to obtain appropriate support information for maintenance with the conventional maintenance support system that uses only the information on the phenomenon and the model information.

[0005] The present disclosure has been made to solve the above problem, and its purpose is to provide a maintenance support system and a maintenance support method that can appropriately acquire appropriate support information for maintenance.

[0006] In order to solve the above problems, one aspect of the present disclosure is a maintenance support system including: a faulty part estimation unit that estimates a faulty part of a device to be diagnosed based on diagnostic data for diagnosing the device, the diagnostic data having data of a plurality of data items including malfunction symptoms; an information providing unit that provides support information for maintaining the device to be diagnosed based on the diagnostic data and an estimation result estimated by the faulty part estimation unit; and an output information generating unit that generates output information based on the support information provided by the information providing unit and the estimation result.

[0007] Another aspect of the present disclosure is a maintenance support method in which a faulty part estimation unit estimates a faulty part of a device to be diagnosed based on diagnostic data for diagnosing the device, the diagnostic data having data of a plurality of data items including malfunction symptoms, an information providing unit provides support information for maintaining the device to be diagnosed based on the diagnostic data and an estimation result estimated by the faulty part estimation unit, and an output information generating unit generates output information based on the support information provided by the information providing unit and the estimation result.

[0008] According to the present disclosure, appropriate support information for maintenance can be appropriately acquired.

[0009] 1 is a functional block diagram showing an example of a maintenance support system according to the present embodiment. FIG. 2 is a diagram showing an example of an input screen for diagnostic data of a maintenance terminal according to the present embodiment. FIG. 3 is a diagram showing example data of a maintenance record information storage unit according to the present embodiment. FIG. 4 is a diagram showing example data of an estimation result storage unit according to the present embodiment. FIG. 5 is a diagram showing an example of an output screen for faulty part detection according to the present embodiment. FIG. 6 is a diagram showing an example of an output screen for similar past cases according to the present embodiment. FIG. 7 is a diagram showing an example of tag information for maintenance-related information according to the present embodiment. FIG. 8 is a flowchart showing an example of model learning processing of a model learning device according to the present embodiment. FIG. 9 is a diagram showing an example of diagnostic processing of the maintenance support system according to the present embodiment. FIG. 10 is a flowchart showing an example of part code providing processing of an output information providing device according to the present embodiment. FIG. 11 is a flowchart showing an example of link information providing processing of an output information providing device according to the present embodiment. FIG. 12 is a diagram explaining the hardware configuration of each device of the maintenance support system according to the present embodiment.

[0010] A maintenance support system and a maintenance support method according to an embodiment of the present disclosure will be described below with reference to the drawings.

[0011] 1 is a functional block diagram showing an example of a maintenance support system 1 according to this embodiment. As shown in FIG. 1, the maintenance support system 1 according to this embodiment includes a diagnostic device 10, a plurality of diagnosis target devices 20, a plurality of maintenance terminals 30, a model learning device 40, an output information providing device 50, and an information providing server 60.

[0012] In this embodiment, among the multiple diagnosis target devices 20, devices that have been diagnosed in the past or devices that are currently in normal operation will be described as diagnosis target devices 21, and devices that are currently being diagnosed will be described as diagnosis target devices 22. In addition, in the maintenance support system 1, when referring to any diagnosis target device or when no particular distinction is made, they will be described as diagnosis target devices 20.

[0013] In this embodiment, of the multiple maintenance terminals 30, the terminal that has transmitted maintenance record information, which is a past diagnosis result, will be described as the maintenance terminal 31, and the terminal currently performing the diagnosis will be described as the maintenance terminal 32. In addition, in the maintenance support system 1, when referring to any maintenance terminal or when no particular distinction is made, the terminals will be described as the maintenance terminal 30.

[0014] The diagnostic device 10, the plurality of devices to be diagnosed 21, the plurality of maintenance terminals 30 (31, 32), the model learning device 40, the output information providing device 50, and the information providing server 60 are connectable to a network NW1 and can communicate with each other via the network NW1. The device to be diagnosed 22 and the maintenance terminal 32 are connectable by a network NW2 and can communicate with each other via the network NW2.

[0015] The network NW1 is, for example, a wide area network (WAN), and the network NW2 is, for example, a local area network (LAN) within the building in which the diagnosis target device 22 is installed.

[0016] The diagnosis target devices 20 (21, 22) are, for example, home appliances such as air conditioners. The diagnosis target devices 20 (21, 22) are devices that are the targets of fault diagnosis.

[0017] The maintenance terminals 30 (31, 32) are terminal devices for maintaining the diagnosis target device 20, and are, for example, smartphones, tablet terminals, mobile PCs (mobile personal computers), etc. The maintenance terminals 30 (31, 32) are devices used by a maintenance company to diagnose and maintain the diagnosis target device 20 on-site, or to diagnose the diagnosis target device 20 before heading to the site.

[0018] In addition, the maintenance terminal 32 is a terminal that diagnoses the diagnosis target device 22 that is the target of diagnosis (maintenance), and is equipped with a NW (network) communication unit 321, an input unit 322, a display unit 323, a terminal memory unit 324, and a terminal control unit 325.

[0019] The NW communication unit 321 is a functional unit realized by a communication device such as a network adapter. The NW communication unit 321 is connected to the network NW2 and is capable of communicating with the diagnosis target device 22. The NW communication unit 321 is also connected to the network NW1 and is capable of communicating with, for example, the diagnosis device 10.

[0020] The input unit 322 is an input device such as a keyboard, a touch screen, or buttons. The input unit 322 accepts various input information in response to operations by a user (maintenance contractor). The input unit 322 is used, for example, for the maintenance contractor to input diagnostic data. The diagnostic data includes, for example, the model name, installation year, installation area, and malfunction symptoms of the diagnostic target device 22.

[0021] The display unit 323 is a display device such as a liquid crystal display. The display unit 323 displays, for example, an input screen for inputting diagnostic data and output information received from the diagnostic device 10 described below. Here, the output information is, for example, a diagnosis result for the diagnostic data, such as a candidate for a faulty part. Details of the output information will be described later.

[0022] The terminal storage unit 324 stores various types of information used by the maintenance terminal 32. For example, the terminal storage unit 324 stores input information from the input unit 322, display information on the display unit 323, information transmitted to and received from the diagnostic device 10, etc.

[0023] The terminal control unit 325 is a functional unit realized by, for example, causing a processor including a CPU (Central Processing Unit) to execute a program. The terminal control unit 325, for example, transmits diagnostic data received via the input unit 322 to the diagnostic device 10 via the network NW1. The terminal control unit 325 also transmits operating data acquired from the diagnostic target device 22 via the network NW2 to the diagnostic device 10 via the network NW1. The terminal control unit 325 also displays output information received from the diagnostic device 10 via the network NW1 on the display unit 323. When receiving diagnostic data from the maintenance company, the terminal control unit 325 displays, for example, an input screen such as that shown in FIG. 2 on the display unit 323.

[0024] 2 is a diagram showing an example of a diagnostic data input screen of the maintenance terminal 32 in this embodiment. Screen G1 shown in Fig. 2 shows the diagnostic data input screen displayed on the display unit 323 of the maintenance terminal 32. Screen G1 is configured so that the region, model name (product name), installation year, slip number, and symptoms can be input via the input unit 322.

[0025] Furthermore, as shown in screen G1, the terminal control unit 325 displays an "Execute" button BT1 on the display unit 323. The terminal control unit 325 accepts the region, model name (product name), installation year, invoice number, and symptoms as diagnostic data via the input unit 322. Furthermore, when the "Execute" button BT1 is clicked (pressed) via the input unit 322, the terminal control unit 325 transmits the accepted diagnostic data and the operating data acquired from the diagnosis target device 22 to the diagnostic device 10 via the NW communication unit 321.

[0026] The above-mentioned operating data includes detection data from various sensors (not shown) provided in the diagnosis target device 22, error code information, and the like.

[0027] 1 , the model learning device 40 is, for example, a server device connectable to the network NW1. The model learning device 40 executes a learning process for the faulty component detection model. The model learning device 40 also includes a network communication unit 41, a learning storage unit 42, and a learning processing unit 43.

[0028] The NW communication unit 41 is a functional unit realized by a communication device such as a network adapter. The NW communication unit 41 is connected to the network NW1 and is capable of communicating with the diagnosis target device 21, the maintenance terminal 31, and the diagnosis device 10.

[0029] The learning storage unit 42 is a storage device such as a RAM, a flash memory, or a hard disk drive (HDD), and stores various information used by the model learning device 40. The learning storage unit 42 includes a maintenance record information storage unit 421, an operating data storage unit 422, and a model storage unit 423.

[0030] The maintenance record information storage unit 421 stores maintenance record information collected from multiple maintenance terminals 31. The maintenance record information is, for example, a maintenance work report created by a maintenance company. The maintenance record information storage unit 421 stores, for example, maintenance record information of past diagnoses of the diagnosis target device 21, including data on multiple data items and faulty part information. Here, an example of data stored in the maintenance record information storage unit 421 will be described with reference to FIG. 3.

[0031] 3 is a diagram showing an example of data stored in the maintenance record information storage unit 421 according to this embodiment. As shown in FIG. 3, the maintenance record information storage unit 421 stores maintenance record information that associates a NO (number), a date, a model name, years since installation, a region, symptoms, a replacement part P1, and a replacement part P2.

[0032] In FIG. 3 , NO is an example of individual identification information of the diagnosis target device 21 (20). The date indicates the date on which the maintenance work was performed by the maintenance company, and the model name indicates the model name of the diagnosis target device 21 (20). The model name is an example of model identification information that identifies the model of the diagnosis target device 21 (20). The installation years and region indicate the years (period) and region in which the diagnosis target device 21 (20) has been installed. The symptoms indicate symptoms of a malfunction or failure that occurred when the diagnosis target device 21 (20) was diagnosed in the past. Replacement parts P1 and P2 indicate parts that were replaced during past maintenance work. The model name, installation years, region, and symptoms correspond to data items.

[0033] For example, in the example shown in FIG. 3, the maintenance record information with a NO of "1" indicates that the maintenance work date is "2023 / 1 / 20" (January 20, 2023), the model name is "MSZXXX01S," and the installation year is "5" (five years). It also indicates that the region is "Tokyo" and the symptom is "not cooling." It also indicates that replacement parts P1 and P2 are a "compressor" and an "expansion valve."

[0034] Returning to the explanation of FIG. 1 , the operating data storage unit 422 stores operating data collected from each diagnosis target device 21 (20). Here, the operating data includes detection data from various sensors (not shown) provided in each diagnosis target device 21 (20), error code information, etc. The operating data includes, for example, a history of errors that have occurred in the past, such as error codes, or time-series data such as compressor frequency. The operating data storage unit 422 stores, for example, the above-mentioned number and model name, the detection date and time, and the operating data in association with each other.

[0035] The model storage unit 423 stores a faulty part detection model, which is a learning result obtained by learning the maintenance record information and the operating data as learning data. The faulty part detection model is, for example, an estimation model that estimates a faulty part from the diagnostic data and the operating data of the diagnosis target device 22 (20).

[0036] The model storage unit 423 may generate a faulty part detection model that estimates faulty parts from diagnostic data using maintenance record information as learning data, without using operational data.

[0037] The learning processing unit 43 is a functional unit realized by, for example, causing a processor including a CPU to execute a program. The learning processing unit 43 executes a learning process to learn a faulty part detection model. The learning processing unit 43 includes a maintenance record information collection unit 431, an operation data collection unit 432, and a model learning unit 433.

[0038] The maintenance record information collection unit 431 collects maintenance record information from the maintenance terminal 31 (30) and stores the collected maintenance record information in the maintenance record information storage unit 421. The maintenance record information collected by the maintenance record information collection unit 431 is used as learning data for learning a faulty part detection model.

[0039] The operating data collection unit 432 collects operating data from the diagnosis target device 21 (20) and stores the collected operating data in the operating data storage unit 422. The operating data collected by the operating data collection unit 432 may be used as part of learning data for learning a faulty part detection model.

[0040] The model learning unit 433 learns the maintenance record information as learning data and generates a faulty part detection model that estimates faulty parts from the diagnostic data. The model learning unit 433 generates the faulty part detection model using a machine learning method such as LightGBM or SVM (Support Vector Machine) using, for example, past maintenance record information stored in the maintenance record information storage unit 421 and driving data stored in the driving data storage unit 422 as learning data. Note that the model learning unit 433 may also generate the faulty part detection model using the maintenance record information as learning data without using the driving data.

[0041] The model learning unit 433 stores the generated faulty part detection model in the model storage unit 423. Furthermore, the model learning unit 433 transmits, for example, the faulty part detection model stored in the model storage unit 423 to the diagnostic device 10 via the NW communication unit 41.

[0042] The diagnostic device 10 is, for example, a server device connectable to the network NW1. The diagnostic device 10 estimates a faulty part by utilizing a faulty part detection model generated by the model learning device 40. The diagnostic device 10 estimates a faulty part of the diagnosis target device 22 using diagnostic data and operating data acquired from the maintenance terminal 32 via the network NW1 as input data.

[0043] The diagnostic device 10 also transmits diagnostic data and estimation results to the output information providing device 50 via the network NW1, and acquires support information for maintenance of the diagnosis target device 22 from the output information providing device 50. The diagnostic device 10 also generates a display screen as output information based on the estimation results of the faulty part and the support information, and transmits it to the maintenance terminal 32 via the network NW1. The diagnostic device 10 also includes a NW communication unit 11, a device storage unit 12, and a diagnostic processing unit 13.

[0044] The NW communication unit 11 is a functional unit realized by a communication device such as a network adapter. The NW communication unit 11 is connected to the network NW1 and is capable of communicating with the maintenance terminal 32, the model learning device 40, and the output information providing device 50.

[0045] The device storage unit 12 is a storage device such as a RAM, a flash memory, or an HDD, and stores various information used by the diagnostic device 10. The device storage unit 12 includes a diagnostic data storage unit 121, an operating data storage unit 122, a model storage unit 123, an estimation result storage unit 124, and an output information storage unit 125.

[0046] The diagnostic data storage unit 121 stores diagnostic data acquired from the maintenance terminal 32. The diagnostic data has data items similar to the input data, excluding the item of replacement parts in the maintenance record information used in the learning process by the model learning device 40. The diagnostic data storage unit 121 stores diagnostic data for data items such as model, region, capacity range, and age.

[0047] The operating data storage unit 122 stores operating data of the diagnosis target device 22 acquired from the maintenance terminal 32. The operating data has the same data items as the operating data used in the learning process by the above-described model learning device 40. The operating data has data items such as detection data from various sensors (e.g., indoor temperature, indoor humidity, outdoor temperature, outdoor humidity, compressor frequency) and error codes.

[0048] The model storage unit 123 stores the faulty component detection model acquired from the model learning device 40. The model storage unit 123 stores the same information as that stored in the model storage unit 423 of the model learning device 40.

[0049] The estimation result storage unit 124 stores the estimation results estimated by the faulty part estimation unit 133 (described later) as candidates for faulty parts of the diagnosis target device 22. The estimation result storage unit 124 stores, as estimation results, candidates for faulty parts of the diagnosis target device 22 in association with failure probabilities (likelihoods). Here, an example of data stored in the estimation result storage unit 124 will be described with reference to FIG. 4 .

[0050] 4 is a diagram showing an example of data stored in the estimation result storage unit 124 in this embodiment. As shown in FIG. 4, the estimation result storage unit 124 stores estimation results in association with failure probabilities (likelihoods). The estimation results here are candidates for faulty parts. The estimation result storage unit 124 stores multiple candidates for faulty parts in descending order of failure probability.

[0051] 4, the candidate for the faulty part with the highest failure probability is the "compressor," with a failure probability of "51.2%." The candidate for the faulty part with the next highest failure probability is the "four-way valve," with a failure probability of "27.8%."

[0052] 1, the output information storage unit 125 stores output information from an output information generation unit 134, which will be described later. The output information generated by the output information generation unit 134 will be described later with reference to FIGS. 5 and 6.

[0053] The diagnostic processing unit 13 is a functional unit realized by causing a processor including a CPU to execute a program, and includes a diagnostic data acquisition unit 131, an operating data acquisition unit 132, a faulty part estimation unit 133, and an output information generation unit 134.

[0054] The diagnostic data acquisition unit 131 acquires diagnostic data from the maintenance terminal 32 via the NW communication unit 11. The diagnostic data acquisition unit 131 stores the acquired diagnostic data in the diagnostic data storage unit 121.

[0055] The operating data acquisition unit 132 acquires operating data of the diagnosis target device 22 from the maintenance terminal 32 via the NW communication unit 11. The operating data acquisition unit 132 stores the acquired operating data of the diagnosis target device 22 in the operating data storage unit 122.

[0056] The faulty part estimation unit 133 estimates a faulty part of the diagnosis target device 22 based on diagnostic data for diagnosing the diagnosis target device 22, the diagnostic data having data of a plurality of data items including malfunction symptoms. The faulty part estimation unit 133 estimates a faulty part of the diagnosis target device 22 from the diagnostic data stored in the diagnostic data storage unit 121 and the operating data stored in the operating data storage unit 122, using a faulty part detection model stored in the model storage unit 123.

[0057] The failed part estimation unit 133 uses the failed part detection model to estimate, for example, a plurality of failed part candidates and generate a failure probability (likelihood) for each failed part candidate. The failed part estimation unit 133 sorts the failed part candidates in descending order by failure probability (likelihood), and stores the failed part candidates (estimation results) in association with the failure probabilities (likelihoods) in the estimation result storage unit 124, as shown in FIG.

[0058] The faulty part estimation unit 133 may extract similar cases that are similar to the diagnostic data from the maintenance record information storage unit 421 that stores maintenance record information, and estimate the faulty part from the extracted similar cases using a faulty part detection model.

[0059] In this case, the failed part estimation unit 133 calculates the similarity between the past cases stored in the maintenance record information storage unit 421 and the diagnostic data, and extracts multiple past cases (e.g., 100 cases) with high similarity as similar cases. The failed part estimation unit 133 estimates failed part candidates and failure probabilities for each of the multiple similar cases using a failed part detection model. The failed part estimation unit 133 may calculate the average failure probability for the failed parts in the multiple similar cases, sort the similar cases in descending order of average failure probability, and output a specific number of the top failed part candidates as estimation results.

[0060] The faulty part estimation unit 133 also transmits the estimation result (faulty part name) and diagnostic data to the output information providing device 50 via the NW communication unit 11, and receives support information for maintenance of the diagnosis target device 22 from the output information providing device 50. The support information includes, for example, the part code of the faulty part, various link information, etc.

[0061] The output information generation unit 134 generates output information based on the support information provided by the output information providing device 50 and the estimation result of the failed part estimation unit 133. The output information generation unit 134 generates display information (output screen) including the estimation result and link information LN1 as shown in Fig. 5, for example.

[0062] 5 is a diagram showing an example of an output screen for faulty part detection in this embodiment. Screen G2 shown in Fig. 5 is an output screen for faulty part detection output generated by the output information generation unit 134, and is a screen to be displayed on the display unit 323 of the maintenance terminal 32. As shown in screen G2, the output information generation unit 134 generates an output screen that displays faulty part candidates, probabilities (failure probabilities), model names, and link information LN1 in association with each other.

[0063] Here, the link information LN1 can be connected to a link destination (e.g., URL: Uniform Resource Locator) via the network NW1 by clicking on the display using the input unit 322 of the maintenance terminal 32. The link information LN1 includes, for example, specifications, determination, maintenance procedures, and ordering. Here, the specifications are link information displaying the specifications of the faulty part, and the determination is link information such as an abnormality determination flow for the diagnosis target device 22. The maintenance procedures are link information such as maintenance manuals for the diagnosis target device 22 and the faulty part, and the ordering is link information such as a website for ordering the faulty part.

[0064] In addition to the above-mentioned link information, the output information generation unit 134 may include, on the output screen, link information of maintenance-related information, such as information on the region, model, know-how information, part-specific failure information, and its maintenance (repair) method.

[0065] In addition, the screen G2 shown in Figure 5 includes a "Check similar past cases" button BT2, and when the "Check similar past cases" button BT2 is clicked (pressed) via the input unit 322, the output information generation unit 134 generates an output screen such as the screen G3 shown in Figure 6.

[0066] Fig. 6 is a diagram showing an example of an output screen of similar past cases in this embodiment. Screen G3 shown in Fig. 6 is an output screen of similar past cases generated by the output information generation unit 134. As shown in screen G3, the output information generation unit 134 generates, as output information, an output screen (display information) including similar cases that are similar to the diagnostic data and graphs (e.g., pie charts) that represent trends for each data item of the similar cases.

[0067] In addition, on screen G3, data items and graphs of similar cases can be added or deleted from the list of "Other items" on the right side. In addition, in the example shown on screen G3, an indication of the degree of similarity is added to each similar case.

[0068] 5 and 6 , and stores the generated output information in the output information storage unit 125. In addition, the output information generation unit 134 transmits the output information stored in the output information storage unit 125 to the maintenance terminal 32 via the NW communication unit 11, and displays it on the display unit 323 of the maintenance terminal 32.

[0069] 1 , the output information providing device 50 is, for example, a server device connectable to the network NW1. The output information providing device 50 provides support information to the diagnostic device 10 in accordance with the estimation result (the name of the faulty part) and diagnostic data received from the diagnostic device 10 via the network NW1.

[0070] The output information providing device 50 includes a network communication unit 51 , a model / part specification information storage unit 52 , a maintenance-related information storage unit 53 , a link information storage unit 54 , and an information providing unit 55 .

[0071] NW communication unit 51 is a functional unit realized by a communication device such as a network adapter, etc. NW communication unit 51 is connected to network NW1 and is capable of communicating with diagnostic device 10.

[0072] The model / component specification information storage unit 52 (an example of a model / component information storage unit) is, for example, a storage device such as a flash memory or an HDD. The model / component specification information storage unit 52 stores a model / component correspondence table that associates the model name of the diagnosis target device 21 with the names and component codes of components mounted on the diagnosis target device 21. Here, the model name is an example of model identification information that identifies the model of the diagnosis target device 21. Furthermore, the component code is an example of component identification information that identifies a faulty component.

[0073] The maintenance-related information storage unit 53 is a storage device such as a flash memory or a HDD. The maintenance-related information storage unit 53 stores the maintenance-related information in association with tag information for searching the maintenance-related information. Here, the tag information of the maintenance-related information will be described with reference to FIG. 7 .

[0074] 7 is a diagram showing an example of tag information for maintenance-related information in this embodiment. As shown in Fig. 7, the tag information includes, as data items, a maintenance-related information number, a model name, a part surface, a part code, an area, a coastal or inland area, an age, an age (divided into three), a capacity range, symptoms, an error code, and the like.

[0075] Returning to the explanation of FIG. 1 , the link information storage unit 54 is, for example, a storage device such as a flash memory or HDD. The link information storage unit 54 stores, in association with the model name and part code, link information indicating links to information related to the model and faulty part of the diagnostic target device 22. The link information includes, for example, links to the above-mentioned region, model, know-how information, part-specific fault information, and its maintenance (repair) method. The link information may also include link information that allows direct access to maintenance-related information.

[0076] The information providing unit 55 is a functional unit realized by, for example, causing a processor including a CPU to execute a program. The information providing unit 55 provides the diagnostic device 10 with support information for maintaining the diagnosis target device 22 based on the diagnostic data and the estimation result estimated by the faulty part estimation unit 133. The information providing unit 55 receives, for example, the diagnostic data and the estimation result (faulty part name) from the diagnostic device 10 via the NW communication unit 51, and transmits (outputs) the support information to the diagnostic device 10.

[0077] The information providing unit 55 extracts a part code from the model / part specification information storage unit 52 based on, for example, the model identification information and the part name of the faulty part included in the diagnostic data, and outputs the extracted part code as support information to the diagnostic device 10. The information providing unit 55 also acquires link information from the link information storage unit 54 based on the model name and the part code, and outputs the acquired link information to the diagnostic device 10 as support information.

[0078] The information providing unit 55 also outputs to the diagnostic device 10, for example, specification information of the faulty part, maintenance-related information of the diagnosis target device 22, and link information including a link destination of at least one of the ordering sites for the faulty part.

[0079] In addition, the information providing unit 55 calculates the similarity between the diagnostic data and part code and the tag information assigned to the maintenance-related information, selects the maintenance-related information based on the similarity, and outputs link information that allows access to the selected maintenance-related information.

[0080] Specifically, the information providing unit 55 calculates the similarity (Sim ｎ ) is calculated.

[0081]

[0082] Here, Sim ｎ indicates the similarity of the nth maintenance-related information, and α, β, ... indicate the weight of each data item. Also, x~, y~, ... indicate the value of each data item of the diagnostic data and part code, and x, y, ... indicate the value of each data item of the tag information. Also, function f is a function that outputs "1" when the data items of the diagnostic data and part code match the data items of the tag information, and outputs "0" when they do not match.

[0083] In this embodiment, a variable with a line through the letter x is represented as x~, and a variable with a line through the letter y is represented as y~. The weight of each data item is arbitrary, and they may all be the same weight, or the weights of some data items may be adjusted based on past trends.

[0084] The information providing unit 55 calculates the similarity (Sim ｎ ) in descending order to select the maintenance-related information with the highest similarity. Here, the number of selections is arbitrary, and may be one, or a numerical value such as the top 10 pieces of information may be specified.

[0085] The information providing unit 55 creates link information for the selected maintenance-related information and outputs it as support information to the diagnostic device 10. The information providing unit 55 may obtain the link information for the selected maintenance-related information, for example, by using the link information storage unit 54 described above.

[0086] The information providing server 60 is, for example, a server device connectable to the network NW1. The information providing server 60 provides various information or services in response to a connection request (access request) from the maintenance terminal 32 to a link destination of the link information.

[0087] The information providing server 60 includes a network communication unit 61 , a parts ordering processing unit 62 , a failure determination information providing unit 63 , a service information providing unit 64 , and a maintenance manual providing unit 65 .

[0088] The NW communication unit 61 is a functional unit realized by a communication device such as a network adapter, etc. The NW communication unit 61 is connected to the network NW1 and is capable of communicating with the maintenance terminal 32 (30).

[0089] The parts ordering processing unit 62 is a functional unit realized by, for example, causing a processor including a CPU to execute a program. The parts ordering processing unit 62 provides an ordering service for faulty parts. For example, the parts ordering processing unit 62 provides the ordering service for faulty parts in response to an access request based on the link information for "order" on the screen G2 shown in FIG. 5.

[0090] The fault determination information providing unit 63 is a functional unit realized by, for example, causing a processor including a CPU to execute a program. The fault determination information providing unit 63 provides fault determination flow information for the diagnosis target device 22 in response to an access request based on the link information for “Determination” on the screen G2 shown in FIG.

[0091] The service information providing unit 64 is a functional unit realized by, for example, causing a processor including a CPU to execute a program. The service information providing unit 64 provides the maintenance-related information as service information in response to an access request based on link information of the maintenance-related information, for example.

[0092] The maintenance manual providing unit 65 is a functional unit that is realized by, for example, causing a processor including a CPU to execute a program. The maintenance manual providing unit 65 provides maintenance manual information for the diagnosis target device 22 in response to an access request based on link information for "Maintenance Procedure" on the screen G2 shown in FIG. 5, for example.

[0093] Next, the operation of the maintenance support system 1 according to this embodiment will be described with reference to the drawings.

[0094] First, the model learning process of the model learning device 40 will be described with reference to Fig. 8. Fig. 8 is a flowchart showing an example of the model learning process of the model learning device 40 in this embodiment.

[0095] 8 , the model learning device 40 collects maintenance work reports and operating data via the network NW1 (step S101). The maintenance record information collection unit 431 of the model learning device 40 collects maintenance work reports as maintenance record information from the maintenance terminal 31 via the NW communication unit 41, and stores the collected maintenance record information (maintenance work reports) in the maintenance record information storage unit 421. In addition, the operating data collection unit 432 of the model learning device 40 collects operating data from the diagnosis target device 21 via the NW communication unit 41, and stores the collected operating data in the operating data storage unit 422.

[0096] Next, the model learning unit 433 of the model learning device 40 classifies input data and output data from the maintenance work report and the operation data (step S102). The model learning unit 433 classifies the maintenance record information (maintenance work report) stored in the maintenance record information storage unit 421 and the operation data stored in the operation data storage unit 422 as learning data into input data and output data. For example, in the case shown in FIG. 3, "model name," "years of installation," "area," and "symptoms" are classified as input data, and "replacement part P1" and "replacement part P2" are classified as output data.

[0097] Next, the model learning unit 433 learns the relationship between the input data and the output data and generates a faulty component detection model (step S103). The model learning unit 433 generates the faulty component detection model from the above-mentioned learning data using a machine learning method such as LightGBM or SVM. The model learning unit 433 stores the generated faulty component detection model in the model storage unit 423.

[0098] Next, the model learning unit 433 transmits the failed part detection model to the diagnostic device 10 (step S104). The model learning unit 433 transmits the failed part detection model stored in the model storage unit 423 to the diagnostic device 10 via the NW communication unit 41. The transmitted failed part detection model is stored in the model storage unit 123 of the diagnostic device 10. After the processing of step S104, the model learning unit 433 ends the model learning process.

[0099] Next, the diagnostic processing of the maintenance support system 1 according to this embodiment will be described with reference to Fig. 9. Fig. 9 is a diagram showing an example of the diagnostic processing of the maintenance support system 1 according to this embodiment.

[0100] 9, in the diagnostic process of the maintenance support system 1, first, the maintenance terminal 32 acquires diagnostic data from the maintenance company (step S201). The terminal control unit 325 of the maintenance terminal 32 displays, for example, screen G1 shown in FIG. 2 and acquires the diagnostic data via the input unit 322.

[0101] Next, the maintenance terminal 32 transmits the diagnostic data to the diagnostic device 10 (step S202). The terminal control unit 325 transmits the diagnostic data to the diagnostic device 10 via the NW communication unit 321. The terminal control unit 325 may transmit the operating data acquired from the diagnosis target device 22 to the diagnostic device 10 together with the diagnostic data.

[0102] Next, the diagnostic device 10 uses the faulty part detection model to estimate the faulty part from the diagnostic data (step S203). The faulty part estimation unit 133 of the diagnostic device 10 uses the faulty part detection model stored in the model storage unit 123 to estimate candidates for the faulty part and the failure probability from the diagnostic data (and the operating data) received from the maintenance terminal 32.

[0103] Next, the diagnostic device 10 transmits the diagnostic data and the estimation result to the output information providing device 50 (step S204). The output information generating unit 134 of the diagnostic device 10 transmits the diagnostic data (and the driving data) and the estimation result (e.g., the name of the faulty part) to the output information providing device 50 via the NW communication unit 11.

[0104] Next, the output information providing device 50 extracts part codes of parts installed in the model from the model name and part names (step S205). The information providing unit 55 of the output information providing device 50 extracts part codes corresponding to the part name (faulty part name) of the estimation result and the model name included in the diagnostic data from the model / part specification information storage unit 52.

[0105] Next, the information providing unit 55 extracts support information related to the model, part name, and diagnostic data (step S206). Here, the support information includes part codes and various link information. The information providing unit 55 acquires the various link information, for example, using the link information storage unit 54.

[0106] Next, the output information providing device 50 transmits the extracted output information (support information) to the diagnostic device 10 (step S207). The information providing unit 55 transmits the support information, such as the part code and various link information, to the diagnostic device 10 via the NW communication unit 51.

[0107] Next, the output information generating unit 134 of the diagnostic device 10 generates output information (screen information) from the estimation result and the support information (step S208). The output information generating unit 134 generates output information such as screen G2 shown in Fig. 5 and screen G3 shown in Fig. 6, and stores the output information in the output information storage unit 125.

[0108] Next, diagnostic device 10 transmits the output information (screen information) to maintenance terminal 32 (step S209). Output information generator 134 transmits the output information stored in output information storage unit 125 to maintenance terminal 32 via NW communication unit 11.

[0109] Next, the maintenance terminal 32 displays output information (screen information) on the display unit 323 (step S210). The terminal control unit 325 displays output information such as screen G2 shown in Fig. 5 or screen G3 shown in Fig. 6 on the display unit 323.

[0110] Next, the details of the part code providing process of the output information providing device 50 will be described with reference to Fig. 10. Fig. 10 is a flowchart showing an example of the part code providing process of the output information providing device 50 in this embodiment.

[0111] 10 , the information providing unit 55 of the output information providing device 50 first acquires the model name and the name of the estimated faulty part from the diagnostic device 10 (step S301). The information providing unit 55 receives the model name and the name of the faulty part via the NW communication unit 51.

[0112] Next, the information providing unit 55 extracts the corresponding part code from the model / part correspondence table (step S302). The information providing unit 55 extracts the part code corresponding to the model name and the name of the malfunctioning part from the model / part specification information storage unit 52.

[0113] Next, the information providing unit 55 transmits the extracted part codes to the diagnostic device 10 (step S303). The information providing unit 55 transmits the extracted part codes as support information to the diagnostic device 10 via the NW communication unit 51. After the processing of step S303, the information providing unit 55 ends the part code providing process.

[0114] Next, the link information providing process of the output information providing device 50 will be described in detail with reference to Fig. 11. Fig. 11 is a flowchart showing an example of the link information providing process of the output information providing device 50 in this embodiment.

[0115] 11, the information providing unit 55 of the output information providing device 50 first acquires the model name and the name of the estimated faulty part from the diagnostic device 10 (step S401). Note that the processes of steps S401 and S402 are similar to the processes of steps S301 and S302 shown in FIG. 10, and therefore, description thereof will be omitted here.

[0116] In step S403, the information providing unit 55 generates link information as support information related to the model name and the part code. The information providing unit 55 acquires, as support information, link information corresponding to the model name and the part code from the link information storage unit 54, for example.

[0117] Next, information providing unit 55 transmits the generated link information to diagnostic device 10 (step S404). Information providing unit 55 transmits the generated link information as support information to diagnostic device 10 via NW communication unit 51. After processing of step S404, information providing unit 55 ends the link information providing process.

[0118] Next, details of the maintenance-related information providing process of the output information providing device 50 will be described with reference to Fig. 12. Fig. 12 is a flowchart showing an example of the maintenance-related information providing process of the output information providing device 50 in this embodiment.

[0119] In FIG. 12, the processes of steps S501 and S502 are the same as the processes of steps S301 and S302 shown in FIG. 10 described above, and therefore a description thereof will be omitted here.

[0120] In step S503, the information providing unit 55 generates a similarity between the tag information of each piece of maintenance-related information and the diagnostic data and the part code. ｎ ) is calculated using the above-mentioned formula (1).

[0121] Next, the information providing unit 55 sorts the maintenance-related information in descending order of similarity, selects the maintenance-related information with the highest similarity, and generates link information (step S504). The information providing unit 55 acquires link information for directly accessing the selected maintenance-related information from, for example, the link information storage unit 54.

[0122] Next, the information providing unit 55 transmits the link information of the extracted maintenance-related information to the diagnostic device 10 (step S505). The information providing unit 55 transmits the link information of the maintenance-related information as support information to the diagnostic device 10 via the NW communication unit 51. After the processing of step S505, the information providing unit 55 ends the processing of providing the maintenance-related information.

[0123] As described above, the maintenance support system 1 according to this embodiment includes the faulty part estimation unit 133, the information providing unit 55 (output information providing device 50), and the output information generating unit 134. The faulty part estimation unit 133 estimates a faulty part of the diagnosis target device 22 based on diagnostic data for diagnosing the diagnosis target device 22, the diagnostic data having data on a plurality of data items including malfunction symptoms. The information providing unit 55 provides support information for maintaining the diagnosis target device 22 based on the diagnostic data and the estimation result estimated by the faulty part estimation unit 133. The output information generating unit 134 generates output information based on the support information provided by the information providing unit 55 and the estimation result.

[0124] As a result, the maintenance support system 1 according to this embodiment generates output information based on the support information and the estimation result (faulty part), allowing the maintenance company to obtain appropriate support information for maintenance. Therefore, the maintenance support system 1 according to this embodiment can make the maintenance work of the maintenance company more efficient.

[0125] In this embodiment, the information providing unit 55 extracts a part code from the model / component specification information storage unit 52 (model / component information storage unit) based on the model name (model identification information) and the part name of the faulty part included in the diagnostic data, and outputs the extracted part code as support information. The model / component specification information storage unit 52 (model / component information storage unit) stores the model identification information of the diagnosis target device 21 and the names and part codes of the parts mounted on the diagnosis target device 21 in association with each other.

[0126] As a result, the maintenance support system 1 according to this embodiment does not require the maintenance company to manually check the part code of a faulty part, for example. Therefore, the maintenance support system 1 according to this embodiment can easily obtain various related support information using the part code, further improving the work efficiency of the maintenance company.

[0127] In this embodiment, the information providing unit 55 acquires link information from the link information storage unit 54 based on the model identification information and the part code, and outputs the acquired link information as support information. The link information storage unit 54 stores the model identification information and the part code in association with link information indicating the link destination of information related to the model and faulty part of the diagnosis target device 22. The output information generating unit 134 generates display information including the estimation result and the link information.

[0128] As a result, the maintenance support system 1 according to this embodiment can provide link information to the maintenance company, allowing the maintenance company to easily access link destinations related to maintenance work. Therefore, the maintenance support system 1 according to this embodiment can further improve the work efficiency of the maintenance company.

[0129] In this embodiment, the information providing unit 55 outputs link information including a link to at least one of the specification information of the faulty part, the maintenance-related information of the diagnosis target device 22, and the ordering site of the faulty part.

[0130] As a result, the maintenance support system 1 according to this embodiment can easily access links related to maintenance work, such as specification information for the faulty part, maintenance-related information for the equipment 22 to be diagnosed, and the ordering site for the faulty part, thereby further improving the work efficiency of maintenance companies.

[0131] In addition, in this embodiment, the information providing unit 55 calculates the similarity between the diagnostic data and part code and the tag information assigned to the maintenance-related information, selects the maintenance-related information based on the similarity, and outputs link information that allows access to the selected maintenance-related information.

[0132] As a result, the maintenance support system 1 according to this embodiment selects maintenance-related information based on the similarity, making it possible to obtain appropriate maintenance-related information and further improve the work efficiency of maintenance companies. The maintenance support system 1 according to this embodiment can better associate failure trends with diagnostic information, and is expected to be able to search for maintenance information according to the situation.

[0133] The maintenance support system 1 according to this embodiment also includes a model learning unit 433. The model learning unit 433 generates a faulty component detection model for estimating a faulty component using learning data including maintenance record information from past diagnoses of the diagnosis target device 21. The faulty component estimation unit 133 estimates a faulty component using the faulty component detection model.

[0134] As a result, the maintenance support system 1 according to this embodiment can accurately estimate the faulty part by using the faulty part detection model to estimate the faulty part, thereby improving the diagnostic quality of the maintenance company.

[0135] Furthermore, in this embodiment, the faulty part estimation unit 133 extracts similar cases that are similar to the diagnostic data from the maintenance record information storage unit 421 that stores maintenance record information, and estimates the faulty part from the extracted similar cases using the faulty part detection model.

[0136] As a result, the maintenance support system 1 according to this embodiment can accurately estimate the faulty part by taking into account similar past cases. Therefore, the maintenance support system 1 according to this embodiment can improve the accuracy of fault diagnosis and the quality of diagnosis by the maintenance company.

[0137] In this embodiment, the model learning unit 433 generates a faulty part detection model using learning data including operation data of the diagnosis target device 21 previously collected from the diagnosis target device 21 (e.g., sensor detection data, error codes, etc.) and maintenance record information. The faulty part estimation unit 133 estimates the faulty part based on the diagnostic data and operation data received from the maintenance terminal 32. The output information generation unit 134 transmits output information to the maintenance terminal 32.

[0138] As a result, the maintenance support system 1 according to this embodiment generates a faulty part detection model taking into account operating data (e.g., sensor detection data, error codes, etc.), thereby enabling more accurate estimation of faulty parts.

[0139] Furthermore, in this embodiment, the output information generating unit 134 generates, as output information, display information including similar cases that are similar to the diagnostic data and graphs that represent trends for each data item of the similar cases.

[0140] As a result, the maintenance support system 1 according to this embodiment can appropriately grasp the trends of similar cases using graphs, and can further improve the work efficiency of maintenance companies.

[0141] Furthermore, the maintenance support method according to this embodiment includes a faulty part inferring step, an information providing step, and an output information generating step. In the faulty part inferring step, the faulty part inferring unit 133 infers a faulty part of the diagnosis target device 22 based on diagnostic data for diagnosing the diagnosis target device 22, the diagnostic data having data for a plurality of data items including malfunction symptoms. In the information providing step, the information providing unit 55 provides support information for maintaining the diagnosis target device 22 based on the diagnostic data and the estimation result estimated by the faulty part inferring unit 133. In the output information generating step, the output information generating unit 134 generates output information based on the support information provided by the information providing unit 55 and the estimation result.

[0142] As a result, the maintenance support method according to this embodiment achieves the same effects as the maintenance support system 1 described above, allowing the maintenance company to obtain appropriate support information for maintenance, thereby making the maintenance work of the maintenance company more efficient.

[0143] 13 is a diagram illustrating the hardware configuration of each device in the maintenance support system 1 according to this embodiment. The devices shown in FIG. 13 illustrate the hardware configuration of each device (the diagnosis device 10, the model learning device 40, the output information providing device 50, and the information providing server 60) in the maintenance support system 1.

[0144] As shown in FIG. 13, each device of the maintenance support system 1 (the diagnostic device 10, the model learning device 40, the output information providing device 50, and the information providing server 60) includes a communication device H11, a memory H12, and a processor H13.

[0145] The communication device H11 is a communication device such as a LAN card that can be connected to the network NW1. The memory H12 is a storage device such as a RAM, a flash memory, or an HDD, and stores various information and programs used by each device (the diagnostic device 10, the model learning device 40, the output information providing device 50, and the information providing server 60).

[0146] The processor H13 is a processing circuit including, for example, a CPU, etc. The processor H13 executes various processes of each device (the diagnostic device 10, the model learning device 40, the output information providing device 50, and the information providing server 60) by executing programs stored in the memory H12.

[0147] The present disclosure is not limited to the above-described embodiments and may be modified within the scope of the present disclosure. For example, in the above-described embodiments, the maintenance support system 1 includes the diagnostic device 10, the model learning device 40, and the output information providing device 50. However, the present disclosure is not limited to this. Some or all of these devices may be integrated into other devices, for example, they may be realized by a single device. Furthermore, the functions may be further divided, and the maintenance support system 1 may be configured by four or more devices.

[0148] In the above embodiment, the model learning device 40 generates a faulty part detection model using maintenance record information and driving data, but the present invention is not limited to this. A faulty part detection model may be generated without using driving data. In this case, the diagnostic device 10 may estimate a faulty part without using driving data.

[0149] In addition, in the above embodiment, an example was described in which communication between each device is achieved using two networks, network NW1 and network NW2, but this is not limited to this and may be achieved using one network or three or more networks.

[0150] In the above embodiment, an air conditioner has been described as an example of the diagnosis target device 20, but the diagnosis target device 20 is not limited to this. The diagnosis target device 20 may be, for example, another home appliance, an IoT device, or the like.

[0151] In the above embodiment, the information providing unit 55 of the output information providing device 50 calculates the similarity with the tag information using the above-mentioned formula (1), but the present invention is not limited to this. The faulty part estimation unit 133 of the diagnostic device 10 may also use formula (1) in calculating the similarity between similar cases.

[0152] In addition, in the above embodiment, an example has been described in which the output information generation unit 134 generates an output screen as shown in Figures 5 and 6, but this is not limited to this, and the output information generation unit 134 may transmit display information to the maintenance terminal 32, and the maintenance terminal 32 may generate an output screen based on the display information.

[0153] Each component of the maintenance support system 1 described above has an internal computer system. A program for implementing the functions of each component of the maintenance support system 1 described above may be recorded on a computer-readable recording medium, and the program recorded on the recording medium may be read into a computer system and executed to perform processing in each component of the maintenance support system 1 described above. Here, "reading a program recorded on a recording medium into a computer system and executing it" includes installing the program into a computer system. The term "computer system" here includes an OS and hardware such as peripheral devices.

[0154] Furthermore, a "computer system" may include multiple computer devices connected via a network, including communication lines such as the Internet, WAN, LAN, and dedicated lines. Furthermore, a "computer-readable recording medium" refers to portable media such as flexible disks, optical magnetic disks, ROMs, and CD-ROMs, as well as storage devices such as hard disks built into a computer system. Thus, the recording medium storing the program may be a non-transitory recording medium such as a CD-ROM.

[0155] The recording medium also includes internal or external recording media accessible from a distribution server for distributing the program. The program may be divided into multiple parts, downloaded at different times, and then combined by each component of the maintenance support system 1, or each divided program may be distributed by a different distribution server. Furthermore, the term "computer-readable recording medium" also includes a medium that stores a program for a certain period of time, such as volatile memory (RAM) within a computer system that serves as a server or client when a program is transmitted over a network. The program may also be a medium for implementing part of the above-described functions. Furthermore, the program may be a so-called differential file (differential program) that can realize the above-described functions in combination with a program already stored in the computer system.

[0156] 1...Maintenance support system, 10...Diagnostic device, 11, 41, 51, 61, 321...NW communication unit, 12...Device storage unit, 13...Diagnosis processing unit, 20, 21, 22...Diagnosis target equipment, 30, 31, 32...Maintenance terminal, 40...Model learning device, 42...Learning storage unit, 43...Learning processing unit, 50...Output information providing device, 52...Model type and part specification information storage unit, 53...Maintenance related information storage unit, 54...Link information storage unit, 55...Information providing unit, 60...Information providing server, 62...Parts ordering processing unit, 63...Failure determination information providing unit, 64...Service information providing unit, 65...Maintenance Maintenance manual providing unit, 121... diagnostic data storage unit, 122, 422... driving data storage unit, 123, 423... model storage unit, 124... estimation result storage unit, 125... output information storage unit, 131... diagnostic data acquisition unit, 132... driving data acquisition unit, 133... faulty part estimation unit, 134... output information generation unit, 322... input unit, 323... display unit, 324... terminal storage unit, 325... terminal control unit, 421... maintenance record information storage unit, 431... maintenance record information collection unit, 432... driving data collection unit, 433... model learning unit, NW1, NW2... network

Claims

1. A maintenance support system comprising: a faulty part estimation unit that estimates a faulty part of a device to be diagnosed based on diagnostic data for diagnosing the device, the diagnostic data having data of a plurality of data items including malfunction symptoms; an information providing unit that provides support information for maintaining the device to be diagnosed based on the diagnostic data and an estimation result estimated by the faulty part estimation unit; and an output information generating unit that generates output information based on the support information provided by the information providing unit and the estimation result.

2. The maintenance support system according to claim 1, wherein the information providing unit extracts the part code from a model / part information storage unit that stores model identification information of the device to be diagnosed in association with the names and part codes of parts installed in the device to be diagnosed, based on the model identification information and the name of the faulty part contained in the diagnostic data, and outputs the extracted part code as the support information.

3. The maintenance support system of claim 2, wherein the information providing unit obtains the link information based on the model identification information and the part code from a link information storage unit that stores, in association with each other, the model identification information and the part code, and link information indicating a link destination of information related to the model of the diagnosed equipment and the faulty part, and outputs the obtained link information as the support information; and the output information generating unit generates display information including the estimation result and the link information.

4. The maintenance support system according to claim 3, wherein the information providing unit outputs the link information including at least one link destination among specification information of the faulty part, maintenance-related information of the equipment to be diagnosed, and an ordering site for the faulty part.

5. The maintenance support system according to claim 4, wherein the information providing unit calculates a similarity between the diagnostic data and the part code and tag information assigned to the maintenance-related information, selects the maintenance-related information based on the similarity, and outputs the link information that enables access to the selected maintenance-related information.

6. A maintenance support system as claimed in any one of claims 1 to 5, further comprising a model learning unit that generates a faulty part detection model for estimating the faulty part using learning data including maintenance record information from past diagnoses of the equipment to be diagnosed, wherein the faulty part estimation unit estimates the faulty part using the faulty part detection model.

7. The maintenance support system according to claim 6, wherein the faulty part estimation unit extracts similar cases similar to the diagnostic data from a maintenance record information storage unit that stores the maintenance record information, and estimates the faulty part from the extracted similar cases using the faulty part detection model.

8. The maintenance support system described in claim 6 or claim 7, wherein the model learning unit generates the faulty part detection model using the learning data including the maintenance record information and the operation data of the equipment to be diagnosed previously collected from the equipment to be diagnosed; the faulty part estimation unit estimates the faulty part based on the diagnostic data and the operation data received from a maintenance terminal; and the output information generation unit transmits the output information to the maintenance terminal.

9. A maintenance support system as described in any one of claims 1 to 8, wherein the output information generation unit generates, as the output information, display information including similar cases similar to the diagnostic data and graphs showing trends for each data item of the similar cases.

10. A maintenance support method, in which a faulty part estimation unit estimates a faulty part of a device to be diagnosed based on diagnostic data for diagnosing the device, the diagnostic data having data of a plurality of data items including malfunction symptoms, an information providing unit provides support information for maintaining the device to be diagnosed based on the diagnostic data and the estimation result estimated by the faulty part estimation unit, and an output information generating unit generates output information based on the support information provided by the information providing unit and the estimation result.

Images