Search Results

ARP9013/3 recommended practice specifies a product acceptance system using process control methods. Its purpose is to assure conformance for specified characteristics. Use of process control techniques for product acceptance requires maintaining process stability and capability. A stable and capable process is the best assurance of conforming hardware for the customer. There can be lower inspection costs associated with a process control acceptance approach.

These requirements are applicable to IAQG sector schemes when making use of ABs, CRBs and their auditors, for the assessment and certification/registration of supplier quality systems in accordance with the requirements of this document. The quality management system standard used by the CRB shall be 9100/9110/9120, as appropriate to the supplier’s activities. It shall be applied to the supplier’s complete Quality System that covers aerospace products. Sectors may use these requirements for other standards. IAQG members have committed to recognize the equivalence of certification/registration of a suppliers quality management system to either of the AS, EN or JISQ/SJAC standards.

This document provides the minimum requirements (Body of Knowledge) for AQMS auditors who will participate in AQMS certification/registration activities, including the auditor authentication process and requirements for a training organization. It is applicable to auditors seeking formal approval to conduct audits of the AQMS in support of the IAQG, and those who manage the competency element of an AQMS audit program and/or training organizations.

The requirements of 9100 apply with the following clarification for software. This document supplements the 9100 standard requirements for deliverable software and contains quality management system requirements for organizations that design, develop, and/or produce deliverable software for the aviation, space, and defense industry. This includes, as required, support software that is used in the development and maintenance of deliverable software. The deliverable software may be stand-alone, embedded, or loadable into a target computer. Where the use of Hardware Description Language (HDL) or high order language is utilized as the design source of electronic hardware [e.g., Application Specific Integrated Circuit (ASIC), Programmable Logic Device (PLD)], the organization and customer shall agree on the extent of applicability of this supplement. NOTE 1: For airborne electronic hardware guidance, see RTCA/DO-254 or EUROCAE ED-80; and for product realization requirements, see 9100.

The requirements of 9100 apply with the following clarification for software. This standard supplements the 9100 standard requirements for deliverable software and contains quality management system requirements for organizations that design, develop, and/or produce deliverable software and services for the aviation, space, and defense industry. This includes, as required, support software that is used in the development and maintenance of deliverable software and services. The deliverable software may be stand-alone, embedded, mobile application, or loadable into a target computer. This deliverable software may also be part of services (e.g., cloud environment, web hosted solutions or platforms).

Limited to the aerospace industry, where an approved manufacturer requests a supplier to ship an article against the approved manufacturer’s quality system directly to a customer. The direct ship process is not required or applicable to standard parts or military parts. In this process the approved manufacturer is responsible for assurance that the article conforms to type design information.

Limited to the Aerospace industry where an approved manufacturer requests a supplier to ship an article against the approved manufacturer’s quality system directly to a customer. The direct ship process is not required or applicable to standard parts or military parts. In this process the approved manufacturer is responsible for assurance that the article conforms to Type Design information.

This document is limited to the aerospace industry, where an approved manufacturer requests a supplier to ship an article against the approved manufacturer’s quality system directly to a customer. The direct ship process is not required or applicable to standard parts or military parts. In this process, the approved manufacturer is responsible for assurance that the article conforms to type design information.

Limited to the Aerospace industry where an approved manufacturer requests a supplier to ship an article against the approved manufacturer's quality system directly to a customer. The direct ship process is not required or applicable to standard parts or military parts. In this process the approved manufacturer is responsible for assurance that the article conforms to Type Design information.

Limited to the Aerospace industry where an approved manufacturer requests a supplier to ship an article against the approved manufacturer’s quality system directly to a customer. The direct ship process is not required or applicable to standard parts or military parts. In this process the approved manufacturer is responsible for assurance that the article conforms to Type Design information.

Limited to the Commercial Aerospace industry where a request is made for a Production Organization (PO) to have Direct Delivery Authorization (DDA), which includes an Appropriate Arrangement (AA) between the PO and the Design Organization (DO). In this process the DO is responsible for ensuring the continuous updating of design and airworthiness data to the PO, whilst the PO is responsible for assurance that the manufactured article conforms to Approved Design and Airworthiness Data. The PO is responsible to provide airworthiness release documentation.

The basic requirements of AS9100A apply with the following clarifications. This document supplements the requirements of AS9100A for deliverable software. This supplement contains Quality System requirements for suppliers of products that contain deliverable embedded or loadable airborne, spaceborne or ground support software components that are part of an aircraft Type Design, weapon system, missile or spacecraft operational software and/or support software that is used in the development and maintenance of deliverable software. This includes the host operating system software including assemblers, compilers, linkers, loaders, editors, code generators, analyzers, ground simulators and trainers, flight test data reduction, etc., that directly support creation, test and maintenance of the deliverable software.

This standard defines uniform quality and technical requirements relative to metallic parts marking performed using "data matrix symbology" within the aviation, space, and defense industry. ISO/IEC 16022 specifies general requirements (e.g., data character encodation, error correction rules, decoding algorithm). In addition to ISO/IEC 16022 specification, part identification with such symbology is subject to the requirements in this standard to ensure electronic reading of the symbol. The marking processes covered by this standard are as follows: Dot Peening Laser Electro-Chemical Etching Further marking processes will be included, if required. Unless specified otherwise in the contractual business relationship, the company responsible for the design of the part shall determine the location of the data matrix marking. Symbol position should allow optimum illumination from all sides for readability. This standard does not specify information to be encoded.

This Standard defines uniform Quality and Technical requirements relative to metallic parts marking performed in using "Data Matrix symbology" (2D) coding used within the aerospace industry. The ISO 16022 specifies general requirements (data characters encodation, error correction rules, decoding algorithm, etc.). In addition to this specification, part Identification with such coding is subject to the following requirements to ensure electronic reading (scanning) ability of the symbol. The marking processes covered by this standard are as follows: Dot Peening Laser Marking Electro-Chem Etching Further marking processes will be included if required. Unless specified otherwise in the contractual business relationship, the company responsible for the design of the part shall determine the location of the Data Matrix Marking. Symbol position should allow illumination from all sides for readability.

This document is intended to prescribe consistent requirements for CSI management for organizations and suppliers who perform work for prime contractors receiving direct contracts from U.S. government agencies (i.e., first-tier or prime suppliers).

The aviation, space, and defense industries rely on the development and manufacture of complex products comprised of multiple systems, subsystems, and components each designed by individual designers (design activities) at various levels within the supply chain. Each design activity controls various aspects of the configuration and specifications related to the product. When a change to design information is requested or required, the change has to be evaluated against the impacts to the higher-level system. Proposed changes to design information that the design activity identifies to be minor and have no effect on their product requirements or specifications have the potential to be concurrently implemented and approved, where authorized to do so. Changes that affect customer mandated requirements or specifications must be approved prior to implementation.

The aviation, space, and defense industries rely on the development and manufacture of complex products comprised of multiple systems, subsystems, and components each designed by individual designers (design activities) at various levels within the supply chain. Each design activity controls various aspects of the configuration and specifications related to the product. When a change to design information is requested or required, the change has to be evaluated against the impacts to the higher-level system. Proposed changes to design information that the design activity identifies to be minor and have no effect on their product requirements or specifications have the potential to be concurrently implemented and approved, where authorized to do so. Changes that affect customer mandated requirements or specifications must be approved prior to implementation.

Operator Self-Verification can apply to a variety of processes. The primary focus is on traditional manufacturing operations, but applications can be made wherever traditional inspection methods are employed. The practices recommended in this document are intended to identify the basic elements for structuring Operator Self-Verification programs within the aerospace industry; applicable to producers of commercial and military aircraft and weapons platforms, space vehicles, and all related hardware, software, electronics, engines and composite components. Operator Self-Verification programs are applied to improve overall efficiency and product quality to processes considered mature, as judged by the organization. Operator Self-Verification programs are not stand-alone processes, but augment existing quality management system standard requirements.

The focus of Operator Self-Verification is on traditional manufacturing operations, and applications can be made wherever traditional inspection is employed. The practices recommended in this document are intended to identify the basic elements and provide a “guideline” for structuring Operator Self-Verification programs within the aerospace industry; applicable to producers of commercial and military aircraft and weapons platforms, space vehicles, and all related hardware, software, electronics, engines and composite components. Operator Self-Verification programs are applied to improve the overall efficiency and product quality of processes considered mature, as judged by the implementing organization. Operator Self-Verification programs are not stand-alone processes, but augment existing quality management systems.

This document identifies the basic elements and provides a standard for structuring operator self-verification programs within the aviation, space, and defense industry for producers of commercial and military aircraft and weapons platforms, space vehicles, and all related hardware, software, electronics, engines, and composite components. The requirements specified in this standard are complementary (not alternative) to contractual and applicable statutory and regulatory requirements. Should there be a conflict between the requirements of this standard and applicable statutory or regulatory requirements, the latter shall take precedence.