ARMY MIL-STD-40051-3 B CHANGE 2-2006 TECHNICAL MANUALS TROUBLESHOOTING PROCEDURES《故障排除程序的技术手册》.pdf

《ARMY MIL-STD-40051-3 B CHANGE 2-2006 TECHNICAL MANUALS TROUBLESHOOTING PROCEDURES《故障排除程序的技术手册》.pdf》由会员分享，可在线阅读，更多相关《ARMY MIL-STD-40051-3 B CHANGE 2-2006 TECHNICAL MANUALS TROUBLESHOOTING PROCEDURES《故障排除程序的技术手册》.pdf（26页珍藏版）》请在麦多课文档分享上搜索。

1、 MIL-STD-40051-3B(TM) w/CHANGE 212 MAY 2006 SUPERSEDING MIL-STD-40051-3B(TM) w/CHANGE 130 NOVEMBER 2003 DEPARTMENT OF DEFENSE STANDARD PRACTICE TECHNICAL MANUALS TROUBLESHOOTING PROCEDURES AMCS A7329 AREA TMSS DISTRIBUTION STATEMENT A. Approved for public release; distribution is unlimited. NOT MEAS

2、UREMENT SENSTIVE Provided by IHSNot for ResaleNo reproduction or networking permitted without license from IHS-,-,-MIL-STD-40051-3B(TM)CONTENTSPARAGRAPH PAGEii1. SCOPE11.1 Scope.12. APPLICABLE DOCUMENTS13. DEFINITIONS.14. GENERAL REQUIREMENTS.14.1 General14.2 Development of troubleshooting instructi

3、ons14.3 Maintenance level applicability14.4 Depot maintenance work requirements (DMWR) and National maintenancework requirements (NMWR)24.5 Preparation of digital data for electronic delivery.24.6 Use of DTDs/XSLs24.6.1 Page-based TMs.24.6.2 Frame-based TMs 24.7 Content structure and format24.8 Styl

4、e and format.24.9 Work package development .24.10 Safety devices and interlocks24.11 Electrostatic discharge (ESD) sensitive parts34.12 Nuclear hardness34.13 Selective application and tailoring35. DETAILED REQUIREMENTS35.1 Testing and troubleshooting philosophy.35.1.1 Methods of testing and troubles

5、hooting45.1.1.1 Manual (nonautomatic) troubleshooting.45.1.1.2 Semi-automatic or automatic testing and troubleshooting.45.1.1.3 Testing and troubleshooting using built-in-test equipment45.1.2 Types of testing and troubleshooting information.45.1.2.1 Fault reporting/fault isolation information (aircr

6、aft and major weaponsystems).45.1.2.2 Integrated system testing and troubleshooting (aircraft and major weaponsystems).55.1.2.2.1 Integrated systems having self-test or built-in test capability55.1.2.2.2 Integrated systems requiring the use of system peculiar test sets.55.1.2.2.3 Integrated systems

7、requiring the use of common test equipment.55.2 Troubleshooting procedures content.55.3 Testing and troubleshooting work packages.65.3.1 Work package content75.3.2 Introduction work package (Aircraft Troubleshooting TMs only) 7Provided by IHSNot for ResaleNo reproduction or networking permitted with

8、out license from IHS-,-,-MIL-STD-40051-3B(TM)CONTENTSPARAGRAPH PAGEiii5.3.3 Types of testing and troubleshooting work packages75.3.3.1 Examples of required testing and troubleshooting work packages.75.3.3.2 Troubleshooting index work package 75.3.3.2.1 Malfunction/symptom index 75.3.3.2.2 System/sub

9、system index 85.3.3.3 Preshop analysis work package (DMWR/NMWR only) 85.3.3.3.1 Preshop analysis procedures (DMWR/NMWR only) .85.3.3.4 Component checklist work package (DMWR/NMWR only)95.3.3.4.1 Introduction .95.3.3.4.2 Component checklist 95.3.3.5 Technical description work packages (page-based Air

10、craftTroubleshooting Manuals only)105.3.3.6 Operational checkout and troubleshooting procedures work packages105.3.3.6.1 Operational checkout and troubleshooting procedures content105.3.3.6.2 Operational checkout and troubleshooting procedure work packagedevelopment.115.3.3.6.3 Operational checkout

11、work package (page-based TMs only) .115.3.3.6.4 Troubleshooting work package (page-based TMs only) .125.3.3.6.5 Combined operational checkout and troubleshooting work package.135.3.3.6.6 Integrated system troubleshooting procedures work packages 146. NOTES.15Provided by IHSNot for ResaleNo reproduct

12、ion or networking permitted without license from IHS-,-,-MIL-STD-40051-3B(TM)CONTENTSFIGURE PAGEivFIGURE 1. Example of a cover sheet/frame for preshop analysis checklist 16FIGURE 2. Example of a component checklist 17FIGURE 3. Example of content for an operational checkout procedure18FIGURE 4. Examp

13、le of content for a troubleshooting procedure (Method A).19FIGURE 5. Example of content for a troubleshooting procedure (Method B).20FIGURE 6. Example of content for a troubleshooting procedure (Method C).21FIGURE 7. Example ofcontent for a combination testing and troubleshooting procedure22Provided

14、 by IHSNot for ResaleNo reproduction or networking permitted without license from IHS-,-,-MIL-STD-40051-3B(TM)11. SCOPE.1.1 Scope. This standard establishes the technical content requirements for the preparation oftroubleshooting procedures for major weapon systems, and their related systems, subsys

15、tems,equipment, weapons replacement assemblies (WRAs), and shop replacement assemblies (SRAs).The requirements are applicable for all maintenance levels through overhaul (depot) includingDepot Maintenance Work Requirements (DMWRs) and National Maintenance WorkRequirements (NMWRs). The requirements c

16、an be used to develop TMs in a variety of outputforms including interactive screen presentations (frame-based manuals) and paper (paged-basedmanuals).2. APPLICABLE DOCUMENTS.The applicable documents in section 2 of MIL-STD-40051 apply to this Part.3. DEFINITIONS.The definitions in section 3 of MIL-S

17、TD-40051 apply to this Part.4. GENERAL REQUIREMENTS.4.1 General. Troubleshooting procedures shall be prepared for weapon systems, majorequipment, components, and applicable support and interface equipment. Troubleshootingprocedures and supporting illustrations shall be prepared so that operator/crew

18、 and maintenancepersonnel can perform all required operator through depot level (overhaul) troubleshooting.4.2 Development oftroubleshooting instructions. Troubleshooting instructions shall cover allitems comprising the weapon system/equipment, such as assemblies, subassemblies,components, wiring, j

19、unction boxes, and accessories. Troubleshooting procedures shall isolatefaults to the part(s) authorized by the RPSTL for repair or replacement at the maintenance leveladdressed. Tasks shall be presented in the order in which they are performed. ApprovedLogistics Management Information (LMI), and se

20、rvice experience, performance data on similarequipment, and all other reliability, maintainability, and supportability (RMS) and operationalavailability (Ao) data available shall be used in the preparation of specific troubleshootingprocedures. Troubleshooting procedures shall begin with testing, ob

21、served problems, a faultsymptom or malfunction and shall diagnose to a single fault/failure. Troubleshooting shall referto specific maintenance or repair tasks to correct the fault. Instructions, where applicable, shallflow from operator level through service/AMC, field/ASB, and below depot sustainm

22、ent untilthe fault is isolated. Procedures shall include schematics and illustrations as needed (or shallreference to required schematics, etc.). Troubleshooting data shall be test and fault-isolationoriented. Troubleshooting instructions shall include detailed inspection and troubleshootinginformat

23、ion. Instructions shall include or reference to functional descriptions of subsystemsbeing diagnosed to aid the operator/technician. The method used for identifying systemequipment test points, including the requirements and methods of determining defects throughvisual inspection, shall be explained

24、.4.3 Maintenance level applicability. Requirements contained in this standard are applicable toall maintenance levels unless specifically noted in bold and in parentheses (i.e.,Field).The labeled requirements shall be applicable to all TMs containing that maintenance level. AnProvided by IHSNot for

25、ResaleNo reproduction or networking permitted without license from IHS-,-,-MIL-STD-40051-3B(TM)2explanation of all applicable Department of Army maintenance levels is provided inMIL-STD-40051, Appendix A.4.4 Depot maintenance work requirements (DMWR) and National maintenance workrequirements (NMWR).

26、 When the acquiring activity specifies that a Depot Maintenance WorkRequirement (DMWR) or National Maintenance Work Requirement (NMWR) shall be preparedto the best commercial practices, the depot requirements contained in this standard shall be usedonly as a guide; therefore, the conforming modular

27、DTD for troubleshooting procedures cannotbe used.4.5 Preparation of digital data for electronic delivery. Technical manual data prepared anddelivered digitally in accordance with this standard shall be Extensible Markup Language (XML)tagged using the Document Type Definition (DTD) for Troubleshootin

28、g Procedures and theXML Stylesheet Language (XSL), or style sheets in accordance with MIL-STD-2361. Refer toMIL-STD-40051 (paragraph 4.6) for information on obtaining or accessing this DTD. XML tagsused in the DTD are noted throughout the text of this standard in bracketed, bold characters (i.e.,) a

29、s a convenience for the TM author and to ensure that the tags are used correctly whendeveloping a document instance.4.6 Use of DTDs/XSLs.4.6.1 Page-based TMs. The DTDs referenced in this standard interpret the technical content andstructure for the functional requirements contained in this standard

30、and are mandatory for use.The XSLs referenced herein interpret the style and format. As specified by the contractingactivity, XSLs, or style sheets may be used to produce final reproducible paper copy for all TMsprepared in accordance with this standard. For additional information on DTDs and specif

31、icXSL or style sheets, refer to MIL-STD-2361.4.6.2 Frame-based TMs. The DTD referenced in this standard interprets the technical contentand structure for the functional requirements contained in this standard and is mandatory for use.Development of TMs is accomplished through the use of the DTD comb

32、ined with therequirements contained in MIL-PRF-87268. The requirements contained in MIL-PRF-87268apply unless they conflict with the requirements in this standard. The requirements in thisstandard take precedence over the requirements contained in MIL-PRF-87268. A style sheet isused to interpret the

33、 style and format for screen display. For additional information on DTDsand specific XSLs or style sheets, refer to MIL-STD-2361.4.7 Content structure and format. The examples provided herein and in MIL-STD-40051 are anaccurate representation of the content structure and format requirements containe

34、d in this Partand shall be followed to permit the effective use of the DTD for Troubleshooting Procedures.4.8 Style and format. MIL-STD-40051, provides style and format requirements for thepreparation of both page-based and TMs. These requirements are considered mandatory and areintended for complia

35、nce.4.9 Work package development. Technical manual data developed in accordance with thisstandard shall be divided into individual, stand alone units of information called work packages.A work package shall consist of descriptive, operational, maintenance, troubleshooting, support,or parts informati

36、on for the weapon systemor equipment.4.10 Safety devices and interlocks. Information shall be prepared pertaining to the purpose andlocation of all safety devices and interlocks in conjunction with the pertinent procedures.Provided by IHSNot for ResaleNo reproduction or networking permitted without

37、license from IHS-,-,-MIL-STD-40051-3B(TM)34.11 Electrostatic discharge (ESD) sensitive parts. If the equipment contains ESD sensitiveparts, components, or circuits, cautions and ESD labels shall be incorporated into the applicabletasks and procedures to ensure ESD sensitive parts are not damaged or

38、degraded duringMaintenance and operation. Refer to MIL-STD-40051 for requirements on labeling with ESD.Actions which could damage ESD sensitive parts, but which are not directly related to handlingor operation of ESD sensitive parts, shall not be annotated with the ESD acronym, but shall bepreceded

39、by a caution statement.4.12 Nuclear hardness. If the weapon system/equipment has nuclear survivability requirements(for example, over pressure and burst, thermal radiation, electromagnetic pulse, or transientradiation effects on electronics), cautions and Hardness-Critical Processes (HCP) labels sha

40、ll beincorporated into the applicable tasks and procedures to ensure the hardness of the equipment isnot degraded during handling or operation. Refer to MIL-STD-40051 for requirements onlabeling with HCP. Actions which could degrade hardness, but which are not directly involvedin establishing nuclea

41、r hardness, shall not be annotated with the acronym, but shall be precededby a caution statement.4.13 Selective application and tailoring. MIL-STD-40051 contains some requirements that maynot be applicable to the preparation of all technical manuals. Selective application and tailoringof requirement

42、s contained in MIL-STD-40051 are the responsibility of the acquiring activity andshall be accomplished using Appendix A, Technical Manual Content Selection Matrixes, ofMIL-STD-40051. The applicability of some requirements is also designated by one of thefollowing statements: unless specified otherwi

43、se by the acquiring activity; as/when specified bythe acquiring activity; or when specified by the acquiring activity.5. DETAILED REQUIREMENTS.5.1 Testing and troubleshooting philosophy. Testing and troubleshooting data shall be developedto the extent required to maintain aircraft and other major we

44、apon systems, equipment,components and support equipment at the authorized maintenance level in accordance with theLogistics Management Information (LMI), Maintenance Allocation Chart (MAC), orMaintenance Plan and the Source, Maintenance, and Recoverability (SMR) codes developed forthe weapon system

45、/equipment. Other factors to be considered in the development oftroubleshooting procedures include, but are not limited to, the following:a. Technical experience (target audience).b. User environment.c. System quick-turnaround requirements.d. Test equipment requirements and availability.e. Automated

46、 versus manual testing.f. Replaceable component and part reliability.g. Ease of testing.h. Test access time.i. Test time.Provided by IHSNot for ResaleNo reproduction or networking permitted without license from IHS-,-,-MIL-STD-40051-3B(TM)4Troubleshooting information shall be provided in combination

47、 with test procedures. This testingand troubleshooting information shall guide the technician, in as practical a manner as possible,to the system, subsystem, equipment, weapons replacement assembly (WRA), shop replacementassembly (SRA), or further to the replaceable part, interconnecting wire, or me

48、chanical linkagewhich caused the malfunction or failure. All information required to perform the tests andevaluate probable malfunctions of the assembled systems or equipment shall be provided.5.1.1 Methods of testing and troubleshooting. The number of interrelated systems, assemblies,subassemblies,

49、 and components, types of equipment, and maintenance plan shall be taken intoconsideration as to the type and depth of testing and troubleshooting instructions to bedeveloped. Based on the complexity of the system or equipment, manual (non-automatic),semi-automatic or automatic testing and troubleshooting methods shall be used. Functionaltesting is usually performed usi