EN 9223-102:2018

Programme Management - Configuration Management - Part 102: Configuration status accounting

The present document:
-   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 capture, safekeeping and release of configuration information. It details the principles described in EN 9223-100.
It is up to each programme responsible person to define the necessary details of application and tailoring in the Configuration Management plan.

Programm-Management - Konfigurationsmanagement - Teil 102: Konfigurationsbuchführung

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,
- behandelt die Erfassung, Verwahrung und Herausgabe von Konfigurationsangaben. Es führt die in EN 9223-100 beschriebenen Grundsätze im Detail aus.
Es obliegt jeder für ein Programm verantwortlichen Person, die notwendigen Einzelheiten der Anwendung und Anpassung im Plan des Konfigurationsmanagements zu definieren.

Management de Programme - Gestion de la Configuration - Partie 102 : Enregistrement de la configuration

La présente recommandation :
-   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 la saisie, conservation et mise à disposition des informations de configuration. Elle précise les principes identifiés dans l’EN 9223-100.
Il revient à chaque responsable de programme de définir dans le plan de gestion de la configuration les modalités d’application et d’ajustement nécessaires.

Vodenje programov - Vodenje konfiguracije - 102. del: Računovodsko stanje 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«;
 obravnava zajemanje, hrambo in posredovanje informacij o konfiguraciji. Podrobno opredeljuje načela, opisana v standardu EN 9223-100.
Vsaka oseba, odgovorna za program, določi potrebne podrobnosti uporabe in prilagajanja načrta vodenja konfiguracije.

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-102:2018 - Programme Management - Configuration Management - Part 102: Configuration status accounting

Overview

EN 9223-102:2018 - Programme Management: Configuration Management - Part 102: Configuration status accounting (CEN) defines principles and processes for configuration status accounting within programme and company-level configuration management. Published by CEN (approved Oct 2017, issued Mar 2018), this standard focuses on the capture, safekeeping and controlled release of configuration information throughout the product lifecycle, with emphasis on the programme viewpoint. It elaborates the principles in EN 9223-100 and expects each programme to tailor application details in a Configuration Management Plan (CMP).

Key topics and requirements

• Configuration status accounting process: continuous recording of configuration data produced by identification, control and verification processes; storing and releasing configuration “accounts” for stakeholders.
• Configuration baselines and status types: treatment and reporting of baselines (functional, allocated, production) and common statuses such as as-designed, as-built, in-use, and other programme-defined statuses.
• Recording initialization: define objects to record (items, documents, attributes), object structure and database formats; plan roles, responsibilities, periodicity, storage, access, retention and suppression rules.
• Traceability and history: maintain history of configuration changes, decisions and justifications to ensure traceability across the lifecycle.
• Records by process: required records for configuration identification (item lists, document links), configuration control (change requests, decisions, implementation rank), and verification/reviews/audits.
• Data exchange and IT prerequisites: requirements for secure sharing and integration with customer/supplier systems; information system capabilities to protect, shelter and enable timely release of configuration information.
• Interface with lifecycle processes: guidance on relationships with specification, design, qualification, production, in‑use and disposal processes.

Practical applications and users

Who benefits:

• Programme managers and configuration managers in aerospace, defence and complex systems programmes
• Systems engineers, quality managers and supply chain partners responsible for product data integrity
• Organisations implementing EN 9100/ISO 9000 series who need robust configuration traceability

Typical uses:

• Establishing a CMP that defines how configuration status accounting will be implemented and tailored
• Implementing or specifying configuration management information systems (CMDBs, PLM, PDM) that capture baselines, changes and history
• Producing authoritative configuration reports for audits, production release and in-service support

Related standards

• EN 9223-100 (guidance on CM principles)
• EN 9223-105 (glossary)
• EN 9100, EN 9200, EN ISO 9000, ISO 10007

EN 9223-102:2018 is a practical, lifecycle-focused resource for organisations that need standardized approaches to capture, secure and release configuration information with clear traceability and auditability.

Standards Content (Sample)

SLOVENSKI STANDARD
01-maj-2018
9RGHQMHSURJUDPRY9RGHQMHNRQILJXUDFLMHGHO5DþXQRYRGVNRVWDQMH
NRQILJXUDFLMH
Programme Management - Configuration Management - Part 102: Configuration status
accounting
Programm-Management - Konfigurationsmanagement - Teil 102:
Konfigurationsbuchführung
Management de Programme - Gestion de la Configuration - Partie 102 : Enregistrement
de la configuration
Ta slovenski standard je istoveten z: EN 9223-102: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-102
EUROPEAN STANDARD
NORME EUROPÉENNE
March 2018
EUROPÄISCHE NORM
ICS 35.080; 49.020
English Version
Programme Management - Configuration Management -
Part 102: Configuration status accounting
Management de Programme - Gestion de la Programm-Management - Konfigurationsmanagement
Configuration - Partie 102 : Enregistrement de la - Teil 102: Konfigurationsbuchführung
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-102: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 status accounting process and its place in the overall programme
Configuration Management . 6
4.1 Configuration status accounting process overview . 6
4.2 Nature of the configuration status accounting process . 7
4.3 Recording initialisation . 8
4.4 Configuration status accounting and lifecycle . 9
5 Records associated with the configuration identification process . 9
6 Records associated with the configuration control process . 10
7 Records associated with the configuration verification, review and audit process . 11
8 Relationship with other processes . 12
8.1 Scope . 12
8.2 Relationship with need specification process . 12
8.3 Relationship with preliminary design process . 13
8.4 Relationship with the detailed design process. 13
8.5 Relationship with qualification process . 14
8.6 Relationship with industrialisation and production processes . 14
8.7 Relationship with operational in use process . 15
8.8 Relationship with the disposal process . 16
9 Requirements for exchanging and/or sharing data . 16
10 Implementation of traceability requirements in the configuration status accounting
process . 17
(informative) Information system prerequisite needed for configuration status
accounting . 18
(informative) Non exhaustive examples of attributes that allow to assure
traceability . 20
Bibliography . 21

European foreword
This document (EN 9223-102: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.
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.
1 Scope
The present document:
 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 capture, safekeeping and release of configuration information. It details the principles
described in EN 9223-100.
It is up to each programme responsible person to define the necessary details of application and
tailoring in the Configuration Management plan.
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 9200, Aerospace series — Programme management — Guidelines for project management
specifications
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
3 Terms and definitions
For the purposes of this document, the terms and definitions given in EN ISO 9000, ISO 10007 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
The specific terms needed to understand and to use the document are the object of definitions
appearing in EN 9223-105.
Published as ASD-STAN Prestandard at the date of publication of this standard. http://www.asd-stan.org/
4 The configuration status accounting process and its place in the overall
programme Configuration Management
4.1 Configuration status accounting process overview

Figure 1 — Place of the configuration status accounting process in Configuration Management
processes
Configuration status accounting is a process present during all activities of Configuration Management.
It consists in recording configuration data as outputs of the 3 other Configuration Management
processes, then to store them and release them as accounts that can be used in aid of other processes
(compliant with 4.3).
Configuration status linked to key steps during the life of a specimen (or a defined set of specimens) is
inferred from one or other of the three main configuration baselines. The following configuration status
can be found at some manufacturers or customers, called by example as follows:
 the updated approved configuration, including the configuration baseline completed with all
decided technical changes;
 “as-designed” configuration, associated to a specimen, batch or lot to be manufactured or foreseen;
 the “as-built” configuration: this configuration is characterized by gaps in compliance with as
designed configuration (these gaps are dealt with concessions). These gaps are the result of
technical events, anomalies, repairs, used life potential, etc. that have impacted the product before
delivery;
 the “in-use” configuration that takes into account technical events occurring during the operational
life of the specimen starting with as-built configuration. By example, these events can be technical
changes and deviations decided and applied during this life phase, so as technical events and
anomalies. Remaining nonconformities are usually dealt with concessions.
We can also find other status configurations as “as specified”, “as-planed” or “as-maintained”. The
configuration management plan defines the need and the content for particular status.

Figure 2 — Configuration baselines and configuration status (example)
4.2 Nature of the configuration status accounting process
This process is the support process central and essential to Configuration Management.
It is a support in the way that it uses the decisions from other Configuration Management processes and
returns them as usable accounts.
It is central in the way that any other Configuration Management process communicates through this
one.
It is essential because, during the whole lifecycle of the system or product, it assures the safekeeping,
the sharing (release) and the uniqueness of configuration information produced by other Configuration
Management processes.
It consists in:
 recording all the product or system configuration information with its validity status in an
information system;
 returning information in a defined format according to the needs of the users;
 assuring the safekeeping of the configuration information history;
 assuring the traceability of decisions.
4.3 Recording initialisation
Recording of configuration data presupposes that the following are defined taking into account the
provisional estimation of the volume and complexity of activities linked to Configuration Management:
 type of objects to be recorded (items, data, attributes, documents, etc.);
 structure of these objects (links between managed objects);
 data bases (including input/output formats, requests, etc.) that will be used for recording these
objects.
The recording environment must be adapted to the objects that shall be processed (their volume, but
also their nature: text, drawings, software data, etc.), protect them against any deterioration or any
unauthorized change, shelter them against natural disaster and other destructive accidents, and allow
to access them and to release them within an appropriate schedule to authorized stakeholders.
The recording system must take into account the means implemented in all the organisations involved
in the programme, in order to assure the incorporation of data stemming from other systems
(customers, partners, suppliers).
The recording activity must first be planned as regards:
 the receiving structure, (data structure, relations, roles);
 the data base structure.
The data organisation at each level of this structure shall foresee:
 the configuration data concerned by the recording;
 the configuration data attributes;
 the traceability and recording ability requirements;
 roles and responsibility;
 recording instance (periodicity, triggering events);
 rules for storage, sheltering, accessing, time schedule for keeping and suppression of records;
 templates for forms and reports;
 distribution criteria (taking into account need and right to know).
Data configuration recording must be initialized as early as possible in a product or system lifecycle.
In order to simplify the future documentation control, it is suitable to limit at the most documents
breakdown structures and to prefer each time it is possible links between items and documents instead
of links between documents.
4.4 Configuration status accounting and lifecycle

Figure 3 — Configuration status accounting
CAPTURE:
Data must be recorded during the whole lifecycle including the operational support process and up to
disposal.
OUTPUTS:
 a list of approved documents and data which are associated with configuration baselines and/or
with configuration status during the whole product lifecycle;
 gaps between the various configurations of a product or a specimen of this product (retrofit, repair,
etc.);
 history of configurations according to statements defined in the Configuration Management Plan
(CMP);
 history of decisions taken in the other Configuration Management processes with their justification.
The
...