CN112527542A - Fault analysis method - Google Patents
Fault analysis method Download PDFInfo
- Publication number
- CN112527542A CN112527542A CN202010976199.7A CN202010976199A CN112527542A CN 112527542 A CN112527542 A CN 112527542A CN 202010976199 A CN202010976199 A CN 202010976199A CN 112527542 A CN112527542 A CN 112527542A
- Authority
- CN
- China
- Prior art keywords
- data
- data set
- failure
- components
- vin
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q10/00—Administration; Management
- G06Q10/20—Administration of product repair or maintenance
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
- G06F11/0703—Error or fault processing not based on redundancy, i.e. by taking additional measures to deal with the error or fault not making use of redundancy in operation, in hardware, or in data representation
- G06F11/079—Root cause analysis, i.e. error or fault diagnosis
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
- G06F11/08—Error detection or correction by redundancy in data representation, e.g. by using checking codes
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
- G06F11/08—Error detection or correction by redundancy in data representation, e.g. by using checking codes
- G06F11/085—Error detection or correction by redundancy in data representation, e.g. by using checking codes using codes with inherent redundancy, e.g. n-out-of-m codes
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F18/00—Pattern recognition
- G06F18/20—Analysing
- G06F18/21—Design or setup of recognition systems or techniques; Extraction of features in feature space; Blind source separation
- G06F18/214—Generating training patterns; Bootstrap methods, e.g. bagging or boosting
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q50/00—Systems or methods specially adapted for specific business sectors, e.g. utilities or tourism
- G06Q50/04—Manufacturing
-
- G—PHYSICS
- G07—CHECKING-DEVICES
- G07C—TIME OR ATTENDANCE REGISTERS; REGISTERING OR INDICATING THE WORKING OF MACHINES; GENERATING RANDOM NUMBERS; VOTING OR LOTTERY APPARATUS; ARRANGEMENTS, SYSTEMS OR APPARATUS FOR CHECKING NOT PROVIDED FOR ELSEWHERE
- G07C5/00—Registering or indicating the working of vehicles
- G07C5/08—Registering or indicating performance data other than driving, working, idle, or waiting time, with or without registering driving, working, idle or waiting time
- G07C5/0808—Diagnosing performance data
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
- Y02P—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN THE PRODUCTION OR PROCESSING OF GOODS
- Y02P90/00—Enabling technologies with a potential contribution to greenhouse gas [GHG] emissions mitigation
- Y02P90/30—Computing systems specially adapted for manufacturing
Abstract
The invention relates to a method for fault analysis of a device having a plurality of interacting components, comprising the following steps: importing data relating to a fault event; analyzing the data to assign a device identifier to each associated device; analyzing the data in order to assign to each device having the associated assigned device identifier a failure data set indicating the associated failure, respectively, in order to thus form a device failure data set in each case; forming group datasets by assigning the device failure datasets to the same failure event; augmenting the set of datasets with additional data from the OEM database containing data relating to components of the device; generating a profile data set by analyzing the augmented group data set, the profile data set indicating the presence of components in the respective device; and determining the frequency of occurrence of the component.
Description
Technical Field
The invention relates to a method for fault analysis of a device having a plurality of interacting components. The invention also relates to a computer program product, a profile data set and a system designed to perform such a method.
Background
Unreliable or inelastic equipment and its components and interactions between these components that have not been adequately tested, verified or validated in advance may be the cause of warranty cases. The complexity of the device and its components (especially hardware and software components) makes it virtually impossible to reliably verify the device even in cases where component testing is highly intensive.
As a result, warranty cases arise, which leads to a difficult task of determining the cause of the warranty case. Due to the complexity of the device and the very limited feedback that the user can provide, it may take some time to find the cause. During this time, the number of warranty cases is increasing.
US 2016/0035145 a1 discloses a data analysis method that analyzes data relating to equipment and data from OEM databases.
US 9582944 discloses a method for providing service information which together with additional data from a database analyzes a device identifier of a device.
Thus, there is a need to show ways in which a solution can be provided.
Disclosure of Invention
The object of the invention is achieved by a method for fault analysis of a device having a plurality of interacting components, comprising the steps of:
importing data relating to a fault event;
analyzing the data to assign a device identifier to each associated device;
analyzing the data in order to assign to each device having the associated assigned device identifier a failure data set indicating the associated failure, respectively, in order to thus form a device failure data set in each case;
forming group datasets by assigning the device failure datasets to the same failure event;
augmenting the set of datasets with additional data from the OEM database containing data related to the device component;
generating a profile data set by analyzing the augmented group data set, the profile data set indicating the presence of components in the respective device; and
the frequency of occurrence of the component is determined.
In this process, the method assumes that only one component of the device, which is also present in all devices in which a fault event occurs, is considered to be the cause of the fault event occurring in the plurality of devices. The localization of faults can thereby be simplified in a particularly simple manner.
This approach is particularly advantageous if diagnostic data from the on-board diagnostic system for fault analysis is lost, for example due to a loss of voltage (e.g., due to a low battery of the vehicle or a loss of voltage resulting from a replacement vehicle battery), and then because the diagnostic data cannot be used to locate the fault.
According to an embodiment of the invention, the device failure data set is augmented with additional data from a manufacturer database using the device identifier. In this case, the device identifier allows a unique identification of the device, for example, a Vehicle Identification Number (VIN) of the motor vehicle. It consists of a world manufacturer identifier, a manufacturer specific code and a serial number, which usually depends on the year of manufacture. The data may include the model number, model family, engine type, year of manufacture, or date of the failure event of the device. The accuracy of the fault analysis can thereby be improved.
According to another embodiment, the associated device identifier is used for the purpose of augmenting the group dataset with additional data from the OEM database containing data relating to the components of the device. The OEM database may be an OEM database from an original equipment manufacturer or a manufacturer as at least one component of the equipment. In the case of a motor vehicle, the OEM database may be a database of a supplier company that manufactures the components already installed in the device or motor vehicle. By analyzing the OEM database, specific data may be collected that provides information about existing versions of hardware components and/or software components. Therefore, the accuracy of fault analysis can be further improved.
According to another embodiment, the components are hardware components and/or software components. It is therefore possible to analyze exclusively the interaction between the hardware and software components of the device, which otherwise would be possible only with great effort due to their complexity.
The invention also relates to a computer program product, a profile data set and a system designed to perform such a method.
Drawings
The invention will now be described with reference to the accompanying drawings, in which:
fig. 1 shows a device with a plurality of components in a schematic view;
FIG. 2 schematically illustrates a profile data set;
fig. 3 shows a method sequence in a schematic representation.
Detailed Description
Reference is first made to fig. 1.
A device 2a is shown with a plurality of components 4a, 4b, 4c, 4n, four of which 4a, 4b, 4c, 4d are shown in fig. 1.
In the present exemplary embodiment, the device 2a is a motor vehicle, for example an automobile. The components 4a, 4b, 4c, … …, 4n may be, for example, a vehicle battery and other components (e.g., load, charge current regulator, etc.) that interact with the vehicle battery. The components 4a, 4b, 4c, … …, 4n may be hardware components or software components.
During the warranty period of the device 2a, one of the components 4a, 4b, 4c, … …, 4n may fail. This may be due to the components 4a, 4b, 4c, … …, 4n themselves (e.g. due to a battery failure), or due to other areas, e.g. in the case of a motor vehicle as the device 2a, due to a failure of the engine control module, a software state or a setting failure in the vehicle (e.g. setting the system to its initialization state). However, the component 4a, 4b, 4c, … …, 4n itself is not the cause of the fault at all, but another one of the components 4a, 4b, 4c, … …, 4n is the cause of the fault.
To simplify fault localization in this case, a system 6 is provided, which system 6 may contain hardware components and/or software components for the tasks and functions described below.
The system 6 is designed to import data D (see fig. 3) relating to a failure event of the device 2a, which failure event has been reported by a user, for example.
The system 6 is further designed to assign a device identifier VIN (see fig. 3) of the device 2a to the imported data D. In the present exemplary embodiment, the device identifier VIN is a vehicle identification number.
In addition, the system 6 is designed to form a device failure data set VFD (see fig. 3) by combining the device identifier VIN with the failure data set FD (see fig. 3). The fault data set FD may be a code number, a voice message or a text message describing the fault that has occurred.
Further, the system 6 in the present exemplary embodiment may assign additional data from the manufacturer database 8 related to the device 2a to the device failure data set VFD based on the device identifier VIN. The additional data may be the model number, model series, engine type, year of manufacture or date of the failure event of the device 2 a.
After forming a plurality of device failure data sets VFD for a plurality of devices 2 having a plurality of failure events, the system 6 is further designed to form a plurality of group data sets GD by assigning the device failure data sets VFD to the same failure event.
In addition, the system 6 accesses the OEM database 10 using the associated device identifier VIN in order to augment the device failure data set VFD with additional data D' relating to the components 4a, 4b, 4c, … …, 4n of the device 2 a. As a result, a plurality of extended group datasets DG' may then be used.
The system 6 is also designed to form a profile data set HD (Histogramm-Datensatz) by analyzing the extended group data set DG'. As explained with reference to fig. 2, the profile data set HD indicates the frequency of occurrence H of the components 4a, 4b, 4c, … …, 4n in the device 2 a.
The profile data set HD is now explained with additional reference to fig. 2.
The profile data set HD contains data of five devices 2a, 2b, 2c, 2d, 2 e.
The device 2a in the first row, which is identified by the device identifier VIN, failed on day 7, 13 of 2014 and belongs to model series 1. The components 4a, 4b, 4c, … …, 4n are referred to as part 1 to part 3 belonging to the device 2 a.
The device 2b in the second row fails the same as the device 2a in the first row and contains components 4a, 4b, 4c, … …, 4n in sections 1 through 3 and section 91.
For the purpose of analyzing the profile data set HD, respective sums are formed for the same components 4a, 4b, 4c, … …, 4 n. In the exemplary embodiment shown in fig. 2, all five listed devices 2 contain a component 4c in the section 3.
The component 4c is thus a subdivision comprised by all the apparatuses 2a, 2b, 2c, 2d, 2 e. Thus, this component 4c may be identified as the most likely cause of the problem identified in the device 2 a.
The method procedure for operating the system 6 shown in fig. 1 is now explained with additional reference to fig. 3.
In a first step S100, the system 6 imports data D relating to a failure event.
In a further step S200, the system 6 analyzes the data D in order to determine the device identifier VIN of the device 2 a.
In a further step S300 the system 6 analyses the data D in order to assign a fault data set DF indicative of the fault to the device 2a with the now assigned device identifier VIN in order to form a device fault data set VFD relating to the device 2 a.
In a further step S400, the system 6 forms a plurality of group data sets GD once a plurality of device failure data sets VFD for a plurality of devices 2a, 2b, 2c, 2d, 2e having different failure events have been formed.
In another step S500, the system 6 augments the group dataset GD with additional data D' from the OEM database 10.
In a further step S600, the system 6 generates a profile data set HD by analyzing the augmented group data set DG', which profile data set HD indicates the presence of the components 4a, 4b, 4c, … …, 4n in the respective devices 2a, 2b, 2c, 2d, 2 e.
In a further step S700, the system 6 then determines the frequency of occurrence H of the components 4a, 4b, 4c, … …, 4n in the respective devices 2a, 2b, 2c, 2d, 2 e.
As an alternative to the present exemplary embodiment, the order of the steps may also be different. In addition, multiple steps may be performed simultaneously or concurrently. Further, as an alternative to the present exemplary embodiment, the respective steps may also be skipped or omitted.
The localization of faults can thereby be simplified in a particularly simple manner.
List of reference numerals
2a device
2b device
2c device
2d device
2e device
4a parts
4b parts
4c parts
4d parts
4n parts
6 System
8 manufacturer database
10OEM database
D data
D' data from the manufacturer database
D' data from OEM database
FD Fault data set
GD group dataset
GD' augmented group dataset
Frequency of occurrence of H
HD profile data set
VFD device failure data set
VIN device identifier
S100 step
S200 step
S300 step
S400 step
S500 step
S600 step
S700 step
Claims (10)
1. A method for fault analysis of a device (2a, 2b, 2c, 2d, 2e) having a plurality of interacting components (4a, 4b, 4c, … … 4n), comprising the steps of:
importing data (D) relating to a fault event;
analysing said data (D) to assign a device identifier (VIN) to each associated device (2a, 2b, 2c, 2D, 2 e);
analyzing the data (D) in order to assign each device (2a, 2b, 2c, 2D, 2e) with an associated assigned device identifier (VIN) a failure data set (FD) indicative of the associated failure, respectively, in order to thus form in each case a device failure data set (VFD);
forming Group Datasets (GD) by assigning the device failure datasets (VFD) to the same failure event;
augmenting the Group Dataset (GD) with additional data (D') from an OEM database (10) containing data relating to components (4a, 4b, 4c, … … 4n) of the device (2a, 2b, 2c, 2D, 2 e);
generating a profile data set (HD) by analyzing the augmented group data set (DG'), the profile data set (HD) indicating the presence of the components (4a, 4b, 4c, … … 4n) in the respective devices (2a, 2b, 2c, 2d, 2 e); and
the frequency of occurrence (H) of the components (4a, 4b, 4c, … … 4n) is determined.
2. The method of claim 1, wherein the device failure data set (VFD) is augmented with additional data (D') from a manufacturer database (8) using a device identifier (VIN).
3. The method according to claim 1 or 2, wherein the related device identifier (VIN) is used for the purpose of augmenting the Group Dataset (GD) with additional data (D') from an OEM database (10) containing data relating to components (4a, 4b, 4c, … … 4n) of a device (2a, 2b, 2c, 2D, 2 e).
4. A method according to claim 1, 2 or 3, wherein the component (4a, 4b, 4c, 4n) is a hardware component and/or a software component.
5. A computer program product designed to perform the method according to any one of claims 1 to 4.
6. A profile data set (HD) generated by the method according to any one of claims 1 to 4.
7. A system (6) for fault analysis of a device (2a, 2b, 2c, 2d, 2e) having a plurality of interacting components (4a, 4b, 4c, … … 4n), wherein the system (6) is designed to: importing data (D) relating to a fault event; analysing said data (D) to assign a device identifier (VIN) to each associated device (2a, 2b, 2c, 2D, 2 e); analyzing the data (D) in order to assign each device (2a, 2b, 2c, 2D, 2e) with an associated assigned device identifier (VIN) a failure data set (FD) indicative of the associated failure, respectively, in order to thus form in each case a device failure data set (VFD); forming Group Datasets (GD) by assigning the device failure datasets (VFD) to the same failure event; augmenting the Group Dataset (GD) with additional data (D') from an OEM database (10) containing data relating to components (4a, 4b, 4c, … … 4n) of the device (2a, 2b, 2c, 2D, 2 e); generating a profile data set (HD) by analyzing the augmented group data set (DG'), the profile data set (HD) indicating the presence of the components (4a, 4b, 4c, … … 4n) in the respective devices (2a, 2b, 2c, 2d, 2 e); and to determine the frequency of occurrence (H) of the components (4a, 4b, 4c, … … 4 n).
8. The system (6) as claimed in claim 7, wherein the system (6) is designed to augment the device failure data set (VFD) with additional data (D') from a manufacturer database (8) using a device identifier (VIN).
9. The system (6) as claimed in claim 7 or 8, wherein the system (6) is designed for the purpose of augmenting the Group Dataset (GD) with additional data (D') from an OEM database (10) containing data relating to components (4a, 4b, 4c, … … 4n) of a device (2a, 2b, 2c, 2D, 2e) with an associated device identifier (VIN).
10. The system (5) according to claim 7, 8 or 9, wherein the component (4a, 4b, 4c, 4n) is a hardware component and/or a software component.
Applications Claiming Priority (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| DE102019125077.3 | 2019-09-18 | ||
| DE102019125077.3A DE102019125077A1 (en) | 2019-09-18 | 2019-09-18 | Procedure for failure analysis |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN112527542A true CN112527542A (en) | 2021-03-19 |
Family
ID=74686235
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202010976199.7A Pending CN112527542A (en) | 2019-09-18 | 2020-09-16 | Fault analysis method |
Country Status (2)
| Country | Link |
|---|---|
| CN (1) | CN112527542A (en) |
| DE (1) | DE102019125077A1 (en) |
Families Citing this family (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| DE102021112661A1 (en) | 2021-05-17 | 2022-11-17 | Bayerische Motoren Werke Aktiengesellschaft | Method, device, computer program and computer-readable storage medium for determining faulty vehicles |
Family Cites Families (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| DE102005040142A1 (en) * | 2005-08-25 | 2007-03-01 | Daimlerchrysler Ag | Method for identifying complex diagnostic situations in customer service |
| US8977423B2 (en) * | 2012-05-23 | 2015-03-10 | Snap-On Incorporated | Methods and systems for providing vehicle repair information |
| US20160035145A1 (en) * | 2014-07-31 | 2016-02-04 | Ford Global Technologies, Llc | Method and Apparatus for Vehicle Data Gathering and Analysis |
| US11429936B2 (en) * | 2015-10-02 | 2022-08-30 | Snap-On Incorporated | System and method for dynamically-changeable displayable pages with vehicle service information |
-
2019
- 2019-09-18 DE DE102019125077.3A patent/DE102019125077A1/en active Pending
-
2020
- 2020-09-16 CN CN202010976199.7A patent/CN112527542A/en active Pending
Also Published As
| Publication number | Publication date |
|---|---|
| DE102019125077A1 (en) | 2021-03-18 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN108563214B (en) | Vehicle diagnosis method, device and equipment | |
| CN107918382B (en) | Automobile fault diagnosis method, automobile fault diagnosis device and electronic equipment | |
| US8527441B2 (en) | Developing fault model from service procedures | |
| EP2803048B1 (en) | System and method for providing diagnostic fault information | |
| Guissouma et al. | An empirical study on the current and future challenges of automotive software release and configuration management | |
| US20180174373A1 (en) | Synthetic fault codes | |
| WO2010067547A1 (en) | Vehicle failure diagnostic device | |
| Papadopoulos et al. | The potential for a generic approach to certification of safety critical systems in the transportation sector | |
| CN110555115A (en) | method and device for determining vehicle maintenance scheme | |
| EP4254254A1 (en) | Automatic construction method and apparatus for automobile bus topology map, and computing device | |
| US8452774B2 (en) | Methodology to establish term co-relationship using sentence boundary detection | |
| Sax et al. | A survey on the state and future of automotive software release and configuration management | |
| US20180164760A1 (en) | System and method to construct diagnostic dependence model | |
| CN112527542A (en) | Fault analysis method | |
| CN115016428A (en) | Three-dimensional multi-stage diagnosis system and method applied to special vehicle | |
| Graf et al. | Ivam: Implicit variant modeling and management for automotive embedded systems | |
| Altinger | State of the Art Software Development in the Automotive Industry and Analysis Upon Applicability of Software Fault Prediction | |
| Armengaud et al. | Using the CESAR Safety Framework for Functional Safety Management in the context of ISO 26262 | |
| Meroth et al. | Optimization of the development process of intelligent transportation systems using automotive SPICE and ISO 26262 | |
| Bock et al. | Analytical test effort estimation for multisensor driver assistance systems | |
| CN110297947A (en) | A kind of data calling method, device and electronic equipment | |
| Angermeier et al. | „Risk-driven Security Engineering in the Automotive Domain “ | |
| EP4167040A1 (en) | Fault model editor and diagnostic tool | |
| Pries | Failure mode & effects analysis in software development | |
| US20100241300A1 (en) | Computer-implemented squeak detection method and system |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination |