DEVELOPING FAULT MODEL FROM UNSTRUCTURED TEXT DOCUMENTS

• US 20120233112A1
• Filed: 03/10/2011
• Published: 09/13/2012
• Est. Priority Date: 03/10/2011
• Status: Abandoned Application

• Current Assignee: GM Global Technology Operations LLC (General Motors Company)
• Original Assignee: GM Global Technology Operations LLC (General Motors Company)
• Inventors: Rajpathak, Dnyanesh, Singh, Satnam
• Application Number:
  US13/045,310
• Publication Number:
  US 20120233112A1
• Time in Patent Office: Days
• US Class Current: 706/54
• CPC Class Codes: G06F 40/30 Semantic analysis

Abstract

A method and system for developing fault models from unstructured text documents, such as text verbatim descriptions from customers and service technicians. An ontology, or data model, and heuristic rules are used to identify and extract descriptive terms from the text verbatim document. The descriptive terms are then classified into types, including symptoms, failure modes, and parts. Like-meaning but differently-worded descriptive terms are then merged using text similarity scoring techniques. The resultant symptoms, failure modes, parts, and correlations are then assembled into a fault model, which can be used for real-time fault diagnosis onboard a vehicle, or off-board at service shops.

Claims

1. A method for creating a fault model for a hardware or software system, said method comprising:

providing an unstructured text document containing diagnostic information about the hardware or software system;

extracting descriptive terms from the unstructured text document using an ontology and heuristic rules;

classifying the descriptive terms into types;

merging phrases in the descriptive terms which mean the same thing but are worded differently; and

assembling the fault model from the descriptive terms.

2. The method of claim 1 wherein the descriptive terms include symptoms, failure modes, and correlation values.

3. The method of claim 1 wherein extracting descriptive terms includes detecting sentence boundaries, removing non-descriptive words, identifying parts, symptoms, and failure modes, and performing frequency analysis to determine which of the parts, the symptoms, and the failure modes are valid for inclusion in the fault model.

4. The method of claim 3 wherein detecting sentence boundaries includes identifying full-stop punctuation marks, using the full-stop punctuation marks to define sentence boundaries, and defining correlations between the parts, the symptoms, and the failure modes based on the sentence boundaries.

5. The method of claim 1 wherein the ontology is a data model describing elements of the hardware or software system, including parts, symptoms, and failure modes, and relationships between the parts, the symptoms, and the failure modes.

6. The method of claim 1 wherein classifying the descriptive terms into types includes classifying the descriptive terms as Diagnostic Trouble Code (DTC) symptoms, non-DTC symptoms, failure modes, and parts.

7. The method of claim 1 wherein merging phrases in the descriptive terms includes using text similarity techniques to assign a similarity score to a pair of descriptive terms, comparing the similarity score to a threshold value, and equating the pair of descriptive terms if the similarity score exceeds the threshold value.

8. The method of claim 1 wherein assembling the fault model includes creating rows of failure modes, creating columns of symptoms, and placing correlation values in intersections of the rows and the columns.

9. The method of claim 1 wherein the hardware or software system is a vehicle or a vehicle sub-system.

10. The method of claim 9 wherein the unstructured text document contains text verbatim descriptions from a customer of the vehicle, or from a service technician who worked on the vehicle or the vehicle sub-system.

11. A method for creating a fault model for a vehicle or a vehicle sub-system, said method comprising:

providing a text verbatim document from a customer or a service technician, said document containing diagnostic information about the vehicle or the vehicle sub-system;

extracting descriptive terms from the text verbatim document using an ontology and heuristic rules;

classifying the descriptive terms into types, where the types include Diagnostic Trouble Code (DTC) symptoms, non-DTC symptoms, failure modes, and parts;

merging phrases in the descriptive terms which mean the same thing but are worded differently; and

assembling the fault model from the descriptive terms.

12. The method of claim 11 wherein extracting descriptive terms includes detecting sentence boundaries, removing non-descriptive words, identifying descriptive terms, and performing frequency analysis to determine which of the descriptive terms are valid for inclusion in the fault model.

13. The method of claim 11 wherein merging phrases in the descriptive terms includes using text similarity techniques to assign a similarity score to a pair of descriptive terms, comparing the similarity score to a threshold value, and equating the pair of descriptive terms if the similarity score exceeds the threshold value.

14. The method of claim 11 further comprising using the fault model for fault diagnosis in connection with the vehicle or the vehicle sub-system.

15. A system for creating a fault model, said system comprising:

means for providing an unstructured text document containing diagnostic information about a hardware or software system;

means for extracting descriptive terms from the unstructured text document using an ontology and heuristic rules;

means for classifying the descriptive terms into types;

means for merging phrases in the descriptive terms which mean the same thing but are worded differently; and

means for assembling the fault model from the descriptive terms.

16. The system of claim 15 wherein the means for extracting descriptive terms detects sentence boundaries, removes non-descriptive words, identifies parts, symptoms, and failure modes, and performs frequency analysis to determine which of the parts, the symptoms, and the failure modes are valid for inclusion in the fault model.

17. The system of claim 15 wherein the means for classifying the descriptive terms into types classifies the descriptive terms as Diagnostic Trouble Code (DTC) symptoms, non-DTC symptoms, failure modes, and parts.

18. The system of claim 15 wherein the means for merging phrases in the descriptive terms uses text similarity techniques to assign a similarity score to a pair of descriptive terms, compares the similarity score to a threshold value, and equates the pair of descriptive terms if the similarity score exceeds the threshold value.

19. The system of claim 15 wherein the means for assembling the fault model creates rows of failure modes, creates columns of symptoms, and places correlation values in intersections of the rows and the columns.

20. The system of claim 15 wherein the hardware or software system is a vehicle or a vehicle sub-system, and the unstructured text document contains text verbatim descriptions from a customer of the vehicle, or from a service technician who worked on the vehicle or the vehicle sub-system.