ML23345A135: Difference between revisions
StriderTol (talk | contribs) (StriderTol Bot insert) |
StriderTol (talk | contribs) (StriderTol Bot change) |
||
(One intermediate revision by the same user not shown) | |||
Line 17: | Line 17: | ||
=Text= | =Text= | ||
{{#Wiki_filter:Periodic Review RG 1.168 Revision 2 Regulatory Guide Number: | {{#Wiki_filter:Periodic Review RG 1.168 Revision 2 Regulatory Guide Number: | ||
1.168, Revision 2 | |||
==Title:== | ==Title:== | ||
Verification, Validation, Reviews, and Audits for Digital Computer Software Used in Safety Systems of Nuclear Power Plant Office/Division/Branch: | Verification, Validation, Reviews, and Audits for Digital Computer Software Used in Safety Systems of Nuclear Power Plant Office/Division/Branch: | ||
: 1. | NRR/DEX/EICB Technical Lead: | ||
William Roggenbrodt Staff Action Decided: | |||
Revise | |||
: 1. | |||
What are the known technical or regulatory issues with the current version of the Regulatory Guide (RG)? | |||
The current version of this RG states, Software used in nuclear power plant safety systems should be assigned Integrity Level 4 or the equivalent, as demonstrated by a mapping between the applicant or licensee approach and integrity Level 4 as defined in Institute of Electrical and Electronics Engineers Standard (IEEE Std.) | The current version of this RG states, Software used in nuclear power plant safety systems should be assigned Integrity Level 4 or the equivalent, as demonstrated by a mapping between the applicant or licensee approach and integrity Level 4 as defined in Institute of Electrical and Electronics Engineers Standard (IEEE Std.) | ||
1012-2004. Specifying an integrity Level 4 scheme1 correlates to the maximum number of Verification and Validation (V&V) tasks specified in the standard, which continues to increase with newer versions of the standard. Such an approach does not seem aligned with the objectives realized during the last several years efforts to modernize the digital Instrumentation and Controls (I&C) regulatory infrastructure, which include performing regulatory I&C reviews in an efficient, effective, consistent, and risk-informed manner. Furthermore, such an approach does not seem aligned with the overall intent of the standard, in which the user defines the integrity level and uses a graded approach for the V&V tasks. | 1012-2004. Specifying an integrity Level 4 scheme1 correlates to the maximum number of Verification and Validation (V&V) tasks specified in the standard, which continues to increase with newer versions of the standard. Such an approach does not seem aligned with the objectives realized during the last several years efforts to modernize the digital Instrumentation and Controls (I&C) regulatory infrastructure, which include performing regulatory I&C reviews in an efficient, effective, consistent, and risk-informed manner. Furthermore, such an approach does not seem aligned with the overall intent of the standard, in which the user defines the integrity level and uses a graded approach for the V&V tasks. | ||
The current scope of IEEE Std. 1012-2016 has expanded to include both system and hardware activities, whereas the scope of the IEEE Std. referenced in the current version of RG 1.168 only discusses software V&V activities. The staff would like to consider endorsing IEEE Std. 1012-2016, with potential exceptions and additions, in the revision to RG 1.168. | The current scope of IEEE Std. 1012-2016 has expanded to include both system and hardware activities, whereas the scope of the IEEE Std. referenced in the current version of RG 1.168 only discusses software V&V activities. The staff would like to consider endorsing IEEE Std. 1012-2016, with potential exceptions and additions, in the revision to RG 1.168. | ||
In addition, the significant changes have been made to the approaches and methods to design, develop, and test software since IEEE Std. 1012-2004 was issued, which are reflected in IEEE Std. 1012-2016. | In addition, the significant changes have been made to the approaches and methods to design, develop, and test software since IEEE Std. 1012-2004 was issued, which are reflected in IEEE Std. 1012-2016. | ||
: 2. | : 2. | ||
The approach of specifying an Integrity Level 4 in the current version of the RG could unnecessarily result in potential inefficiencies in the industry use of this standard and | What is the impact on internal and external stakeholders of not updating the RG for the known issues, in terms of anticipated numbers of licensing and inspection activities over the next several years? | ||
The approach of specifying an Integrity Level 4 in the current version of the RG could unnecessarily result in potential inefficiencies in the industry use of this standard and 1The standard defines four integrity levels where 4 is the highest level. The degree of rigor and intensity in performing and documenting any V&V tasks associated with a system, software, or hardware work product is commensurate with the integrity level. | |||
staffs licensing reviews. This is evident when the Nuclear Power Engineering Committee (NPEC) subcommittee for the IEEE 7-4.3.2, IEEE Standard Criteria for Programmable Digital Devices in Safety Systems of Nuclear Power Generating Stations, recently voted to explore the use of International Electrotechnical Commission (IEC) Standards versus the use of IEEE-1012. | staffs licensing reviews. This is evident when the Nuclear Power Engineering Committee (NPEC) subcommittee for the IEEE 7-4.3.2, IEEE Standard Criteria for Programmable Digital Devices in Safety Systems of Nuclear Power Generating Stations, recently voted to explore the use of International Electrotechnical Commission (IEC) Standards versus the use of IEEE-1012. | ||
Additionally, licensees may not be able to take advantage of the latest approaches for efficiencies addressing digital I&C technical issues that have been incorporated into the current version of IEEE Std. 1012-2016. These include: (1) rearranging some V&V activities and tasks to facilitate understanding and ease of use; and (2) emphasizing a series of concepts throughout the standard (e.g., intensity and rigor applied to V&V tasks). | Additionally, licensees may not be able to take advantage of the latest approaches for efficiencies addressing digital I&C technical issues that have been incorporated into the current version of IEEE Std. 1012-2016. These include: (1) rearranging some V&V activities and tasks to facilitate understanding and ease of use; and (2) emphasizing a series of concepts throughout the standard (e.g., intensity and rigor applied to V&V tasks). | ||
: 3. What is an estimate of the level of effort needed to address identified issues in terms of full-time equivalent (FTE) and contractor resources? | : 3. | ||
Approximately .3 FTE. | What is an estimate of the level of effort needed to address identified issues in terms of full-time equivalent (FTE) and contractor resources? | ||
: 4. Based on the answers to the questions above, what is the staff action for this guide? | Approximately.3 FTE. | ||
: 4. | |||
Based on the answers to the questions above, what is the staff action for this guide? | |||
Based on the results of the periodic review, the staff concludes that a revision to RG 1.168, Revision 2 is warranted. | Based on the results of the periodic review, the staff concludes that a revision to RG 1.168, Revision 2 is warranted. | ||
: 5. Provide a conceptual plan and timeframe to address the issues identified during the review. | : 5. | ||
Provide a conceptual plan and timeframe to address the issues identified during the review. | |||
Completion of a draft RG for public comment is expected to take 9-12 months upon starting in fiscal year 2024, based on current resources and other digital I&C priorities. | Completion of a draft RG for public comment is expected to take 9-12 months upon starting in fiscal year 2024, based on current resources and other digital I&C priorities. | ||
NOTE: | NOTE: | ||
This review was conducted in December 2023 and reflects the staffs plans as of that date. These plans are tentative and subject to change.}} |
Latest revision as of 07:32, 25 November 2024
ML23345A135 | |
Person / Time | |
---|---|
Issue date: | 01/02/2024 |
From: | William Roggenbrodt NRC/NRR/DEX/EICB |
To: | |
Shared Package | |
ML23345A132 | List: |
References | |
RG-1.168, Rev 2 | |
Download: ML23345A135 (2) | |
Text
Periodic Review RG 1.168 Revision 2 Regulatory Guide Number:
1.168, Revision 2
Title:
Verification, Validation, Reviews, and Audits for Digital Computer Software Used in Safety Systems of Nuclear Power Plant Office/Division/Branch:
NRR/DEX/EICB Technical Lead:
William Roggenbrodt Staff Action Decided:
Revise
- 1.
What are the known technical or regulatory issues with the current version of the Regulatory Guide (RG)?
The current version of this RG states, Software used in nuclear power plant safety systems should be assigned Integrity Level 4 or the equivalent, as demonstrated by a mapping between the applicant or licensee approach and integrity Level 4 as defined in Institute of Electrical and Electronics Engineers Standard (IEEE Std.)
1012-2004. Specifying an integrity Level 4 scheme1 correlates to the maximum number of Verification and Validation (V&V) tasks specified in the standard, which continues to increase with newer versions of the standard. Such an approach does not seem aligned with the objectives realized during the last several years efforts to modernize the digital Instrumentation and Controls (I&C) regulatory infrastructure, which include performing regulatory I&C reviews in an efficient, effective, consistent, and risk-informed manner. Furthermore, such an approach does not seem aligned with the overall intent of the standard, in which the user defines the integrity level and uses a graded approach for the V&V tasks.
The current scope of IEEE Std. 1012-2016 has expanded to include both system and hardware activities, whereas the scope of the IEEE Std. referenced in the current version of RG 1.168 only discusses software V&V activities. The staff would like to consider endorsing IEEE Std. 1012-2016, with potential exceptions and additions, in the revision to RG 1.168.
In addition, the significant changes have been made to the approaches and methods to design, develop, and test software since IEEE Std. 1012-2004 was issued, which are reflected in IEEE Std. 1012-2016.
- 2.
What is the impact on internal and external stakeholders of not updating the RG for the known issues, in terms of anticipated numbers of licensing and inspection activities over the next several years?
The approach of specifying an Integrity Level 4 in the current version of the RG could unnecessarily result in potential inefficiencies in the industry use of this standard and 1The standard defines four integrity levels where 4 is the highest level. The degree of rigor and intensity in performing and documenting any V&V tasks associated with a system, software, or hardware work product is commensurate with the integrity level.
staffs licensing reviews. This is evident when the Nuclear Power Engineering Committee (NPEC) subcommittee for the IEEE 7-4.3.2, IEEE Standard Criteria for Programmable Digital Devices in Safety Systems of Nuclear Power Generating Stations, recently voted to explore the use of International Electrotechnical Commission (IEC) Standards versus the use of IEEE-1012.
Additionally, licensees may not be able to take advantage of the latest approaches for efficiencies addressing digital I&C technical issues that have been incorporated into the current version of IEEE Std. 1012-2016. These include: (1) rearranging some V&V activities and tasks to facilitate understanding and ease of use; and (2) emphasizing a series of concepts throughout the standard (e.g., intensity and rigor applied to V&V tasks).
- 3.
What is an estimate of the level of effort needed to address identified issues in terms of full-time equivalent (FTE) and contractor resources?
Approximately.3 FTE.
- 4.
Based on the answers to the questions above, what is the staff action for this guide?
Based on the results of the periodic review, the staff concludes that a revision to RG 1.168, Revision 2 is warranted.
- 5.
Provide a conceptual plan and timeframe to address the issues identified during the review.
Completion of a draft RG for public comment is expected to take 9-12 months upon starting in fiscal year 2024, based on current resources and other digital I&C priorities.
NOTE:
This review was conducted in December 2023 and reflects the staffs plans as of that date. These plans are tentative and subject to change.