Refine Your Search

Topic

Search Results

Standard

Direct Ship - Recommended Practices for Aerospace Companies

2002-04-08
HISTORICAL
ARP9004
Limited to the Aerospace industry where an approved manufacturer requests a supplier to ship an article against the approved manufacturer’s quality system directly to a customer. The direct ship process is not required or applicable to standard parts or military parts. In this process the approved manufacturer is responsible for assurance that the article conforms to Type Design information.
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

2000-03-01
HISTORICAL
AIR5359
This procedure shall be applied by ANSI-RAB or other Accreditation Bodies to registrars that meet the criteria of 5.2 of this document, when specified by an aerospace company requiring assessment and/or registration of their quality system to the requirements of this procedure. The quality system standard shall be AS9000 or AS9100 and shall be applied to the supplier's complete Quality System that covers aerospace products.
Standard

Statistical Product Acceptance Requirements Using Process Control Methods

2018-06-02
CURRENT
ARP9013/3A
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 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

Aerospace Operator Self-Verification Programs

2004-03-24
HISTORICAL
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 Basic Quality System Standard

1998-03-01
HISTORICAL
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

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

Control of Aviation Critical Safety Items

2017-03-17
CURRENT
AS9017
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).
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

Aerospace Operator Self-Verification Programs

2005-05-10
HISTORICAL
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 Guidance for Non-Deliverable Software

2005-06-06
HISTORICAL
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
CURRENT
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.
X