Refine Your Search

Search Results

Viewing 1 to 5 of 5
Standard

Standard for Preparing an Electronic Components Management Plan

2007-11-01
HISTORICAL
EIASTD4899A
This document defines the requirements for developing an Electronic Components Management Plan (ECMP), hereinafter also called the Plan, to assure customers and regulatory agencies that all of the electronic components in the equipment of the Plan owner are selected and applied in controlled processes compatible with the end application; and that the Technical Requirements detailed in clause 5.0 are accomplished. In general the owners of a complete Electronic Components Management Plan are avionics equipment manufacturers.
Standard

Standard for Preparing a DMSMS Management Plan

2011-08-01
HISTORICAL
STD0016
This document defines the requirements for developing a DMSMS Management Plan, hereinafter also called the Plan, to assure customers that the Plan owner is using a proactive DMSMS process for minimizing the cost and impact that part and material obsolescence will have on equipment delivered by the Plan owner. The technical requirements detailed in clause 5 ensure that the Plan owner can meet the requirement of having a process to address obsolescence as required by Industry Standards such as EIA-4899 “Standard for Preparing an Electronic Components Management Plan” and DoD Programs as required by MIL-STD-3018 “Parts Management”. Owners of DMSMS Management Plans include System Integrators, Original Equipment Manufacturers (OEM), and logistics support providers.
Standard

Requirements for an Electronic Components Management Plan

2015-02-17
HISTORICAL
EIASTD4899B
This document applies to the development of Plans for integrating and managing electronic components in equipment for the military and commercial aerospace markets; as well as other ADHP markets that wish to use this document. Examples of electronic components, as described in this document, include resistors, capacitors, diodes, integrated circuits, hybrids, application specific integrated circuits, wound components, and relays. It is critical for the Plan owner to review and understand the design, materials, configuration control, and qualification methods of all “as-received” electronic components, and their capabilities with respect to the application; identify risks, and where necessary, take additional action to mitigate the risks. The technical requirements are in Clause 3 of this standard, and the administrative requirements are in Clause 4.
Standard

Requirements for an Electronic Components Management Plan

2017-05-09
CURRENT
EIASTD4899C
This document applies to the development of Plans for integrating and managing electronic components in equipment for the military and commercial aerospace markets; as well as other ADHP markets that wish to use this document. Examples of electronic components, as described in this document, include resistors, capacitors, diodes, integrated circuits, hybrids, application specific integrated circuits, wound components, and relays. It is critical for the Plan owner to review and understand the design, materials, configuration control, and qualification methods of all “as-received” electronic components, and their capabilities with respect to the application; identify risks, and where necessary, take additional action to mitigate the risks. The technical requirements are in Clause 3 of this standard, and the administrative requirements are in Clause 4.
Standard

Methods to Address Specific Issues Related to COTS Electronic Components in Airborne Electronic Hardware

2020-11-09
CURRENT
ARP7495
This ARP is not a certification document; it contains no certification requirements beyond those already contained in existing certification documents. The purpose of this ARP is to provide more detailed descriptions of the 12 hardware-related COTS issues listed in Appendix B, and to provide recommendations on existing practices, processes, and methods to address them. This ARP also describes artifacts that may be used as evidence that the issues have been addressed. The recommended practices and artifacts may be used to facilitate communication between, for example, the provider and the user of the avionics systems into which COTS components are integrated, or between the applicant for certification and the certification body. This ARP does not claim that the recommended practices and artifacts described in this ARP are the only acceptable ones.
X