Refine Your Search

Search Results

Viewing 1 to 5 of 5
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

Quality Management Systems – Requirements for Aviation, Space and Defense Organizations – Deliverable Software (Supplement to 9100)

2010-04-27
HISTORICAL
AS9115
The requirements of 9100 apply with the following clarification for software. This document supplements the 9100 standard requirements for deliverable software and contains quality management system requirements for organizations that design, develop, and/or produce deliverable software for the aviation, space, and defense industry. This includes, as required, support software that is used in the development and maintenance of deliverable software. The deliverable software may be stand-alone, embedded, or loadable into a target computer. Where the use of Hardware Description Language (HDL) or high order language is utilized as the design source of electronic hardware [e.g., Application Specific Integrated Circuit (ASIC), Programmable Logic Device (PLD)], the organization and customer shall agree on the extent of applicability of this supplement. NOTE 1: For airborne electronic hardware guidance, see RTCA/DO-254 or EUROCAE ED-80; and for product realization requirements, see 9100.
Standard

Quality Management Systems - Requirements for Aviation, Space, and Defense Organizations - Deliverable Software (Supplement to 9100:2016)

2017-02-01
CURRENT
AS9115A
The requirements of 9100 apply with the following clarification for software. This standard supplements the 9100 standard requirements for deliverable software and contains quality management system requirements for organizations that design, develop, and/or produce deliverable software and services for the aviation, space, and defense industry. This includes, as required, support software that is used in the development and maintenance of deliverable software and services. The deliverable software may be stand-alone, embedded, mobile application, or loadable into a target computer. This deliverable software may also be part of services (e.g., cloud environment, web hosted solutions or platforms).
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

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