1、BSI Standards PublicationWB11885_BSI_StandardCovs_2013_AW.indd 1 15/05/2013 15:06Programme Management Configuration ManagementPart 102: Configuration status accountingBS EN 9223102:2018EUROPEAN STANDARD NORME EUROPENNE EUROPISCHE NORM EN 9223-102 March 2018 ICS 35.080; 49.020 English Version Program
2、me Management - Configuration Management - Part 102: Configuration status accounting Management de Programme - Gestion de la Configuration - Partie 102 : Enregistrement de la configuration Programm-Management - Konfigurationsmanagement - Teil 102: Konfigurationsbuchfhrung This European Standard was
3、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 nati
4、onal 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 langu
5、age 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,
6、 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 EUROPEN DE NORMALISATION EUROPISCHES KOMITEE FR NOR
7、MUNG 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 worldwide for CEN national Members. Ref. No. EN 9223-102:2018 ENational forewordThis British Standard is the UK implementation of EN 9223102:2018.The UK
8、 participation in its preparation was entrusted to Technical Committee ACE/1, International and European Aerospace Policy and Processes.A list of organizations represented on this committee can be obtained on request to its secretary.This publication does not purport to include all the necessary pro
9、visions of a contract. Users are responsible for its correct application. The British Standards Institution 2018 Published by BSI Standards Limited 2018ISBN 978 0 580 90025 9ICS 35.080; 49.020Compliance with a British Standard cannot confer immunity from legal obligations.This British Standard was p
10、ublished under the authority of the Standards Policy and Strategy Committee on 31 March 2018.Amendments/corrigenda issued since publicationDate Text affectedBRITISH STANDARDBS EN 9223102:2018EUROPEAN STANDARD NORME EUROPENNE EUROPISCHE NORM EN 9223-102 March 2018 ICS 35.080; 49.020 English Version P
11、rogramme Management - Configuration Management - Part 102: Configuration status accounting Management de Programme - Gestion de la Configuration - Partie 102 : Enregistrement de la configuration Programm-Management - Konfigurationsmanagement - Teil 102: Konfigurationsbuchfhrung This European Standar
12、d 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 suc
13、h 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
14、 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, G
15、reece, 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 EUROPEN DE NORMALISATION EUROPISCHES KOMITEE
16、FR 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 worldwide for CEN national Members. Ref. No. EN 9223-102:2018 EBS EN 9223102:2018EN 9223-102:2018 (E) 2 Contents Page European foreword . 3 Introd
17、uction 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 .
18、 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 proce
19、ss 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 industrial
20、isation 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 (informati
21、ve) Information system prerequisite needed for configuration status accounting . 18 (informative) Non exhaustive examples of attributes that allow to assure traceability . 20 Bibliography . 21 BS EN 9223102:2018EN 9223-102:2018 (E) 3 European foreword This document (EN 9223-102:2018) has been prepar
22、ed 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 countrie
23、s 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. A
24、ttention 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 followi
25、ng 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, Nor
26、way, Poland, Portugal, Romania, Serbia, Slovakia, Slovenia, Spain, Sweden, Switzerland, Turkey and the United Kingdom. BS EN 9223102:2018EN 9223-102:2018 (E) 4 Introduction The finality of Configuration Management is to assure during the whole product lifecycle1: consistency and commonality of the t
27、echnical 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
28、 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); t
29、echnical changes and gaps processing in order to keep the consistency of this information (configuration control). 1See EN ISO 9000. BS EN 9223102:2018EN 9223-102:2018 (E) 5 1 Scope The present document: is based on internationally-recognised concepts; proposes organisational principles and implemen
30、tation 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 responsi
31、ble 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, on
32、ly 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 projec
33、t management specifications EN 9223-100, Programme Management Configuration Management Part 100: A guide for the application of the principles of configuration management2EN 9223-105, Programme Management Configuration Management Part 105: Glossary2EN ISO 9000, Quality management systems Fundamental
34、s 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 standar
35、dization 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. 2Published as ASD-S
36、TAN Prestandard at the date of publication of this standard. http:/www.asd-stan.org/ BS EN 9223102:2018EN 9223-102:2018 (E) 6 4 The configuration status accounting process and its place in the overall programme Configuration Management 4.1 Configuration status accounting process overview Figure 1 Pl
37、ace 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, t
38、hen 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 followin
39、g 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 manuf
40、actured 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 pro
41、duct before delivery; BS EN 9223102:2018EN 9223-102:2018 (E) 7 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
42、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 p
43、articular 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 Conf
44、iguration 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)
45、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 t
46、he users; assuring the safekeeping of the configuration information history; BS EN 9223102:2018EN 9223-102:2018 (E) 8 assuring the traceability of decisions. 4.3 Recording initialisation Recording of configuration data presupposes that the following are defined taking into account the provisional es
47、timation 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
48、 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 othe
49、r 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.
