1、MIL-STD-3001-2(AS)15 May 2001SUPERSEDING(See Section 6.)DEPARTMENT OF DEFENSESTANDARD PRACTICEDIGITAL TECHNICAL INFORMATIONFORMULTI-OUTPUT PRESENTATIONOFTECHNICAL MANUALSDESCRIPTION, PRINCIPLES OF OPERATION ANDOPERATION DATA(PART 2 OF 8 PARTS)AMSC A7194 AREA TMSSDISTRIBUTION STATEMENT A. Approved fo
2、r public release; distribution is unlimited.NOT MEASUREMENTSENSITIVEProvided by IHSNot for ResaleNo reproduction or networking permitted without license from IHS-,-,-MIL-STD-3001-2(AS) ii FOREWORD 1. This eight-part standard establishes the requirements needed to prepare digital technical informatio
3、n for multi-output 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 weapo
4、ns/ equipment, and 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-2 is Part 2 of 8 Par
5、ts and is incomplete without Part 1 and Parts 3 through 8. Part 2 establishes the technical content requirements for the preparation of description, principles of operation, and operating data for aircraft weapon systems, aeronautical equipment, airborne weapons/equipment, and support equipment. Thi
6、s data can be used to develop 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
7、contain specific functional technical 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 Descript
8、ion, Principles of Operation, and 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-ST
9、D-3001-8 Separate Illustrated Parts 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 pag
10、e-oriented, scrollable and frame-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
11、, Highway 547, Lakehurst, NJ 08733-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-2(AS) CONTENTS PARAGRAP
12、H PAGE iii FOREWORD . ii 1. SCOPE 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
13、Technical content . 1 4.5.1 Work packages . 2 4.5.2 Style and format requirements 2 4.6 Standard tables and lists 2 5. DETAILED REQUIREMENTS. 2 5.1 Preparation of descriptive information, principles of operation and operation data 2 5.2 Work package content 2 5.2.1 Title block 2 5.2.2 Work package i
14、nformation . 3 5.2.2.1 Reference material list . 3 5.2.2.2 Record of Applicable Technical Directives . 3 5.2.2.3 Support equipment required list (operation data only) 4 5.2.2.4 Additional work package information (ETMs and IETMs only). 5 5.2.3 Required descriptive information, principles of operatio
15、n and operation data . 5 5.2.4 Description work packages 5 5.2.4.1 Aircraft general description work packages (General Aircraft Information and Plane Captains Manuals only) 5 5.2.4.1.1 Aircraft general description work package . 6 5.2.4.1.1.1 Aircraft description 6 5.2.4.1.1.2 Aircraft dimensions .
16、6 5.2.4.1.1.3 Aircraft materials distribution . 6 5.2.4.1.2 Aircraft arrangement work package 6 5.2.4.1.3 Aircraft systems description work package 6 5.2.4.1.4 Aircraft instrument panel location work package 6 5.2.4.1.5 Danger areas and precautionary measures work package 6 5.2.4.1.6 Aircraft statio
17、ns work package . 6 5.2.4.1.7 Aircraft dimensions work package . 6 Provided by IHSNot for ResaleNo reproduction or networking permitted without license from IHS-,-,-MIL-STD-3001-2(AS) CONTENTS PARAGRAPH PAGE iv 5.2.4.1.8 Aircraft access and inspection panels and provisions work package . 7 5.2.4.1.9
18、 Aircraft external power source connections work package . 7 5.2.4.2 Aircraft systems, aeronautical, airborne weapons/equipment, support equipment, and engine description work packages 7 5.2.4.2.1 Aircraft system, subsystem, and component description work packages . 7 5.2.4.2.1.1 Controls and indica
19、tor descriptions 7 5.2.4.2.2 Aeronautical equipment, airborne weapons/equipment, and support equipment description work packages . 8 5.2.4.2.3 Engine and engine system description work packages . 8 5.2.4.2.4 Programming software description work packages 9 5.2.5 Principles of operation 9 5.2.5.1 Air
20、craft weapon system principles of operation work packages 9 5.2.5.2 Aeronautical equipment, airborne weapons/equipment, and support equipment principles of operation work packages . 10 5.2.5.3 Engine systems principles of operation work packages . 10 5.2.5.4 Schematic diagram work packages 10 5.2.6
21、Operation data. 10 5.2.6.1 Operating instruction work packages (end item) 11 5.2.6.2 Software loading work packages . 12 6. NOTES 12 Provided by IHSNot for ResaleNo reproduction or networking permitted without license from IHS-,-,-MIL-STD-3001-2(AS) 1 1. SCOPE. 1.1 Scope. This part of the standard e
22、stablishes the technical content requirements for the preparation of description, principles of operation, and operating data for aircraft weapon systems, aeronautical equipment, airborne weapons/equipment, and support equipment. This data can be used to develop Technical Manuals (TMs) in a variety
23、of output forms, including interactive screen presentations and page-based, printed manuals. 2. APPLICABLE DOCUMENTS. The applicable documents in section 2 of MIL-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
24、. 4.1 General. Sufficient descriptive information and principles of operation necessary for a user to familiarize and comprehend the aircraft weapon system, aeronautical equipment, airborne weapons/ equipment or support equipment shall be developed. In addition, operating data for selected end item
25、equipment shall also be prepared. 4.2 Maintenance level applicability. 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 appl
26、ication and tailoring. This Part contains some requirements that 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 cont
27、ained in MIL-STD-3001-1, Appendix A. The applicability of some requirements 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 m
28、anual data prepared and delivered digitally in accordance with this Part of the 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 note
29、d throughout the text of this Part in bracketed, bold characters (i.e., ) as a convenience for the TM author and to denote the appropriate tag to be used for the specific information when developing a document instance. 4.4.1 Use of the DTDs. The modular DTDs referenced in this Part interpret the te
30、chnical content and structure for the functional 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 de
31、veloped shall Provided by IHSNot for ResaleNo reproduction or networking permitted without license from IHS-,-,-MIL-STD-3001-2(AS) 2 conform to the associated modular Document Type Definition (DTD) for Description, Principles of Operation, and Operation information. For examples of typical technical
32、 content for specific work packages covered in this standard, refer to MIL-HDBK-3001. 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 descriptiv
33、e information, and controls and indicators descriptions for the weapon system/equipment. Additional data that supports 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-
34、oriented. Task-oriented WPs reflect all required maintenance or operation tasks 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
35、Logistics Management Information (LMI), the Level of Repair Analysis (LORA), or the approved maintenance plan, and the established repair concept (SM repetition of the manual title and publication number is not required. f. Additional WPs within the same manual that are required to complete the task
36、 or discussion should be presented first in numerical sequence. The WP title and WP number shall also be identified. The publication number is not required. g. Referenced publications not prepared in WP format shall be presented in numerical sequence. The title and publication number shall also be i
37、ncluded. 5.2.2.2 Record of Applicable Technical Directives . Technical directives applicable to a specific work package shall be listed in a record of applicable technical directives list (standard list). If no technical directives apply, the heading “Record of Applicable Technical Directives“ shall
38、 be omitted from the work package. The record of applicable technical directives shall be prepared in accordance with the following guidelines. a. All issued technical directives having any impact on the WP shall be listed upon incorporation into the WP. Provided by IHSNot for ResaleNo reproduction
39、or networking permitted without license from IHS-,-,-MIL-STD-3001-2(AS) 4 b. Approved engineering change proposals (ECPs) that have no effect on retrofit of the end item shall not be listed in the record of applicable technical directives (e.g., “no technical directive will be issued“). c. All techn
40、ical directives and related ECPs or Rapid Action Minor Engineering Changes (RAMECs) shall be listed upon incorporation into the WP: (1) “TD Type/No.“ - Enter the type and number of the technical directive, e.g., “A6 AFC 454“ or “AVC 1492.“ Note: The “TD Type/No.“ is identified on the Change Control
41、Board (CCB) formal letter of ECP or RAMEC approval. Refer to NAVAIR 00-25-300. (2) “TD Date“ - Enter the date of issue of the technical directive. If the number of the technical directive has been assigned but the directive has not been issued, a dash (-) shall be entered. (3) “Title and ECP/RAMEC N
42、o.“ - The title of the technical directive and the ECP number or RAMEC, if applicable, shall be listed. If a technical directive listed is the direct result of an approved ECP or RAMEC, the acronym ECP or RAMEC and number shall be shown in parentheses following the technical directive title. (4) “Da
43、te Inc.“ - The date the information affected by the technical directive or the ECP was incorporated into the WP. (a) If the technical directive number has been assigned and the directive has not yet been issued (retrofit program), but the ECP that incorporates the change in the production program ha
44、s been approved, the production ECP coverage shall be included, and the notation “Production coverage only“ shall be entered under “Remarks.“ (b) When the retrofit TD is approved and incorporated in a change or revision following the incorporation of the production ECP coverage, the TD date of issue
45、 shall be entered under “TD Date,“ the notation “Production coverage only“ shall be removed from under “Remarks,“ and the date of retrofit coverage incorporation shall be listed under “Date Inc.“ (in lieu of the production ECP coverage incorporation date). (5) “Remarks“ - Enter any applicable remark
46、s. 5.2.2.3 Support equipment required list (operation data only). All support equipment (SE), including special tools required to perform operational type procedures shall be listed (standard list) immediately following the record of applicable technical directive data. If no support equipment is re
47、quired, the heading “Support Equipment Required“ shall be omitted from the work package. Only those special tools (including torque wrenches) and equipment authorized for use at the level of maintenance covered shall be listed. Items shall be listed in alphabetical sequence by noun nomenclature. Sta
48、ndard hand tools shall not be listed. Illustrations shall not be prepared in support of such lists. When the WP is used by other services or commands that require usage restrictions, the item shall be identified by a symbol following the part number in parentheses. The usage of the symbol shall be e
49、xplained in a notation (e.g., “(AF)=USAF only,“ “(NS)=NAVSEA only,“ “(MC)=MARINE CORPS only“). Provided by IHSNot for ResaleNo reproduction or networking permitted without license from IHS-,-,-MIL-STD-3001-2(AS) 5 5.2.2.3.1 Each support equipment entry in the list shall be identified by “Nomenclature,“ “Part Number“ and “CAGE Code.“ When more than one of the same item is required, the
