Search Results

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.

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.

This SAE Aerospace Recommended Practice (ARP) specifies for quality requirements that are additive to a procurement document or contract, where an organization: a needs to provide additional guidance for suppliers and other organizations in the delivery of products, goods and services in accordance with stated quality demands, and b needs to provide information in addition or in absence of existing quality system requirements to provide the assurance of conformity to customer and applicable regulatory requirements. NOTE: In this ARP, the term ‘product’ applies only to the product intended for, or required by, a customer.

This SAE Aerospace Recommended Practice (ARP) specifies for quality requirements that are additive to a procurement document or contract, where an organization: a needs to provide additional guidance for suppliers and other organizations in the delivery of products, goods and services in accordance with stated quality demands, and b needs to provide information in addition or in absence of existing quality system requirements to provide the assurance of conformity to customer and applicable regulatory requirements. NOTE: In this ARP, the term ‘product’ applies only to the product intended for, or required by, a customer.

This SAE Aerospace Standard (AS) establishes requirements for performing and documenting the First Article Inspection (FAI).

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

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.

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.

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

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.

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.

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.

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

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.