ML22347A153: Difference between revisions

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


=Text=
=Text=
{{#Wiki_filter:Limerick Generating Station Digital Modernization Project Acceptance Review Follow-up on IEEE-603 Compliance Issues December 15, 2022
{{#Wiki_filter:Limerick Generating Station Digital Modernization Project Acceptance Review Follow-up on IEEE-603 Compliance Issues


CEG Participants
December 15, 2022 CEG Participants
* Licensing
* Licensing
* Dave Helker, Licensing Manager
* Dave Helker, Licensing Manager
Line 28: Line 28:
* Jim Berg, Site Regulatory Assurance
* Jim Berg, Site Regulatory Assurance
* Engineering
* Engineering
      - John Connelly, Central Design Organization (CDO) Manager
- John Connelly, Central Design Organization (CDO) Manager
      - Mark Samselski, CDO - Lead Responsible Engineer
- Mark Samselski, CDO - Lead Responsible Engineer
      - George Bonanni, CDO - Senior Staff Engineer
- George Bonanni, CDO - Senior Staff Engineer
      - Scott Schumacher, Systems Engineering
- Scott Schumacher, Systems Engineering
* WEC
* WEC
      - Warren Odess-Gillett, WEC Licensing Lead 1
- Warren Odess-Gillett, WEC Licensing Lead


Opening Remarks
1 Opening Remarks
* NRC
* NRC
* CEG 2
* CEG


Acceptance Review Letter- IEEE 603 Compliance
2 Acceptance Review Letter-IEEE 603 Compliance
* Items 2 and 3: Exceptions to IEEE-603-1991
* Items 2 and 3: Exceptions to IEEE-603-1991
* At the public meeting, the staff noted that the IEEE-603-1991 clauses that Constellation is taking exception to correspond to similar requirements in IEEE Standard 279-1968 that are required to be met for proposed protection systems at Limerick in accordance with 10 CFR 55.55a(h)(2). Taking exception to the clauses in IEEE-603-1991 would seem to indicate that the system planned for Limerick would not comply with 10 CFR 55.55 a(h)(2), in which case the system could not be approved without additional licensing actions (e.g., requesting an exemption or alternative request). As justification for the exception, the LAR references, and Constellation discussed at the public meeting, Limericks updated final safety analysis report (UFSAR) and emergency operating procedures. However, the staff could not identify a clear regulatory basis for the exceptions in these references during the acceptance review period.
* At the public meeting, the staff noted that the IEEE-603-1991 clauses that Constellation is taking exception to correspond to similar requirements in IEEE Standard 279-1968 that are required to be met for proposed protection systems at Limerick in accordance with 10 CFR 55.55a(h)(2). Taking exception to the clauses in IEEE-603-1991 would seem to indicate that the system planned for Limerick would not comply with 10 CFR 55.55 a(h)(2), in which case the system could not be approved without additional licensing actions (e.g., requesting an exemption or alternative request). As justification for the exception, the LAR references, and Constellation discussed at the public meeting, Limericks updated final safety analysis report (UFSAR) and emergency operating procedures. However, the staff could not identify a clear regulatory basis for the exceptions in these references during the acceptance review period.
* While follow up is necessary to determine if the licensing basis documents provide sufficient justification, the staff concluded that resolution of these issues was not necessary to support acceptance of the LAR because Constellation had provided a justification for the exceptions. Because the staff has not been able to verify the adequacy of the justification through its review of the information provided to date, this issue is a high priority licensing concern that needs to be addressed by Constellation.
* While follow up is necessary to determine if the licensing basis documents provide sufficient justification, the staff concluded that resolution of these issues was not necessary to support acceptance of the LAR because Constellation had provided a justification for the exceptions. Because the staff has not been able to verify the adequacy of the justification through its review of the information provided to date, this issue is a high priority licensing concern that needs to be addressed by Constellation.
* The staff will discuss this issue further at the public meeting with Constellation scheduled for December 15, 2022, to identify an appropriate regulatory path forward.
* The staff will discuss this issue further at the public meeting with Constellation scheduled for December 15, 2022, to identify an appropriate regulatory path forward.
Possible paths include the staff issuing a request for additional information as part of its detailed review of the LAR, or Constellation providing supplemental information or an 3
Possible paths include the staff issuing a request for additional information as part of its detailed review of the LAR, or Constellation providing supplemental information or an additional licensing action requesting an exemption or alternative request.
additional licensing action requesting an exemption or alternative request.
3 Vendor Oversight
 
Vendor Oversight
* Constellations Vendor Oversight Plan (VOP) was executed during review.
* Constellations Vendor Oversight Plan (VOP) was executed during review.
* The plan requires the execution of Constellations Owners Acceptance Review of External Technical Products Procedure.
* The plan requires the execution of Constellations Owners Acceptance Review of External Technical Products Procedure.
Line 53: Line 51:
* The typo identified for IEEE 603 Clause 5.6.1 was not identified by reviewers.
* The typo identified for IEEE 603 Clause 5.6.1 was not identified by reviewers.
* The following actions were taken per the VOP to ensure high quality:
* The following actions were taken per the VOP to ensure high quality:
    - An entry into Constellations Supplier Fundamental Management System (SFMS)
- An entry into Constellations Supplier Fundamental Management System (SFMS)
    - An entry into the VOP Action Tracking Item Assignment System (ATI 04456784) to formally track completion and results of the vendors Corrective Action Program Issue Report (CAP-2022-10020).
- An entry into the VOP Action Tracking Item Assignment System (ATI 04456784) to formally track completion and results of the vendors Corrective Action Program Issue Report (CAP-2022-10020).
    - Review results of the issue report
- Review results of the issue report
    - Ensure LTR is revised 4
- Ensure LTR is revised


IEEE 603 Clauses 6.6 & 7.4
4 IEEE 603 Clauses 6.6 & 7.4
* Constellation provided comments to ensure EOPs and SAGs overrides are described appropriately in the LTR during the review process.
* Constellation provided comments to ensure EOPs and SAGs overrides are described appropriately in the LTR during the review process.
* Subsequent to the first Acceptance Review Meeting, the Constellation team reached out to industry experts to aid in the understanding of the Operating Bypass definition in the context of EOPs and SAGs.
* Subsequent to the first Acceptance Review Meeting, the Constellation team reached out to industry experts to aid in the understanding of the Operating Bypass definition in the context of EOPs and SAGs.
Line 67: Line 65:
== Conclusion:==
== Conclusion:==
LTR miscategorized overrides as operating bypasses. This will be corrected in next LTR revision.
LTR miscategorized overrides as operating bypasses. This will be corrected in next LTR revision.
5


What is an Operating Bypass?
5 What is an Operating Bypass?
* According to IEEE Std 603-1991, an operating bypass is used to permit plant mode changes:
*According to IEEE Std 603-1991, an operating bypass is used to permit plant mode changes:
* With this definition for operating bypass, all PPS operating bypasses meet the criteria in both IEEE Std 279 and 603, the bypass will be removed automatically whenever permissive conditions are not met. [IEEE Std 279].
* With this definition for operating bypass, all PPS operating bypasses meet the criteria in both IEEE Std 279 and 603, the bypass will be removed automatically whenever permissive conditions are not met. [IEEE Std 279].
* Overrides in the Limerick EOPs and SAGs are not operating bypasses per the definition in IEEE Std 603-1991 and therefore this criteria in IEEE Std 279 and 603 does not apply.
*Overrides in the Limerick EOPs and SAGs are not operating bypasses per the definition in IEEE Std 603-1991 and therefore this criteria in IEEE Std 279 and 603 does not apply.
* With this decision of full compliance, there will be no action to request alternate compliance via 10CFR50.55(a)(z), as discussed during previous Acceptance Review Meeting held on November 10, 2022.
*With this decision of full compliance, there will be no action to request alternate compliance via 10CFR50.55(a)(z), as discussed during previous Acceptance Review Meeting held on November 10, 2022.
6


Changes to the Licensing Technical Report (LTR)
6 Changes to the Licensing Technical Report (LTR)
* Accordingly, the LTR (WCAP-18598) will be revised.
* Accordingly, the LTR (WCAP-18598) will be revised.
* Compliance to IEEE Std 603 Table ( Section 7) for Clause 5.6.1 will be changed from PC to C.
* Compliance to IEEE Std 603 Table ( Section 7) for Clause 5.6.1 will be changed from PC to C.
Line 83: Line 79:
* It is expected that additional changes will also be incorporated into LTR during the final design process and during the RAI process, with goal of updating these and the above in Spring 2023.
* It is expected that additional changes will also be incorporated into LTR during the final design process and during the RAI process, with goal of updating these and the above in Spring 2023.
* The revised LTR will be submitted on the docket when completed.
* The revised LTR will be submitted on the docket when completed.
7


Changes to the Licensing Technical Report (LTR) 8
7 Changes to the Licensing Technical Report (LTR)
 
8 Changes to the Licensing Technical Report (LTR)


Changes to the Licensing Technical Report (LTR)
Table 7-1 Compliance/Conformance Matrix for IEEE Std 603 and IEEE Std 7-4.3.2
Table 7-1 Compliance/Conformance Matrix for IEEE Std 603 and IEEE Std 7-4.3.2 IEEE  IEEE                Title      Compliance/ Section(s)
Std  Std 7-                            Conformance 603    4.3.2 Clause Clause 5.6.1          Between Redundant Portions PC C        3.5.14.1 of a Safety System 6.6        6*  Operating Bypasses          EC          3.3.2.8 7.4            Operating Bypass            EC          3.3.2.8 7*
9


Close Out Remarks
IEEE IEEE Title Compliance/ Section(s)
Std Std 7-Conformance 603 4.3.2 Clause Clause 5.6.1 Between RedundantPortions PC C 3.5.14.1 ofaSafetySystem
 
6.6 6* OperatingBypasses EC 3.3.2.8 7.4 7* Operating Bypass EC 3.3.2.8
 
9 Close Out Remarks
* Questions?
* Questions?
* Next Steps?
* Next Steps?
* Final Remarks
* Final Remarks
* CEG
* CEG
* NRC 10}}
* NRC
 
10}}

Latest revision as of 15:30, 15 November 2024

Public Meeting Presentation, December 15, 2022 Di&C License Amendment Request
ML22347A153
Person / Time
Site: Limerick  Constellation icon.png
Issue date: 12/13/2022
From:
Constellation Energy Generation
To:
Division of Operating Reactor Licensing
Sreenivas V, NRR/DORL/LPLI, 415-2597
References
EPID L-2022-LLA-0140
Download: ML22347A153 (1)


Text

Limerick Generating Station Digital Modernization Project Acceptance Review Follow-up on IEEE-603 Compliance Issues

December 15, 2022 CEG Participants

  • Licensing
  • Dave Helker, Licensing Manager
  • Frank Mascitelli, Licensing Lead
  • Ashley Rickey, Licensing Engineer
  • Pareez Golub, Digital Licensing SME
  • Jim Berg, Site Regulatory Assurance
  • Engineering

- John Connelly, Central Design Organization (CDO) Manager

- Mark Samselski, CDO - Lead Responsible Engineer

- George Bonanni, CDO - Senior Staff Engineer

- Scott Schumacher, Systems Engineering

- Warren Odess-Gillett, WEC Licensing Lead

1 Opening Remarks

  • NRC

2 Acceptance Review Letter-IEEE 603 Compliance

  • At the public meeting, the staff noted that the IEEE-603-1991 clauses that Constellation is taking exception to correspond to similar requirements in IEEE Standard 279-1968 that are required to be met for proposed protection systems at Limerick in accordance with 10 CFR 55.55a(h)(2). Taking exception to the clauses in IEEE-603-1991 would seem to indicate that the system planned for Limerick would not comply with 10 CFR 55.55 a(h)(2), in which case the system could not be approved without additional licensing actions (e.g., requesting an exemption or alternative request). As justification for the exception, the LAR references, and Constellation discussed at the public meeting, Limericks updated final safety analysis report (UFSAR) and emergency operating procedures. However, the staff could not identify a clear regulatory basis for the exceptions in these references during the acceptance review period.
  • While follow up is necessary to determine if the licensing basis documents provide sufficient justification, the staff concluded that resolution of these issues was not necessary to support acceptance of the LAR because Constellation had provided a justification for the exceptions. Because the staff has not been able to verify the adequacy of the justification through its review of the information provided to date, this issue is a high priority licensing concern that needs to be addressed by Constellation.
  • The staff will discuss this issue further at the public meeting with Constellation scheduled for December 15, 2022, to identify an appropriate regulatory path forward.

Possible paths include the staff issuing a request for additional information as part of its detailed review of the LAR, or Constellation providing supplemental information or an additional licensing action requesting an exemption or alternative request.

3 Vendor Oversight

  • Constellations Vendor Oversight Plan (VOP) was executed during review.
  • The plan requires the execution of Constellations Owners Acceptance Review of External Technical Products Procedure.
  • Constellation provided comments to ensure Emergency Operating Procedures (EOPs) and Severe Accident Guidelines (SAGs) overrides are described appropriately in the Licensing Technical Report (LTR).
  • The typo identified for IEEE 603 Clause 5.6.1 was not identified by reviewers.
  • The following actions were taken per the VOP to ensure high quality:

- An entry into Constellations Supplier Fundamental Management System (SFMS)

- An entry into the VOP Action Tracking Item Assignment System (ATI 04456784) to formally track completion and results of the vendors Corrective Action Program Issue Report (CAP-2022-10020).

- Review results of the issue report

- Ensure LTR is revised

4 IEEE 603 Clauses 6.6 & 7.4

  • Constellation provided comments to ensure EOPs and SAGs overrides are described appropriately in the LTR during the review process.
  • Subsequent to the first Acceptance Review Meeting, the Constellation team reached out to industry experts to aid in the understanding of the Operating Bypass definition in the context of EOPs and SAGs.
  • Discussions with IEEE standards working group members identified that Operating Bypasses, by definition, permit plant mode changes in IEEE 603-1991 & IEEE-279.
  • Further review of the application of EOPs and SAGs in the PPS revealed that these features do not permit plant mode changes.
  • The logic developed to support the EOPs and SAGs are overrides to ensure the appropriate safety function can be executed.

Conclusion:

LTR miscategorized overrides as operating bypasses. This will be corrected in next LTR revision.

5 What is an Operating Bypass?

  • According to IEEE Std 603-1991, an operating bypass is used to permit plant mode changes:
  • With this definition for operating bypass, all PPS operating bypasses meet the criteria in both IEEE Std 279 and 603, the bypass will be removed automatically whenever permissive conditions are not met. [IEEE Std 279].
  • With this decision of full compliance, there will be no action to request alternate compliance via 10CFR50.55(a)(z), as discussed during previous Acceptance Review Meeting held on November 10, 2022.

6 Changes to the Licensing Technical Report (LTR)

  • Compliance to IEEE Std 603 Table ( Section 7) for Clause 5.6.1 will be changed from PC to C.
  • The Compliance/Conformance indication in the IEEE Std 603 Compliance Table (Section 7) for Clauses 6.6 and 7.4 will change from E to C.
  • Section 3.3.2.8 will be revised as shown on the next slide.
  • It is expected that additional changes will also be incorporated into LTR during the final design process and during the RAI process, with goal of updating these and the above in Spring 2023.
  • The revised LTR will be submitted on the docket when completed.

7 Changes to the Licensing Technical Report (LTR)

8 Changes to the Licensing Technical Report (LTR)

Table 7-1 Compliance/Conformance Matrix for IEEE Std 603 and IEEE Std 7-4.3.2

IEEE IEEE Title Compliance/ Section(s)

Std Std 7-Conformance 603 4.3.2 Clause Clause 5.6.1 Between RedundantPortions PC C 3.5.14.1 ofaSafetySystem

6.6 6* OperatingBypasses EC 3.3.2.8 7.4 7* Operating Bypass EC 3.3.2.8

9 Close Out Remarks

  • Questions?
  • Next Steps?
  • Final Remarks
  • NRC

10