1、MIL-STD-3001-3(AS)15 May 2001SUPERSEDING(See Section 6.)DEPARTMENT OF DEFENSESTANDARD PRACTICEDIGITAL TECHNICAL INFORMATIONFORMULTI-OUTPUT PRESENTATIONOFTECHNICAL MANUALSTESTING AND TROUBLESHOOTING PROCEDURES(PART 3 OF 8 PARTS)AMSC A7194 AREA TMSSDISTRIBUTION STATEMENT A. Approved for public release
2、; distribution is unlimited.NOT MEASUREMENTSENSITIVEProvided by IHSNot for ResaleNo reproduction or networking permitted without license from IHS-,-,-MIL-STD-3001-3(AS) ii FOREWORD 1. This eight-part standard establishes the requirements needed to prepare digital technical information for multi-outp
3、ut presentation of NAVAIR work package Technical Manuals (TMs). The technical content and mandatory style and format requirements contained in this eight-part standard can be used to develop and assemble complete TMs for aircraft weapon systems, aeronautical equipment, airborne weapons/ equipment, a
4、nd support equipment work package technical manuals. The requirements are applicable for the output of paper technical manuals or for the display of page-oriented, scrollable and frame-based technical manuals on an Electronic Display System (EDS). 2. MIL-STD-3001-3 is Part 3 of 8 Parts and is incomp
5、lete without Parts 1, 2 and Parts 4 through 8. Part 3 establishes the technical content requirements for the preparation of testing and troubleshooting procedures for aircraft weapon systems, aeronautical equipment, airborne weapons/equipment, and support equipment. This data can be used to develop
6、TMs in a variety of output forms, including interactive screen presentations and page-based printed manuals. 3. MIL-STD-3001-1 contains general preparation requirements for the multi-output presentation of NAVAIR work package TMs. MIL-STD-3001-2 through MIL-STD-3001-8 contain specific functional tec
7、hnical content requirements for the preparation of all NAVAIR work package TMs and revisions. Parts 1 through 8 are identified below. MIL-STD-3001-1 Preparation of Digital Technical Information for Multi-output Presentation of Technical Manuals. MIL-STD-3001-2 Description, Principles of Operation, a
8、nd Operation Data. MIL-STD-3001-3 Testing and Troubleshooting Procedures. MIL-STD-3001-4 Maintenance Information with IPB. MIL-STD-3001-5 Aircraft Wiring Information. MIL-STD-3001-6 Structural Repair Information. MIL-STD-3001-7 Periodic Maintenance Requirements. MIL-STD-3001-8 Separate Illustrated P
9、arts Breakdown (IPB). 4. MIL-HDBK-3001, Guide to the General Style and Format of U.S. Navy Work Package Technical Manuals, complements this eight-part standard. MIL-HDBK-3001 provides Navy-preferred, nonmandatory style and format requirements for the preparation of page-oriented, scrollable and fram
10、e-based work package technical manuals. 5. Beneficial comments (recommendations, additions, deletions) and any pertinent data which may be of use in improving this document should be addressed to: Commander, Naval Air Warfare Center Aircraft Division, Code 414100B120-3, Highway 547, Lakehurst, NJ 08
11、733-5100 by using the Standardization Document Improvement Proposal (DD Form 1426) appearing at the end of this document or by letter. Provided by IHSNot for ResaleNo reproduction or networking permitted without license from IHS-,-,-MIL-STD-3001-3(AS) CONTENTS PARAGRAPH PAGE iii FOREWORD . ii 1. SCO
12、PE. . 1 1.1 Scope 1 2. APPLICABLE DOCUMENTS. 1 3. DEFINITIONS 1 4. GENERAL REQUIREMENTS 1 4.1 General 1 4.2 Maintenance level applicability 1 4.3 Selective application and tailoring. 1 4.4 Preparation of digital data for electronic delivery 1 4.4.1 Use of the DTDs. 1 4.5 Technical content . 1 4.5.1
13、Work packages . 2 4.5.2 Style and format requirements 2 4.6 Standard tables and lists 2 4.7 Electrostatic discharge (ESD) sensitive equipment 2 4.8 Nuclear hardness . 2 4.9 Ozone depleting substances (ODS) 3 4.10 Special processes . 3 5. DETAILED REQUIREMENTS. 3 5.1 Testing and troubleshooting . 3 5
14、.1.1 Methods of testing and troubleshooting 3 5.1.1.1 Manual (nonautomatic) troubleshooting. 3 5.1.1.2 Semi-automatic or automatic testing and troubleshooting 3 5.1.1.3 Testing and troubleshooting using built-in-test equipment 3 5.1.2 Aircraft and aircraft system operational checkout and troubleshoo
15、ting. 4 5.1.2.1 Fault reporting/fault isolation information. 4 5.1.2.2 Integrated system operational checkout and troubleshooting. 4 5.1.2.2.1 Integrated systems having self-test or built-in test capability 4 5.1.2.2.2 Integrated systems requiring the use of system peculiar test sets . 4 5.1.2.2.3 I
16、ntegrated systems requiring the use of common test equipment 4 5.1.3 Aeronautical equipment, airborne weapons/equipment or support equipment testing and troubleshooting 5 5.1.4 Engine testing and troubleshooting. 5 5.2 Preparation of testing and troubleshooting procedures . 5 5.3 Work package conten
17、t 6 5.3.1 Title block 6 5.3.2 Work package information . 6 5.3.2.1 Reference material list . 6 5.3.2.2 Record of Applicable Technical Directives . 7 Provided by IHSNot for ResaleNo reproduction or networking permitted without license from IHS-,-,-MIL-STD-3001-3(AS) CONTENTS PARAGRAPH PAGE iv 5.3.2.3
18、 Support equipment required list 8 5.3.2.4 Materials required list . 8 5.3.2.5 Additional work package information (ETMs and IETMs only) 9 5.3.3 Required operational checkout, testing and troubleshooting information 9 5.3.4 Aircraft and aircraft systems testing and troubleshooting work packages. 9 5
19、.3.4.1 Maintenance code listing work package (fault reporting manual only) 9 5.3.4.2 Fault indications work package (fault reporting manual only) 10 5.3.4.3 Fault descriptor work package (fault reporting manual only) . 11 5.3.4.4 Symbology work packages (fault reporting manual only) . 11 5.3.4.5 Fau
20、lt isolation troubleshooting procedure work packages (fault isolation manual only) . 11 5.3.4.5.1 Troubleshooting procedure development for fault isolation troubleshooting procedures work packages 11 5.3.4.6 Operational checkout and troubleshooting procedures work packages. 12 5.3.4.6.1 Operational
21、checkout and troubleshooting procedures content . 12 5.3.4.6.2 Operational checkout and troubleshooting procedure work package development . 12 5.3.4.6.3 Operational checkout work package 13 5.3.4.6.4 Troubleshooting work package 13 5.3.4.6.5 Combined operational checkout and troubleshooting work pa
22、ckage . 14 5.3.4.7 Functional flow diagram work packages . 15 5.3.4.7.1 Functional flow diagram technical content requirements 15 5.3.5 Aeronautical equipment, airborne weapons/equipment and support equipment testing and troubleshooting work packages 16 5.3.6 Engine testing and troubleshooting work
23、packages (intermediate and depot maintenance only) 16 5.3.6.1 Engine testing procedures work package 16 5.3.6.2 Engine troubleshooting work package . 19 6. NOTES 20 FIGURES FIGURE 1. Example of content for a fault isolation manual fault isolation troubleshooting procedure 22 FIGURE 2. Example of con
24、tent for an operational checkout procedure. 23 FIGURE 3. Example of content for a trouble shooting procedure (Method A). 25 FIGURE 4. Example of content for a troubleshooting procedure (Method B). 26 FIGURE 5. Example of content for a combination testing and troubleshooting procedure. . 27 Provided
25、by IHSNot for ResaleNo reproduction or networking permitted without license from IHS-,-,-MIL-STD-3001-3(AS) 1 1. SCOPE. 1.1 Scope. This part of the standard establishes the technical content requirements for the preparation of testing and troubleshooting procedures for aircraft weapon systems, aeron
26、autical equipment, airborne weapons/equipment, and support equipment. This data can be used to develop technical manuals (TMs) in a variety of output forms, including interactive screen presentations and page-based, printed manuals. 2. APPLICABLE DOCUMENTS. The applicable documents in section 2 of M
27、IL-STD-3001-1 apply to this Part. 3. DEFINITIONS. The definitions in section 3 of MIL-STD-3001-1 apply to this Part. 4. GENERAL REQUIREMENTS. 4.1 General. Sufficient testing and troubleshooting procedures shall be developed for the aircraft weapon system, aeronautical equipment, airborne weapons/equ
28、ipment or support equipment so that maintenance personnel can perform all authorized operator through depot level testing and troubleshooting. This information shall be contained in Testing and Troubleshooting Information Modules that are subdivided into work packages. 4.2 Maintenance level applicab
29、ility. Requirements contained in this Part are applicable to all types and maintenance levels of TMs unless specifically noted in bold and in parentheses (i.e., Support Equipment Manuals only, Depot Level only, etc.). 4.3 Selective application and tailoring. This Part contains some requirements that
30、 may not be applicable to the preparation of all technical manuals. Selective application and tailoring of requirements contained in this Part shall be accomplished through the use of the Technical Manual Content Selection Matrixes contained in MIL-STD-3001-1, Appendix A. The applicability of some r
31、equirements is also designated by one of the following statements: unless specified otherwise by the requiring activity or as/when specified by the requiring activity. 4.4 Preparation of digital data for electronic delivery. Technical manual data prepared in work package format and delivered digital
32、ly in accordance with this standard shall be SGML-tagged and assembled using the modular Document Type Definition (DTD). Refer to MIL-STD-3001-1 for information on obtaining or accessing this modular DTD. SGML tags used in the modular DTD are noted throughout the text of this standard in bracketed,
33、bold characters (i.e., ) as a convenience for the TM author and to denote the appropriate tag to be used for this specific information when developing a document instance. 4.4.1 Use of the DTDs. The modular DTDs referenced in this Part interpret the technical content and structure for the functional
34、 requirements contained in this Part and are mandatory for use. 4.5 Technical content. Technical content requirements contained in this Part are considered mandatory and are intended for compliance. The content structure for the technical data being developed shall Provided by IHSNot for ResaleNo re
35、production or networking permitted without license from IHS-,-,-MIL-STD-3001-3(AS) 2 conform to the associated modular Document Type Definition (DTD) for Testing and Troubleshooting. For examples of typical technical content for specific work packages covered in this standard, refer to MIL-HDBK-3001
36、. 4.5.1 Work packages. There are basically two types of work packages (WPs). The first type is an information-oriented work package. It provides support information such as principles of operation, general descriptive information, and controls and indicators descriptions for the weapon system/equipm
37、ent. Additional data that supports the procedural and maintenance tasks, such as lists of materials required, lists of support equipment, etc., are also considered information-oriented WPs. The second type of WP is task-oriented. Task-oriented WPs reflect all required maintenance or operation tasks
38、at the assigned level of maintenance, and environment, material, and support equipment required for each defined task. WPs shall reflect the maintenance concept developed from the Logistics Support Analysis (LSA) or the Logistics Management Information (LMI), the Level of Repair Analysis (LORA), or
39、the approved maintenance plan, and the established repair concept (SM another is the incorporation of electronically controlled sensors within the systems to be tested. Testing procedures shall identify the specific part number tape or the software required for test performance. Sensors, installed a
40、t critical points in aircraft systems, are used to detect discrepancies in system operation during flight. Readout capability varies from magnetic tape in-flight monitors to digital display maintenance monitoring panels. Special documentation have been designed to properly interpret these displays a
41、nd isolate and correct malfunctions. Provided by IHSNot for ResaleNo reproduction or networking permitted without license from IHS-,-,-MIL-STD-3001-3(AS) 4 5.1.2 Aircraft and aircraft system operational checkout and troubleshooting. Operational checkout (testing) and troubleshooting includes fault r
42、eporting/fault isolation data for the overall aircraft weapon system and detailed checkout and troubleshooting procedures. These procedures shall include all information and instructions required to perform ground tests (system/subsystem checkout), evaluate test indications, and troubleshoot malfunc
43、tions or failures of aircraft systems/subsystems, interconnecting wiring, and components. 5.1.2.1 Fault reporting/fault isolation information. Fault reporting information provides flight crews and ground operating personnel with a standardized means for reporting and interpreting aircraft malfunctio
44、ns and fault symptoms. Fault isola tion information is designed for use in rapid isolation of faults revealed during flight or while the airplane is in an operational configuration on the ground (i.e., just prior to launch or just after landing). This data shall instruct maintenance personnel as to
45、what maintenance actions to perform and/or what procedures to use to correct reported faults. Fault reporting information and the fault isolation data are designed to be used together. Fault isolation information coverage shall be limited to faults identified in the fault reporting data which requir
46、e specific procedures to isolate the cause. Fault reporting data shall reference the fault isolation data to the maximum extent practical for isolation of indicated malfunctions. 5.1.2.2 Integrated system operational checkout and troubleshooting. When several systems are dependent upon each other fo
47、r proper operation, the interdependent systems, as a unit, are identified as an integrated system. The operational test of an integrated system is an operational checkout of the interdependent systems, less non-associated systems, and shall reflect the assumption that the technician performing the c
48、heck is qualified on the aircraft and is familiar with its systems and subsystems. Integrated system troubleshooting procedures shall be presented in two levels; first, the integrated system as a unit, second the systems that make up the integrated system. Development and content of operational chec
49、kout and troubleshooting for integrated systems shall be determined based on the systems having self-test or built-in test capabilities or requiring the use of a system peculiar test set or common test equipment. An integrated system may involve the need to use all three types of test capabilities. These compound applications require more specifics on the criteria of which components or signals are tested by which me
