Search Results

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.

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.

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.

This standard defines the common nonconformance data definition and documentation that shall be exchanged between an internal/external supplier or sub-tier supplier, and the customer when informing about a nonconformity requiring formal decision. The requirements are applicable, partly or totally, when reporting a product nonconformity to the owner or operator, as user of the end item (e.g., engine, aircraft, spacecraft, helicopter), if specified by contract. The process of exchanging, coordinating, and approving nonconformance data varies with the multiple relationships and agreements among all parties concerned. The information provided by this standard forms guidelines for submitting and managing of data through accurate communication. The main objective is to provide the definition of a data set that can be integrated into any form of communication (e.g., electronic data interchange, submission of conventional paper forms).

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.

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.

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.

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.

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.