1、 ASD-STAN STANDARD NORME ASD-STAN ASD-STAN NORM ASD-STAN prEN 9223-102: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 102: Configuration status accounting Programm-Management Konfigurationsmanagement Teil 102: Aufzeichnung des Konfigurationsstatus Management de Programme Gestion de la Configuration Partie 102 : Enregistrement de la configuration Thi
3、s “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 the needs of the European Aerospace Industry. It has been technically approved by the experts of the concerned D
4、omain 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 or functionally, without re-identification of the standard. After examination and review by users and formal agr
5、eement 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 European Standard (EN). The CEN national members have then to implement the EN at national level by giving the EN the
6、 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 needs of the European Aerospace Industry. The use of this standard is entirely voluntary, and its applicabilit
7、y 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 at least every five years at which time it may be revised, reaffirmed, stabilized or cancelled. ASD-STAN invites
8、 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 any form or by any means, electronic, mechanical, photocopying, recording, or otherwise, without prior written pe
9、rmission 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 of publication to ASD-STAN General Domain prEN 9223-102:2016 (E) 2 Contents Page Foreword 3 Introduction 3 1 S
10、cope . 4 2 Normative references . 4 3 Terms and definitions. 4 4 The configuration status accounting process and its place in the overall programme Configuration Management 5 4.1 Configuration status accounting process overview . 5 4.2 Nature of the configuration status accounting process 6 4.3 Reco
11、rding initialisation . 7 4.4 Configuration status accounting and lifecycle . 8 5 Records associated with the configuration identification process 8 6 Records associated with the configuration control process . 9 7 Records associated with the configuration verification, review and audit process . 10
12、8 Relationship with other processes . 11 8.1 Scope 11 8.2 Relationship with need specification process 11 8.3 Relationship with preliminary design process 11 8.4 Relationship with the detailed design process . 12 8.5 Relationship with qualification process . 13 8.6 Relationship with industrialisatio
13、n and production processes . 13 8.7 Relationship with operational in use process 14 8.8 Relationship with the disposal process . 15 9 Requirements for exchanging and/or sharing data . 15 10 Implementation of traceability requirements in the configuration status accounting process 16 (informative) In
14、formation system prerequisite needed for configuration status Annex Aaccounting 17 Non exhaustive examples of attributes that allow to assure traceability 18 Annex BBibliography . 19 prEN 9223-102:2016 (E) 3 Foreword This standard was reviewed by the Domain Technical Coordinator of ASD-STANs General
15、 Domain. After inquiries and votes carried out in accordance with the rules of ASD-STAN defined in ASD-STANs General Process Manual, this standard has received approval for Publication. Introduction The finality of Configuration Management is to assure during the whole product lifecycle1): consisten
16、cy 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
17、, 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 verificati
18、ons, reviews and audits); technical changes and gaps processing in order to keep the consistency of this information (configuration control). 1)See EN ISO 9000. prEN 9223-102:2016 (E) 4 1 Scope The present document: is based on internationally-recognised concepts; proposes organisational principles
19、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 progra
20、mme responsible person to define the necessary details of application and tailoring in the Configuration Management plan. 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
21、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
22、Management Part 100: A guide for the application of the principles of configuration management2)EN 9223-105, Programme Management Configuration Management Part 105: Glossary2)EN ISO 9000, Quality management systems Fundamentals and vocabulary ISO 10007:2003, Quality management systems Guidelines for
23、 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. 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
24、-STAN Prestandard at the date of publication of this standard. http:/www.asd-stan.org/ prEN 9223-102:2016 (E) 5 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 con
25、figuration 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 t
26、hem and release them as accounts that can be used in aid of other processes (compliant with paragraph 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 co
27、nfiguration 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 manufactu
28、red 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
29、 before delivery; prEN 9223-102:2016 (E) 6 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
30、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. Fi
31、gure 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
32、 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 o
33、f 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 t
34、he safekeeping of the configuration information history; assuring the traceability of decisions. prEN 9223-102:2016 (E) 7 4.3 Recording initialisation Recording of configuration data presupposes that the following are defined taking into account the provisional estimation of the volume and complexit
35、y 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 re
36、cording 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 t
37、o 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, part
38、ners, 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 d
39、ata 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 (
40、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
41、 possible links between items and documents instead of links between documents. prEN 9223-102:2016 (E) 8 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
42、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 o
43、f 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 following paragraphs detail the captured and output data associated with each Configuration Management
44、 process. 5 Records associated with the configuration identification process CAPTURE: recording of configuration baseline data: o list and structure of the configuration items that build up the product (identifier, index, links); o documents (identifiers, index, links). OUTPUTS: the three approved c
45、onfiguration baselines (functional, allocated and production); the availability status of “formalized” documents and data associated with configuration baselines of a configuration item, so as functional and physical architecture; prEN 9223-102:2016 (E) 9 configuration status of specific specimens (
46、mock-up, demonstration specimens, prototypes, etc.) NOTE In order to facilitate all the Configuration Management tasks, the following data may be usefully associated to configuration data: decisional authority associated to configuration items; successive owners and “warrantors”. 6 Records associate
47、d with the configuration control process For that process, the same data is successively captured and returned: changes (from request to decision); decisions (change documentation, justification, rank of implementation, etc.); data of as designed configurations: o list and structure of the configura
48、tion items that build up the product (identifiers, index, links); o documents (identifiers, index, links). data of as-built configurations: o list (reference and serial number) of the selected components according to the required traceability; o listing of noticed nonconformity without any identifie
49、r difference between as designed and as-built configuration; o data specific to installation premises. consequences of changes on each concerned configuration; data of as-built and/or as-maintained configurations: applied changes, technical events, interventions, potential tracking, etc. This data is generally gathered in the log-book or product register file; nonconformity processing: o requests for deviations or concessions (identifier, subject, classification
