1、1,Configuration Management,2,Overview of CM,Requirement Schedule for performing these activities CM tools,6,Requirements,d) CM methods and documented procedure(s); e) Organizations and responsibilities assigned to them; f) Level of required control for each configuration item; and g) Points at which

2、 items are brought under configuration management,7,Definition,Configuration: Interrelated functional and physical characteristics of a product as defined in technical documents (product configuration information) Configuration baseline: Configuration of a product, formally established at a specific

3、 point in time, which serves as reference for further activities (established whenever necessary),8,Configuration board (CB): Group of technical and administrative experts with assigned authority and responsibility to make decisions on the configuration and its management, also known as CCB. Configu

4、ration control: Activities comprising the control of changes to a configuration item after formal establishment of its configuration documents,9,Configuration identification(CI): Entity within a configuration that satisfied an end use function Product configuration information: Requirements for prod

5、uct design, realization, verification, operation and support (comprises both product definition & product operational information),10,Configuration status accounting (CSA): Formalized recording and reporting of the established configuration documents, the status of proposed changes and the status of

6、 the implementation of approved changes Configuration item (CI): Aggregation of hardware, software, processed materials, services, or any its discrete portions, that is designed for configuration management and treated as a single entity in the CM process,11,Objectives,To document and provide full v

7、isibility of the products present configuration and on the status of achievement of its physical and functional requirements. Another objective is that everyone working on the project at any time in its life cycle uses correct and accurate documentation,12,CM Process,Configuration identification Cha

8、nge control Configuration status accounting Configuration auditing,13,Organization of CM,CM should be organized with defined responsibilities and sufficient independence and authority to achieve the required CM objectives,14,Configuration board,It has the correct authority in relation to the relevan

9、t configuration baselines,15,CM plans and procedure,CMP: documented, approved, controlled, procedure, defined R & A, conveyed to suppliers Focus on customer requirements for the products, CM process be detailed in a CM plan CM plan may be a stand-alone document, or a part of another document, or com

10、posed of several documents,16,Configuration Identification,A family tree of product structure and selection of configuration items Documentation of configuration items Product configuration information Establishment of configuration baselines,17,Selection of Ci,Regulatory & statutory requirements Ne

11、w or modified technology, design or development Criticality in terms of high risks, safety Interfaces with other configuration items Support and service,18,Selection of Ci,Procurement conditions Logistics and maintenance aspects CIs should be initiated as early as possible in the product life cycle,

12、19,Documentation of Ci,All physical and functional characteristics necessary to define a CI throughout its life cycle should be documented Include specs, design documents, list, software data, manual CI depends on the level of control needs,20,Configuration baselines,Consists of all approved documen

13、ts that present the definition of the product at a specific point Be established whenever it is necessary to define a reference configuration during the product life cycle which serves as a starting point for further activities,21,Change control,Document and justify the changes Evaluate consequences

14、 of the change Approve or disapprove the change Implement and verify the change Process deviations and waivers,22,Change control procedure,All change proposals should be documented: * Config.items & related documents to be changed, name(s) & revision status * Name of the individual preparing the pro

15、posal, the organization and date prepared * Reason & description for the change * Urgency,23,Evaluation of change,The technical merits of the proposed change The impact on interchangeability, interfaces, and the necessity for re-identification The impact on regulatory, risk, contract, schedule, cost

16、, manufacturing, test, inspection method, purchases, stocks, maintenance, user handbooks, spare parts, spare-part manuals, delivery and customer support requirements.,24,Dispositioning Authority,Prior to approval of a change, should verify: The change is necessary The consequences are acceptable The

17、 change has been properly documented and classified The plan for the implementation of the change into documents, HW/SW is satisfactory Also be called a CCB,25,Approval of change,The R&A should be defined The authority for approval/disapproval may vary depending on the significant of the change. A d

18、ecision concerning approval/disapproval should be documented and notified the relevant areas.,26,The implementation and verification of an approved change normally includes following steps: Changes to the CI should be formally approved Appropriate consequential actions by the affected departments sh

19、ould be initiated Compliance should be verified,27,Configuration status accounting,CSA should perform throughout the life cycle of the product CSA should provide information of all CIs and all departures from the specified configuration baselines, it thus enables changes to configuration baselines t

20、o be traceable CSA records and reports should be a by-product of the identification and control activities,28,CSA Records,When: During configuration identification and change control What: Products configuration information (ID, title, effective date, version, change history, part number or build st

21、atus) Status of release of new product Products configuration (P/N, product design or build status) The processing of change,29,CSA Records,How: 8 steps Provide protection from corruptions or unauthorized change Provide means for disaster recovery Permit retrieval .,30,Reporting,A list of configurat

22、ion baselines documents A list of Configuration items and their configuration baselines Current configuration status Status reports on changes, deviations, waivers Status reports on the implementation and verification of changes,31,Configuration audit(CA),CA should be performed in accordance with do

23、cumented procedure to assure the product complies with its contracted or specified requirements and to assure the product is accurately reflected by its configuration documents,32,Configuration audit(CA),Functional CA: a formal examination to verify that a configuration item has achieved the perform

24、ance and functional characteristics specified in its configuration documents Physical CA: a formal examination if the “as-built/produced” configuration of a CI to verify that it conforms to its product configuration documents,33,Configuration audit(CA),CA may be required before the formal acceptance of a configuration item Not intended to replace other forms of verification, review, test o