1、BSI Standards PublicationWB11885_BSI_StandardCovs_2013_AW.indd 1 15/05/2013 15:06Programme Management - Configuration ManagementPart 101: Configuration identificationBS EN 9223101:2018National forewordThis British Standard is the UK implementation of EN 9223101:2018.The UK participation in its prepa
2、ration 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 provisions of a contract. User
3、s are responsible for its correct application. The British Standards Institution 2018 Published by BSI Standards Limited 2018ISBN 978 0 580 90024 2ICS 35.080; 49.020Compliance with a British Standard cannot confer immunity from legal obligations. This British Standard was published under the authori
4、ty of the Standards Policy and Strategy Committee on 31 March 2018.Amendments/corrigenda issued since publicationDate Text affectedBRITISH STANDARDBS EN 9223101:2018EUROPEAN STANDARDNORME EUROPENNEEUROPISCHE NORMEN 9223101March 2018ICS 35.080; 49.020EUROPEAN COMMITTEE FOR STANDARDIZATIONCOMIT EUROPE
5、N DE NORMALISATIONEUROPISCHES KOMITEE FR NORMUNGCENCENELEC Management Centre: Avenue Marnix 17, B1000 Brussels 2018 CEN Ref. No. EN 9223101:2018: EAll rights of exploitation in any form and by any means reserved worldwide for CEN national MembersProgramme Management Configuration Management Part 101
6、: Configuration identificationManagement de Programme Gestion de la Configuration - Partie 101 : Identification de la configurationProgrammManagement Konfigurationsmanagement - Teil 101: KonfigurationsidentifizierungThis European Standard was approved by CEN on 1 October 2017.CEN members are bound t
7、o 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. Uptodate lists and bibliographical references concerning such national standards may be obtained on application to the CENCENE
8、LEC 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
9、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, Luxembour
10、g, Malta, Netherlands, Norway, Poland, Portugal, Romania, Serbia, Slovakia, Slovenia, Spain, Sweden, Switzerland, Turkey and United Kingdom.English VersionEN 9223101:2018 (E)European forewordThis document (EN 9223101:2018) has been prepared by the Aerospace and Defence Industries Association of Euro
11、pe Standardization (ASDSTAN).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 countries of ASD, prior to its presentation to CEN.This European Standard
12、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.Attention is drawn to the possibility that some of the elements of th
13、is 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 CENCENELEC Internal Regulations, the national standards organisations of the following countries are bound to implement this European Standard: Austria, B
14、elgium, 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, Swe
15、den, Switzerland, Turkey and the United Kingdom.2BS EN 9223101:2018EN 9223101:2018 (E)IntroductionThe finality of Configuration Management is to assure during the whole product lifecycle1): consistency and commonality of the technical information among all actors; traceability of this technical info
16、rmation.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); capture, keeping this infor
17、mation 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 keep the consistency of th
18、is information (configuration control).1) See EN ISO 9000:2005.3BS EN 9223101:2018EN 9223101:2018 (E)European foreword 2Introduction . 3European foreword 5Introduction . 61 Scope . 72 Normative references 73 Terms and definitions . 74 The configuration identification and its place in the overall pro
19、gramme Configuration Management . 84.1 Nature of the configuration identification process 84.2 Identification: starting point for other Configuration Management processes 84.3 Tasks associated with identification 94.3.1 Documentation Management Tasks 94.3.2 Configuration Management tasks prior to id
20、entification . 94.3.3 Identifier of items, identification documentation and specimens .105 Configuration identification principles .105.1 General 105.2 Attribution of a configuration item to an authority .105.3 Configuration items selection . 115.3.1 Principles of selecting configuration items 115.3
21、.2 Progressiveness of the configuration items selection 115.3.3 Selection criteria of configuration items 115.4 Data selection 115.4.1 Data selection principles 115.4.2 Progressiveness in selecting configuration data .125.4.3 Criteria for selection configuration data 125.5 Configuration baselines 12
22、5.5.1 General. 125.5.2 Functional configuration baseline . 135.5.3 Allocated configuration baseline 135.5.4 Product configuration baseline 145.5.5 Configuration status of particular specimens or items .155.6 Evolution of identification throughout a programme lifecycle 165.6.1 Change of scope of Conf
23、iguration Management authority .165.6.2 Addition and removal of configuration items 165.6.3 Change in the identification documentation content 165.7 Configuration identification activities throughout a programme lifecycle 175.7.1 At the beginning of a programme .175.7.2 During the preliminary design
24、 phase .175.7.3 During the detailed design phase .185.7.4 During the mass production phase . 185.7.5 During the in-use phase 195.7.6 During the dismantling phase . 196 Specific cases .206.1 Component off the shelf (COTS) 206.2 Configuration items shared by several programmes 206.3 Programmes with sh
25、ared responsibilities . 21Annex A (informative) Document management prerequisite necessary for Configuration Management .22Bibliography .234Contents PageBS EN 9223101:2018EN 9223101:2018 (E)European forewordThis document (EN 9223101:2018) has been prepared by the Aerospace and Defence Industries Ass
26、ociation of Europe Standardization (ASDSTAN).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 countries of ASD, prior to its presentation to CEN.This Eu
27、ropean 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.Attention is drawn to the possibility that some of th
28、e 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 CENCENELEC Internal Regulations, the national standards organisations of the following countries are bound to implement this European Stan
29、dard: 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, Slov
30、enia, Spain, Sweden, Switzerland, Turkey and the United Kingdom.5BS EN 9223101:2018EN 9223101:2018 (E)IntroductionThe finality of Configuration Management is to assure during the whole product lifecycle1): consistency and commonality of the technical information among all actors; traceability of thi
31、s 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); capture, ke
32、eping 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 keep the c
33、onsistency of this information (configuration control).1) See EN ISO 9000:2005.6BS EN 9223101:2018EN 9223101:2018 (E)1 ScopeThe present document is declined from the principles described in the EN 9223100, it: is based on internationallyrecognised concepts; proposes organisational principles and imp
34、lementation 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 metho
35、ds of application and tailoring as necessary.2 Normative referencesThe 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, only the edition cited applies. For undated references, the latest e
36、dition of the referenced document (including any amendments) applies.EN 9100, Quality Management Systems Requirements for Aviation, Space and Defense organizationsEN 92231001), Programme Management Configuration Management Part 100: A guide for the application of the principles of configuration mana
37、gementEN 92231052, Programme Management Configuration Management Part 105: GlossaryEN ISO 9000, Quality management systems Fundamentals and vocabularyISO 10007:2003, Quality management systems Guidelines for configuration managementISO/IEC 65231, Information technology Structure for the identificati
38、on of organizations and organization parts Part 1: Identification of organization identification schemesISO/IEC 65232, Information technology Structure for the identification of organizations and organization parts Part 2: Registration of organization identification schemesNF L 09001A, Identificatio
39、n of aerospace components Part numbers writing3 Terms and definitionsFor the purposes of this document, the terms and definitions given in EN ISO 9000, ISO 10007:2003 and EN 9200 apply.ISO and IEC maintain terminological databases for use in standardization at the following addresses: IEC Electroped
40、ia: available at http:/www.electropedia.org/ ISO Online browsing platform: available at http:/www.iso.org/obpThe specific terms needed to understand and to use the document are the object of definitions appearing in EN 9223105.1) Published as ASDSTAN Prestandard at the date of publication of this st
41、andard. http:/www.asdstan.org/7BS EN 9223101:2018EN 9223101:2018 (E)4 The configuration identification and its place in the overall programme Configuration Management4.1 Nature of the configuration identification processThis process is mainly a decisional process (preparing decision and decide) dedi
42、cated 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, co
43、nfiguration 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 decisionmaking delegations throughout a network of customers, par
44、tners, 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 plan
45、.4.2 Identification: starting point for other Configuration Management processesThe 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 is th
46、us “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 selection
47、s; 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 decisionmaking (responsibility) breakdown an
48、d products breakdowns.8 BS EN 9223101:2018EN 9223101:2018 (E)Figure 1 Place of the configuration identification process in Configuration Management processesIn the above figure: if the prior configuration baseline is the functional configuration baseline (FBL), the new configuration baseline is allo
49、cated 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 identification4.3.1 Documentation Management TasksDocumentation management tasks are not 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 unique
