BS EN 9223‑104:2018 pdf download.Programme Management – Configuration Management Part 104: Configuration Control.
4.2 The Configuration Control process nature The configuration management process is composed of a set of actions and decisions (product and responsibilities‑trees), set up in order to keep and improve consistent relationships between the configurations and the products trees: — maintainingidentification(updatesoffunctional,allocatedandproductconfigurationbaselines,etc.); — maintaining qualifications (verification of non‑regression); — maintaining links between the different configurations of a same item such as, links between index of definition file and index of the technical requirement specification. Configuration control is mainly a decisional process (preparing decision and decision making, and control of decisions implementation) meant to guarantee the overtime consistency for configuration items and associated data. As such, for a given authority, configuration control exclusively concerns items and data selected during the configuration identification process. This set of items and data establishes the authority’s field of competence. The process is implemented as soon as the first configuration baseline is established. It addresses any effects on the configuration of (see Figure 3): — needs for technical changes (including those following the detection of defects); — technical events and anomalies.
4.3 Tasks associated with configuration control 4.3.1 Identifying process The following tasks apply to all items, whether selected or not as configuration items, even though these tasks cannot be considered as Configuration Management activities. Nonetheless, an efficient configuration control process cannot be carried out without their rigorous implementation. The Configuration Management plan shall specify details of implementation. 4.3.2 Document management tasks The setting up of a system of identifiers permit to identify changes within a document, although it does not belong to configuration management activities (indeed, an item or a document shall have an identifier, whether it is considered as a configuration item or not). 4.3.3 Product marking Products or batches/lots marking shall permit to link these items to any control decision. Thus: — this marking, thanks to the documentation of associated configuration status, can lead to know all the control decisions (change index, deviation or concession marking); — serialisationmarkingalsoguaranteesthetraceabilitynecessarytomaintenance(interchangeability); — marking ensuring interchangeability must be implemented on the specimen or on its associated accompanying documents. Marking rules could be clarified in the configuration management plan.
5 Configuration control principles 5.1 General For a specific authority, configuration control over an item encompasses the configuration documentation and associated data, “identified” as a whole. In order to define its scope of intervention, each authority 2) assumes the decision to recognise configuration items and data for which it has been delegated configuration management authority. 5.2 Allocation of an item to an authority The allocation of an item to an authority, and reciprocally, is deduced from an analysis based on the configuration data and items, as potentially impacted by a control decision. This allocation rule shall be clarified in the configuration management plan. 5.3 Technical changes, deviations permits and concessions shared provisions In the following clauses, provisions common to technical changes, deviation permits and concessions and provisions specific to each category will be distinguished. Each technical change, deviation permit and concession experiences its own life cycle and is subject to a decision‑making process.BS EN 9223‑104 pdf download.