ML22349A647

Issuance of Amendment Nos. 325, 348, and 308; 362 and 356; and 158 and 66 Regarding Adoption of TSTF-529, Rev. 4, Clarify Use and Application Rules

ML22349A647
Person / Time
Site:	Browns Ferry, Watts Bar, Sequoyah
Issue date:	01/20/2023
From:	Perry Buckberg Plant Licensing Branch II
To:	Jim Barstow Tennessee Valley Authority
Green K
References
EPID L-2022-LLA-0088
Download: ML22349A647 (78)

Text

January 20, 2023 Mr. James Barstow Vice President, Nuclear Regulatory Affairs and Support Services Tennessee Valley Authority 1101 Market Street, LP 4A-C Chattanooga, TN 37402-2801

SUBJECT:

BROWNS FERRY NUCLEAR PLANT, UNITS 1, 2, AND 3; SEQUOYAH NUCLEAR PLANT, UNITS 1 AND 2; WATTS BAR NUCLEAR PLANT, UNITS 1 AND 2 - ISSUANCE OF AMENDMENT NOS. 326, 349, AND 309; 361 AND 355; 158 AND 66 REGARDING ADOPTION OF TSTF-529, REVISION 4, CLARIFY USE AND APPLICATION RULES (EPID L-2022-LLA-0088)

Dear Mr. Barstow:

The U.S. Nuclear Regulatory Commission (the Commission) has issued the enclosed Amendment Nos. 326, 349, and 309 to Renewed Facility Operating Licenses Nos. DPR-33, DPR-52, and DPR-68 for the Browns Ferry Nuclear Plant, Units 1, 2, and 3, respectively; Amendment Nos. 361 and 355 to Renewed Facility Operating License Nos. DPR-77 and DPR-79, for the Sequoyah Nuclear Plant, Units 1 and 2, respectively; and Amendment Nos. 158 and 66 to Facility Operating License Nos. NPF-90 and NPF-96 for the Watts Bar Nuclear Plant, Units 1 and 2, respectively. The amendment consists of changes to the Technical Specifications (TSs) in response to your application dated June 13, 2022.

The amendments revise the TSs Sections 1.3, Completion Times, and 3.0, Limiting Condition for Operation (LCO) Applicability and Surveillance Requirement (SR) Applicability for Browns Ferry Nuclear Plant, Units 1, 2, and 3; Sequoyah Nuclear Plant, Units 1 and 2; and Watts Bar Nuclear Plant, Units 1 and 2. Specifically, these changes clarify and expand the use and application of the TS usage rules and are consistent with NRC-approved Technical Specifications Task Force (TSTF) Traveler TSTF-529, Revision 4, Clarify Use and Application Rules, TSTF-529, Revision 4, was approved by the NRC on April 21, 2016.

J. Barstow A copy of the Safety Evaluation is also enclosed. Notice of Issuance will be included in the Commissions monthly Federal Register notice.

Sincerely,

/RA/

Perry H. Buckberg, Senior Project Manager Plant Licensing Branch II-2 Division of Operating Reactor Licensing Office of Nuclear Reactor Regulation Docket Nos. 50-259, 50-260, 50-296, 50-327, 50-328, 50-390, and 50-391

Enclosures:

1. Amendment No. 326 to DPR-33

2. Amendment No. 349 to DPR-52

3. Amendment No. 309 to DPR-68

4. Amendment No. 361 to DPR-77

5. Amendment No. 355 to DPR-79

6. Amendment No. 158 to NPF-90

7. Amendment No. 66 to NPF-96

8. Safety Evaluation cc: Listserv TENNESSEE VALLEY AUTHORITY DOCKET NO. 50-259 BROWNS FERRY NUCLEAR PLANT UNIT 1 AMENDMENT TO RENEWED FACILITY OPERATING LICENSE Amendment No. 326 Renewed License No. DPR-33 1.

The U.S. Nuclear Regulatory Commission (the Commission) has found that:

A.

The application for amendment by the Tennessee Valley Authority (the licensee) dated June 13, 2022, complies with the standards and requirements of the Atomic Energy Act of 1954, as amended (the Act), and the Commissions rules and regulations set forth in Title 10 of the Code of Federal Regulations (10 CFR)

Chapter I; B.

The facility will operate in conformity with the application, the provisions of the Act, and the rules and regulations of the Commission; C.

There is reasonable assurance (i) that the activities authorized by this amendment can be conducted without endangering the health and safety of the public, and (ii) that such activities will be conducted in compliance with the Commissions regulations; D.

The issuance of this amendment will not be inimical to the common defense and security or to the health and safety of the public; and E.

The issuance of this amendment is in accordance with 10 CFR Part 51 of the Commissions regulations and all applicable requirements have been satisfied.

2.

Accordingly, the license is amended by changes to the Technical Specifications as indicated in the attachment to this license amendment and paragraph 2.C.(2) of Renewed Facility Operating License No. DPR-33 is hereby amended to read as follows:

(2)

Technical Specifications The Technical Specifications contained in Appendices A and B, as revised through Amendment No. 326, are hereby incorporated in the renewed operating license. The licensee shall operate the facility in accordance with the Technical Specifications.

3.

This license amendment is effective as of its date of issuance and shall be implemented within 60 days from the date of issuance.

FOR THE NUCLEAR REGULATORY COMMISSION David J. Wrona, Chief Plant Licensing Branch II-2 Division of Operating Reactor Licensing Office of Nuclear Reactor Regulation

Attachment:

Changes to the Renewed Facility Operating License and Technical Specifications Date of Issuance: January 20, 2023 David J.

Wrona Digitally signed by David J. Wrona Date: 2023.01.20 14:17:07 -05'00'

ATTACHMENT TO LICENSE AMENDMENT NO. 326 BROWNS FERRY NUCLEAR PLANT, UNIT 1 TO RENEWED FACILITY OPERATING LICENSE NO. DPR-33 DOCKET NO. 50-259 Replace page 3 of Renewed Facility Operating License No. DPR-33 with the attached page 3.

The revised page is identified by amendment number and contains a marginal line indicating the area of change.

Replace the following pages of the Appendix A Technical Specifications with the attached pages. The revised pages are identified by amendment number and contain marginal lines indicating the areas of change.

Remove Insert 1.3-1 1.3-1 1.3-2 1.3-2 3.0-2 3.0-2 3.0-4 3.0-4 BFN-UNIT 1 Renewed License No. DPR-33 Amendment No. 326 (3)

Pursuant to the Act and 10 CFR Parts 30, 40, and 70, to receive, possess, and use at any time any byproduct, source, and special nuclear material as sealed neutron sources for reactor startup, sealed sources for reactor instrumentation and radiation monitoring equipment calibration, and as fission detectors in amounts as required; (4)

Pursuant to the Act and 10 CFR Parts 30, 40, and 70, to receive, possess, and use in amounts as required any byproduct, source, or special nuclear material without restriction to chemical or physical form for sample analysis or equipment and instrument calibration or associated with radioactive apparatus or components; (5)

Pursuant to the Act and 10 CFR Parts 30 and 70, to possess but not separate, such byproduct and special nuclear materials as may be produced by the operation of the facility.

C.

This renewed operating license shall be deemed to contain and is subject to the conditions specified in the following Commission regulations in 10 CFR Chapter I:

Part 20, Section 30.34 of Part 30, Section 40.41 of Part 40, Sections 50.54 and 50.59 of Part 50, and Section 70.32 of Part 70; is subject to all applicable provisions of the Act and to the rules, regulations, and orders of the Commission now or hereafter in effect; and is subject to the additional conditions specified or incorporated below:

(1)

Maximum Power Level The licensee is authorized to operate the facility at steady state reactor core power levels not in excess of 3952 megawatts thermal.

(2)

Technical Specifications The Technical Specifications contained in Appendices A and B, as revised through Amendment No. 326, are hereby incorporated in the renewed operating license. The licensee shall operate the facility in accordance with the Technical Specifications.

For Surveillance Requirements (SRs) that are new in Amendment 234 to Facility Operating License DPR-33, the first performance is due at the end of the first surveillance interval that begins at implementation of the Amendment 234. For SRs that existed prior to Amendment 234, including SRs with modified acceptance criteria and SRs whose frequency of performance is being extended, the first performance is due at the end of the first surveillance interval that begins on the date the surveillance was last performed prior to implementation of Amendment 234.

Completion Times 1.3 (continued)

BFN-UNIT 1 1.3-1 Amendment No. 234, 326 1.0 USE AND APPLICATION 1.3 Completion Times PURPOSE The purpose of this section is to establish the Completion Time convention and to provide guidance for its use.

BACKGROUND Limiting Conditions for Operation (LCOs) specify minimum requirements for ensuring safe operation of the unit. The ACTIONS associated with an LCO state Conditions that typically describe the ways in which the requirements of the LCO can fail to be met. Specified with each stated Condition are Required Action(s) and Completion Times(s).

DESCRIPTION The Completion Time is the amount of time allowed for completing a Required Action. It is referenced to the discovery of a situation (e.g.,

inoperable equipment or variable not within limits) that requires entering an ACTIONS Condition unless otherwise specified, providing the unit is in a MODE or specified condition stated in the Applicability of the LCO.

Unless otherwise specified, the Completion Time begins when a senior licensed operator on the operating shift crew with responsibility for plant operations makes the determination that an LCO is not met and an ACTIONS Condition is entered. The "otherwise specified" exceptions are varied, such as a Required Action Note or Surveillance Requirement Note that provides an alternative time to perform specific tasks, such as testing, without starting the Completion Time. While utilizing the Note, should a Condition be applicable for any reason not addressed by the Note, the Completion Time begins. Should the time allowance in the Note be exceeded, the Completion Time begins at that point. The exceptions may also be incorporated into the Completion Time. For example, LCO 3.8.1, "AC Sources - Operating," Required Action B.3, requires declaring required feature(s) supported by an inoperable diesel generator, inoperable when the redundant required feature(s) are inoperable. The Completion Time states, "4 hours4.62963e-5 days <br />0.00111 hours <br />6.613757e-6 weeks <br />1.522e-6 months <br /> from discovery of Condition B concurrent with inoperability of redundant required feature(s)." In this case the Completion Time does not begin until the conditions in the Completion Time are satisfied.

Required Actions must be completed prior to the expiration of the specified Completion Time. An ACTIONS Condition remains in effect and the Required Actions apply until the Condition no longer exists or the unit is not within the LCO Applicability.

Completion Times 1.3 (continued)

BFN-UNIT 1 1.3-2 Amendment No. 234, 326 1.3 Completion Times DESCRIPTION If situations are discovered that require entry into more than one (continued)

Condition at a time within a single LCO (multiple Conditions), the Required Actions for each Condition must be performed within the associated Completion Time. When in multiple Conditions, separate Completion Times are tracked for each Condition starting from the discovery of the situation that required entry into the Condition, unless otherwise specified.

Once a Condition has been entered, subsequent divisions, subsystems, components, or variables expressed in the Condition, discovered to be inoperable or not within limits, will not result in separate entry into the Condition unless specifically stated. The Required Actions of the Condition continue to apply to each additional failure, with Completion Times based on initial entry into the Condition, unless otherwise specified.

However, when a subsequent division, subsystem, component, or variable expressed in the Condition is discovered to be inoperable or not within limits, the Completion Time(s) may be extended. To apply this Completion Time extension, two criteria must first be met. The subsequent inoperability:

a. Must exist concurrent with the first inoperability; and

b. Must remain inoperable or not within limits after the first inoperability is resolved.

The total Completion Time allowed for completing a Required Action to address the subsequent inoperability shall be limited to the more restrictive of either:

a. The stated Completion Time, as measured from the initial entry into the Condition, plus an additional 24 hours2.777778e-4 days <br />0.00667 hours <br />3.968254e-5 weeks <br />9.132e-6 months <br />; or

b. The stated Completion Time as measured from discovery of the subsequent inoperability.

The above Completion Time extensions do not apply to those Specifications that have exceptions that allow completely separate re-entry into the Condition (for each division, subsystem, component or variable expressed in the Condition) and separate tracking of Completion Times based on this re-entry. These exceptions are stated in individual Specifications.

LCO Applicability 3.0 (continued)

BFN-UNIT 1 3.0-2 Amendment No. 234, 249, 326 3.0 LCO APPLICABILITY (continued)

LCO 3.0.4 When an LCO is not met, entry into a MODE or other specified condition in the Applicability shall only be made:

a.

When the associated ACTIONS to be entered permit continued operation in the MODE or other specified condition in the Applicability for an unlimited period of time; b.

After performance of a risk assessment addressing inoperable systems and components, consideration of the results, determination of the acceptability of entering the MODE or other specified condition in the Applicability, and establishment of risk management actions, if appropriate (exceptions to this Specification are stated in the individual Specifications); or c.

When an allowance is stated in the individual value, parameter, or other Specification.

This Specification shall not prevent changes in MODES or other specified conditions in the Applicability that are required to comply with ACTIONS or that are part of a shutdown of the unit.

LCO 3.0.5 Equipment removed from service or declared inoperable to comply with ACTIONS may be returned to service under administrative control solely to perform testing required to demonstrate its OPERABILITY or the OPERABILITY of other equipment. This is an exception to LCO 3.0.2 for the system returned to service under administrative control to perform the testing required to demonstrate OPERABILITY.

LCO 3.0.6 When a supported system LCO is not met solely due to a support system LCO not being met, the Conditions and Required Actions associated with this supported system are not required to be entered. Only the support system LCO ACTIONS are required to be entered. This is an exception to LCO 3.0.2 for the supported system. In this event, an evaluation shall be performed in accordance with Specification 5.5.11, "Safety Function Determination Program (SFDP)." If a loss of safety function is

SR Applicability 3.0 (continued)

BFN-UNIT 1 3.0-4 Amendment No. 234, 243, 326 3.0 SURVEILLANCE REQUIREMENT (SR) APPLICABILITY SR 3.0.1 SRs shall be met during the MODES or other specified conditions in the Applicability for individual LCOs, unless otherwise stated in the SR. Failure to meet a Surveillance, whether such failure is experienced during the performance of the Surveillance or between performances of the Surveillance, shall be failure to meet the LCO.

Failure to perform a Surveillance within the specified Frequency shall be failure to meet the LCO except as provided in SR 3.0.3.

Surveillances do not have to be performed on inoperable equipment or variables outside specified limits.

SR 3.0.2 The specified Frequency for each SR is met if the Surveillance is performed within 1.25 times the interval specified in the Frequency, as measured from the previous performance or as measured from the time a specified condition of the Frequency is met.

For Frequencies specified as "once," the above interval extension does not apply. If a Completion Time requires periodic performance on a "once per..." basis, the above Frequency extension applies to each performance after the initial performance.

Exceptions to this Specification are stated in the individual Specifications.

SR 3.0.3 If it is discovered that a Surveillance was not performed within its specified Frequency, then compliance with the requirement to declare the LCO not met may be delayed, from the time of discovery, up to 24 hours2.777778e-4 days <br />0.00667 hours <br />3.968254e-5 weeks <br />9.132e-6 months <br /> or up to the limit of the specified Frequency, whichever is greater. This delay period is permitted to allow performance of the Surveillance. The delay period is only applicable when there is a reasonable expectation the Surveillance will be met when performed. A risk evaluation shall be performed for any Surveillance delayed greater than 24 hours2.777778e-4 days <br />0.00667 hours <br />3.968254e-5 weeks <br />9.132e-6 months <br /> and the risk impact shall be managed.

TENNESSEE VALLEY AUTHORITY DOCKET NO. 50-260 BROWNS FERRY NUCLEAR PLANT, UNIT 2 AMENDMENT TO RENEWED FACILITY OPERATING LICENSE Amendment No. 349 Renewed License No. DPR-52

1.

The U.S. Nuclear Regulatory Commission (the Commission) has found that:

A.

The application for amendment by the Tennessee Valley Authority (the licensee) dated June 13, 2022, complies with the standards and requirements of the Atomic Energy Act of 1954, as amended (the Act), and the Commissions rules and regulations set forth in Title 10 of the Code of Federal Regulations (10 CFR)

Chapter I; B.

The facility will operate in conformity with the application, the provisions of the Act, and the rules and regulations of the Commission; C.

There is reasonable assurance (i) that the activities authorized by this amendment can be conducted without endangering the health and safety of the public, and (ii) that such activities will be conducted in compliance with the Commissions regulations; D.

The issuance of this amendment will not be inimical to the common defense and security or to the health and safety of the public; and E.

The issuance of this amendment is in accordance with 10 CFR Part 51 of the Commissions regulations and all applicable requirements have been satisfied.

2.

Accordingly, the license is amended by changes to the Technical Specifications as indicated in the attachment to this license amendment and paragraph 2.C.(2) of Renewed Facility Operating License No. DPR-52 is hereby amended to read as follows:

(2)

Technical Specifications The Technical Specifications contained in Appendices A and B, as revised through Amendment No. 349, are hereby incorporated in the renewed operating license. The licensee shall operate the facility in accordance with the Technical Specifications.

3.

This license amendment is effective as of its date of issuance and shall be implemented within 60 days from the date of issuance.

FOR THE NUCLEAR REGULATORY COMMISSION David J. Wrona, Chief Plant Licensing Branch II-2 Division of Operating Reactor Licensing Office of Nuclear Reactor Regulation

Attachment:

Changes to the Renewed Facility Operating License and Technical Specifications Date of Issuance: January 20, 2023 David J.

Wrona Digitally signed by David J. Wrona Date: 2023.01.20 14:17:47 -05'00'

ATTACHMENT TO LICENSE AMENDMENT NO. 349 BROWNS FERRY NUCLEAR PLANT, UNIT 2 RENEWED FACILITY OPERATING LICENSE NO. DPR-52 DOCKET NO. 50-260 Replace page 3 of Renewed Facility Operating License No. DPR-52 with the attached page 3.

The revised page is identified by amendment number and contains a marginal line indicating the area of change.

Replace the following pages of the Appendix A Technical Specifications with the attached pages. The revised pages are identified by amendment number and contain marginal lines indicating the areas of change.

Remove Insert 1.3-1 1.3-1 1.3-2 1.3-2 3.0-2 3.0-2 3.0-4 3.0-4 BFN-UNIT 2 Renewed License No. DPR-52 Amendment No. 349 sealed neutron sources for reactor startup, sealed sources for reactor instrumentation and radiation monitoring equipment calibration, and as fission detectors in amounts as required; (4)

Pursuant to the Act and 10 CFR Parts 30, 40, and 70, to receive, possess, and use in amounts as required any byproduct, source, or special nuclear material without restriction to chemical or physical form for sample analysis or equipment and instrument calibration or associated with radioactive apparatus or components; (5)

Pursuant to the Act and 10 CFR Parts 30 and 70, to possess but not separate, such byproduct and special nuclear materials as may be produced by the operation of the facility.

C.

This renewed operating license shall be deemed to contain and is subject to the conditions specified in the following Commission regulations in 10 CFR Chapter I:

Part 20, Section 30.34 of Part 30, Section 40.41 of Part 40, Sections 50.54 and 50.59 of Part 50, and Section 70.32 of Part 70; is subject to all applicable provisions of the Act and to the rules, regulations, and orders of the Commission now or hereafter in effect; and is subject to the additional conditions specified or incorporated below:

(1)

Maximum Power Level The licensee is authorized to operate the facility at steady state reactor core power levels not in excess of 3952 megawatts thermal.

(2)

Technical Specifications The Technical Specifications contained in Appendices A and B, as revised through Amendment No. 349, are hereby incorporated in the renewed operating license. The licensee shall operate the facility in accordance with the Technical Specifications.

For Surveillance Requirements (SRs) that are new in Amendment 253 to Facility Operating License DPR-52, the first performance is due at the end of the first surveillance interval that begins at implementation of the Amendment 253. For SRs that existed prior to Amendment 253, including SRs with modified acceptance criteria and SRs whose frequency of performance is being extended, the first performance is due at the end of the first surveillance interval that begins on the date the surveillance was last performed prior to implementation of Amendment 253.

3)

The licensee is authorized to relocate certain requirements included in Appendix A and the former Appendix B to licensee-controlled documents.

Implementation of this amendment shall include the relocation of these requirements to the appropriate documents, as described in the licensees

Completion Times 1.3 (continued)

BFN-UNIT 2 1.3-1 Amendment No. 253, 349 1.0 USE AND APPLICATION 1.3 Completion Times PURPOSE The purpose of this section is to establish the Completion Time convention and to provide guidance for its use.

BACKGROUND Limiting Conditions for Operation (LCOs) specify minimum requirements for ensuring safe operation of the unit. The ACTIONS associated with an LCO state Conditions that typically describe the ways in which the requirements of the LCO can fail to be met. Specified with each stated Condition are Required Action(s) and Completion Times(s).

DESCRIPTION The Completion Time is the amount of time allowed for completing a Required Action. It is referenced to the discovery of a situation (e.g.,

inoperable equipment or variable not within limits) that requires entering an ACTIONS Condition unless otherwise specified, providing the unit is in a MODE or specified condition stated in the Applicability of the LCO.

Unless otherwise specified, the Completion Time begins when a senior licensed operator on the operating shift crew with responsibility for plant operations makes the determination that an LCO is not met and an ACTIONS Condition is entered. The "otherwise specified" exceptions are varied, such as a Required Action Note or Surveillance Requirement Note that provides an alternative time to perform specific tasks, such as testing, without starting the Completion Time. While utilizing the Note, should a Condition be applicable for any reason not addressed by the Note, the Completion Time begins. Should the time allowance in the Note be exceeded, the Completion Time begins at that point. The exceptions may also be incorporated into the Completion Time. For example, LCO 3.8.1, "AC Sources - Operating," Required Action B.3, requires declaring required feature(s) supported by an inoperable diesel generator, inoperable when the redundant required feature(s) are inoperable. The Completion Time states, "4 hours4.62963e-5 days <br />0.00111 hours <br />6.613757e-6 weeks <br />1.522e-6 months <br /> from discovery of Condition B concurrent with inoperability of redundant required feature(s)." In this case the Completion Time does not begin until the conditions in the Completion Time are satisfied.

Required Actions must be completed prior to the expiration of the specified Completion Time. An ACTIONS Condition remains in effect and the Required Actions apply until the Condition no longer exists or the unit is not within the LCO Applicability.

Completion Times 1.3 (continued)

BFN-UNIT 2 1.3-2 Amendment No. 253, 349 1.3 Completion Times DESCRIPTION If situations are discovered that require entry into more than one (continued)

Condition at a time within a single LCO (multiple Conditions), the Required Actions for each Condition must be performed within the associated Completion Time. When in multiple Conditions, separate Completion Times are tracked for each Condition starting from the discovery of the situation that required entry into the Condition, unless otherwise specified.

Once a Condition has been entered, subsequent divisions, subsystems, components, or variables expressed in the Condition, discovered to be inoperable or not within limits, will not result in separate entry into the Condition unless specifically stated. The Required Actions of the Condition continue to apply to each additional failure, with Completion Times based on initial entry into the Condition, unless otherwise specified.

However, when a subsequent division, subsystem, component, or variable expressed in the Condition is discovered to be inoperable or not within limits, the Completion Time(s) may be extended. To apply this Completion Time extension, two criteria must first be met. The subsequent inoperability:

a.

Must exist concurrent with the first inoperability; and b.

Must remain inoperable or not within limits after the first inoperability is resolved.

The total Completion Time allowed for completing a Required Action to address the subsequent inoperability shall be limited to the more restrictive of either:

a.

The stated Completion Time, as measured from the initial entry into the Condition, plus an additional 24 hours2.777778e-4 days <br />0.00667 hours <br />3.968254e-5 weeks <br />9.132e-6 months <br />; or b.

The stated Completion Time as measured from discovery of the subsequent inoperability.

The above Completion Time extensions do not apply to those Specifications that have exceptions that allow completely separate re-entry into the Condition (for each division, subsystem, component or variable expressed in the Condition) and separate tracking of Completion Times based on this re-entry. These exceptions are stated in individual Specifications.

LCO Applicability 3.0 (continued)

BFN-UNIT 2 3.0-2 Amendment No. 253, 286, 349 3.0 LCO APPLICABILITY (continued)

LCO 3.0.4 When an LCO is not met, entry into a MODE or other specified condition in the Applicability shall only be made:

a.

When the associated ACTIONS to be entered permit continued operation in the MODE or other specified condition in the Applicability for an unlimited period of time; b.

After performance of a risk assessment addressing inoperable systems and components, consideration of the results, determination of the acceptability of entering the MODE or other specified condition in the Applicability, and establishment of risk management actions, if appropriate (exceptions to this Specification are stated in the individual Specifications); or c.

When an allowance is stated in the individual value, parameter, or other Specification.

This Specification shall not prevent changes in MODES or other specified conditions in the Applicability that are required to comply with ACTIONS or that are part of a shutdown of the unit.

LCO 3.0.5 Equipment removed from service or declared inoperable to comply with ACTIONS may be returned to service under administrative control solely to perform testing required to demonstrate its OPERABILITY or the OPERABILITY of other equipment. This is an exception to LCO 3.0.2 for the system returned to service under administrative control to perform the testing required to demonstrate OPERABILITY.

LCO 3.0.6 When a supported system LCO is not met solely due to a support system LCO not being met, the Conditions and Required Actions associated with this supported system are not required to be entered. Only the support system LCO ACTIONS are required to be entered. This is an exception to LCO 3.0.2 for the supported system. In this event, an evaluation shall be performed in accordance with Specification 5.5.11, "Safety Function Determination Program (SFDP)." If a loss of safety function is

SR Applicability 3.0 (continued)

BFN-UNIT 2 3.0-4 Amendment No. 253, 278, 349 3.0 SURVEILLANCE REQUIREMENT (SR) APPLICABILITY SR 3.0.1 SRs shall be met during the MODES or other specified conditions in the Applicability for individual LCOs, unless otherwise stated in the SR. Failure to meet a Surveillance, whether such failure is experienced during the performance of the Surveillance or between performances of the Surveillance, shall be failure to meet the LCO.

Failure to perform a Surveillance within the specified Frequency shall be failure to meet the LCO except as provided in SR 3.0.3.

Surveillances do not have to be performed on inoperable equipment or variables outside specified limits.

SR 3.0.2 The specified Frequency for each SR is met if the Surveillance is performed within 1.25 times the interval specified in the Frequency, as measured from the previous performance or as measured from the time a specified condition of the Frequency is met.

For Frequencies specified as "once," the above interval extension does not apply. If a Completion Time requires periodic performance on a "once per..." basis, the above Frequency extension applies to each performance after the initial performance.

Exceptions to this Specification are stated in the individual Specifications.

SR 3.0.3 If it is discovered that a Surveillance was not performed within its specified Frequency, then compliance with the requirement to declare the LCO not met may be delayed, from the time of discovery, up to 24 hours2.777778e-4 days <br />0.00667 hours <br />3.968254e-5 weeks <br />9.132e-6 months <br /> or up to the limit of the specified Frequency, whichever is greater. This delay period is permitted to allow performance of the Surveillance. The delay period is only applicable when there is a reasonable expectation the Surveillance will be met when performed. A risk evaluation shall be performed for any Surveillance delayed greater than 24 hours2.777778e-4 days <br />0.00667 hours <br />3.968254e-5 weeks <br />9.132e-6 months <br /> and the risk impact shall be managed.

TENNESSEE VALLEY AUTHORITY DOCKET NO. 50-296 BROWNS FERRY NUCLEAR PLANT, UNIT 3 AMENDMENT TO RENEWED FACILITY OPERATING LICENSE Amendment No. 309 Renewed License No. DPR-68

1.

The U.S. Nuclear Regulatory Commission (the Commission) has found that:

A.

The application for amendment by the Tennessee Valley Authority (the licensee) dated June 13, 2022, complies with the standards and requirements of the Atomic Energy Act of 1954, as amended (the Act), and the Commissions rules and regulations set forth in Title 10 of the Code of Federal Regulations (10 CFR)

Chapter I; B.

The facility will operate in conformity with the application, the provisions of the Act, and the rules and regulations of the Commission; C.

There is reasonable assurance (i) that the activities authorized by this amendment can be conducted without endangering the health and safety of the public, and (ii) that such activities will be conducted in compliance with the Commissions regulations; D.

The issuance of this amendment will not be inimical to the common defense and security or to the health and safety of the public; and E.

The issuance of this amendment is in accordance with 10 CFR Part 51 of the Commissions regulations and all applicable requirements have been satisfied.

2.

Accordingly, the license is amended by changes to the Technical Specifications as indicated in the attachment to this license amendment and paragraph 2.C.(2) of Renewed Facility Operating License No. DPR-68 is hereby amended to read as follows:

(2)

Technical Specifications The Technical Specifications contained in Appendices A and B, as revised through Amendment No. 309, are hereby incorporated in the renewed operating license. The licensee shall operate the facility in accordance with the Technical Specifications.

3.

This license amendment is effective as of its date of issuance and shall be implemented within 60 days from the date of issuance.

FOR THE NUCLEAR REGULATORY COMMISSION David J. Wrona, Chief Plant Licensing Branch II-2 Division of Operating Reactor Licensing Office of Nuclear Reactor Regulation

Attachment:

Changes to the Renewed Facility Operating License and Technical Specifications Date of Issuance: January 20, 2023 David J.

Wrona Digitally signed by David J. Wrona Date: 2023.01.20 14:18:18 -05'00'

ATTACHMENT TO LICENSE AMENDMENT NO. 309 BROWNS FERRY NUCLEAR PLANT, UNIT 3 TO RENEWED FACILITY OPERATING LICENSE NO. DPR-68 DOCKET NO. 50-296 Replace page 3 of Renewed Facility Operating License No. DPR-68 with the attached page 3.

The revised page is identified by amendment number and contains a marginal line indicating the area of change.

Replace the following pages of the Appendix A Technical Specifications with the attached pages. The revised pages are identified by amendment number and contain marginal lines indicating the areas of change.

Remove Insert 1.3-1 1.3-1 1.3-2 1.3-2 3.0-2 3.0-2 3.0-4 3.0-4 BFN-UNIT 3 Renewed License No. DPR-68 Amendment No. 309 (3)

Pursuant to the Act and 10 CFR Parts 30, 40, and 70, to receive, possess, and use at any time any byproduct, source, and special nuclear material as sealed neutron sources for reactor startup, sealed sources for reactor instrumentation and radiation monitoring equipment calibration, and as fission detectors in amounts as required; (4)

Pursuant to the Act and 10 CFR Parts 30, 40, and 70, to receive, possess, and use in amounts as required any byproduct, source, or special nuclear material without restriction to chemical or physical form for sample analysis or equipment and instrument calibration or associated with radioactive apparatus or components; (5)

Pursuant to the Act and 10 CFR Parts 30 and 70, to possess but not separate, such byproduct and special nuclear materials as may be produced by the operation of the facility.

C.

This renewed operating license shall be deemed to contain and is subject to the conditions specified in the following Commission regulations in 10 CFR Chapter I:

Part 20, Section 30.34 of Part 30, Section 40.41 of Part 40, Sections 50.54 and 50.59 of Part 50, and Section 70.32 of Part 70; is subject to all applicable provisions of the Act and to the rules, regulations, and orders of the Commission now or hereafter in effect; and is subject to the additional conditions specified or incorporated below:

(1)

Maximum Power Level The licensee is authorized to operate the facility at steady state reactor core power levels not in excess of 3952 megawatts thermal.

(2)

Technical Specifications The Technical Specifications contained in Appendices A and B, as revised through Amendment No. 309, are hereby incorporated in the renewed operating license. The licensee shall operate the facility in accordance with the Technical Specifications.

For Surveillance Requirements (SRs) that are new in Amendment 212 to Facility Operating License DPR-68, the first performance is due at the end of the first surveillance interval that begins at implementation of the Amendment 212. For SRs that existed prior to Amendment 212, including SRs with modified acceptance criteria and SRs whose frequency of performance is being extended, the first performance is due at the end of the first surveillance interval that begins on the date the surveillance was last performed prior to implementation of Amendment 212.

Completion Times 1.3 (continued)

BFN-UNIT 3 1.3-1 Amendment No. 212, 309 1.0 USE AND APPLICATION 1.3 Completion Times PURPOSE The purpose of this section is to establish the Completion Time convention and to provide guidance for its use.

BACKGROUND Limiting Conditions for Operation (LCOs) specify minimum requirements for ensuring safe operation of the unit. The ACTIONS associated with an LCO state Conditions that typically describe the ways in which the requirements of the LCO can fail to be met. Specified with each stated Condition are Required Action(s) and Completion Times(s).

DESCRIPTION The Completion Time is the amount of time allowed for completing a Required Action. It is referenced to the discovery of a situation (e.g.,

inoperable equipment or variable not within limits) that requires entering an ACTIONS Condition unless otherwise specified, providing the unit is in a MODE or specified condition stated in the Applicability of the LCO.

Unless otherwise specified, the Completion Time begins when a senior licensed operator on the operating shift crew with responsibility for plant operations makes the determination that an LCO is not met and an ACTIONS Condition is entered. The "otherwise specified" exceptions are varied, such as a Required Action Note or Surveillance Requirement Note that provides an alternative time to perform specific tasks, such as testing, without starting the Completion Time. While utilizing the Note, should a Condition be applicable for any reason not addressed by the Note, the Completion Time begins. Should the time allowance in the Note be exceeded, the Completion Time begins at that point. The exceptions may also be incorporated into the Completion Time. For example, LCO 3.8.1, "AC Sources - Operating," Required Action B.3, requires declaring required feature(s) supported by an inoperable diesel generator, inoperable when the redundant required feature(s) are inoperable. The Completion Time states, "4 hours4.62963e-5 days <br />0.00111 hours <br />6.613757e-6 weeks <br />1.522e-6 months <br /> from discovery of Condition B concurrent with inoperability of redundant required feature(s)." In this case the Completion Time does not begin until the conditions in the Completion Time are satisfied.

Required Actions must be completed prior to the expiration of the specified Completion Time. An ACTIONS Condition remains in effect and the Required Actions apply until the Condition no longer exists or the unit is not within the LCO Applicability.

Completion Times 1.3 (continued)

BFN-UNIT 3 1.3-2 Amendment No. 212, 309 1.3 Completion Times DESCRIPTION If situations are discovered that require entry into more than one (continued)

Condition at a time within a single LCO (multiple Conditions), the Required Actions for each Condition must be performed within the associated Completion Time. When in multiple Conditions, separate Completion Times are tracked for each Condition starting from the discovery of the situation that required entry into the Condition, unless otherwise specified.

Once a Condition has been entered, subsequent divisions, subsystems, components, or variables expressed in the Condition, discovered to be inoperable or not within limits, will not result in separate entry into the Condition unless specifically stated. The Required Actions of the Condition continue to apply to each additional failure, with Completion Times based on initial entry into the Condition, unless otherwise specified.

However, when a subsequent division, subsystem, component, or variable expressed in the Condition is discovered to be inoperable or not within limits, the Completion Time(s) may be extended. To apply this Completion Time extension, two criteria must first be met. The subsequent inoperability:

a.

Must exist concurrent with the first inoperability; and b.

Must remain inoperable or not within limits after the first inoperability is resolved.

The total Completion Time allowed for completing a Required Action to address the subsequent inoperability shall be limited to the more restrictive of either:

a.

The stated Completion Time, as measured from the initial entry into the Condition, plus an additional 24 hours2.777778e-4 days <br />0.00667 hours <br />3.968254e-5 weeks <br />9.132e-6 months <br />; or b.

The stated Completion Time as measured from discovery of the subsequent inoperability.

The above Completion Time extensions do not apply to those Specifications that have exceptions that allow completely separate re-entry into the Condition (for each division, subsystem, component or variable expressed in the Condition) and separate tracking of Completion Times based on this re-entry. These exceptions are stated in individual Specifications.

LCO Applicability 3.0 (continued)

BFN-UNIT 3 3.0-2 Amendment No. 212, 244, 309 3.0 LCO APPLICABILITY (continued)

LCO 3.0.4 When an LCO is not met, entry into a MODE or other specified condition in the Applicability shall only be made:

a.

When the associated ACTIONS to be entered permit continued operation in the MODE or other specified condition in the Applicability for an unlimited period of time; b.

After performance of a risk assessment addressing inoperable systems and components, consideration of the results, determination of the acceptability of entering the MODE or other specified condition in the Applicability, and establishment of risk management actions, if appropriate (exceptions to this Specification are stated in the individual Specifications); or c.

When an allowance is stated in the individual value, parameter, or other Specification.

This Specification shall not prevent changes in MODES or other specified conditions in the Applicability that are required to comply with ACTIONS or that are part of a shutdown of the unit.

LCO 3.0.5 Equipment removed from service or declared inoperable to comply with ACTIONS may be returned to service under administrative control solely to perform testing required to demonstrate its OPERABILITY or the OPERABILITY of other equipment. This is an exception to LCO 3.0.2 for the system returned to service under administrative control to perform the testing required to demonstrate OPERABILITY.

LCO 3.0.6 When a supported system LCO is not met solely due to a support system LCO not being met, the Conditions and Required Actions associated with this supported system are not required to be entered. Only the support system LCO ACTIONS are required to be entered. This is an exception to LCO 3.0.2 for the supported system. In this event, an evaluation shall be performed in accordance with Specification 5.5.11, "Safety Function Determination Program (SFDP)." If a loss of safety function is

SR Applicability 3.0 (continued)

BFN-UNIT 3 3.0-4 Amendment No. 212, 237, 309 3.0 SURVEILLANCE REQUIREMENT (SR) APPLICABILITY SR 3.0.1 SRs shall be met during the MODES or other specified conditions in the Applicability for individual LCOs, unless otherwise stated in the SR. Failure to meet a Surveillance, whether such failure is experienced during the performance of the Surveillance or between performances of the Surveillance, shall be failure to meet the LCO.

Failure to perform a Surveillance within the specified Frequency shall be failure to meet the LCO except as provided in SR 3.0.3.

Surveillances do not have to be performed on inoperable equipment or variables outside specified limits.

SR 3.0.2 The specified Frequency for each SR is met if the Surveillance is performed within 1.25 times the interval specified in the Frequency, as measured from the previous performance or as measured from the time a specified condition of the Frequency is met.

For Frequencies specified as "once," the above interval extension does not apply. If a Completion Time requires periodic performance on a "once per..." basis, the above Frequency extension applies to each performance after the initial performance.

Exceptions to this Specification are stated in the individual Specifications.

SR 3.0.3 If it is discovered that a Surveillance was not performed within its specified Frequency, then compliance with the requirement to declare the LCO not met may be delayed, from the time of discovery, up to 24 hours2.777778e-4 days <br />0.00667 hours <br />3.968254e-5 weeks <br />9.132e-6 months <br /> or up to the limit of the specified Frequency, whichever is greater. This delay period is permitted to allow performance of the Surveillance. The delay period is only applicable when there is a reasonable expectation the Surveillance will be met when performed. A risk evaluation shall be performed for any Surveillance delayed greater than 24 hours2.777778e-4 days <br />0.00667 hours <br />3.968254e-5 weeks <br />9.132e-6 months <br /> and the risk impact shall be managed.

TENNESSEE VALLEY AUTHORITY DOCKET NO. 50-327 SEQUOYAH NUCLEAR PLANT, UNIT 1 AMENDMENT TO RENEWED FACILITY OPERATING LICENSE Amendment No. 361 Renewed License No. DPR-77

1.

The U.S. Nuclear Regulatory Commission (the Commission) has found that:

A.

The application for amendment by the Tennessee Valley Authority (the licensee) dated June 13, 2022, complies with the standards and requirements of the Atomic Energy Act of 1954, as amended (the Act), and the Commissions rules and regulations set forth in Title 10 of the Code of Federal Regulations (10 CFR)

Chapter I; B.

The facility will operate in conformity with the application, the provisions of the Act, and the rules and regulations of the Commission; C.

There is reasonable assurance (i) that the activities authorized by this amendment can be conducted without endangering the health and safety of the public, and (ii) that such activities will be conducted in compliance with the Commissions regulations; D.

The issuance of this amendment will not be inimical to the common defense and security or to the health and safety of the public; and E.

The issuance of this amendment is in accordance with 10 CFR Part 51 of the Commissions regulations and all applicable requirements have been satisfied.

2.

Accordingly, the license is amended by changes to the Technical Specifications as indicated in the attachment to this license amendment and paragraph 2.C.(2) of Renewed Facility Operating License No. DPR-77 is hereby amended to read as follows:

(2)

Technical Specifications The Technical Specifications contained in Appendices A and B, as revised through Amendment No. 361, are hereby incorporated in the renewed license. The licensee shall operate the facility in accordance with the Technical Specifications.

3.

This license amendment is effective as of the date of its issuance and shall be implemented within 60 days.

FOR THE NUCLEAR REGULATORY COMMISSION David J. Wrona, Chief Plant Licensing Branch II-2 Division of Licensing Project Management Office of Nuclear Reactor Regulation

Attachment:

Changes to the Renewed Facility Operating License and Technical Specifications Date of Issuance: January 20, 2023 David J.

Wrona Digitally signed by David J. Wrona Date: 2023.01.20 14:18:47 -05'00'

ATTACHMENT TO LICENSE AMENDMENT NO. 361 SEQUOYAH NUCLEAR PLANT, UNIT 1 RENEWED FACILITY OPERATING LICENSE NO. DPR-77 DOCKET NO. 50-327 Replace page 3 of Renewed Facility Operating License No. DPR 77 with the attached page 3.

The revised page is identified by amendment number and contains a marginal line indicating the area of change.

Replace the following pages of the Appendix A Technical Specifications with the attached pages. The revised pages are identified by amendment number and contain marginal lines indicating the areas of change.

Remove Insert 1.3-1 1.3-1 1.3-2 1.3-2 1.3-3 3.0-1 3.0-4 1.3-3 1.3-4 1.3-5 3.0-1 3.0-4 1.3-4 1.3-5 Amendment No. 361 Renewed License No. DPR-77 (3)

Pursuant to the Act and 10 CFR Parts 30, 40 and 70, to receive, possess, and use at any time any byproduct, source and special nuclear material as sealed neutron sources for reactor startup, sealed sources for reactor instrumentation and radiation monitoring equipment calibration, and as fission detectors in amounts as required; (4)

Pursuant to the Act and 10 CFR Parts 30, 40 and 70, to receive, possess, and use in amounts as required any byproduct, source or special nuclear material without restriction to chemical or physical form, for sample analysis or instrument calibration or associated with radioactive apparatus or components; and (5)

Pursuant to the Act and 10 CFR Parts 30, 40 and 70, to possess, but not separate, such byproduct and special nuclear materials as may be produced by the operation of the Sequoyah and Watts Bar Unit 1 Nuclear Plants.

C.

This renewed license shall be deemed to contain and is subject to the conditions specified in the Commissions regulations set forth in 10 CFR Chapter I and is subject to all applicable provisions of the Act and to the rules, regulations, and orders of the Commission now or hereafter in effect; and is subject to the additional conditions specified or incorporated below:

(1)

Maximum Power Level The Tennessee Valley Authority is authorized to operate the facility at reactor core power levels not in excess of 3455 megawatts thermal.

(2)

Technical Specifications The Technical Specifications contained in Appendices A and B, as revised through Amendment No. 361 are hereby incorporated into the renewed license. The licensee shall operate the facility in accordance with the Technical Specifications.

(3)

Initial Test Program The Tennessee Valley Authority shall conduct the post-fuel-loading initial test program (set forth in Section 14 of Tennessee Valley Authoritys Final Safety Analysis Report, as amended), without making any major modifications of this program unless modifications have been identified and have received prior NRC approval. Major modifications are defined as:

a.

Elimination of any test identified in Section 14 of TVAs Final Safety Analysis Report as amended as being essential; b.

Modification of test objectives, methods, or acceptance criteria for any test identified in Section 14 of TVAs Final Safety Analysis Report as amended as being essential;

Completion Times 1.3 SEQUOYAH - UNIT 1 1.3-1 Amendment 334, 361 1.0 USE AND APPLICATION 1.3 Completion Times PURPOSE The purpose of this section is to establish the Completion Time convention and to provide guidance for its use.

BACKGROUND Limiting Conditions for Operation (LCOs) specify minimum requirements for ensuring safe operation of the unit. The ACTIONS associated with an LCO state Conditions that typically describe the ways in which the requirements of the LCO can fail to be met. Specified with each stated Condition are Required Action(s) and Completion Time(s).

DESCRIPTION The Completion Time is the amount of time allowed for completing a Required Action. It is referenced to the discovery of a situation (e.g.,

inoperable equipment or variable not within limits) that requires entering an ACTIONS Condition unless otherwise specified, providing the unit is in a MODE or specified condition stated in the Applicability of the LCO.

Unless otherwise specified, the Completion Time begins when a senior licensed operator on the operating shift crew with responsibility for plant operations makes the determination that an LCO is not met and an ACTIONS Condition is entered. The "otherwise specified" exceptions are varied, such as a Required Action Note or Surveillance Requirement Note that provides an alternative time to perform specific tasks, such as testing, without starting the Completion Time. While utilizing the Note, should a Condition be applicable for any reason not addressed by the Note, the Completion Time begins. Should the time allowance in the Note be exceeded, the Completion Time begins at that point. The exceptions may also be incorporated into the Completion Time. For example, LCO 3.8.1, "AC Sources - Operating," Required Action B.2, requires declaring required feature(s) supported by an inoperable diesel generator, inoperable when the redundant required feature(s) are inoperable. The Completion Time states, "4 hours4.62963e-5 days <br />0.00111 hours <br />6.613757e-6 weeks <br />1.522e-6 months <br /> from discovery of Condition B concurrent with inoperability of redundant required feature(s)." In this case the Completion Time does not begin until the conditions in the Completion Time are satisfied.

Required Actions must be completed prior to the expiration of the specified Completion Time. An ACTIONS Condition remains in effect and the Required Actions apply until the Condition no longer exists or the unit is not within the LCO Applicability.

If situations are discovered that require entry into more than one Condition at a time within a single LCO (multiple Conditions), the Required Actions for each Condition must be performed within the associated Completion Time. When in multiple Conditions, separate Completion Times are tracked for each Condition starting from the discovery of the situation that required entry into the Condition, unless otherwise specified.

Completion Times 1.3 SEQUOYAH - UNIT 1 1.3-2 Amendment 334, 361 1.3 Completion Times DESCRIPTION (continued)

Once a Condition has been entered, subsequent trains, subsystems, components, or variables expressed in the Condition, discovered to be inoperable or not within limits, will not result in separate entry into the Condition, unless specifically stated. The Required Actions of the Condition continue to apply to each additional failure, with Completion Times based on initial entry into the Condition, unless otherwise specified.

However, when a subsequent train, subsystem, component, or variable expressed in the Condition is discovered to be inoperable or not within limits, the Completion Time(s) may be extended. To apply this Completion Time extension, two criteria must first be met. The subsequent inoperability:

a.

Must exist concurrent with the first inoperability and b.

Must remain inoperable or not within limits after the first inoperability is resolved.

The total Completion Time allowed for completing a Required Action to address the subsequent inoperability shall be limited to the more restrictive of either:

a.

The stated Completion Time, as measured from the initial entry into the Condition, plus an additional 24 hours2.777778e-4 days <br />0.00667 hours <br />3.968254e-5 weeks <br />9.132e-6 months <br /> or b.

The stated Completion Time as measured from discovery of the subsequent inoperability.

The above Completion Time extensions do not apply to those Specifications that have exceptions that allow completely separate re-entry into the Condition (for each train, subsystem, component, or variable expressed in the Condition) and separate tracking of Completion Times based on this re-entry. These exceptions are stated in individual Specifications.

The above Completion Time extension does not apply to a Completion Time with a modified "time zero." This modified "time zero" may be expressed as a repetitive time (i.e., "once per 8 hours9.259259e-5 days <br />0.00222 hours <br />1.322751e-5 weeks <br />3.044e-6 months <br />," where the Completion Time is referenced from a previous completion of the Required Action versus the time of Condition entry) or as a time modified by the phrase "from discovery..."

Completion Times 1.3 SEQUOYAH - UNIT 1 1.3-3 Amendment 334, 361 1.3 Completion Times EXAMPLES The following examples illustrate the use of Completion Times with different types of Conditions and changing Conditions.

EXAMPLE 1.3-1 ACTIONS CONDITION REQUIRED ACTION COMPLETION TIME B. Required Action and associated Completion Time not met.

B.1 Be in MODE 3.

AND B.2 Be in MODE 5.

6 hours6.944444e-5 days <br />0.00167 hours <br />9.920635e-6 weeks <br />2.283e-6 months <br /> 36 hours Condition B has two Required Actions. Each Required Action has its own separate Completion Time. Each Completion Time is referenced to the time that Condition B is entered.

The Required Actions of Condition B are to be in MODE 3 within 6 hours6.944444e-5 days <br />0.00167 hours <br />9.920635e-6 weeks <br />2.283e-6 months <br /> AND in MODE 5 within 36 hours4.166667e-4 days <br />0.01 hours <br />5.952381e-5 weeks <br />1.3698e-5 months <br />. A total of 6 hours6.944444e-5 days <br />0.00167 hours <br />9.920635e-6 weeks <br />2.283e-6 months <br /> is allowed for reaching MODE 3 and a total of 36 hours4.166667e-4 days <br />0.01 hours <br />5.952381e-5 weeks <br />1.3698e-5 months <br /> (not 42 hours4.861111e-4 days <br />0.0117 hours <br />6.944444e-5 weeks <br />1.5981e-5 months <br />) is allowed for reaching MODE 5 from the time that Condition B was entered. If MODE 3 is reached within 3 hours3.472222e-5 days <br />8.333333e-4 hours <br />4.960317e-6 weeks <br />1.1415e-6 months <br />, the time allowed for reaching MODE 5 is the next 33 hours3.819444e-4 days <br />0.00917 hours <br />5.456349e-5 weeks <br />1.25565e-5 months <br /> because the total time allowed for reaching MODE 5 is 36 hours4.166667e-4 days <br />0.01 hours <br />5.952381e-5 weeks <br />1.3698e-5 months <br />.

If Condition B is entered while in MODE 3, the time allowed for reaching MODE 5 is the next 36 hours4.166667e-4 days <br />0.01 hours <br />5.952381e-5 weeks <br />1.3698e-5 months <br />.

Completion Times 1.3 SEQUOYAH - UNIT 1 1.3-4 1.3 Completion Times EXAMPLES (continued)

EXAMPLE 1.3-2 ACTIONS CONDITION REQUIRED ACTION COMPLETION TIME A. One pump inoperable.

A.1 Restore pump to OPERABLE status.

7 days B. Required Action and associated Completion Time not met.

B.1 Be in MODE 3.

AND B.2 Be in MODE 5.

6 hours6.944444e-5 days <br />0.00167 hours <br />9.920635e-6 weeks <br />2.283e-6 months <br /> 36 hours When a pump is declared inoperable, Condition A is entered. If the pump is not restored to OPERABLE status within 7 days, Condition B is also entered and the Completion Time clocks for Required Actions B.1 and B.2 start. If the inoperable pump is restored to OPERABLE status after Condition B is entered, Conditions A and B are exited, and therefore, the Required Actions of Condition B may be terminated.

When a second pump is declared inoperable while the first pump is still inoperable, Condition A is not re-entered for the second pump.

LCO 3.0.3 is entered, since the ACTIONS do not include a Condition for more than one inoperable pump. The Completion Time clock for Condition A does not stop after LCO 3.0.3 is entered, but continues to be tracked from the time Condition A was initially entered.

While in LCO 3.0.3, if one of the inoperable pumps is restored to OPERABLE status and the Completion Time for Condition A has not expired, LCO 3.0.3 may be exited and operation continued in accordance with Condition A.

While in LCO 3.0.3, if one of the inoperable pumps is restored to OPERABLE status and the Completion Time for Condition A has expired, LCO 3.0.3 may be exited and operation continued in accordance with Condition B. The Completion Time for Condition B is tracked from the time the Condition A Completion Time expired.

On restoring one of the pumps to OPERABLE status, the Condition A Completion Time is not reset, but continues from the time the first pump Amendment 334, 361

Completion Times 1.3 SEQUOYAH - UNIT 1 1.3-5 1.3 Completion Times EXAMPLES (continued) was declared inoperable. This Completion Time may be extended if the pump restored to OPERABLE status was the first inoperable pump. A 24 hour2.777778e-4 days <br />0.00667 hours <br />3.968254e-5 weeks <br />9.132e-6 months <br /> extension to the stated 7 days is allowed, provided this does not result in the second pump being inoperable for > 7 days.

EXAMPLE 1.3-3 ACTIONS CONDITION REQUIRED ACTION COMPLETION TIME A. One Function X train inoperable.

A.1 Restore Function X train to OPERABLE status.

7 days B. One Function Y train inoperable.

B.1 Restore Function Y train to OPERABLE status.

72 hours8.333333e-4 days <br />0.02 hours <br />1.190476e-4 weeks <br />2.7396e-5 months <br /> C. One Function X train inoperable.

AND One Function Y train inoperable.

C.1 Restore Function X train to OPERABLE status.

OR C.2 Restore Function Y train to OPERABLE status.

72 hours8.333333e-4 days <br />0.02 hours <br />1.190476e-4 weeks <br />2.7396e-5 months <br /> 72 hours When one Function X train and one Function Y train are inoperable, Condition A and Condition B are concurrently applicable. The Completion Times for Condition A and Condition B are tracked separately for each train starting from the time each train was declared inoperable and the Condition was entered. A separate Completion Time is established for Condition C and tracked from the time the second train was declared inoperable (i.e., the time the situation described in Condition C was discovered).

Amendment 334, 361

LCO Applicability 3.0 SEQUOYAH - UNIT 1 3.0-1 Amendment 334, 361 3.0 LIMITING CONDITION FOR OPERATION (LCO) APPLICABILITY LCO 3.0.1 LCOs shall be met during the MODES or other specified conditions in the Applicability, except as provided in LCO 3.0.2, LCO 3.0.7, LCO 3.0.8, and LCO 3.0.9.

LCO 3.0.2 Upon discovery of a failure to meet an LCO, the Required Actions of the associated Conditions shall be met, except as provided in LCO 3.0.5 and LCO 3.0.6.

If the LCO is met or is no longer applicable prior to expiration of the specified Completion Time(s), completion of the Required Action(s) is not required unless otherwise stated.

LCO 3.0.3 When an LCO is not met and the associated ACTIONS are not met, an associated ACTION is not provided, or if directed by the associated ACTIONS, the unit shall be placed in a MODE or other specified condition in which the LCO is not applicable. Action shall be initiated within 1 hour1.157407e-5 days <br />2.777778e-4 hours <br />1.653439e-6 weeks <br />3.805e-7 months <br /> to place the unit, as applicable, in:

a.

MODE 3 within 7 hours8.101852e-5 days <br />0.00194 hours <br />1.157407e-5 weeks <br />2.6635e-6 months <br />; b.

MODE 4 within 13 hours1.50463e-4 days <br />0.00361 hours <br />2.149471e-5 weeks <br />4.9465e-6 months <br />; and c.

MODE 5 within 37 hours4.282407e-4 days <br />0.0103 hours <br />6.117725e-5 weeks <br />1.40785e-5 months <br />.

Exceptions to this Specification are stated in the individual Specifications.

Where corrective measures are completed that permit operation in accordance with the LCO or ACTIONS, completion of the actions required by LCO 3.0.3 is not required.

LCO 3.0.3 is only applicable in MODES 1, 2, 3, and 4.

LCO 3.0.4 When an LCO is not met, entry into a MODE or other specified condition in the Applicability shall only be made:

a.

When the associated ACTIONS to be entered permit continued operation in the MODE or other specified condition in the Applicability for an unlimited period of time; b.

After performance of a risk assessment addressing inoperable systems and components, consideration of the results, determination of the acceptability of entering the MODE or other specified condition in the Applicability, and establishment of risk management actions, if appropriate (exceptions to this Specification are stated in the individual Specifications); or

SR Applicability 3.0 SEQUOYAH - UNIT 1 3.0-4 Amendment 334, 361 3.0 SURVEILLANCE REQUIREMENT (SR) APPLICABILITY SR 3.0.1 SRs shall be met during the MODES or other specified conditions in the Applicability for individual LCOs, unless otherwise stated in the SR.

Failure to meet a Surveillance, whether such failure is experienced during the performance of the Surveillance or between performances of the Surveillance, shall be failure to meet the LCO. Failure to perform a Surveillance within the specified Frequency shall be failure to meet the LCO except as provided in SR 3.0.3. Surveillances do not have to be performed on inoperable equipment or variables outside specified limits.

SR 3.0.2 The specified Frequency for each SR is met if the Surveillance is performed within 1.25 times the interval specified in the Frequency, as measured from the previous performance or as measured from the time a specified condition of the Frequency is met.

For Frequencies specified as "once," the above interval extension does not apply.

If a Completion Time requires periodic performance on a "once per..."

basis, the above Frequency extension applies to each performance after the initial performance.

Exceptions to this Specification are stated in the individual Specifications.

SR 3.0.3 If it is discovered that a Surveillance was not performed within its specified Frequency, then compliance with the requirement to declare the LCO not met may be delayed, from the time of discovery, up to 24 hours2.777778e-4 days <br />0.00667 hours <br />3.968254e-5 weeks <br />9.132e-6 months <br /> or up to the limit of the specified Frequency, whichever is greater. This delay period is permitted to allow performance of the Surveillance. The delay period is only applicable when there is a reasonable expectation the surveillance will be met when performed. A risk evaluation shall be performed for any Surveillance delayed greater than 24 hours2.777778e-4 days <br />0.00667 hours <br />3.968254e-5 weeks <br />9.132e-6 months <br /> and the risk impact shall be managed.

If the Surveillance is not performed within the delay period, the LCO must immediately be declared not met, and the applicable Condition(s) must be entered.

When the Surveillance is performed within the delay period and the Surveillance is not met, the LCO must immediately be declared not met, and the applicable Condition(s) must be entered.

SR 3.0.4 Entry into a MODE or other specified condition in the Applicability of an LCO shall only be made when the LCO's Surveillances have been met within their specified Frequency, except as provided by SR 3.0.3. When an LCO is not met due to Surveillances not having been met, entry into a MODE or other specified condition in the Applicability shall only be made in accordance with LCO 3.0.4.

TENNESSEE VALLEY AUTHORITY DOCKET NO. 50-328 SEQUOYAH NUCLEAR PLANT, UNIT 2 AMENDMENT TO RENEWED FACILITY OPERATING LICENSE Amendment No. 355 Renewed License No. DPR-79 1.

The U.S. Nuclear Regulatory Commission (the Commission) has found that:

A.

The application for amendment by the Tennessee Valley Authority (the licensee) dated June 13, 2022, complies with the standards and requirements of the Atomic Energy Act of 1954, as amended (the Act), and the Commissions rules and regulations set forth in Title 10 of the Code of Federal Regulations (10 CFR)

Chapter I; B.

The facility will operate in conformity with the application, the provisions of the Act, and the rules and regulations of the Commission; C.

There is reasonable assurance (i) that the activities authorized by this amendment can be conducted without endangering the health and safety of the public, and (ii) that such activities will be conducted in compliance with the Commissions regulations; D.

The issuance of this amendment will not be inimical to the common defense and security or to the health and safety of the public; and E.

The issuance of this amendment is in accordance with 10 CFR Part 51 of the Commissions regulations and all applicable requirements have been satisfied.

2.

Accordingly, the license is amended by changes to the Technical Specifications as indicated in the attachment to this license amendment and paragraph 2.C.(2) of Renewed Facility Operating License No. DPR-79 is hereby amended to read as follows:

(2)

Technical Specifications The Technical Specifications contained in Appendices A and B, as revised through Amendment No. 355, are hereby incorporated in the renewed license. The licensee shall operate the facility in accordance with the Technical Specifications.

3.

This license amendment is effective as of the date of its issuance and shall be implemented within 60 days.

FOR THE NUCLEAR REGULATORY COMMISSION David J. Wrona, Chief Plant Licensing Branch II-2 Division of Licensing Project Management Office of Nuclear Reactor Regulation

Attachment:

Changes to the Renewed Facility Operating License and Technical Specifications Date of Issuance: January 20, 2023 David J.

Wrona Digitally signed by David J. Wrona Date: 2023.01.20 14:19:18 -05'00'

ATTACHMENT TO LICENSE AMENDMENT NO. 355 SEQUOYAH NUCLEAR PLANT, UNIT 2 RENEWED FACILITY OPERATING LICENSE NO. DPR-79 DOCKET NO. 50-328 Replace page 3 of Renewed Facility Operating License No. DPR 79 with the attached page 3.

The revised page is identified by amendment number and contains a marginal line indicating the area of change.

Replace the following pages of the Appendix A Technical Specifications with the attached pages. The revised pages are identified by amendment number and contain marginal lines indicating the areas of change.

Remove Insert 1.3-1 1.3-1 1.3-2 1.3-2 1.3-3 3.0-1 3.0-4 1.3-3 1.3-4 1.3-5 3.0-1 3.0-4 1.3-4 1.3-5 Amendment No. 355 Renewed License No. DPR-79 (3)

Pursuant to the Act and 10 CFR Parts 30, 40 and 70, to receive, possess, and use at any time any byproduct, source and special nuclear material as sealed neutron sources for reactor startup, sealed sources for reactor instrumentation and radiation monitoring equipment calibration, and as fission detectors in amounts as required; (4)

Pursuant to the Act and 10 CFR Parts 30, 40 and 70, to receive, possess, and use in amounts as required any byproduct, source or special nuclear material without restriction to chemical or physical form, for sample analysis or instrument calibration or associated with radioactive apparatus or components; and (5)

Pursuant to the Act and 10 CFR Parts 30, 40 and 70, to possess, but not separate, such byproduct and special nuclear materials as may be produced by the operation of the Sequoyah and Watts Bar Unit 1 Nuclear Plants.

C.

This renewed license shall be deemed to contain and is subject to the conditions specified in the Commissions regulations set forth in 10 CFR Chapter I and is subject to all applicable provisions of the Act and to the rules, regulations, and orders of the Commission now or hereafter in effect; and is subject to the additional conditions specified or incorporated below:

(1)

Maximum Power Level The Tennessee Valley Authority is authorized to operate the facility at reactor core power levels not in excess of 3455 megawatts thermal.

(2)

Technical Specifications The Technical Specifications contained in Appendices A and B, as revised through Amendment No. 355 are hereby incorporated into the renewed license. The licensee shall operate the facility in accordance with the Technical Specifications.

(3)

Initial Test Program The Tennessee Valley Authority shall conduct the post-fuel-loading initial test program (set forth in Section 14 of Tennessee Valley Authoritys Final Safety Analysis Report, as amended), without making any major modifications of this program unless modifications have been identified and have received prior NRC approval. Major modifications are defined as:

a.

Elimination of any test identified in Section 14 of TVAs Final Safety Analysis Report as amended as being essential;

Completion Times 1.3 SEQUOYAH - UNIT 2 1.3-1 Amendment 327, 355 1.0 USE AND APPLICATION 1.3 Completion Times PURPOSE The purpose of this section is to establish the Completion Time convention and to provide guidance for its use.

BACKGROUND Limiting Conditions for Operation (LCOs) specify minimum requirements for ensuring safe operation of the unit. The ACTIONS associated with an LCO state Conditions that typically describe the ways in which the requirements of the LCO can fail to be met. Specified with each stated Condition are Required Action(s) and Completion Time(s).

DESCRIPTION The Completion Time is the amount of time allowed for completing a Required Action. It is referenced to the discovery of a situation (e.g.,

inoperable equipment or variable not within limits) that requires entering an ACTIONS Condition unless otherwise specified, providing the unit is in a MODE or specified condition stated in the Applicability of the LCO.

Unless otherwise specified, the Completion Time begins when a senior licensed operator on the operating shift crew with responsibility for plant operations makes the determination that an LCO is not met and an ACTIONS Condition is entered. The "otherwise specified" exceptions are varied, such as a Required Action Note or Surveillance Requirement Note that provides an alternative time to perform specific tasks, such as testing, without starting the Completion Time. While utilizing the Note, should a Condition be applicable for any reason not addressed by the Note, the Completion Time begins. Should the time allowance in the Note be exceeded, the Completion Time begins at that point. The exceptions may also be incorporated into the Completion Time. For example, LCO 3.8.1, "AC Sources - Operating," Required Action B.2, requires declaring required feature(s) supported by an inoperable diesel generator, inoperable when the redundant required feature(s) are inoperable. The Completion Time states, "4 hours4.62963e-5 days <br />0.00111 hours <br />6.613757e-6 weeks <br />1.522e-6 months <br /> from discovery of Condition B concurrent with inoperability of redundant required feature(s)." In this case the Completion Time does not begin until the conditions in the Completion Time are satisfied.

Required Actions must be completed prior to the expiration of the specified Completion Time. An ACTIONS Condition remains in effect and the Required Actions apply until the Condition no longer exists or the unit is not within the LCO Applicability.

If situations are discovered that require entry into more than one Condition at a time within a single LCO (multiple Conditions), the Required Actions for each Condition must be performed within the associated Completion Time. When in multiple Conditions, separate Completion Times are tracked for each Condition starting from the discovery of the situation that required entry into the Condition, unless otherwise specified.

Completion Times 1.3 SEQUOYAH - UNIT 2 1.3-2 Amendment 327, 355 1.3 Completion Times DESCRIPTION (continued)

Once a Condition has been entered, subsequent trains, subsystems, components, or variables expressed in the Condition, discovered to be inoperable or not within limits, will not result in separate entry into the Condition, unless specifically stated. The Required Actions of the Condition continue to apply to each additional failure, with Completion Times based on initial entry into the Condition, unless otherwise specified.

However, when a subsequent train, subsystem, component, or variable expressed in the Condition is discovered to be inoperable or not within limits, the Completion Time(s) may be extended. To apply this Completion Time extension, two criteria must first be met. The subsequent inoperability:

a.

Must exist concurrent with the first inoperability and b.

Must remain inoperable or not within limits after the first inoperability is resolved.

The total Completion Time allowed for completing a Required Action to address the subsequent inoperability shall be limited to the more restrictive of either:

a.

The stated Completion Time, as measured from the initial entry into the Condition, plus an additional 24 hours2.777778e-4 days <br />0.00667 hours <br />3.968254e-5 weeks <br />9.132e-6 months <br /> or b.

The stated Completion Time as measured from discovery of the subsequent inoperability.

The above Completion Time extensions do not apply to those Specifications that have exceptions that allow completely separate re-entry into the Condition (for each train, subsystem, component, or variable expressed in the Condition) and separate tracking of Completion Times based on this re-entry. These exceptions are stated in individual Specifications.

The above Completion Time extension does not apply to a Completion Time with a modified "time zero." This modified "time zero" may be expressed as a repetitive time (i.e., "once per 8 hours9.259259e-5 days <br />0.00222 hours <br />1.322751e-5 weeks <br />3.044e-6 months <br />," where the Completion Time is referenced from a previous completion of the Required Action versus the time of Condition entry) or as a time modified by the phrase "from discovery..."

Completion Times 1.3 SEQUOYAH - UNIT 2 1.3-3 Amendment 327, 355 1.3 Completion Times EXAMPLES The following examples illustrate the use of Completion Times with different types of Conditions and changing Conditions.

EXAMPLE 1.3-1 ACTIONS CONDITION REQUIRED ACTION COMPLETION TIME B. Required Action and associated Completion Time not met.

B.1 Be in MODE 3.

AND B.2 Be in MODE 5.

6 hours6.944444e-5 days <br />0.00167 hours <br />9.920635e-6 weeks <br />2.283e-6 months <br /> 36 hours Condition B has two Required Actions. Each Required Action has its own separate Completion Time. Each Completion Time is referenced to the time that Condition B is entered.

The Required Actions of Condition B are to be in MODE 3 within 6 hours6.944444e-5 days <br />0.00167 hours <br />9.920635e-6 weeks <br />2.283e-6 months <br /> AND in MODE 5 within 36 hours4.166667e-4 days <br />0.01 hours <br />5.952381e-5 weeks <br />1.3698e-5 months <br />. A total of 6 hours6.944444e-5 days <br />0.00167 hours <br />9.920635e-6 weeks <br />2.283e-6 months <br /> is allowed for reaching MODE 3 and a total of 36 hours4.166667e-4 days <br />0.01 hours <br />5.952381e-5 weeks <br />1.3698e-5 months <br /> (not 42 hours4.861111e-4 days <br />0.0117 hours <br />6.944444e-5 weeks <br />1.5981e-5 months <br />) is allowed for reaching MODE 5 from the time that Condition B was entered. If MODE 3 is reached within 3 hours3.472222e-5 days <br />8.333333e-4 hours <br />4.960317e-6 weeks <br />1.1415e-6 months <br />, the time allowed for reaching MODE 5 is the next 33 hours3.819444e-4 days <br />0.00917 hours <br />5.456349e-5 weeks <br />1.25565e-5 months <br /> because the total time allowed for reaching MODE 5 is 36 hours4.166667e-4 days <br />0.01 hours <br />5.952381e-5 weeks <br />1.3698e-5 months <br />.

If Condition B is entered while in MODE 3, the time allowed for reaching MODE 5 is the next 36 hours4.166667e-4 days <br />0.01 hours <br />5.952381e-5 weeks <br />1.3698e-5 months <br />.

Completion Times 1.3 SEQUOYAH - UNIT 2 1.3-4 1.3 Completion Times EXAMPLES (continued)

EXAMPLE 1.3-2 ACTIONS CONDITION REQUIRED ACTION COMPLETION TIME A. One pump inoperable.

A.1 Restore pump to OPERABLE status.

7 days B. Required Action and associated Completion Time not met.

B.1 Be in MODE 3.

AND B.2 Be in MODE 5.

6 hours6.944444e-5 days <br />0.00167 hours <br />9.920635e-6 weeks <br />2.283e-6 months <br /> 36 hours When a pump is declared inoperable, Condition A is entered. If the pump is not restored to OPERABLE status within 7 days, Condition B is also entered and the Completion Time clocks for Required Actions B.1 and B.2 start. If the inoperable pump is restored to OPERABLE status after Condition B is entered, Conditions A and B are exited, and therefore, the Required Actions of Condition B may be terminated.

When a second pump is declared inoperable while the first pump is still inoperable, Condition A is not re-entered for the second pump.

LCO 3.0.3 is entered, since the ACTIONS do not include a Condition for more than one inoperable pump. The Completion Time clock for Condition A does not stop after LCO 3.0.3 is entered, but continues to be tracked from the time Condition A was initially entered.

While in LCO 3.0.3, if one of the inoperable pumps is restored to OPERABLE status and the Completion Time for Condition A has not expired, LCO 3.0.3 may be exited and operation continued in accordance with Condition A.

While in LCO 3.0.3, if one of the inoperable pumps is restored to OPERABLE status and the Completion Time for Condition A has expired, LCO 3.0.3 may be exited and operation continued in accordance with Condition B. The Completion Time for Condition B is tracked from the time the Condition A Completion Time expired.

On restoring one of the pumps to OPERABLE status, the Condition A Completion Time is not reset, but continues from the time the first pump Amendment 327, 355

Completion Times 1.3 SEQUOYAH - UNIT 2 1.3-5 1.3 Completion Times EXAMPLES (continued) was declared inoperable. This Completion Time may be extended if the pump restored to OPERABLE status was the first inoperable pump. A 24 hour2.777778e-4 days <br />0.00667 hours <br />3.968254e-5 weeks <br />9.132e-6 months <br /> extension to the stated 7 days is allowed, provided this does not result in the second pump being inoperable for > 7 days.

EXAMPLE 1.3-3 ACTIONS CONDITION REQUIRED ACTION COMPLETION TIME A. One Function X train inoperable.

A.1 Restore Function X train to OPERABLE status.

7 days B. One Function Y train inoperable.

B.1 Restore Function Y train to OPERABLE status.

72 hours8.333333e-4 days <br />0.02 hours <br />1.190476e-4 weeks <br />2.7396e-5 months <br /> C. One Function X train inoperable.

AND One Function Y train inoperable.

C.1 Restore Function X train to OPERABLE status.

OR C.2 Restore Function Y train to OPERABLE status.

72 hours8.333333e-4 days <br />0.02 hours <br />1.190476e-4 weeks <br />2.7396e-5 months <br /> 72 hours When one Function X train and one Function Y train are inoperable, Condition A and Condition B are concurrently applicable. The Completion Times for Condition A and Condition B are tracked separately for each train starting from the time each train was declared inoperable and the Condition was entered. A separate Completion Time is established for Condition C and tracked from the time the second train was declared inoperable (i.e., the time the situation described in Condition C was discovered).

Amendment 327, 355

LCO Applicability 3.0 SEQUOYAH - UNIT 2 3.0-1 Amendment 327, 355 3.0 LIMITING CONDITION FOR OPERATION (LCO) APPLICABILITY LCO 3.0.1 LCOs shall be met during the MODES or other specified conditions in the Applicability, except as provided in LCO 3.0.2, LCO 3.0.7, LCO 3.0.8, and LCO 3.0.9.

LCO 3.0.2 Upon discovery of a failure to meet an LCO, the Required Actions of the associated Conditions shall be met, except as provided in LCO 3.0.5 and LCO 3.0.6.

If the LCO is met or is no longer applicable prior to expiration of the specified Completion Time(s), completion of the Required Action(s) is not required unless otherwise stated.

LCO 3.0.3 When an LCO is not met and the associated ACTIONS are not met, an associated ACTION is not provided, or if directed by the associated ACTIONS, the unit shall be placed in a MODE or other specified condition in which the LCO is not applicable. Action shall be initiated within 1 hour1.157407e-5 days <br />2.777778e-4 hours <br />1.653439e-6 weeks <br />3.805e-7 months <br /> to place the unit, as applicable, in:

a.

MODE 3 within 7 hours8.101852e-5 days <br />0.00194 hours <br />1.157407e-5 weeks <br />2.6635e-6 months <br />; b.

MODE 4 within 13 hours1.50463e-4 days <br />0.00361 hours <br />2.149471e-5 weeks <br />4.9465e-6 months <br />; and c.

MODE 5 within 37 hours4.282407e-4 days <br />0.0103 hours <br />6.117725e-5 weeks <br />1.40785e-5 months <br />.

Exceptions to this Specification are stated in the individual Specifications.

Where corrective measures are completed that permit operation in accordance with the LCO or ACTIONS, completion of the actions required by LCO 3.0.3 is not required.

LCO 3.0.3 is only applicable in MODES 1, 2, 3, and 4.

LCO 3.0.4 When an LCO is not met, entry into a MODE or other specified condition in the Applicability shall only be made:

a.

When the associated ACTIONS to be entered permit continued operation in the MODE or other specified condition in the Applicability for an unlimited period of time; b.

After performance of a risk assessment addressing inoperable systems and components, consideration of the results, determination of the acceptability of entering the MODE or other specified condition in the Applicability, and establishment of risk management actions, if appropriate (exceptions to this Specification are stated in the individual Specifications); or

SR Applicability 3.0 SEQUOYAH - UNIT 2 3.0-4 Amendment 327, 355 3.0 SURVEILLANCE REQUIREMENT (SR) APPLICABILITY SR 3.0.1 SRs shall be met during the MODES or other specified conditions in the Applicability for individual LCOs, unless otherwise stated in the SR.

Failure to meet a Surveillance, whether such failure is experienced during the performance of the Surveillance or between performances of the Surveillance, shall be failure to meet the LCO. Failure to perform a Surveillance within the specified Frequency shall be failure to meet the LCO except as provided in SR 3.0.3. Surveillances do not have to be performed on inoperable equipment or variables outside specified limits.

SR 3.0.2 The specified Frequency for each SR is met if the Surveillance is performed within 1.25 times the interval specified in the Frequency, as measured from the previous performance or as measured from the time a specified condition of the Frequency is met.

For Frequencies specified as "once," the above interval extension does not apply.

If a Completion Time requires periodic performance on a "once per..."

basis, the above Frequency extension applies to each performance after the initial performance.

Exceptions to this Specification are stated in the individual Specifications.

SR 3.0.3 If it is discovered that a Surveillance was not performed within its specified Frequency, then compliance with the requirement to declare the LCO not met may be delayed, from the time of discovery, up to 24 hours2.777778e-4 days <br />0.00667 hours <br />3.968254e-5 weeks <br />9.132e-6 months <br /> or up to the limit of the specified Frequency, whichever is greater. This delay period is permitted to allow performance of the Surveillance. The delay period is only applicable when there is a reasonable expectation the surveillance will be met when performed. A risk evaluation shall be performed for any Surveillance delayed greater than 24 hours2.777778e-4 days <br />0.00667 hours <br />3.968254e-5 weeks <br />9.132e-6 months <br /> and the risk impact shall be managed.

If the Surveillance is not performed within the delay period, the LCO must immediately be declared not met, and the applicable Condition(s) must be entered.

When the Surveillance is performed within the delay period and the Surveillance is not met, the LCO must immediately be declared not met, and the applicable Condition(s) must be entered.

SR 3.0.4 Entry into a MODE or other specified condition in the Applicability of an LCO shall only be made when the LCO's Surveillances have been met within their specified Frequency, except as provided by SR 3.0.3. When an LCO is not met due to Surveillances not having been met, entry into a MODE or other specified condition in the Applicability shall only be made in accordance with LCO 3.0.4.

TENNESSEE VALLEY AUTHORITY DOCKET NO. 50-390 WATTS BAR NUCLEAR PLANT, UNIT 1 AMENDMENT TO FACILITY OPERATING LICENSE Amendment No. 158 License No. NPF-90

1.

The U.S. Nuclear Regulatory Commission (the Commission) has found that:

A.

The application for amendment by the Tennessee Valley Authority (TVA) dated June 13, 2022, complies with the standards and requirements of the Atomic Energy Act of 1954, as amended (the Act), and the Commissions rules and regulations set forth in Title 10 of the Code of Federal Regulations (10 CFR)

Chapter I; B.

The facility will operate in conformity with the application, the provisions of the Act, and the rules and regulations of the Commission; C.

There is reasonable assurance (i) that the activities authorized by this amendment can be conducted without endangering the health and safety of the public, and (ii) that such activities will be conducted in compliance with the Commissions regulations; D.

The issuance of this amendment will not be inimical to the common defense and security or to the health and safety of the public; and E.

The issuance of this amendment is in accordance with 10 CFR Part 51 of the Commissions regulations and all applicable requirements have been satisfied.

2.

Accordingly, the license is amended by changes to the Technical Specifications as indicated in the attachment to this license amendment, and paragraph 2.C.(2) of Facility Operating License No. NPF-90 is hereby amended to read as follows:

(2)

Technical Specifications and Environmental Protection Plan The Technical Specifications contained in Appendix A as revised through Amendment No. 158 and the Environmental Protection Plan contained in Appendix B, both of which are attached hereto, are hereby incorporated into this license. TVA shall operate the facility in accordance with the Technical Specifications and the Environmental Protection Plan.

3.

This license amendment is effective as of the date of its issuance and shall be implemented within 60 days.

FOR THE NUCLEAR REGULATORY COMMISSION David J. Wrona, Chief Plant Licensing Branch II-2 Division of operating Reactor Licensing Office of Nuclear Reactor Regulation

Attachment:

Changes to the Facility Operating License and Technical Specifications Date of Issuance: January 20, 2023 David J.

Wrona Digitally signed by David J. Wrona Date: 2023.01.20 14:19:49 -05'00'

ATTACHMENT TO AMENDMENT NO. 158 WATTS BAR NUCLEAR PLANT, UNIT 1 FACILITY OPERATING LICENSE NO. NPF-90 DOCKET NO. 50-390 Replace page 3 of Renewed Facility Operating License No. NPF 90 with the attached page 3.

The revised page is identified by amendment number and contains a marginal line indicating the area of change.

Replace the following pages of the Appendix A Technical Specifications with the attached pages. The revised pages are identified by amendment number and contain marginal lines indicating the areas of change.

Remove Insert 1.3-1 1.3-1 1.3-2 1.3-2 3.0-2 3.0-2 3.0-4 3.0-4 Facility License No. NPF-90 Amendment No. 158 (4)

TVA, pursuant to the Act and 10 CFR Parts 30, 40 and 70, to receive, possess, and use in amounts as required, any byproduct, source or special nuclear material without restriction to chemical or physical form, for sample analysis, instrument calibration, or other activity associated with radioactive apparatus or components; and (5)

TVA, pursuant to the Act and 10 CFR Parts 30, 40 and 70, to possess, but not separate, such byproduct and special nuclear materials as may be produced by the operation of the facility.

C.

This license shall be deemed to contain and is subject to the conditions specified in the Commissions regulations set forth in 10 CFR Chapter I and is subject to all applicable provisions of the Act and to the rules, regulations, and orders of the Commission now or hereafter in effect, and is subject to the additional conditions specified or incorporated below.

(1)

Maximum Power Level TVA is authorized to operate the facility at reactor core power levels not in excess of 3459 megawatts thermal.

(2)

Technical Specifications and Environmental Protection Plan The Technical Specifications contained in Appendix A as revised through Amendment No. 158 and the Environmental Protection Plan contained in Appendix B, both of which are attached hereto, are hereby incorporated into this license. TVA shall operate the facility in accordance with the Technical Specifications and the Environmental Protection Plan.

(3)

Safety Parameter Display System (SPDS) (Section 18.2 of SER Supplements 5 and 15)

Prior to startup following the first refueling outage, TVA shall accomplish the necessary activities, provide acceptable responses, and implement all proposed corrective actions related to having the Watts Bar Unit 1 SPDS operational.

(4)

Vehicle Bomb Control Program (Section 13.6.9 of SSER 20)

During the period of the exemption granted in paragraph 2.D.(3) of this license, in implementing the power ascension phase of the approved initial test program, TVA shall not exceed 50% power until the requirements of 10 CFR 73.55(c)(7) and (8) are fully implemented. TVA shall submit a letter under oath or affirmation when the requirements of 73.55(c)(7) and (8) have been fully implemented.

Completion Times 1.3 1.3 Completion Times (continued)

Watts Bar-Unit 1 1.3-1 1.0 USE AND APPLICATION 1.3 Completion Times PURPOSE The purpose of this section is to establish the Completion Time convention and to provide guidance for its use.

BACKGROUND Limiting Conditions for Operation (LCOs) specify minimum requirements for ensuring safe operation of the unit. The ACTIONS associated with an LCO state Conditions that typically describe the ways in which the requirements of the LCO can fail to be met. Specified with each stated Condition are Required Action(s) and Completion Time(s).

DESCRIPTION The Completion Time is the amount of time allowed for completing a Required Action. It is referenced to the discovery of a situation (e.g., inoperable equipment or variable not within limits) that requires entering an ACTIONS Condition unless otherwise specified, providing the unit is in a MODE or specified condition stated in the Applicability of the LCO.

Unless otherwise specified, the Completion Time begins when a senior licensed operator on the operating shift crew with responsibility for plant operations makes the determination that an LCO is not met and an ACTIONS Condition is entered.

The "otherwise specified" exceptions are varied, such as a Required Action Note or Surveillance Requirement Note that provides an alternative time to perform specific tasks, such as testing, without starting the Completion Time. While utilizing the Note, should a Condition be applicable for any reason not addressed by the Note, the Completion Time begins. Should the time allowance in the Note be exceeded, the Completion Time begins at that point. The exceptions may also be incorporated into the Completion Time. For example, LCO 3.8.1, "AC Sources - Operating," Required Action B.3, requires declaring required feature(s) supported by an inoperable diesel generator, inoperable when the redundant required feature(s) are inoperable. The Completion Time states, "4 hours4.62963e-5 days <br />0.00111 hours <br />6.613757e-6 weeks <br />1.522e-6 months <br /> from discovery of Condition B concurrent with inoperability of redundant required feature(s)." In this case the Completion Time does not begin until the conditions in the Completion Time are satisfied.

Required Actions must be completed prior to the expiration of the specified Completion Time. An ACTIONS Condition remains in effect and the Required Actions apply until the Condition no longer exists or the unit is not within the LCO Applicability.

If situations are discovered that require entry into more than one Condition at a time within a single LCO (multiple Conditions), the Required Actions for each Amendment 158

Completion Times 1.3 1.3 Completion Times (continued)

Watts Bar-Unit 1 1.3-2 DESCRIPTION Condition must be performed within the associated Completion Time. When in (continued) multiple Conditions, separate Completion Times are tracked for each Condition starting from the discovery of the situation that required entry into the Condition, unless otherwise specified.

Once a Condition has been entered, subsequent trains, subsystems, components, or variables expressed in the Condition, discovered to be inoperable or not within limits, will not result in separate entry into the Condition, unless specifically stated. The Required Actions of the Condition continue to apply to each additional failure, with Completion Times based on initial entry into the Condition, unless otherwise specified.

However, when a subsequent train, subsystem, component, or variable expressed in the Condition is discovered to be inoperable or not within limits, the Completion Time(s) may be extended. To apply this Completion Time extension, two criteria must first be met. The subsequent inoperability:

a.

Must exist concurrent with the first inoperability; and b.

Must remain inoperable or not within limits after the first inoperability is resolved.

The total Completion Time allowed for completing a Required Action to address the subsequent inoperability shall be limited to the more restrictive of either:

a.

The stated Completion Time, as measured from the initial entry into the Condition, plus an additional 24 hours2.777778e-4 days <br />0.00667 hours <br />3.968254e-5 weeks <br />9.132e-6 months <br />; or b.

The stated Completion Time as measured from discovery of the subsequent inoperability.

The above Completion Time extensions do not apply to those Specifications that have exceptions that allow completely separate re-entry into the Condition (for each train, subsystem, component, or variable expressed in the Condition) and separate tracking of Completion Times based on this re-entry. These exceptions are stated in individual Specifications.

The above Completion Time extension does not apply to a Completion Time with a modified "time zero." This modified "time zero" may be expressed as a repetitive time (i.e., "once per 8 hours9.259259e-5 days <br />0.00222 hours <br />1.322751e-5 weeks <br />3.044e-6 months <br />," where the Completion Time is referenced from a previous completion of the Required Action versus the time of Condition entry) or as a time modified by the phrase "from discovery..." Example 1.3-3 illustrates one use of this type of Completion Time. The 10 day Completion Time specified for Conditions A and B in Example 1.3-3 may not be extended.

Amendment 158

LCO Applicability 3.0 (continued)

Watts Bar-Unit 1 3.0-2 Amendment 55, 158 3.0 LCO APPLICABILITY LCO 3.0.4 (continued) b.

After performance of a risk assessment addressing inoperable systems and components, consideration of the results, determination of the acceptability of entering the MODE or other specified condition in the Applicability, and establishment of risk management actions, if appropriate (exceptions to this Specification are stated in the individual Specifications); or c.

When an allowance is stated in the individual value, parameter, or other Specification.

This Specification shall not prevent changes in MODES or other specified conditions in the Applicability that are required to comply with ACTIONS or that are part of a shutdown of the unit.

LCO 3.0.5 Equipment removed from service or declared inoperable to comply with ACTIONS may be returned to service under administrative control solely to perform testing required to demonstrate its OPERABILITY or the OPERABILITY of other equipment. This is an exception to LCO 3.0.2 for the system returned to service under administrative control to perform the testing required to demonstrate OPERABILITY.

LCO 3.0.6 When a supported system LCO is not met solely due to a support system LCO not being met, the Conditions and Required Actions associated with this supported system are not required to be entered. Only the support system LCO ACTIONS are required to be entered. This is an exception to LCO 3.0.2 for the supported system. In this event, additional evaluations and limitations may be required in accordance with Specification 5.7.2.18, "Safety Function Determination Program (SFDP)." If a loss of safety function is determined to exist by this program, the appropriate Conditions and Required Actions of the LCO in which the loss of safety function exists are required to be entered.

SR Applicability 3.0 (continued)

Watts Bar-Unit 1 3.0-4 Amendment 42, 114, 121, 135, 158 3.0 SURVEILLANCE REQUIREMENT (SR) APPLICABILITY SR 3.0.1 SRs shall be met during the MODES or other specified conditions in the Applicability for individual LCOs, unless otherwise stated in the SR. Failure to meet a Surveillance, whether such failure is experienced during the performance of the Surveillance or between performances of the Surveillance, shall be failure to meet the LCO. Failure to perform a Surveillance within the specified Frequency shall be failure to meet the LCO except as provided in SR 3.0.3.

Surveillances do not have to be performed on inoperable equipment or variables outside specified limits.

SR 3.0.2 The specified Frequency for each SR is met if the Surveillance is performed within 1.25 times the interval specified in the Frequency, as measured from the previous performance or as measured from the time a specified condition of the Frequency is met.

For Frequencies specified as "once," the above interval extension does not apply.

If a Completion Time requires periodic performance on a "once per..." basis, the above Frequency extension applies to each performance after the initial performance.

Exceptions to this Specification are stated in the individual Specifications.

SR 3.0.3 If it is discovered that a Surveillance was not performed within its specified Frequency, then compliance with the requirement to declare the LCO not met may be delayed, from the time of discovery, up to 24 hours2.777778e-4 days <br />0.00667 hours <br />3.968254e-5 weeks <br />9.132e-6 months <br /> or up to the limit of the specified Frequency, whichever is greater. This delay period is permitted to allow performance of the Surveillance. The delay period is only applicable when there is a reasonable expectation the surveillance will be met when performed. A risk evaluation shall be performed for any Surveillance delayed greater than 24 hours2.777778e-4 days <br />0.00667 hours <br />3.968254e-5 weeks <br />9.132e-6 months <br /> and the risk impact shall be managed.

If the Surveillance is not performed within the delay period, the LCO must immediately be declared not met, and the applicable Condition(s) must be entered.

TENNESSEE VALLEY AUTHORITY DOCKET NO. 50-391 WATTS BAR NUCLEAR PLANT, UNIT 2 AMENDMENT TO FACILITY OPERATING LICENSE Amendment No. 66 License No. NPF-96 1.

The U.S. Nuclear Regulatory Commission (the Commission) has found that:

A.

The application for amendment by the Tennessee Valley Authority (TVA) dated June 13, 2022, complies with the standards and requirements of the Atomic Energy Act of 1954, as amended (the Act), and the Commissions rules and regulations set forth in Title 10 of the Code of Federal Regulations (10 CFR)

Chapter I; B.

The facility will operate in conformity with the application, the provisions of the Act, and the rules and regulations of the Commission; C.

There is reasonable assurance (i) that the activities authorized by this amendment can be conducted without endangering the health and safety of the public, and (ii) that such activities will be conducted in compliance with the Commissions regulations; D.

The issuance of this amendment will not be inimical to the common defense and security or to the health and safety of the public; and E.

The issuance of this amendment is in accordance with 10 CFR Part 51 of the Commissions regulations and all applicable requirements have been satisfied.

2.

Accordingly, the license is amended by changes to the Technical Specifications as indicated in the attachment to this license amendment, and paragraph 2.C.(2) of Facility Operating License No. NPF-96 is hereby amended to read as follows:

(2)

Technical Specifications and Environmental Protection Plan The Technical Specifications contained in Appendix A as revised through Amendment No. 66 and the Environmental Protection Plan contained in Appendix B, both of which are attached hereto, are hereby incorporated into this license. TVA shall operate the facility in accordance with the Technical Specifications and the Environmental Protection Plan.

3.

This license amendment is effective as of the date of its issuance and shall be implemented within 60 days.

FOR THE NUCLEAR REGULATORY COMMISSION David J. Wrona, Chief Plant Licensing Branch II-2 Division of operating Reactor Licensing Office of Nuclear Reactor Regulation

Attachment:

Changes to the Operating License and Technical Specifications Date of Issuance: January 20, 2023 David J.

Wrona Digitally signed by David J. Wrona Date: 2023.01.20 14:20:19 -05'00'

ATTACHMENT TO AMENDMENT NO. 66 WATTS BAR NUCLEAR PLANT, UNIT 2 FACILITY OPERATING LICENSE NO. NPF-96 DOCKET NO. 50-391 Replace page 3 of Facility Operating License No. NPF-96 with the attached revised page 3. The revised page is identified by amendment number and contains a marginal line indicating the area of change.

Replace the following pages of the Appendix A Technical Specifications with the attached pages. The revised pages are identified by amendment number and contain marginal lines indicating the areas of change.

Remove Insert 1.3-1 1.3-1 1.3-2 1.3-2 1.3-2a 3.0-2 3.0-2 3.0-4 3.0-4 Unit 2 Facility Operating License No. NPF-96 Amendment No. 66 C.

The license shall be deemed to contain and is subject to the conditions specified in the Commissions regulations set forth in 10 CFR Chapter I and is subject to all applicable provisions of the Act, and to the rules, regulations, and orders of the Commission now or hereafter in effect, and is subject to the additional conditions specified or incorporated below.

(1)

Maximum Power Level TVA is authorized to operate the facility at reactor core power levels not in excess of 3459 megawatts thermal.

(2)

Technical Specifications and Environmental Protection Plan The Technical Specifications contained in Appendix A as revised through Amendment No. 66 and the Environmental Protection Plan contained in Appendix B, both of which are attached hereto, are hereby incorporated into this license. TVA shall operate the facility in accordance with the Technical Specifications and the Environmental Protection Plan.

(3)

TVA shall implement permanent modifications to prevent overtopping of the embankments of the Fort Loudon Dam due to the Probable Maximum Flood by June 30, 2018.

(4)

Full SPECTRUM LOCA Methodology shall be implemented when the WBN Unit 2 steam generators are replaced with steam generators equivalent to the existing steam generators at WBN Unit 1.

(5)

By December 31, 2019, the licensee shall report to the NRC that the actions to resolve the issues identified in Bulletin 2012-01, Design Vulnerability in Electrical Power System, have been implemented.

(6)

The licensee shall maintain in effect the provisions of the physical security plan, security personnel training and qualification plan, and safeguards contingency plan, and all amendments made pursuant to the authority of 10 CFR 50.90 and 50.54(p).

(7)

TVA shall fully implement and maintain in effect all provisions of the Commission approved cyber security plan (CSP), including changes made pursuant to the authority of 10 CFR 50.90 and 10 CFR 50.54(p). The TVA approved CSP was discussed in NUREG-0847, Supplement 28, as amended by changes approved in License Amendment No. 7.

(8)

TVA shall implement and maintain in effect all provisions of the approved fire protection program as described in the Fire Protection Report for the facility, as described in NUREG-0847, Supplement 29, subject to the following provision:

Completion Times 1.3 1.3 Completion Times (continued)

Watts Bar - Unit 2 1.3-1 1.0 USE AND APPLICATION 1.3 Completion Times PURPOSE The purpose of this section is to establish the Completion Time convention and to provide guidance for its use.

BACKGROUND Limiting Conditions for Operation (LCOs) specify minimum requirements for ensuring safe operation of the unit. The ACTIONS associated with an LCO state Conditions that typically describe the ways in which the requirements of the LCO can fail to be met. Specified with each stated Condition are Required Action(s) and Completion Time(s).

DESCRIPTION The Completion Time is the amount of time allowed for completing a Required Action. It is referenced to the discovery of a situation (e.g., inoperable equipment or variable not within limits) that requires entering an ACTIONS Condition unless otherwise specified, providing the unit is in a MODE or specified condition stated in the Applicability of the LCO.

Unless otherwise specified, the Completion Time begins when a senior licensed operator on the operating shift crew with responsibility for plant operations makes the determination that an LCO is not met and an ACTIONS Condition is entered. The "otherwise specified" exceptions are varied, such as a Required Action Note or Surveillance Requirement Note that provides an alternative time to perform specific tasks, such as testing, without starting the Completion Time. While utilizing the Note, should a Condition be applicable for any reason not addressed by the Note, the Completion Time begins. Should the time allowance in the Note be exceeded, the Completion Time begins at that point. The exceptions may also be incorporated into the Completion Time. For example, LCO 3.8.1, "AC Sources - Operating," Required Action B.3, requires declaring required feature(s) supported by an inoperable diesel generator, inoperable when the redundant required feature(s) are inoperable. The Completion Time states, "4 hours4.62963e-5 days <br />0.00111 hours <br />6.613757e-6 weeks <br />1.522e-6 months <br /> from discovery of Condition B concurrent with inoperability of redundant required feature(s)." In this case the Completion Time does not begin until the conditions in the Completion Time are satisfied.

Required Actions must be completed prior to the expiration of the specified Completion Time. An ACTIONS Condition remains in effect and the Required Actions apply until the Condition no longer exists or the unit is not within the LCO Applicability.

Amendment 66

Completion Times 1.3 1.3 Completion Times (continued)

Watts Bar - Unit 2 1.3-2 DESCRIPTION (continued)

If situations are discovered that require entry into more than one Condition at a time within a single LCO (multiple Conditions), the Required Actions for each Condition must be performed within the associated Completion Time. When in multiple Conditions, separate Completion Times are tracked for each Condition starting from the discovery of the situation that required entry into the Condition, unless otherwise specified.

Once a Condition has been entered, subsequent trains, subsystems, components, or variables expressed in the Condition, discovered to be inoperable or not within limits, will not result in separate entry into the Condition, unless specifically stated. The Required Actions of the Condition continue to apply to each additional failure, with Completion Times based on initial entry into the Condition, unless otherwise specified.

Amendment 66

Completion Times 1.3 1.3 Completion Times (continued)

Watts Bar - Unit 2 1.3-2a However, when a subsequent train, subsystem, component, or variable expressed in the Condition is discovered to be inoperable or not within limits, the Completion Time(s) may be extended. To apply this Completion Time extension, two criteria must first be met. The subsequent inoperability:

a.

Must exist concurrent with the first inoperability; and b.

Must remain inoperable or not within limits after the first inoperability is resolved.

The total Completion Time allowed for completing a Required Action to address the subsequent inoperability shall be limited to the more restrictive of either:

a.

The stated Completion Time, as measured from the initial entry into the Condition, plus an additional 24 hours2.777778e-4 days <br />0.00667 hours <br />3.968254e-5 weeks <br />9.132e-6 months <br />; or b.

The stated Completion Time as measured from discovery of the subsequent inoperability.

The above Completion Time extensions do not apply to those Specifications that have exceptions that allow completely separate re-entry into the Condition (for each train, subsystem, component, or variable expressed in the Condition) and separate tracking of Completion Times based on this re-entry. These exceptions are stated in individual Specifications.

The above Completion Time extension does not apply to a Completion Time with a modified "time zero." This modified "time zero" may be expressed as a repetitive time (i.e., "once per 8 hours9.259259e-5 days <br />0.00222 hours <br />1.322751e-5 weeks <br />3.044e-6 months <br />," where the Completion Time is referenced from a previous completion of the Required Action versus the time of Condition entry) or as a time modified by the phrase "from discovery..." Example 1.3-3 illustrates one use of this type of Completion Time. The 10 day Completion Time specified for Conditions A and B in Example 1.3-3 may not be extended.

Amendment 66

LCO Applicability 3.0 3.0 LCO APPLICABILITY Watts Bar - Unit 2 3.0-2 (continued)

LCO 3.0.4 (continued) b.

After performance of a risk assessment addressing inoperable systems and components, consideration of the results, determination of the acceptability of entering the MODE or other specified condition in the Applicability, and establishment of risk management actions, if appropriate (exceptions to this Specification are stated in the individual Specifications); or c.

When an allowance is stated in the individual value, parameter, or other Specification.

This Specification shall not prevent changes in MODES or other specified conditions in the Applicability that are required to comply with ACTIONS or that are part of a shutdown of the unit.

LCO 3.0.5 Equipment removed from service or declared inoperable to comply with ACTIONS may be returned to service under administrative control solely to perform testing required to demonstrate its OPERABILITY or the OPERABILITY of other equipment. This is an exception to LCO 3.0.2 for the system returned to service under administrative control to perform the testing required to demonstrate OPERABILITY.

LCO 3.0.6 When a supported system LCO is not met solely due to a support system LCO not being met, the Conditions and Required Actions associated with this supported system are not required to be entered.

Only the support system LCO ACTIONS are required to be entered.

This is an exception to LCO 3.0.2 for the supported system. In this event, additional evaluations and limitations may be required in accordance with Specification 5.7.2.18, "Safety Function Determination Program (SFDP)." If a loss of safety function is determined to exist by this program, the appropriate Conditions and Required Actions of the LCO in which the loss of safety function exists are required to be entered.

When a support system's Required Action directs a supported system to be declared inoperable or directs entry into Conditions and Required Actions for a supported system, the applicable Conditions and Required Actions shall be entered in accordance with LCO 3.0.2.

Amendment 66

SR Applicability 3.0 Watts Bar - Unit 2 3.0-4 (continued) 3.0 SURVEILLANCE REQUIREMENT (SR) APPLICABILITY SR 3.0.1 SRs shall be met during the MODES or other specified conditions in the Applicability for individual LCOs, unless otherwise stated in the SR.

Failure to meet a Surveillance, whether such failure is experienced during the performance of the Surveillance or between performances of the Surveillance, shall be failure to meet the LCO. Failure to perform a Surveillance within the specified Frequency shall be failure to meet the LCO except as provided in SR 3.0.3. Surveillances do not have to be performed on inoperable equipment or variables outside specified limits.

SR 3.0.2 The specified Frequency for each SR is met if the Surveillance is performed within 1.25 times the interval specified in the Frequency, as measured from the previous performance or as measured from the time a specified condition of the Frequency is met.

For Frequencies specified as "once," the above interval extension does not apply.

If a Completion Time requires periodic performance on a "once per..."

basis, the above Frequency extension applies to each performance after the initial performance.

Exceptions to this Specification are stated in the individual Specifications.

SR 3.0.3 If it is discovered that a Surveillance was not performed within its specified Frequency, then compliance with the requirement to declare the LCO not met may be delayed, from the time of discovery, up to 24 hours2.777778e-4 days <br />0.00667 hours <br />3.968254e-5 weeks <br />9.132e-6 months <br /> or up to the limit of the specified Frequency, whichever is greater. This delay period is permitted to allow performance of the Surveillance. The delay period is only applicable when there is a reasonable expectation the surveillance will be met when performed. A risk evaluation shall be performed for any Surveillance delayed greater than 24 hours2.777778e-4 days <br />0.00667 hours <br />3.968254e-5 weeks <br />9.132e-6 months <br /> and the risk impact shall be managed.

If the Surveillance is not performed within the delay period, the LCO must immediately be declared not met, and the applicable Condition(s) must be entered.

Amendment No. 3, 12, 39, 66

SAFETY EVALUATION BY THE OFFICE OF NUCLEAR REACTOR REGULATION AMENDMENT NO. 326 TO RENEWED FACILITY OPERATING LICENSE NO. DPR 33 AMENDMENT NO. 349 TO RENEWED FACILITY OPERATING LICENSE NO. DPR 52 AMENDMENT NO. 309 TO RENEWED FACILITY OPERATING LICENSE NO. DPR 68 AMENDMENT NO. 361 TO RENEWED FACILITY OPERATING LICENSE NO. DPR-77 AMENDMENT NO. 355 TO RENEWED FACILITY OPERATING LICENSE NO. DPR-79 AMENDMENT NO. 158 TO FACILITY OPERATING LICENSE NO. NPF-90 AMENDMENT NO. 66 TO FACILITY OPERATING LICENSE NO. NPF-96 BROWNS FERRY NUCLEAR PLANT, UNITS 1, 2, AND 3 SEQUOYAH NUCLEAR PLANT, UNITS 1 AND 2 WATTS BAR NUCLEAR PLANT, UNITS 1 AND 2 TENNESSEE VALLEY AUTHORITY DOCKET NOS. 50-259, 50-260, 50-296, 50-327, 50-328, 50-390, AND 50-391

1.0 INTRODUCTION

By letter dated June 13, 2022 (Agencywide Documents Access and Management System Accession No. ML22164A806), the Tennessee Valley Authority (the licensee) submitted a license amendment request for Browns Ferry Nuclear Plant (Browns Ferry), Units 1, 2, and 3; Sequoyah Nuclear Plant (Sequoyah), Units 1 and 2; and Watts Bar Nuclear Plant (Watts Bar),

Units 1 and 2.

The proposed changes would revise each plants Technical Specification (TS) section 1.3, Completion Times, and 3.0, LCO [limiting condition for operation] Applicability and SR

[surveillance requirement] Applicability, and the TS Bases for section 3.0, LCO Applicability and SR Applicability. The proposed changes would also clarify and expand the use and application of the TS usage rules. These changes are consistent with U.S. Nuclear Regulatory Commission (NRC or the Commission)-approved Technical Specifications Task Force (TSTF)

Traveler TSTF-529, Revision 4, Clarify Use and Application Rules. TSTF-529, Revision 4, made changes to Standard Technical Specification (STS) Section 1.3, STS LCO 3.0.4, and SR 3.0.3. TSTF-529, Revision 4 was approved by the NRC by letter dated April 21, 2016 (ML16060A441).

2.0 REGULATORY EVALUATION

2.1 Description of the Subject TS Sections Limiting conditions for operation (LCOs) specify minimum requirements for ensuring safe operation of the unit. The actions associated with an LCO state conditions that typically describe the ways in which the requirements of the LCO can fail to be met. Specified with each stated condition are required action(s) and completion time(s).

Browns Ferry, Sequoyah, and Watts Bar TS section 1.3, Completion Times, currently describes completion times as follow:

The completion time is the amount of time allowed for completing a Required Action. It is referenced to the time of discovery of a situation (e.g., inoperable equipment or variable not within limits) that requires entering an ACTIONS Condition unless otherwise specified, providing the unit is in a MODE or specified condition stated in the Applicability of the LCO. Required Actions must be completed prior to the expiration of the specified Completion Time.

An ACTIONS Condition remains in effect and the Required Actions apply until the Condition no longer exists or the unit is not within the LCO Applicability.

If situations are discovered that require entry into more than one Condition at a time within a single LCO (multiple Conditions), the Required Actions for each Condition must be performed within the associated Completion Time. When in multiple Conditions, separate Completion Times are tracked for each Condition starting from the time of discovery of the situation that required entry into the Condition.

Once a Condition has been entered, subsequent divisions, subsystems, components, or variables expressed in the Condition, discovered to be inoperable or not within limits, will not result in separate entry into the Condition, unless specifically stated. The Required Actions of the Condition continue to apply to each additional failure, with Completion Times based on initial entry into the Condition.

The LCOs under TS Section 3.0 establish the general requirements applicable to all specifications and apply at all times, unless otherwise stated. Similarly, SR 3.0.1 through SR 3.0.4 establish the general requirements for surveillances that are applicable to all specifications and apply at all times, unless otherwise stated.

2.2 Description of TS Changes The proposed change will revise the TS sections 1.3, Completion Times, and 3.0, LCO Applicability and SR Applicability, and the TS Bases for section 3.0, LCO Applicability and SR Applicability. The proposed changes are described in more detail below.

2.2.1 Proposed Changes to Time of Discovery Browns Ferry, Sequoyah, and Watts Bar TS section 1.3, Description, currently states, in part, the following (with emphasis added on time of):

The Completion Time is the amount of time allowed for completing a Required Action. It is referenced to the time of discovery of a situation (e.g., inoperable equipment or variable not within limits) that requires entering an ACTIONS Condition unless otherwise specified, providing the unit is in a MODE or specified condition stated in the Applicability of the LCO.

TS Section 1.3, Description, also currently states, in part, the following (with emphasis added on time of):

If situations are discovered that require entry into more than one Condition at a time within a single LCO (multiple Conditions), the Required Actions for each Condition must be performed within the associated Completion Time. When in multiple Conditions, separate Completion Times are tracked for each Condition starting from the time of discovery of the situation that required entry into the Condition.

The proposed TS Section 1.3 would delete time of from the previous statements and read as follow:

The Completion Time is the amount of time allowed for completing a Required Action. It is referenced to the discovery of a situation (e.g., inoperable equipment or variable not within limits) that requires entering an ACTIONS Condition unless otherwise specified, providing the unit is in a MODE or specified condition stated in the Applicability of the LCO.

[]

If situations are discovered that require entry into more than one Condition at a time within a single LCO (multiple Conditions), the Required Actions for each Condition must be performed within the associated Completion Time. When in multiple Conditions, separate Completion Times are tracked for each Condition starting from the discovery of the situation that required entry into the Condition.

The adequacy of this change is discussed in section 3.1.1.1.

2.2.2 Proposed Addition to Time of Discovery The licensee proposed to add the following paragraph to section 1.3 of the Browns Ferry, Sequoyah, and Watts Bar TSs under

Description:

Unless otherwise specified, the Completion Time begins when a senior licensed operator on the operating shift crew with responsibility for plant operations makes the determination that an LCO is not met and an ACTIONS Condition is entered. The otherwise specified exceptions are varied, such as a Required Action Note or Surveillance Requirement Note that provides an alternative time to perform specific tasks, such as testing, without starting the Completion Time. While utilizing the Note, should a Condition be applicable for any reason not addressed by the Note, the Completion Time begins. Should the time allowance in the Note be exceeded, the Completion Time begins at that point. The exceptions may also be incorporated into the Completion Time.

For example, LCO 3.8.1, AC Sources - Operating, Required Action B.2 [Action B.3 for Browns Ferry and Watts Bar], requires declaring required feature(s) supported by an inoperable diesel generator, inoperable when the redundant required feature(s) are inoperable. The Completion Time states, 4 hours4.62963e-5 days <br />0.00111 hours <br />6.613757e-6 weeks <br />1.522e-6 months <br /> from discovery of Condition B concurrent with inoperability of redundant required feature(s). In this case the Completion Time does not begin until the conditions in the Completion Time are satisfied.

The proposed change augments the NRC staffs expectation that a senior licensed operator on the operating shift crew with responsibility for plant operations makes the determination that an LCO is not met and a Condition is entered.

The adequacy of this change is discussed in section 3.1.1.2.

2.2.3 Proposed Addition of Unless Otherwise Specified Browns Ferry, Sequoyah, and Watts Bar TS section 1.3, Description, currently states the following (with emphasis added on unless otherwise specified):

The Completion Time is the amount of time allowed for completing a Required Action. It is referenced to the time of discovery of a situation (e.g., inoperable equipment or variable not within limits) that requires entering an ACTIONS Condition unless otherwise specified, providing the unit is in a MODE or specified condition stated in the Applicability of the LCO.

The licensee proposed to add the following sentence right after the above statement to TS section 1.3, which contains the phrase unless otherwise specified:

Unless otherwise specified, the Completion Time begins when a senior licensed operator on the operating shift crew with responsibility for plant operations makes the determination that an LCO is not met and an ACTIONS Condition is entered.

In addition, the licensee proposed adding the phrase unless otherwise specified to the following two statements:

When in multiple Conditions, separate Completion Times are tracked for each Condition starting from the discovery of the situation that required entry into the Condition, unless otherwise specified.

and The Required Actions of the Condition continue to apply to each additional failure, with Completion Times based on initial entry into the Condition, unless otherwise specified.

The adequacy of this change is discussed in section 3.1.1.3.

2.2.4 Proposed Changes to LCO 3.0.4 Browns Ferry, Sequoyah, and Watts Bar TS LCO 3.0.4 currently states:

When an LCO is not met, entry into a MODE or other specified condition in the Applicability shall only be made:

a.

When the associated ACTIONS to be entered permit continued operation in the MODE or other specified condition in the Applicability for an unlimited period of time;

b.

After performance of a risk assessment addressing inoperable systems and components, consideration of the results, determination of the acceptability of entering the MODE or other specified condition in the Applicability, and establishment of risk management actions, if appropriate; exceptions to this Specification are stated in the individual Specifications, or

c.

When an allowance is stated in the individual value, parameter, or other Specification.

The licensee proposed to clarify the b statement above by placing the statement regarding exceptions in parenthesis and replacing the ending comma with a semicolon. The proposed TS LCO 3.0.4 would state the following:

When an LCO is not met, entry into a MODE or other specified condition in the Applicability shall only be made:

a.

When the associated ACTIONS to be entered permit continued operation in the MODE or other specified condition in the Applicability for an unlimited period of time;

b.

After performance of a risk assessment addressing inoperable systems and components, consideration of the results, determination of the acceptability of entering the MODE or other specified condition in the Applicability, and establishment of risk management actions, if appropriate (exceptions to this Specification are stated in the individual Specifications); or

c.

When an allowance is stated in the individual value, parameter, or other Specification.

The adequacy of this change is discussed in section 3.1.2.

2.2.5 Proposed Changes to TS SR 3.0.3 Browns Ferry, Sequoyah, and Watts Bar TS SR 3.0.3 currently states the following:

If it is discovered that a Surveillance was not performed within its specified Frequency, then compliance with the requirement to declare the LCO not met may be delayed, from the time of discovery, up to 24 hours2.777778e-4 days <br />0.00667 hours <br />3.968254e-5 weeks <br />9.132e-6 months <br /> or up to the limit of the specified Frequency, whichever is greater. This delay period is permitted to allow performance of the Surveillance. A risk evaluation shall be performed for any Surveillance delayed greater than 24 hours2.777778e-4 days <br />0.00667 hours <br />3.968254e-5 weeks <br />9.132e-6 months <br /> and the risk impact shall be managed.

If the Surveillance is not performed within the delay period, the LCO must immediately be declared not met, and the applicable Condition(s) must be entered.

When the Surveillance is performed within the delay period and the Surveillance is not met, the LCO must immediately be declared not met, and the applicable Condition(s) must be entered.

The licensee-proposed TS LCO SR 3.0.3 states the following (the additional sentence is underlined):

If it is discovered that a Surveillance was not performed within its specified Frequency, then compliance with the requirement to declare the LCO not met may be delayed, from the time of discovery, up to 24 hours2.777778e-4 days <br />0.00667 hours <br />3.968254e-5 weeks <br />9.132e-6 months <br /> or up to the limit of the specified Frequency, whichever is greater. This delay period is permitted to allow performance of the Surveillance. The delay period is only applicable when there is a reasonable expectation the surveillance will be met when performed. A risk evaluation shall be performed for any Surveillance delayed greater than 24 hours2.777778e-4 days <br />0.00667 hours <br />3.968254e-5 weeks <br />9.132e-6 months <br /> and the risk impact shall be managed.

If the Surveillance is not performed within the delay period, the LCO must immediately be declared not met, and the applicable Condition(s) must be entered.

When the Surveillance is performed within the delay period and the Surveillance is not met, the LCO must immediately be declared not met, and the applicable Condition(s) must be entered.

The adequacy of this change is discussed in section 3.1.3.

2.3 Regulatory Requirements, Licensing Information, Guidance Documents Per Title 10 of the Code of Federal Regulations (10 CFR) Section 50.36(b), each license authorizing operation of a utilization facility will include TSs. The TSs will be derived from the analyses and evaluations included in the safety analysis report, and amendments thereto, submitted pursuant to 10 CFR 50.34 (describing the technical information to be included in applications for an operating license). The Commission may include such additional TSs as the Commission finds appropriate.

The NRC staffs guidance for review of the TSs is in Chapter 16, Technical Specifications, of NUREG-0800, Standard Review Plan [(SRP)], Revision 3, dated March 2010 (ML100351425).

As described therein, as part of the regulatory standardization effort, the NRC staff has prepared STS (NUREG-1430 to NUREG-1434) for each of the light-water reactor nuclear steam supply systems (NSSSs) and associated balance-of-plant equipment systems.

Accordingly, the NRC staffs review includes consideration of whether the proposed technical specifications are consistent with the applicable reference TS (i.e., the current STS), as modified by NRC-approved TSTF Travelers such as TSTF-529, Revision 4. Special attention is given to technical specification provisions that depart from the reference technical specifications and NRC-approved TSTF Travelers to determine whether proposed differences are justified by uniqueness in plant design or other considerations so that 10 CFR 50.36 is met.

3.0 TECHNICAL EVALUATION

During the review of TSTF-529, Revision 4, the NRC staff considered generally the guidance on acceptance criteria of the SRP sections described in Section 2.3 of this safety evaluation, and, in particular, the acceptance criteria in Chapter 16, Technical Specifications, of NUREG-0800, Revision 3. Additionally, the NRC staff evaluated the proposed changes to the STS against what is required to be in the technical specifications under 10 CFR 50.36(c).

3.1 Requested Changes 3.1.1 Proposed Changes to Section 1.3, Completion Times 3.1.1.1 Proposed Changes to Time of Discovery The only mention of the term time of discovery in relation to completion times is in Browns Ferry, Sequoyah, and Watts Bar TS Section 1.3 (quoted in section 2.2.1 of this SE). Throughout the TS, the term discovery is used to describe the point in time that it is recognized that the requirements of an LCO are not met. For example, TS LCO 3.0.2 states in part, Upon discovery of a failure to meet an LCO, the Required Actions of the associated Conditions shall be met, except as provided in LCO 3.0.5 and LCO 3.0.6. In addition, the Bases to LCO 3.0.2, state, in part, LCO 3.0.2 establishes that upon discovery of a failure to meet an LCO, the associated ACTIONS shall be met.

The proposed Browns Ferry, Sequoyah, and Watts Bar TS section 1.3 would delete time of from the previous statements. The NRC staff finds the proposed change acceptable because it makes section 1.3 consistent with the language used throughout the rest of the TS. This provides clarity to the term discovery, and therefore provides a clear and objective application of the technical specification required actions and associated completion times. The change is editorial since it does not change the requirements currently in the TSs. Therefore, the NRC staff finds the proposed change acceptable.

3.1.1.2 Proposed Addition to Time of Discovery The licensee also proposed to add the following paragraph to section 1.3 of the TS under the

==

Description:==

Unless otherwise specified, the Completion Time begins when a senior licensed operator on the operating shift crew with responsibility for plant operations makes the determination that an LCO is not met and an ACTIONS Condition is entered. The otherwise specified exceptions are varied, such as a Required Action Note or Surveillance Requirement Note that provides an alternative time to perform specific tasks, such as testing, without starting the Completion Time. While utilizing the Note, should a Condition be applicable for any reason not addressed by the Note, the Completion Time begins. Should the time allowance in the Note be exceeded, the Completion Time begins at that point. The exceptions may also be incorporated into the Completion Time.

For example, LCO 3.8.1, AC Sources - Operating, Required Action B.2 [Action B.3 for Browns Ferry and Watts Bar], requires declaring required feature(s) supported by an inoperable diesel generator, inoperable when the redundant required feature(s) are inoperable. The Completion Time states, 4 hours4.62963e-5 days <br />0.00111 hours <br />6.613757e-6 weeks <br />1.522e-6 months <br /> from discovery of Condition B concurrent with inoperability of redundant required feature(s). In this case the Completion Time does not begin until the conditions in the Completion Time are satisfied.

The operating shift crew is responsible for overall control of facility operation. As part of that responsibility, the operating shift crew must be aware of the status of the plant and condition of structures, systems, and components (SSCs). This includes status of degraded or nonconforming conditions that may affect plant operation. Therefore, the proposed change simply augments the NRC staffs expectation that a senior licensed operator on the operating shift crew with responsibility for plant operations makes the determination that an LCO is not met and a Condition is entered. The phrase and an ACTIONS Condition is entered in the above proposed insertion, is necessary to accommodate circumstances in which LCO 3.0.6 allows an LCO to not be met without entry into the Conditions. In those circumstances, a Completion Time does not begin. In addition, an example is added to the proposed insertion in order to explain the concept presented.

The NRC staff finds the proposed change acceptable since it clarifies senior reactor operators responsibilities and the allowances of LCO 3.0.6, and therefore, provides a clear and objective application of the TS Required Actions and associated Completion Times. For Browns Ferry and Watts Bar however, the added paragraph will reflect Required Action B.3 consistent with the Browns Ferry and Watts Bar TSs.

3.1.1.3 Proposed Addition of Unless Otherwise Specified The phrase, unless otherwise specified, in Browns Ferry, Sequoyah, and Watts Bar TS section 1.3, refers to those instances in which TS LCOs define the start of the Completion Time as different from discovery. For example, TS, Revision 4, Specification 3.8.1, AC Sources -

Operating, Required Action B.2 (Required Action B.3 for Browns Ferry and Watts Bar), calls for declaring required feature(s) supported by an inoperable diesel generator inoperable when the redundant required feature(s) are inoperable. The Completion Time states, 4 hours4.62963e-5 days <br />0.00111 hours <br />6.613757e-6 weeks <br />1.522e-6 months <br /> from discovery of Condition B concurrent with inoperability of redundant required feature(s). In this case, the Completion Time does not begin until the conditions in the Completion Time are satisfied.

As discussed in section 2.2.3 of this SE, the licensee proposed to add the following sentence to Browns Ferry, Sequoyah, and Watts Bar TS Section 1.3, which contains the phrase unless otherwise specified:

Unless otherwise specified, the Completion Time begins when a senior licensed operator on the operating shift crew with responsibility for plant operations makes the determination that an LCO is not met and an ACTIONS Condition is entered.

In addition, the licensee proposed adding the phrase unless otherwise specified to the following two statements:

When in multiple Conditions, separate Completion Times are tracked for each Condition starting from the discovery of the situation that required entry into the Condition, unless otherwise specified.

and The Required Actions of the Condition continue to apply to each additional failure, with Completion Times based on initial entry into the Condition, unless otherwise specified.

The addition of the phrase unless otherwise specified acknowledges that there are instances, as indicated in the individual technical specifications, when the completion time does not start at discovery. These exceptions are varied, such as when a Required Action Note or Surveillance Requirement Note provides an alternative time to perform specific tasks, such as testing, without starting the Completion Time. While utilizing the Note, should a Condition be applicable for any reason not addressed by the Note, the Completion Time begins. Should the time allowance in the Note be exceeded, the Completion Time begins at that point.

The NRC staff finds the proposed change acceptable since it clarifies that there are exceptions and, therefore, provides a clear and objective application of the TS Required Actions and associated Completion Times.

3.1.2 Proposed Changes to LCO 3.0.4 As stated in Section 2.2.4 of this SE, the current Browns Ferry, Sequoyah, and Watts Bar TS LCO 3.0.4 contains three options, (a, b, and c). Paragraph a ends with a semicolon and paragraph b ends with, or.

The LCO 3.0.4.b, After performance of a risk assessment stated in the individual Specifications, or, could lead to operator misinterpretation. Operators could misapply this statement by believing the or applies to the phrase regarding exceptions and that LCO 3.0.4.a, b, and c apply concurrently.

The licensee is proposing to clarify this sentence by placing the statement regarding exceptions in parenthesis and replacing the ending comma with a semicolon. The proposed TS LCO 3.0.4 would state the following: After performance of a risk assessment if appropriate (exceptions to this specification are stated in the individual specifications); or.

The NRC staff finds that the change is editorial since it does not change the requirements currently in the technical specifications. The NRC staff finds the proposed change acceptable since it removes potential for misapplication of LCO 3.0.4 allowances, and therefore, provides a clear and objective application of the TS Required Actions.

3.1.3 Proposed Changes to SR 3.0.3 The NRC has typically interpreted SR 3.0.3, which is quoted in section 2.2.5 of this SE, as inapplicable to SRs that have never been previously performed. This is because the allowance provided by SR 3.0.3 is based on the fact that the SR was satisfactorily met in the past and the most probable result of performing the SR is the verification of conformance with the requirements. Therefore, there is reasonable expectation the SR will be met when performed.

However, the NRC staff recognizes that there are instances in which an SR may not have been performed in the past, but there is still a reasonable expectation the SR will be met when performed. For example, an SR requires testing of a relay contact. A licensee finds the relay contact has never been tested as required in accordance with a particular SR. That licensee, however, finds there is a reasonable expectation the SR will be met when performed because the subject relay contact has been tested by another SR or historical operation of the subject relay contact has been successful.

The delay period allowed by TS SR 3.0.3 offers adequate time to complete SRs that have been missed. In addition, this delay period permits the completion of an SR before complying with required actions or other remedial measures that might preclude completion of the SR. The NRC staff finds the application of the delay period provided by STS SR 3.0.3 acceptable for use on SRs that have never been performed so as long as licensees can provide an adequate determination of reasonable expectation the SR will be met when performed.

The licensee-proposed Browns Ferry, Sequoyah, and Watts Bar TS LCO SR 3.0.3 states the following (the new sentence reflecting the inclusion of SRs that have never been performed is underlined):

If it is discovered that a Surveillance was not performed within its specified Frequency, then compliance with the requirement to declare the LCO not met may be delayed, from the time of discovery, up to 24 hours2.777778e-4 days <br />0.00667 hours <br />3.968254e-5 weeks <br />9.132e-6 months <br /> or up to the limit of the specified Frequency, whichever is greater. This delay period is permitted to allow performance of the Surveillance. The delay period is only applicable when there is a reasonable expectation the surveillance will be met when performed. A risk evaluation shall be performed for any Surveillance delayed greater than 24 hours2.777778e-4 days <br />0.00667 hours <br />3.968254e-5 weeks <br />9.132e-6 months <br /> and the risk impact shall be managed.

If the Surveillance is not performed within the delay period, the LCO must immediately be declared not met, and the applicable Condition(s) must be entered.

When the Surveillance is performed within the delay period and the Surveillance is not met, the LCO must immediately be declared not met, and the applicable Condition(s) must be entered.

When making a determination of reasonable expectation that the SR will be met when performed, licensees should consider many factors. These factors include, but are not limited to, things such as the period of time since the SR was last performed, or whether the SR, or a portion thereof, has ever been performed, and many other indications, tests, or activities that might support the expectation that the SR will be met when performed. It is not sufficient to infer the behavior of the associated equipment from the performance of similar equipment. The rigor of determining whether there is a reasonable expectation an SR will be met when performed should increase based on the length of time since the last performance of the SR. If the SR has been performed recently, a review of the SR history and equipment performance may be sufficient to support a reasonable expectation that the SR will be met when performed. For SRs that have not been performed for a long period or that have never been performed, a rigorous evaluation based on objective evidence should provide a high degree of confidence that the equipment is capable of performing its specified safety function(s). The evaluation should be documented in sufficient detail to allow a knowledgeable individual to understand the basis for the determination.

The proposed change, which expands the scope of SR 3.0.3 to SRs that have never been performed, is acceptable because it requires there to be an adequate determination of a reasonable expectation the SR will be met when performed. In addition, the proposed change augments plant safety since it could prevent unnecessary shutdowns by providing adequate time to complete SRs that have never been performed but are likely to achieve satisfactory results.

3.2 Summary As described in Section 2.3 of this SE, the regulations contained in 10 CFR 50.36 require that technical specifications include items in specified categories, including LCOs and SRs. The proposed changes modify the LCOs, conditions, required actions, completion times, and SRs applicable to their usage and application. The technical specifications continue to specify the LCOs and specify the remedial measures to be taken if one of these requirements is not satisfied. The technical specifications continue to specify the appropriate SRs to ensure the necessary quality of affected structures, systems and components are maintained. Therefore, the NRC staff finds that the changes to the LCOs and SRs proposed by the licensee meet 10 CFR 50.36(c)(2) and 50.36(c)(3), respectively.

4.0 STATE CONSULTATION

In accordance with the Commissions regulations, the Tennessee State official and the Alabama State official were notified of the proposed issuance of the amendments on December 14, 2022, and January 5, 2023, respectively. The State officials had no comments.

5.0 ENVIRONMENTAL CONSIDERATION

The amendments change a requirement with respect to installation or use of a facility component located within the restricted area as defined in 10 CFR Part 20. The NRC staff has determined that the amendments involve no significant increase in the amounts, and no significant change in the types, of any effluents that may be released offsite, and that there is no significant increase in individual or cumulative occupational radiation exposure. The Commission has previously issued a proposed finding that the amendments involve no significant hazards consideration, and there has been no public comment on such finding published in the Federal Register on September 6, 2022 (87 FR 54554). Accordingly, the amendments meet the eligibility criteria for categorical exclusion set forth in 10 CFR 51.22(c)(9).

Pursuant to 10 CFR 51.22(b), no environmental impact statement or environmental assessment need be prepared in connection with the issuance of the amendments.

6.0 CONCLUSION

The Commission has concluded, based on the considerations discussed above, that: (1) there is reasonable assurance that the health and safety of the public will not be endangered by operation in the proposed manner, (2) there is reasonable assurance that such activities will be conducted in compliance with the Commissions regulations, and (3) the issuance of the amendments will not be inimical to the common defense and security or to the health and safety of the public.

Principal Contributor: C. Tilton, NRR Date: January 20, 2023

ML22349A647 OFFICE NRR/DORL/LPLII-2/PM NRR/DORL/LPLII-2/LA NRR/DSS/STSB/BC NAME PBuckberg RButler (DHarrison for)

VCusumano DATE 12/28/2022 01/20/2023 01/06/2023 OFFICE NRR/DORL/LPLII-2/BC NRR/DORL/LPLII-2/PM NAME DWrona PBuckberg DATE 01/20/2023 01/20/2023