ML24289A228: Difference between revisions

From kanterella
Jump to navigation Jump to search
(StriderTol Bot insert)
 
(StriderTol Bot change)
 
Line 15: Line 15:


=Text=
=Text=
{{#Wiki_filter:Proposed Path Forward for Industry s Use of Institute of Electrical and Electronics Engineers Standard (IEEE) 603-2018, Criteria for Safety Systems
{{#Wiki_filter:Proposed Path Forward for Industrys Use of Institute of Electrical and Electronics Engineers Standard (IEEE) 603-2018, Criteria for Safety Systems 10 CFR 50.55a(h), IEEE Std. 603


10 CFR 50.55a(h), IEEE Std. 603 Outline
Outline
* Meeting Purpose
* Meeting Purpose
* Background
* Background
Line 27: Line 27:
* Staff Approach and Considerations
* Staff Approach and Considerations
* Rulemaking Process and Milestones
* Rulemaking Process and Milestones
* Questions
* Questions 2
 
2 Meeting Purpose
 
To present the staff s progress on the path forward to address the use of the 2018 version of IEEE 603, IEEE Standard Criteria for Safety Systems for Nuclear Power Generating Stations, in the development of safety -
related instrumentation and control (I&C) systems.
* Obtain stakeholder feedback on the staff s proposed path forward.
* Help inform the staff s proposed rulemaking for IEEE 603 -2018.


Meeting Purpose To present the staffs progress on the path forward to address the use of the 2018 version of IEEE 603, IEEE Standard Criteria for Safety Systems for Nuclear Power Generating Stations, in the development of safety-related instrumentation and control (I&C) systems.
* Obtain stakeholder feedback on the staffs proposed path forward.
* Help inform the staffs proposed rulemaking for IEEE 603-2018.
3
3


===Background===
===
Background===
* Regulations for the design of protection and safety systems for nuclear power plants.
* Regulations for the design of protection and safety systems for nuclear power plants.
- Title 10 of the Code of Federal Regulations (10 CFR), Section 50.55a(h), Protection and safety systems, provides requirements for the design of protection and safety systems for nuclear power reactors.
- Title 10 of the Code of Federal Regulations (10 CFR), Section 50.55a(h), Protection and safety systems, provides requirements for the design of protection and safety systems for nuclear power reactors.
- IEEE 279-1968, 279-1971, and 603-1991 are incorporated by reference (IBR) into 10 CFR 50.55a(h).
- IEEE 279-1968, 279-1971, and 603-1991 are incorporated by reference (IBR) into 10 CFR 50.55a(h).
* On September 14, 2023, NRC staff engaged with external stakeholders, receiving input on its plans for the development on a path forward for the use of IEEE 603-2018 (ML23242A169).
* On September 14, 2023, NRC staff engaged with external stakeholders, receiving input on its plans for the development on a path forward for the use of IEEE 603-2018 (ML23242A169).
* NEI provided their recommendation November 3, 2023, for IBR of IEEE 603-2018 with exception to Clause 5.16 Common Cause Failure (ML23307A127).
* NEI provided their recommendation November 3, 2023, for IBR of IEEE 603-2018 with exception to Clause 5.16 Common Cause Failure (ML23307A127).
4


4 Objectives and Options
Objectives and Options
* Objectives
* Objectives
: 1. Provide industry with the regulatory confidence to use the 2018 version in the development of safety-related I&C systems.
: 1. Provide industry with the regulatory confidence to use the 2018 version in the development of safety-related I&C systems.
: 2. Establish a streamlined path to endorse new and improved standards that are developed to address digital technology advancements.
: 2. Establish a streamlined path to endorse new and improved standards that are developed to address digital technology advancements.
* Options A. Revise a Regulatory Guide (e.g. RG 1.153).
* Options A. Revise a Regulatory Guide (e.g. RG 1.153).
B. Initiate rulemaking to incorporate by reference IEEE 603 -2018.
B. Initiate rulemaking to incorporate by reference IEEE 603-2018.
C. Issue generic communication to summarize licensing pathways to using newer versions of the standard.
C. Issue generic communication to summarize licensing pathways to using newer versions of the standard.
* Staff evaluated the options on the basis of how well the options meet the two objectives to determine the path forward.
* Staff evaluated the options on the basis of how well the options meet the two objectives to determine the path forward.
5


5 Option A - Regulatory Guide
Option A - Regulatory Guide Revise a Regulatory Guide (e.g., RG 1.153)
 
Revise a Regulatory Guide (e. g., RG 1.153)
Objective 1 is partially met Does not provide licensees and applicants the equivalent regulatory confidence as updating the regulations.
Objective 1 is partially met Does not provide licensees and applicants the equivalent regulatory confidence as updating the regulations.
Objective 2 is met Utilizes existing regulatory guide process to endorse a standard.
Objective 2 is met Utilizes existing regulatory guide process to endorse a standard.
6


6 Option B - Rulemaking
Initiate rulemaking to incorporate by reference IEEE Std 603-2018 Objective 1 is met Provides licensees and applicants regulatory confidence to use IEEE Std. 603-2018.
 
Initiate rulemaking to incorporate by reference IEEE Std 603-2018 Objective 1 is met P rovides licensees and applicants regulatory confidence to use IEEE Std. 603 -2018.
 
Objective 2 is met Provides the opportunity to generate a blueprint for IEEE-603 to streamline future rulemaking efforts.
Objective 2 is met Provides the opportunity to generate a blueprint for IEEE-603 to streamline future rulemaking efforts.
Option B - Rulemaking 7


7 Option C - Generic Communication
Option C - Generic Communication Issue generic communication to summarize licensing pathways to using newer versions of the standard Objective 1 is partially met Does not provide licensees and applicants the equivalent regulatory confidence as updating the regulations.
 
Issue generic communication to summarize licensing pathways to using newer versions of the standard Objective 1 is partially met Does not provide licensees and applicants the equivalent regulatory confidence as updating the regulations.
 
Objective 2 is not met Utilizes existing generic communication process.
Objective 2 is not met Utilizes existing generic communication process.
8


8 Other Option - Removal of IEEE Stds. from 50.55a
Removal of the IEEE reference may necessitate alternative requirements either through IBR of a different industry standard (e.g., International Standards) or development and inclusion of newly developed requirements within 10 CFR Part 50.55a.
 
Other Option - Removal of IEEE Stds. from 50.55a 9
Removal of the IEEE reference may necessitate alternative requirements either through IBR of a different industry standard (e. g., International Standards) or development and inclusion of newly developed requirements within 10 CFR Part 50.55a.


9 Selected Option for Path Forward
Selected Option for Path Forward
* Along with factoring stakeholder input and feedback, NRC staff evaluated and determined to proceed with Option B, Rulemaking.
* Along with factoring stakeholder input and feedback, NRC staff evaluated and determined to proceed with Option B, Rulemaking.
* Develop staff position and blueprint to pursue rulemaking to incorporate by reference of IEEE 603-2018.
* Develop staff position and blueprint to pursue rulemaking to incorporate by reference of IEEE 603-2018.
10


10 Combining IEEE and ASME Rulemakings
Combining IEEE and ASME Rulemakings
* NRC staff considered combining IEEE and ASME Rulemakings
* NRC staff considered combining IEEE and ASME Rulemakings
* Results Summary
* Results Summary
- Complications from the misalignment in frequency of updates (ASME 2/6 yrs.
- Complications from the misalignment in frequency of updates (ASME 2/6 yrs.
vs IEEE 10 yrs.).
vs IEEE 10 yrs.).
- Increase in scope of the combined rulemaking could negatively impact both rules (i.e. schedule, complexity).
- Increase in scope of the combined rulemaking could negatively impact both rules (i.e. schedule, complexity).
* NRC staff decided not to pursue combined rulemaking
* NRC staff decided not to pursue combined rulemaking
- OMB accepts one rulemaking per CFR at a time.
- OMB accepts one rulemaking per CFR at a time.
- Coordinate with ASME Code rulemaking to ensure schedules do not conflict.
- Coordinate with ASME Code rulemaking to ensure schedules do not conflict.
11


11 Comparison Between IEEE 603 -1991 and IEEE 603 -2018 Clauses and subclauses were divided into items (151) to facilitate the comparison.
Comparison Between IEEE 603-1991 and IEEE 603-2018 Clauses and subclauses were divided into items (151) to facilitate the comparison.
Identical - No changes in wording between the two standards; Equivalent - Formatting changes, updated standard revisions, updated wording, restructured numbering or similar; Enhancement - Improvements, clarifications, additional text modifying items on existing topics; and New - Added items (clauses, subclauses, or text) addressing new topics.
Identical - No changes in wording between the two standards; Equivalent - Formatting changes, updated standard revisions, updated wording, restructured numbering or similar; Enhancement - Improvements, clarifications, additional text modifying items on existing topics; and New - Added items (clauses, subclauses, or text) addressing new topics.
12


12 Comparison Between IEEE 603-1991 and IEEE-2018 (Cont.)
Comparison Between IEEE 603-1991 and IEEE-2018 (Cont.)
* The staff completed a comparative analysis of IEEE 603-1991 and IEEE 603-2018.
* The staff completed a comparative analysis of IEEE 603-1991 and IEEE 603-2018.
* The staff concluded the following:
* The staff concluded the following:
- the update to the standard is generally routine in nature, with predominantly identical, equivalent, or enhanced language
- the update to the standard is generally routine in nature, with predominantly identical, equivalent, or enhanced language
- for the four new items related to CCF, further evaluation necessary to ensure consistency with Commission Policy
- for the four new items related to CCF, further evaluation necessary to ensure consistency with Commission Policy 13


13 Clause 5.16 - Common Cause Failure
Clause 5.16 - Common Cause Failure The safety system design and development shall address common-cause failures (CCF) that create a potential to degrade or defeat the safety system function. Methods for addressing CCF should include determining the following:
a) The CCF has sufficiently low likelihood of occurring.
Acceptable ways of reducing the likelihood of occurrence of some sources of CCF include the requirements imposed by this standard. Quality assurance programs (5.3), equipment qualification (5.4), and design attributes (e.g., 5.5 and 5.6) afford protection from design and manufacturing defects, external environmental effects, and internal failures. Human factors considerations (5.14) afford protection from operator errors.
Additionally, personnel training and plant procedures (i.e., operating, maintenance, and surveillance) afford protection from human errors. Other factors that may be considered are testability, applicable operating experience, and diversity within the safety system design.
b) The safety consequence that would result from the occurrence of the CCF in conjunction with any design basis event is low, such that public health and safety are maintained.
An acceptable way of determining the consequence of a CCF of the safety system is to perform a plant-level analysis of the loss or degradation of safety functions concurrent with applicable design basis events.
A safety system design that contains a source of CCF may be justified if the resulting consequence of the CCF is low, even when it cannot be demonstrated that the likelihood of occurrence of the CCF is sufficiently low. If the resulting consequence of the CCF is severe, a determination that the CCF has a very low likelihood of occurrence could be credited toward justification of the safety system design. Each identified source of CCF should be evaluated on a case-by-case basis.
Item 1 Item 2 Item 3 Item 4


Item 1 The s afety system design and development shall address common-cause failures (CCF) that create a potential to degrade or defeat the s afety system function. Methods fo r addressing CCF should include determining the following :
a) The CCF has sufficiently low likelihood of occurring.
Acceptable ways of reducing the likelihood of occurrence of some s ources of CCF include the requirements imposed by this stan d ard. Quality assurance p ro gra ms (5. 3), equipment qualification (5. 4), and design attributes Item 2 (e. g., 5. 5 and 5. 6) a f fo rd protecti on from design and manufacturing defects, ex te rn al environ mental effects, and internal failures. Human factors considerations (5. 14) a f fo rd protection from o p e rat or e r ro rs.
Additionally, personnel training and plant procedures (i.e., operating, maintenance, and surveillance) a f fo rd protecti on from human er rors. Other factors that m ay be considered are testabi li t y, applicable operating experience, and diversity within the safety system design.
b) The safety consequence that would result from the occurrence of the CCF in conjunction with a ny design basis Item 3 event is l o w, such that public health and safety are maintained.
An acceptable way of determining the consequence of a CCF of the s a fe t y system is to perform a pl ant-level analysis of the loss or degradation of safety functions con cu r rent with applicable design basis events.
A s a fe t y system design that contains a s ource of CCF may be justified if the resulting consequence of the CCF is l o w, Item 4 even when it cannot be d emonstrated that the likelihood of occurrence of the CCF is sufficiently l ow. If the resulting consequence of the CCF is severe, a determination that the CCF has a ver y l ow likelihood of occurrence could be cred i ted t owa rd justification of the safety system design. Each identified s ource of CCF should be evaluated on a case-by-case basis.
Clause 5.16 Common Cause Failure (cont.)
Clause 5.16 Common Cause Failure (cont.)
* I te m 1 is consistent with our c u r re nt CCF policy
* Item 1 is consistent with our current CCF policy  
- SRM-S ECY 0076, SRM-S EC Y 087, N U REG-0800 BT P 7-19 Revision 9.
- SRM-SECY-22-0076, SRM-SECY-93-087, NUREG-0800 BTP 7-19 Revision 9.
* Items 2, 3 and 4 a re not fully congruent with our c u r re nt CCF policy
* Items 2, 3 and 4 are not fully congruent with our current CCF policy
- Not requirements but a re methods or guidance on how to address CCF
- Not requirements but are methods or guidance on how to address CCF
- SRM-S EC Y 0076 provides for the expanded use of risk-informed approaches.
- SRM-SECY-22-0076 provides for the expanded use of risk-informed approaches.
* NRC staff recommends to IBR to 10 CFR 50.55a(h) the entirety of IEEE 603-2018 (with just the bolded portion of Item 1) with exemption to Items 2, 3 and 4 in order to be aligned with current Commission Policy.
* NRC staff recommends to IBR to 10 CFR 50.55a(h) the entirety of IEEE 603-2018 (with just the bolded portion of Item 1) with exemption to Items 2, 3 and 4 in order to be aligned with current Commission Policy.
15


15 Staff Approach and Considerations
Staff Approach and Considerations
* Incorporate the entirety of IEEE 603-2018 into 50.55a(h), with only the first sentence of Clause 5.16.
* Incorporate the entirety of IEEE 603-2018 into 50.55a(h), with only the first sentence of Clause 5.16.
- Aligned with existing CCF policies and guidance.
- Aligned with existing CCF policies and guidance.
- Regulatory treatment of referenced standards (i.e. secondary references) would remain unchanged - treated as guidance.
- Regulatory treatment of referenced standards (i.e. secondary references) would remain unchanged - treated as guidance.
- Applicable to new applicants, optional for current licensees.
- Applicable to new applicants, optional for current licensees.
* Once the rulemaking is complete, NRC may evaluate repurposing RG 1.153 to provide implementation guidance.
* Once the rulemaking is complete, NRC may evaluate repurposing RG 1.153 to provide implementation guidance.  
 
*This slide represents current staff position and subject to change 16
16
*This slide represents current staff position and subject to change Rulemaking Process & Milestones
 
Proposed Rule (Estimated) Final Rule (Estimated)
Rule Commencement 8/15/2024 Submission to Signature 4/7/2026 Authority Submission to Signature 3/25/2025 Publication in the Federal 7/24/2026 Authority Register Publication in the Federal 6/30/2025 Rule Becomes Effective 8/23/2026 Register Public Comment Period 6/30 -8/29/2025 Public Meeting TBD
 
For more information on NRCs rulemaking process click here: https://www.nrc. gov/about-nrc/regulatory/rulemaking /rulemaking-process.html


For updates regarding this rulemaking click here: https://www.nrc. gov/reading-rm/doc-collections/rulemaking-ruleforum/active/ruledetails.html?id=2203
Rulemaking Process & Milestones Proposed Rule (Estimated)
Final Rule (Estimated)
Rule Commencement 8/15/2024 Submission to Signature Authority 4/7/2026 Submission to Signature Authority 3/25/2025 Publication in the Federal Register 7/24/2026 Publication in the Federal Register 6/30/2025 Rule Becomes Effective 8/23/2026 Public Comment Period 6/30 -8/29/2025 Public Meeting TBD For more information on NRCs rulemaking process click here: https://www.nrc.gov/about-nrc/regulatory/rulemaking/rulemaking-process.html For updates regarding this rulemaking click here: https://www.nrc.gov/reading-rm/doc-collections/rulemaking-ruleforum/active/ruledetails.html?id=2203 17


17 Questions?}}
Questions?}}

Latest revision as of 10:12, 24 November 2024

IEEE 603-2018 NRC Presentation on Proposed Path Forward for Industrys Use of Institute of Electrical and Electronics Engineers Standards, Criteria for Safety Sysyems September 19, 2024
ML24289A228
Person / Time
Issue date: 10/15/2024
From: Calvin Cheung
NRC/NRR/DEX/EICB
To:
Gilberto Blas
References
Download: ML24289A228 (1)


Text

Proposed Path Forward for Industrys Use of Institute of Electrical and Electronics Engineers Standard (IEEE) 603-2018, Criteria for Safety Systems 10 CFR 50.55a(h), IEEE Std. 603

Outline

  • Meeting Purpose
  • Background
  • Objectives and Options
  • Evaluation of Options
  • Combining IEEE and ASME Rulemakings
  • Clause 5.16 - Common Cause Failure
  • Staff Approach and Considerations
  • Rulemaking Process and Milestones
  • Questions 2

Meeting Purpose To present the staffs progress on the path forward to address the use of the 2018 version of IEEE 603, IEEE Standard Criteria for Safety Systems for Nuclear Power Generating Stations, in the development of safety-related instrumentation and control (I&C) systems.

  • Obtain stakeholder feedback on the staffs proposed path forward.

3

=

Background===

  • Regulations for the design of protection and safety systems for nuclear power plants.

- Title 10 of the Code of Federal Regulations (10 CFR), Section 50.55a(h), Protection and safety systems, provides requirements for the design of protection and safety systems for nuclear power reactors.

- IEEE 279-1968, 279-1971, and 603-1991 are incorporated by reference (IBR) into 10 CFR 50.55a(h).

  • On September 14, 2023, NRC staff engaged with external stakeholders, receiving input on its plans for the development on a path forward for the use of IEEE 603-2018 (ML23242A169).
  • NEI provided their recommendation November 3, 2023, for IBR of IEEE 603-2018 with exception to Clause 5.16 Common Cause Failure (ML23307A127).

4

Objectives and Options

  • Objectives
1. Provide industry with the regulatory confidence to use the 2018 version in the development of safety-related I&C systems.
2. Establish a streamlined path to endorse new and improved standards that are developed to address digital technology advancements.
  • Options A. Revise a Regulatory Guide (e.g. RG 1.153).

B. Initiate rulemaking to incorporate by reference IEEE 603-2018.

C. Issue generic communication to summarize licensing pathways to using newer versions of the standard.

  • Staff evaluated the options on the basis of how well the options meet the two objectives to determine the path forward.

5

Option A - Regulatory Guide Revise a Regulatory Guide (e.g., RG 1.153)

Objective 1 is partially met Does not provide licensees and applicants the equivalent regulatory confidence as updating the regulations.

Objective 2 is met Utilizes existing regulatory guide process to endorse a standard.

6

Initiate rulemaking to incorporate by reference IEEE Std 603-2018 Objective 1 is met Provides licensees and applicants regulatory confidence to use IEEE Std. 603-2018.

Objective 2 is met Provides the opportunity to generate a blueprint for IEEE-603 to streamline future rulemaking efforts.

Option B - Rulemaking 7

Option C - Generic Communication Issue generic communication to summarize licensing pathways to using newer versions of the standard Objective 1 is partially met Does not provide licensees and applicants the equivalent regulatory confidence as updating the regulations.

Objective 2 is not met Utilizes existing generic communication process.

8

Removal of the IEEE reference may necessitate alternative requirements either through IBR of a different industry standard (e.g., International Standards) or development and inclusion of newly developed requirements within 10 CFR Part 50.55a.

Other Option - Removal of IEEE Stds. from 50.55a 9

Selected Option for Path Forward

  • Along with factoring stakeholder input and feedback, NRC staff evaluated and determined to proceed with Option B, Rulemaking.
  • Develop staff position and blueprint to pursue rulemaking to incorporate by reference of IEEE 603-2018.

10

Combining IEEE and ASME Rulemakings

  • NRC staff considered combining IEEE and ASME Rulemakings
  • Results Summary

- Complications from the misalignment in frequency of updates (ASME 2/6 yrs.

vs IEEE 10 yrs.).

- Increase in scope of the combined rulemaking could negatively impact both rules (i.e. schedule, complexity).

  • NRC staff decided not to pursue combined rulemaking

- OMB accepts one rulemaking per CFR at a time.

- Coordinate with ASME Code rulemaking to ensure schedules do not conflict.

11

Comparison Between IEEE 603-1991 and IEEE 603-2018 Clauses and subclauses were divided into items (151) to facilitate the comparison.

Identical - No changes in wording between the two standards; Equivalent - Formatting changes, updated standard revisions, updated wording, restructured numbering or similar; Enhancement - Improvements, clarifications, additional text modifying items on existing topics; and New - Added items (clauses, subclauses, or text) addressing new topics.

12

Comparison Between IEEE 603-1991 and IEEE-2018 (Cont.)

  • The staff concluded the following:

- the update to the standard is generally routine in nature, with predominantly identical, equivalent, or enhanced language

- for the four new items related to CCF, further evaluation necessary to ensure consistency with Commission Policy 13

Clause 5.16 - Common Cause Failure The safety system design and development shall address common-cause failures (CCF) that create a potential to degrade or defeat the safety system function. Methods for addressing CCF should include determining the following:

a) The CCF has sufficiently low likelihood of occurring.

Acceptable ways of reducing the likelihood of occurrence of some sources of CCF include the requirements imposed by this standard. Quality assurance programs (5.3), equipment qualification (5.4), and design attributes (e.g., 5.5 and 5.6) afford protection from design and manufacturing defects, external environmental effects, and internal failures. Human factors considerations (5.14) afford protection from operator errors.

Additionally, personnel training and plant procedures (i.e., operating, maintenance, and surveillance) afford protection from human errors. Other factors that may be considered are testability, applicable operating experience, and diversity within the safety system design.

b) The safety consequence that would result from the occurrence of the CCF in conjunction with any design basis event is low, such that public health and safety are maintained.

An acceptable way of determining the consequence of a CCF of the safety system is to perform a plant-level analysis of the loss or degradation of safety functions concurrent with applicable design basis events.

A safety system design that contains a source of CCF may be justified if the resulting consequence of the CCF is low, even when it cannot be demonstrated that the likelihood of occurrence of the CCF is sufficiently low. If the resulting consequence of the CCF is severe, a determination that the CCF has a very low likelihood of occurrence could be credited toward justification of the safety system design. Each identified source of CCF should be evaluated on a case-by-case basis.

Item 1 Item 2 Item 3 Item 4

Clause 5.16 Common Cause Failure (cont.)

  • Item 1 is consistent with our current CCF policy

- SRM-SECY-22-0076, SRM-SECY-93-087, NUREG-0800 BTP 7-19 Revision 9.

  • Items 2, 3 and 4 are not fully congruent with our current CCF policy

- Not requirements but are methods or guidance on how to address CCF

- SRM-SECY-22-0076 provides for the expanded use of risk-informed approaches.

  • NRC staff recommends to IBR to 10 CFR 50.55a(h) the entirety of IEEE 603-2018 (with just the bolded portion of Item 1) with exemption to Items 2, 3 and 4 in order to be aligned with current Commission Policy.

15

Staff Approach and Considerations

  • Incorporate the entirety of IEEE 603-2018 into 50.55a(h), with only the first sentence of Clause 5.16.

- Aligned with existing CCF policies and guidance.

- Regulatory treatment of referenced standards (i.e. secondary references) would remain unchanged - treated as guidance.

- Applicable to new applicants, optional for current licensees.

  • Once the rulemaking is complete, NRC may evaluate repurposing RG 1.153 to provide implementation guidance.
  • This slide represents current staff position and subject to change 16

Rulemaking Process & Milestones Proposed Rule (Estimated)

Final Rule (Estimated)

Rule Commencement 8/15/2024 Submission to Signature Authority 4/7/2026 Submission to Signature Authority 3/25/2025 Publication in the Federal Register 7/24/2026 Publication in the Federal Register 6/30/2025 Rule Becomes Effective 8/23/2026 Public Comment Period 6/30 -8/29/2025 Public Meeting TBD For more information on NRCs rulemaking process click here: https://www.nrc.gov/about-nrc/regulatory/rulemaking/rulemaking-process.html For updates regarding this rulemaking click here: https://www.nrc.gov/reading-rm/doc-collections/rulemaking-ruleforum/active/ruledetails.html?id=2203 17

Questions?