iTeh StandardsiTeh Standards
EURUSD
Your shopping cart is empty.
CEN

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

Status
Published
Publication Date
06-Mar-2018
Withdrawal Date
29-Sep-2018
ICS
35.080 - Software
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-101:2018 - Programme Management - Configuration Management - Part 101: Configuration identification

Buy Standard

EN 9223-101:2018EN 9223-101:2018
PreviousNext
Standard
EN 9223-101:2018
English language
23 pages
sale 10% off
Preview
sale 10% off
Preview
e-Library read for
1 day

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 .
...

Questions, Comments and Discussion

Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.

This May Also Interest You

CEN
EN 9115:2018(Main)
Quality Management Systems - Requirements for Aviation, Space and Defense Organizations - Deliverable Software (Supplement to EN 9100)
SIST EN 9115:2018

The requirements of EN 9100 apply with the following clarification for software.
This European standard supplements the EN 9100 standard requirements for deliverable software and
contains quality management system requirements for organizations that design, develop, and/or
produce deliverable software and services for the aviation, space, and defence industry. This includes,
as required, support software that is used in the development and maintenance of deliverable software
and services. The deliverable software may be stand-alone, embedded, mobile application, or loadable
into a target computer
This deliverable software may also be part of services (e.g., cloud environment, web hosted solutions or
platforms).
Where the use of Hardware Description Language (HDL) or high order language is utilized as the design
source of electronic hardware [e.g., Application Specific Integrated Circuit (ASIC), Programmable Logic
Device (PLD)]; the organization and customer, and/or supplier shall agree on the extent of applicability
of this supplement.
NOTE For airborne electronic hardware guidance, see RTCA/DO-254 or EUROCAE ED-80. For operations
requirements, see EN 9100, clause 8.
Where Commercial-Off-The-Shelf (COTS) or non-developmental software is integrated into a
deliverable product, the organization and customer shall agree on the extent of applicability of this
supplement.
For the purposes of this document, the terms “product” and “software product” are considered
synonymous.
For the purposes of this document, the term “services” may be considered a product.

  • Standard
    27 pages
    English language
    sale 10% off
    e-Library read for
    1 day
CEN
EN 9223-102:2018(Main)
Programme Management - Configuration Management - Part 102: Configuration status accounting
SIST EN 9223-102:2018

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.

  • Standard
    21 pages
    English language
    sale 10% off
    e-Library read for
    1 day
CEN
EN 9223-104:2018(Main)
Programme Management - Configuration Management - Part 104: Configuration Control
SIST EN 9223-104:2018

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 control 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.

  • Standard
    33 pages
    English language
    sale 10% off
    e-Library read for
    1 day
CEN
EN 9223-105:2018(Main)
Programme Management - Configuration Management - Part 105: Glossary
SIST EN 9223-105:2018

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 -04, Programme Management - Configuration Management - Part 104: Configuration Control

  • Standard
    14 pages
    English language
    sale 10% off
    e-Library read for
    1 day
CEN
EN 9223-100:2018(Main)
Programme Management - Configuration Management - Part 100: A guide for the application of the principles of configuration management
SIST EN 9223-100:2018

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).

  • Standard
    32 pages
    English language
    sale 10% off
    e-Library read for
    1 day
CEN
EN 9223-103:2018(Main)
Programme Management - Configuration Management - Part 103: Configuration Verifications, Reviews and Audits
SIST EN 9223-103:2018

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;
-   deals with verifications, reviews and audits tending towards the validation of the configuration information consistency. 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.
Important remark:
Configuration audit doesn’t be confused with quality audit (for detailed information, see 4.1).
This document does not deal with configuration system audits (quality audit) deployed within the scope of a programme. These audits stem from quality audits as defined in EN ISO 9001 (process conformity or efficiency audits).

  • Standard
    25 pages
    English language
    sale 10% off
    e-Library read for
    1 day
CEN
EN 9320:2014(Main)
Aerospace series - Programme Management - General guidelines for acquisition and supply of open systems
SIST EN 9320:2015

These general guidelines cover the open system acquisition and supply processes.
There is an increasing requirement for systems designed and produced by industry, particularly in the aeronautic, space and defence fields, to be used with other systems designed, produced, acquired and operated independently.
The concept of open systems is touched upon in many systems engineering documents. This document deals specifically with this subject. To this end, through the various processes applied, it provides information to stakeholders (buyers, suppliers, designers, subcontractors, supervisors, etc.) on the best practice to be adopted.
The specific nature of openness for a system is defined by all the following properties:
-   Interchangeability,
-   Interoperability,
-   Upgradability,
-   Reusability,
-   Reversibility,
-   Flexibility,
-   Affordability.
These properties are defined in the glossary for these general guidelines.
These general guidelines are largely based on the structure and system life cycle processes described in standard ISO/IEC 15288:2008.
The characteristics of openness also relate to:
-   The products or services offered by the company (target systems resulting from use of company processes).
-   The company’s processes (project systems). Several stakeholders, with their own assignments, cultures, jobs and geographical locations, different working methods, modelling frameworks, standards, tools and aids, etc. are involved in the activities, which are sometimes multidisciplinary, of the internal and external processes of a company. These diverse elements are not necessarily all suited to working together without causing certain risks, a loss of autonomy, effectiveness and/or efficiency, etc. A company must, for example, develop its ability and capacity in terms of interoperability both internally (between the systems of which it is made) and externally (with other partners), including, by way of an example:
-   Ability of each stakeholder and each department involved to maintain efficient and trusting relationships with other stakeholders, taking into account deadline, cost and quality objectives,
-   Ability to exchange, communicate and use the necessary flows (data, information, knowledge, materials, energy) autonomously, without error and dynamically throughout the life cycle of the target system,
-   Ability to coordinate, synchronise and manage common tasks and share and use resources (human, machine or application) and services efficiently and appropriately.

  • Standard
    44 pages
    English language
    sale 10% off
    e-Library read for
    1 day
CEN
prEN 9125(Main)
Aerospace series - Requirements for Aviation, Space, and Defence Organizations - Non-Deliverable Software
oSIST prEN 9115-002:2022

1.1 General
This document defines the requirements for the effective control of non-deliverable software. This document can be used during the development, test, production, release, use, maintenance, and retirement of non-deliverable software. This can include non-deliverable software procured from outside manufacturers and incorporated in the production, evaluation, test, acceptance, or calibration of a deliverable product. When an organization outsources one or more of the processes involved in the creation of non-deliverable software, this document applies.
This document focuses solely on the unique requirements of the operational processes that pertain to non-deliverable software as defined by section 1.2. Operational processes not covered in this document are addressed by the organization’s Quality Management System (QMS), based on EN 9100 and/or ISO 9001.
1.2 Application
This document applies to non-deliverable software (including firmware) that directly affects the quality of a deliverable product or service. Following are several applications and supporting examples of non-deliverable software that is within scope of this document:
-   Design and Development: modelling, simulation, virtual reality, virtual machine, data science, Computer-Aided Design (CAD), Three-Dimensional (3D) modelling, analysis tools, software compiler, and code generators.
-   Manufacture: additive manufacturing data files, Computer Numerical Controlled (CNC) programs, robotics, factory automation, tools that load deliverable software, special process (e.g., heat treat, shot peen, sonic wall inspection), and automated manufacturing software (i.e., pick and place).
-   Verification and Validation: Coordinate Measuring Machine (CMM) programs, hardware or software qualification, code coverage, test scripts, analysis tools, acceptance test, production acceptance, calibration (inspection, test or calibration), simulator, and emulator.
Non-deliverable software is not delivered to the customer under a contract or agreement.
The following types of software are not within scope of this standard:
-   deliverable software (refer to EN 9115);
-   embedded manufacturing and test equipment software (e.g., operating system);
-   business systems or office software; and
-   information systems software for business applications.

  • Draft
    13 pages
    English language
    sale 10% off
    e-Library read for
    1 day
CEN
EN 9115:2018(Main)
Quality Management Systems - Requirements for Aviation, Space and Defense Organizations - Deliverable Software (Supplement to EN 9100)
SIST EN 9115:2018

The requirements of EN 9100 apply with the following clarification for software.
This European standard supplements the EN 9100 standard requirements for deliverable software and
contains quality management system requirements for organizations that design, develop, and/or
produce deliverable software and services for the aviation, space, and defence industry. This includes,
as required, support software that is used in the development and maintenance of deliverable software
and services. The deliverable software may be stand-alone, embedded, mobile application, or loadable
into a target computer
This deliverable software may also be part of services (e.g., cloud environment, web hosted solutions or
platforms).
Where the use of Hardware Description Language (HDL) or high order language is utilized as the design
source of electronic hardware [e.g., Application Specific Integrated Circuit (ASIC), Programmable Logic
Device (PLD)]; the organization and customer, and/or supplier shall agree on the extent of applicability
of this supplement.
NOTE For airborne electronic hardware guidance, see RTCA/DO-254 or EUROCAE ED-80. For operations
requirements, see EN 9100, clause 8.
Where Commercial-Off-The-Shelf (COTS) or non-developmental software is integrated into a
deliverable product, the organization and customer shall agree on the extent of applicability of this
supplement.
For the purposes of this document, the terms “product” and “software product” are considered
synonymous.
For the purposes of this document, the term “services” may be considered a product.

  • Standard
    27 pages
    English language
    sale 10% off
    e-Library read for
    1 day
CEN
EN 9223-102:2018(Main)
Programme Management - Configuration Management - Part 102: Configuration status accounting
SIST EN 9223-102:2018

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.

  • Standard
    21 pages
    English language
    sale 10% off
    e-Library read for
    1 day