Aerospace Series - Notice of Change (NOC) Requirements

Standard:
Issued:
  • 2014-10-30
 
  • CURRENT
Publisher:
  • SAE International
Pages:
28
Scope:

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. In many cases, the design activity is not the design approver or authority; ultimate approval may be several layers above the design activity. The typical flow of design requirements to the supplier, from the design authority, and the change notification flow is presented in Figure 1.

Submitting NOC data either electronically or conventionally on paper is subject to the terms and conditions of the customer’s contract. This also includes, where applicable, data access under the regulations of export control.

The process of exchanging, coordinating, and approving NOC data varies with the multiple relationships and agreements among all organizations concerned. The information provided by this standard forms the architecture for submitting and managing data that allows for concise and accurate communication using various methods. One objective of this standard 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).

If all or part of this standard is invoked in the contract, design activities and design holders (i.e., the organization responsible for the design) that have responsibility for change management of products used on other higher-level designs shall use the information and processes defined in this standard, and in accordance with the contract, for submitting change notifications to customers.

Rationale:

This standard was created to define the process requirements and data expectations for the submission of proposed changes in design information that requires concurrent approval of the design authority, when the design authority is different from the design activity. This standard provides for the organizational requirements, definitions, and data submission, including suggested data descriptions and format (paper or electronic submission).

This standard was created to provide for the uniform submittal of change notifications and/or approval when contractually invoked at any level or as guidance within the aviation, space, and defense industries. This standard can be invoked as a stand-alone requirement or used in conjunction with 9100-series standards (i.e., 9100, 9110, 9120).

History:
Standard Published Revision Status
AS9116 2014-10-30 Latest Issued
Access
Now
SAE MOBILUS Subscriber? You may already have access.
Buy
Select
Price
List
Download
$76.00
Add
Mail
$76.00
Members save up to 18% off list price.
Grade
If you are currently using this technical report:
Share
HTML for Linking to Page
Page URL

Related Items

Training / Education
2013-04-09
Technical Paper / Journal Article
2014-04-20
Training / Education
2017-11-01
Training / Education
2013-04-09
Training / Education
2017-10-31