EN 9223-101:2018

SLOVENSKI STANDARD
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
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.

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.

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

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.
Introduction
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).
See EN ISO 9000:2005.
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
application of the principles of configuration management
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

Published as ASD-STAN Prestandard at the date of publication of this standard. http://www.asd-stan.org/
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.
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
...