Refine Your Search

Topic

null

Search Results

Standard

A Process Standard for the Storage, Retrieval and Use of Three-Dimensional Type Design Data

2003-09-04
ARP9034
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.
Standard

A Process Standard for the Storage, Retrieval and Use of Three-Dimensional Type Design Data

2015-04-21
ARP9034A
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.
Standard

AS9000 AUDIT SUMMARY AND SUPPLIER PROFILE INSTRUCTIONS

1997-08-01
AS9000-APPNDX1
To assure customer satisfaction, aerospace industry manufacturers must produce world class quality products at the lowest possible cost. AS9000 standardizes, to the greatest extent possible, the quality system requirements of the aerospace industry. Standardization of compliance requirements results in cost savings due to the elimination or reduction of unique requirements developed for each different customer. AS9000 Appendix 1, AS9000 Audit Summary and Supplier Profile Instructions, facilitates the standardization of this process.
Standard

AS9000 Audit Summary and Supplier Profile Instructions

2003-12-19
AS9000-APPNDX1A
To assure customer satisfaction, aerospace industry manufacturers must produce world class quality products at the lowest possible cost. AS9000 standardizes, to the greatest extent possible, the quality system requirements of the aerospace industry. Standardization of compliance requirements results in cost savings due to the elimination or reduction of unique requirements developed for each different customer. AS9000 Appendix 1, AS9000 Audit Summary and Supplier Profile Instructions, facilitates the standardization of this process.
Standard

Aerospace Basic Quality System Standard

1998-03-01
AS9000
To assure customer satisfaction, aerospace industry manufacturers must produce world class quality products at the lowest possible cost. This document standardizes, to the greatest extent possible, the quality system requirements of the aerospace industry. Standardization of compliance requirements results in cost savings due to the elimination or reduction of unique requirements developed for each different customer.
Standard

Aerospace Contract Clauses

2017-06-21
ARP9009A
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.
Standard

Aerospace Contract Clauses

2006-01-21
ARP9009
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.
Standard

Aerospace First Article Inspection Requirement

2014-10-06
AS9102B
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.
Standard

Aerospace Guidance for Non-Deliverable Software

2005-06-06
ARP85G
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.
Standard

Aerospace Guidance for Non-Deliverable Software

2005-06-06
ARP9005
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.
Standard

Aerospace Guidance for Non-Deliverable Software

2016-06-27
ARP9005A
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.
Standard

Aerospace Operator Self-Verification Programs

2004-03-24
ARP9062
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.
Standard

Aerospace Operator Self-Verification Programs

2005-05-10
ARP9162
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.
Standard

Aerospace Operator Self-Verification Programs

2016-11-08
AS9162
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.
Standard

Aerospace Series - Certificate of Conformity Requirements

2022-12-07
AS9163
This SAE Aerospace Standard (AS) provides a harmonized process and documentation requirements for the establishment of CoCs used to attest the conformity of aviation, space, and defense products (e.g., assemblies, sub-assemblies, equipment and systems, parts, material, software) or services. It includes a CoC template and supporting instructions on how to complete it. When quoted by the customer in a contractual requirement, application of this document is mandatory. In other cases, its use is recommended, but if there is a conflict between the requirements of this standard and customer or applicable statutory/regulatory requirements, the latter shall take precedence.
Standard

Aerospace Series - Notice of Change (NOC) Requirements

2014-10-30
AS9116
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.
Standard

Aerospace Series - Notice of Change (NOC) Requirements

2019-04-05
WIP
AS9116A
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.
X