Search Results

Non-deliverable software is defined as software that facilitates the design, development, manufacture, inspection, test, acceptance, or calibration of a deliverable product, and is not generally delivered under a contract. This may include deliverable services software such as but not limited to maintenance procedures, order processing and/or various types of online technical support resources. As Industry efforts increase to improve product quality and reliability and reduce production costs, use of computer software programs for automation, control and monitoring of production processes and product test, acceptance and calibration is also increasing. It is therefore vital to assure these software programs are controlled to ensure product conformity requirements are properly supported.

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.

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.

The purpose of ARP9013/4 is to ensure conformance for each product characteristic being verified under these methods. ARP9013/4 provides the requirements for continuous sampling, skip-lot sampling, and for statistical methods for product acceptance that do not derive from industry standard tables.

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.

The purpose of ARP9013/2 is to ensure conformance for each product characteristic being verified in each lot in the series. ARP9013/2 document specifies a product acceptance system using either attribute or variable lot acceptance methods documented in ANSI/ASQC Z1.4, ANSI/ASQC Z1.9, and "Zero Acceptance Number Sampling Plans " by Nicholas L. Squeglia.

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.

The purpose of ARP9013/4 is to ensure conformance for each product characteristic being verified under these methods. ARP9013/4 provides the requirements for continuous sampling, skip-lot sampling, and for statistical methods for product acceptance that do not derive from industry standard tables.

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.

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

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.

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.

This standard defines the requirements for the effective control of non-deliverable software. This standard can be used during the design, development, test, production, release, use, maintenance, and retirement of non-deliverable software. This can include non-deliverable software procured from external suppliers and utilized in the design, production, evaluation, test, acceptance, or calibration of a deliverable product. This standard focuses solely on the unique requirements of the operational processes that pertain to non-deliverable software as identified by clause 1.2. Operational processes not covered in this standard are addressed by the respective organization’s Quality Management System (QMS), based on the 9100-series (i.e., 9100, 9110, 9120) and/or ISO 9001 standards. If there is a conflict between the requirements of this standard, and customer or applicable statutory/regulatory requirements, the latter shall take precedence.

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.

The requirements established in this document are applicable to the IAQG and associated sectors for managing oversight to established requirements contained in 9104-series standards (i.e., 9104/1, 9104/2, 9104/3). The requirements are applicable to IAQG working groups for oversight.

This SAE Aerospace Recommended Practice (ARP) establishes the general requirements when implementing any of the statistical product acceptance methods as defined in ARP9013/1, ARP9013/2, ARP9013/3, and ARP9013/4. This recommended practice also establishes the minimum content required to be covered in an organization’s documented procedures that govern their application of statistical product acceptance methods. These general requirements and documented procedures apply the requirements of AS9100 plus requirements for retrievability, safety/critical characteristics, quality parameters, and that these parameters protect the customer. This recommended practice is to be used in conjunction with the variety of sampling strategies, statistical techniques, and process control methods of the ARP9013/1 through ARP9013/4 recommended practices as chosen by the organization.

This SAE Aerospace Recommended Practice (ARP) establishes the general requirements when implementing any of the statistical product acceptance methods as defined in ARP9013/1, ARP9013/2, ARP9013/3, and ARP9013/4. This recommended practice also establishes the minimum content required to be covered in an organization's documented procedures that govern their application of statistical product acceptance methods. These general requirements and documented procedures apply the requirements of AS9100 plus requirements for retrievability, safety/critical characteristics, quality parameters, and that these parameters protect the customer. This recommended practice is to be used in conjunction with the variety of sampling strategies, statistical techniques, and process control methods of the ARP9013/1 through ARP9013/4 recommended practices as chosen by the organization.

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.

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.