1、 NOT MEASUREMENT SENSITIVE MIL-STD-1796A(USAF) 13 October 2011 SUPERSEDING MIL-STD-1796(USAF) 31 July 1986 MIL-HDBK-87244(USAF) 30 January 1995 DEPARTMENT OF DEFENSE STANDARD PRACTICE AVIONICS INTEGRITY PROGRAM (AVIP) Reinstated after 13 October 2011 and may be used for new and existing designs and
2、acquisitions. AMSC N/A FSG 15GP DISTRIBUTION STATEMENT A. Approved for public release, distribution is unlimited. Provided by IHSNot for ResaleNo reproduction or networking permitted without license from IHS-,-,-MIL-STD-1796A(USAF) ii FOREWORD 1. This standard is approved for use by the Department o
3、f the Air Force and is available for use by all Departments and Agencies of the Department of Defense. 2. The Avionics Integrity Program (AVIP) identifies the design tasks needed to achieve high reliability, long life, safe operation and supportability of aviation electronics in operational environm
4、ents. 3. This standard replaces the Avionics/Electronics Integrity Process (AVIP) handbook, MIL-HDBK-87244. AVIP originated in the mid-1980s as a “reliability by design“ standard to improve electronic products used in military applications, then was replaced in the late 1980s by a less prescriptive
5、handbook. This new version of AVIP revives the original MIL-STD-1796 number and title and is, once again, a standard which can be cited as a contractual requirement. 4. AVIP is focused on the “integrity” performance requirements (tolerate the environment, perform reliably, etc.), as opposed to “miss
6、ion” performance requirements (e.g., radar range, navigation accuracy, communication capability, etc.). The document focuses on tasks to be performed to define and achieve avionics integrity rather than focusing on specification requirements. 5. The task and product requirements in this standard are
7、 to be referenced or copied into statements of work and other contractual documents. The tasks required by this version of AVIP are not new or exotic they are the same tasks successful programs have used in the past to build robust avionics. The need for consistent application of these system engine
8、ering techniques is driven by the users requirement for systems with high mission-capable rates, high availability rates and low support cost. 6. The AVIP requirements and process tasks are to be used in conjunction with the other integrity program documents as part of a balanced systems engineering
9、 process to foster an engineering and manufacturing climate that is consistent with integrated program development concepts. 7. AVIP does not focus on aircraft safety certification, but some products used in AVIP will also support certification of avionics to MIL-HDBK-516, Airworthiness Certificatio
10、n Criteria. 8. Comments, suggestions, or questions on this document should be addressed to the Aeronautical Systems Center, Engineering Standards Office: ASC/ENRS, 2145 Monahan Way, Wright-Patterson AFB OH 45433-7017, or emailed to Engineering.Standardswpafb.af.mil. Since contact information can cha
11、nge, you may want to verify the currency of this address information using the ASSIST Online database at https:/assist.daps.dla.mil. Provided by IHSNot for ResaleNo reproduction or networking permitted without license from IHS-,-,-MIL-STD-1796A(USAF) CONTENTS PARAGRAPH PAGE iii 1 SCOPE 1 1.1 Scope 1
12、 1.2 Use 1 1.3 Applicability 1 1.4 Tailoring 1 1.5 Approach 1 2 APPLICABLE DOCUMENTS . 2 2.1 General . 2 2.2 Government documents 2 2.2.1 Specifications, standards, and handbooks . 2 2.3 Non-Government publications . 2 2.4 Order of precedence 3 3 DEFINITIONS 3 3.1 Definitions 3 3.1.1 Aging . 3 3.1.2
13、 Analysis . 3 3.1.3 Anti-tamper (AT) . 3 3.1.4 Commercial off-the-shelf (COTS) 3 3.1.5 Corrosion . 3 3.1.6 Defect 3 3.1.7 Demonstration 4 3.1.8 Derating. 4 3.1.9 Design life 4 3.1.10 Durability . 4 3.1.11 Durability life test 4 3.1.12 Economic life . 4 3.1.13 Failure . 4 3.1.14 Inspection 4 3.1.15 I
14、ntegrity . 4 3.1.16 Life limited items. 5 3.1.17 Lead-free electronics 5 Provided by IHSNot for ResaleNo reproduction or networking permitted without license from IHS-,-,-MIL-STD-1796A(USAF) CONTENTS PARAGRAPH PAGE iv 3.1.18 Maintenance . 5 3.1.19 Maintenance action/event . 5 3.1.20 Margin . 5 3.1.2
15、1 Mission critical 5 3.1.22 Non-critical 6 3.1.23 Opportunistic maintenance 6 3.1.24 Parts integrity 6 3.1.25 Preventive maintenance . 6 3.1.26 Safety critical . 6 3.1.27 Safety Critical Function (SCF) 6 3.1.28 Scheduled maintenance 6 3.1.29 Supportability 6 3.1.30 Test 6 3.1.31 Tolerance 7 3.1.32 U
16、nscheduled maintenance . 7 3.1.33 Usage . 7 3.2 Acronyms 7 4 GENERAL REQUIREMENTS 7 4.1 Avionics integrity program (AVIP) 7 4.2 Summary of requirements . 8 4.3 Criticality and incremental verification 11 5 DETAILED REQUIREMENTS 12 5.1 Phase I: Design information (proposal and contract) 12 5.1.1 Plan
17、ning and coordination 12 5.1.2 Design criteria . 12 5.1.3 Characterizing the environment . 12 5.1.4 Characterizing materials and components . 13 5.1.5 Identification and tracking of critical items/critical functions 13 5.1.6 Analysis . 13 5.1.7 Tests and demonstrations 14 5.1.8 Life management 14 Pr
18、ovided by IHSNot for ResaleNo reproduction or networking permitted without license from IHS-,-,-MIL-STD-1796A(USAF) CONTENTS PARAGRAPH PAGE v 5.2 Phase II: Preliminary planning and design (complete by PDR) 14 5.2.1 Planning and coordination 14 5.2.2 Design criteria . 14 5.2.3 Characterizing environm
19、ent . 15 5.2.4 Characterizing materials and components . 15 5.2.5 Identification and tracking of critical items/critical functions 15 5.2.6 Analysis . 15 5.2.7 Tests and demonstrations 16 5.2.8 Life management 16 5.3 Phase III: Design and manufacturing development (complete by CDR) 16 5.3.1 Planning
20、 and coordination 16 5.3.2 Design criteria . 16 5.3.3 Characterizing the environment . 16 5.3.4 Characterizing materials and components . 16 5.3.5 Identification and tracking of critical items and critical functions . 16 5.3.6 Analysis . 17 5.3.7 Tests and demonstrations 17 5.3.8 Life management 17
21、5.4 Phase IV: Verification and production (complete by delivery) 17 5.4.1 Planning and coordination 17 5.4.2 Design criteria . 17 5.4.3 Characterizing the environment . 17 5.4.4 Characterizing materials and components . 17 5.4.5 Identification and tracking of critical items and critical functions .
22、18 5.4.6 Analysis . 18 5.4.7 Tests and demonstrations 18 5.4.8 Life management 18 5.5 Phase V: Force management (operational) . 18 5.5.1 Planning and coordination 18 5.5.2 Design criteria . 19 5.5.3 Characterizing the environment . 19 Provided by IHSNot for ResaleNo reproduction or networking permit
23、ted without license from IHS-,-,-MIL-STD-1796A(USAF) CONTENTS PARAGRAPH PAGE vi 5.5.4 Characterizing materials and components . 19 5.5.5 Identification and tracking of critical items and critical functions . 19 5.5.6 Analysis . 19 5.5.7 Tests and demonstrations 19 5.5.8 Life management 19 6 NOTES 19
24、 6.1 Intended use . 19 6.2 Acquisition requirements . 19 6.3 Subject term (key word) listing 20 6.4 Changes from previous issue . 20 FIGURES FIGURE 1. Tolerance and margin relationship. 5TABLES TABLE I. Summary of AVIP requirements. . 9TABLE II. Timing of environmental and life testing. . 11Provided
25、 by IHSNot for ResaleNo reproduction or networking permitted without license from IHS-,-,-MIL-STD-1796A(USAF) 1 1 SCOPE 1.1 Scope. This standard identifies the design tasks needed to achieve high reliability, long life, safe operation and supportability of aviation electronics in operational environ
26、ments. 1.2 Use. This standard should be applied to avionics subsystem and system development programs for military aircraft. Apply the requirements of section 5 to acquisitions by calling out MIL-STD-1796 as a contractual compliance document. Include the potential of a developer to execute section 5
27、 requirements as source selection evaluation criteria and as statement of work tasking. This standard may be used as a contractual requirement by any group or agency, program office or contractor. This standard also supports development of statements of work, systems engineering management plans, sc
28、hedules, specifications and other program documentation. Requirements of the document are intentionally limited such that this standard can be invoked as a contract requirement without over-constraining the design or process. 1.3 Applicability. This standard is applicable, when tailored, to Technolo
29、gy Development, Engineering and Manufacturing Development, Production including equipment referred to as commercial off-the-shelf (COTS) or non-developmental items (NDI). Aviation electronics includes all airborne electronics and may include ground electronics when they are specifically associated w
30、ith the air vehicle (e.g., ground control stations for unmanned vehicles). 1.4 Tailoring. The requirements of this document should be tailored as necessary by incorporating a requirement to comply with this standard into appropriate contractual documents, along with caveats excluding any paragraphs
31、that should not apply, and adding any additional related requirements. 1.5 Approach. The Avionics Integrity Program (AVIP) is intended to be one part of an integrated product development effort, not a separate program. AVIP assumes that a disciplined systems engineering management process is in plac
32、e, based on the practices defined in the ASC/EN systems engineering guide. This document does not cover manufacturing processes and quality control. This document deals only with integrity of the avionics. Therefore, it does not address: a. Mission performance issues (e.g., radar range, display brig
33、htness, radio performance, navigation accuracy, etc.) b. Normal “best practices” of system engineering (e.g., configuration control, data management and submittal, etc.) Provided by IHSNot for ResaleNo reproduction or networking permitted without license from IHS-,-,-MIL-STD-1796A(USAF) 2 c. Softwar
34、e safety levels or criteria 2 APPLICABLE DOCUMENTS 2.1 General. The documents listed in this section are specified in sections 3, 4, or 5 of this standard. This section does not include documents cited in other sections of this standard or recommended for additional information or as examples. While
35、 every effort has been made to ensure the completeness of this list, document users are cautioned that they must meet all specified requirements of documents cited in sections 3, 4, or 5 of this standard, whether or not they are listed. 2.2 Government documents. 2.2.1 Specifications, standards, and
36、handbooks. The following specifications, standards, and handbooks form a part of this document to the extent specified herein. Unless otherwise specified, the issues of these documents are those cited in the solicitation or contract. DEPARTMENT OF DEFENSE STANDARDS MIL-STD-1798 Mechanical Equipment
37、and Subsystems Integrity Program DEPARTMENT OF DEFENSE HANDBOOKS MIL-HDBK-338 Electronic Reliability Design Handbook (Copies of this document are available online at https:/assist.daps.dla.mil/quicksearch/ or from the Standardization Document Order Desk, 700 Robbins Avenue, Building 4D, Philadelphia
38、, PA 19111-5094.) 2.3 Non-Government publications. The following documents form a part of this document to the extent specified herein. Unless otherwise specified, the issues of these documents are those cited in the solicitation or contract. GOVERNMENT ELECTRONICS AND INFORMATION TECHNOLOGY ASSOCIA
39、TION (GEIA) GEIA-STD-0005-1 Performance Standard for Aerospace and High Performance Electronic Systems Containing Lead-Free Solder GEIA-HB-0005-1 Program Management/Systems Engineering Guidelines for Managing the Transition to Lead-Free Electronics Provided by IHSNot for ResaleNo reproduction or net
40、working permitted without license from IHS-,-,-MIL-STD-1796A(USAF) 3 (Copies may be obtained from Government Electronics and Information Technology Association, Standards for example, specification limits (see FIGURE 1). 3.1.32 Unscheduled maintenance. Unexpected maintenance of critical items that m
41、ust be accomplished for mission and/or safety reasons. 3.1.33 Usage. The operational parameters that define how an item is used. These parameters may be critical to function, performance, and service-life of the system and equipment (e.g.; number of missions or duty cycles, degree of loading, enviro
42、nments, etc.). 3.2 Acronyms. Acronyms used in this document are expanded as follows: AIMP avionics integrity master plan ALC Air Logistics Center AT anti-tamper AVIP avionics integrity program BIT built-in-test CDR critical design review FMECA failure modes, effects, and criticality analysis FMET fa
43、ilure modes and effects testing LFE lead-free electronics PDR preliminary design review RFP request for proposal R&M reliability and maintainability SIL system integration laboratory SOF safety of flight SOW statement of work TO technical order 4 GENERAL REQUIREMENTS 4.1 Avionics integrity program (
44、AVIP). AVIP supports achievement of overall program objectives. It should improve operational readiness and mission success of the avionics, and reduce demand for maintenance manpower and logistic support. The acquisition program should identify the resources, schedule, Provided by IHSNot for Resale
45、No reproduction or networking permitted without license from IHS-,-,-MIL-STD-1796A(USAF) 8 management structure, and controls necessary to ensure specified tasks are satisfactorily accomplished. AVIP will focus on the following: a. Environmental design and qualification 1) Defining the total environ
46、ment 2) Designing to ensure equipment will operate in the required environment 3) Verifying (often by test) that equipment operates in and survives the environment b. Durability/life requirements to ensure equipment will meet design life requirements in the defined environment. c. Impact on integrit
47、y of implementing requirements such as lead-free electronics and anti-tamper. d. Identification and management of flight/safety critical functions, parts obsolescence, and parts integrity. e. Follow-up control through maintenance, inspection, and data gathering from the deployed force. 4.2 Summary o
48、f requirements. TABLE I summarizes the requirements which apply to the five phases and eight elements of AVIP. These requirements are detailed in section 5 of this document. Where this document requires that something be “documented” or “established,” such information is to be available for use by the product team (including the customer or procuring activity) and preserved for use in future stages of the program. A prime contractor will typically generate this data (or collect it from subcontractors) and maintain it in a program data base. The procuring agency should have access to the da
