CN106155035B - Method for diagnosing faults and fault diagnosis system based on repair class data - Google Patents

Method for diagnosing faults and fault diagnosis system based on repair class data Download PDF

Info

Publication number
CN106155035B
CN106155035B CN201510154810.7A CN201510154810A CN106155035B CN 106155035 B CN106155035 B CN 106155035B CN 201510154810 A CN201510154810 A CN 201510154810A CN 106155035 B CN106155035 B CN 106155035B
Authority
CN
China
Prior art keywords
troubleshooting
failure
fault
fault message
failure cause
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.)
Active
Application number
CN201510154810.7A
Other languages
Chinese (zh)
Other versions
CN106155035A (en
Inventor
刘煜原
黄加阳
陈金
高飞鹏
王洪
魏元雷
晏震乾
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Commercial Aircraft Corp of China Ltd
Original Assignee
Commercial Aircraft Corp of China Ltd
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by Commercial Aircraft Corp of China Ltd filed Critical Commercial Aircraft Corp of China Ltd
Priority to CN201510154810.7A priority Critical patent/CN106155035B/en
Publication of CN106155035A publication Critical patent/CN106155035A/en
Application granted granted Critical
Publication of CN106155035B publication Critical patent/CN106155035B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Abstract

Based on the method for diagnosing faults and fault diagnosis system of repair class data, the present invention provides a kind of method for diagnosing faults, including:I. at least one fault message is received;Ii. it is based at least one fault message, determines corresponding at least one failure cause, and be ranked up at least one failure cause;Iii. the sequence based on fixed at least one failure cause, determines troubleshooting flow.By using technical scheme of the present invention, the efficiency of airplane fault diagnosis can be improved, the flight delay brought by fault diagnosis is reduced and aircraft maintenance cost can be effectively reduced.

Description

Method for diagnosing faults and fault diagnosis system based on repair class data
Technical field
The present invention is generally related to aircraft field, more specifically, is related to a kind of failure based on repair class data Diagnostic method and fault diagnosis system.
Background technology
With the continuous development of aeronautical technology, the contact of each system of aircraft is more and more closer, failure also become increasingly complex and It is difficult to judge, any one failure is likely to be related to other multiple system cisco unity malfunctions.Based on repair class handbook Method for diagnosing faults is one of the important means of airplane fault diagnostic method, and carries out one of the important method of health control.
Fault Isolation Manual is that planemaker goes out according to the design feature and each user of aircraft according to its aircraft possessed Existing failure is aggregated into planemaker, and the procedure manual of the partial fault method for removing then provided again to airline is High level overview in relation to maintenance knowledge.Handbook is made full use of, the troubleshooting programming system of staff, troubleshooting work can be made to have Chapter can follow.
Therefore, there is an urgent need for a kind of fault diagnosis systems that can determine failure cause as early as possible.
Invention content
In view of the above problems, the present invention provides one kind being based on database, it can determine that the failure of failure cause is examined as early as possible Disconnected system, to which necessary troubleshooting measure can be taken to debug when airplane fault, it is ensured that the safe operation of aircraft.
According to the first aspect of the invention, a kind of method for diagnosing faults is provided, including:I. at least one failure is received Information;Ii. be based at least one fault message, determine corresponding at least one failure cause, and to it is described at least One failure cause is ranked up;Iii. the sequence based on fixed at least one failure cause, determines troubleshooting flow.
Preferably, further include in the step ii:Based at least one fault message and its corresponding failure case Example, history troubleshooting statistic record and failure principle, determine at least one failure cause
Preferably, further include in the step ii:When the number of the fault message is more than one, compare and the event Hinder the corresponding failure cause of information, and determine the degree of overlapping and/or danger classes of the failure cause, is based on the degree of overlapping And/or danger classes is ranked up the failure cause and determines corresponding troubleshooting flow.
Preferably, when single failure information corresponds to single failure reason, based on the data pair in the Maintenance plan The failure cause carries out troubleshooting;If troubleshooting is unsuccessful, it is based on the corresponding fault case of the fault message and/or failure principle To determine failure cause and corresponding troubleshooting flow.
Preferably, when the single fault message corresponds to multiple failure causes, to the multiple failure cause successively into Row troubleshooting, or according to the row determined by the corresponding fault case of the fault message, history troubleshooting statistic record and failure principle Therefore Optimizing Flow carries out troubleshooting;If troubleshooting is unsuccessful, according to based on the corresponding other fault cases of the fault message And/or failure principle determines failure cause and corresponding troubleshooting flow.
Preferably, the troubleshooting Optimizing Flow is determined by following steps:To the corresponding fault case of the fault message, go through History troubleshooting statistic record and failure principle assign different weights respectively, then determine that failure corresponding with the fault message is former Cause and corresponding troubleshooting flow.
Preferably, the weight of the fault case, history troubleshooting statistic record and failure principle is respectively 0.3,0.5 and 0.2。
Preferably, if troubleshooting success, it is determined that the failure cause, and record letter associated with the failure cause Breath.
The invention also provides a kind of fault diagnosis systems, including:Input module, for receiving at least one failure letter Breath;Data memory module, for storing failure cause corresponding with fault message and corresponding troubleshooting method;Accident analysis mould Block is communicated to connect with the input module, is configured as being based at least one fault message, is determined corresponding at least one A failure cause, and at least one failure cause is ranked up, to determine troubleshooting flow.
Preferably, the failure analysis module is additionally configured to:Based on event corresponding at least one fault message Hinder case, history troubleshooting statistic record and failure principle, determines at least one failure cause
Preferably, the failure analysis module is additionally configured to:When the number of the fault message is more than one, compare Failure cause corresponding with the fault message, and determine the degree of overlapping and/or danger classes of the failure cause, based on described Degree of overlapping and/or danger classes are ranked up the failure cause.
Preferably, if a fault message only corresponds to a failure cause in Maintenance plan, based on described Data in Maintenance plan carry out troubleshooting to the failure cause;If fault message correspondence in Maintenance plan is more When a failure cause, troubleshooting is carried out successively to the multiple failure cause, or based on by the corresponding failure case of the fault message Example, history troubleshooting statistic record and failure principle determine troubleshooting Optimizing Flow, and carry out troubleshooting;If troubleshooting is unsuccessful, it is based on The corresponding fault case of the fault message and/or failure principle determine failure cause and corresponding troubleshooting flow.
Preferably, the troubleshooting Optimizing Flow is determined by following steps:To the corresponding fault case of the fault message, go through History troubleshooting statistic record and failure principle assign different weights respectively, then determine that failure corresponding with the fault message is former Cause and corresponding troubleshooting flow.
By using technical scheme of the present invention, there can be following advantageous effects:1. improving airplane fault diagnosis Efficiency;2. reducing the flight delay brought by fault diagnosis;3. aircraft maintenance cost can be effectively reduced.
Description of the drawings
After description by reference to the specific implementation mode of the present invention given by following drawings, it is better understood with this Invention, and other objects of the present invention, details, features and advantages will become apparent.In the accompanying drawings:
Fig. 1 is the configuration diagram of the fault diagnosis of embodiment according to the present invention;
Fig. 2 shows the first troubleshooting flows of embodiment according to the present invention;
Fig. 3 shows second of troubleshooting flow of embodiment according to the present invention.
Specific implementation mode
Fault diagnosis system is established in present invention proposition based on servicing manual, to make maintenance personnel quickly confirm generation The possible cause of failure improves efficiency of operation and plays an important role to reducing maintenance cost.It, can in troubleshooting maintenance work Multiple failures can be had while waiting for investigation, and these failures are if it is as caused by a certain common cause, it is common for this The troubleshooting of reason, it will greatly improve troubleshooting efficiency.
Fig. 1 is the configuration diagram of the fault diagnosis of embodiment according to the present invention.
Fault diagnosis system 10 includes:Input module 11, for receiving at least one fault message;Data memory module 12, for storing failure cause corresponding with fault message and corresponding troubleshooting method;Failure analysis module 13, with input mould Block communicates to connect, and is configured as being based at least one fault message, determines corresponding at least one failure cause, and at least One failure cause is ranked up, to determine troubleshooting flow.
When input module 11 receives fault message, failure analysis module 13 will be according between fault message and failure cause Correspondence handled.For example, when input module 11 receives a plurality of fault message, failure analysis module 13 can be to defeated The failure cause for entering fault message is compared analysis, for example, is compared to the failure cause and danger classes of input fault Analysis, finally obtain each failure in all failure causes share reason degree of overlapping sequence and and preventive maintenance, then carry Show that user can preferentially carry out troubleshooting by the failure cause troubleshooting of degree of overlapping sequence, or by high-grade failure.
When carrying out troubleshooting to single fault message, generally there are two following situations:
The first:Single failure information corresponds to single failure reason
It is better simply a kind of situation in troubleshooting work, at this moment accident analysis that one fault message, which corresponds to a failure cause, Module 13 directly can carry out troubleshooting according to the stored troubleshooting flow corresponding to the failure cause in data memory module 12. If troubleshooting fails, failure analysis module 13 determines corresponding with the fault message other according to failure principle, fault case Failure cause, and be ranked up according to possibility, and then troubleshooting is carried out again.
Fig. 2 shows the first troubleshooting flows of embodiment according to the present invention.
First, it determines that single failure corresponds to single failure reason (step S21), is then based in data memory module 12 and deposits The corresponding troubleshooting flow (for example, deriving from servicing manual mantenance data etc.) of storage carries out troubleshooting (step S22);Judge troubleshooting Whether successful (step S23) exports diagnostic result (step S24) if success, i.e. output shows the information of faulty equipment, and The relevant information (step S25) for recording troubleshooting, is for example recorded in history troubleshooting statistic record.
If in step S22 troubleshooting failure, failure analysis module 13 according to failure principle, fault case come determine with The corresponding other failure causes of the fault message, and be ranked up (step S27) according to possibility, and then referring again to data mould Other handbooks of block carry out troubleshooting (step S28);Judge whether troubleshooting is successful (step S29), it is defeated if success, thens follow the steps S24 Go out to show the information of faulty equipment, and record the relevant information (step S25) of troubleshooting, until terminating (step S26).
Second:One fault message corresponds to multiple failure causes
It is that troubleshooting most situations occurs in the process that one fault message, which corresponds to multiple failure causes, in this case may be used To take two ways:One is mantenance data troubleshooting is directly pressed, in addition can also refer to according to former based on fault case, failure Reason, history troubleshooting statistic record determine Optimizing Flow, then carry out troubleshooting again.If do not debugged, can further join It examines failure principle, the other reasons that fault case is listed, then inquires other handbook troubleshootings one by one, until troubleshooting.
Fig. 3 shows second of troubleshooting flow of embodiment according to the present invention.
First, it determines that single failure corresponds to multiple failure causes (step S301), is then based in data memory module 12 The corresponding troubleshooting flow (for example, servicing manual data etc.) of storage carries out troubleshooting (step S302);Judge troubleshooting whether at Work((step S303) exports diagnostic result (step S304) if success, i.e. output shows the information of faulty equipment, and records The relevant information (step S305) of troubleshooting.
Equally, step S310 can also be executed after step S301, that is, is determined troubleshooting Optimizing Flow, referred again to the optimization Flow executes troubleshooting (S311), then equally judges whether troubleshooting succeeds in step S303.
Here to how to determine that the process that troubleshooting Optimizing Flow carries out is illustrated.For specific fault message, data Data in memory module 12 may provide multiple possible causes, and troubleshooting flow will investigate these reasons, positioning failure one by one. In order to be quickly found out failure cause, failure analysis module 13 is based on history troubleshooting statistic record, (similar) fault case, failure original Reason, determines whole failure causes, and whole failure causes that any of the above reference result is provided into row information fusion and Weighted analysis, so that it is determined that specific fault reason leads to failure possibility occurrence (fusion index) and integrated by the possibility Sequence, and then realize the accurate positionin of failure cause, finally provide troubleshooting Optimizing Flow.By being arranged with the Optimizing Flow Therefore the troubleshooting time can be shortened.
When based on two kinds of fault case, failure principle fault diagnosis modes come when analyzing fault message, for same therefore Hinder information, the diagnostic result that two kinds of diagnostic modes provide may be not quite similar, and can mainly show that obtained failure cause exists There is any discrepancy on content and possibility size order, in this case, need according to the characteristics of information source to provided failure Reason and its sort order distribute different weights, in conjunction with previous statistical result, provide best troubleshooting scheme.
Here the computational methods of weighted analysis are as follows:
The original of+0.2 × i of case number of statistics number+0.3 × i of convergence analysis index=0.5 × i of failure cause i Manage number
The sum of the convergence analysis index of the fusion index of reason i=reason i/all reasons convergence analysis index
Here, the weight of fault case, history troubleshooting statistic record and failure principle is respectively 0.3,0.5 and 0.2.
The numerical value of the fusion index of each reason is bigger, shows that the reason causes the possibility of this failure bigger, needs It is urgent to exclude.
If troubleshooting failure in step s 302, failure analysis module 13 are determined according to failure principle, fault case Other failure causes corresponding with the fault message, and be ranked up (step S307) according to possibility, and then referring again to number According to module, other handbooks carry out troubleshooting (step S308);Judge whether troubleshooting is successful (step S309), if success, thens follow the steps S304, output show the information of faulty equipment, and record the relevant information (step S305) of troubleshooting, until terminating (step S306)。
Data in data memory module 12 above-mentioned are originated from the relevant servicing manual of aircraft, fault case, history row Therefore statistic record etc..For example, for the data from servicing manual, can using failure code as major key, with failure code come Failure is indicated, and each attribute, including the affiliated section number information of failure, failure-description letter are added for the failure in Mishap Database Breath, fault harm class information, fault reason information etc..Therefore, when user obtains failure cause based on above-mentioned diagnostic system When, it can rapidly obtain the flow of troubleshooting.
The invention also provides a kind of method for diagnosing faults, including:I. at least one fault message is received;Ii. being based on should At least one fault message determines corresponding at least one failure cause, and arranges at least one failure cause Sequence;Iii. the sequence based on fixed at least one failure cause, determines troubleshooting flow.
For example, when receiving a plurality of fault message, failure analysis module 13 to the failure cause of input fault information into Row comparative analysis, for example, failure cause and danger classes to input fault are compared analysis.
At this point, for step ii comprising:When the number of the fault message is more than one, compare and the fault message Corresponding failure cause, and determine the degree of overlapping and/or danger classes of the failure cause, based on the degree of overlapping and/or danger etc. Grade, is ranked up the failure cause and determines corresponding troubleshooting flow.Then, user can need the event with degree of overlapping sequence Hinder reason troubleshooting, or troubleshooting is preferentially carried out by high-grade failure.
When single failure information corresponds to single failure reason, based on the data in the Maintenance plan to the failure cause Carry out troubleshooting;If troubleshooting is unsuccessful, failure original is determined based on the corresponding fault case of the fault message and/or failure principle Cause and corresponding troubleshooting flow.
Preferably, when the single fault message corresponds to multiple failure causes, multiple failure cause is arranged successively Therefore or optimized according to the troubleshooting determined by the corresponding fault case of the fault message, history troubleshooting statistic record and failure principle Flow carries out troubleshooting;If troubleshooting is unsuccessful, according to based on the corresponding other fault cases of the fault message and/or failure Principle determines failure cause and corresponding troubleshooting flow.
By using technical scheme of the present invention, there can be following advantageous effects:
1. improving the efficiency of airplane fault diagnosis
The troubleshooting work of airline is carried out mainly in accordance with troubleshooting handbook.Have at present with the relevant handbook of aeronautical maintenance tens of A large amount of engineering technical document is also consulted while planting, and consult handbook, this gives brings larger difficulty according to the troubleshooting of handbook Degree, the present invention are mutually tied by based on handbook, taking into account the historical statistical data of system with other method for diagnosing faults It closes, applied mathematics tool, realizes high-grade intelligent diagnosis, can effectively solve traditional handbook troubleshooting and case troubleshooting mode takes Long, heavy workload and fault location inaccuracy situation, airline Maintenance Engineer can quickly arrange in positioning failure reason, raising Therefore efficiency.
2. reducing the flight delay brought by fault diagnosis
The present invention can help airline maintenance personnel to judge to generate the possible cause of failure, quickly navigate to corresponding event Phragma further according to isolation program validation and is debugged, from program to improve the accuracy and working efficiency of troubleshooting, Ke Yiji The flight percent of punctuality of big raising airline.
3. aircraft maintenance cost can be effectively reduced
It will be an effective way for saving maintenance cost to provide repair level and troubleshooting efficiency unquestionably.The present invention can Fault solution is quickly and accurately found by handbook chained technology, to improve lower troubleshooting under traditional troubleshooting mode Efficiency achievees the purpose that be substantially reduced aircraft maintenance and operation cost.
The above description of the disclosure is for enabling any those of ordinary skill of this field to realize or use the present invention.It is right For those of ordinary skill in the art, the various modifications of the disclosure will be apparent from, and generality defined herein Principle can also be applied to other deformations in the case of without deviating from the spirit and scope of the disclosed invention.Therefore, the present invention is simultaneously It is not limited to example as described herein and design, but it is consistent with the widest scope of principle disclosed herein and novel features.

Claims (11)

1. a kind of method for diagnosing faults, including:
I. at least one fault message is received;
Ii. it is based at least one fault message, determines corresponding at least one failure cause, and to described at least one A failure cause is ranked up;
Iii. the sequence based on fixed at least one failure cause, determines troubleshooting flow,
Further include in wherein step ii:
Based at least one fault message and its corresponding fault case, history troubleshooting statistic record and failure principle, Determine at least one failure cause.
2. the method as described in claim 1, which is characterized in that further include in the step ii:
When the number of the fault message is more than one, compare failure cause corresponding with the fault message, and determine institute The degree of overlapping and/or danger classes of failure cause are stated, the failure cause is carried out based on the degree of overlapping and/or danger classes It sorts and determines corresponding troubleshooting flow.
3. the method as described in claim 1, which is characterized in that when single failure information corresponds to single failure reason, be based on Data in Maintenance plan carry out troubleshooting to the failure cause;
If troubleshooting is unsuccessful, failure cause is determined based on the corresponding fault case of the fault message and/or failure principle And corresponding troubleshooting flow.
4. the method as described in claim 1, which is characterized in that when the single fault message corresponds to multiple failure causes,
Troubleshooting is carried out successively to the multiple failure cause, or according to by the corresponding fault case of the fault message, history row Therefore the statistic record and failure principle troubleshooting Optimizing Flow that determines carries out troubleshooting;
If troubleshooting is unsuccessful, basis is based on the corresponding other fault cases of the fault message and/or failure principle come really Determine failure cause and corresponding troubleshooting flow.
5. method as claimed in claim 4, which is characterized in that the troubleshooting Optimizing Flow is determined by following steps:
Different power is assigned respectively to the corresponding fault case of the fault message, history troubleshooting statistic record and failure principle Then weight determines failure cause corresponding with the fault message and corresponding troubleshooting flow.
6. method as claimed in claim 5, which is characterized in that the fault case, history troubleshooting statistic record and failure are former The weight of reason is respectively 0.3,0.5 and 0.2.
7. the method as described in claim 1, which is characterized in that
If troubleshooting success, it is determined that the failure cause, and record information associated with the failure cause.
8. a kind of fault diagnosis system, including:
Input module, for receiving at least one fault message;
Data memory module, for storing failure cause corresponding with fault message and corresponding troubleshooting method;
Failure analysis module is communicated to connect with the input module, is configured as being based at least one fault message, really Fixed corresponding at least one failure cause, and at least one failure cause is ranked up, to determine troubleshooting flow,
The wherein described failure analysis module is additionally configured to:
Based on fault case corresponding at least one fault message, history troubleshooting statistic record and failure principle, determine At least one failure cause.
9. system as claimed in claim 8, which is characterized in that the failure analysis module is additionally configured to:
When the number of the fault message is more than one, compare failure cause corresponding with the fault message, and determine institute The degree of overlapping and/or danger classes of failure cause are stated, the failure cause is carried out based on the degree of overlapping and/or danger classes Sequence.
10. system as claimed in claim 8, which is characterized in that
If a fault message only corresponds to a failure cause in Maintenance plan, based in the Maintenance plan Data to the failure cause carry out troubleshooting;
If a fault message corresponds to multiple failure causes in Maintenance plan, successively to the multiple failure cause Troubleshooting is carried out, or row is determined based on by the corresponding fault case of the fault message, history troubleshooting statistic record and failure principle Therefore Optimizing Flow, and carry out troubleshooting;
If troubleshooting is unsuccessful, failure cause is determined based on the corresponding fault case of the fault message and/or failure principle And corresponding troubleshooting flow.
11. system as claimed in claim 10, which is characterized in that the troubleshooting Optimizing Flow is determined by following steps:
Different power is assigned respectively to the corresponding fault case of the fault message, history troubleshooting statistic record and failure principle Then weight determines failure cause corresponding with the fault message and corresponding troubleshooting flow.
CN201510154810.7A 2015-04-02 2015-04-02 Method for diagnosing faults and fault diagnosis system based on repair class data Active CN106155035B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN201510154810.7A CN106155035B (en) 2015-04-02 2015-04-02 Method for diagnosing faults and fault diagnosis system based on repair class data

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN201510154810.7A CN106155035B (en) 2015-04-02 2015-04-02 Method for diagnosing faults and fault diagnosis system based on repair class data

Publications (2)

Publication Number Publication Date
CN106155035A CN106155035A (en) 2016-11-23
CN106155035B true CN106155035B (en) 2018-09-07

Family

ID=57338463

Family Applications (1)

Application Number Title Priority Date Filing Date
CN201510154810.7A Active CN106155035B (en) 2015-04-02 2015-04-02 Method for diagnosing faults and fault diagnosis system based on repair class data

Country Status (1)

Country Link
CN (1) CN106155035B (en)

Families Citing this family (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN106789243B (en) * 2016-12-22 2019-06-14 烟台东方纵横科技股份有限公司 A kind of IT operational system with intelligent trouble analytic function
CN107590541A (en) * 2017-08-04 2018-01-16 国网浙江省电力公司 A kind of field treatment method of load data collection success rate low defect
CN107516414A (en) * 2017-08-21 2017-12-26 中国电力科学研究院 A kind of power information acquisition system Analysis on Fault Diagnosis method and system
CN109558220B (en) * 2017-09-26 2021-02-05 汉海信息技术(上海)有限公司 Management method and equipment for fault vehicle
CN109284841A (en) * 2018-11-16 2019-01-29 四川长虹电器股份有限公司 Household electrical appliances fault diagnosis system based on history mantenance data
CN109592525A (en) * 2018-12-07 2019-04-09 上海辛格林纳新时达电机有限公司 Elevator frequency converter fault diagnosis system and method
CN110221592A (en) * 2019-05-30 2019-09-10 北京博锐尚格节能技术股份有限公司 Build functional failure of electromechanical diagnostic method, apparatus and system

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6785636B1 (en) * 1999-05-14 2004-08-31 Siemens Corporate Research, Inc. Fault diagnosis in a complex system, such as a nuclear plant, using probabilistic reasoning
CN102012697A (en) * 2010-09-21 2011-04-13 三一重工股份有限公司 Engineering machinery and intelligent fault treatment method and system thereof
CN102819239A (en) * 2011-06-08 2012-12-12 同济大学 Intelligent fault diagnosis method of numerical control machine tool
CN103914058A (en) * 2012-12-29 2014-07-09 上海可鲁系统软件有限公司 Fault diagnosis and alarm method and system for oil-gas pipeline industrial control equipment remote monitoring system
CN104077483A (en) * 2014-06-27 2014-10-01 南京理工大学 Determining method of overall influence degrees of failure modes and failure causes of urban rail vehicle components

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6785636B1 (en) * 1999-05-14 2004-08-31 Siemens Corporate Research, Inc. Fault diagnosis in a complex system, such as a nuclear plant, using probabilistic reasoning
CN102012697A (en) * 2010-09-21 2011-04-13 三一重工股份有限公司 Engineering machinery and intelligent fault treatment method and system thereof
CN102819239A (en) * 2011-06-08 2012-12-12 同济大学 Intelligent fault diagnosis method of numerical control machine tool
CN103914058A (en) * 2012-12-29 2014-07-09 上海可鲁系统软件有限公司 Fault diagnosis and alarm method and system for oil-gas pipeline industrial control equipment remote monitoring system
CN104077483A (en) * 2014-06-27 2014-10-01 南京理工大学 Determining method of overall influence degrees of failure modes and failure causes of urban rail vehicle components

Also Published As

Publication number Publication date
CN106155035A (en) 2016-11-23

Similar Documents

Publication Publication Date Title
CN105223843B (en) A kind of re-entry space vehicle combination property checking system based on data sharing
CN105721193B (en) System information monitoring method and device
RU2675728C2 (en) Method and device for implementing testing process of rail vehicle
CN106844775B (en) Spacecraft fault rapid detection system
US7522978B2 (en) Method and device of generating logic control units for railroad station-based vital computer apparatuses
EP0570513B1 (en) Maintenance apparatus and method initiated by a hierarchical distributed knowledge based machine
CN100456191C (en) Satellite automatization test platform and test method
CN102879680B (en) The general detection of rail transit vehicle equipment and method for diagnosing faults and system
US4766595A (en) Fault diagnostic system incorporating behavior models
US6615367B1 (en) Method and apparatus for diagnosing difficult to diagnose faults in a complex system
Kitchenham et al. The SQUID approach to defining a quality model
CA1336206C (en) Diagnostic expert system
CN100554980C (en) Be used for supporting the method for the fault functional unit of recognology device
US7350106B2 (en) Device for aiding the locating of failure of a complex system
CN102591318B (en) Process for service diagnostic and service procedures enhancement
US8566139B2 (en) Method for deterministic safety analysis in non-stationary high risk system, control method and control system using thereof
Deb et al. QSI's integrated diagnostics toolset
WO2016077997A1 (en) Wind turbine condition monitoring method and system
Čepin DEPEND-HRA—A method for consideration of dependency in human reliability analysis
US8996235B2 (en) Repair assist system for vehicle servicing
US7702435B2 (en) Method and apparatus for system monitoring and maintenance
CN103699111B (en) The fault detection method of distributed monitoring system and device
CN102096760B (en) Detecting anomalies in field failure data
CN103473710A (en) Graded handling method for faults of centralized operation and maintenance systems
EP2064106A1 (en) Diagnostic system and method for monitoring a rail system

Legal Events

Date Code Title Description
C06 Publication
PB01 Publication
C10 Entry into substantive examination
SE01 Entry into force of request for substantive examination
GR01 Patent grant
GR01 Patent grant