SIST EN 9223-101:2018
(Main)Programme Management - Configuration Management - Part 101: Configuration identification
Programme Management - Configuration Management - Part 101: Configuration identification
The present document is declined from the principles described in the EN 9223-100, it:
is based on internationally-recognised concepts;
proposes organisational principles and implementation processes for Configuration Management
from both viewpoints: “programme” and “company”, with emphasis on the “programme”
viewpoint;
deals with configuration identification but not contract management methods.
It is up to each person responsible for a programme to define the detailed methods of application and
tailoring as necessary.
Programm-Management - Konfigurationsmanagement - Teil 101: Konfigurationsidentifizierung
Das vorliegende Dokument ist aus den Grundsätzen von EN 9223-100 abgeleitet und
- basiert auf international anerkannten Konzepten,
- schlägt organisatorische Grundsätze und Umsetzungsprozesse für das Konfigurationsmanagement aus den beiden Perspektiven "Programm" und "Unternehmen"mit dem Schwerpunkt auf der Perspektive "Programm" vor,
- behandelt die Konfigurationsidentifizierung, nicht aber die Verfahren des Vertragsmanagements.
Es obliegt jeder für ein Programm verantwortlichen Person, detaillierte Verfahren der Anwendung und Anpassung, je nach Bedarf, zu definieren.
Management de Programme - Gestion de la Configuration - Partie 101 : Identification de la configuration
La présente recommandation est une déclinaison des principes identifiés dans l’EN 9223-100, elle :
- s’appuie sur les concepts reconnus au niveau international,
- propose des principes d’organisation et de mise en oeuvre de la gestion de la configuration suivant les dimensions « programme » et « entreprise », tout en privilégiant la dimension « programme »,
- traite de l’identification de la configuration mais pas des modalités de la gestion des contrats.
Il revient à chaque responsable de programme de définir les modalités d’application et d’ajustement nécessaires.
Vodenje programov - Vodenje konfiguracije - 101. del: Identifikacija konfiguracije
Obstoječi dokument je izključen iz načel, opisanih v standardu EN 9223-100, in:
temelji na mednarodno priznanih konceptih;
predlaga organizacijska načela in izvedbene postopke za vodenje konfiguracije z obeh vidikov: »programa« in »podjetja«, s poudarkom na vidiku »programa«;
obravnava identifikacijo konfiguracije, ne pa tudi metod upravljanja pogodbe.
Vsaka oseba, odgovorna za program, določi podrobne načine uporabe in po potrebi prilagajanja.
General Information
Standards Content (Sample)
SLOVENSKI STANDARD
SIST EN 9223-101:2018
01-maj-2018
Vodenje programov - Vodenje konfiguracije - 101. del: Identifikacija konfiguracije
Programme Management - Configuration Management - Part 101: Configuration
identification
Programm-Management - Konfigurationsmanagement - Teil 101:
Konfigurationsidentifizierung
Management de Programme - Gestion de la Configuration - Partie 101 : Identification de
la configuration
Ta slovenski standard je istoveten z: EN 9223-101:2018
ICS:
03.100.70 Sistemi vodenja Management systems
49.020 Letala in vesoljska vozila na Aircraft and space vehicles in
splošno general
SIST EN 9223-101:2018 en,fr,de
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.
---------------------- Page: 1 ----------------------
SIST EN 9223-101:2018
---------------------- Page: 2 ----------------------
SIST EN 9223-101:2018
EN 9223-101
EUROPEAN STANDARD
NORME EUROPÉENNE
March 2018
EUROPÄISCHE NORM
ICS 35.080; 49.020
English Version
Programme Management - Configuration Management -
Part 101: Configuration identification
Management de Programme - Gestion de la Programm-Management - Konfigurationsmanagement
Configuration - Partie 101 : Identification de la - Teil 101: Konfigurationsidentifizierung
configuration
This European Standard was approved by CEN on 1 October 2017.
CEN members are bound to comply with the CEN/CENELEC Internal Regulations which stipulate the conditions for giving this
European Standard the status of a national standard without any alteration. Up-to-date lists and bibliographical references
concerning such national standards may be obtained on application to the CEN-CENELEC Management Centre or to any CEN
member.
This European Standard exists in three official versions (English, French, German). A version in any other language made by
translation under the responsibility of a CEN member into its own language and notified to the CEN-CENELEC Management
Centre has the same status as the official versions.
CEN members are the national standards bodies of Austria, Belgium, Bulgaria, Croatia, Cyprus, Czech Republic, Denmark, Estonia,
Finland, Former Yugoslav Republic of Macedonia, France, Germany, Greece, Hungary, Iceland, Ireland, Italy, Latvia, Lithuania,
Luxembourg, Malta, Netherlands, Norway, Poland, Portugal, Romania, 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
© 2018 CEN All rights of exploitation in any form and by any means reserved Ref. No. EN 9223-101:2018 E
worldwide for CEN national Members.
---------------------- Page: 3 ----------------------
SIST EN 9223-101:2018
EN 9223-101:2018 (E)
Contents Page
European foreword . 3
Introduction . 4
1 Scope . 5
2 Normative references . 5
3 Terms and definitions . 5
4 The configuration identification and its place in the overall programme
Configuration Management . 6
4.1 Nature of the configuration identification process. 6
4.2 Identification: starting point for other Configuration Management processes . 6
4.3 Tasks associated with identification. 7
5 Configuration identification principles . 8
5.1 General . 8
5.2 Attribution of a configuration item to an authority . 9
5.3 Configuration items selection . 9
5.4 Data selection . 10
5.5 Configuration baselines . 10
5.6 Evolution of identification throughout a programme lifecycle . 15
5.7 Configuration identification activities throughout a programme lifecycle . 16
6 Specific cases . 19
6.1 Component off the shelf (COTS) . 19
6.2 Configuration items shared by several programmes. 20
6.3 Programmes with shared responsibilities . 21
(informative) Document management prerequisite necessary for Configuration
Management . 22
Bibliography . 23
2
---------------------- Page: 4 ----------------------
SIST EN 9223-101:2018
EN 9223-101:2018 (E)
European foreword
This document (EN 9223-101:2018) 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 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 September 2018, and conflicting national standards
shall be withdrawn at the latest by September 2018.
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.
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, 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 the United Kingdom.
3
---------------------- Page: 5 ----------------------
SIST EN 9223-101:2018
EN 9223-101:2018 (E)
Introduction
1
The finality of Configuration Management is to assure during the whole product lifecycle :
consistency and commonality of the technical information among all actors;
traceability of this technical information.
For that purpose, Configuration Management organizes and implements the following activities:
selection of items and technical information that shall be submitted to Configuration Management,
under clearly established responsibility (configuration identification);
capture, keeping this information and making it available (configuration status accounting);
verification and validation of the coherence of this information at defined steps of the product
lifecycle (configuration verifications, reviews and audits);
technical changes and gaps processing in order to keep the consistency of this information
(configuration control).
1
See EN ISO 9000:2005.
4
---------------------- Page: 6 ----------------------
SIST EN 9223-101:2018
EN 9223-101:2018 (E)
1 Scope
The present document is declined from the principles described in the EN 9223-100, it:
is based on internationally-recognised concepts;
proposes organisational principles and implementation processes for Configuration Management
from both viewpoints: “programme” and “company”, with emphasis on the “programme”
viewpoint;
deals with configuration identification but not contract management methods.
It is up to each person responsible for a programme to define the detailed methods of application and
tailoring as necessary.
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 9100, Quality Management Systems — Requirements for Aviation, Space and Defense organizations
EN 9223-100, Programme Management — Configuration Management — Part 100: A guide for the
2
application of the principles of configuration management
2
EN 9223-105, Programme Management — Configuration Management — Part 105: Glossary
EN ISO 9000, Quality management systems — Fundamentals and vocabulary
ISO 10007:2003, Quality management systems — Guidelines for configuration management
ISO/IEC 6523-1, Information technology — Structure for the identification of organizations and
organization parts — Part 1: Identification of organization identification schemes
ISO/IEC 6523-2, Information technology — Structure for the identification of organizations and
organization parts — Part 2: Registration of organization identification schemes
NF L 09-001A, Identification of aerospace components — Part numbers writing
3 Terms and definitions
For the purposes of this document, the terms and definitions given in EN ISO 9000, ISO 10007:2003 and
EN 9200 apply.
ISO and IEC maintain terminological databases for use in standardization at the following addresses:
• IEC Electropedia: available at http://www.electropedia.org/
• ISO Online browsing platform: available at http://www.iso.org/obp
2
Published as ASD-STAN Prestandard at the date of publication of this standard. http://www.asd-stan.org/
5
---------------------- Page: 7 ----------------------
SIST EN 9223-101:2018
EN 9223-101:2018 (E)
The specific terms needed to understand and to use the document are the object of definitions
appearing in EN 9223-105.
4 The configuration identification and its place in the overall programme
Configuration Management
4.1 Nature of the configuration identification process
This process is mainly a decisional process (preparing decision and decide) dedicated to configuration
items and data selection.
Its objectives are to define the perimeter of the configuration according to future management, i. e.:
identify what shall be controlled;
identify what shall be recorded;
identify what shall be submitted to configuration audit.
Within this framework, configuration identification is based on an organisation that:
associates customers, industrial partners and suppliers to jointly assure tasks and responsibilities;
associates each configuration item to a decisional authority;
allocates decision-making delegations throughout a network of customers, partners, suppliers
according to selection decisions;
describes the evolution of a decisional system during time;
uses existing documentation management systems (see Annex A);
uses existing technical data management systems;
details identification methods as described in a Configuration Management plan.
4.2 Identification: starting point for other Configuration Management processes
The decision, by an authority, to submit an item and its associated documentation to the overall
Configuration Management processes is named configuration identification, it has the following
consequences:
the item is thus “identified” as a “configuration item” for this authority and the delegated
authorities;
the whole content of the “identified configuration” of the configuration item is submitted to all
Configuration Management processes under the responsibility of the authority that proceeded to
these selections;
all that has not been selected at an authority level shall be managed at a delegated level and, at least
at the design level authority.
As an output of this process, the product is structured according to a configuration items breakdown,
consistent with decision-making (responsibility) breakdown and products breakdowns.
6
---------------------- Page: 8 ----------------------
SIST EN 9223-101:2018
EN 9223-101:2018 (E)
Figure 1 — Place of the configuration identification process in Configuration Management
processes
In the above figure:
if the prior configuration baseline is the functional configuration baseline (FBL), the new
configuration baseline is allocated configuration baseline (ABL);
if the prior configuration baseline is the allocated configuration baseline, the new configuration
baseline is the product configuration baseline (PBL).
4.3 Tasks associated with identification
4.3.1 Documentation Management Tasks
Documentation management tasks are not part of configuration identification but are sometimes
associated to it. To set up a system of identifiers/codification of items, documents and samples ensures
the uniqueness of the tracking (see Annex A).
The corresponding verifications are detailed, phase by phase, in 5.7.
4.3.2 Configuration Management tasks prior to identification
In order to enable an authority to select configuration item or data, this item or data necessarily exists
or has been subject to a decision of existence and can be identified (description and identifier). Thus,
the item name appears in a breakdown and an identifier is given by the designer, allowing the different
7
---------------------- Page: 9 ----------------------
SIST EN 9223-101:2018
EN 9223-101:2018 (E)
stakeholders to exchange in order to define the content and the perimeter of its documentation. These
Configuration Management tasks shall be recorded.
If item or data have not been yet treated as a configuration item or configuration data for the
considered authority, this item or data shall, most of the time, be considered as a configuration item by
a delegated authority (down flowed to the subcontractor) or at least its designer.
The process of authority appropriation or transfer will be treated in the following chapters.
4.3.3 Identifier of items, identification documentation and specimens
When a product is changed, its product identifier (on the document or specimen) is updated to reflect
the new configuration, when:
the updated product is no longer interchangeable, functionally or physically, with the product it
replaces;
the updated product requires new or revised testing, maintenance, repair, training, operating
procedures;
the updated product has different restrictions. Example: use restrictions.
5 Configuration identification principles
5.1 General
The configuration item is defined by an “identified” set of documents and associated data.
This above defined set establishes the boundary of the Configuration Management authority of this
item.
3
In order to establish its intervention perimeter, each authority assumes at its level, the following
decisions:
take into account the configuration items and data for which it has been given delegation of
authority upon Configuration Management;
select at proper times:
components items for which it self-ensures authority upon configuration, then selects the
technical data (or documents) necessary to delimit them and describe their configuration;
items for which it decides to delegate management authority and designates the delegate.
propose to higher level authorities the configuration items and associated data for which they are
supposed to take the decision concerning the configuration.
The following actions are often associated to this configuration identification tasks:
3
Several authority levels exist and each authority is responsible for the configuration identification at its level.
8
---------------------- Page: 10 ----------------------
SIST EN 9223-101:2018
EN 9223-101:2018 (E)
verification of the setting up of an identifier (item number, official designation, alias, etc.) and its
uniqueness for each item where configuration is managed (see NF L 09-001 and ISO/IEC 6523-1
and ISO/IEC 6523-2);
verification of the completeness and efficiency of the configuration documentation describing the
configuration item (see 5.3.1);
verification of the setting-up of relevant identifiers on selected documents.
5.2 Attribution of a configuration item to an authority
Attribution of an item to an authority, as described in EN 9223-100, is set up progressively and
discontinuously during the system preliminary design.
This attribution is delegated, starting with the system management authority.
5.3 Configuration items selection
5.3.1 Principles of selecting configuration items
Within the framework of its mandate, each authority shall select items the control of which will be
further implemented by this authority.
This selection usually progresses in a sequential but not in a continuous manner, at specific moments as
the programme progresses.
A sufficient amount of configuration items shall be selected to guarantee a full control of the system. A
contrario, only just necessary number of configuration items shall be selected to ensure an efficient
control. Any overmuch selection will provoke a decrease in the control process efficiency but a cost
increase for further control.
The selection of configuration items shall be based on an appropriate risks cotation.
5.3.2 Progressiveness of the configuration items selection
During the item design, the designer shall be left enough freedom as long as possible in order to assume
the technical decisions at his responsibility level. According to these technical choices and to the criteria
described hereafter, the decision to select an item occurs when the configuration item data must be
shared.
5.3.3 Selection criteria of configuration items
In accordance with 5.3.1, the usual criteria are based on the risk represented by the item for the
programme and are mainly (non-restrictive list):
safe use of the item;
critically or complexity;
potential importance upon the global cost;
importance on functions and performances;
importance on operating condition and logistic support;
9
---------------------- Page: 11 ----------------------
SIST EN 9223-101:2018
EN 9223-101:2018 (E)
importance on reliability and maintainability;
potential consequences on programme organisation;
legal, regulatory and contractual requirements;
specificities of each configuration baseline.
5.4 Data selection
5.4.1 Data selection principles
Within the framework of its mandate and for a given configuration item, each authority selects data or
documents upon which he will assume further control.
Necessary data and documents shall be selected to subsequently ensure an efficient control of
configuration baselines and configuration status associated to specimens. A contrario, only the data and
documents necessary to ensure an efficient control shall be selected. Any overmuch selection will
provoke a decrease in Configuration Management efficiency or a cost increase.
When an authority wants to select only some pieces of data contained in a document as configuration
data, it is the authority’s responsibility to specify the provisions intended to guarantee implementation
of Configuration Management principles concerning this data.
NOTE One possibility is to extract and gather selected data in specific documents. Another possibility is to
affect the data as attributes of the given configuration item.
5.4.2 Progressiveness in selecting configuration data
Like items selection, data selection is achieved in a sequential manner when establishing
configuration baselines. This selection is based on the criteria defined in the Configuration
Management plan.
This selection begins with data and documents which precise the requirements associated to the
functions which shall be implemented in the configuration item.
During design, this sequence ensures designers are given enough freedom to adapt themselves to
design difficulties and to outline the programme content freezing, just in time, irreversible options by
selecting functional, allocated then physical data.
Decision to select data occurs when data information must be exchanged. This selection is implemented
according to a pre-established schedule and based on the programme breakdown structure or any
other organisational document of the programme.
5.4.3 Criteria for selection configuration data
Selection of data is based on the same criteria than items selection (see 5.3.3).
5.5 Configuration baselines
5.5.1 General
A configuration baseline is established when during the product lifecycle it is necessary to agree on a
baseline which shall support further Configuration Management activities.
10
---------------------- Page: 12 ----------------------
SIST EN 9223-101:2018
EN 9223-101:2018 (E)
Generally, three configuration baselines are distinguished:
functional configuration baseline;
allocated configuration baseline;
product configuration baseline.
Those configuration baselines are only made of documents.
4
Other configuration statuses are derived from those configuration baselines
Other configuration baselines than those mentioned above can include products and sub-products in
some progress state. Thus, a configuration baseline may be established:
to be used as a starting point for definition qualification (configuration of a qualification specimen);
to define configuration baselines made of successive configuration status during an incremental
development;
when there are some major configuration changes, at main manufacturing process milestones;
during major retrofit stages;
etc.
Whatever the implemented Configuration Management system may be, traceability and consistency
between the different configuration baselines must be guaranteed.
5.5.2 Functional configuration baseline
Functional configuration baseline of a configuration item is the agreed baseline to start the
preliminary design process for this item.
This baseline is generally named by its internationally-acknowledged abbreviation FBL (Functional
Baseline).
Its purpose is to describe functional requirements of the configuration item, so it is essentially made of:
technical requirement specification, in an agreed version for that purpose;
selection of descriptive elements associated with the agreed solution.
After creation and before formalization, functional configuration baseline is subject to analysis, for
example during a design review.
It is generally declared “functional configuration baseline” by a decision of the Configuration
Management authority for this item.
4
Configuration statuses are those defined in the Configuration Management plan.
11
---------------------- Page: 13 ----------------------
SIST EN 9223-101:2018
EN 9223-101:2018 (E)
NOTE All the selected data set, gathered as “functional configuration baseline”, constitutes an output of the
identification process and an input of the status accounting process.
5.5.3 Allocated configuration baseline
Allocated configuration baseline is the agreed baseline to start the detailed design process for the
configuration item.
This baseline is generally named by its internationally-acknowledged abbreviation ABL (Allocated
Baseline).
This configuration is based on requirements allocation to subordinate items and takes into account:
functional requirements imposed by the functional configuration baseline, taking into account its
belonging to miscellaneous functional allocations;
legal requirements related to product;
constraints deriving from the future use of the configuration item (logistics, manufacturing,
operating, support, etc.);
requirements on configuration item external interfaces;
constraints related to design choice concerning configuration item;
justification of the above-mentioned requirements.
It describes and imposes:
the configuration item architecture through its internal breakdown;
performances allocations to subordinated configuration items when item performances depend on
these allocations;
design requirements stemming from design choices of the configuration item.
It links together (call or document tree links) the requirements derived from the functional
configuration baseline to requirements allocated to subordinate configuration items, through a
requirements traceability file, for instance a requirements allocation justification file or DJE (Dossier
Justificatif d’allocation des Exigences).
It formalizes and contains or refers to:
the functional and physical description of the configuration item and its external interfaces
(preliminary definition file, functional schemes, weight breakdown allocation, reliability allocation,
security and consumption model allocations, etc.);
the description of the configuration item internal interfaces (physical and functional interfaces);
the whole set of configuration items breakdowns (Configuration Management breakdown,
assembly breakdown, logistic breakdown).
NOTE It is advisable to group the constitutive elements of this configuration baseline together in a file (paper
or numeric) for further control process efficiency.
12
---------------------- Page: 14 ----------------------
SIST EN 9223-101:2018
EN 9223-101:2018 (E)
It shall be noticed that the nature of information contained in this file is half-way between technical
specifications and definition file. Indeed this file is composed of technical choices description as the
definition file, but it also contains requirements for the sub-systems.
5.5.4 Product configuration baseline
Product configuration baseline is the agreed configuration, attached to the decision to start
industrialisation and/or mass production processes.
This baseline is generally named by its internationally-acknowledged abbreviation PBL (Product
Baseline).
It contains or refers to:
updated functional configuration baseline of the configuration item (technical requirement
specification and specification documents);
updated functional configuration baseline of configuration items of higher level, when necessary;
updated allocated configuration baseline (allocation documents and description of internal
interfaces).
It takes into account:
functional requirements imposed by the functional configuration baseline;
requirements of interfaces external to the configuration item;
design requirements imposed by the allocated configuration baselines.
It describes and imposes:
configuration item architecture through its miscellaneous breakdowns;
definition of the configuration item;
particular manufacturing requirements (imposed processes);
verification and control requirements;
technical requirements associated to others processes (supply, support, utilisation, etc.).
It links together (call or documentation links):
manufacturing choices (breakdowns, technologies and interfaces) to requirements imposed to
subordinate configuration items;
the new configuration baseline with its previous configuration baseline(s).
It formalizes and contains or refers to:
the functional and physical description of the configuration item and its external interfaces
(definition files, imposed processes, control specifications, etc.).
13
---------------------- Page: 15 ----------------------
SIST EN 9223-101:2018
EN 9223-101:2018 (E)
This configuration is acquired when progress in the detailed design was observed by stakeholders, so
that:
the acquired definition is enough justified to serve as reference for industrialisation and/or mass
production;
identified residual risks are reduced to a level consistent with the commitments to be achieved.
This configuration must be traceable from previous configurations.
It is subject to a specific review.
This configuration can be a set of
...
Questions, Comments and Discussion
Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.