Refine Your Search

Topic

Search Results

Standard

Quality Management Systems - Nonconformance Documentation - Word Format

2007-09-26
AS9131AW
AS9131 - This standard defines the common nonconformance data definition and documentation that an internal or external supplier or sub-tier supplier must submit when informing a customer of a nonconformity. The requirements shall be are applicable for reporting a nonconforming product to the owner/operator (i.e., end item user), if specified by contract. Reporting of nonconformance data, either electronically or conventionally on paper, is subject to the terms and conditions of the contract. This also includes, where applicable, data access under export control regulations.
Standard

AS9000 AUDIT SUMMARY AND SUPPLIER PROFILE INSTRUCTIONS

1997-08-01
HISTORICAL
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

Aerospace Series – Notice of Change (NOC) Requirements

2009-06-11
HISTORICAL
AS9016
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.
Standard

Aerospace Series – Notice of Change (NOC) Requirements

2015-03-12
CURRENT
AS9016A
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.
Standard

Requirements for Registration of Quality Systems to AS9000 or AS9100

2001-07-01
HISTORICAL
AIR5359A
These requirements are applicable to Accreditation Bodies, Registrars and OEMs, when specified by an aerospace company requiring assessment and/or registration of their quality system in accordance with the requirements of this document. The quality management system standard shall be AS9000 or AS9100 and shall be applied to the organization’s complete Quality System that covers aerospace products.
Standard

Requirements for Certification/Registration of Aerospace Quality Management Systems

2003-07-23
HISTORICAL
AIR5359B
The requirements defined in this AIR are applicable to Accreditation Bodies (ABs), Certification/Registration Bodies (CRBs), and Original Equipment Manufacturers (OEMs), during assessment and/or certification/registration to the applicable quality management system standard to meet industry accepted practices.
Standard

Statistical Product Acceptance Requirements Using Process Control Methods

2005-10-27
HISTORICAL
ARP9013/3
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.
Standard

Statistical Product Acceptance Requirements Using Isolated Lot Sampling Methods

2005-10-27
HISTORICAL
ARP9013/1
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.
Standard

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

2003-09-04
HISTORICAL
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
CURRENT
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

Aerospace Guidance for Non-Deliverable Software

2005-06-06
HISTORICAL
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

Direct Delivery Authorization Guidance for Aerospace Companies

2005-09-09
HISTORICAL
ARP9107
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.
Standard

Direct Delivery Authorization Guidance for Aerospace Companies

2017-11-09
CURRENT
ARP9107A
Limited to the commercial aerospace industry where a request is made for a 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.
Standard

Supplier Self Verification Process Delegation Programs

2007-09-26
HISTORICAL
AS9015
This SAE Aerospace Standard (AS) further defines the requirements for a delegation process identified in Aerospace Quality Management System (AQMS) standards (i.e., AS9100, AS9110, AS9120). This standard establishes minimum requirements for the delegation of product verification to an organization’s suppliers; outlining requirements for the initial delegation (qualification/selection), maintenance, and removal/withdrawal of delegations.
X