ML17137A041

Issuance of Amendments Regarding the Adoption of TSTF-529, Revision 4, Clarify Use and Application Rules (CAC Nos. MF8897, MF8898, MF8900-MF8902, and MF8921)

ML17137A041
Person / Time
Site:	Hatch, Vogtle, Farley
Issue date:	06/27/2017
From:	Michael Orenak Plant Licensing Branch II
To:	Hutto J Southern Nuclear Operating Co
Orenak M, NRR/DORL/LPLII-1, 415-3229
References
CAC MF8890, CAC MF8897, CAC MF8898, CAC MF8901, CAC MF8902, CAC MF8921
Download: ML17137A041 (62)

Text

{{#Wiki_filter:UNITED STATES NUCLEAR REGULATORY COMMISSION WASHINGTON, D.C. 20555-0001 June 27, 2017 Mr. James J. Hutto Regulatory Affairs Director Southern Nuclear Operating Company, Inc. P.O. Box 1295 /Bin - 038 Birmingham, AL 35201-1295

SUBJECT:

JOSEPH M. FARLEY NUCLEAR PLANT, UNITS 1 AND 2; VOGTLE ELECTRIC GENERATING PLANT, UNITS 1 AND 2; AND EDWIN I. HATCH NUCLEAR PLANT, UNIT NOS. 1 AND 2 - ISSUANCE OF AMENDMENTS REGARDING THE ADOPTION OF TSTF-529, REVISION 4, "CLARIFY USE AND APPLICATION RULES" (CAC NOS. MF8897, MF8898, MF8900, MF8901, MF8902, AND MF8921)

Dear Mr. Hutto:

The U.S. Nuclear Regulatory Commission (NRC or the Commission) has issued the enclosed Amendment No. 211 to the Joseph M. Farley Nuclear Plant (FNP), Unit 1, Renewed Facility Operating License No. NPF-2; Amendment No. 208 to FNP, Unit 2, Renewed Facility Operating License No. NPF-8; Amendment No. 186 to the Vogtle Electric Generating Plant (VEGP), Unit 1, Renewed Facility Operating License No. NPF-68; Amendment No. 169 to VEGP, Unit 2, Renewed Facility Operating License No. NPF-81; Amendment No. 285 to the Edwin I. Hatch Nuclear Plant (HNP), Unit No. 1, Renewed Facility Operating License No. DPR-57; and Amendment No. 230 to HNP, Unit No. 2, Renewed Facility Operating License No. NPF-5. The amendments are in response to your application dated December 1, 2016, as supplemented by letter dated June 22, 2017. The amendments consist of modifications to the Technical Specifications requirements in Section 1.3 and Section 3.0 regarding Limiting Conditions for Operation and Surveillance Requirement usage. These changes are consistent with NRG-approved Technical Specifications Task Force (TSTF) Traveler TSTF-529, Revision 4, "Clarify Use and Application Rules."

J.Hutto A copy of the related Safety Evaluation is also enclosed. A Notice of Issuance will be included in the Commission's biweekly Federal Register notice. Si~~ Michael D. Orenak, Project Manager Plant Licensing Branch 11-1 Division of Operating Reactor Licensing Office of Nuclear Reactor Regulation Docket Nos. 50-348, 50-364, 50-424, 50-425, 50-321, and 50-366

Enclosures:

1. Amendment No. 211 to NPF-2

2. Amendment No. 208 to NPF-8

3. Amendment No. 186 to NPF-68

4. Amendment No. 169 to NPF-81

5. Amendment No. 285 to DPR-57

6. Amendment No. 230 to NPF-5

7. Safety Evaluation cc w/enclosures: Distribution via Listserv

UNITED STATES NUCLEAR REGULATORY COMMISSION WASHINGTON, D.C. 20555-0001 SOUTHERN NUCLEAR OPERATING COMPANY ALABAMA POWER COMPANY DOCKET NO. 50-348 JOSEPH M. FARLEY NUCLEAR PLANT, UNIT 1 AMENDMENT TO RENEWED FACILITY OPERATING LICENSE Amendment No. 211 Renewed License No. NPF-2

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

A. The application for amendment to the Joseph M. Farley Nuclear Plant, Unit 1 (the facility), Renewed Facility Operating License No. NPF-2, filed by Southern Nuclear Operating Company (the licensee), dated December 1, 2016, as supplemented by letter dated June 22, 2017, complies with the standards and requirements of the Atomic Energy Act of 1954, as amended (the Act), and the Commission's rules and regulations set forth in 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 Commission's regulations; D. The issuance of this license 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 Commission's regulations and all applicable requirements have been satisfied. Enclosure 1

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. NPF-2 is hereby amended to read as follows:

(2) Technical Specifications The Technical Specifications contained in Appendix A, as revised through Amendment No. 211, are hereby incorporated in the renewed license. Southern Nuclear 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 90 days of issuance.

FOR THE NUCLEAR REGULATORY COMMISSION

                                        ~-{.~

Michael T. Markley, Chief Plant Licensing Branch 11-1 Division of Operating Reactor Licensing Office of Nuclear Reactor Regulation

Attachment:

Changes to the Renewed Operating License and Technical Specifications Date of Issuance: June 2 7, 2o1 7

UNITED STATES NUCLEAR REGULATORY COMMISSION WASHINGTON, D.C. 20555-0001 SOUTHERN NUCLEAR OPERATING COMPANY ALABAMA POWER COMPANY DOCKET NO. 50-364 JOSEPH M. FARLEY NUCLEAR PLANT, UNIT 2 AMENDMENT TO RENEWED FACILITY OPERATING LICENSE Amendment No. 208 Renewed License No. NPF-8

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

A. The application for amendment to the Joseph M. Farley Nuclear Plant, Unit 2 (the facility), Renewed Facility Operating License No. NPF-8, filed by Southern Nuclear Operating Company (the licensee), dated December 1, 2016, as supplemented by letter dated June 22, 2017, complies with the standards and requirements of the Atomic Energy Act of 1954, as amended (the Act), and the Commission's rules and regulations set forth in 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 Commission's regulations; D. The issuance of this license 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 Commission's regulations and all applicable requirements have been satisfied. Enclosure 2

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. NPF-8 is hereby amended to read as follows:

(2) Technical Specifications The Technical Specifications contained in Appendix A, as revised through Amendment No. 208, are hereby incorporated in the renewed license. Southern Nuclear 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 90 days of issuance.

FOR THE NUCLEAR REGULATORY COMMISSION

                                        ~~fa~

Michael T. Markley, Chief Plant Licensing Branch 11-1 Division of Operating Reactor Licensing Office of Nuclear Reactor Regulation

Attachment:

Changes to the Renewed Operating License and Technical Specifications Date of Issuance: June 2 7 , 2 o1 7

ATTACHMENT TO LICENSE AMENDMENT NOS. 211 AND 208 JOSEPH M. FARLEY NUCLEAR PLANT, UNITS 1AND2 RENEWED FACILITY OPERATING LICENSE NOS. NPF-2 AND NPF-8 DOCKET NOS. 50-348 AND 50-364 Replace the following pages of the Licenses and the Appendix "A" Technical Specifications (TSs) with the attached revised pages. The revised pages are identified by amendment number and contain marginal lines indicating the areas of change. Remove Pages Insert Pages License License License No. NPF-2, page 4 License No. NPF-2, page 4 License No. NPF-8, page 3 License No. NPF-8, page 3 TSs TSs 1.3-1 1.3-1 1.3-2 1.3-2 1.3-3 1.3-3 3.0-2 3.0-2 3.0-4 3.0-4 3.0-5 3.0-5

(2) Technical Specifications The Technical Specifications contained in Appendix A, as revised through Amendment No. 211, are hereby incorporated in the renewed license. Southern Nuclear shall operate the facility in accordance with the Technical Specifications. (3) Additional Conditions The matters specified in the following conditions shall be completed to the satisfaction of the Commission within the stated time periods following the Issuance of the renewed license or within the operational restrictions indicated. The removal of these conditions shall be made by an amendment to the renewed license supported by a favorable evaluation by the Commission.

a. Southern Nuclear shall not operate the reactor in Operational Modes 1 and 2 with less than three reactor coolant pumps in operation.

b. Deleted per Amendment 13

c. Deleted per Amendment 2

d. Deleted per Amendment 2

e. Deleted per Amendment 152 Deleted per Amendment 2

f. Deleted per Amendment 158

g. Southern Nuclear shall maintain a secondary water chemistry monitoring program to inhibit steam generator tube degradation.

This program shall include:

1) Identification of a sampling schedule for the critical parameters and control points for these parameters;

2) Identification of the procedures used to quantify parameters that are critical to control points;

3) Identification of process sampling points;

4) A procedure for the recording and management of data;

5) Procedures defining corrective actions for off control point chemistry conditions; and Farley - Unit 1 Renewed License No. NPF-2 Amendment No. 211

(2) Alabama Power Company, pursuant to Section 103 of the Act and 10 CFR Part 50, "Licensing of Production and Utilization Facilities," to possess but not operate the facility at the designated location in Houston County, Alabama in accordance with the procedures and limitations set forth in this renewed license. (3) Southern Nuclear, pursuant to the Act and 10 CFR Part 70, to receive, possess and use at any time special nuclear material as reactor fuel, in accordance with the limitations for storage and amounts required for reactor operation, as described in the Final Safety Analysis Report, as supplemented and amended; (4) Southern Nuclear, 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; (5) Southern Nuclear, pursuant to the Act and 10 CFR Parts 30, 40 and 70, to receive, possess, and use in amounts as required any byproducts, 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 (6) Southern Nuclear, 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 renewed license shall be deemed to contain and is subject to the conditions specified in the Commission's 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 incorporate below: (1) Maximum Power Level Southern Nuclear is authorized to operate the facility at reactor core power levels not in excess of 2775 megawatts thermal. (2) Technical Specifications The Technical Specifications contained in Appendix A, as revised through Amendment No. 208, are hereby incorporated in the renewed license. Southern Nuclear shall operate the facility in accordance with the Technical Specifications. (3) Delete per Amendment 144 (4) Delete Per Amendment 149 (5) Delete per Amend 144 Farley - Unit 2 Renewed License No. NPF-8 Amendment No. 208

Completion Times 1.3 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 the inoperable DG set inoperable when its required redundant feature(s) is inoperable. The Completion Time states, "4 hours 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. (continued) Farley Units 1 and 2 1.3-1 Amendment No. 211 (Unit 1) Amendment No. 208 (Unit 2)

Completion Times 1.3 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 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 hours; 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. (continued) Farley Units 1 and 2 1.3-2 Amend~ent No. 211 (Unit 1) Amendment No. 208 (Unit 2)

Completion Times 1.3 1.3 Completion Times DESCRIPTION The above Completion Time extension does not apply to a Completion (continued) Time with a modified "time zero." This modified "time zero" may be expressed as a repetitive time (i.e., "once per 8 hours," 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 ... " 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 B.1 Be in MODE 3. 6 hours Action and associated Completion Time not met. B.2 Be in MODE 5. 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 hours AND in MODE 5 within 36 hours. A total of 6 hours is allowed for reaching MODE 3 and a total of 36 hours (not 42 hours) is allowed for reaching MODE 5 from the time that Condition B was entered. If MODE 3 is reached within 3 hours. the time allowed for reaching MODE 5 is the next 33 hours because the total time allowed for reaching MODE 5 is 36 hours. If Condition B is entered while in MODE 3, the time allowed for reaching MODE 5 is the next 36 hours. (continued) Farley Units 1 and 2 1.3-3 Amendment No. 211 (Unit 1) Amendment No. 208 (Unit 2)

LCO Applicability 3.0 3.0 LCO APPLICABILITY LCO 3.0.4 b. After performance of a risk assessment addressing inoperable (continued) 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.15, "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. LCO 3.0.7 Test Exception LCO 3.1.8 allows specified Technical Specification (TS) requirements to be changed to permit performance of special tests and operations. Unless otherwise specified, all other TS requirements remain unchanged. Compliance with Test Exception LCOs is optional. When a Test Exception LCO is desired to be met but is not met, the ACTIONS of the Test Exception LCO shall be met. When a Test Exception LCO is not desired to be met, entry into a MODE or other specified condition in the Applicability shall be made in accordance with the other applicable Specifications. Farley Units 1 and 2 3.0-2 Amendment No. 211 (Unit 1) Amendment No. 208 (Unit 2)

SR Applicability 3.0 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 hours 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 hours 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. Farley Units 1 and 2 3.0-4 Amendment No. 211 (Unit 1) Amendment No. 208 (Unit 2)

SR Applicability 3.0 3.0 SURVEILLANCE REQUIREMENT (SR) APPLICABILITY 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. This provision shall not prevent entry into 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. Farley Units 1 and 2 3.0-5 Amendment N..o * . 211 .. ( Un.it 1 ) Amendment No. 208 (Unit 2)

UNITED STATES NUCLEAR REGULATORY COMMISSION WASHINGTON, D.C. 20555-0001 SOUTHERN NUCLEAR OPERATING COMPANY, INC. GEORGIA POWER COMPANY OGLETHORPE POWER CORPORATION MUNICIPAL ELECTRIC AUTHORITY OF GEORGIA CITY OF DALTON, GEORGIA DOCKET NO. 50-424 VOGTLE ELECTRIC GENERATING PLANT, UNIT 1 AMENDMENT TO RENEWED FACILITY OPERATING LICENSE Amendment No. 186 Renewed License No. NPF-68

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

A. The application for amendment to the Vogtle Electric Generating Plant, Unit 1 (the facility), Renewed Facility Operating License No. NPF-68, filed by the Southern Nuclear Operating Company, Inc. (the licensee), acting for itself; Georgia Power Company; Oglethorpe Power Corporation; Municipal Electric Authority of Georgia; and City of Dalton, Georgia (the owners), dated December 1, 2016, as supplemented by letter dated June 22, 2017, complies with the standards and requirements of the Atomic Energy Act of 1954, as amended (the Act), and the Commission's rules and regulations set forth in 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 Commission's 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 Commission's regulations and all applicable requirements have been satisfied.

2. Accordingly, the license is hereby amended by page changes to the Technical Enclosure 3

Specifications as indicated in the attachment to this license amendment, and paragraph 2.C.(2) of Renewed Facility Operating License No. NPF-68 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. 186, and the Environmental Protection Plan contained in Appendix B, both of which are attached hereto, are hereby incorporated into this license. Southern Nuclear shall operate the facility in accordance with the Technical Specifications and the Environmental Protection Plan.

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

FOR THE NUCLEAR REGULA TORY COMMISSION

                                          ~:-~(!

Michael T. Markley, Chief Plant Licensing Branch 11-1 Division of Operating Reactor Licensing Office of Nuclear Reactor Regulation

Attachment:

Changes to the Renewed Operating License and Technical Specifications Date of Issuance: June 2 7 , 2 O1 7

UNITED STATES NUCLEAR REGULATORY COMMISSION WASHINGTON, D.C. 20555-0001 SOUTHERN NUCLEAR OPERATING COMPANY. INC. GEORGIA POWER COMPANY OGLETHORPE POWER CORPORATION MUNICIPAL ELECTRIC AUTHORITY OF GEORGIA CITY OF DALTON, GEORGIA DOCKET NO. 50-425 VOGTLE ELECTRIC GENERATING PLANT, UNIT 2 AMENDMENT TO RENEWED FACILITY OPERATING LICENSE Amendment No. 169 Renewed License No. NPF-81

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

A. The application for amendment to the Vogtle Electric Generating Plant, Unit 2 (the facility), Renewed Facility Operating License No. NPF-81, filed by the Southern Nuclear Operating Company, Inc. (the licensee), acting for itself; Georgia Power Company; Oglethorpe Power Corporation; Municipal Electric Authority of Georgia; and City of Dalton, Georgia (the owners), dated December 1, 2016, as supplemented by letter dated June 22, 2017, complies with the standards and requirements of the Atomic Energy Act of 1954, as amended (the Act), and the Commission's rules and regulations set forth in 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 Commission's 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 Commission's regulations and all applicable requirements have been satisfied.

2. Accordingly, the license is hereby amended by page changes to the Technical Enclosure 4

Specifications as indicated in the attachment to this license amendment, and paragraph 2.C.(2) of Renewed Facility Operating License No. NPF-81 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. 169, and the Environmental Protection Plan contained in Appendix B, both of which are attached hereto, are hereby incorporated into this license. Southern Nuclear shall operate the facility in accordance with the Technical Specifications and the Environmental Protection Plan.

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

FOR THE NUCLEAR REGULATORY COMMISSION Michael T. Markley, Chief Plant Licensing Branch 11-1 Division of Operating Reactor Licensing Office of Nuclear Reactor Regulation

Attachment:

Changes to the Renewed Operating License and Technical Specifications Date of Issuance: June 2 7, 2O1 7

ATTACHMENT TO LICENSE AMENDMENT NOS. 186 AND 169 VOGTLE ELECTRIC GENERATING PLANT, UNITS 1 AND 2 RENEWED FACILITY OPERATING LICENSE NOS. NPF-68 AND NPF-81 DOCKET NOS. 50-424 AND 50-425 Replace the following pages of the Licenses and the Appendix A Technical Specifications (TSs) with the attached revised pages. The revised pages are identified by amendment number and contain marginal lines indicating the areas of change. Remove Pages Insert Pages License License License No. NPF-68, page 4 License No. NPF-68, page 4 License No. NPF-81, page 3 License No. NPF-81, page 3 TSs TSs 1.3-1 1.3-1 1.3-2 1.3-2 1.3-3 1.3-3 3.0-2 3.0-2 3.0-4 3.0-4

(1) Maximum Power Level Southern Nuclear is authorized to operate the facility at reactor core power levels not in excess of 3625.6 megawatts thermal (100 percent power) in accordance with the conditions specified herein. (2) Technical Specifications and Environmental Protection Plan The Technical Specifications contained in Appendix A, as revised through Amendment No. 186, and the Environmental Protection Plan contained in Appendix B, both of which are attached hereto, are hereby incorporated into this license. Southern Nuclear shall operate the facility in accordance with the Technical Specifications and the Environmental Protection Plan. (3) Southern Nuclear Operating Company shall be capable of establishing containment hydrogen monitoring within 90 minutes of initiating safety injection following a loss of coolant accident. (4) Deleted (5) Deleted (6) Deleted (7) Deleted (8) Deleted (9) Deleted (10) Mitigation Strategy License Condition The licensee shall develop and maintain strategies for addressing large fires and explosions and that include the following key areas: (a) Fire fighting response strategy with the following elements:

1. Pre-defined coordinated fire response strategy and guidance

2. Assessment of mutual aid fire fighting assets

3. Designated staging areas for equipment and materials

4. Command and control

5. Training and response personnel (b) Operations to mitigate fuel damage considering the following:

1. Protection and use of personnel assets

2. Communications

3. Minimizing fire spread

4. Procedures for Implementing integrated fire response strategy

5. Identification of readily-available pre-staged equipment

6. Training on integrated fire response strategy Renewed Operating License NPF-68 Amendment No. 186

(2) Georgia Power Company, Oglethorpe Power Corporation, Municipal Electric Authority of Georgia, and City of Dalton, Georgia, pursuant to the Act and 10 CFR Part 50, to possess but not operate the facility at the designated location in Burke County, Georgia, in accordance with the procedures and limitations set forth in this license; (3) Southern Nuclear, pursuant to the Act and 10 CFR Part 70, to receive, possess, and use at any time special nuclear material as reactor fuel, in accordance with the limitations for storage and amounts required for reactor operation, as described in the Final Safety Analysis Report, as supplemented and amended; (4) Southern Nuclear, 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; (5) Southern Nuclear, 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; (6) Southern Nuclear, pursuant to the Act and 10 CFR Parts 30, 40 and 70, to possess, but not separate, such byproduct and special nuclear materials as my be produced by the operation of the facility authorized herein. C. This license shall be deemed to contain and is subject to the conditions specified in the Commission's regulations set forth in 10 CFR Chapter 1 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 Southern Nuclear is authorized to operate the facility at reactor core power levels not in excess of 3625.6 megawatts thermal (100 percent power) in accordance with the conditions specified herein. (2) Technical Specifications and Environmental Protection Plan The Technical Specifications contained in Appendix A, as revised through Amendment No. 169 and the Environmental Protection Plan contained in Appendix B, both of which are attached hereto, are hereby incorporated into this license. Southern Nuclear shall operate the facility in accordance with the Technical Specifications and the Environmental Protection Plan. The Surveillance requirements (SRs) contained in the Appendix A Technical Specifications and listed below are not required to be performed immediately upon implementation of Amendment No. 74. The SRs listed below shall be Renewed Operating License NPF-81 Amendment No. 169

Completion Times 1.3 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 the inoperable DG. inoperable when its required redundant feature(s) is inoperable. The Completion Time states, "4 hours 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. (continued) Vogtle Units 1 and 2 1.3-1 Amendment No. 1 86 (Unit 1) Amendment No. 1 6 9 (Unit 2)

Completion Times 1.3 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 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 hours; 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. (continued) Vogtle Units 1 and 2 1.3-2 Amendment No. 186 (Unit 1) Amendment No. 169 (Unit 2)

Completion Times 1.3 1.3 Completion Times DESCRIPTION The above Completion Time extension does not apply to a Completion (continued) Time with a modified "time zero." This modified "time zero" may be expressed as a repetitive time (i.e., "once per 8 hours," 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 ... " EXAMPLES The following examples illustrate the use of Completion Times with different types of Conditions and changing Conditions. EXAMPLE 1.3-1 COMPLETION TIMES ACTIONS CONDITION REQUIRED ACTION COMPLETION TIME B. Required B.1 Be in MODE 3. 6 hours Action and associated AND Completion Time not B.2 Be in MODE 5. 36 hours met. 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 hours AND in MODE 5 within 36 hours. A total of 6 hours is allowed for reaching MODE 3 and a total of 36 hours (not 42 hours) is allowed for reaching MODE 5 from the time that Condition B was entered. If MODE 3 is reached within 3 hours, the time allowed for reaching MODE 5 is the next 33 hours because the total time allowed for reaching MODE 5 is 36 hours. If Condition B is entered while in MODE 3, the time allowed for reaching MODE 5 is the next 36 hours. (continued) Vogtle Units 1 and 2 1.3-3 Amendment No. 186 (Unit 1) Amendment No. 169 (Unit 2)

LCO Applicability 3.0 3.0 LCO APPLICABILITY LCO 3.0.4 b. After performance of a risk assessment addressing inoperable (continued) 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.5.15, "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. (continued) Vogtle Units 1 and 2 3.0-2 Amendment No. 186 (Unit 1) Amendment No. 169 (Unit 2)

SR Applicability 3.0 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 hours 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 hours 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. * (continued) Vogtle Units 1 and 2 3.0-4 Amendment No. 186 (Unit 1) Amendment No. 169 (Unit 2)

UNITED STATES NUCLEAR REGULATORY COMMISSION WASHINGTON, D.C. 20555-0001 SOUTHERN NUCLEAR OPERATING COMPANY, INC. GEORGIA POWER COMPANY OGLETHORPE POWER CORPORATION MUNICIPAL ELECTRIC AUTHORITY OF GEORGIA CITY OF DALTON, GEORGIA DOCKET NO. 50-321 EDWIN I. HATCH NUCLEAR PLANT, UNIT NO. 1 AMENDMENT TO RENEWED FACILITY OPERATING LICENSE Amendment No. 285 Renewed License No. DPR-57

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

A. The application for amendment to the Edwin I. Hatch Nuclear Plant, Unit No. 1 (the facility), Renewed Facility Operating License No. DPR-57, filed by Southern Nuclear Operating Company, Inc. (the licensee), acting for itself; Georgia Power Company; Oglethorpe Power Corporation; Municipal Electric Authority of Georgia; and City of Dalton, Georgia (the owners), dated December 1, 2016, as supplemented by letter dated June 22, 2017, complies with the standards and requirements of the Atomic Energy Act of 1954, as amended (the Act), and the Commission's rules and regulations set forth in 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 Commission's 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 Commission's regulations and all applicable requirements have been satisfied. Enclosure 5

2. Accordingly, the license is hereby amended by page 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-57 is hereby amended to read as follows:

(2) Technical Specifications The Technical Specifications (Appendix A) and the Environmental Protection Plan (Appendix B), as revised through Amendment No. 285, are hereby incorporated in the renewed license. Southern Nuclear shall operate the facility in accordance with the Technical Specifications and the Environmental Protection Plan.

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

FOR THE NUCLEAR REGULATORY COMMISSION Michael T. Markley, Chief Plant Licensing Branch 11-1 Division of Operating Reactor Licensing Office of Nuclear Reactor Regulation

Attachment:

Changes to the Renewed Operating License and Technical Specifications Date of Issuance: June 2 7, 2o1 7

ATTACHMENT TO LICENSE AMENDMENT NO. 285 EDWIN I. HATCH NUCLEAR PLANT, UNIT NO. 1 RENEWED FACILITY OPERATING LICENSE NO. DPR-57 DOCKET NO. 50-321 Replace the following pages of the License and the Appendix A Technical Specifications (TSs) with the attached revised pages. The revised pages are identified by amendment number and contain marginal lines indicating the areas of change. Remove Pages Insert Pages License License 4 4 TSs TSs 1.3-1 1.3-1 1.3-2 1.3-2 1.3-3 1.3-3 3.0-2 3.0-2 3.0-4 3.0-4

for sample analysis or instrumentation calibration, or associated with radioactive apparatus or components; (6) Southern Nuclear, 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 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, Section 50.54 of Part 50, and Section 70.32 of Part 70; all applicable provisions of the Act and the rules, regulations, and orders of the Commission now or hereafter in effect; and the additional conditions specified or incorporated below: (1) Maximum Power Level Southern Nuclear is authorized to operate the facility at steady sate reactor core power levels not in excess of 2804 megawatts thermal. (2) Technical Specifications The Technical Specifications (Appendix A) and the Environmental Plan (Appendix B), as revised through Amendment No. 285 are hereby incorporated in the renewed license. Southern Nuclear shall operate the facility in accordance with the Technical Specifications and the Environmental Protection Plan. The Surveillance Requirement (SR) contained in the Technical Specifications and listed below, is not required to be performed immediately upon implementation of Amendment No. 195. The SR listed below shall be successfully demonstrated before the time and condition specified: SR 3.8.1.18 shall be successfully demonstrated at its next regularly scheduled performance. (3) Fire Protection Southern Nuclear shall implement and maintain in effect all provisions of the fire protection program, which is referenced in the Updated Final Safety Analysis Report for the facility, as contained in the updated Fire Hazards Analysis and Fire Protection Program for the Edwin I. Hatch Nuclear Plant, Units 1 and 2, which was originally submitted by letter dated July 22, 1986. Southern Nuclear may make changes to the fire protection program without prior Commission approval only if the changes Renewed License No. DPR-57 Amendment No. 285

Completion Times 1.3 1.0 USE ANO 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 8.2, requires declaring required feature(s) supported by the inoperable OG, inoperable when the redundant required feature(s) are inoperable. The Completion Time states, "4 hours 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. (continued) HATCH UNIT 1 1.3-1 Amendment No. 285

Completion Times 1.3 1.3 Completion Times DESCRIPTION If situations are discovered that require entry into more than one Condition (continued) 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 hours; or

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

The above Completion Time extension does 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. (continued) HATCH UNIT 1 1.3-2 Amendment No. 285

Completion Times 1.3 1.3 Completion Times DESCRIPTION The above Completion Time extension does not apply to a Completion (continued) Time with a modified "time zero." This modified "time zero" may be expressed as a repetitive time (i.e., "once per 8 hours," 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 ... " 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 B.1 Be in MODE 3. 12 hours and associated Completion Time AND not met. B.2 Be in MODE 4. 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 12 hours AND in MODE 4 within 36 hours. A total of 12 hours is allowed for reaching MODE 3 and a total of 36 hours (not 48 hours) is allowed for reaching MODE 4 from the time that Condition B was entered. If MODE 3 is reached within 6 hours, the time allowed for reaching MODE 4 is the next 30 hours because the total time allowed for reaching MODE 4 is 36 hours. If Condition B is entered while in MODE 3, the time allowed for reaching MODE 4 is the next 36 hours. (continued) HATCH UNIT 1 1.3-3 Amendment No. 285

LCO Applicability 3.0 3.0 LCO APPLICABILITY LCO 3.0.4 management actions, if appropriate (exceptions to this (continued) 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 required testing. 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.5.10, "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. LCO 3.0.7 Special Operations LCOs in Section 3.1 O allow specified Technical Specifications (TS) requirements to be changed to permit performance of special tests and operations. Unless otherwise specified, all other TS requirements remain unchanged. Compliance with Special Operations LCOs is optional. When a Special Operations LCO is desired to be met but is not met, the ACTIONS of the Special Operations LCO shall be met. When a Special Operations LCO is not desired to be met, entry into a MODE or other specified condition in the Applicability shall only be made in accordance with the other applicable Specifications. (continued) HATCH UNIT 1 3.0-2 Amendment No. 285

• SR Applicability 3.0 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. I 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 hours 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 > 24 hours 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. (continued) HATCH UNIT 1 3.0-4 Amendment No. 285

UNITED STATES NUCLEAR REGULATORY COMMISSION WASHINGTON, D.C. 20555-0001 SOUTHERN NUCLEAR OPERATING COMPANY, INC. GEORGIA POWER COMPANY OGLETHORPE POWER CORPORATION MUNICIPAL ELECTRIC AUTHORITY OF GEORGIA CITY OF DALTON, GEORGIA DOCKET NO. 50-366 EDWIN I. HATCH NUCLEAR PLANT, UNIT NO. 2 AMENDMENT TO RENEWED FACILITY OPERATING LICENSE Amendment No. 230 Renewed License No. NPF-5

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

A. The application for amendment to the Edwin I. Hatch Nuclear Plant, Unit No. 2 (the facility), Renewed Facility Operating License No. NPF-5, filed by Southern Nuclear Operating Company, Inc. (the licensee), acting for itself; Georgia Power Company; Oglethorpe Power Corporation; Municipal Electric Authority of Georgia; and City of Dalton, Georgia (the owners), dated December 1, 2016, as supplemented by letter dated June 22, 2017, complies with the standards and requirements of the Atomic Energy Act of 1954, as amended (the Act), and the Commission's rules and regulations set forth in 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 Commission's 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 Commission's regulations and all applicable requirements have been satisfied. Enclosure 6

2. Accordingly, the license is hereby amended by page 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. NPF-5 is hereby amended to read as follows:

(2) Technical Specifications The Technical Specifications (Appendix A) and the Environmental Protection Plan (Appendix B), as revised through Amendment No. 230, are hereby incorporated in the renewed license. Southern Nuclear shall operate the facility in accordance with the Technical Specifications and the Environmental Protection Plan.

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

FOR THE NUCLEAR REGULATORY COMMISSION Michael T. Markley, Chief Plant Licensing Branch 11-1 Division of Operating Reactor Licensing Office of Nuclear Reactor Regulation

Attachment:

Changes to the Renewed Operating License and Technical Specifications Date of Issuance: June 2 7 , 2o1 7

ATTACHMENT TO LICENSE AMENDMENT NO. 230 EDWIN I. HATCH NUCLEAR PLANT, UNIT NO. 2 RENEWED FACILITY OPERATING LICENSE NO. NPF-5 DOCKET NO. 50-366 Replace the following pages of the License and the Appendix A Technical Specifications (TSs) with the attached revised pages. The revised pages are identified by amendment number and contain marginal lines indicating the areas of change. Remove Pages Insert Pages License License 4 4 TSs TSs 1.3-1 1.3-1 1.3-2 1.3-2 1.3-3 1.3-3 3.0-2 3.0-2 3.0-4 3.0-4

(6) Southern Nuclear, 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 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, Section 50.54 of Part 50, and Section 70.32 of Part 70; all applicable provisions of the Act and the rules, regulations, and orders of the Commission now or hereafter in effect; and the additional conditions 2 specified or incorporated below: (1) Maximum Power Level Southern Nuclear is authorized to operate the facility at steady sate reactor core power levels not in excess of 2,804 megawatts thermal, in accordance with the conditions specified herein. (2) Technical Specifications The Technical Specifications (Appendix A) and the Environmental Protection Plan (Appendix B); as revised through Amendment No. 230 are hereby incorporated in the renewed license. Southern Nuclear shall operate the facility in accordance with the Technical Specifications and the Environmental Protection Plan. (3) Additional Conditions The matters specified in the following conditions shall be completed to the satisfaction of the Commission within the stated time periods following the issuance of the renewed license or within the operational restrictions indicated. The removal of these conditions shall be made by an amendment to the license supported by a favorable evaluation by the Commission. (a) Fire Protection Southern Nuclear shall implement and maintain in effect all provisions of the fire protection program, which is referenced in the Updated Final Safety Analysis Report for the facility, as contained 2 The original licensee authorized to possess, use, and operate the facility with Georgia Power Company (GPC). Consequently, certain historical references to GPC remain in certain license conditions. Renewed License No. NPF-5 Amendment No. 230

Completion Times 1.3 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 the inoperable DG. inoperable when the redundant required feature(s) are inoperable The Completion Time states, "4 hours from discovery of Condition 8 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. (continued) HATCH UNIT 2 1.3-1 Amendment No. 230

Completion Times 1.3 1.3 Completion Times DESCRIPTION If situations are discovered that require entry into more than one Condition (continued) 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 hours; or

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

The above Completion Time extension does 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. (continued) HATCH UNJT2 1.3-2 Amendment No. 230

Completion Times 1.3 1.3 Completion Times DESCRIPTION The above Completion Time extension does not apply to a Completion (continued) Time with a modified "time zero." This modified "time zero" may be expressed as a repetitive time (i.e., "once per 8 hours," 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 ... " 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 B.1 Be in MODE 3. 12 hours and associated Completion Time not met. B.2 Be in MODE 4. 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 12 hours AND in MODE 4 within 36 hours. A total of 12 hours is allowed for reaching MODE 3 and a total of 36 hours (not 48 hours) is allowed for reaching MODE 4 from the time that Condition B was entered. If MODE 3 is reached within 6 hours, the time allowed for reaching MODE 4 is the next 30 hours because the total time allowed for reaching MODE 4 is 36 hours. If Condition B is entered while in MODE 3, the time allowed for reaching MODE 4 is the next 36 hours. (continued) HATCH UNIT 2 1.3-3 Amendment No. 230

SR Applicability 3.0 3.0 LCO APPLICABILITY LCO 3.0.4 management actions, if appropriate (exceptions to this specification (continued) 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 required testing. 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.5.10, "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. LCO 3.0.7 Special Operations LCOs in Section 3.10 allow specified Technical Specifications (TS) requirements to be changed to permit performance of special tests and operations. Unless otherwise specified, all other TS requirements remain unchanged. Compliance with Special Operations LCOs is optional. When a Special Operations LCO is desired to be met but is not met, the ACTIONS of the Special Operations LCO shall be met. When a Special Operations LCO is not desired to be met, entry into a MODE or other specified condition in the Applicability shall only be made in accordance with the other applicable Specifications. (continued) HATCH UNIT 2 3.0-2 Amendment No. 230

SR Applicability 3.0 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 hours 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 > 24 hours 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. (continued) HATCH UNIT 2 3.0-4 Amendment No. 230

UNITED STATES NUCLEAR REGULATORY COMMISSION WASHINGTON, D.C. 20555-0001 SAFETY EVALUATION BY THE OFFICE OF NUCLEAR REACTOR REGULATION RELATED TO JOSEPH M. FARLEY NUCLEAR PLANT, UNITS 1 AND 2 AMENDMENT NO. 211 TO RENEWED FACILITY OPERATING LICENSE NO. NPF-2 AMENDMENT NO. 208 TO RENEWED FACILITY OPERATING LICENSE NO. NPF-8 AND VOGTLE ELECTRIC GENERATING PLANT, UNITS 1AND2 AMENDMENT NO. 186 TO RENEWED FACILITY OPERATING LICENSE NO. NPF-68 AMENDMENT NO. 169 TO RENEWED FACILITY OPERATING LICENSE NO. NPF-81 AND EDWIN I. HATCH NUCLEAR PLANT, UNIT NOS. 1 AND 2 AMENDMENT NO. 285 TO RENEWED FACILITY OPERATING LICENSE NO. DPR-57 AMENDMENT NO. 230 TO RENEWED FACILITY OPERATING LICENSE NO. NPF-5 SOUTHERN NUCLEAR OPERATING COMPANY, INC. DOCKET NOS. 50-348, 50-364, 50-424, 50-425. 50-321, AND 50-366

1.0 INTRODUCTION

By application dated December 1, 2016 (Agencywide Documents Access and Management System (ADAMS) Accession No. ML16340A005), as supplemented by letter dated June 22, 2017 (ADAMS Accession No. ML17173A863), Southern Nuclear Operating Company (SNC, the licensee) requested changes to the technical specifications (TSs) in the Renewed Facility Operating Licenses for the Joseph M. Farley Nuclear Plant (FNP), Units 1 and 2; Vogtle Electric Generating Plant (VEGP), Units 1 and 2; and Edwin I. Hatch Nuclear Plant (HNP), Unit Nos. 1 and 2. The proposed changes would modify the TSs requirements in Section 1.3, "Completion Times," and Section 3.0, "Limiting Condition for Operation (LCO) Applicability," and "Surveillance Requirement (SR) Applicability." The licensee stated that these proposed changes are Enclosure 7

consistent with NRG-approved Technical Specifications Task Force (TSTF) Traveler TSTF-529, Revision 4, "Clarify Use and Application Rules" (ADAMS Accession No. ML16062A271). NRC support for the changes in TSTF-529, Revision 4, was provided in a letter dated April 21, 2016 (ADAMS Accession No. ML16060A441).

2.0 REGULATORY EVALUATION

2.1 Description of Subject TS Sections As specified in Title 10 of the Code of Federal Regulations (10 CFR) 50.36(c)(2), LCOs are the lowest functional capability or performance levels of equipment required for safe operation of the facility. The actions associated with an LCO state conditions that typically describe the ways in which the requirements can fail to be met. Specified with each stated condition are Required Action(s) and Completion Time(s). FNP, Units 1 and 2, and VEGP, Units 1 and 2, TS Section 1.3, "Completion Times," currently describes Completion Times as follows: 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 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. HNP, Unit Nos. 1 and 2, TS Section 1.3, "Completion Times," currently describes Completion Times as follows: 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. LCOs 3.0.1 through 3.0.9 establish the general requirements applicable to all specifications and apply at all times, unless otherwise stated. Similarly, SRs 3.0.1 through 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 Proposed TS Changes The proposed changes would revise FNP, Units 1 and 2, HNP, Unit Nos. 1 and 2, and VEGP, Units 1 and 2, TS Sections 1.3, "Completion Times," and 3.0, "LCO Applicability." The proposed changes are described in more detail below. 2.2.1 Proposed Changes to "Time of Discovery" FNP, Units 1 and 2, HNP, Unit Nos. 1 and 2, and VEGP, Units 1 and 2, TS Section 1.3, "Description," currently states, in part, the following (with emphasis added to "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. FNP, Units 1 and 2, HNP, Unit Nos. 1 and 2, and VEGP ,Units 1 and 2, TS Section 1.3, "Description," also currently states, in part, the following (with emphasis added to "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 licensee's proposed changes to FNP, Units 1 and 2; HNP, Unit Nos. 1 and 2; and VEGP, Units 1 and 2, TS Section 1.3 would delete "time of' from the previous statements so that they 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 of this safety evaluation (SE). 2.2.2 Proposed Addition to "Time of Discovery" The licensee proposed to add the following paragraph to the FNP, Units 1 and 2, TS Section 1.3 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 8.2, requires declaring required feature(s) supported by the inoperable DG set inoperable when its required redundant feature(s) is inoperable. The Completion Time states, "4 hours 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 licensee proposed to add the following paragraph to the HNP, Unit Nos. 1 and 2, TS Section 1.3 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 8.2, requires declaring required feature(s) supported by the inoperable DG, inoperable when the required redundant feature(s) are inoperable. The Completion Time states, "4 hours from discovery of Condition 8 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 licensee proposed to add the following paragraph to VEGP, Units 1 and 2, TS Section 1.3 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 8.3 requires declaring required feature(s) supported by the inoperable DG inoperable when its required redundant feature(s) is inoperable. The Completion Time states, "4 hours from discovery of Condition 8 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 staff's 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 that a Condition is entered.

The adequacy of this change is discussed in Section 3.1.1.2 of this SE. 2.2.3 Proposed Addition of "Unless Otherwise Specified" FNP, Units 1 and 2, HNP, Unit Nos. 1 and 2, and VEGP, Units 1 and 2, TS Section 1.3, "Description," currently states the following (with emphasis added to "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 FNP, Units 1 and 2; HNP, Unit Nos. 1 and 2; and VEGP, Units 1 and 2, 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 of this SE. 2.2.4 Proposed Changes to LCO 3.0.4 FNP, Units 1 and 2, and HNP, Unit Nos. 1 and 2, TS LCO 3.0.4 currently states, in part: 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.

VEGP, Units 1 and 2, TS LCO 3.0.4 currently states, in part: 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 for all plants and replacing the ending comma with a semicolon for FNP, Units 1 and 2, and HNP, Unit Nos. 1 and 2. Note that VEGP, Units 1 and 2, already had this semicolon instead of a comma. The proposed FNP, Units 1 and 2, HNP, Unit Nos. 1 and 2, and VEGP, Units 1 and 2, TS LCO 3.0.4 would state the following, in part: 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 of this SE. 2.2.5 Proposed Changes to TS SR 3.0.3 FNP, Units 1 and 2, and VEGP, Units 1 and 2, 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 hours 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 hours 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. HNP, Unit Nos. 1 and 2, TS SR 3.0.3 currently state 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 hours 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 > 24 hours 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 the following changes to FNP, Units 1 and 2, and VEGP, Units 1 and 2, TS SR 3.0.3 (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 hours 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 hours 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 the following changes to HNP, Unit Nos. 1 and 2, TS SR 3.0.3 (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 hours 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 > 24 hours 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 these changes is discussed in Section 3.1.3 of this SE. 2.3 Regulatory Requirements. Licensing Information, Guidance Documents The U.S. Nuclear Regulatory Commission (NRG) staff considered the following regulatory requirements, guidance, and licensing information during its review of the proposed changes. Under 10 CFR 50.36(c), TSs are required to include items in the following categories: (1) safety limits, limiting safety system settings, and limiting control settings; (2) LCOs; (3) SRs; (4) design

features; (5) administrative controls; (6) decommissioning; (7) initial notification; and (8) written reports. Section 50.36(c)(2) of 10 CFR states that: Limiting conditions for operation are the lowest functional capability or performance levels of equipment required for safe operation of the facility. When [an LCO] of a nuclear reactor is not met, the licensee shall shut down the reactor or follow any remedial action permitted by the technical specifications until the condition can be met. When [an LCO] of any process step in the system of a fuel reprocessing plant is not met, the licensee shall shut down that part of the operation or follow any remedial action permitted by the technical specifications until the condition can be met. and Section 50.36(c)(3) of 10 CFR states that: Surveillance requirements are requirements relating to test, calibration, or inspection to assure that the necessary quality of systems and components is maintained, that facility operation will be within safety limits, and that the [LCOs] will be met. The NRC staff's guidance for the review of the TS is in NUREG-0800, "Standard Review Plan for the Review of Safety Analysis Reports for Nuclear Power Plants: LWR [Light-Water Reactor] Edition," Chapter 16, "Technical Specifications," Revision 3, dated March 2010 (ADAMS Accession No. ML100351425). As described therein, as part of the regulatory standardization effort, the NRC staff has prepared improved STSs for each of the LWR nuclear steam supply systems and associated balance-of-plant equipment systems. The licensee's proposed amendment is based on TSTF-529, Revision 4, which is a change to the improved STSs that the NRC approved in April 2016 (ADAMS Accession No. ML16060A441). The NRC staff's review includes consideration of whether the proposed changes are consistent with the NRG-approved TSTF-529, Revision 4. Special attention is given to TS provisions that depart from the improved STSs, as modified by NRG-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 Standard Review Plan sections described in Section 2.3 of this SE, 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 plants' TS against what is required to be in the TS under 10 CFR 50.36. 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 the plants' TS Section 1.3 (quoted in Section 2.2.1 of this SE). Throughout the plants' 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 requires in part that upon discovery of a failure to

meet an LCO, the Required Actions of the associated Conditions shall be met, except as provided in LCOs 3.0.5 and 3.0.6. The proposed changes to the plants' 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 TS. This provides clarity to the term "discovery," and therefore provides a clear and objective application of the TS Required Actions and associated Completion Times. The change is editorial since it does not change requirements currently in TS. Therefore, the NRC staff finds the proposed change acceptable. 3.1.1.2 Proposed Addition to "Time of Discovery" The licensee proposed to add the following paragraph to the FNP, Units 1 and 2, TS Section 1.3 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, requires declaring required feature(s) supported by the inoperable DG set inoperable when its required redundant feature(s) is inoperable. The Completion Time states, "4 hours 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 licensee proposed to add the following paragraph to the HNP, Unit Nos. 1 and 2, TS Section 1.3 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, requires declaring required feature(s) supported by the inoperable DG, inoperable when the required redundant feature(s) are inoperable. The Completion Time states, "4 hours 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 licensee proposed to add the following paragraph to VEGP, Units 1 and 2, TS Section 1.3 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.3 requires declaring required feature(s) supported by the inoperable DG inoperable when its required redundant feature(s) is inoperable. The Completion Time states, "4 hours 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 the condition of structures, systems, and components. This includes the status of degraded or nonconforming conditions that may affect plant operation. Therefore, the proposed change simply augments the NRC staff's 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 illustrate 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 plants' TS Required Actions and associated Completion Times. 3.1.1.3 Proposed Addition of "Unless Otherwise Specified" The phrase, "unless otherwise specified," in the plants' 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, FNP, Units 1 and 2, HNP, Unit Nos. 1 and 2, and VEGP, Units 1 and 2, TS 3.8.1, "AC [alternating current] Sources - Operating," Required Action B.2 (for VEGP, Units 1 and 2, it is

Required Action 8.3), calls for declaring required feature(s) supported by an inoperable diesel generator inoperable when the required redundant feature(s) are inoperable. The Completion Time states, "4 hours 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 all plants' 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 for all plants: 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 TS, when the Completion Time does not start at discovery. These exceptions are varied, such as when a Required Action note or SR 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 as well. 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 plants' 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 TS LCO 3.0.4 for FNP, Units 1 and 2; HNP, Unit Nos. 1 and 2; and VEGP, Units 1 and 2, contains three options (i.e., a, b, and c). Paragraph a ends with a semicolon and paragraph b, in the case of FNP, Units 1 and 2, and HNP, Unit Nos. 1 and 2, ends with", or". The LCO 3.0.4.b statement: "After performance of a risk assessment ... stated in the individual Specifications, or," could lead to operator misinterpretation. Operators could misapply this statement by believing that the "or" applies to the phrase regarding exceptions and that LCO 3.0.4.a, b, and c apply concurrently.

The licensee proposed to clarify this sentence by placing the statement regarding exceptions in parenthesis for all plants. For FNP, Units 1 and 2, and HNP, Unit Nos. 1 and 2, the licensee proposes to replace the ending comma with a semicolon. The proposed TS LCO 3.0.4 statement for all plants would be 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 TS. 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 plants' TS Required Actions. 3.1.3 Proposed Changes to TS SR 3.0.3 The NRC has typically interpreted TS 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 TS 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 the plants' 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 TS SR 3.0.3 acceptable for use on SRs that have never been performed so long as licensees can provide an adequate determination of reasonable expectation the SR will be met when performed. The licensee proposed the following changes to TS SR 3.0.3 for FNP, Units 1 and 2, and VEGP, Units 1 and 2 (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 hours 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 hours 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 the following changes to TS SR 3.0.3 for HNP, Unit Nos. 1 and 2 (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 hours 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 > 24 hours 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 the plants' TS SR 3.0.3 to SRs that have never been performed, is acceptable because it requires 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.

Based on the above, the NRC staff concludes that the requirements of 10 CFR 50.36 continue to be met, therefore, the proposed changes are acceptable.

4.0 STATE CONSULTATION

In accordance with the Commission's regulations, the State of Alabama official and the State of Georgia official were notified of the proposed issuance of the amendments on May 17, 2017. On May 17, 2017, the NRC staff confirmed that neither State official had comments.

5.0 ENVIRONMENTAL CONSIDERATION

The amendments change a requirement with respect to the installation or use of facility components 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 on February 28, 2017 (82 FR 12135). 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 Commission's 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 Date of issuance: June 2 7 , 2o1 7

ML17137A041 *via memo OFFICE NRR/DORL/LPL2-1 /PM NRR/DORL/LPL2-1 /LA NRR/DSS/STSB/BC(A)* OGC- NLO NAME MOrenak KGoldstein JWhitman JWachutka DATE 5/24/2017 6/12/2017 5/1/2017 6/5/2017 OFFICE NRR/DORL/LPL2-1 /BC NRR/DORL/LPL2-1 /PM NAME MMarkley Orenak DATE 6/27/2017 6/27/2017}}