Refine Your Search

Date

Date

Topic

Topic

Heat transfer G-14 Americas Aerospace Quality Standards Committee (AAQSC) Design Engineering and Styling Terminology Thermodynamics Engine components

Search Results

Viewing 1 to 20 of 39
12Next >Last >>
Sort by relevance
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

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 Isolated Lot Sampling Methods
2018-06-02
CURRENT
ARP9013/1A
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

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

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

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

Data Matrix (2D) Coding Quality Requirements for Parts Marking
2002-02-26
HISTORICAL
AS9132
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.
Standard

Deliverable Aerospace Software Supplement for AS9100AQuality Management Systems - Aerospace - Requirements for Software (based on AS9100A)
2013-07-09
HISTORICAL
AS9006A
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.
Standard

Deliverable Aerospace Software Supplement for AS9100A Quality Management Systems - Aerospace - Requirements for Software (based on AS9100A)
2003-03-12
HISTORICAL
AS9006
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.
Standard

Aerospace – Customer Identified Major Quality Management System Nonconformity Other Party Collaborative Corrective Action Process
2021-10-18
CURRENT
AS9018
This standard is applicable to AQMS COs listed in the Online Aerospace Supplier Information System (OASIS) database. This standard is intended for the management and resolution of AQMS CO’s major QMS nonconformities. This standard is not intended to address QMS nonconformities classified as minor or nonconformities related to the products or services provided by the CO.
Standard

Aerospace Series - Root Cause Analysis and Problem Solving (9S Methodology)
2016-11-08
CURRENT
ARP9136
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.
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.
12Next >Last >>
X