EN 9223-100:2018

Programme Management - Configuration Management - Part 100: A guide for the application of the principles of configuration management

The present document:
-   is based on internationally-recognized concepts;
-   proposes organisational principles and implementation processes for configuration management from both viewpoints: "programme" and "company", with emphasis on the "programme" viewpoint.
The required procedures for implementation and necessary tailoring have to be prescribed for each programme.
This document encompasses some aspects of the relationship between configuration management and contract management, but does not address contract management procedures.
Intended for use in complex programmes (aerospace, defence, etc.), this document is an extension of standard ISO 10007 Quality management systems - Guidelines for configuration management.
This document is coherent with EN 9200 Programme management - Guidelines for project management specifications.
The described principles concern all the stakeholders in the programme (authorities, manufacturers, skills, etc.) from the feasibility phase to disposal. These principles can be applied or tailored to any products (material or software).

Programm-Management - Konfigurationsmanagement - Teil 100: Anwendungsanleitung für die Grundsätze des Konfigurationsmanagement

Das vorliegende Dokument
- 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.
Die erforderlichen Verfahren zur Umsetzung und notwendigen Anpassung sind für jedes Programm fest-zulegen.
Dieses Dokument umfasst einige Aspekte des Zusammenhanges zwischen dem Konfigurationsmanagement und dem Vertragsmanagement, behandelt allerdings nicht die Verfahren des Vertragsmanagements.
Dieses Dokument ist zur Anwendung in komplexen Programmen (Luftfahrt-, Raumfahrt- und Verteidigungs¬industrie usw.) gedacht und stellt eine Erweiterung der Norm ISO 10007, Quality management systems - Guidelines for configuration management dar.
Dieses Dokument entspricht EN 9200, Luft- und Raumfahrt - Programm-Management - Richtlinie für eine Projektmanagement-Spezifikation.
Die beschriebenen Grundsätze betreffen alle Interessengruppen im Programm (verantwortliche Stellen, Hersteller, Disziplinen usw.) von der Durchführbarkeitsphase bis zur Entsorgung. Diese Grundsätze können auf alle Pro¬dukte (materielle Produkte oder Software) angewendet oder angepasst werden.

Management de Programme - Gestion de la Configuration - Partie 100 : Guide pour la mise en œuvre des principes de la gestion de la configuration

Le présent document :
-   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 deux dimensions « programme » et « entreprise », tout en privilégiant la dimension « programme ».
Il convient pour chaque programme de définir les modalités d’application et d’ajustement nécessaires.
Ce document traite certains aspects des relations entre la gestion de la configuration et la gestion des contrats mais elle ne traite pas des modalités de la gestion des contrats.
La présente recommandation constitue, au profit des programmes complexes (aéronautique, armement, ...), un prolongement de la norme ISO 10007 Management pour la Qualité - Lignes directrices pour la gestion de la configuration.
Le présent document est cohérent avec la norme EN 9200 Management de programme - Recommandation pour une spécification de management de projet.
Les principes exposés concernent tous les acteurs du programme (organismes, industriels, métiers, ...) depuis la faisabilité jusqu'au retrait de service. Ils peuvent être appliqués ou adaptés à l’ensemble des produits matériels ou logiciels.

Vodenje programov - Vodenje konfiguracije - 100. del: Vodilo za uporabo načel upravljanja konfiguracije

Ta dokument:
 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«.
Za vsak program je treba predpisati zahtevane postopke za izvedbo in potrebno prilagajanje.
Ta dokument obsega nekatere vidike odnosa med vodenjem konfiguracije in upravljanjem pogodbe, ne obravnava pa postopkov upravljanja pogodbe.
Namenjen je uporabi v kompleksnih programih (aeronavtika, obramba itn.) in predstavlja razširitev standarda ISO 10007 Sistemi vodenja kakovosti — Smernice za vodenje konfiguracije.
Ta dokument je skladen s standardom EN 9200 Vodenje programov — Smernice za specifikacijo vodenja projekta.
Opisana načela zadevajo vse deležnike programa (organi, proizvajalci, spretnosti itn.), od faze izvedljivosti do odlaganja. Ta načela se lahko uporabijo ali prilagodijo kateremu koli izdelku (materialu ali programski opremi).

General Information

• Status: Published
• Publication Date: 06-Mar-2018
• Withdrawal Date: 29-Sep-2018
• ICS: 35.080 - Software
• ICS: 49.020 - Aircraft and space vehicles in general
• Technical Committee: ASD-STAN - Aerospace
• Drafting Committee: ASD-STAN/D 1/S 6 - Engineering
• Current Stage: 6060 - Definitive text made available (DAV) - Publishing
• Start Date: 07-Mar-2018
• Completion Date: 07-Mar-2018
• Ref Project: SIST EN 9223-100:2018 - Programme Management - Configuration Management - Part 100: A guide for the application of the principles of configuration management

Standards Content (Sample)

SLOVENSKI STANDARD
SIST EN 9223-100:2018
01-maj-2018
9RGHQMHSURJUDPRY9RGHQMHNRQILJXUDFLMHGHO9RGLOR]DXSRUDERQDþHO
XSUDYOMDQMDNRQILJXUDFLMH
Programme Management - Configuration Management - Part 100: A guide for the
application of the principles of configuration management
Programm-Management - Konfigurationsmanagement -Teil 100: Anwendungsanleitung
für die Grundsätze des Konfigurationsmanagement

Management de Programme - Gestion de la Configuration - Partie 100 : Guide pour la

mise en oeuvre des principes de la gestion de la configuration
Ta slovenski standard je istoveten z: EN 9223-100: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-100: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-100:2018
---------------------- Page: 2 ----------------------
SIST EN 9223-100:2018
EN 9223-100
EUROPEAN STANDARD
NORME EUROPÉENNE
March 2018
EUROPÄISCHE NORM
ICS 35.080; 49.020
English Version
Programme Management - Configuration Management -
Part 100: A guide for the application of the principles of
configuration management

Management de Programme - Gestion de la Programm-Management - Konfigurationsmanagement

Configuration - Partie 100 : Guide pour la mise en -Teil 100: Anwendungsanleitung für die Grundsätze

œuvre des principes de la gestion de la configuration des Konfigurationsmanagement

This European Standard was approved by CEN on 25 September 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-100:2018 E

worldwide for CEN national Members.
---------------------- Page: 3 ----------------------
SIST EN 9223-100:2018
EN 9223-100:2018 (E)
Contents Page

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

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

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

3 Terms and definitions ................................................................................................................................... 6

4 Configuration management: basic concepts ......................................................................................... 6

4.1 “Programme” and “company” viewpoints .............................................................................................. 6

4.2 Objectives, services and interfaces with other disciplines .............................................................. 7

4.2.1 Objectives ........................................................................................................................................................... 7

4.2.2 Services to be provided ................................................................................................................................. 7

4.2.3 Input from/Output towards other disciplines...................................................................................... 8

4.3 Configuration management processes .................................................................................................... 9

5 Configuration management as part of programme management .............................................. 10

5.1 Configuration baselines ............................................................................................................................. 10

5.1.1 Main configuration baselines .................................................................................................................. 10

5.1.2 Functional configuration baseline ......................................................................................................... 10

5.1.3 Allocated configuration baseline ............................................................................................................ 10

5.1.4 Product Configuration baseline .............................................................................................................. 10

5.1.5 Other configurations status ...................................................................................................................... 11

5.2 Configuration management and associated responsibilities ....................................................... 11

5.2.1 Principle .......................................................................................................................................................... 11

5.2.2 Configuration item - Configuration data .............................................................................................. 11

5.2.3 Configuration items designated by the customer ............................................................................ 11

5.2.4 Configuration management authority and configuration management board ..................... 12

5.2.5 Other authorities involved in configuration related decisions ................................................... 13

5.3 Configuration management, during the life cycle processes........................................................ 13

5.3.1 General ............................................................................................................................................................. 13

5.3.2 Configuration Management, during the expression of need ........................................................ 13

5.3.3 Configuration Management during the preliminary design process ........................................ 13

5.3.4 Configuration management, during the detailed design process ............................................... 13

5.3.5 Configuration management, during the qualification process .................................................... 14

5.3.6 Configuration management during the industrialisation and production processes ........ 14

5.3.7 Configuration management, during the utilisation process ......................................................... 15

5.3.8 Configuration management, during the disposal process ............................................................. 15

5.3.9 Particular cases ............................................................................................................................................. 16

5.4 Quality audit of the configuration management system ................................................................ 16

6 Configuration management processes ................................................................................................. 16

6.1 Configuration identification ..................................................................................................................... 16

6.2 Configuration control ................................................................................................................................. 17

6.3 Configuration status accounting ............................................................................................................. 19

6.4 Configuration verifications, reviews and audits ............................................................................... 20

7 Management specification and configuration management plan .............................................. 20

7.1 General ............................................................................................................................................................. 20

7.2 Configuration management requirements ......................................................................................... 21

7.3 Configuration management plan ............................................................................................................ 21

---------------------- Page: 4 ----------------------
SIST EN 9223-100:2018
EN 9223-100:2018 (E)

(informative) List of the main tasks of configuration management ........................................ 23

(informative) Summary of a configuration management plan (Example) ............................ 29

(informative) Cartography of standards generally used by configuration

management people .................................................................................................................................... 31

Bibliography ................................................................................................................................................................. 32

---------------------- Page: 5 ----------------------
SIST EN 9223-100:2018
EN 9223-100:2018 (E)
European foreword

This document (EN 9223-100: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.
---------------------- Page: 6 ----------------------
SIST EN 9223-100:2018
EN 9223-100:2018 (E)
1 Scope
The present document:
 is based on internationally-recognized concepts;

 proposes organisational principles and implementation processes for configuration management

from both viewpoints: “programme” and “company”, with emphasis on the “programme”

viewpoint.

The required procedures for implementation and necessary tailoring have to be prescribed for each

programme.

This document encompasses some aspects of the relationship between configuration management and

contract management, but does not address contract management procedures.

Intended for use in complex programmes (aerospace, defence, etc.), this document is an extension of

standard ISO 10007 Quality management systems — Guidelines for configuration management.

This document is coherent with EN 9200 Programme management — Guidelines for project

management specifications.

The described principles concern all the stakeholders in the programme (authorities, manufacturers,

skills, etc.) from the feasibility phase to disposal. These principles can be applied or tailored to any

products (material or software).
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.

Applicable standards may change according to the related skills (mechanical, chemical and software,

etc. or according to the different domains (Defence, Space, Aircraft, etc.)

EN 9223-101, Programme Management — Configuration Management — Part 101: Configuration

identification

EN 9223-102, Programme Management — Configuration Management — Part 102: Configuration status

accounting

EN 9223-103, Programme Management — Configuration Management — Part 103: Configuration

Verifications, Reviews and Audits

EN 9223-104, Programme Management — Configuration Management — Part 104: Configuration

Control

EN 9223-105, Programme Management — Configuration Management — Part 105: Glossary

EN 9100, Quality Management Systems — Requirements for Aviation, Space and Defence organizations

1) Published as ASD-STAN Prestandard at the date of publication of this standard http://www.asd-stan.org/.

---------------------- Page: 7 ----------------------
SIST EN 9223-100:2018
EN 9223-100:2018 (E)
EN ISO 9000, Quality management systems — Fundamentals and vocabulary
EN ISO 9001, Quality management systems — Requirements

ISO 10007:2003, Quality management systems — Guidelines for configuration management

NOTE A list of publications is given in the bibliography. A table summarizes the relationships of the main

documents dealing with configuration management identified at the time this document was published.

3 Terms and definitions

For the purposes of this document, the terms and definitions given in EN 9223-105 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
4 Configuration management: basic concepts
4.1 “Programme” and “company” viewpoints

The following diagram presents configuration management from the “programme” and “company”

viewpoints.
Figure 1 — “Programme” and “Company” viewpoints in configuration management

The necessity of combining these two viewpoints implies that common concepts and methods for the

different stakeholders make these viewpoints consistent. The programme manager is responsible for

defining management methods for “programme” configuration management, taking into account the

programme particular needs and especially it's phasing and scheduling.

The present document develops the configuration management according to the “programme”

viewpoint. The “company” viewpoint is given preference in other standards.
---------------------- Page: 8 ----------------------
SIST EN 9223-100:2018
EN 9223-100:2018 (E)
4.2 Objectives, services and interfaces with other disciplines
4.2.1 Objectives

In order to achieve convergence towards the expected product, the main objectives of “programme”

configuration management are:

 to know the physical and functional description of the product, its components and the associated

supporting elements;
 to enable each participant to use coherent and validated data.

From the designer to the end-user, each stakeholder uses and provides his partners with technical data

about products, processes and their associated means. This collection of data grows as the programme

progresses. Configuration management arrangements must therefore be adjusted at every level in the

customer/supplier chain in an integrated engineering of products, processes and associated resources.

The distinction must be made between:

 specific processes and the associated tools which are part of the product's configuration

(mandatory processes, for example);

 pre-existing processes and the associated tools, for which configuration management is at the

supplier's sole initiative.

Doing that, the supplier may apply the principles outlined in the present document.

4.2.2 Services to be provided

Configuration management serves any stakeholders who need to share and/or exchange technical data.

The added value generated by the data consistency guarantee and their integrity over time therefore

benefits:

 the customer who is responsible for expressing the objectives in terms of prices and cost, lead

times and performance;

 the supplier in his different roles (designer, purchaser, manufacturer, and where applicable,

providers of services during in-service operation, etc.);

 the end-user for his different activities (operation and maintenance scheduling, provisioning,

material fleet management, etc.).

Data to be managed in the scope of Configuration Management encompass the whole product life cycle,

from the initial expression of need to disposal, through the successive configuration baselines (see 5.1).

Configuration management shall as a whole:

 provide a global view on the specifications and on the functional and physical characteristics of the

products in order to ensure convergence towards fulfilment of the requirements;
 apply to all components of the product and to the associated interfaces;

 encompass all the stakeholders involved in preparing and making any decision relating to

configuration;
---------------------- Page: 9 ----------------------
SIST EN 9223-100:2018
EN 9223-100:2018 (E)
 ensure traceability:
 of the configuration data shared and/or exchanged among the stakeholders;

 of the decision elements related to shared and/or exchanged configuration data.

 address together with Quality Assurance, the nonconformities and requests for concessions.

4.2.3 Input from/Output towards other disciplines

Configuration management needs existence and elaboration of a documentary management system, a

technical data management system and a product lifecycle management system, fitted to programme

characteristics.

Addressees and use of the outputs of Configuration Management are introduced in the above 4.2.2.

In addition, Configuration Management depends on direct or indirect inputs from other processes and

disciplines of the programme management, such as:

 a product-tree, which shall be consistent with the one used to draw out the Work Breakdown

Structure and in which Configuration Items are identified and delimited (see 5.2.2 and 5.2.3);

 programme organisation, a base for designating and mandating the Configuration Management

Authorities in the frame of delegation system (see 5.2.4);

 programme phasing and scheduling, a base for programming the Configuration Management

processes and key-events, including establishment of the Configuration Baselines (see 5.1 and 5.3);

 requests for technical changes, deviations, concessions (see 6.2); such requests may result from

processing technical events, anomalies and nonconformities;
 statements of conformity/nonconformity to:
 the Configuration Management processes;
 the applicable configuration.

The above inputs/outputs, and related interfaces, should be described in a formal document, for

example the applicable Configuration Management Plan or Quality system management documentation.

---------------------- Page: 10 ----------------------
SIST EN 9223-100:2018
EN 9223-100:2018 (E)
4.3 Configuration management processes
Figure 2 — Different configuration management processes
Conventionally, configuration management is organized in four processes:
 configuration identification;
 configuration control;
 configuration status accounting;
 configuration audit (reviews and verifications).
These processes are defined from:
 establishment of “configuration management authorities” (see 5.2.4);
 product breakdown into configuration items (see 5.2.2 and 5.2.3);
 for each configuration item:
 establishment of the configuration baseline (see 5.1);

 control of the technical changes and discrepancies with this configuration baseline (see 6.2).

---------------------- Page: 11 ----------------------
SIST EN 9223-100:2018
EN 9223-100:2018 (E)

At each level of the product breakdown, allocation of configuration management tasks and associated

decision-making delegation (or subdelegation) are defined to the lowest level found competent.

The corresponding provisions are described in the configuration management plan established in

response to the management specification (see Annex B).
5 Configuration management as part of programme management
5.1 Configuration baselines
5.1.1 Main configuration baselines

Whenever it is necessary during the life cycle of a product to agree on a baseline to be used for

identifying future configurations, a “configuration baseline” is established.
Three main configuration baselines are distinguished:
 the functional configuration baseline;
 the allocated configuration baseline;
 the product configuration baseline.

Independently from the implemented configuration management system, traceability must be

guaranteed between the different configuration baselines.

The configuration baselines establishment is an integral part of the identification process which is

described in the EN 9223-101.
5.1.2 Functional configuration baseline

The functional configuration baseline is the agreed baseline used to launch the preliminary design.

This baseline, in its initial official issue, is generally named by its internationally-acknowledged

abbreviation FBL (Functional Baseline).

The baseline constitution is part of the Identification process as described in EN 9223-101.

5.1.3 Allocated configuration baseline

The allocated configuration baseline is the agreed baseline used to launch the detailed design.

This baseline, in its initial official issue, is generally named by its internationally-acknowledged

abbreviation ABL (Allocated Baseline).

This configuration takes into account the requirements of the Functional Baseline (FBL) and prepares

the future building of the Product Baseline (PBL).
5.1.4 Product Configuration baseline

The product configuration baseline is the agreed baseline, in connection with the decision to launch

industrialization and/or production processes.

This baseline, in its initial official issue, is generally named by its internationally-acknowledged

abbreviation PBL (Product Baseline).
---------------------- Page: 12 ----------------------
SIST EN 9223-100:2018
EN 9223-100:2018 (E)

This configuration takes into account the requirements from the Functional Baseline (FBL) or from the

Allocated Baseline.
5.1.5 Other configurations status

Others configurations are derived from one of the three configuration baselines mentioned above, in

connection with key events in the life cycle of one specimen (or a delimited batch), such as:

 approved current configuration;
 as-designed configuration;
 “as built” configuration;
 “in use” configuration.

These different configurations and their relationship are described in EN 9223-102.

5.2 Configuration management and associated responsibilities
5.2.1 Principle
Each component of a product is submitted to configuration management.

As part of the “programme” configuration management system, this management is organised through a

series of authorities, delegation mandates and items.
Each mandate is summed up as a couple “one configuration item – one authority”.
5.2.2 Configuration item - Configuration data
To cope with the product complexity, the product is structured into components.

At a given level, any component or set of components which is treated as a single entity during the

configuration management process is established as a configuration item. Because of its consequences

on the programme efficiency and economy, the selection of the level of aggregation/breaking down of

the components is an important decision.

For each configuration item, data (functional, physical and interfaces) are gathered in agreed

configuration baselines, from which identified/described discrepancies are controlled.

Configuration Items and data selection is done by the configuration identification process, as described

in EN 9223-101.
5.2.3 Configuration items designated by the customer

On the basis of criteria outlined above, a customer may designate the configuration items on which he

estimates necessary to intervene directly (these items may have different names; in this document, they

are called “customer configuration items”). As soon as possible, this designation should be made and

this designation, as well as the role that the customer intends to reserve for himself, should be

implemented in the contract and more particularly in the Specification of Management.

NOTE The fact that a component of the product tree is designated as a “customer configuration item” does

not impose that the higher level assembly of this item is a customer configuration item.

---------------------- Page: 13 ----------------------
SIST EN 9223-100:2018
EN 9223-100:2018 (E)
5.2.4 Configuration management authority and configuration management board

The setting up of the “programme” configuration management is based on the responsible of the

programme appointing a “system level configuration management authority” entitled to pronounce the

decisions related to the configuration management of the system.
This authority is in charge of:

 validating organisation arrangements and processes proposed in response to the requirements of

“programme” configuration management;
 selecting item and data;
 identifying as such the configuration baselines;

 taking decisions regarding technical changes and conformity discrepancies concerning system

level;

 making sure of consistency and efficiency in the processing of technical changes and the

nonconformities at each subordinate level;

 ensuring that the impacts of the decisions on contractual aspects are taken into account.

This authority may rely on a structure, sometimes referred as “system configuration management

board”.

Through a top-down delegation process, the configuration management of each configuration item is

entrusted to a competent management authority invested with appropriate decision power.

The configuration item management authority is the lowest level of authority whose field of

competence entirely includes the content of the item configuration.

Except opposite arrangements stipulated in his mandate, the field of competence of the configuration

item management authority does not include interfaces with upper and adjacent items, and therefore

its external specifications (Technical Requirement Specifications/TRS).

NOTE The configuration of specifics items of the operational and logistic support is, as a rule, closely linked

with the configurations of corresponding system configuration items. The associated fields of competence and

their limits, for the decisional authority, should be consistent with such links.

Each authority is in charge of implementing at its level the arrangements specified at the system level,

after having previously:
 acknowledged its own field of competence;

 clarified it as necessary from directives issued at system level (interfaces with other authorities

fields of competence, configuration baselines of each configuration item, selection of configuration

data);

 designated the stakeholders he mandates in the downstream chain of delegation as well as other

ones that shall be involved in technical changes and nonconformities processing;

 established, when necessary, ad hoc board and defined arrangements for its operations and

deliberations.
---------------------- Page: 14 ----------------------
SIST EN 9223-100:2018
EN 9223-100:2018 (E)

Any authority acting under a delegation shall enable, under conditions agreed upon, the delegating

authority with the right to watch its operations and on the decisions either taken or in process within

its field of competence.
5.2.5 Other authorities involved in configuration related decisions

The configuration related decisions may consider issues (schedule, cost, quality, contract, industrial

aspects) that cause the decisions to be taken outside the Configuration Management scope.

The relationships between the authorities involved in such decisions shall be specified in the

programme management plan and/or called back in the Configuration Management Plan.

Once taken, the decision and any subsequent effects are recorded under the Configuration Management

process.
5.3 Configuration management, during the life cycle processes
5.3.1 General

Configuration management is closely integrated in all stakeholders involved in the programme and in

the life cycle processes. The programme manager shall, in connectio
...