EN 9223-105:2018

SLOVENSKI STANDARD
01-maj-2018
Vodenje programov - Vodenje konfiguracije - 105. del: Slovar
Programme Management - Configuration Management - Part 105: Glossary
Programm-Management - Konfigurationsmanagement - Teil 105: Glossar
Management de Programme - Gestion de la Configuration - Partie 105 : Glossaire
Ta slovenski standard je istoveten z: EN 9223-105:2018
ICS:
01.040.49 Letalska in vesoljska tehnika Aircraft and space vehicle
(Slovarji) engineering (Vocabularies)
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-105
EUROPEAN STANDARD
NORME EUROPÉENNE
March 2018
EUROPÄISCHE NORM
ICS 35.080; 49.020
English Version
Programme Management - Configuration Management -
Part 105: Glossary
Management de Programme - Gestion de la Programm-Management - Konfigurationsmanagement
Configuration - Partie 105 : Glossaire - Teil 105: Glossar
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-105:2018 E
worldwide for CEN national Members.

Contents Page
European foreword . 3
1 Scope . 4
2 Terms and definitions . 4
Bibliography . 14

European foreword
This document (EN 9223-105: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 organizations 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.
1 Scope
This document explains the wording in use within the following standards:
EN 9223-100, Programme Management — Configuration Management — Part 100: A guide for the
application of the principles of configuration management
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
2 Terms and definitions
For the purposes of this document, the following terms and definitions apply.
Help for definitions reading
Notes are integral parts of the initial definition whereas comments provide additional information to this
definition and are specific to this documents set.
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.1
corrective action
action to eliminate the cause of a detected nonconformity or other undesirable situation
Note 1 to entry: There can be more than one cause for a nonconformity.
Note 2 to entry: Corrective action is taken to prevent recurrence whereas preventive action is taken to prevent
occurrence.
Note 3 to entry: There is a distinction between, curative action, correction and corrective action.
[SOURCE: EN ISO 9000]
2.2
curative action
action to restore the conformity of a product initially nonconforming see paragraph “rework”
2.3
preventive action
action to eliminate the cause of a potential nonconformity or other undesirable potential situation
Note 1 to entry: There can be more than one cause for a potential nonconformity.
Note 2 to entry: Preventive action is taken to prevent occurrence whereas corrective action is taken to prevent
recurrence.
[SOURCE: EN ISO 9000]
2.4
anomaly
gap between a current situation and an expected one
Note 1 to entry: An anomaly justifies an investigation which might lead to the discovery of a nonconformity or
a defect.
[SOURCE: EN 9200]
2.5
item
the item includes the notions of component, compound, part, ingredient, assembly, functional element,
product and system, bought or manufactured by a manufacturer
It concerns hardware, software, or a combination of them. Elements of support system are also
concerned (test bench, tooling, user documentation, packaging, etc.).
Items can be selected as configuration item, or not; they are documented.
2.6
configuration item
entity within a configuration that satisfies an end use function
Note 1 to entry: It is a set (hardware, software, documents or their combination) that has been selected for
configuration management and is managed as a single entity in the configuration management process.
A configuration item can be, on its own, specified, identified, built, checked and maintained.
[SOURCE: adapted from ISO 10007:2003]
2.7
attribute
specific characteristic of a data or information that can be used as a selection or ordering criteria
2.8
audit
systematic, independent and documented process for obtaining audit evidence and evaluating it
objectively to determine the extent to which the audit criteria are fulfilled
Note 1 to entry: Although this definition derived from EN ISO 19011, and can be used to define configuration
audit, configuration audits shall not be based on the EN ISO 19011 standard, which mainly addresses process
audits.
[SOURCE: EN ISO 19011]
2.9
configuration audit
a configuration management process that step-by-step examines products in order to check:
 they comply with requirements;
 they achieve the performances and the physical and/or functional characteristics, as required in the
previous formalized Baseline configuration(s);
 they comply with product design information.
Configuration audits can be clearly split into functional and physical configuration audits.
Note 1 to entry: Each configuration item shall be subject to configuration audits.
Note 2 to entry: Configuration audit process applied to a configuration item only takes place at specific
moments of its lifecycle.
Note 3 to entry: These audits must end up with the formal establishment of the Baseline configuration from the
candidate Baseline configuration.
Functional Configuration Audit (FCA): this is a formal examination to verify that a configuration item
has achieved the functional and performance characteristics specified in its product configuration
information (ISO 10007:2003).
Physical Configuration Audit (PCA): this is a formal examination to verify that a configuration item
has achieved the physical characteristics specified in its product configuration information
(ISO 10007:2003).
3.0
dispositioning authority
person or a group of persons assigned responsibility and authority to make decisions on the
configuration
Note 1 to entry: Dispositioning authority can also be called a “configuration control board”.
Note 2 to entry: Relevant interested parties within and outside the organization should be represented on the
dispositioning authority.
Note 3 to entry: This authority is not restricted to change board.
[SOURCE: adapted from ISO 10007:2003]
3.1
configuration
interrelated functional and physical characteristics of a product defined in product configuration
information
Note 1 to entry: Set of functional and physical characteristics of a product (hardware and software), as defined
in the documentation and obtained in the physical product.
[SOURCE: ISO 10007:2003]
3.2
updated approved configuration
configuration that takes into account the Baseline configuration and all decided engineering changes
3.3
applicable configuration (for production)
configuration of a product as expected to be produced. It is established for a unit or batch (for instance,
decision to start production)
Note 1 to entry: At a specific time, several applicable configurations can exist for different physical units of a
same product.
Note 2 to entry: Deviations are also included in the applicable configuration.
Note 3 to entry: This configuration can be recorded for a unit:
 of production;
 of qualification;
 of retrofit;
 to perform specific tests.
3.4
as-built configuration
configuration of a product item established from the applicable configuration and to which conformity
gaps and complementary configuration technical information is added
Note 1 to entry: Gaps shall be submitted to approval (concession).
Note 2 to entry: There are (almost) as many as-built configurations as product physical units.
Note 3 to entry: Complementary configuration technical information can include batch/lot or serial number etc.
3.5
configuration Baseline
approved product configuration information that establishes the characteristics of a product at a point
in time that serves as reference for activities throughout the lifecycle of the product
Note 1 to entry: Throughout the product lifecycle, a configuration Baseline is established to agree on a basis
from which other configuration Baselines can be identified (described), as necessary.
Note 2 to entry: Three main configuration Baselines can be distinguished:
 the Functional configuration Baseline (FBL);
 the Development or Allocated configuration Baseline (ABL);
 the Production configuration Baseline (PBL);
These configuration Baselines consist only of documents.
Note 3 to entry: Configuration Baselines other than the three above mentioned may also include products or
sub-products in a given state of progress. Ex.: configuration of a qualification unit.
[SOURCE: ISO 10007:2003]
3.6
in-use (as maintained) configuration
configuration of a product item based on the as-built configuration, to which the consequences of the
in-service events on the configuration information are included (maintenance, damage, repair, potential
consumption, etc.)
3.7
concession (deviation, waiver)
permission to use or released a product that does not conform to specified requirements
Note 1 to entry: A concession is generally limited to the delivery of the product that has nonconforming
characteristics within specified limits for an agreed time or quantity of that product.
Note 2 to entry: Concession is an ambiguous term since it covers concessions before production and after
production or in-service.
Note 3 to entry: In EN 9223-100 and EN 9223-101 to EN 9223-105:
 “deviation” is synonymous with “concession before production” (see EN ISO 9000);
 “waiver” is synonymous with “concession after production” or “in-service concession”.
Each time necessary, it should be mentioned:
 “Waiver after production”: if the nonconformity is detected during the production or before delivery;
 “In-service waiver” (in-use): if the nonconformity is detected in-service (in-use).
[SOURCE: adapted from ISO 10007:2003]
3.8
deviation permit
permission to depart from the originally specified requirements of a product prior to its realization
Note 1 to entry: synonymous in the present document to “concession before production” in the sense of
EN ISO 9000.
N
...