1、 ASD-STAN STANDARD NORME ASD-STAN ASD-STAN NORM ASD-STAN prEN 9223-105: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 105: Glossary Programm-Management Konfigurationsmanagement Teil 105: Glossar Management de Programme Gestion de la Configuration Partie 105 : Glossaire This “Aerospace Series“ Prestandard has been drawn up under the responsibility of
3、 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 following member comments. Subsequent to the publication of this Prestan
4、dard, 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 ASD-STAN, the ASD-STAN prEN will be submitted as a draft European St
5、andard (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 a national standard and by withdrawing any national standards confl
6、icting 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 suitability for any particular use, including any patent infringement ar
7、ising 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 send your written comments or any suggestions that may arise. All righ
8、ts 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 ASD-STAN. Order details: E-mail: salesasd-stan.org Web address: ht
9、tp:/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-105:2016 (E) 2 Contents Page Foreword 3 1 Scope . 4 2 Terms and definitions. 4 Bibliography . 14 prEN 9223-105:2016 (E) 3 Foreword This
10、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 has received approval for Publication. prEN 9223-105:2016 (E) 4 1 Scope Thi
11、s document explains the wording in use within the following standards: EN 9223-100, Programme Management Configuration Management Part 100: A guide for the application of the principles of configuration management EN 9223-101, Programme Management Configuration Management Part 101: Configuration ide
12、ntification EN 9223-102, Programme Management Configuration Management Part 102: Configuration status accounting EN 9223-103, Programme Management Configuration Management Part 103: Configuration Verifications, Reviews and Audits EN 9223-104, Programme Management Configuration Management Part 104: C
13、onfiguration Control Help for definitions reading Notes are integral parts of the initial definition whereas comments provide additional information to this definition and are specific to this documents set. 2 Terms and definitions For the purposes of this document, the following terms and definitio
14、ns apply. 2.1 corrective action action to eliminate the cause of a detected nonconformity or other undesirable situation Note 1 to entry: There can be more than one cause for a nonconformity. Note 2 to entry: Corrective action is taken to prevent recurrence whereas preventive action is taken to prev
15、ent occurrence. Note 3 to entry: There is a distinction between, curative action, correction and corrective action. SOURCE: EN ISO 9000 2.2 curative action action to restore the conformity of a product initially nonconforming see paragraph “rework” 2.3 preventive action action to eliminate the cause
16、 of a potential nonconformity or other undesirable potential situation Note 1 to entry: There can be more than one cause for a potential nonconformity. Note 2 to entry: Preventive action is taken to prevent occurrence whereas corrective action is taken to prevent recurrence. SOURCE: EN ISO 9000 prEN
17、 9223-105:2016 (E) 5 2.4 anomaly gap between a current situation and an expected one Note 1 to entry: An anomaly justifies an investigation which might lead to the discovery of a nonconformity or a defect. SOURCE: EN 9200 2.5 item the item includes the notions of component, compound, part, ingredien
18、t, assembly, functional element, product and system, bought or manufactured by a manufacturer It concerns hardware, software, or a combination of them. Elements of support system are also concerned (test bench, tooling, user documentation, packaging, etc.). Items can be selected as configuration ite
19、m, or not; they are documented. 2.6 configuration item entity within a configuration that satisfies an end use function Note 1 to entry: It is a set (hardware, software, documents or their combination) that has been selected for configuration management and is managed as a single entity in the confi
20、guration management process. A configuration item can be, on its own, specified, identified, built, checked and maintained. SOURCE: adapted from ISO 10007:2003 2.7 attribute specific characteristic of a data or information that can be used as a selection or ordering criteria 2.8 audit systematic, in
21、dependent and documented process for obtaining audit evidence and evaluating it objectively to determine the extent to which the audit criteria are fulfilled Note 1 to entry: Although this definition derived from EN ISO 19011, and can be used to define configuration audit, configuration audits shall
22、 not be based on the EN ISO 19011 standard, which mainly addresses process audits. SOURCE: EN ISO 19011 prEN 9223-105:2016 (E) 6 2.9 configuration audit a configuration management process that step-by-step examines products in order to check: they comply with requirements; they achieve the performan
23、ces and the physical and/or functional characteristics, as required in the previous formalized Baseline configuration(s); they comply with product design information. Configuration audits can be clearly split into functional and physical configuration audits. Note 1 to entry: Each configuration item
24、 shall be subject to configuration audits. Note 2 to entry: Configuration audit process applied to a configuration item only takes place at specific moments of its lifecycle. Note 3 to entry: These audits must end up with the formal establishment of the Baseline configuration from the candidate Base
25、line configuration. Functional Configuration Audit (FCA): this is a formal examination to verify that a configuration item has achieved the functional and performance characteristics specified in its product configuration information (ISO 10007:2003). Physical Configuration Audit (PCA): this is a fo
26、rmal examination to verify that a configuration item has achieved the physical characteristics specified in its product configuration information (ISO 10007:2003). 3.0 dispositioning authority person or a group of persons assigned responsibility and authority to make decisions on the configuration N
27、ote 1 to entry: Dispositioning authority can also be called a “configuration control board”. Note 2 to entry: Relevant interested parties within and outside the organization should be represented on the dispositioning authority. Note 3 to entry: This authority is not restricted to change board. SOUR
28、CE: adapted from ISO 10007:2003 3.1 configuration interrelated functional and physical characteristics of a product defined in product configuration information Note 1 to entry: Set of functional and physical characteristics of a product (hardware and software), as defined in the documentation and o
29、btained in the physical product. SOURCE: ISO 10007:2003 3.2 updated approved configuration configuration that takes into account the Baseline configuration and all decided engineering changes prEN 9223-105:2016 (E) 7 3.3 applicable configuration (for production) configuration of a product as expecte
30、d to be produced. It is established for a unit or batch (for instance, decision to start production) Note 1 to entry: At a specific time, several applicable configurations can exist for different physical units of a same product. Note 2 to entry: Deviations are also included in the applicable config
31、uration. Note 3 to entry: This configuration can be recorded for a unit: of production; of qualification; of retrofit; to perform specific tests. 3.4 as-built configuration configuration of a product item established from the applicable configuration and to which conformity gaps and complementary co
32、nfiguration technical information is added Note 1 to entry: Gaps shall be submitted to approval (concession). Note 2 to entry: There is (almost) as many as-built configurations as product physical units. Note 3 to entry: Complementary configuration technical information can include batch/lot or seri
33、al number etc. 3.5 configuration Baseline approved product configuration information that establishes the characteristics of a product at a point in time that serves as reference for activities throughout the lifecycle of the product Note 1 to entry: Throughout the product lifecycle, a configuration
34、 Baseline is established to agree on a basis from which other configuration Baselines can be identified (described), as necessary. Note 2 to entry: Three main configuration Baselines can be distinguished: the Functional configuration Baseline (FBL); the Development or Allocated configuration Baselin
35、e (ABL); the Production configuration Baseline (PBL); These configuration Baselines consist only of documents. Note 3 to entry: Configuration Baselines other than the three above mentioned may also include products or sub-products in a given state of progress. Ex.: configuration of a qualification u
36、nit. SOURCE: ISO 10007:2003 prEN 9223-105:2016 (E) 8 3.6 in-use (as maintained) configuration configuration of a product item based on the as-built configuration, to which the consequences of the in-service events on the configuration information are included (maintenance, damage, repair, potential
37、consumption, etc.) 3.7 concession (deviation, waiver) permission to use or released a product that does not conform to specified requirements Note 1 to entry: A concession is generally limited to the delivery of the product that has nonconforming characteristics within specified limits for an agreed
38、 time or quantity of that product. Note 2 to entry: Concession is an ambiguous term since it covers concessions before production and after production or in-service. Note 3 to entry: In EN 9223-100 and EN 9223-101 to EN 9223-105: “deviation” is synonymous with “concession before production” (see EN
39、ISO 9000); “waiver” is synonymous with “concession after production” or “in-service concession”. Each time necessary, it should be mentioned: “Waiver after production”: if the nonconformity is detected during the production or before delivery; “In-service waiver” (in-use): if the nonconformity is de
40、tected in-service (in-use). SOURCE: adapted from ISO 10007:2003 3.8 deviation permit synonymous in the present document to “concession before production” in the sense of EN ISO 9000 Permission to depart from the originally specified requirements of a product prior to its realization. Note 1 to entry
41、: A deviation permit is generally given for a limited quantity of a product, period of time, and for a specific use. Note 2 to entry: Some companies do not use the wording “deviation” but prefer the wording “concession before production”. Deviations can be: improvements (application of a necessary c
42、hange, before approval); temporary gaps for a given use or mission; consecutive or supporting gaps for a concession or a retrofit. prEN 9223-105:2016 (E) 9 3.9 document information and its supporting medium Note 1 to entry: The medium can be paper, magnetic, electronic or optical computer disc, phot
43、ograph or master sample, or a combination thereof. SOURCE: adapted from EN ISO 9000 4.0 configuration data a product is characterized and/or defined by technical data “Configuration data” are data selected to be exchanged between the stakeholders. Note 1 to entry: Technical data are: requirements, i
44、nterfaces, models, drawings, bill of materials, references, acceptance specifications, batch/lot/serial numbers, residual potential or potential consumption, in-service life data, etc. 4.1 configuration status accounting configuration management activities concern configuration information, associat
45、ed to configuration Baselines and status, in preparation for their: data capture; safekeeping; availability to authorized persons; hand-over, according to agreed formats. 4.2 configuration report extract (report, listing etc.) of the configuration status accounting process, especially for: the updat
46、ed approved configuration (includes Baseline configuration and any decided technical changes); the applicable configuration (see definition above); the “as built” configuration (see definition above); the “in use” configuration (see definition above). Note 1 to entry: Each configuration item specime
47、n can have the configuration reports mentioned above. Note 2 to entry: Each configuration item specimen can have different configuration reports from neighbour specimen ones. 4.3 technical event any significant technical event, predicted or not, arising during the lifecycle of a product SOURCE: EN 9
48、200 prEN 9223-105:2016 (E) 10 4.4 configuration management coordinated activities to direct and control configuration of a configuration item Note 1 to entry: Configuration management generally concentrates on technical and organizational activities that establish and maintain control of a product a
49、nd its product configuration information throughout the life cycle of the product. Note 2 to entry: For a given authority, configuration management applies, and only applies, to items and characteristics selected to have their configuration Baseline managed. Configuration management consists in the following activities: identify (select) the configuration to be managed; control voluntary and involuntary changes brought over to this configuration; to capture and record ea
