Aerospace series - Notice of Change (NOC) Requirements

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 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 European Standard forms the architecture for submitting and managing data that allows for concise and accurate communication using various methods. One objective of this European 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 European 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 European Standard, and in accordance with the contract, for submitting change notifications to customers.
1.2   Application
This European Standard defines the common NOC requirements for aviation, space, and defence organizations. Included are the requirements that an internal/external supplier or subcontractor shall use when submitting a NOC to the customer for either change authorization or notification. A NOC informs the customer of physical or functional (including software) 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 to some degree in defence and space applications per contractual requirements.
This European Standard is not applicable to products that are manufactured by a supplier to their customer's designs and processing requirements (also known as build-to-print). Change requests to this type of product shall be formally submitted to the customer and approved via the customer’s change request process. Additionally, this European Standard is not applicable to commercial parts (off-the-shelf items not specifically designed for aviation, space, or defence products) for which changes in product definition is not affected or known, but change to commercial parts that are kno

Luft- und Raumfahrt - Anforderungen an eine Änderungsmitteilung

Série aérospatiale - Avis de modification (NOC) - Exigences

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 (entités de conception) à plusieurs niveaux de la chaîne d'approvisionnement. Chaque activité de conception maîtrise plusieurs aspects de la configuration et des spécifications liées au produit. Quand une modification des données de conception est exigée ou demandée, la modification doit être évaluée en fonction de ses impacts sur le système de niveau supérieur.
Les demandes de modifications des données de conception identifiées comme mineures et sans effet sur les exigences du produit par l'activité de conception peuvent être mises en oeuvre et approuvées simultanément, après autorisation. Les modifications qui affectent les exigences ou les spécifications autorisées doivent être approuvées avant leur mise en oeuvre. Dans de nombreux cas, l'activité de conception n'est pas l'autorité ou l'approbateur de la conception ; l'approbation finale peut intervenir à plusieurs niveaux au-dessus de l'activité de conception. Le flux classique des exigences de conception de l'autorité de conception envers le fournisseur, ainsi que le flux de notification des modifications sont présentés dans la Figure 1.
La soumission des données du NOC se fera soit par voie électronique, soit par voie conventionnelle (papier), selon les termes du contrat du client. L'accès aux données peut impliquer, le cas échéant, le respect des règlements de l'autorité de 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 entreprises concernées. Les informations fournies par la présente norme européenne forment l'architecture de soumission et de gestion des données qui permet, par l'utilisation de plusieurs méthodes, une communication brève et précise. L'un des objectifs de la présente norme européenne est de fournir la définition d'un ensemble de données qui peut s'intégrer à n'importe quelle forme de communication (par exemple, l'échange de données électroniques, la soumission de formulaires papier conventionnels).
Si tout ou partie de la présente norme européenne est invoqué dans le contrat, les entités de conception et les titulaires de l'agrément de conception (c'est-à-dire l'entreprise responsable de la conception) qui sont responsables de la gestion des modifications de produits utilisés pour des conceptions à un niveau supérieur doivent utiliser les informations et les processus définis dans la présente norme européenne, en conformité avec les termes du contrat, pour soumettre des notifications de modification aux clients.

Aeronavtika - Zahteve za sporočilo o spremembah

Letalska, vesoljska in obrambna industrija se zanaša razvoj in proizvodnjo kompleksnih izdelkov, ki jih sestavljajo številni sistemi, podsistemi in komponente, pri čemer vsako od njih projektirajo posamezni projektanti (projektne dejavnosti) na različnih ravneh v dobavni verigi. Vsaka projektna dejavnost nadzira določene vidike konfiguracije in specifikacij v zvezi z izdelkom. Kadar je potrebna ali zahtevana sprememba projektnih informacij, je treba analizirati vplive te spremembe na sistem na višji ravni.
Predlagane spremembe projektnih informacij, za katere projektna dejavnost prepozna, da so manjšega obsega in ne vplivajo na zahteve ali specifikacije njihovega izdelka, so lahko sočasno implementirane in odobrene, kjer je to odobreno. Spremembe, ki vplivajo na zahteve ali specifikacije stranke, je treba odobriti pred implementacijo. Projektna dejavnost v številnih primerih nima pooblastil za odobritev zasnove, temveč je končna odobritev lahko dodeljena šele nekaj ravni višje od projektne dejavnosti.
Elektronsko ali običajno papirno predložitev podatkov sporočila o spremembah (NOC) urejajo pogoji in določila pogodbe s stranko. To prav tako vključuje, kjer je to primerno, dostop do podatkov v okviru predpisov za nadzor izvoza.
Proces izmenjave, usklajevanja in odobritve podatkov sporočila o spremembah se razlikuje glede na mnoga razmerja in pogodbe med zadevnimi organizacijami. Informacije, ki jih zagotavlja ta evropski standard, tvorijo arhitekturo za predložitev in upravljanje podatkov, ki prek različnih metod omogoča jedrnato in natančno komunikacijo. Eden od ciljev tega evropskega standarda je opredeliti nabor podatkov, ki ga je mogoče integrirati v katero koli obliko komunikacije (npr. elektronska izmenjava podatkov, predložitev običajnih papirnih obrazcev).
Če se v pogodbi navede sklic na ta celotni evropski standard ali njegov del, projektne dejavnosti in imetniki projekta (tj. organizacija, odgovorna za projektiranje), ki so odgovorni za upravljanje sprememb izdelkov, uporabljenih na višjih ravneh projektiranja, uporabijo informacije in procese, opredeljene v tem evropskem standardu, in – v skladu s pogodbo – strankam predložijo sporočila o spremembah.

General Information

Status
Published
Publication Date
22-Dec-2015
Withdrawal Date
29-Jun-2016
Technical Committee
Drafting Committee
Current Stage
6060 - Definitive text made available (DAV) - Publishing
Start Date
23-Dec-2015
Completion Date
23-Dec-2015

Relations

Buy Standard

Standard
EN 9116:2016
English language
36 pages
sale 10% off
Preview
sale 10% off
Preview
e-Library read for
1 day

Standards Content (Sample)


SLOVENSKI STANDARD
01-marec-2016
$HURQDYWLND=DKWHYH]DVSRURþLORRVSUHPHPEDK
Aerospace series - Notice of Change (NOC) Requirements
Luft- und Raumfahrt - Anforderungen an eine Änderungsmitteilung
Série aérospatiale - Avis de modification
Ta slovenski standard je istoveten z: EN 9116:2015
ICS:
49.020 Letala in vesoljska vozila na Aircraft and space vehicles in
splošno general
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.

EN 9116
EUROPEAN STANDARD
NORME EUROPÉENNE
December 2015
EUROPÄISCHE NORM
ICS 49.020
English Version
Aerospace series - Notice of Change (NOC) Requirements
Série aérospatiale - Avis de modification Luft- und Raumfahrt - Anforderungen an eine
Änderungsmitteilung
This European Standard was approved by CEN on 26 September 2015.

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. Up-to-date lists and bibliographical references
concerning such national standards may be obtained on application to the CEN-CENELEC Management Centre or to any CEN
member.
This European Standard exists 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, Former Yugoslav Republic of Macedonia, France, Germany, Greece, Hungary, Iceland, Ireland, Italy, Latvia, Lithuania,
Luxembourg, Malta, Netherlands, Norway, Poland, Portugal, Romania, Slovakia, Slovenia, Spain, Sweden, Switzerland, Turkey and
United Kingdom.
EUROPEAN COMMITTEE FOR STANDARDIZATION
COMITÉ EUROPÉEN DE NORMALISATION

EUROPÄISCHES KOMITEE FÜR NORMUNG

CEN-CENELEC Management Centre: Avenue Marnix 17, B-1000 Brussels
© 2015 CEN All rights of exploitation in any form and by any means reserved Ref. No. EN 9116:2015 E
worldwide for CEN national Members.

Contents Page
European foreword . 3
RATIONALE . 4
1 Scope . 5
1.1 General . 5
1.2 Application . 5
2 Normative references . 6
3 Terms and definitions . 7
4 Configuration change definitions . 8
4.1 Changes to baseline configuration . 8
4.2 Change types . 12
4.2.1 Changes that require customer acceptance prior to implementation . 12
4.2.2 Changes that may require customer acceptance prior to implementation . 12
4.2.3 Changes implemented concurrent with notification for customer acceptance . 13
4.2.4 Changes – non-configuration . 13
4.3 Change impact analysis tool . 14
5 Requirements for organizations to obtain authorization to analyze changes on
behalf of customer . 15
5.1 Quality management system requirements . 15
5.2 Customer agreements . 15
5.3 Approval of design activity to perform change impact assessments . 16
5.3.1 Prerequisites for design activities to perform change impact assessments . 16
5.3.2 Requesting and maintaining design change impact assessment approval . 16
5.3.3 Design change impact assessment processes and procedures . 17
5.4 Requirements for data submission of notice of change . 17
5.5 Record retention . 18
6 NOTES . 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 . 26
Annex D (informative) Sample Notice of Change (NOC) form . 33

European foreword
This document (EN 9116:2015) has been prepared by the Aerospace and Defence Industries
Association of Europe - Standardization (ASD-STAN).
After enquiries and votes carried out in accordance with the rules of this Association, this European
Standard has received the approval of the National Associations and the Official Services of the member
countries of ASD, prior to its presentation to CEN.
This European Standard shall be given the status of a national standard, either by publication of an
identical text or by endorsement, at the latest by June 2016, and conflicting national standards shall be
withdrawn at the latest by June 2016.
Attention is drawn to the possibility that some of the elements of this document may be the subject of
patent rights. CEN [and/or CENELEC] shall not be held responsible for identifying any or all such patent
rights.
According to the CEN-CENELEC Internal Regulations, the national standards organizations of the
following countries are bound to implement this European Standard: Austria, Belgium, Bulgaria, Croatia,
Cyprus, Czech Republic, Denmark, Estonia, Finland, Former Yugoslav Republic of Macedonia, France,
Germany, Greece, Hungary, Iceland, Ireland, Italy, Latvia, Lithuania, Luxembourg, Malta, Netherlands,
Norway, Poland, Portugal, Romania, Slovakia, Slovenia, Spain, Sweden, Switzerland, Turkey and the
United Kingdom.
RATIONALE
This European 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 European Standard
provides for the organizational requirements, definitions, and data submission, including suggested
data descriptions and format (paper or electronic submission).
This European 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
defence industries. This European Standard can be invoked as a stand-alone requirement or used in
conjunction with 9100-series standards (i.e., 9100, 9110, 9120).
To assure customer satisfaction, aviation, space, and defence industry organizations must produce and
continually improve safe, reliable products that meet or exceed customer and regulatory authority
requirements. The globalization of the industry and the resulting diversity of regional/national
requirements and expectations have complicated this objective. End-product organizations face the
challenge of assuring the quality and integration of product purchased from suppliers throughout the
world and at all levels within the supply chain. Industry suppliers and processors face the challenge of
delivering product to multiple customers having varying quality expectations and requirements.
The aviation, space, and defence industry established the International Aerospace Quality Group (IAQG)
for the purpose of achieving significant improvements in quality and safety, and reductions in cost
throughout the value stream. This organization includes representation from companies in the
Americas, Asia/Pacific, and Europe. This international standard has been prepared by the IAQG.
A change process consists of design change management and/or manufacturing process change to a
previously approved design (baseline configuration) of the product. This document standardizes
requirements for 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.
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 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.
REQUIREMENTS
Supplier Integrator Design Holder Design Authority

SUPPLIER CHANGE NOTIFICATION
Design Activity Change Evaluator (Customer) Design Authority
Figure 1 — Typical design requirements and 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 organizations concerned. The information provided by this European
Standard forms the architecture for submitting and managing data that allows for concise and accurate
communication using various methods. One objective of this European 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 European 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
European Standard, and in accordance with the contract, for submitting change notifications to
customers.
1.2 Application
This European Standard defines the common NOC requirements for aviation, space, and defence
organizations. Included are the requirements that an internal/external supplier or subcontractor shall
use when submitting a NOC to the customer for either change authorization or notification. A NOC
informs the customer of physical or functional (including software) 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 to some degree in defence and space applications per contractual
requirements.
This European Standard is not applicable to products that are manufactured by a supplier to their
customer's designs and processing requirements (also known as build-to-print). Change requests to
this type of product shall be form
...

Questions, Comments and Discussion

Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.