49.020 - Aircraft and space vehicles in general
ICS 49.020 Details
Aircraft and space vehicles in general
Luft- und Raumfahrzeuge im allgemeinen
Aéronautique et espace en général
Letala in vesoljska vozila na splošno
General Information
Frequently Asked Questions
ICS 49.020 is a classification code in the International Classification for Standards (ICS) system. It covers "Aircraft and space vehicles in general". The ICS is a hierarchical classification system used to organize international, regional, and national standards, facilitating the search and identification of standards across different fields.
There are 904 standards classified under ICS 49.020 (Aircraft and space vehicles in general). These standards are published by international and regional standardization bodies including ISO, IEC, CEN, CENELEC, and ETSI.
The International Classification for Standards (ICS) is a hierarchical classification system maintained by ISO to organize standards and related documents. It uses a three-level structure with field (2 digits), group (3 digits), and sub-group (2 digits) codes. The ICS helps users find standards by subject area and enables statistical analysis of standards development activities.
e-Library Subscription
Create subscription and get permanent access to documents within 49.020 - Aircraft and space vehicles in general
Currently subscription includes documents marked with .We are working on making all documents available within the subscription.
This document specifies common fundamental concepts for long term archiving and retrieval of mechanical CAD information for elementary parts and assemblies. It details the “fundamentals and concepts” of EN 9300-003:2012 in the specific context of long-term archiving of CAD mechanical models.
Mechanical CAD information is divided into assembly structure and geometrical information, both including explicit and implicit geometrical representation, geometric dimensioning and tolerancing with form features.
The EN 9300-1XX series is organized as a sequence of parts, each building on the previous ones in a consistent way, each adding a level of complexity in the CAD data model. This includes the detailing of relationships between the essential information for the different types of CAD information covered by the EN 9300-1XX series.
As technology matures, additional parts will be released in order to support new requirements within the aerospace community.
1.2 In Scope
This document specifies:
- the fundamentals and concepts for long-term archiving and retrieval of 3D mechanical CAD information;
- the document structure of the EN 9300-1XX series, and the links between all these parts;
- the qualification methods for long-term preservation of archived mechanical CAD information; more specially, principles for the CAD validation properties and for verification of the quality of the CAD archived file;
- specifications for the preservation planning of archived CAD information;
- specific functions for administration and monitoring of CAD archived mechanical models;
- the definition of archive information packages for CAD data.
1.3 Out of scope
The following are out of scope for this part:
- long-term archiving of CAD 2D drawings;
- other CAD specialization disciplines, such as electrical harnesses, composite.
- Standard53 pagesEnglish languagee-Library read for1 day
This document provides means to demonstrate compliance with:
— the “geo-awareness” requirements specified in Part 2 points (13), Part 3 points (15) and Part 4 points (10) of the Commission Delegated Regulation (EU) 2019/945; and to
— the requirement on the smooth interaction of the optional geofencing function with the flight control system of the UA set by Part 2 points (14), Part 3 points (16) and Part 4 points (11) on the optional geofencing function.
This document specifies the minimum performance required from this “geo-awareness” function, without prescribing its design and implementation as far as possible.
Compliance with this document is recommended as one means of assuring that the geo-awareness function will perform its intended sub-functions satisfactorily under all conditions normally encountered in routine aeronautical operation.
Compliance to the “smooth interaction” requirement is, for a large part, addressed by 6.3 on safe controllability of EN 4709-001:2026. This document will therefore refer to it to a large extend.
NOTE In this document, we will use “function” to designate the objects of this specification, and “equipment” to identify the entity implementing this function in whatever form.
- Standard31 pagesEnglish languagee-Library read for1 day
This document provides technical specification and verification method to support compliance with the requirements defined by the product harmonisation legislation set by Chapter II of Commission Delegated Regulation (EU) 2019/945 of 12 March 2019 on unmanned aircraft systems and on thirdcountry operators of unmanned aircraft systems.
This document does not cover UAS lighter than air (e.g. airships and balloons).
This document is only applicable for UA with energy sources based on electro-chemical technologies.
- Standard142 pagesEnglish languagee-Library read for1 day
1.1 In Scope
From Clause 8 to Clause 15, the scope includes:
- Management Information;
- Product Design;
- Change Management;
- Documents;
- Application of PDM-specific metadata (see EN 9300-21);
- Definition of PDM-specific metadata for Archive Information Packages (AIP).
Common Meta Data archive package requirements defined in EN 9300-21.
A visual representation of the scope of this document can be seen in Figure 1. An overview of the various parts in the EN 9300-200 series is provided in Table 1.
[Figure 1 - Scope of EN 9300-210 As Designed]
[Table 1 - EN 9300 Part 200 series]
This document does not attempt to specify how to create an OAIS/LOTAR information package. Nor does it address common issues in the archive domain, such as: snapshot vs. incremental archival methods (which are determined as part of the implementation of an archive system), or package-to-package linkages (Meta Data WG) or how to identify metadata for an archival package (Meta Data WG). Integration of PDM metadata with other domain and common metadata will be in EN 9300-021.
The scope of EN 9300-210 is same as the EN 9300-001.
1.2 Out of scope
This document does not attempt to describe how to create an OAIS/LOTAR information package. Nor does it address common issues in the archive domain, such as: snapshot vs. incremental archival methods (which are determined as part of the implementation of an archive system), or package-to-package linkages (Meta Data WG) or how to identify metadata for an archival package (Meta Data WG). For integration of PDM metadata with other domain and common metadata, see EN 9300-21.
- Standard38 pagesEnglish languagee-Library read for1 day
This document specifies common fundamental concepts for long term archiving and retrieval of mechanical CAD information for elementary parts and assemblies. It details the “fundamentals and concepts” of EN 9300-003:2012 in the specific context of long-term archiving of CAD mechanical models.
Mechanical CAD information is divided into assembly structure and geometrical information, both including explicit and implicit geometrical representation, geometric dimensioning and tolerancing with form features.
The EN 9300-1XX series is organized as a sequence of parts, each building on the previous ones in a consistent way, each adding a level of complexity in the CAD data model. This includes the detailing of relationships between the essential information for the different types of CAD information covered by the EN 9300-1XX series.
As technology matures, additional parts will be released in order to support new requirements within the aerospace community.
1.2 In Scope
This document specifies:
- the fundamentals and concepts for long-term archiving and retrieval of 3D mechanical CAD information;
- the document structure of the EN 9300-1XX series, and the links between all these parts;
- the qualification methods for long-term preservation of archived mechanical CAD information; more specially, principles for the CAD validation properties and for verification of the quality of the CAD archived file;
- specifications for the preservation planning of archived CAD information;
- specific functions for administration and monitoring of CAD archived mechanical models;
- the definition of archive information packages for CAD data.
1.3 Out of scope
The following are out of scope for this part:
- long-term archiving of CAD 2D drawings;
- other CAD specialization disciplines, such as electrical harnesses, composite.
- Standard53 pagesEnglish languagee-Library read for1 day
1.1 In Scope
From Clause 8 to Clause 15, the scope includes:
- Management Information;
- Product Design;
- Change Management;
- Documents;
- Application of PDM-specific metadata (see EN 9300-21);
- Definition of PDM-specific metadata for Archive Information Packages (AIP).
Common Meta Data archive package requirements defined in EN 9300-21.
A visual representation of the scope of this document can be seen in Figure 1. An overview of the various parts in the EN 9300-200 series is provided in Table 1.
[Figure 1 - Scope of EN 9300-210 As Designed]
[Table 1 - EN 9300 Part 200 series]
This document does not attempt to specify how to create an OAIS/LOTAR information package. Nor does it address common issues in the archive domain, such as: snapshot vs. incremental archival methods (which are determined as part of the implementation of an archive system), or package-to-package linkages (Meta Data WG) or how to identify metadata for an archival package (Meta Data WG). Integration of PDM metadata with other domain and common metadata will be in EN 9300-021.
The scope of EN 9300-210 is same as the EN 9300-001.
1.2 Out of scope
This document does not attempt to describe how to create an OAIS/LOTAR information package. Nor does it address common issues in the archive domain, such as: snapshot vs. incremental archival methods (which are determined as part of the implementation of an archive system), or package-to-package linkages (Meta Data WG) or how to identify metadata for an archival package (Meta Data WG). For integration of PDM metadata with other domain and common metadata, see EN 9300-21.
- Standard38 pagesEnglish languagee-Library read for1 day
1.1 General
This document establishes the minimum requirements for the qualification and certification of personnel performing nondestructive testing (NDT), nondestructive inspection (NDI), or nondestructive evaluation (NDE) in the aerospace manufacturing, service, maintenance and overhaul industries. For the purposes of this document, the term NDT will be used and will be considered equivalent to NDI and NDE.
In Europe, the term "approval" is used to denote a written statement by an employer that an individual has met specific requirements and has operating approval. The term "certification" as defined in 3.3 is used throughout this document as a substitute for the term "approval". Except when otherwise specified in the written practice, certification in accordance with this document includes operating approval.
1.2 Purpose
1.2.1 Applicability
This document applies to personnel who:
- use NDT methods or equipment to test and/or accept materials, products, components, assemblies or sub-assemblies;
- are directly responsible for the technical adequacy of the NDT methods and equipment used;
- operate automatic interpretation or evaluation systems;
- approve NDT procedures or work instructions;
- audit NDT facilities; or
- provide technical NDT support or training.
This document does not apply to individuals who only have administrative or supervisory authority over NDT personnel or to research personnel developing NDT technology for subsequent implementation and approval by a certified Level 3. See Clause 8 regarding applicability to personnel performing specialized inspections using certain direct readout instruments.
1.2.2 Implementation
This document addresses the use of a National Aerospace NDT Board (NANDTB). NANDTBs are only used as specified per Annex C and it is not mandatory to have such a board for compliance with this document. Personnel certified to previous revisions of NAS410/EN 4179 need not recertify to the requirements of this document until their current certification expires.
1.2.3 NDT methods
This document contains detailed requirements for the following NDT methods:
eddy current testing (ET)
penetrant testing (PT)
magnetic particle testing (MT)
radiographic testing (RT)
shearography testing (ST)
thermographic testing (IRT)
ultrasonic testing (UT)
When invoked by engineering, quality, cognizant engineering organization or prime contractor requirements, this document applies to other NDT methods used to determine the acceptability or suitability for intended service of a material, part, component, sub-assembly or assembly. Such methods can include, but are not limited to, acoustic emission, neutron radiography, leak testing, and holography.
- Standard39 pagesEnglish languagee-Library read for1 day
1.1 General
This document establishes the minimum requirements for the qualification and certification of personnel performing nondestructive testing (NDT), nondestructive inspection (NDI), or nondestructive evaluation (NDE) in the aerospace manufacturing, service, maintenance and overhaul industries. For the purposes of this document, the term NDT will be used and will be considered equivalent to NDI and NDE.
In Europe, the term "approval" is used to denote a written statement by an employer that an individual has met specific requirements and has operating approval. The term "certification" as defined in 3.3 is used throughout this document as a substitute for the term "approval". Except when otherwise specified in the written practice, certification in accordance with this document includes operating approval.
1.2 Purpose
1.2.1 Applicability
This document applies to personnel who:
- use NDT methods or equipment to test and/or accept materials, products, components, assemblies or sub-assemblies;
- are directly responsible for the technical adequacy of the NDT methods and equipment used;
- operate automatic interpretation or evaluation systems;
- approve NDT procedures or work instructions;
- audit NDT facilities; or
- provide technical NDT support or training.
This document does not apply to individuals who only have administrative or supervisory authority over NDT personnel or to research personnel developing NDT technology for subsequent implementation and approval by a certified Level 3. See Clause 8 regarding applicability to personnel performing specialized inspections using certain direct readout instruments.
1.2.2 Implementation
This document addresses the use of a National Aerospace NDT Board (NANDTB). NANDTBs are only used as specified per Annex C and it is not mandatory to have such a board for compliance with this document. Personnel certified to previous revisions of NAS410/EN 4179 need not recertify to the requirements of this document until their current certification expires.
1.2.3 NDT methods
This document contains detailed requirements for the following NDT methods:
eddy current testing (ET)
penetrant testing (PT)
magnetic particle testing (MT)
radiographic testing (RT)
shearography testing (ST)
thermographic testing (IRT)
ultrasonic testing (UT)
When invoked by engineering, quality, cognizant engineering organization or prime contractor requirements, this document applies to other NDT methods used to determine the acceptability or suitability for intended service of a material, part, component, sub-assembly or assembly. Such methods can include, but are not limited to, acoustic emission, neutron radiography, leak testing, and holography.
- Standard39 pagesEnglish languagee-Library read for1 day
The scope of the present document is to provide the elements needed for elaborating the programme execution logic and drafting the execution plan for the realization of a product.
NOTE 1 In this document, the term “logic” alone is sometimes used for “execution logic”.
NOTE 2 In this document, the term “product” is used to designate the object of the program concerned, and the term “system” is used to designate the product for anything related to system engineering.
NOTE 3 The product is also considered a “system-of-interest” and its enabling systems are also taken into account.
The execution logic and plan enable customers/suppliers to reach an agreement on how their respective processes and activities can be organized.
The aim is to enable each actor in the programme to manage their activities with sufficient visibility of the sequencing of the other stakeholdersʼ activities.
This document belongs to the documents supporting EN 9200 relating to the programme management specification.
The present document describes the principles of programme execution logic and defines the corresponding management requirements. This description is supplemented:
— on the one hand, in terms of execution logic principles, by:
— the challenges of a basic logic common to all actors (synchronization);
— the applicable criteria to set up this basic logic;
— the translation of this logic into the programme processes;
— on the other hand, in terms of implementing the execution logic, by:
— the procedures for practical implementation of the management requirements defined in EN 9200;
— adaptations of the logic according to the various constraints and specificities of the programme, and justification of these adaptations;
— the consistency between the basic logic at system level and the logics at subsystem and constituent levels.
The breakdown of clauses as used in this document gives a gradual understanding of the approach to be adopted to construct an execution logic. For instance:
— Clause 5 presents the end-purpose of a programme execution logic as well as the associated basic concepts and the constituents of this logic;
— Clause 6 describes and characterizes the process for building the logic;
— Clause 7 concerns change control to the execution logic;
— Clause 8 concentrates on the importance of capitalization and lessons learned.
This document applies to aeronautical, space and defence programmes. The principles can be extended to other areas of activity.
It applies to realization of a single product, of several samples or of a series. It applies to any customer/supplier level, while ensuring consistency between successive levels.
The principles described concern all programme actors, from initial expression of need through to closure of the programme.
- Standard47 pagesEnglish languagee-Library read for1 day
The purpose of this document is to:
— identify and describe, in a structured way, the principles of the integrated logistic support (ILS) activities and tasks for the main types of stakeholders in the system life cycle, from the expression of need to disposal;
— place the activities, tasks and ILS deliverables within the programme execution;
— identify the main selection and sizing of activities and tasks criteria according to the nature and the requirements of the programme;
— control the relations with the other aspects of programme management.
This document covers the following subjects:
— management of ILS (definition, implementation and running of the processes);
— expression of the support requirements;
— elaboration of the contracts (e.g. for development, maintenance, supply);
— implementation of the tasks and processes.
This document is also related to the following subjects:
— relations with costs and lead times control, configuration management, performance and RAMS management, quality assurance, documentation management;
— regulations (e.g. information system security, export controls, safety at work);
— human and organizational factors (HOF);
— environment (e.g. RoHS, REACh);
— information systems (IS) and the links between them;
— logistics information systems (LIS);
— in-service support (ISS) activities;
— configuration management of ILS objects;
— life cycle.
The following stakeholders are concerned by ILS:
— users in the broadest sense: operators, maintenance operators, administrators, dismantlers of the system, trainers;
— the customer, who:
— prepares technical and contractual specifications of need with which the system will comply;
— sets up the funding of the programme;
— oversees the realization and commissioning of the main system and of the support system;
— facilitates the feedback.
NOTE 1 At the highest level of the system, the customer can also be referred to as the “project owner”.
NOTE 2 The “main system” can also be referred to as the “system of interest”.
— the supplier(s) who deliver a system (main and support) to the customer, which meets the performance specifications on time and for the agreed cost, throughout the system life cycle;
NOTE 3 At the highest level of the system, the supplier can also be referred to as the “industrial prime contractor”.
— the regulatory authorities that supervise and approve the support processes and equipment, as needed.
The principles laid down in this document can be applied, after adaptation, to all the customer/supplier relations resulting from the breakdown of the main contract into sub-contracts.
- Standard41 pagesEnglish languagee-Library read for1 day
The scope of the present document is to provide the elements needed for elaborating the programme execution logic and drafting the execution plan for the realization of a product.
NOTE 1 In this document, the term “logic” alone is sometimes used for “execution logic”.
NOTE 2 In this document, the term “product” is used to designate the object of the program concerned, and the term “system” is used to designate the product for anything related to system engineering.
NOTE 3 The product is also considered a “system-of-interest” and its enabling systems are also taken into account.
The execution logic and plan enable customers/suppliers to reach an agreement on how their respective processes and activities can be organized.
The aim is to enable each actor in the programme to manage their activities with sufficient visibility of the sequencing of the other stakeholdersʼ activities.
This document belongs to the documents supporting EN 9200 relating to the programme management specification.
The present document describes the principles of programme execution logic and defines the corresponding management requirements. This description is supplemented:
— on the one hand, in terms of execution logic principles, by:
— the challenges of a basic logic common to all actors (synchronization);
— the applicable criteria to set up this basic logic;
— the translation of this logic into the programme processes;
— on the other hand, in terms of implementing the execution logic, by:
— the procedures for practical implementation of the management requirements defined in EN 9200;
— adaptations of the logic according to the various constraints and specificities of the programme, and justification of these adaptations;
— the consistency between the basic logic at system level and the logics at subsystem and constituent levels.
The breakdown of clauses as used in this document gives a gradual understanding of the approach to be adopted to construct an execution logic. For instance:
— Clause 5 presents the end-purpose of a programme execution logic as well as the associated basic concepts and the constituents of this logic;
— Clause 6 describes and characterizes the process for building the logic;
— Clause 7 concerns change control to the execution logic;
— Clause 8 concentrates on the importance of capitalization and lessons learned.
This document applies to aeronautical, space and defence programmes. The principles can be extended to other areas of activity.
It applies to realization of a single product, of several samples or of a series. It applies to any customer/supplier level, while ensuring consistency between successive levels.
The principles described concern all programme actors, from initial expression of need through to closure of the programme.
- Standard47 pagesEnglish languagee-Library read for1 day
This document specifies a test procedure to identify performance characteristics and a weight rating of convection and steam ovens used on aircraft. Furthermore, it specifies the calculation procedure to determine an energy consumption index and a performance index. There is no direct correlation between the ECO efficiency and cooking performance in terms of food quality and appearance. The two index values represent the ECO efficiency.
- Standard11 pagesEnglish languagee-Library read for1 day
The purpose of this document is to:
— identify and describe, in a structured way, the principles of the integrated logistic support (ILS) activities and tasks for the main types of stakeholders in the system life cycle, from the expression of need to disposal;
— place the activities, tasks and ILS deliverables within the programme execution;
— identify the main selection and sizing of activities and tasks criteria according to the nature and the requirements of the programme;
— control the relations with the other aspects of programme management.
This document covers the following subjects:
— management of ILS (definition, implementation and running of the processes);
— expression of the support requirements;
— elaboration of the contracts (e.g. for development, maintenance, supply);
— implementation of the tasks and processes.
This document is also related to the following subjects:
— relations with costs and lead times control, configuration management, performance and RAMS management, quality assurance, documentation management;
— regulations (e.g. information system security, export controls, safety at work);
— human and organizational factors (HOF);
— environment (e.g. RoHS, REACh);
— information systems (IS) and the links between them;
— logistics information systems (LIS);
— in-service support (ISS) activities;
— configuration management of ILS objects;
— life cycle.
The following stakeholders are concerned by ILS:
— users in the broadest sense: operators, maintenance operators, administrators, dismantlers of the system, trainers;
— the customer, who:
— prepares technical and contractual specifications of need with which the system will comply;
— sets up the funding of the programme;
— oversees the realization and commissioning of the main system and of the support system;
— facilitates the feedback.
NOTE 1 At the highest level of the system, the customer can also be referred to as the “project owner”.
NOTE 2 The “main system” can also be referred to as the “system of interest”.
— the supplier(s) who deliver a system (main and support) to the customer, which meets the performance specifications on time and for the agreed cost, throughout the system life cycle;
NOTE 3 At the highest level of the system, the supplier can also be referred to as the “industrial prime contractor”.
— the regulatory authorities that supervise and approve the support processes and equipment, as needed.
The principles laid down in this document can be applied, after adaptation, to all the customer/supplier relations resulting from the breakdown of the main contract into sub-contracts.
- Standard41 pagesEnglish languagee-Library read for1 day
This document specifies a test procedure to identify performance characteristics and a weight rating of convection and steam ovens used on aircraft. Furthermore, it specifies the calculation procedure to determine an energy consumption index and a performance index. There is no direct correlation between the ECO efficiency and cooking performance in terms of food quality and appearance. The two index values represent the ECO efficiency.
- Standard11 pagesEnglish languagee-Library read for1 day
The purpose of this document is to:
— remind the end-purpose of the development phase (see Clause 5);
— precise the content and outcomes of a development plan (see Clause 6).
This document is a supporting document that supplements EN 9241 regarding the specific aspects to be taken into account in the development plan.
The iteratively realized development plan is consistent with the documents identified in 6.2.2.
This document applies to each level of the product breakdown structure. In particular, it takes into account the customer/supplier relationships.
- Standard14 pagesEnglish languagee-Library read for1 day
This document comprehensively examines information grounded in International Standards applicable to uncrewed aircraft system (UAS) traffic management (UTM) systems and the operational frameworks for UTM systems across various countries. It systematically catalogues the current entities involved in UTM systems, including the actors, services, functions and data. Additionally, it delineates the safety, security and quality specifications for these services, focusing on data management and referring, where appropriate, to standards developed by other standard development organizations (SDOs).
- Technical report30 pagesEnglish languagesale 15% off
The purpose of this document is to:
- remind the end-purpose of the development phase (see Clause 5);
- precise the content and outcomes of a development plan (see Clause 6).
This document is a supporting document that supplements RG.Aero 000 41 regarding the specific aspects to be taken into account in the development plan.
The iteratively realized development plan is consistent with the documents identified in 6.2.2.
This document applies to each level of the product breakdown structure. In particular, it takes into account the customer/supplier relationships.
- Standard14 pagesEnglish languagee-Library read for1 day
This document specifies a test procedure to identify performance characteristics and a weight rating for espresso makers used on a commercial aircraft. Furthermore it specifies the calculation procedure to determine an energy consumption index and a performance index. The effect of the espresso makers on espresso quality is not addressed in this document.
- Standard11 pagesEnglish languagee-Library read for1 day
This document specifies a test procedure to identify performance characteristics and trash volume capacity rating of trash compactors used on a commercial aircraft. Furthermore it specifies the calculation procedure to determine an energy consumption index and a performance index.
- Standard10 pagesEnglish languagee-Library read for1 day
This document specifies a test procedure to identify performance characteristics and a weight rating of beverage maker products used on aircraft. Furthermore it specifies the calculation procedure to determine an energy consumption index and a performance index. The effect of the beverage makers on beverage quality is not addressed in this document.
- Standard11 pagesEnglish languagee-Library read for1 day
This document specifies a test procedure to identify performance characteristics and a weight rating for espresso makers used on a commercial aircraft. Furthermore it specifies the calculation procedure to determine an energy consumption index and a performance index. The effect of the espresso makers on espresso quality is not addressed in this document.
- Standard11 pagesEnglish languagee-Library read for1 day
This document specifies a test procedure to identify performance characteristics and trash volume capacity rating of trash compactors used on a commercial aircraft. Furthermore it specifies the calculation procedure to determine an energy consumption index and a performance index.
- Standard10 pagesEnglish languagee-Library read for1 day
This document specifies a test procedure to identify performance characteristics and a weight rating of a galley chilling equipment used on aircraft. Furthermore it specifies the calculation procedure to determine an energy consumption index and a performance index. The effect of the chilling equipment on food quality is not addressed in this document.
- Standard13 pagesEnglish languagee-Library read for1 day
This document specifies a test procedure to identify performance characteristics and a weight rating of beverage maker products used on aircraft. Furthermore it specifies the calculation procedure to determine an energy consumption index and a performance index. The effect of the beverage makers on beverage quality is not addressed in this document.
- Standard11 pagesEnglish languagee-Library read for1 day
This document specifies the test procedures and calculations to determine the ECO efficiency of the following catering equipment installed in an aircraft:
— chilling equipment (with and without freeze function);
— ovens (steam and convection ovens);
— beverage makers (coffee makers, water heaters);
— trash compactors (single and double bin);
— espresso makers (grain, powder, pad and capsule based).
Based on the results it will be possible to derive the energy consumption index and a performance index of the considered equipment type. The two index values represent the ECO efficiency.
- Standard19 pagesEnglish languagee-Library read for1 day
This document describes minimum requirements for small spacecraft. This document covers different categories of small spacecraft – so-called mini-, micro-, nano-, pico- and femto-, as well as CubeSat, spacecraft. Therefore, for the sake of convenience, the term “small spacecraft” is used throughout this document as a generic term. This document can be applied by small spacecraft developers, as well as dispenser providers and launch operators.
- Standard6 pagesEnglish languagesale 15% off
This document defines terms relating to uncrewed aircraft systems that are widely used in science and technology.
- Standard10 pagesEnglish languagesale 15% off
This document defines the common terms, abbreviations and references used throughout the EN 9300 series of standard parts.
- Standard41 pagesEnglish languagee-Library read for1 day
The purpose of this document is to provide customers and their suppliers with a document specifying the notions of product reliability "construction" and "management".
It offers programme directors and project managers information likely to help them:
- determine the tasks to be performed and the application procedures, according to the specific nature of the programme and its goals;
- define and implement the provisions necessary for performing these tasks;
- within programme execution, situate the various tasks involved in constructing and managing the reliability of a product.
This document applies to all programmes (in particular aeronautical, space and armament programmes).
These reliability construction procedures concern not only all the products and its constituents covered by these programmes, but also the means and manufacturing processes to be implemented for their realization.
The provisions of this document can be negotiated at all levels between the parties directly concerned by a given programme. This implies, on the part of the customer, that each lower level is provided with the information necessary to perform tasks and meet the specified targets.
- Standard30 pagesEnglish languagee-Library read for1 day
The purpose of this document is to provide customers and their suppliers with a document specifying the notions of “construction” and “management” of product dependability and safety (RAMS).
It offers programme directors and project managers information likely to help them:
— determine the tasks to be performed and the application procedures, according to the specific nature of the programme and its goals;
— define and implement the provisions necessary for performing these tasks;
— within programme execution, situate the various tasks involved in constructing and managing the RAMS of a product.
This document applies to all programmes that involve customer/supplier relation.
RAMS management concerns not only all the products covered by these programmes, but also the components of these products and the production and support resources and processes to be implemented.
The provisions of this document can be negotiated at all levels between the parties directly concerned by a given programme. This implies, on the part of the ordering parties, that each lower level is provided with the information needed to perform the tasks and meet the specified targets. This also implies, on the part of suppliers, an escalation of information pertaining to the RAMS results of the products for which they are responsible.
This document is mainly concerned with the technical aspects, aspects of a legislative (in particular safety at work and regulatory conformity) and confidential nature are not dealt with in this document.
- Standard44 pagesEnglish languagee-Library read for1 day
This document defines the common terms, abbreviations and references used throughout the EN 9300 series of standard parts.
- Standard41 pagesEnglish languagee-Library read for1 day
This document specifies the requirements for the effective control of non-deliverable software. This document can be used during the design, development, test, production, release, use, maintenance, and retirement of non-deliverable software. This can include non-deliverable software procured from external suppliers and utilized in the design, production, evaluation, test, acceptance, or calibration of a deliverable product.
This document focuses solely on the unique requirements of the operational processes that pertain to non-deliverable software as identified below:
This document applies to non-deliverable software (including firmware) that affects a deliverable product or service. Following are several applications and supporting examples of non-deliverable software that is within the scope of this document:
— design and development: modelling, simulation, virtual reality, virtual machine, computer-aided design (CAD), three-dimensional (3D) modelling and analysis tools, software compiler, and code generators;
— manufacturing: additive manufacturing, computer numerical controlled (CNC) programs, robotics, factory automation, tools that load deliverable software, software used in special process (e.g. heat treat, shot peen, sonic wall inspection), and automated manufacturing software (i.e. pick and place);
— verification, validation and maintenance: coordinate measuring machine (CMM) programs, hardware or software qualification, code coverage, test scripts, analysis tools, acceptance test, production acceptance, calibration (inspection, test or calibration), simulator, emulator, and software used in post-delivery service provisions.
The following types of software are not within scope of this document:
— deliverable software (refer to EN 9115);
— manufacturing and measuring equipment embedded software (e.g. operating system, drivers);
— enterprise or office software (e.g. MS Office, word processing or spreadsheet applications, Teams, network software, email, employee management system).
Operational processes not covered in this document are addressed by the respective organization’s quality management system (QMS), based on the EN 9100-series (i.e. EN 9100, EN 9110, EN 9120) and/or ISO 9001 standards.
- Standard14 pagesEnglish languagee-Library read for1 day
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.
[...]
- Standard38 pagesEnglish languagee-Library read for1 day
This document specifies the requirements for the effective control of non-deliverable software. This document can be used during the design, development, test, production, release, use, maintenance, and retirement of non-deliverable software. This can include non-deliverable software procured from external suppliers and utilized in the design, production, evaluation, test, acceptance, or calibration of a deliverable product.
This document focuses solely on the unique requirements of the operational processes that pertain to non-deliverable software as identified below:
This document applies to non-deliverable software (including firmware) that affects a deliverable product or service. Following are several applications and supporting examples of non-deliverable software that is within the scope of this document:
— design and development: modelling, simulation, virtual reality, virtual machine, computer-aided design (CAD), three-dimensional (3D) modelling and analysis tools, software compiler, and code generators;
— manufacturing: additive manufacturing, computer numerical controlled (CNC) programs, robotics, factory automation, tools that load deliverable software, software used in special process (e.g. heat treat, shot peen, sonic wall inspection), and automated manufacturing software (i.e. pick and place);
— verification, validation and maintenance: coordinate measuring machine (CMM) programs, hardware or software qualification, code coverage, test scripts, analysis tools, acceptance test, production acceptance, calibration (inspection, test or calibration), simulator, emulator, and software used in post-delivery service provisions.
The following types of software are not within scope of this document:
— deliverable software (refer to EN 9115);
— manufacturing and measuring equipment embedded software (e.g. operating system, drivers);
— enterprise or office software (e.g. MS Office, word processing or spreadsheet applications, Teams, network software, email, employee management system).
Operational processes not covered in this document are addressed by the respective organization’s quality management system (QMS), based on the EN 9100-series (i.e. EN 9100, EN 9110, EN 9120) and/or ISO 9001 standards.
- Standard14 pagesEnglish languagee-Library read for1 day
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.
[...]
- Standard38 pagesEnglish languagee-Library read for1 day
This document specifies safety and quality requirements for detection and avoidance (DAA) systems used between uncrewed aircraft systems (UAS) and other objects including aircraft. This document includes the requirements for radars and optical sensors used for DAA and is derived to meet the requirements for UAS operations involving DAA set out in ISO 21384-3.
- Standard16 pagesEnglish languagesale 15% off
The aim of a MIF and the associated justifications is to ensure that manufacturing and/or inspection operations are realized in a compliant and reproducible manner.
The purpose of this document is to provide a guide to the elaboration of the MIF and the associated justifications by:
— positioning them within the framework:
o of a programme and its objectives, on the one hand;
o of the realization of a product, on the other;
— describing, until production of the product ceases:
o the principles and conditions applying to the elaboration and then the validation of the MIF within the framework of the industrialization process;
o the principles and conditions applying to the elaboration and then the validation of the MIJF associated with the MIF, within the framework of the industrialization process;
o the principles and change and control conditions applying to the MIF and the MIJF.
This document can be used for all processes or sets of processes implemented on a tangible product, which may incorporate software associated with the product. It does not apply to purely software product, commercial-off-the-shelf product (catalogue part) or service (intangible product).
This document applies more particularly to serial production. Nevertheless, the principles and conditions set forth in this document may be applied, making any necessary adaptations, to unit production or to the realization of products to meet development needs (prototypes, demonstrators, etc.).
This document covers the MIF and the MIJF of a product, including the activities related to procurement and the associated industrial means in particular.
- Standard51 pagesEnglish languagee-Library read for1 day
The aim of a MIF and the associated justifications is to ensure that manufacturing and/or inspection operations are realized in a compliant and reproducible manner.
The purpose of this document is to provide a guide to the elaboration of the MIF and the associated justifications by:
— positioning them within the framework:
o of a programme and its objectives, on the one hand;
o of the realization of a product, on the other;
— describing, until production of the product ceases:
o the principles and conditions applying to the elaboration and then the validation of the MIF within the framework of the industrialization process;
o the principles and conditions applying to the elaboration and then the validation of the MIJF associated with the MIF, within the framework of the industrialization process;
o the principles and change and control conditions applying to the MIF and the MIJF.
This document can be used for all processes or sets of processes implemented on a tangible product, which may incorporate software associated with the product. It does not apply to purely software product, commercial-off-the-shelf product (catalogue part) or service (intangible product).
This document applies more particularly to serial production. Nevertheless, the principles and conditions set forth in this document may be applied, making any necessary adaptations, to unit production or to the realization of products to meet development needs (prototypes, demonstrators, etc.).
This document covers the MIF and the MIJF of a product, including the activities related to procurement and the associated industrial means in particular.
- Standard51 pagesEnglish languagee-Library read for1 day
This document specifies field measurements of spray deposition to determine the quantity and distribution of spray in a plane surface area in the transverse direction to the flight direction, treated by specific Unmanned Agricultural Aerial Sprayer (UAAS) with downward directed application. These field measurements can be used to determine the effective swath width of UAAS. This document is not appropriate for evaluating spray deposition within a crop canopy (three-dimensional deposition). It is not appropriate for those spraying systems which rely on the presence of a crop canopy for efficient spray deposition (for example directed spraying, electrostatic charged spraying, very fine sprays).
- Standard28 pagesEnglish languagesale 15% off
- Standard30 pagesFrench languagesale 15% off
- Amendment13 pagesEnglish languagee-Library read for1 day
This document defines the structure and content for the long-term preservation of digital product and technical data. EN 9300 is broken into a series of separate standard parts to make the standard applicable for different business requirements and extensible for further long-term archiving formats.
The following outlines the total scope of this document:
- for the purpose of this document, structure, and content of EN 9300 standard parts are detailed.
- Standard16 pagesEnglish languagee-Library read for1 day
The objective of this document is to present the results of the tests defined in the IEC 61108-7 draft [1] performed with a maritime receiver updated based on the SBAS maritime guidelines [2] and other GNSS SBAS receivers.
The list of test scenarios prepared, the receiver analysed, the configuration used and procedures are included in Clause 4. In Clause 5, graphical and numerical results for each of the test performed are presented, including if the tests are passed or failed. Annex A provides additional information on the test case setup.
- Technical report75 pagesEnglish languagee-Library read for1 day
This document defines the structure and content for the long-term preservation of digital product and technical data. EN 9300 is broken into a series of separate standard parts to make the standard applicable for different business requirements and extensible for further long-term archiving formats.
The following outlines the total scope of this document:
- for the purpose of this document, structure, and content of EN 9300 standard parts are detailed.
- Standard16 pagesEnglish languagee-Library read for1 day
This document enables the specific needs of the aeronautical, space and defence fields to be met. It can also apply to other fields.
However, the specificity of some fields can lead to the use of existing sectorial standards such as EN 16601-80, Space project management - Risk management (derived from ECSS-M-80).
This document:
- proposes a framework for implementing organization of risk management and opportunity management within programme management; this framework may serve as a basis for writing risk management specifications and opportunity management specifications;
- describes a process for keeping programme risks within the defined limitations that are considered tolerable; this standard process can be used as a methodological guide for writing the programme risk control plan;
- describes a process for addressing and developing opportunities that have positive consequences on the execution of a programme; this standard process can be used as a methodological guide for writing the strategic programme opportunity control plan;
- recognizes the need for knowledge management in order to capitalize and to share lessons learned with other programmes, as well as the maturity assessment of the risk management and opportunity management processes;
- identifies useful documents for risk management and opportunity management;
- proposes an example of a typical list of risks and opportunities.
- Standard70 pagesEnglish languagee-Library read for1 day
This document enables the specific needs of the aeronautical, space and defence fields to be met. It can also apply to other fields.
However, the specificity of some fields can lead to the use of existing sectorial standards such as EN 16601-80, Space project management - Risk management (derived from ECSS-M-80).
This document:
- proposes a framework for implementing organization of risk management and opportunity management within programme management; this framework may serve as a basis for writing risk management specifications and opportunity management specifications;
- describes a process for keeping programme risks within the defined limitations that are considered tolerable; this standard process can be used as a methodological guide for writing the programme risk control plan;
- describes a process for addressing and developing opportunities that have positive consequences on the execution of a programme; this standard process can be used as a methodological guide for writing the strategic programme opportunity control plan;
- recognizes the need for knowledge management in order to capitalize and to share lessons learned with other programmes, as well as the maturity assessment of the risk management and opportunity management processes;
- identifies useful documents for risk management and opportunity management;
- proposes an example of a typical list of risks and opportunities.
- Standard70 pagesEnglish languagee-Library read for1 day
This document specifies minimum requirements for life rafts carried on helicopters operating in a hostile sea area or over very rough sea conditions. Life rafts covered by this document are for use by helicopter crew members and passengers in the event of a ditching or water impact.
They are intended either for integration into the helicopter, or stowed in the cabin before being manhandled out of the helicopter. This document does not cover air-drop life rafts.
- Standard54 pagesEnglish languagee-Library read for1 day
This document specifies minimum requirements for life rafts carried on helicopters operating in a hostile sea area or over very rough sea conditions. Life rafts covered by this document are for use by helicopter crew members and passengers in the event of a ditching or water impact.
They are intended either for integration into the helicopter, or stowed in the cabin before being manhandled out of the helicopter. This document does not cover air-drop life rafts.
- Standard54 pagesEnglish languagee-Library read for1 day
This document provides a report on tests that were performed to ensure the "safety and quality" requirements of detection and avoidance (DAA) systems used between UASs and other objects, including aircraft. This document describes test methods and the results of related experiments, which successfully meet the requirements of a DAA system architecture with radar and optical sensors.
- Technical report15 pagesEnglish languagesale 15% off
1.1 General
This document establishes the requirements for performing and documenting FAI. It is emphasized the requirements specified in this document are complementary (not alternative) to customer and applicable statutory and regulatory requirements.
1.2 Purpose
The primary purpose of FAI is to verify and validate product realization processes are capable of producing characteristics that meet engineering and design requirements. A well-planned and executed FAI by a multi-disciplinary team (e.g. members from responsible functions) provides objective evidence the manufacturer’s processes can produce compliant product; having effectively understood and incorporated the associated requirements.
NOTE A FAI is not a product acceptance document. While interrelated, FAI and product acceptance are separate activities. The focus of FAI is verification of production processes via assessment of product. FAI and supporting documentation do not provide assurance regarding conformance for product acceptance purposes; neither does the lack of a FAI necessarily imply product is nonconforming to engineering and design requirements.
FAI will:
- provide confidence, through objective evidence, the product realization processes are capable of producing conforming product;
- demonstrate the manufacturers and processors of the product have an understanding of the associated requirements;
- provide assurance of product conformance at the start of production and after changes, as outlined in this document.
A FAI is intended to:
- mitigate risks associated with production startup and process changes;
- reduce future escapes;
- help ensure product safety;
- improve quality, delivery, and customer satisfaction;
- reduce costs and production delays associated with product nonconformances;
- identify product realization processes not capable of producing conforming characteristics and initiate and/or validate associated corrective actions.
-
1.3 Application
This document applies to organizations and their suppliers responsible for product realization processes that produce the design characteristics of the product. The organization shall flow down the requirements of this document to suppliers who produce design characteristics.
This document also applies to suppliers performing special process(es). A certificate of conformance (CoC) provided by processors attests to satisfying the requirements. External suppliers providing special process(es) can satisfy this document's requirements by either:
- documenting the design characteristics and associated results on a first article inspection report (FAIR); or
- documenting the design characteristics and associated results on a detailed CoC.
This document applies to assemblies, sub-assemblies, and detail parts including castings, forgings, and modifications to standard catalogue or commercial-off-the-shelf (COTS) items. Each of these items have a separate FAI.
Unless contractually required, this document does not apply to:
- development and prototype parts that are not considered as part of the first production run;
- procured standard catalogue item, COTS, or deliverable software. When these items are included in an assembly, they shall be documented in the index of part numbers in an assembly FAIR.
1.4 Informative
If there is a conflict between the requirements of this document, and customer or applicable statutory/regulatory requirements, the latter takes precedence.
In this document, the following verbal forms are used:
- "shall" indicates a requirement;
- "should" indicates a recommendation;
- "may" indicates a permission;
- "can" indicates a possibility or a capability.
Information marked as "NOTE" is for guidance in understanding or clarifying the associated requirement .
- Standard28 pagesEnglish languagee-Library read for1 day
1.1 General
This document establishes the requirements for performing and documenting FAI. It is emphasized the requirements specified in this document are complementary (not alternative) to customer and applicable statutory and regulatory requirements.
1.2 Purpose
The primary purpose of FAI is to verify and validate product realization processes are capable of producing characteristics that meet engineering and design requirements. A well-planned and executed FAI by a multi-disciplinary team (e.g. members from responsible functions) provides objective evidence the manufacturer’s processes can produce compliant product; having effectively understood and incorporated the associated requirements.
NOTE A FAI is not a product acceptance document. While interrelated, FAI and product acceptance are separate activities. The focus of FAI is verification of production processes via assessment of product. FAI and supporting documentation do not provide assurance regarding conformance for product acceptance purposes; neither does the lack of a FAI necessarily imply product is nonconforming to engineering and design requirements.
FAI will:
- provide confidence, through objective evidence, the product realization processes are capable of producing conforming product;
- demonstrate the manufacturers and processors of the product have an understanding of the associated requirements;
- provide assurance of product conformance at the start of production and after changes, as outlined in this document.
A FAI is intended to:
- mitigate risks associated with production startup and process changes;
- reduce future escapes;
- help ensure product safety;
- improve quality, delivery, and customer satisfaction;
- reduce costs and production delays associated with product nonconformances;
- identify product realization processes not capable of producing conforming characteristics and initiate and/or validate associated corrective actions.
-
1.3 Application
This document applies to organizations and their suppliers responsible for product realization processes that produce the design characteristics of the product. The organization shall flow down the requirements of this document to suppliers who produce design characteristics.
This document also applies to suppliers performing special process(es). A certificate of conformance (CoC) provided by processors attests to satisfying the requirements. External suppliers providing special process(es) can satisfy this document's requirements by either:
- documenting the design characteristics and associated results on a first article inspection report (FAIR); or
- documenting the design characteristics and associated results on a detailed CoC.
This document applies to assemblies, sub-assemblies, and detail parts including castings, forgings, and modifications to standard catalogue or commercial-off-the-shelf (COTS) items. Each of these items have a separate FAI.
Unless contractually required, this document does not apply to:
- development and prototype parts that are not considered as part of the first production run;
- procured standard catalogue item, COTS, or deliverable software. When these items are included in an assembly, they shall be documented in the index of part numbers in an assembly FAIR.
1.4 Informative
If there is a conflict between the requirements of this document, and customer or applicable statutory/regulatory requirements, the latter takes precedence.
In this document, the following verbal forms are used:
- "shall" indicates a requirement;
- "should" indicates a recommendation;
- "may" indicates a permission;
- "can" indicates a possibility or a capability.
Information marked as "NOTE" is for guidance in understanding or clarifying the associated requirement .
- Standard28 pagesEnglish languagee-Library read for1 day