Document: NRC Regulatory Guide
Document ID: 3eb179d3-5491-407d-8b0e-eed083d58a17
Document Type: regulatory_guide
Title: Configuration Management Plans for Digital Computer Software Used in Safety Systems of Nuclear Power Plants + HISTORY - HISTORY 08/2012 – DG-1206 , Proposed Revision 1 08/1996 – DG-1055 , Proposed Revision 0 (Rev. 1)
Source: NRC Regulatory Guide Division 1
Source URL: https://www.nrc.gov/docs/ML1032/ML103200044.pdf
Revision Date: 2023-06
Chapter: 
Section ID: RG-1.169
CFR Part: 
CFR Title: 

Content:
is commensurate with the life-cycle stage (nearness to release) and the product’s importance to safety. The promotion of a software product from one level of safety significance to another level of safety significance could involve a change in level of control (as described in Clause 3.3.2.3 of IEEE Std. 828-2005) and a change in responsible individual. 3. Acceptance Criteria The SCM plan should describe the criteria for selecting control points, as defined in Clause 2.1.1 of IEEE Std. 828-2005, and establish the correspondence between control points identified in the plan and baselines, project milestones, and life-cycle milestones. 4. Configuration Management The minimal set of safety system software activities to be covered by the SCM plan should accomplish the following: a. identification and control of all software designs and code; b. identification and control of all software design interfaces; c. control of all software design changes; d. control of software documentation (user, operating, and maintenance documentation); e. control of software vendors supplying safety system software; f. control and retrieval of qualification information associated with software designs and code; g. software configuration audits; h. status accounting; and i. control of building, release, and delivery of products. Other quality assurance activities may serve or control some of these functions; in that case, the SCM plan should describe the division of responsibility. An SCM program that complies with IEEE Std. 828-2005 should take control of contractually developed or qualified commercial software products that are safety system software. This means, for example, that the exact version of the product should be identified and controlled according to the change control procedures applied to other configuration items, and the SCM system should track and report its usage. 5. Corrective Action Criterion XVI requires, in part, that conditions adverse to quality, such as