EN 9116:2015

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 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 known (i.e., change
in definition from one commercial part number to a different commercial part number) shall be
processed in accordance with this European Standard.
When this European Standard is applied to an organization that distributes product, then this European
Standard shall be a requirement from the distribution organization to the organization from which the
product is procured. The distribution organization may act as a conduit for the NOC or the design
activity (supplier) may work directly with the design authority (customer). The distributor should be
compliant with the 9120 standard, as defined by customer requirements.
Application or implementation of this European Standard in any form, either expressed or implied, is
not allowed for product which has escaped the supplier’s quality system.
2 Normative references
The following documents, in whole or in part, are normatively referenced in this document and are
indispensable for its application. For dated references, only the edition cited applies. For undated
references, the latest edition of the referenced document (including any amendments) applies. When a
conflict in requirements between this document and referenced standards exists, the requirements of
this document shall take precedence. Nothing in this document, however, supersedes applicable laws
and regulations, unless a specific exemption has been obtained.
EN 9100, Quality Management Systems — Requirements for Aviation, Space and Defence Organizations
EN 9110, Quality Management Systems — Requirements for Aviation Maintenance Organizations
EN 9120, Quality Management Systems — Requirements for Aviation, Space, and Defence Distributors
NOTE Equivalent versions (e.g., AS, EN, JISQ, SJAC, NBR) of the IAQG standards listed above are published
internationally in each sector.
ANSI/ASME Y14.24, Types and Applications of Engineering Drawings [document available from
American National Standards Institute (ANSI); www.ansi.org]
ARP9034, A Process Standard for the Storage, Retrieval and Use of Three-Dimensional Type Design Data
EIA – 649, National Consensus Standard for Configuration Management [document available from
Electronic Industries Alliance (EIA) Publications; www.eia.org]
ISO 9000:2005, Quality management systems — Fundamentals and vocabulary
RTCA/DO-254 (EUROCAE ED-80), Design Assurance Guide for Airborne Electronic Hardware [document
available from Radio Technical Commission for Aeronautics Inc.; www.rtca.org]
3 Terms and definitions
Definitions for general terms can be found in ISO 9000 and the IAQG Dictionary, which is located on
the IAQG website. An acronym log for this European Standard is presented in Annex A. For the
purpose of this European Standard, the following shall apply:
3.1
baseline configuration
the design definition for the physical product and its performance requirements from which design
change control can then take place. This is determined jointly by the customer and the design activity
3.2
change evaluator
the person authorized on behalf of the design authority to assess the potential impact of the change(s),
evaluates changes for the potential impact on the fit, form, or functionality of the part, system, or
assembly and failure to meet the customer requirements. The change evaluator could also be the
customer or the producer of the end item and/or the design authority.
3.3
critical items
those items (e.g., functions, parts, software, characteristics, processes) having significant effect on the
product realization and use of the product; including safety, performance, form, fit, function,
producibility, service life, etc.; that require specific actions to ensure they are adequately managed.
Examples of critical items include safety critical items, fracture critical items, mission critical items, key
characteristics, etc.
3.4
deliverable
any design data provided to the customer which represents the product provided
3.5
design activities
the supplier design activity or subcontractor that owns the design and provides a deliverable to the
customer
3.6
design authority
an organization with formal authority for the design, validation, and service support of a product
Note 1 to entry: In civil aviation, this is the organization responsible for the design of articles or for changes
thereto that is the holder of a design approval granted by a regulatory authority [i.e., Type Certificate (TC);
Supplemental Type Certificate (STC); Parts Manufacturer Approval (PMA); Technical Standard Order
(TSO)/European Technical Standard Order (ETSO); European Part Approval (EPA); European Aviation Safety
Agency (EASA) Part 21 - “Design Organization Approval Holder”, or equivalent].
3.7
end item
the item that is ultimately delivered to the end user (e.g., vehicle, propulsion system)
3.8
key characteristics
an attribute or feature whose variation has a significant effect on product fit, form, function,
performance, service life, or producibility that requires specific actions for the purpose of controlling
variation (refer to section 3.3)
3.9
mandatory
a requirement that shall be fulfilled or common transferable data that shall be provided and
systematically recorded
3.10
optional
any data field that is not defined as mandatory by this European Standard, including any special data
fields requested by the customer or the originator
3.11
product
any aviation, space, and defence vehicle, engine, propeller, airframe part or equipment (within that
vehicle) to be used in operating or controlling a vehicle in flight. The result of a process, which in the
context of this European Standard, includes finished detailed parts, assemblies, forgings, and castings.
Note 1 to entry: Product may include software that is embedded or field loadable in the end item.
3.12
Source Control Drawing (SOCD)
provides an engineering description, qualification requirements, and acceptance criteria for items
procurable from a specialized segment of industry, that provide the performance, installation,
interchangeability, or other characteristics required for critical applications. Furthermore, it may
provide a list of approved sources of supply and the vendor's item identification that have been
qualified and approved for use in the critical application(s).
Note 1 to entry: Adapted from ANSI/ASME Y14.24.
3.13
special process
a process where the resulting output cannot be verified by subsequent monitoring or measurement and
as a consequence, deficiencies become apparent only after the product is in use or has been delivered
4 Configuration change definitions
4.1 Changes to baseline configuration
A baseline configuration is an agreed configuration definition against which compliance was shown
(e.g., certification baseline). Baseline configuration is captured by design data and is typically retained
by the design activity. The baseline configuration shall clearly define the design characteristics and
performance requirements of the product, including acceptance conditions of the products to the lowest
level of detail necessary to produce the product and ensure compliance with all applicable
requirements of the customer.
All changes to previously customer accepted baseline configurations shall be evaluated and approved.
Until the requirements of section 5 are satisfied, each change (from the lowest level in the supply chain)
shall be submitted to the customer and ultimately to the design authority for concurrence to implement.
Figure 2 depicts the process when customer delegated change evaluation is not obtained and Figure 3 is
for organization’s with customer delegated change evaluation approval.
The product baseline configuration from which changes will be evaluated may include:
a. SOCD.
b. Product specifications and drawings, including electronic data sets and supersession.
c. Bill of Materials (BOM), including definition of spare or substitute parts which may be used in
repair, but have different definition than those of baseline configuration parts.
d. Process specifications in accordance with contractual requirements.
e. Manufacturing methods, as shown on engineering drawings.
f. Product usage/function/systems application, which may include:
• Effect of product failure on system application.
• Identification of key components, processes, and/or characteristics, as applicable.
Figure 2 — Flow chart for Notice of Change (NOC) submittal
(Design Activity is NOT Authorized to Analyze Changes on Behalf of Customer)
NOTE Design activity does NOT meet criteria of section 5.
Figure 3 — Flow chart for Notice of Change (NOC) submittal
(Design Activity is Authorized to Analyze Changes on Behalf of Customer)
NOTE Design activity meets criteria of section 5.
4.2 Change types
Change types are controlled by the customer and/or design authority. The following are default
categories that shall apply, unless modified or changed by the customer/design authority.
4.2.1 Changes that require customer acceptance prior to implementation
These are changes in design or design information that will always require prior acceptance from the
customer, unless otherwise stated in the contract:
a. Any change that affects product airworthiness or safety.
b. Any change to product function.
c. Any change affecting a SOCD or top-level drawing.
d. Any change to product performance tolerances specified by customer or product definition.
e. Weight, balance, or moment of inertia change outside of specification requirements.
f. Change affecting interchangeability, compatibility, maintainability, or repairability at customer
serviceable level.
g. Electromagnetic characteristics or signature change.
h. Change in product technical data, including Qualification Test Plan (QTP) or Acceptance Test Plan
(ATP); see section 4.2.1.q.
i. Any change in installed software/firmware that changes the software identity or functionality.
j. Change affecting environmental interactions (e.g., use of hazardous/prohibited materials).
k. Change affecting traceability of a required traceable item.
l. Any change to a ‘frozen’ design or process.
m. Change to customer identified ‘critical items’ or ‘key characteristics’.
n. Change that negatively impacts contractual prices, schedules, or deliveries to the customer.
o. Change that positively or negatively impact Failure Modes and Effects Analysis (FMEA) or Failure
Review and Corrective Action System (FRACAS) information originally approved.
p. Any change of electronic or specific component.
q. Any change to tooling or gages used for product acceptance.
4.2.2 Changes that may require customer acceptance prior to implementation
Depending on product definition or customer requirements, these types of changes to design
information may also require prior acceptance from the customer. The customer agreement shall
determine prior acceptance requirements.
a. Change to the BOM.
b. Any change of a special process (type or process).
c. Change of special process sources.
d. Change in sources of supply of sub-components, may include obsolescence.
e. Change in manufacturing methods, including changes to specified tolerances.
f. Change in location of manufacture for the end item.
g. Change to manuals or instructional material which has been provided to the customer (e.g.,
component maintenance manuals, shop manuals).
h. Revision to a repair/modification drawing that changes the baseline configuration, which had been
previously approved by the design holder/design authority.
4.2.3 Changes implemented concurrent with notification for customer acceptance
Changes other than those described in sections 4.2.1, and potentially 4.2.2, may be implemented and
delivered prior to customer acceptance, if the authority to proceed is granted in accordance with
section 5 requirements. Any change to design information that does not require prior customer
acceptance is considered eligible for implementation and requires a NOC record to be created.
Submittal of the NOC record to the customer concurrently for any change is necessary, when required
by the customer/design authority.
If authority for change implementation is not granted from the customer, then changes other than those
defined in sections 4.2.1, and potentially 4.2.2, may be implemented at the risk of the design and
manufacturing activities, but shall not be delivered to the customer pending acceptance.
4.2.4 Changes – non-configuration
Changes to design information that are clerical in nature or are to correct errors in previously approved
design information, and do not effect items listed in sections 4.2.1, 4.2.2, and 4.2.3, do not have to be
reported or documented via the NOC process defined in this European Standard. However, these types
of changes do have to be recorded and documented within the design activities’ configuration
management system and records retained per section 5.5. In addition, the design authority/customer
may negotiate with the design holder/supplier a schedule for notification of non-configuration changes
for information purposes.
Examples of non-configuration changes include:
a. Drawing corrections; bringing records in line with manufacturing practices.
b. Drawing corrections; elimination of clerical/typing/drafting drawing errors.
c. Addition of instructional information and/or inspection requirements to a drawing, but shall not
remove or modify without prior approval.
d. Alteration of non-functional features, as long as, no formal qualification testing is required,
providing that any change does not increase the envelope of the unit or affect unit performance.
e. Addition of dash number to catalogue component drawings; does not affect existing configurations.
f. Supplier order office name and address changes/additions for industry standard catalogue
components and detail parts.
g. Revision of notes to incorporate latest revision of industry standards and supplier company
specifications where there is no impact on configuration or product characteristics or change to
contractual requirements.
h. Addition, selection, or amendment of data/information on drawings not delivered to the customer
where there is no impact on configuration or product characteristics or change to contractual
requirements.
i. Changes to the format of drawings not delivered to the customer [e.g., transfer from paper to
Computer-aided Design (CAD) format].
j. Corrections to component part markings that do not affect traceability.
k. Update of the method of component part marking, but not the contents.
l. Changes that do not require update to design technical data delivered to the customer.
4.3 Change impact analysis tool
In order to assist in proper evaluation of changes, there is an industry-developed tool for the evaluation
of change and configuration change effects. This tool is available at
http://www.sae.org/iaqg/publications/9116toollink.docx and is intended to assist the design activity in
the evaluation of the category of change per section 4.2 with respect to the impact on:
a. Airworthiness (safety).
b. Form.
c. Fit.
d. Function.
e. Mass properties.
f. Environment.
g. Reliability.
h. Drawing, engineering data (e.g., three-dimensional models), or specification changes.
i. Traceability.
j. In-service effects.
k. Producibility or inspectability.
l. Test.
m. Contractual price.
The description of the questions is listed in Annex B; for the most current information, consult the
referenced IAQG website. The requirements as to what constitutes a change are subject to customer
purchase and contract agreements in effect at the time of the product change request.
NOTE The design authority or the customer reserves the right to use an alternative tool or not to use the tool,
based on its applicability to their products.
5 Requirements for organizations to obtain authorization to analyze changes on
behalf of customer
The design activity shall submit a Change Impact Analysis (CIA) and a NOC to the customer, prior to
implementing any change described in sections 4.2.1, 4.2.2, and 4.2.3. However, the design activity shall
meet the criteria requirements of sections 5.1 and 5.2 in order to be authorized to analyze changes
described in section 4.2.3 on behalf of the customer (see Figure 3).
5.1 Quality management system requirements
The design activity shall have a quality management system that contains the following, at a minimum:
a. A design control system that complies with the applicable requirements detailed in the 9100
standard (see section 7.3).
b. A configuration management system that complies with the requirements of EIA – 649 or the 9100
standard (see section 7.1.3).
c. Control of sub-tier supplier changes in accordance with the 9100 standard (see section 7.4.2).
d. Control of nonconforming product in accordance with the 9100 standard (see section 8.3).
e. A corrective action process in accordance with the 9100 standard (see section 8.5.2).
f. Record retention in accordance with the 9100 standard (see section 4.2.4).
5.2 Customer agreements
In order to be eligible for submitting design information changes or change requests concurrently, the
supplier/design activity shall have the following agreements with the customer/design authority, at a
minimum:
a. Baseline definition of each product in compliance with section 4.1.
b. A process for authorization of personnel with the necessary product knowledge to verify design
analysis determinations in terms of change effects.
c. Customer review/acceptance cycle and frequency of submittal of NOCs.
d. A formal approval, including any limitations, from the customer allowing use of the authorization
provisions of this European Standard (see section 5.3).
Additionally, the supplier/design activity shall be subject to approval and reviews by the customer or
design authority for assurance that the requirements of section 5.1 are satisfied and for verification of
change classifications. This includes access to and review of design data, procedures, and records at the
supplier/design activity by the customer/design authority. The method of review and approval is at the
discretion of the customer/design authority.
5.3 Approval of design activity to perform change impact assessments
The approval to perform design change impact assessments, on behalf of the customer/design authority,
is intended for suppliers that design the product. The customer/design authority has the responsibility
to ensure design changes to its products comply with applicable customer and regulatory requirements.
This requires that the customer/design authority maintain the appropriate level of definition, approval,
and oversight of the design change impact assessments performed by supplier/design activities. The
customer/design authority reserves the right for the definition and interpretation of all requirements
associated with these design change impact assessments.
5.3.1 Prerequisites for design activities to perform change impact assessments
Supplier/design activities shall meet the following prerequisites before requesting any level of design
change impact assessments approvals:
a. The supplier/design activity shall have a quality system that complies with the requirements
delineated within section 5.1.
b. The supplier/design activity shall have sufficient design capability recognized by the
customer/design authority for the products for which they are requesting design change impact
assessment approval. Design capability is typically recognized by the customer/design authority
through a contract requirement for design to a specification, SOCD, or other engineering definition.
c. The supplier/design activity shall have Engineering organizations in place, and of sufficient breadth
and capability, as recognized by the customer/design authority, to implement and support the
design change impact assessment system.
d. The supplier/design activity shall have written procedures to implement and support the design
change impact assessment system per section 5.3.3. The procedures, and any subsequent revisions,
shall be submitted to the customer/design authority for approval prior to implementation. The
implementation procedures of the supplier/design activity should be initially submitted for
review/approval with the authorization request letter defined within section 5.3.2.
5.3.2 Requesting and maintaining design change impact assessment approval
a. Supplier/design activities that meet the prerequisites of sections 5.1 and 5.2, shall request design
change impact assessment approval by submitting an authorization request letter to the
customer/design authority to define the scope of the proposed design change impact assessment.
The letter shall identify the type of product being supplied on which the supplier/design activity has
design capability and requests design change impact assessment approval. The letter shall also
identify the applicable supplier/design activity design change impact assessment procedure(s) that
meet the requirements of this European Standard.
b. The customer/design authority will review the supplier/design activity request to determine if it is
within the scope for design change impact assessment approval. If the scope is acceptable, the
customer/design authority will notify the supplier/design activity in writing authorizing the
supplier/design activities’ design change impact assessment approval, at which point the
supplier/design activity may begin performing design change impact assessments on behalf of the
customer/design authority, and within requirements of this European Standard. A record of the
supplier/design activities’ design change impact assessment approval request and customer/design
authority’s authorization letters shall be retained by the supplier/design activity.
c. The supplier/design activity shall submit a new design change impact assessment approval request
letter for changes in scope (e.g., providing a new type of product, additional approval for existing
product).
d. Deviations from the requirements of this European Standard may be requested by the
supplier/design activity through correspondence with the customer/design authority, but shall be
approved by the customer/design authority prior to implementation. Records of any approved
deviations shall be documented and retained by the supplier/design activity.
5.3.3 Design change impact assessment processes and procedures
The supplier/design activity shall maintain processes and procedures that clearly define the
requirements of their overall design change impact assessment system including the following:
a. Design change impact assessment system description.
b. Design change impact assessment system scope of approval identified in section 5.3.2.a.
c. Design change impact assessment system organizational responsibilities and reporting
relationships.
d. Design change impact assessment system forms.
e. Design change impact assessment system personnel listing and any limits on their authority to
conduct design change impact assessment on behalf of the customer/design authority.
f. Design change impact assessment system personnel qualifications including education, experience,
product and process knowledge, training, and training maintenance requirements.
g. Design change impact assessment system records and retention requirements.
The supplier/design activities design change impact assessment processes and procedures shall clearly
define how design change impact assessment authority is given to sub-tier supplier/design activities
and how the requirements of this document are flowed down. The supplier/design activities’ records
shall include a listing of any sub-tier supplier/design activities that have been given design change
impact assessment authority and their applicable design change impact assessment processes, if
applicable.
5.4 Requirements for data submission of notice of change
Data related to the NOC (e.g., content, format, size) should be in accordance with the complete data set
as defined in Annex C, "List of Notice Of Change (NOC) Data". Data may be in either in electronic or
paper form. Mandatory data (in bold and marked with an *) shall be systematically recorded and
transferred to every customer. Optional data (without marking) shall appear when requested by the
customer but may also appear at originator's own needs.
NOTE 1 For any data field recorded and transferred, whether mandatory or optional, not applicable (N/A) shall
be entered as a minimum requirement prior to final approval/signature, if there is no data to be entered.
NOTE 2 Different customers may require different optional data fields tailored to meet contractual
requirements. It is therefore recommended that the Information Technology (IT) System (electronic data storage)
is capable of processing all sets of data (i.e., mandatory, optional). The system should recognize data fields not
effectively used as being inactive, and should be capable of adding new requirements or changing existing
requirements.
The entities responsible for entering and/or approving/acknowledging NOC data shall process the
activities in accordance with the terms and conditions of the contract.
Attached files shall preferably be in a protected format (e.g., pdf, tif, jpg). Formats that can be easily
changed (e.g., doc, xls, ppt) should be avoided, as much as possible, but may be used if necessary. In
such cases, appropriate precautions should be taken to prevent inadvertent changes to the document.
Some data systems actually impose file-size constraints (e.g., maximum 500 kbyte). Due to the fact that
pictures occupy large amounts of electronic memory space, a ’file optimization tool’ (e.g., zip, number of
dpi, appropriate compressed format) shall be used, when feasible, to minimize the size of attached files.
When the NOC is not required in electronic format and/or when it is required as a printout, it shall be in
a linear format similar to the example shown in Annex D, “Sample Notice of Change (NOC) Form”.
However, the size and order of the fields may be changed to suit the individual application provided
that:
a. The box numbers and contents allocation specified in this European Standard are maintained.
b. All mandatory data fields are printed out on the paper form.
c. The form is not changed to the extent that would make it unrecognizable.
d. It is in line with contractual/regulatory requirements.
Forms may be pre-printed, computer generated, or accessed via a net-based system (intranet/internet);
providing in all cases, the printing of lines and characters are clear and legible. The information entered
on the forms shall preferably be machine/computer printed, but may be handwritten as long as block
letters are used and the document remains legible. The use of abbreviations should be kept at a
minimum.
When required, continuation/additional sheets and attachments shall include the same NOC reference
number as the original document.
The information in the data fields shall be in English. Other languages may be acceptable (e.g., bilingual:
English and native language), when in line with contractual requirements.
5.5 Record retention
Change records including NOC data and approvals or acknowledgements shall be retained in
accordance with design data requirements of the customer.
NOTE Typically, design information is required to be retained for 25 years or the service life of the product
plus seven (7) years, whichever is longer. Data should be maintained in either paper or electronic format; the
requirements of ARP9034 should be considered for the storage of data in electronic formats.
6 NOTES
A change bar (|) located in the left margin is for the convenience of the user in locating areas where
technical revisions, not editorial changes, have been made to the previous issue of this document. An
(R) symbol to the left of the document title indicates a complete revision of the document, including
technical revisions. Change bars and (R) are not used in original publications, nor in documents that
contain editorial changes only.
...