ARINC 672-2008 GUIDELINES FOR THE REDUCTION OF NO FAULT FOUND (NFF)《无故障发现的减少指南(NFF)》.pdf

《ARINC 672-2008 GUIDELINES FOR THE REDUCTION OF NO FAULT FOUND (NFF)《无故障发现的减少指南(NFF)》.pdf》由会员分享，可在线阅读，更多相关《ARINC 672-2008 GUIDELINES FOR THE REDUCTION OF NO FAULT FOUND (NFF)《无故障发现的减少指南(NFF)》.pdf（52页珍藏版）》请在麦多课文档分享上搜索。

1、 AN DOCUMENT Prepared by AEEC Published by AERONAUTICAL RADIO, INC. 2551 RIVA ROAD, ANNAPOLIS, MARYLAND 21401-7435 GUIDELINES FOR THE REDUCTION OF NO FAULT FOUND (NFF) ARINC REPORT 672 PUBLISHED: June 9, 2008 This document is published information as defined by 15 CFR Section 734.7 of the Export Adm

2、inistration Regulations (EAR). As publicly available technology under 15 CFR 74.3(b)(3), it is not subject to the EAR and does not have an ECCN. It may be exported without an export license. DISCLAIMER THIS DOCUMENT IS BASED ON MATERIAL SUBMITTED BY VARIOUS PARTICIPANTS DURING THE DRAFTING PROCESS.

3、NEITHER AMC NOR ARINC HAS MADE ANY DETERMINATION WHETHER THESE MATERIALS COULD BE SUBJECT TO VALID CLAIMS OF PATENT, COPYRIGHT OR OTHER PROPRIETARY RIGHTS BY THIRD PARTIES, AND NO REPRESENTATION OR WARRANTY, EXPRESS OR IMPLIED, IS MADE IN THIS REGARD. ARINC INDUSTRY ACTIVITIES USES REASONABLE EFFORT

4、S TO DEVELOP AND MAINTAIN THESE DOCUMENTS. HOWEVER, NO CERTIFICATION OR WARRANTY IS MADE AS TO THE TECHNICAL ACCURACY OR SUFFICIENCY OF THE DOCUMENTS, THE ADEQUACY, MERCHANTABILITY, FITNESS FOR INTENDED PURPOSE OR SAFETY OF ANY PRODUCTS, COMPONENTS, OR SYSTEMS DESIGNED, TESTED, RATED, INSTALLED OR O

5、PERATED IN ACCORDANCE WITH ANY ASPECT OF THIS DOCUMENT OR THE ABSENCE OF RISK OR HAZARD ASSOCIATED WITH SUCH PRODUCTS, COMPONENTS, OR SYSTEMS. THE USER OF THIS DOCUMENT ACKNOWLEDGES THAT IT SHALL BE SOLELY RESPONSIBLE FOR ANY LOSS, CLAIM OR DAMAGE THAT IT MAY INCUR IN CONNECTION WITH ITS USE OF OR R

6、ELIANCE ON THIS DOCUMENT, AND SHALL HOLD ARINC, AMC, AND ANY PARTY THAT PARTICIPATED IN THE DRAFTING OF THE DOCUMENT HARMLESS AGAINST ANY CLAIM ARISING FROM ITS USE OF THE STANDARD. THE USE IN THIS DOCUMENT OF ANY TERM, SUCH AS SHALL OR MUST, IS NOT INTENDED TO AFFECT THE STATUS OF THIS DOCUMENT AS

7、A VOLUNTARY STANDARD OR IN ANY WAY TO MODIFY THE ABOVE DISCLAIMER. NOTHING HEREIN SHALL BE DEEMED TO REQUIRE ANY PROVIDER OF EQUIPMENT TO INCORPORATE ANY ELEMENT OF THIS STANDARD IN ITS PRODUCT. HOWEVER, VENDORS WHICH REPRESENT THAT THEIR PRODUCTS ARE COMPLIANT WITH THIS STANDARD SHALL BE DEEMED ALS

8、O TO HAVE REPRESENTED THAT THEIR PRODUCTS CONTAIN OR CONFORM TO THE FEATURES THAT ARE DESCRIBED AS MUST OR SHALL IN THE STANDARD. ANY USE OF OR RELIANCE ON THIS DOCUMENT SHALL CONSTITUTE AN ACCEPTANCE THEREOF “AS IS” AND BE SUBJECT TO THIS DISCLAIMER. 2008 BY AERONAUTICAL RADIO, INC. 2551 RIVA ROAD

9、ANNAPOLIS, MARYLAND 21401-7435 USA Prepared by the AMC Report 672 Adopted by the AMC Steering Group April 13, 2008 ARINC REPORT 672 GUIDELINES FOR THE REDUCTION OF NO FAULT FOUND (NFF) Published: June 9, 2008ii FOREWORD Aeronautical Radio, Inc., the AMC, and ARINC Standards ARINC organizes aviation

10、industry committees and participates in related industry activities that benefit aviation at large by providing technical leadership and guidance. These activities directly support aviation industry goals: promote safety, efficiency, regularity, and cost-effectiveness in aircraft operations. ARINC I

11、ndustry Activities organizes and provides the secretariat for international aviation organizations (AEEC, AMC, FSEMC) which coordinate the work of aviation industry technical professionals and lead the development of technical standards for airborne electronic equipment, aircraft maintenance equipme

12、nt and practices and flight simulator equipment and used in commercial, military, and business aviation. The AEEC, AMC, and FSEMC develop consensus-based, voluntary standards that are published by ARINC and are known as ARINC Standards. The use of ARINC Standards results in substantial benefits to t

13、he aviation industry by allowing avionics interchangeability and commonality and reducing avionics cost by promoting competition. There are three classes of ARINC Standards: a) ARINC Characteristics Define the form, fit, function, and interfaces of avionics and other airline electronic equipment. AR

14、INC Characteristics indicate to prospective manufacturers of airline electronic equipment the considered and coordinated opinion of the airline technical community concerning the requisites of new equipment including standardized physical and electrical characteristics to foster interchangeability a

15、nd competition. b) ARINC Specifications Are principally used to define either the physical packaging or mounting of avionics equipment, data communication standards, or a high-level computer language. c) ARINC Reports Provide guidelines or general information found by the airlines to be good practic

16、es, often related to avionics maintenance and support. The release of an ARINC Standard does not obligate any organization or ARINC to purchase equipment so described, nor does it establish or indicate recognition or the existence of an operational requirement for such equipment, nor does it constit

17、ute endorsement of any manufacturers product designed or built to meet the ARINC Standard. In order to facilitate the continuous product improvement of this ARINC Standard, two items are included in the back of this volume: An Errata Report solicits any corrections to the text or diagrams in this AR

18、INC Standard. An ARINC IA Project Initiation/Modification (APIM) form solicits any recommendations for addition of substantive material to this volume which would be the subject of a new Supplement. ARINC REPORT 672 TABLE OF CONTENTS iii1.0 INTRODUCTION .1 1.1 Goals .1 1.2 Users of this Document1 1.

19、3 Document Overview.2 1.4 Related Documents .3 2.0 OVERVIEW .4 2.1 Overview of NFF Sources4 2.2 Overview of Recommended Action6 3.0 NFF REDUCTION PROCESS .9 3.1 Establish Potential NFF Candidate 11 3.1.1 Maintenance Event Data.11 3.1.2 Establish Maintenance NFF Criteria11 3.1.3 Assess Maintenance Ev

20、ent Data.11 3.1.4 Identify NFF Candidate .12 3.1.5 NFF Candidate12 3.2 Establish the Most-likely NFF Source 12 3.2.1 Establish NFF Source/Cause Selection Criteria 12 3.2.2 Establish Possible NFF Source/Cause for NFF Candidate12 3.2.3 Determine Most-likely NFF Source(s)12 3.2.4 Most-likely NFF Source

21、(s).12 3.3 Select an Appropriate Solution.12 3.3.1 Establish Solution Selection Criteria12 3.3.2 Generate Possible Solution(s).12 3.3.3 Select Preferred Solution(s) 12 3.3.4 Preferred Solution(s) .13 3.4 Implement Preferred Solution(s) 13 APPENDIX A DESCRIPTION OF NFF SOURCES/ CAUSES14 A-1 Design/Pr

22、oduction .14 A-1.1 Documentation14 A-1.2 Communication .14 A-1.3 Training.14 A-1.4 Testing 15 A-1.5 Systems and Components 15 A-2 Flight Operations .16 A-2.1 Documentation16 A-2.2 Communication .16 A-2.3 Training.16 A-2.4 Testing 16 A-2.5 Systems and Components 17 A-3 Line Operations .17 A-3.1 Docum

23、entation17 A-3.2 Communication .17 A-3.3 Training.18 A-3.4 Testing 18 A-3.5 Systems and Components 19 A-4 Shop Operations19 A-4.1 Documentation19 A-4.2 Communication .20 A-4.3 Training.20 TABLE OF CONTENTS ARINC REPORT 672 iv A-4.4 Testing 20 A-4.5 Systems and Components 20 APPENDIX B DESCRIPTION OF

24、 RECOMMENDED ACTIONS FOR NFF REDUCTION 21 B-1 Design/Production .21 B-1.1 Documentation21 B-1.2 Communication .21 B-1.3 Training.22 B-1.4 Testing 22 B-1.5 Systems and Components 22 B-2 Flight Operations .23 B-2.1 Documentation23 B-2.2 Communication .23 B-2.3 Training.24 B-2.4 Testing 24 B-2.5 System

25、s and Components 24 B-3 Line Operations .24 B-3.1 Documentation24 B-3.2 Communication .25 B-3.3 Training.26 B-3.4 Testing 26 B-3.5 Systems and Components 26 B-4 Shop Operations27 B-4.1 Documentation27 B-4.2 Communication .27 B-4.3 Training.28 B-4.4 Testing 28 B-4.5 Systems and Components 29 APPENDIX

26、 C GLOSSARY OF TERMS30 APPENDIX D ACRONYMS33 APPENDIX E EXAMPLES/CASE STUDIES 34 E-1 Example/Case Study for Shop Operations.34 E-2 Example/Case Study of OEM Chronic Process38 E-2.1 Introduction .38 E-2.2 Description38 E-2.3 Technical Conclusion 39 E-2.4 Chronic Unit Investigation Form 39 E-2.5 Chron

27、ic Unit Process Manager40 E-3 Example/Case Study of Quarantine Process .40 E-3.1 Introduction .40 E-3.2 Definition.40 E-3.3 Outline of the Situation/ Describing the Problem .40 E-4 Example/Case Study of a Mind Map to Illustrate NFF Structuring42 ARINC Errata Report ARINC IA Project Initiation/Modifi

28、cation (APIM) ARINC REPORT 672 - Page 1 1.0 INTRODUCTION 1.0 INTRODUCTION Removals of equipment from service for reasons that cannot be verified by the maintenance process (shop or elsewhere) are a significant burden for aircraft operators. This phenomenon is commonly referred to as No Fault Found (

29、NFF). Many other industry guidelines have been created in the past addressing NFF. NFF is often perceived as a shop-only problem or an individual component reliability problem. This is not true. NFF solutions require an inter-disciplinary effort to identify the true causes and implement successful s

30、olutions. This document describes the most common sources of NFF and provides guidance to develop appropriate solutions. The sources of NFF are spread throughout the following four domains: Design/Production Flight operations Line operations Shop operations This report provides a holistic view of th

31、e NFF problem based on the above domains and the following categories: Documentation Communication Training Testing System/Components design Complete elimination of NFF is not a realistic expectation. However, a structured approach will help toward minimizing the effects of NFF. 1.1 Goals The goal o

32、f this document is to provide the basis for a structured process to identify, analyze and resolve NFF issues, including: Providing guidance for decision making pertinent to the root causes of NFF. Enabling action in an early stage of the component repair cycle. Reducing costs involved with units unn

33、ecessarily removed from an aircraft (e.g. maintenance practices, operational factors, training, documentation etc.). Highlighting the need for addressing the causes of NFF through component and system design. Addressing the development/improvement of maintenance processes. Providing a framework for

34、the interaction between the different domains for the users of this document (listed below) to implement their own strategies. 1.2 Users of this Document This document is intended for use by the following organizations: ARINC REPORT 672 - Page 2 1.0 INTRODUCTION Product support Aircraft manufacturer

35、s Equipment suppliers Aircraft operators Maintenance organizations Flight operations Fleet engineering and anybody else interested! 1.3 Document Overview The document comprises the following sections: 1. Section 1 presents an overview of the document contents. 2. Section 2 provides two tables to sup

36、port NFF identification and potential solutions. Possible sources of NFF and corresponding recommended actions are evident from Tables 2-1 and 2-2 for identified domains and categories. 3. Section 3 describes a generic NFF reduction process. Appendices A and B provide supporting details to Tables 2-

37、1 and 2-2: Appendix A: Description of Possible NFF Sources Appendix B: Description of Recommended Action Figure 1.3-1 depicts the document arrangement and how to use it. If an NFF problem is experienced look up the possible cause/source in Table 2-1, which summarizes possible causes/sources of NFF g

38、rouped into a matrix of Domains versus Categories. Note that the table shows a generic view of the NFF scenario, without any interactions across domain boundaries. To find an appropriate solution look up possible solutions in Table 2-2 in the corresponding matrix reference. Select most suitable solu

39、tion(s) Refer to Figure 3-1 for a generic process view of reducing NFF, which should be customised for in-house use. The intent of the document is not to provide quick fixes/solutions. A certain measure of customization and tailoring is required to adapt it to a specific situation experienced by a s

40、pecific user. The document does not intend to be a recipe. It is a guideline to be applied with judgment. Examples of implemented processes are attached to the document to illustrate strategies of reducing NFF. This document covers NFF issues for the system life-cycle, i.e. from design to operation.

41、 ARINC REPORT 672 - Page 3 1.0 INTRODUCTION CategoryTable 2-1 NFF Sources/ CausesTable 2-2 Recommended ActionsDomainDomainCategoryProcess Application(Section 3)Figure 1.3-1 Document Arrangement 1.4 Related Documents ARINC Report 431: No Fault Found A Case Study ARINC Report 625-2: Industry Guide for

42、 Component Test Development and Management ARINC Report 640: Resolution of In-service Anomalies through ASAPP ARINC Report 663: Data Requirements for Avionics Component Maintenance ATA Specification 109: No Fault Found ATA Spec 2000: E-Business Specification for Material Management ATA iSpec 2200: I

43、nformation Standards for Aviation Maintenance IATA No Fault Found Working Group Report December 1997 ARINC REPORT 672 - Page 4 2.0 OVERVIEW 2.0 OVERVIEW This section provides two tables to support NFF identification and potential solutions: Table 2-1 presents NFF sources Table 2-2 presents the recom

44、mended actions 2.1 Overview of NFF Sources Table 2-1 depicts a cross listing of domains and categories involved in the resolution of an NFF issue. The table should be interpreted as a check list for reviewing items within the Domain named in the columns, i.e. Design/Production, Flight Operations, Li

45、ne Operations, Shop Operations and the Category named in the rows, i.e. Documentation, Communication, Training, Testing, and System/Components. Each domain can involve several different role-players. The list of role-players is not exhaustive and can be appended for a particular situation, e.g. fiel

46、d engineers, fleet engineering, reliability engineering, etc. Each bullet represents possible source(s)/causes(s) that a particular role-player may experience within a particular category and domain. Detailed descriptions of the table entries are presented in Appendix A of the document. The table do

47、es not represent a solution. Recommended actions are summarized in Table 2-2. ARINC REPORT 672 - Page 5 2.0 OVERVIEW Table 2-1 Summary of NFF Sources/Causes for Domain versus Category Matrix Refer to Appendix A for a more detailed description of the NFF Sources/Causes summarised in the table below.

48、Domain Design/Production Flight Operations Line Operations Shop Operations Documentation Inadequate design/production documentation Misleading/incomplete documentation, processes and procedures Unclear reporting in Logbook Unaware of available documentation from aircraft manufacturer Deficiencies in

49、: Aircraft Maintenance Manual (AMM) Troubleshooting Manual (TSM)/Fault Isolation Manual (FIM) Component Built-In Test Equipment (BITE) users manual (considered to be part of TSM/FIM) Logbook entries Repair history keeping Configuration management Deficiencies in awareness of sources and available documentation, e.g. Aircraft Manufacturer, OEM, Supplier, Operators Deficiencies in: Built-In Test Equipment (BITE) decoding information in CMM Component Maintenance Manual (CMM) Mul