Search Results

This standard is applicable to all items used for manufacturing, maintenance, and repair of aviation, space, and defense products from the raw material to the final product (e.g., aircraft, structural items, constituent assemblies, standard parts, consumables with conformity and/or safety impact). This standard considers items dispositioned as scrap in accordance with 9100-series standards’ supporting nonconformity management, corrective action, or organization decisions (e.g., obsolescence, inventory management, missing traceability documentation). 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 applicable statutory or regulatory requirements take precedence.

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.

This SAE Aerospace Recommended Practice (ARP) establishes the general requirements when implementing any of the statistical product acceptance methods as defined in ARP9013/1, ARP9013/2, ARP9013/3, and ARP9013/4. This recommended practice also establishes the minimum content required to be covered in an organization’s documented procedures that govern their application of statistical product acceptance methods. These general requirements and documented procedures apply the requirements of AS9100 plus requirements for retrievability, safety/critical characteristics, quality parameters, and that these parameters protect the customer. This recommended practice is to be used in conjunction with the variety of sampling strategies, statistical techniques, and process control methods of the ARP9013/1 through ARP9013/4 recommended practices as chosen by the organization.

This document defines to supplier/subcontractor common information and documentation required to inform Customers, when applicable about nonconformity (Customer-provider use). It does not apply to the reporting of a nonconformity to the product owner/operator. Reporting of Product Quality Escapes and use of Waiver/Concession is subject to the terms and conditions of the contractual requirements.

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).

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.

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.

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 SAE Aerospace Standard (AS) defines uniform Quality and Technical requirements relative to metallic parts marking performed in using "Data Matrix symbology" used within the aerospace industry. The ISO/IEC 16022 specifies general requirements (data character encodation, error correction rules, decoding algorithm, etc.). In addition to ISO/IEC 16022 specification, part identification with such symbology is subject to the following requirements 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. This standard does not specify information to be encoded. 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 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.

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.

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 contains recommended practices for the effective control of non-deliverable software. It addresses practices for control during the development, production, release maintenance, and retirement of non-deliverable software, as well as for software procured from outside manufacturers and incorporated in the production, evaluation, test, acceptance or calibration of processes. For the purposes of this document, the terms software and non-deliverable software are considered synonymous.

This document contains recommended practices for the effective control of non-deliverable software. It addresses practices for control during the development, production, release maintenance, and retirement of non-deliverable software, as well as for software procured from outside manufacturers and incorporated in the production, evaluation, test, acceptance or calibration of processes. For the purposes of this document, the terms software and non-deliverable software are considered synonymous.

This document contains recommended practices for the effective control of non-deliverable software. It addresses practices for control during the development, production, release maintenance, and retirement of non-deliverable software, as well as for software procured from outside manufacturers and incorporated in the production, evaluation, test, acceptance or calibration of processes. For the purposes of this document, the terms software and non-deliverable software are considered synonymous.