FprEN 9116
(Main)Aerospace series - Notice of change (NOC)
Aerospace series - Notice of change (NOC)
1 Scope
1.1 General
The aviation, space, and defence 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 or manufacturing activity controls various aspects of the configuration and specifications related to the product. When a change to design or process is requested or required, the change is typically required to be evaluated against the impacts to the entire system.
Proposed changes to design data/information that the design activity identifies to be minor and have no effect on the product requirements or specifications, have the potential to be implemented and approved, where authorized to do so, but requires notification. Changes that affect customer mandated requirements or specifications shall be approved prior to implementation. In many cases, the design activity is not conducted by the DAH or design authority. The design activity may be several layers below the design approval. Irrespective of where the design activity is conducted in the supply chain, notification is required. The typical change notification flow is presented in Figure 1.
[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. An objective of this document 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). A sample form can be found in the Supply Chain Management Handbook (SCMH).
If all or part of this document is contractually invoked, design organizations and design holders (i.e. the organization responsible for the product end item design) that have responsibility for change management of products used on other higher-level designs shall use the information and processes defined in this document for submitting change notifications.
1.2 Application
This document defines the common NOC requirements for aviation, space, and defence organizations. The requirements that a design organization are to use when submitting a NOC to the customer for either change authorization or notification are included herein. A NOC informs the customer of physical or functional (e.g. design, material, software, maintenance) changes or any associated process changes to an established baseline configuration.
Retention of the NOC establishes a means of configuration control and captures the evolution of the part. This requirement is of utmost importance in commercial/civil aviation products where changes to type certificated products are mandated by regulations; however, these same concepts are also required in defence and space applications per contractual requirements.
Where there are changes to items which the organization does not have design input or is not permitted to make any changes to the design [e.g. build to print, Technical Standard Order (TSO) articles] then change requests are to be formally submitted to the customer and approved via the customer’s change request process.
[...]
Luft- und Raumfahrt - Anforderungen an eine Änderungsmitteilung
No Scope available
Série aérospatiale - Avis de modification (NOC)
1.1 Généralités
Les industries aéronautique, spatiale et de la défense reposent sur le développement et la fabrication de produits complexes constitués de nombreux systèmes, sous-systèmes, et composants, chacun issu de concepteurs individuels (activités de conception) à plusieurs niveaux de la chaîne d'approvisionnement. Chaque activité de conception ou de fabrication maîtrise plusieurs aspects de la configuration et des spécifications liées au produit. Quand une modification de conception ou de processus est demandée ou exigée, la modification doit généralement être évaluée en fonction de ses impacts sur la totalité du système.
Les demandes de modifications des données/informations de conception que l’activité de conception identifie comme mineures et sans effet sur les exigences ou spécifications du produit peuvent être mises en œuvre et approuvées, lorsque cela est autorisé, mais requièrent une notification. Les modifications qui affectent les exigences ou les spécifications client sont approuvées avant leur mise en œuvre. Dans de nombreux cas, l'activité de conception n'est pas conduite par le DAH ou l'autorité de conception. L'activité de conception peut parfois se trouver plusieurs niveaux au-dessous de l'agrément de conception. Quel que soit l'endroit où l'activité de conception est menée au sein de la chaîne d'approvisionnement, la notification est obligatoire. Le flux de notification type est présenté à la Figure 1.
Figure 1 - Exigences applicables au flux de notification
La soumission des données du NOC se fera soit par voie électronique, soit par voie conventionnelle (papier), selon les termes et conditions du contrat du client. Cela inclut, le cas échéant, l'accès aux données dans le cadre de la réglementation du contrôle des exportations.
Les processus d'échange, de coordination et d'approbation des données du NOC varient en fonction des nombreuses relations et conventions en vigueur parmi toutes les organismes concernées. Le présent document a notamment pour objectif de définir un ensemble de données susceptibles d'être intégrées dans n'importe quelle forme de communication (par exemple, échange de données électroniques, soumission de formulaires conventionnels sur papier). Un modèle de formulaire est donné dans le Supply Chain Management Handbook (SCMH).
Si tout ou partie du présent document est invoqué contractuellement, les organismes de conception et les titulaires de l'agrément de conception (c'est-à-dire l'organisme responsable de la conception du produit final) responsables de la gestion des modifications de produits utilisés pour des conceptions à un niveau supérieur utiliseront les informations et les processus définis dans le présent document pour soumettre les notifications de modification.
1.2 Application
Le présent document définit les exigences communes de NOC pour les organismes aéronautiques, spatiaux et de la défense. Les exigences utilisées par un organisme de conception lors de la soumission d'un NOC au client pour une autorisation ou une notification de modification y sont incluses. Un NOC informe le client des modifications physiques, fonctionnelles (en ce qui concerne par exemple la conception, le matériel, le logiciel, la maintenance) ou de tout processus associé apportées à une configuration de référence établie.
La conservation des NOC établit un moyen de maîtrise de la configuration et témoigne de l'évolution de la pièce. Cette exigence est de la plus haute importance pour les produits de l'aviation commerciale/civile où les modifications de produits avec certificats de type sont régies par des règlements. Cependant, ces mêmes concepts sont également requis pour les applications dans les domaines de la défense et du spatial en fonction des exigences contractuelles.
[...]
Aeronavtika - Sporočilo dobavitelja o spremembi
General Information
Relations
Standards Content (Sample)
SLOVENSKI STANDARD
oSIST prEN 9116:2022
01-junij-2022
Aeronavtika - Sporočilo dobavitelja o spremembi
Aerospace Series - Supplier Notice of Change (NOC)
Ta slovenski standard je istoveten z: prEN 9116
ICS:
49.020 Letala in vesoljska vozila na Aircraft and space vehicles in
splošno general
oSIST prEN 9116:2022 en,fr,de
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.
oSIST prEN 9116:2022
oSIST prEN 9116:2022
DRAFT
EUROPEAN STANDARD
prEN 9116
NORME EUROPÉENNE
EUROPÄISCHE NORM
April 2022
ICS Will supersede EN 9116:2015
English Version
Aerospace Series - Supplier Notice of Change (NOC)
This draft European Standard is submitted to CEN members for enquiry. It has been drawn up by the Technical Committee ASD-
STAN.
If this draft becomes a European Standard, CEN members are bound to comply with the CEN/CENELEC Internal Regulations
which stipulate the conditions for giving this European Standard the status of a national standard without any alteration.
This draft European Standard was established by CEN in three official versions (English, French, German). A version in any other
language made by translation under the responsibility of a CEN member into its own language and notified to the CEN-CENELEC
Management Centre has the same status as the official versions.
CEN members are the national standards bodies of Austria, Belgium, Bulgaria, Croatia, Cyprus, Czech Republic, Denmark, Estonia,
Finland, France, Germany, Greece, Hungary, Iceland, Ireland, Italy, Latvia, Lithuania, Luxembourg, Malta, Netherlands, Norway,
Poland, Portugal, Republic of North Macedonia, Romania, Serbia, Slovakia, Slovenia, Spain, Sweden, Switzerland, Turkey and
United Kingdom.
Recipients of this draft are invited to submit, with their comments, notification of any relevant patent rights of which they are
aware and to provide supporting documentation.
Warning : This document is not a European Standard. It is distributed for review and comments. It is subject to change without
notice and shall not be referred to as a European Standard.
EUROPEAN COMMITTEE FOR STANDARDIZATION
COMITÉ EUROPÉEN DE NORMALISATION
EUROPÄISCHES KOMITEE FÜR NORMUNG
CEN-CENELEC Management Centre: Rue de la Science 23, B-1040 Brussels
© 2022 CEN All rights of exploitation in any form and by any means reserved Ref. No. prEN 9116:2022 E
worldwide for CEN national Members.
oSIST prEN 9116:2022
prEN 9116:2022 (E)
Contents Page
European foreword . 3
0 Introduction . 4
0.1 Rationale . 4
0.2 Introduction . 4
1 Scope . 5
1.1 General. 5
1.2 Purpose . 6
1.3 Convention . 6
2 Normative references . 7
3 Terms and definitions . 7
4 Configuration change requirements . 9
4.1 Changes to baseline configuration. 9
4.2 Change types . 12
4.2.1 General. 12
4.2.2 Approval prior to implementation . 12
4.2.3 Customer acceptance prior to implementation . 13
4.2.4 Concurrent with Notification . 13
4.2.5 Non-configuration. 13
4.3 Change impact analysis tool . 14
5 Requirements for change analysis on behalf of the design holder . 15
5.1 General requirements . 15
5.2 Quality management system requirements . 15
5.3 Customer agreements . 15
5.4 Approval of Design Activity to Perform Change Impact Assessments . 16
5.4.1 General. 16
5.4.2 Prerequisites for change impact assessments . 16
5.4.3 Requesting and maintaining design change impact assessment approval . 16
5.4.4 Design change impact assessment processes . 17
5.5 Requirements for submission of notice of change . 17
5.6 Retained documented information . 18
Annex A (informative) Acronym log . 19
Annex B (informative) Supplier notification of change (NOC) — Change impact analysis
(CIA) logic tree . 20
Annex C (informative) List of notice of change (NOC) data . 28
Annex D (informative) Sample notice of change (NOC) form . 35
Bibliography . 40
oSIST prEN 9116:2022
prEN 9116:2022 (E)
European foreword
This document (prEN 9116:2022) has been prepared by the Aerospace and Defence Industries
Association of Europe — Standardization (ASD-STAN).
This document is currently submitted to the CEN Enquiry.
After enquiries and votes carried out in accordance with the rules of this Association, this document has
received the approval of the National Associations and the Official Services of the member countries of
ASD-STAN, prior to its presentation to CEN.
This document will supersede EN 9116:2015.
oSIST prEN 9116:2022
prEN 9116:2022 (E)
0 Introduction
0.1 Rationale
This document was created to define the process requirements and data expectations for the
submission of proposed changes in design and manufacturing information that requires approval of the
Design Approval Holder (DAH), when the DAH is different from the design activity. This document
provides for the organisational requirements, definitions, and data submission, including suggested
data descriptions and format (paper or electronic submission).
This revision to the document provides updated information and improves the writing clarity to
facilitate uniform submittal of supplier change notifications and/or approval when contractually
invoked at any level, including sub-tier suppliers, or as guidance within the aviation, space, and defence
industries. This document can be invoked as a stand-alone requirement or used in conjunction with
9100-series standards (i.e. 9100, 9110, 9120).
0.2 Introduction
To ensure customer satisfaction, aviation, space, and defence industry organisations needs to provide
and continually improve, safe and reliable products and services that meet or exceed customer and
applicable statutory and regulatory authority requirements. The globalization of the industry and the
resulting diversity of regional and national requirements and expectations have complicated this
objective. Organisations have the challenge of purchasing products and services from external
providers throughout the world and at all levels within the supply chain. External providers have the
challenge of delivering products and services to multiple customers with varying quality expectations
and requirements.
Industry established the International Aerospace Quality Group (IAQG), with representatives from
aviation, space and defence companies in the Americas, Asia/Pacific, and Europe, to implement
initiatives that make significant improvement in quality and reductions in cost throughout the value
stream. This international standard has been prepared by the IAQG.
This document identifies requirements for design change management and/or manufacturing process
change to a previously approved product design (baseline configuration) of the product. This includes
requirements for supplier Notice of Change (NOC) data definition and documentation for the aviation,
space, and defence industries. The establishment of common requirements for use at all levels of the
supply-chain is intended to improve quality, safety, and decrease costs by the elimination or reduction
of organization-unique requirements and the resultant variation inherent in these multiple
expectations. This document can be invoked as a stand-alone requirement or used in conjunction with
IAQG 9100-series standards (i.e. 9100, 9110, 9120).
oSIST prEN 9116:2022
prEN 9116:2022 (E)
1 Scope
1.1 General
The aviation, space, and defence 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 or manufacturing
activity controls various aspects of the configuration and specifications related to the product. When a
change to design or process is requested or required, the change is typically required to be evaluated
against the impacts to the entire 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 implemented and
approved, where authorized to do so, but require notification. Changes that affect customer mandated
requirements or specifications shall be approved prior to implementation. In many cases, the design
activity is not conducted by the DAH or design authority. The design activity may be several layers
below the design approval. Irrespective of the supplier is in the supply chain, notification is required.
The typical change notification flow is presented in Figure 1.
Figure 1 — Requirements for change notification flow
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 organisations concerned. An objective of this document 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). A sample form can be found in the Supply Chain
Management Handbook (SCMH).
If all or part of this document is contractually invoked, design organisations and design holders (i.e. the
organization responsible for the product end item design) that have responsibility for change
management of products used on other higher-level designs need to use the information and processes
defined in this document for submitting change notifications.
oSIST prEN 9116:2022
prEN 9116:2022 (E)
1.2 Purpose
This document defines the common NOC requirements for aviation, space, and defence organisations.
Included are the requirements that an internal/external supplier or subcontractor need to use when
submitting a NOC to the customer for either change authorization or notification. A NOC informs the
customer of physical or functional (e.g. design, material, software) changes or any associated process
changes to an established baseline configuration.
Retention of the NOC establishes a means of configuration control and captures the evolution of the
part. This requirement is of utmost importance in commercial/civil aviation products where changes to
type certificated products are mandated by regulations; however, these same concepts a
...
Questions, Comments and Discussion
Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.