ASD-STAN PREN 9223-100-2016 Programme Management - Configuration Management - Part 100 A guide for the application of the principles of configuration management (Edition P 1).pdf

1、 ASD-STAN STANDARD NORME ASD-STAN ASD-STAN NORM ASD-STAN prEN 9223-100: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 100: A guide for the application of the principles of configuration management Programm-Management Konfigurationsmanagement Teil 100: Anwendungsanleitung fr die Prinzipien des Konfigurationsmanagement Management de Programme Gestion

3、de la Configuration Partie 100 : Guide pour la mise en uvre des principes de la gestion de la configuration This “Aerospace 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 t

4、he needs of the European Aerospace Industry. It has been technically approved by the experts of the concerned Domain following member comments. Subsequent to the publication of this Prestandard, the technical content shall not be changed to an extent that interchangeability is affected, physically o

5、r functionally, without re-identification of the standard. After examination and review by users and formal agreement of ASD-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 Europe

6、an Standard (EN). The CEN national members have then to implement the EN at national level by giving the EN the status of 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

7、 needs of the European Aerospace Industry. The use of this standard is entirely voluntary, and its applicability and suitability 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 a

8、t least every five years at which time it may be revised, reaffirmed, stabilized or cancelled. ASD-STAN invites you to send 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 an

9、y form or by any means, electronic, mechanical, photocopying, recording, or otherwise, without prior written permission of 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

10、 of publication to ASD-STAN General Domain prEN 9223-100:2016 (E) 2 Contents Page 1 Scope 4 2 Normative references 4 3 Terms and definitions 5 4 Configuration management: basic concepts 5 4.1 “Programme” and “company” viewpoints 5 4.2 Objectives, services and interfaces with other disciplines 6 4.3

11、Configuration management processes 8 5 Configuration management as part of programme management . 9 5.1 Configuration baselines 9 5.2 Configuration management and associated responsibilities 10 5.3 Configuration management, during the life cycle processes . 12 5.4 Quality audit of the configuration

12、management system . 15 6 Configuration management processes 15 6.1 Configuration identification 15 6.2 Configuration control . 16 6.3 Configuration status accounting 18 6.4 Configuration verifications, reviews and audits 18 7 Management specification and configuration management plan . 19 7.1 Genera

13、l 19 7.2 Configuration management requirements 19 7.3 Configuration management plan . 20 (informative) List of the main tasks of configuration management . 21 Annex A(informative) Summary of a configuration management plan . 26 Annex B(informative) Cartography of standards generally used by configur

14、ation management Annex Cpeople 28 prEN 9223-100: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 ASD-STANs General Process Manual, this standard ha

15、s received approval for Publication. prEN 9223-100:2016 (E) 4 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

16、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 proced

17、ures. 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 specificat

18、ions”. 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, in whol

19、e 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. Applicable standards may change according to the related skills (mechanical, chemical and software, etc. or according

20、 to the different domains (Defence, Space, Aircraft, etc.) EN 9223-101, Programme Management Configuration Management Part 101: Configuration identification1)EN 9223-102, Programme Management Configuration Management Part 102: Configuration status accounting1)EN 9223-103, Programme Management Config

21、uration Management Part 103: Configuration Verifications, Reviews and Audits1)EN 9223-104, Programme Management Configuration Management Part 104: Configuration Control1)EN 9223-105, Programme Management Configuration Management Part 105: Glossary1)EN 9100, Quality Management Systems Requirements fo

22、r Aviation, Space and Defense organizations EN ISO 9000, Quality management systems Fundamentals and vocabulary EN ISO 9001, Quality management systems Requirements 1)Published as ASD-STAN Prestandard at the date of publication of this standard. http:/www.asd-stan.org/ prEN 9223-100:2016 (E) 5 ISO 1

23、0007: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 def

24、initions For the purposes of this document, the terms and definitions given in EN 9223-105 Configuration Management Glossary apply. 4 Configuration management: basic concepts 4.1 “Programme” and “company” viewpoints The following diagram presents configuration management from the “programme” and “co

25、mpany” 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 man

26、agement methods for “programme” configuration management, taking into account the programme particular needs and especially its phasing and scheduling. The present document develops the configuration management according to the “programme” viewpoint. The “company” viewpoint is given preference in ot

27、her standards. prEN 9223-100:2016 (E) 6 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 th

28、e 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 collectio

29、n 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 a

30、ssociated tools which are part of the products configuration (mandatory processes, for example); pre-existing processes and the associated tools, for which configuration management is at the suppliers sole initiative. Doing that, the supplier may apply the principles outlined in the present document

31、. 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 objectiv

32、es 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, provisi

33、oning, 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

34、 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 a

35、nd making any decision relating to configuration; prEN 9223-100:2016 (E) 7 ensure traceability: o of the configuration data shared and/or exchanged among the stakeholders; o of the decision elements related to shared and/or exchanged configuration data. address, together with Quality Assurance, the

36、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 characteristi

37、cs. 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 th

38、e 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 phas

39、ing 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, an

40、omalies and nonconformities; statements of conformity/nonconformity to: o the Configuration Management processes; o 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 Qu

41、ality system management documentation. prEN 9223-100:2016 (E) 8 4.3 Configuration management processes Figure 2 Different configuration management processes Conventionally, configuration management is organized in four processes: configuration identification; configuration control; configuration sta

42、tus 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: o establishment of the configuration

43、baseline (see 5.1); o control of the technical changes and discrepancies with this configuration baseline (see 6.2). 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

44、 competent. prEN 9223-100:2016 (E) 9 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

45、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 configu

46、ration 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

47、 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

48、 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 n

49、amed 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