MIL-STD-1796A(USAF)
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 environments.
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 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, schedules, 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 Technology Development, Engineering and Manufacturing Development, Production & Deployment, and Operations & Support phases of a program. It is applicable to acquisition of new, existing and modified existing aviation electronics ("avionics"); 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 with 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 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 place, 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 brightness, radio performance, navigation accuracy, etc.)
b. Normal "best practices" of system engineering (e.g., configuration control, data management and submittal, etc.)
1
For Parts Inquires submit RFQ to Parts Hangar, Inc.
© Copyright 2015 Integrated Publishing, Inc.
A Service Disabled Veteran Owned Small Business