Aerospace series - Programme management - Expression of need - Guidance on and format for (Need) Technical Specification

This document belongs to the documents going along with EN 9200 relating to Project Management Specification.
The aims of this document are as follows:
-   to specify/remind the concept of (Need) Technical Specification (N)TS;
-   to define the principles and conditions for drawing up, approving, using and updating a (N)TS;
-   to propose a template of (N)TS.
The template identifies topics and types of related requirements to be covered in a (N)TS without being completely exhaustive or mandatory. It is due to be analysed like a check-list and tailored according to the type of the product of interest, the context of the bodies involved and the contractual details.
The principle of drawing up a (N)TS applies to both tangible and intangible products (e.g. services).
The customer/supplier relationship addressed by these principles may also apply within a single organization. The concepts of customer and supplier are discussed in this document without distinction between internal or external relationship.
This document implements and adapts EN 16271 to the context, in order to meet the specific needs of the aeronautical field and more generally the needs of other fields.
This document is more explicit about certain aspects of ISO/IEC/IEEE 29148 dedicated to requirements engineering, such as the responsibility for drawing up a (N)TS on a contractual basis and also the process of drawing it up within a programme (stages and milestones). It also supplements the technical specification framework proposed by ISO/IEC/IEEE 29148, in particular with requirements relating to safety of operation and result assurance.
The relationships existing between Functional Performance Specification (FPS) and (N)TS for expression of needs are given in Annex A.

Luft- und Raumfahrt - Programm-Management - Bedarfsbekundung - Anleitung und Format für die (Bedarfs-)Technische Lieferbedingung

Série aérospatiale - Management de programme - Expression du besoin - Guide pour l'élaboration de la spécification technique de besoin

Le présent document fait partie des documents d'accompagnement de l’EN 9200 relative à la Spécification de Management de Programme.
Le présent document a pour objet de :
- préciser/rappeler le concept de Spécification Technique de Besoin (STB) ;
- définir les principes et les conditions d'élaboration, d'approbation, d'utilisation et d'évolution d'une STB ;
- proposer un plan type de STB.
Le plan type identifie un certain nombre de thèmes et des types d’exigences associées à aborder dans une STB sans être totalement exhaustif et sans présenter un caractère obligatoire. Il est à analyser comme un aide-mémoire (check-list) et à adapter en fonction du type de produit envisagé, du contexte des organismes en présence et des données contractuelles.
Le principe d’élaboration d’une STB s’applique aux produits tangibles et intangibles (par exemple : services).
Ces principes peuvent même être étendus à des relations de type client/fournisseur internes à un organisme donné. Les notions de client et fournisseur sont abordées dans ce document de façon indifférenciée au sens interne ou externe.
Le présent document permet de mettre en oeuvre et d’adapter au contexte la norme NF EN 16271, pour répondre aux besoins spécifiques du domaine aéronautique et plus largement aux besoins d'autres domaines.
Le présent document précise certains aspects du document ISO/IEC/IEEE 29148 consacré à l’ingénierie des exigences, tels que la responsabilité d’établissement de la STB sur un plan contractuel ainsi que son processus d’élaboration au sein d’un programme (phases et jalons). Elle complète également le canevas de spécification technique proposé par l’ISO/IEC/IEEE 29148 avec notamment les exigences relatives à la sûreté de fonctionnement et celles sur l’assurance de résultat.
Les relations existantes entre le Cahier des Charges Fonctionnel (CdCF) et la STB pour l'expression du besoin sont présentées dans l'Annexe A.

Aeronavtika - Vodenje programov - Izražanje potreb - Navodilo in oblika za (potrebe) tehnične specifikacije

General Information

Status
Published
Public Enquiry End Date
31-Jul-2019
Publication Date
27-Oct-2021
Technical Committee
Current Stage
6060 - National Implementation/Publication (Adopted Project)
Start Date
20-Oct-2021
Due Date
25-Dec-2021
Completion Date
28-Oct-2021

Buy Standard

Standard
SIST EN 9208:2021 - BARVE na PDF-str 14,15
English language
42 pages
sale 10% off
Preview
sale 10% off
Preview
e-Library read for
1 day
Draft
oSIST prEN 9208:2019 - BARVE na PDF-str 14,15
English language
42 pages
sale 10% off
Preview
sale 10% off
Preview
e-Library read for
1 day

Standards Content (sample)

SLOVENSKI STANDARD
SIST EN 9208:2021
01-december-2021
Aeronavtika - Vodenje programov - Izražanje potreb - Navodilo in oblika za
(potrebe) tehnične specifikacije
Aerospace series - Programme management - Expression of need - Guidance on and
format for (Need) Technical Specification
Luft- und Raumfahrt - Programm-Management - Bedarfsbekundung - Anleitung und
Format für die (Bedarfs-)Technische Lieferbedingung
Série aérospatiale - Management de programme - Expression du besoin - Guide pour
l'élaboration de la spécification technique de besoin
Ta slovenski standard je istoveten z: EN 9208:2021
ICS:
03.100.01 Organizacija in vodenje Company organization and
podjetja na splošno management in general
49.020 Letala in vesoljska vozila na Aircraft and space vehicles in
splošno general
SIST EN 9208:2021 en,fr,de

2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.

---------------------- Page: 1 ----------------------
SIST EN 9208:2021
---------------------- Page: 2 ----------------------
SIST EN 9208:2021
EN 9208
EUROPEAN STANDARD
NORME EUROPÉENNE
October 2021
EUROPÄISCHE NORM
ICS 49.020
English Version
Aerospace series - Programme management - Expression
of need - Guidance on and format for (Need) Technical
Specification

Série aérospatiale - Management de programme - Luft- und Raumfahrt - Programm-Management -

Expression du besoin - Guide pour l'élaboration de la Bedarfsbekundung - Anleitung und Format für die

spécification technique de besoin (Bedarfs-)Technische Lieferbedingung
This European Standard was approved by CEN on 23 August 2021.

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, France, Germany, Greece, Hungary, Iceland, Ireland, Italy, Latvia, Lithuania, Luxembourg, Malta, Netherlands, Norway,

Poland, Portugal, Republic of North Macedonia, Romania, Serbia, Slovakia, Slovenia, Spain, Sweden, Switzerland, Turkey and

United Kingdom.
EUROPEAN COMMITTEE FOR STANDARDIZATION
COMITÉ EUROPÉEN DE NORMALISATION
EUROPÄISCHES KOMITEE FÜR NORMUNG
CEN-CENELEC Management Centre: Rue de la Science 23, B-1040 Brussels

© 2021 CEN All rights of exploitation in any form and by any means reserved Ref. No. EN 9208:2021 E

worldwide for CEN national Members.
---------------------- Page: 3 ----------------------
SIST EN 9208:2021
EN 9208:2021 (E)
Contents Page

European foreword ....................................................................................................................................................... 4

1 Scope .................................................................................................................................................................... 5

2 Normative references .................................................................................................................................... 5

3 Terms and definitions ................................................................................................................................... 5

4 List of acronyms ............................................................................................................................................... 8

5 Objectives of the (Need) Technical Specification (N)TS .................................................................... 9

5.1 Purpose of the customer’s expression of need ..................................................................................... 9

5.2 Role and contractual nature of the (N)TS ............................................................................................ 10

6 Principles for drawing up a (N)TS .......................................................................................................... 10

6.1 General ............................................................................................................................................................. 10

6.2 Responsibility for drawing up the (N)TS ............................................................................................. 10

6.3 (N)TS elaboration process ........................................................................................................................ 11

6.3.1 Preparatory stage ........................................................................................................................................ 11

6.3.2 Description of the process ........................................................................................................................ 11

6.3.3 Position in programme phasing and scheduling .............................................................................. 12

6.3.4 Principles for requirement breakdown and allocation according to the product

breakdown structure .................................................................................................................................. 13

6.4 Rules on the expression of requirements ........................................................................................... 14

6.4.1 Requirement quality criteria ................................................................................................................... 14

6.4.2 Format of the requirements ..................................................................................................................... 14

6.4.3 Concepts of flexibility for requirements .............................................................................................. 15

7 Content of the (N)TS .................................................................................................................................... 16

7.1 General remarks ........................................................................................................................................... 16

7.2 Product concept ............................................................................................................................................ 16

7.3 Scope ................................................................................................................................................................. 16

7.4 Context of use ................................................................................................................................................ 16

7.4.1 Expected missions ........................................................................................................................................ 16

7.4.2 Operational context and operational environment ........................................................................ 16

7.4.3 Life profile ....................................................................................................................................................... 16

7.4.4 Operational scenarios ................................................................................................................................ 16

7.5 Documents and terminology (as subclause of the (N)TS) ............................................................. 17

7.6 Technical requirements............................................................................................................................. 17

7.6.1 Functional requirements........................................................................................................................... 17

7.6.2 Lifetime requirements ............................................................................................................................... 18

7.6.3 RAMS requirements .................................................................................................................................... 18

7.6.4 Product protection requirements .......................................................................................................... 20

7.6.5 Human factors requirements................................................................................................................... 21

7.6.6 Requirements relating to logistic support and in-service operations of the product ........ 22

7.6.7 Requirements on resistance to the environmental conditions ................................................... 23

7.6.8 External interfaces requirements .......................................................................................................... 23

7.6.9 Design constraints and imposed solutions ......................................................................................... 24

7.7 Requirements for result assurance ....................................................................................................... 25

7.7.1 General ............................................................................................................................................................. 25

7.7.2 Requirements relating to Definition Justification and Qualification pronouncement ....... 25

---------------------- Page: 4 ----------------------
SIST EN 9208:2021
EN 9208:2021 (E)

7.7.3 Requirements relating to the conditions of acceptance of specimens of the product ......... 25

8 Updating of a (N)TS ...................................................................................................................................... 26

Annex A (informative) Relations between FPS and (N)TS .......................................................................... 27

Annex B (informative) Mapping with CMMI-Acquisition and CMMI-Development models ........... 28

Annex C (informative) Overview of the NATO Architecture Framework (NAF) ................................. 29

Annex D (informative) Architecture views for human factors .................................................................. 32

Annex E (informative) Contents suggested for a (N)TS ................................................................................ 33

Annex F (informative) Standards or guides for safety studies .................................................................. 34

Annex G (informative) Detailed requirements relating to logistic support and in-service

operations of the product .......................................................................................................................... 35

G.1 User support ................................................................................................................................................... 35

G.1.1 Requirements relating to user technical documentation (UTD) ................................................. 35

G.1.2 Requirements relating to user training and learning ..................................................................... 35

G.1.3 Requirements relating to user support (Helpdesk Service) ......................................................... 35

G.2 Customer support ......................................................................................................................................... 35

G.2.1 Requirements relating to asset management on behalf of the customer ................................ 35

G.2.2 Requirements relating to technical support or service provision.............................................. 36

G.3 Operational services .................................................................................................................................... 36

G.3.1 Requirements relating to product deployment ................................................................................. 36

G.3.2 Requirements relating to product operation ..................................................................................... 36

G.3.3 Requirements relating to operation incident treatment ............................................................... 36

G.3.4 Requirements relating to availability and service continuity follow-up ................................. 36

G.4 Analysis of logistic support, logistics and maintenance in operational condition ............... 36

G.4.1 Requirements relating to logistic support analysis ......................................................................... 36

G.4.2 Requirements relating to logistics ......................................................................................................... 37

G.4.2.1 Requirements relating to the product supply chain ........................................................................ 37

G.4.2.2 Requirements relating to packaging, handling, storage and transport (EMST) .................... 37

G.4.2.3 Requirements relating to spare, consumable and ingredient management .......................... 37

G.4.2.4 Requirements relating to support means (test means and platform tooling, except

training platform) ........................................................................................................................................ 37

G.4.3 Requirements relating to maintenance in operational condition .............................................. 38

G.4.3.1 Requirements on in-use product observability and data collection .......................................... 38

G.4.3.2 Requirements relating to product maintenance (repair, spare, change, etc.) ....................... 38

G.4.3.3 Requirements relating to obsolescence management .................................................................... 38

Annex H (informative) Standards and guides related to integrated logistic support (ILS)

requirements ................................................................................................................................................. 39

Bibliography ................................................................................................................................................................. 40

---------------------- Page: 5 ----------------------
SIST EN 9208:2021
EN 9208:2021 (E)
European foreword

This document (EN 9208:2021) has been prepared by the Aerospace and Defence Industries

Association of Europe - Standardization (ASD-STAN).

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 April 2022, and conflicting national standards shall be

withdrawn at the latest by April 2022.

Attention is drawn to the possibility that some of the elements of this document may be the subject of

patent rights. CEN shall not be held responsible for identifying any or all such patent rights.

Any feedback and questions on this document should be directed to the users’ national standards body.

A complete listing of these bodies can be found on the CEN website.

According to the CEN-CENELEC Internal Regulations, the national standards organisations of the

following countries are bound to implement this European Standard: Austria, Belgium, Bulgaria,

Croatia, Cyprus, Czech Republic, Denmark, Estonia, Finland, France, Germany, Greece, Hungary, Iceland,

Ireland, Italy, Latvia, Lithuania, Luxembourg, Malta, Netherlands, Norway, Poland, Portugal, Republic of

North Macedonia, Romania, Serbia, Slovakia, Slovenia, Spain, Sweden, Switzerland, Turkey and the

United Kingdom.
---------------------- Page: 6 ----------------------
SIST EN 9208:2021
EN 9208:2021 (E)
1 Scope

This document belongs to the documents going along with the EN 9200 relating to Project Management

Specification.
The aims of this document are as follows:
— to specify/remind the concept of (Need) Technical Specification (N)TS;

— to define the principles and conditions for drawing up, approving, using and updating a (N)TS;

— to propose a template of (N)TS.

The template identifies topics and types of related requirements to be covered in a (N)TS without being

completely exhaustive or mandatory. It is analysed like a check-list and tailored according to the type of

the product of interest, the context of the bodies involved and the contractual details.

The principle of drawing up a (N)TS applies to both tangible and intangible products (e.g. services).

The customer/supplier relationship addressed by these principles may also apply within a single

organization. The concepts of customer and supplier are discussed in this document without distinction

between internal or external relationship.

This document implements and adapts to the context the EN 16271 standard, in order to meet the

specific needs of the aeronautical field and more generally the needs of other fields.

This document is more explicit about certain aspects of the ISO/IEC/IEEE 29148 document dedicated to

requirements engineering, such as the responsibility for drawing up a (N)TS on a contractual basis and

also the process of drawing it up within a programme (stages and milestones). It also supplements the

technical specification framework proposed by ISO/IEC/IEEE 29148, in particular with requirements

relating to safety of operation and result assurance.

The relationships existing between Functional Performance Specification (FPS) and (N)TS for

expression of needs are given in Annex A.
2 Normative references

The following documents are referred to in the text in such a way that some or all of their content

constitutes requirements of this document. For dated references, only the edition cited applies. For

undated references, the latest edition of the referenced document (including any amendments) applies.

EN 9200, Aerospace series - Programme management - Guidelines for project management specification

3 Terms and definitions

For the purposes of this document, the terms and definitions given in EN 9200 and the following apply.

ISO and IEC maintain terminological databases for use in standardization at the following addresses:

— ISO Online browsing platform: available at https://www.iso.org/obp
— IEC Electropedia: available at http://www.electropedia.org/
3.1
environmental agent

one of the physical, chemical, biological, etc. phenomena that may have direct or indirect, immediate or

delayed, effect on living beings, human activities and systems or their operation

[SOURCE: NF X 50-144-1]
---------------------- Page: 7 ----------------------
SIST EN 9208:2021
EN 9208:2021 (E)
3.2
need
what is necessary for, or desired by, the user

Note 1 to entry: A need may be explicit or implicit; it may be existing or potential.

Note 2 to entry: “Implicit” means that it is usual or a common practice for all the parties concerned.

[SOURCE: Adapted from EN 16271]
3.3
functional performance specification
FPS

document in which the needs are listed in terms of service functions and constraints

Note 1 to entry: Drawing up a FPS implies that a functional analysis has been able to clearly define the users’

needs.

Note 2 to entry: Assessment criteria and their performance levels are defined for each of these functions, when

relevant and possible. Each performance level is expressed with a certain degree of flexibility.

[SOURCE: Adapted from EN 16271]
3.4
constraint

externally imposed limitation on requirements, design, or implementation or on the process used to

develop or modify a product or on any other provision

Note 1 to entry: A constraint is a factor that is imposed on the solution by force or compulsion and may limit or

modify the choice of solution.

Note 2 to entry: Constraints may come from authoritative texts (laws, regulations, standards, market

demand, etc.).
[SOURCE: Adapted from ISO/IEC/IEEE 29148]
3.5
life cycle

set of phases in the life of a product, from the expression of need until disposal

Note 1 to entry: The product can be firstly conceptual then physical.
Note 2 to entry: The life cycle typically includes the following phases:
— Initial expression of need;
— feasibility;
— definition;
— development;
— production;
— operation;
— disposal.
Note 3 to entry: Notion not to be confused with life profile.
---------------------- Page: 8 ----------------------
SIST EN 9208:2021
EN 9208:2021 (E)
3.6
requirement

statement that translates or expresses a need and its associated constraints and conditions

[SOURCE: ISO/IEC/IEEE 29148]
3.7
special requirements

those requirements identified by the customer, or determined by the organisation, which have high

risks of not being met, thus requiring their inclusion in the operational risk management process

Note 1 to entry: Factors used in the determination of special requirements include product or process

complexity, past experience, and product or process maturity.

EXAMPLE performance requirements imposed by the customer that are at the limit of the industry’s

capability, or requirements determined by the organization to be at the limit of its technical or process capabilities

[SOURCE: Adapted from EN 9100]
3.8
interface

boundary shared between two products, or two product parts, which has physical and/or functional

exchanges
3.9
performance
measurable characteristic(s) of a product
3.10
life profile

chronological description of the use situations in which a physical product is expected to be found, from

ex-factory to disposal

Note 1 to entry: By situation, we mean: transport, handling, storage, maintenance, operational use..., with all

environmental conditions, durations and respective occurrences.

Note 2 to entry: The life profile is described for product/customer or product/job couples. For a given product,

there may be several life profiles depending on the considered concepts of use or deployments.

Note 3 to entry: Not to be confused with life cycle.
3.11
operational scenario

description of an imagined sequence of events that includes the interaction of the product or service

with its environment and users, as well as interaction among its product or service components

Note 1 to entry: Operational scenarios are used to evaluate the requirements and design of the product and to

verify and validate the product.
[SOURCE: Adapted from ISO/IEC/IEEE 24765]
---------------------- Page: 9 ----------------------
SIST EN 9208:2021
EN 9208:2021 (E)
3.12
(need) technical specification
(N)TS

contractual document drawn up by the customer, intended for the supplier, in which the customer

expresses his needs (or the needs he has been instructed to convey) in terms of technical requirements

Note 1 to entry: The (Need) Technical Specification may also establish the conditions to ensure that these

requirements are met.
4 List of acronyms
AIS Analogue Interface Sheet
ARINC Aeronautical Radio INCorporated
BIT Built In Test
CMMI Capability Maturity Model Integration
DIS Digital Interface Sheet

EBIOS (Expression des Besoins et Identification des Objectifs de Sécurité) — Expression of need and

Identification of Safety Objectives

EMST (Emballage Manutention Stockage Transport) — Packaging Handling Storage Transport

FEROS (Fiche d’Expression Rationnelle des Objectifs de Sécurité) — Rational expression of Security

Objectives Statement
FPS Functional Performance Specification
HUMS Health and Usage Monitoring System
ICD Interface Control Document
ILS Integrated Logistics Support
IRS Interface Requirement Specification
LRU Line Replaceable Unit

MEHARI (Méthode Harmonisée d’Analyse des Risques) — Harmonized Risk Assessment Methodology

MTBF Mean Time Between Failures
MTTR Mean Time To Repair
NAF NATO Architecture Framework
NATO North Atlantic Treaty Organization
(N)TS (Need) Technical Specification
NRBC Nuclear, Radiological, Bacteriological, Chemical
PTS Product Technical Specification
QoS Quality of Service
RAMS Reliability, Availability, Maintainability and Safety
REACh Registration Evaluation and Authorization of Chemicals
RFID Radio-Frequency IDentification
RoHS Restrictions of Hazardous Substances
SLA Service Level Agreement
TRL Technology Readiness Level
UTD User Technical Documentation
---------------------- Page: 10 ----------------------
SIST EN 9208:2021
EN 9208:2021 (E)
5 Objectives of the (Need) Technical Specification (N)TS
5.1 Purpose of the customer’s expression of need

The (N)TS is drawn up under the customer’s responsibility (see 6.2) and its purpose is to formalize the

needs in technical terms. A (N)TS attached to a contract results from negotiations between the

customer and the supplier. It reflects the compromise between technological feasibility, performance,

imposed solutions, total cost, realization duration and risks.

NOTE 1 The total cost includes non-recurring costs (related to design, development, etc.) and recurring costs

(related to manufacturing, purchasing, operation, support, etc.) over the entire life cycle of the product.

It expresses the technical requirements over the entire life cycle of the product:

— functional and performance requirements;
— lifetime requirements;
— RAMS requirements (reliability, availability, maintainability, safety);
— product protection requirements including information security;
— human factors requirements;

— requirements relating to logistic support and in-service operations of the product;

— requirements on resistance to the environmental conditions;
— external interfaces requirements;
— design constraints and imposed solutions.
It can also express the requirements regarding result assurance:
— relating to definition justification and qualification pronouncement;
— relating to the conditions of acceptance of specimens of the product.

NOTE 2 The expression of need may change according to the phases of the life cycle. It could be considered

compared to expected intermediate supplies, which may be a model, prototype, document, etc. up to the

operational product. Thus mock-ups, prototypes and different versions of the product, which are to be supplied

under contract and which differ from the operational product due to special requirements or tolerances, may be

the subject of a separate (N)TS or a document showing the deviations compared with the (N)TS of the operational

product.

The (N)TS requirements are those necessary and sufficient for a supplier to be able to draw up, if

necessary, its own Product Technical Specification (PTS) and establish a product definition that fulfils

the need.

These requirements are mainly formalized in terms of functions and performance expected from the

product to be designed and defined, bearing in mind the identified risks accepted by the parties

(see 6.1).

It is recommended to take into account the general requirements expressed in the higher-level (N)TS

for each level of the product breakdown structure (see 6.3.4). These general requirements may be:

component policy, marking rule, documentation, etc.
---------------------- Page: 11 ----------------------
SIST EN 9208:2021
EN 9208:2021 (E)

To understand the origin of the requirement, and also how the (N)TS of the product can be integrated in

a larger system (“Where does this need come from? What about this restriction? Why this

requirement?”), the customer should ensure traceability of the requirements from the top-level

(including the case where the product belongs to a larger system, as in the case of systems of systems)

down to the (N)TS appended to the contract. It may also be wise to establish traceability links between

decisions (emails, report, etc.) and the (N)TS requirements, in a requirement justification file for

example.

The Aeronautical Quality Management System standards (EN 9100 and EN 9110) introduce the concept

of “special requirements” for certain requirements (see definition). This concept emphasizes the high

risk of not being able to meet a requirement.

This kind of requirements (“special requirements”) may be determined either by the customer (in the

(N)TS) or by the supplier (in the PTS) and implies these requirements to be dealt with via the risk

management process of the customer and/or supplier.

In order to answer the various questions such as “is this requirement the right one?” it is recommended,

where applicable, to ensure validation of the requirements (using ARP4754A/ED-79A) against the

different expressions of need regarding the context where the product will take place.

5.2 Role and contractual nature of the (N)TS

The (N)TS serves as a contractual basis between a customer and its supplier. The (N)TS allows the

supplier to design and define the product. This product can be developed, modified or selected from a

portfolio of existing products, as long as it fulfils the requirements expressed by the customer.

Based on the customer/supplier relationship, the (N)TS is the reference document that enables the

customer to
— express his need for the supplier in terms of results and not solution,

— pronounce the decision concerning qualification of the product definition and, reciprocally, enables

the supplier to justify the product definition by means of analyses or tests,

— process the technical changes in the product definition; the (N)TS is therefore an element of the

reference configuration of the product (see EN 9223-100 and its accompanying documents) and

— decide on requests for waivers or
...

SLOVENSKI STANDARD
oSIST prEN 9208:2019
01-julij-2019
Aeronavtika - Vodenje programov - Izražanje potreb - Navodilo in oblika za
(potrebe) tehnične specifikacije
Aerospace series - Programme management - Expression of need - Guidance on and
format for (Need) Technical Specification
Luft- und Raumfahrt - Programm-Management - Bedarfsbekundung - Anleitung und
Format für die (Bedarfs-)Technische Lieferbedingung
Ta slovenski standard je istoveten z: prEN 9208
ICS:
03.100.01 Organizacija in vodenje Company organization and
podjetja na splošno management in general
49.020 Letala in vesoljska vozila na Aircraft and space vehicles in
splošno general
oSIST prEN 9208:2019 en,fr,de

2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.

---------------------- Page: 1 ----------------------
oSIST prEN 9208:2019
---------------------- Page: 2 ----------------------
oSIST prEN 9208:2019
DRAFT
EUROPEAN STANDARD
prEN 9208
NORME EUROPÉENNE
EUROPÄISCHE NORM
May 2019
ICS 03.100.01; 49.020
English Version
Aerospace series - Programme management - Expression
of need - Guidance on and format for (Need) Technical
Specification
Luft- und Raumfahrt - Programm-Management -
Bedarfsbekundung - Anleitung und Format für die
(Bedarfs-)Technische Lieferbedingung

This draft European Standard is submitted to CEN members for enquiry. It has been drawn up by the Technical Committee ASD-

STAN.

If this draft becomes a European Standard, CEN members are bound to comply with the CEN/CENELEC Internal Regulations

which stipulate the conditions for giving this European Standard the status of a national standard without any alteration.

This draft European Standard was established by CEN in three official versions (English, French, German). A version in any other

language made by translation under the responsibility of a CEN member into its own language and notified to the CEN-CENELEC

Management Centre has the same status as the official versions.

CEN members are the national standards bodies of Austria, Belgium, Bulgaria, Croatia, Cyprus, Czech Republic, Denmark, Estonia,

Finland, Former Yugoslav Republic of Macedonia, France, Germany, Greece, Hungary, Iceland, Ireland, Italy, Latvia, Lithuania,

Luxembourg, Malta, Netherlands, Norway, Poland, Portugal, Romania, Serbia, Slovakia, Slovenia, Spain, Sweden, Switzerland,

Turkey and United Kingdom.

Recipients of this draft are invited to submit, with their comments, notification of any relevant patent rights of which they are

aware and to provide supporting documentation.

Warning : This document is not a European Standard. It is distributed for review and comments. It is subject to change without

notice and shall not be referred to as a European Standard.
EUROPEAN COMMITTEE FOR STANDARDIZATION
COMITÉ EUROPÉEN DE NORMALISATION
EUROPÄISCHES KOMITEE FÜR NORMUNG
CEN-CENELEC Management Centre: Rue de la Science 23, B-1040 Brussels

© 2019 CEN All rights of exploitation in any form and by any means reserved Ref. No. prEN 9208:2019 E

worldwide for CEN national Members.
---------------------- Page: 3 ----------------------
oSIST prEN 9208:2019
prEN 9208:2019 (E)
Contents Page

European foreword ....................................................................................................................................................... 4

1 Scope .................................................................................................................................................................... 5

2 Normative references .................................................................................................................................... 5

3 Terms and definitions ................................................................................................................................... 5

4 List of acronyms ............................................................................................................................................... 8

5 Objectives of the (Need) Technical Specification (N)TS .................................................................... 9

5.1 Purpose of the customer’s expression of need ..................................................................................... 9

5.2 Role and contractual nature of the (N)TS ............................................................................................ 10

6 Principles for drawing up a (N)TS .......................................................................................................... 11

6.1 General ............................................................................................................................................................. 11

6.2 Responsibility for drawing up the (N)TS ............................................................................................. 11

6.3 (N)TS elaboration process ........................................................................................................................ 11

6.3.1 Preparatory stage ........................................................................................................................................ 11

6.3.2 Description of the process ........................................................................................................................ 11

6.3.3 Position in programme phasing and scheduling .............................................................................. 12

6.3.4 Principles for requirement breakdown and allocation according to the product

breakdown structure .................................................................................................................................. 13

6.4 Rules on the expression of requirements ........................................................................................... 14

6.4.1 Requirement quality criteria ................................................................................................................... 14

6.4.2 Format of the requirements ..................................................................................................................... 14

6.4.3 Concepts of flexibility for requirements .............................................................................................. 15

7 Content of the (N)TS .................................................................................................................................... 15

7.1 General remarks ........................................................................................................................................... 15

7.2 Product concept ............................................................................................................................................ 16

7.3 Scope ................................................................................................................................................................. 16

7.4 Context of use ................................................................................................................................................ 16

7.4.1 Expected missions ........................................................................................................................................ 16

7.4.2 Operational context and operational environment ........................................................................ 16

7.4.3 Life profile ....................................................................................................................................................... 16

7.4.4 Operational scenarios ................................................................................................................................ 16

7.5 Documents and terminology (as subclause of the (N)TS) ............................................................. 17

7.6 Technical requirements............................................................................................................................. 17

7.6.1 Functional requirements........................................................................................................................... 17

7.6.2 Lifetime requirements ............................................................................................................................... 18

7.6.3 RAMS requirements .................................................................................................................................... 18

7.6.4 Product protection requirements .......................................................................................................... 20

7.6.5 Human factors requirements................................................................................................................... 21

7.6.6 Requirements relating to logistic support and in-service operations of the product ........ 22

7.6.7 Requirements on resistance to the environmental conditions ................................................... 22

7.6.8 External interfaces requirements .......................................................................................................... 23

7.6.9 Design constraints and imposed solutions ......................................................................................... 23

7.7 Requirements for result assurance ....................................................................................................... 24

7.7.1 General ............................................................................................................................................................. 24

7.7.2 Requirements relating to Definition Justification and Qualification pronouncement ....... 25

7.7.3 Requirements relating to the conditions of acceptance of specimens of the product ........ 25

---------------------- Page: 4 ----------------------
oSIST prEN 9208:2019
prEN 9208:2019 (E)

8 Updating of a (N)TS ...................................................................................................................................... 25

Annex A (informative) Relations between FPS and (N)TS .......................................................................... 27

Annex B (informative) Mapping with CMMI-Acquisition and CMMI-Development models ........... 28

Annex C (informative) Overview of the NATO Architecture Framework (NAF) ................................. 29

Annex D (informative) Architecture views for human factors .................................................................. 32

Annex E (informative) Contents suggested for (N)TS ................................................................................... 33

Annex F (informative) Standards or guides for safety studies .................................................................. 34

Annex G (informative) Detailed requirements relating to logistic support and in-service

operations of the product .......................................................................................................................... 35

G.1 User support ................................................................................................................................................... 35

G.1.1 Requirements relating to user technical documentation (UTD) ................................................. 35

G.1.2 Requirements relating to user training and learning ..................................................................... 35

G.1.3 Requirements relating to user support (Helpdesk Service) ......................................................... 35

G.2 Customer support ......................................................................................................................................... 35

G.2.1 Requirements relating to asset management on behalf of the customer ................................ 35

G.2.2 Requirements relating to technical support or service provision.............................................. 36

G.3 Operational services .................................................................................................................................... 36

G.3.1 Requirements relating to product deployment ................................................................................. 36

G.3.2 Requirements relating to product operation ..................................................................................... 36

G.3.3 Requirements relating to operation incident treatment ............................................................... 36

G.3.4 Requirements relating to availability and service continuity follow-up ................................. 36

G.4 Analysis of logistic support, logistics and maintenance in operational condition ............... 36

G.4.1 Requirements relating to logistic support analysis ......................................................................... 36

G.4.2 Requirements relating to logistics ......................................................................................................... 37

G.4.2.1 Requirements relating to the product supply chain ........................................................................ 37

G.4.2.2 Requirements relating to packaging, handling, storage and transport (EMST) .................... 37

G.4.2.3 Requirements relating to spare, consumable and ingredient management .......................... 37

G.4.2.4 Requirements relating to support means (test means and platform tooling, except

training platform) ........................................................................................................................................ 37

G.4.3 Requirements relating to maintenance in operational condition .............................................. 38

G.4.3.1 Requirements on in-use product observability and data collection .......................................... 38

G.4.3.2 Requirements relating to product maintenance (repair, spare, change, etc.) ....................... 38

G.4.3.3 Requirements relating to obsolescence management .................................................................... 38

Annex H (informative) Standards and guides related to Integrated logistic support (ILS)

requirements ................................................................................................................................................. 39

Bibliography ................................................................................................................................................................. 40

---------------------- Page: 5 ----------------------
oSIST prEN 9208:2019
prEN 9208:2019 (E)
European foreword

This document (prEN 9208:2019) 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 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 document is currently submitted to the CEN Enquiry.
---------------------- Page: 6 ----------------------
oSIST prEN 9208:2019
prEN 9208:2019 (E)
1 Scope

This document belongs to the documents going along with EN 9200 relating to Project Management

Specification.
The aims of this document are as follows:
— to specify/remind the concept of (Need) Technical Specification (N)TS;

— to define the principles and conditions for drawing up, approving, using and updating a (N)TS;

— to propose a template of (N)TS.

The template identifies topics and types of related requirements to be covered in a (N)TS without being

completely exhaustive or mandatory. It is due to be analysed like a check-list and tailored according to

the type of the product of interest, the context of the bodies involved and the contractual details.

The principle of drawing up a (N)TS applies to both tangible and intangible products (e.g. services).

The customer/supplier relationship addressed by these principles may also apply within a single

organization. The concepts of customer and supplier are discussed in this document without distinction

between internal or external relationship.

This document implements and adapts EN 16271 to the context, in order to meet the specific needs of

the aeronautical field and more generally the needs of other fields.

This document is more explicit about certain aspects of ISO/IEC/IEEE 29148 dedicated to requirements

engineering, such as the responsibility for drawing up a (N)TS on a contractual basis and also the

process of drawing it up within a programme (stages and milestones). It also supplements the technical

specification framework proposed by ISO/IEC/IEEE 29148, in particular with requirements relating to

safety of operation and result assurance.

The relationships existing between Functional Performance Specification (FPS) and (N)TS for

expression of needs are given in Annex A.
2 Normative references

The following documents are referred to in the text in such a way that some or all of their content

constitutes requirements of this document. For dated references, only the edition cited applies. For

undated references, the latest edition of the referenced document (including any amendments) applies.

EN 9200, Aerospace series - Programme management - Guidelines for project management specification

3 Terms and definitions

For the purposes of this document, the terms and definitions given in EN 9200 and the following apply.

ISO and IEC maintain terminological databases for use in standardization at the following addresses:

— ISO Online browsing platform: available at http://www.iso.org/obp
— IEC Electropedia: available at http://www.electropedia.org/
---------------------- Page: 7 ----------------------
oSIST prEN 9208:2019
prEN 9208:2019 (E)
3.1
environmental agent

one of the physical, chemical, biological, etc. phenomena that may have direct or indirect, immediate or

delayed, effect on living beings, human activities and systems or their operation

[SOURCE: NF X 50-144-1]
3.2
need
what is necessary for or desired by the user

Note 1 to entry: A need may be explicit or implicit; it may be existing or potential.

Note 2 to entry: “Implicit” means that it is usual or a common practice for all the parties concerned.

[SOURCE: EN 16271:2012, 3.2, modified – Note 1 to entry has been modified, Note 2 to entry has been

added.]
3.3
functional performance specification
FPS

document in which the needs are listed in terms of service functions and constraints

Note 1 to entry: Drawing up a FPS implies that a functional analysis has been able to clearly define the users'

needs.

Note 2 to entry: Assessment criteria and their performance levels are defined for each of these functions, when

relevant and possible. Each performance level is expressed with a certain degree of flexibility.

[SOURCE: EN 16271:2012, 3.16, modified]
3.4
constraint

externally imposed limitation on requirements, design, or implementation or on the process used to

develop or modify a product or on any other provision

Note 1 to entry: A constraint is a factor that is imposed on the solution by force or compulsion and may limit or

modify the choice of solution.

Note 2 to entry: Constraints may come from authoritative texts (laws, regulations, standards, market demand,

etc.).

[SOURCE: ISO/IEC/IEEE 29148:2018, 3.1.7, modified – Definition and Note 1 to entry has been

modified, Note 2 to entry has been added.]
3.5
life cycle

set of phases in the life of a product, from the expression of need until disposal

Note 1 to entry: The product can be firstly conceptual then physical.
Note 2 to entry: The life cycle typically includes the following phases:
— Initial expression of need,
---------------------- Page: 8 ----------------------
oSIST prEN 9208:2019
prEN 9208:2019 (E)
— feasibility;
— definition;
— development;
— production;
— operation;
— disposal.
Note 3 to entry: Notion not to be confused with life profile.
3.6
requirement

statement which translates or expresses a need and its associated constraints and conditions

[SOURCE: ISO/IEC/IEEE 29148:2018, 3.1.19]
3.7
special requirements

requirements identified by the customer, or determined by the organization, which have high risks of

not being met, thus requiring their inclusion in the operational risk management process; factors used

in the determination of special requirements include product or process complexity, past experience,

and product or process maturity; examples of special requirements include performance requirements

imposed by the customer that are at the limit of the industry’s capability or requirements determined

by the organization to be at the limit of its technical or process capabilities
[SOURCE: EN 9100:2018, 3.5]
3.8
interface

boundary shared between two products, or two product parts, which has physical and/or functional

exchanges
3.9
performance
measurable characteristic(s) of a product
3.10
life profile

chronological description of the use situations in which a physical product is expected to be found, from

ex-factory to disposal; by situation, we mean: transport, handling, storage, maintenance, operational

use…, with all environmental conditions, durations and respective occurrences

Note 1 to entry: The life profile is described for product/customer or product/job couples. For a given product,

there may be several life profiles depending on the considered concepts of use or deployments.

Note 2 to entry: Not to be confused with life cycle.
---------------------- Page: 9 ----------------------
oSIST prEN 9208:2019
prEN 9208:2019 (E)
3.11
operational scenario

description of an imagined sequence of events that includes the interaction of the product or service

with its environment and users, as well as interaction among its product or service components

Note 1 to entry: Operational scenarios are used to evaluate the requirements and design of the product and to

verify and validate the product.
[SOURCE: ISO/IEC/IEEE 24765:2017, 3.2713]
3.12
(need) technical specification
(N)TS

contractual document drawn up by the customer, intended for the supplier, in which the customer

expresses his needs (or the needs he has been instructed to convey) in terms of technical requirements

Note 1 to entry: The (Need) Technical Specification may also establish the conditions to ensure that these

requirements are met.
4 List of acronyms
AIS Analogue Interface Sheet
ARINC Aeronautical Radio INCorporated
BIT Built In Test
CMMI Capability Maturity Model Integration
DIS Digital Interface Sheet

EBIOS (Expression des Besoins et Identification des Objectifs de Sécurité) — Expression of need and

Identification of Safety Objectives

EMST (Emballage Manutention Stockage Transport) — Packaging Handling Storage Transport

FEROS (Fiche d'Expression Rationnelle des Objectifs de Sécurité) — Rational expression of Security

Objectives Statement
FPS Functional Performance Specification
HUMS Health and Usage Monitoring System
ICD Interface Control Document
ILS Integrated Logistics Support
IRS Interface Requirement Specification
LRU Line Replaceable Unit

MEHARI (Méthode Harmonisée d’Analyse des Risques) — Harmonized Risk Assessment Methodology

MTBF Mean Time Between Failures
MTTR Mean Time To Repair
NAF NATO Architecture Framework
NATO North Atlantic Treaty Organization
(N)TS (Need) Technical Specification
NRBC Nuclear, Radiological, Bacteriological, Chemical
---------------------- Page: 10 ----------------------
oSIST prEN 9208:2019
prEN 9208:2019 (E)
PTS Product Technical Specification
QoS Quality of Service
RAMS Reliability, Availability, Maintainability and Safety
REACh Registration Evaluation and Authorization of Chemicals
RFID Radio-Frequency IDentification
RoHS Restrictions of Hazardous Substances
SLA Service Level Agreement
TRL Technology Readiness Level
UTD User Technical Documentation
5 Objectives of the (Need) Technical Specification (N)TS
5.1 Purpose of the customer’s expression of need

The (N)TS is drawn up under the customer’s responsibility (see 6.2) and its purpose is to formalize the

needs in technical terms. A (N)TS attached to a contract results from negotiations between the

customer and the supplier. It reflects the compromise between technological feasibility, performance,

imposed solutions, total cost, realization duration and risks.

NOTE The total cost includes non-recurring costs (related to design, development, etc.) and recurring costs

(related to manufacturing, purchasing, operation, support, etc.) over the entire life cycle of the product.

It expresses the technical requirements over the entire life cycle of the product:

— functional and performance requirements;
— lifetime requirements;
— RAMS requirements (reliability, availability, maintainability, safety);
— product protection requirements including information security;
— human factors requirements;

— requirements relating to logistic support and in-service operations of the product;

— requirements on resistance to the environmental conditions;
— external interfaces requirements;
— design constraints and imposed solutions.
It can also express the requirements regarding result assurance:
— relating to definition justification and qualification pronouncement;
— relating to the conditions of acceptance of specimens of the product.

The expression of need may change according to the phases of the life cycle. It should be considered

compared to expected intermediate supplies, which may be a model, prototype, document, etc. up to the

operational product. Thus mock-ups, prototypes and different versions of the product, which are to be

---------------------- Page: 11 ----------------------
oSIST prEN 9208:2019
prEN 9208:2019 (E)

supplied under contract and which differ from the operational product due to special requirements or

tolerances, may be the subject of a separate (N)TS or a document showing the deviations compared

with the (N)TS of the operational product.

The (N)TS requirements are those necessary and sufficient for a supplier to be able to draw up, if

necessary, its own Product Technical Specification (PTS) and establish a product definition that fulfils

the need.

These requirements are mainly formalized in terms of functions and performance expected from the

product to be designed and defined, bearing in mind the identified risks accepted by the parties

(see 6.1).

It is recommended to take into account the general requirements expressed in the higher-level (N)TS

for each level of the product breakdown structure (see 6.3.4). These general requirements may be:

component policy, marking rule, documentation, etc.

To understand the origin of the requirement, and also how the (N)TS of the product can be integrated in

a larger system (“Where does this need come from? What about this restriction? Why this

requirement?”), the customer should ensure traceability of the requirements from the top-level

(including the case where the product belongs to a larger system, as in the case of systems of systems)

down to the (N)TS appended to the contract. It may also be wise to establish traceability links between

decisions (emails, report, etc.) and the (N)TS requirements, in a requirement justification file for

example.

The Aeronautical Quality Management System standards (EN 9100 and EN 9110) introduce the concept

of “special requirements” for certain requirements (see definition). This concept emphasizes the high

risk of not being able to meet a requirement.

This kind of requirements (“special requirements”) may be determined either by the customer (in the

(N)TS) or by the supplier (in the PTS) and implies these requirements to be dealt with via the risk

management process of the customer and/or supplier.

In order to answer the various questions such as “is this requirement the right one?” it is recommended,

where applicable, to ensure validation of the requirements (using ARP 4754A/ED-79A) against the

different expressions of need regarding the context where the product will take place.

5.2 Role and contractual nature of the (N)TS

The (N)TS serves as a contractual basis between a customer and its supplier. The (N)TS allows the

supplier to design and define the product. This product can be developed, modified or selected from a

portfolio of existing products, as long as it fulfils the requirements expressed by the customer.

Based on the customer/supplier relationship, the (N)TS is the reference document that enables the

customer to:
— express his need for the supplier in terms of results and not solution,

— pronounce the decision concerning qualification of the product definition and, reciprocally, enables

the supplier to justify the product definition by means of analyses or tests,

— process the technical changes in the product definition; the (N)TS is therefore an element of the

reference configuration of the product (see EN 9223-100 and its accompanying documents) and

— decide on requests for waivers or deviation (see EN 9223-105) if elements of the Definition Data

File are not sufficient to decide on this request.

The (N)TS is a part of the contract; the contract also specifies other types of requirements (means to be

implemented, work packages, programme management requirements, etc.).
---------------------- Page: 12 ----------------------
oSIST prEN 9208:2019
prEN 9208:2019 (E)

NOTE For organizations which follow CMMI models, Annex B shows how CMMI models map to the (N)TS.

6 Principles for drawing up a (N)TS
6.1 General
...

Questions, Comments and Discussion

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