1、 ASD-STAN STANDARD NORME ASD-STAN ASD-STAN NORM ASD-STAN prEN 9223-101:2016 Edition P1 2016-10 PUBLISHED BY THE AEROSPACE AND DEFENCE INDUSTRIES ASSOCIATION OF EUROPE - STANDARDIZATION Rue Montoyer 10 - 1000 Brussels - Tel. + 32 2 775 8126 - Fax. + 32 2 775 8131 - www.asd-stan.org ICS: Descriptors:
2、ENGLISH VERSION 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 This “Aerospac
3、e Series” Prestandard has been drawn up under the responsibility of ASD-STAN (The AeroSpace and Defence Industries Association of Europe - Standardization). It is published for the needs of the European Aerospace Industry. It has been technically approved by the experts of the concerned Domain follo
4、wing member comments. Subsequent to the publication of this Prestandard, the technical content shall not be changed to an extent that interchangeability is affected, physically or functionally, without re-identification of the standard. After examination and review by users and formal agreement of A
5、SD-STAN, the ASD-STAN prEN will be submitted as a draft European Standard (prEN) to CEN (European Committee for Standardization) for formal vote and transformation to full European Standard (EN). The CEN national members have then to implement the EN at national level by giving the EN the status of
6、a national standard and by withdrawing any national standards conflicting with the EN. ASD-STAN Technical Committee approves that: “This document is published by ASD-STAN for the needs of the European Aerospace Industry. The use of this standard is entirely voluntary, and its applicability and suita
7、bility for any particular use, including any patent infringement arising therefrom, is the sole responsibility of the user.” ASD-STAN reviews each standard and technical report at least every five years at which time it may be revised, reaffirmed, stabilized or cancelled. ASD-STAN invites you to sen
8、d your written comments or any suggestions that may arise. All rights reserved. No parts of this publication may be reproduced, stored in a retrieval system or transmitted, in any form or by any means, electronic, mechanical, photocopying, recording, or otherwise, without prior written permission of
9、 ASD-STAN. Order details: E-mail: salesasd-stan.org Web address: http:/www.asd-stan.org/ Edition approved for publication Comments should be sent within six months after the date of publication to ASD-STAN General Domain prEN 9223-101:2016 (E) 2 Contents Page Foreword 3 Introduction 4 1 Scope . 5 2
10、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 Ta
11、sks 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 progr
12、amme 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 manageme
13、nt prerequisite necessary for Configuration Annex AManagement 22 Bibliography . 23 prEN 9223-101:2016 (E) 3 Foreword This standard was reviewed by the Domain Technical Coordinator of ASD-STANs General Domain. After inquiries and votes carried out in accordance with the rules of ASD-STAN defined in A
14、SD-STANs General Process Manual, this standard has received approval for Publication. prEN 9223-101:2016 (E) 4 Introduction The finality of Configuration Management is to assure during the whole product lifecycle1): consistency and commonality of the technical information among all actors; traceabil
15、ity 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);
16、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
17、 keep the consistency of this information (configuration control). 1)See EN ISO 9000:2005. prEN 9223-101:2016 (E) 5 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 i
18、mplementation 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 me
19、thods of application and tailoring as necessary. 2 Normative references The following documents, in whole or in part, are normatively referenced in this document and are indispensable for its application. The latest edition of the referenced document (including any amendments) applies. EN 9100, Qual
20、ity 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 management2)EN 9223-105, Programme Management Configuration Management Part 105: Gloss
21、ary2)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 organi
22、zation 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
23、For the purposes of this document, the terms and definitions given in EN ISO 9000, ISO 10007:2003 and EN 9200 apply. The specific terms needed to understand and to use the document are the object of definitions appearing in EN 9223-105. 2)Published as ASD-STAN Prestandard at the date of publication
24、of this standard. http:/www.asd-stan.org/ prEN 9223-101:2016 (E) 6 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) ded
25、icated 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,
26、 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,
27、 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
28、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
29、 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 sel
30、ections; 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) brea
31、kdown and products breakdowns. prEN 9223-101:2016 (E) 7 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 allocate
32、d 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 no
33、t 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 paragraph 5.7. 4.3.2 Config
34、uration Management tasks prior to identification In order to enable an authority to select configuration item or data, this item or data necessarily exists or has been subject to a decision of existence and can be identified (description and identifier). Thus, the item name appears in a breakdown an
35、d an identifier is given by the designer, allowing the different stakeholders to Initial prior configuration baseline Updated prior configuration baseline Control Control IdentificatioConfiguration Verification, Review and Audit New configuration baseline Control Configuration Status Accounting Iden
36、tification prEN 9223-101:2016 (E) 8 exchange in order to define the content and the perimeter of its documentation. These Configuration Management tasks shall be recorded. If item or data have not been yet treated as a configuration item or configuration data for the considered authority, this item
37、or data shall, most of the time, be considered as a configuration item by a delegated authority (downflowed to the subcontractor) or at least its designer. The process of authority appropriation or transfer will be treated in the following chapters. 4.3.3 Identifier of items, identification document
38、ation and specimens When a product is changed, its product identifier (on the document or specimen) is updated to reflect the new configuration, when: the updated product is no longer interchangeable, functionally or physically, with the product it replaces; the updated product requires new or revis
39、ed testing, maintenance, repair, training, operating procedures; the updated product has different restrictions. Example: use restrictions. 5 Configuration identification principles 5.1 General The configuration item is defined by an “identified” set of documents and associated data. This above defi
40、ned set establishes the boundary of the Configuration Management authority of this item. In order to establish its intervention perimeter, each authority3) assumes at its level, the following decisions: take into account the configuration items and data for which it has been given delegation of auth
41、ority upon Configuration Management; select at proper times: o components items for which it self-ensures authority upon configuration, then selects the technical data (or documents) necessary to delimit them and describe their configuration; o items for which it decides to delegate management autho
42、rity and designates the delegate. propose to higher level authorities the configuration items and associated data for which they are supposed to take the decision concerning the configuration. The following actions are often associated to this configuration identification tasks: verification of the
43、setting up of an identifier (item number, official designation, alias, etc.) and its uniqueness for each item where configuration is managed (see NF L 09-001 and ISO/IEC 6523-1 and ISO/IEC 6523-2); 3)Several authority levels exist and each authority is responsible for the configuration identificatio
44、n at its level. prEN 9223-101:2016 (E) 9 verification of the completeness and efficiency of the configuration documentation describing the configuration item (see 5.3.1); verification of the setting-up of relevant identifiers on selected documents. 5.2 Attribution of a configuration item to an autho
45、rity Attribution of an item to an authority, as described in EN 9223-100, is set up progressively and discontinuously during the system preliminary design. This attribution is delegated, starting with the system management authority. 5.3 Configuration items selection 5.3.1 Principles of selecting co
46、nfiguration items Within the framework of its mandate, each authority shall select items the control of which will be further implemented by this authority. This selection usually progresses in a sequential but not in a continuous manner, at specific moments as the programme progresses. A sufficient
47、 amount of configuration items shall be selected to guarantee a full control of the system. A contrario, only just necessary number of configuration items shall be selected to ensure an efficient control. Any overmuch selection will provoke a decrease in the control process efficiency but a cost inc
48、rease for further control. The selection of configuration items shall be based on an appropriate risks cotation. 5.3.2 Progressiveness of the configuration items selection During the item design, the designer shall be left enough freedom as long as possible in order to assume the technical decisions
49、 at his responsibility level. According to these technical choices and to the criteria described hereafter, the decision to select an item occurs when the configuration item data must be shared. 5.3.3 Selection criteria of configuration items In accordance with subclause 5.3.1, the usual criteria are based on the risk represented by the item for the programme and are mainly (non restrictive list): safe use of the item; critically or complexicity; potential importance upon the glo
