Search Results

This standard is primarily intended to apply to new parts and products intended to be produced in an on-going production phase, but can also be applied to parts currently in production (e.g., manufacturing, maintenance). The standard is applicable to all production processes that influence the variation of KCs, as well as maintenance and service processes in which KCs are identified. It applies to organizations for assemblies and all levels of parts within an assembly, down to the basic materials including castings and forgings, and to organizations that are responsible for producing the design characteristics of the product. The variation control process begins with product definition, typically stated in the design documentation (e.g., digital model, engineering drawing, specification) which identifies KCs, and leads to a variation management process for those KCs. This process may also be used for producer-identified KCs (e.g., process KCs, additional/substitute product KCs).

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 shall be approved prior to implementation.

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.

The purpose of ARP9013/4 is to ensure conformance for each product characteristic being verified under these methods. ARP9013/4 provides the requirements for continuous sampling, skip-lot sampling, and for statistical methods for product acceptance that do not derive from industry standard tables.

The purpose of this SAE Aerospace Recommended Practice (ARP) is to ensure conformance for each product characteristic being verified in a lot, without maintaining information from previous lots. ARP9013/1 specifies a product acceptance system for isolated lots. For example, isolated lot sampling avoids keeping track of the normal, tightened, and reduced levels of sampling formerly used in MIL-STD-105 and currently used in ANSI/ASQC Z1.4. Because those switching rules provided significant long-term protection for product quality, these isolated lot tables replace that protection in other ways.

The purpose of ARP9013/2 is to ensure conformance for each product characteristic being verified in each lot in the series. ARP9013/2 document specifies a product acceptance system using either attribute or variable lot acceptance methods documented in ANSI/ASQC Z1.4, ANSI/ASQC Z1.9, and "Zero Acceptance Number Sampling Plans " by Nicholas L. Squeglia.

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 standard establishes requirements when implementing statistical product acceptance methods to meet defined risk requirements. This standard 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 the 9100/9110/9120 quality management system standards, in addition to establishing requirements for retrievability, safety/critical characteristics, and quality parameters that protect the customer.

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 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 objective of any organization, as part of continual improvement, is to reduce the number of issues (i.e., undesirable conditions, defects, failures) and to minimize their impact on quality, delivery performance, and cost. This includes having processes in place to detect and eradicate significant and recurrent issues, which implies having well identified problems, a common understanding of their impact and associated root causes, and having defined and implemented adequate actions so that these problems, including similar issues will not happen again.

This standard establishes requirements for performing and documenting APQP and PPAP. APQP begins with conceptual product needs and extends through product definition, production planning, product and process validation (i.e., PPAP), product use, and post-delivery service. This standard integrates and collaborates with the requirements of the 9100, 9102, 9103, and 9110 standards. 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.

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 describes requirements for standardized processes (and associated technologies) that ensure type design data are retrievable and usable for the life of a type certificate (50+ years). These processes are primarily concerned with, but not limited to, digital type design data retained in three-dimensional representations and associated data that is required for complete product definition, such as tolerances, specification call-outs, product structure and configuration control data, etc. This process standard includes process requirements for managing the evolution of technologies required to ensure the availability of the data for the life of the product. This data must be available to meet regulatory, legal, contractual and business requirements. This process standard is not intended to incorporate every company specific requirement and does not dictate specific organizational structures within a company.

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 shall be approved prior to implementation.

This standard establishes the baseline requirements for performing and documenting FAI. Should there be a conflict between the requirements of this standard and applicable statutory or regulatory requirements, the applicable statutory or regulatory requirements shall take precedence.

This standard defines requirements for the preparation and execution of the audit process. In addition, it defines the content and composition for the audit reporting of conformity and process effectiveness to the 9100-series standards, the organization's QMS documentation, and customer and statutory/regulatory requirements. The requirements in this standard are additions or represent changes to the requirements and guidelines in the standards for conformity assessment, auditing, and certification as published by ISO/IEC (i.e., ISO/IEC 17000, ISO/IEC 17021). When there is conflict with these standards, the requirements of the 9101 standard shall take precedence. NOTE 1: In this standard, the term “9100-series standards” comprises the following Aerospace Quality Management System (AQMS) standards: 9100, 9110, and 9120; developed by the IAQG and published by various national standards bodies.

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 is primarily intended to apply to new parts and products, but can also be applied to parts currently in production. The standard shall be applicable to all production processes, that influence the variation of KCs, as well as maintenance processes in which KCs are identified. It applies to assemblies and all levels of parts within an assembly, down to the basic materials including castings and forgings, and to organizations that are responsible for producing the design characteristics of the product. It does not apply to lab-scale, pilot, or pre-production processes. However, particular management of some KCs might be required using other methods than those described in the standard, during these phases of a program, when required by the customer or deemed appropriate by the organization (e.g., Engineering department requirement).