ML17340A720

From kanterella
Jump to navigation Jump to search

Issuance of Amendments to Adopt TSTF-529, Clarify Use and Application Rules (CAC Nos. MF9999 - MG0008; EPID L-2017-LLA-0255)
ML17340A720
Person / Time
Site: Oconee, Mcguire, Catawba, Harris, Robinson, McGuire  Duke Energy icon.png
Issue date: 02/01/2018
From: Dennis Galvin
Plant Licensing Branch II
To: Capps S
Duke Energy Corp
Galvin D NRR/DORL/LPL2-2 301-415-6256
References
CAC MF9999, CAC MG0000, CAC MG0001, CAC MG0002, CAC MG0003, CAC MG0004, CAC MG0005, CAC MG0006, CAC MG0007, CAC MG0008, EPID L-2017-LLA-0255
Download: ML17340A720 (94)


Text

UNITED STATES NUCLEAR REGULATORY COMMISSION WASHINGTON, D.C. 20555-0001 Mr. Steven Capps Senior Vice President Nuclear Corporate Duke Energy Corporation 526 South Church Street, EC-07H Charlotte, NC 28202 February 1, 2018

SUBJECT:

CATAWBA NUCLEAR STATION, UNITS 1 AND 2; SHEARON HARRIS NUCLEAR POWER PLANT, UNIT 1; MCGUIRE NUCLEAR STATION, UNITS 1 AND 2; OCONEE NUCLEAR STATION, UNITS 1, 2, AND 3; AND H. B. ROBINSON STEAM ELECTRIC PLANT, UNIT NO. 2 - ISSUANCE OF AMENDMENTS TO ADOPT TSTF-529, "CLARIFY USE AND APPLICATION RULES" (CAC NOS. MF9999-MG0008; EPID L-2017-LLA-0255)

Dear Mr. Capps:

The U.S. Nuclear Regulatory Commission (NRC) has issued the following enclosed Amendment Nos. 298 and 294 to Renewed Facility Operating License Nos. NPF-35 and NPF-52 for the Catawba Nuclear Station, Units 1 and 2, respectively; Amendment No. 162 to Renewed Facility Operating License No. NPF-63 for the Shearon Harris Nuclear Power Plant, Unit No. 1; Amendment Nos. 307 and 286 to Renewed Facility Operating License Nos. NPF-9 and NPF-17 for the McGuire Nuclear Station, Units 1 and 2, respectively; Amendment Nos. 407, 409, and 408 to Renewed Facility Operating License Nos. DPR-38, DPR-47, and DPR-55 for the Oconee Nuclear Station, Unit Nos. 1, 2, and 3, respectively; and Amendment No. 256 to Renewed Facility Operating License No. DPR-23 for the H. B. Robinson Steam Electric Plant, Unit No. 2.

The amendments revise the technical specifications (TSs) in response to the Duke Energy Carolinas, LLC and Duke Energy Progress, LLC application dated July 18, 2017, as supplemented by letter dated October 12, 2017 (Agencywide Documents Access and Management System (ADAMS), Accession Nos. ML17199F771 and ML17285A052). The amendments revise the TSs for each of these facilities based on Technical Specification Task Force (TSTF) Traveler TSTF-529, "Clarify Use and Application Rules," Revision 4 (ADAMS Accession No. ML16062A271 ). The changes revise and clarify the technical specification usage rules for completion times, limiting conditions for operation, and surveillance requirements.

A copy of the NRC staffs Safety Evaluation is also enclosed. The Notice of Issuance will be included in the Commission's biweekly Federal Register notice.

If you have any questions, please contact me at (301) 415-6256 or by e-mail at Dennis.Galvin@nrc.gov.

Docket Nos.

50-413, 50-414, 50-400, 50-369, 50-370, 50-269, 50-270, 50-287, and 50-261

Enclosures:

1. Amendment No. 298 to NPF-35
2. Amendment No. 294 to NPF-52
3. Amendment No. 162 to DPR-63
4. Amendment No. 307 to NPF-9
5. Amendment No. 286 to NPF-17
6. Amendment No. 407 to DPR-38
7. Amendment No. 409 to DPR-47
8. Amendment No. 408 to DPR-55
9. Amendment No. 256 to DPR-23
10. Safety Evaluation cc:

Mr. Robert T. Simril Site Vice President Catawba Nuclear Station Duke Energy Carolinas, LLC 4800 Concord Road York, SC 29745 Mr. Ed Burchfield Site Vice President Oconee Nuclear Station Duke Energy Carolinas, LLC 7800 Rochester Highway Seneca, SC 29672-0752 Ms. Tanya Hamilton Site Vice President Shearon Harris Nuclear Power Plant, Unit 1 5413 Shearon Harris Road, M/C HNP01 New Hill, NC 27562-0165 Additional Distribution via Listserv Sincerely, Dennis J. Galvin, Project Manager Plant Licensing Branch 11-2 Division of Operating Reactor Licensing Office of Nuclear Reactor Regulation Mr. Thomas Ray Vice President McGuire Nuclear Station Duke Energy Carolinas, LLC 12700 Hagers Ferry Road Huntersville, NC 28078 Mr. Ernest J. Kapopoulos, Jr.

Site Vice President H. B. Robinson Steam Electric Plant Duke Energy 3581 West Entrance Road, RNPA01 Hartsville, SC 29550

UNITED STATES NUCLEAR REGULATORY COMMISSION WASHINGTON, O.C. 20555-0001 DUKE ENERGY CAROLINAS, LLC DOCKET NO. 50-413 CATAWBA NUCLEAR STATION, UNIT 1 AMENDMENT TO RENEWED FACILITY OPERATING LICENSE Amendment No. 298 Renewed License No. NPF-35

1.

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

A.

The application for amendment to the Catawba Nuclear Station, Unit 1 (the facility) Renewed Facility Operating License No. NPF-35 filed by the Duke Energy Carolinas, LLC, acting for itself, and North Carolina Electric Membership Corporation (licensees), dated July 18, 2017, as supplemented by letter dated October 12, 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 as 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 set forth in 10 CFR Chapter I; 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 Specifications as indicated in the attachment to this license amendment, and paragraph 2.C.(2) of Renewed Facility Operating License No. NPF-35 is hereby amended to read as follows:

(2)

Technical Specifications The Technical Specifications contained in Appendix A, as revised through Amendment No. 298, which are attached hereto, are hereby incorporated into this renewed operating license. Duke Energy Carolinas, LLC, 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 120 days of issuance.

Attachment:

Changes to License No. NPF-35 and Technical Specifications FOR THE NUCLEAR REGULA TORY COMMISSION

!tdit!.!(~;-

Plant Licensing Branch 11-2 Division of Operating Reactor Licensing Office of Nuclear Reactor Regulation Date of Issuance: Elebruary 1, 2018

UNITED STATES NUCLEAR REGULATORY COMMISSION WASHINGTON, 0.C. 20555-0001 DUKE ENERGY CAROLINAS, LLC DOCKET NO. 50-414 CATAWBA NUCLEAR STATION, UNIT 2 AMENDMENT TO RENEWED FACILITY OPERA TING LICENSE Amendment No. 294 Renewed License No. NPF-52

1.

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

A.

The application for amendment to the Catawba Nuclear Station, Unit 2 (the facility) Renewed Facility Operating License No. NPF-52 filed by the Duke Energy Carolinas, LLC, acting for itself, North Carolina Municipal Power Agency No. 1 and Piedmont Municipal Power Agency (licensees), dated July 18, 2017, as supplemented by letter dated October 12, 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 as set forth in 1 O 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 set forth in 10 CFR Chapter I; 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 Specifications as indicated in the attachment to this license amendment, and paragraph 2.C.(2) of Renewed Facility Operating License No. NPF-52 is hereby amended to read as follows:

(2)

Technical Specifications The Technical Specifications contained in Appendix A, as revised through Amendment No. 294, which are attached hereto, are hereby incorporated into this renewed operating license. Duke Energy Carolinas, LLC, 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 120 days of issuance.

Attachment:

Changes to License No. NPF-52 and the Technical Specifications FOR THE NUCLEAR REGULATORY COMMISSION tta~~r Undine Shoop, Chief Plant Licensing Branch 11-2 Division of Operating Reactor Licensing Office of Nuclear Reactor Regulation Date of Issuance: February 1, 2018

ATTACHMENT TO CATAWBA NUCLEAR STATION, UNITS 1 AND 2 LICENSE AMENDMENT NO. 298 RENEWED FACILITY OPERATING LICENSE NO. NPF-35 DOCKET NO. 50-413 AND LICENSE AMENDMENT NO. 294 RENEWED FACILITY OPERATING LICENSE NO. NPF-52 DOCKET NO. 50-414 Replace the following pages of the Renewed Facility Operating 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 License NPF-35, page 4 NPF-52, page 4 TSs 1.3-1 1.3-2 1.3-3 1.3-4 1.3-5 1.3-6 1.3-7 1.3-8 1.3-9 1.3-10 1.3-11 1.3-12 1.3-13 1.3-14 3.0-2 3.0-5 License NPF-35, page 4 NPF-52, page 4 TSs 1.3-1 1.3-2 1.3-3 1.3-4 1.3-5 1.3-6 1.3-7 1.3-8 1.3-9 1.3-10 1.3-11 1.3-12 1.3-13 1.3-14 3.0-2 3.0-5 (2)

Technical Specifications (3)

The Technical Specifications contained in Appendix A, as revised through Amendment No. 298, which are attached hereto, are hereby incorporated into this renewed operating license. Duke Energy Carolinas, LLC shall operate the facility in accordance with the Technical Specifications.

Updated Final Safety Analysis Report The Updated Final Safety Analysis Report supplement submitted pursuant to 10 CFR 54.21 (d), as revised on December 16, 2002, describes certain future activities to be completed before the period of extended operation. Duke shall complete these activities no later than December 6, 2024, and shall notify the NRC in writing when implementation of these activities is complete and can be verified by NRC inspection.

The Updated Final Safety Analysis Report supplement as revised on December 16, 2002, described above, shall be included in the next scheduled update to the Updated Final Safety Analysis Report required by 10 CFR 50.71 (e)(4),

following issuance of this renewed operating license. Until that update is complete, Duke may make changes to the programs described in such supplement without prior Commission approval, provided that Duke evaluates each such change pursuant to the criteria set forth in 10 CFR 50.59 and otherwise complies with the requirements in that section.

(4)

Antitrust Conditions (5)

Duke Energy Carolinas, LLC shall comply with the antitrust conditions delineated in Appendix C to this renewed operating license.

Fire Protection Program Duke Energy Carolinas, LLC shall implement and maintain in effect all provisions of the approved fire protection program that complies with 1 O CFR 50.48(a) and 1 O CFR 50.48(c), as specified in the licensee amendment request dated September 25, 2013; as supplemented by letters dated January 13, 2015; January 28, 2015; February 27, 2015; March 30, 2015; April 28, 2015; July 15, 2015; August 14, 2015; September 3, 2015; December 11, 2015; January 7, 2016; March 23, 2016; June 15, 2016; August 2, 2016; September 7, 2016; and, January 26, 2017, as approved in the SE dated February 8, 2017. Except where NRC approval for changes or deviations is required by 1 O CFR 50.48(c), and provided no other regulation, technical specification, license condition or requirement would require prior NRC approval, the licensee may make changes to the fire protection program without prior approval of the Commission if those changes satisfy the provisions set forth in 1 O CFR 50.48(a) and 1 o CFR 50.48(c), the change does not require a change to a technical specification or a license condition, and the criteria listed below are satisfied.

Renewed License No. NPF-35 Amendment 298

(2)

(3) Technical Specifications The Technical Specifications contained in Appendix A, as revised through Amendment No. 294, which are attached hereto, are hereby incorporated into this renewed operating license. Duke Energy Carolinas, LLC shall operate the facility in accordance with the Technical Specifications.

Updated Final Safety Analysis Report The Updated Final Safety Analysis Report supplement submitted pursuant to 1 O CFR 54.21 (d), as revised on December 16, 2002, describes certain future activities to be completed before the period of extended operation. Duke shall complete these activities no later than December 6, 2024, and shall notify the NRC in writing when implementation of these activities is complete and can be verified by NRC inspection.

The Updated Final Safety Analysis Report supplement as revised on December 16, 2002, described above, shall be included in the next scheduled update to the Updated Final Safety Analysis Report required by 10 CFR 50.71 (e)(4),

following issuance of this renewed operating license. Until that update is complete, Duke may make changes to the programs described in such supplement without prior Commission approval, provided that Duke evaluates each such change pursuant to the criteria set forth in 10 CFR 50.59 and otherwise complies with the requirements in that section.

( 4)

Antitrust Conditions (5)

Duke Energy Carolinas, LLC shall comply with the antitrust conditions delineated in Appendix C to this renewed operating license.

Fire Protection Program Duke Energy Carolinas, LLC shall implement and maintain in effect all provisions of the approved fire protection program that complies with 10 CFR 50.48(a) and 10 CFR 50.48(c), as specified in the licensee amendment request dated September 25, 2013; as supplemented by letters dated January 13, 2015; January 28; 2015; February 27, 2015; March 30, 2015; April 28, 2015; July 15, 2015; August 14, 2015; September 3, 2015; December 11, 2015; January 7, 2016; March 23, 2016; June 15, 2016; August 2, 2016; September 7, 2016; and, January 26, 2017, as approved in the SE dated February 8, 2017. Except where NRC approval for changes or deviations is required by 1 O CFR 50.48(c), and provided no other regulation, technical specification, license condition or requirement would require prior NRC approval, the licensee may make changes to the fire protection program without prior approval of the Commission if those changes satisfy the provisions set forth in 10 CFR 50.48(a) and 10 CFR 50.48(c),

the change does not require a change to a technical specification or a license condition, and the criteria listed below are satisfied.

Renewed License No. NPF-52 Amendment No. 294

Completion Times 1.3 1.0 USE AND APPLICATION 1.3 Completion Times PURPOSE BACKGROUND DESCRIPTION The purpose of this section is to establish the Completion Time convention and to provide guidance for its use.

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).

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 an inoperable diesel generator, inoperable when the redundant required feature(s) are inoperable. The Completion Time states, "4 hours4.62963e-5 days <br />0.00111 hours <br />6.613757e-6 weeks <br />1.522e-6 months <br /> from discovery of Condition B concurrent with inoperability of redundant required feature(s)." In this case the Completion Time does not begin until the conditions in the Completion Time are satisfied.

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

(continued)

Catawba Units 1 and 2 1.3-1 Amendment Nos. 298/294

Completion Times 1.3 1.3 Completion Times (continued)

DESCRIPTION (continued)

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

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

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

a.

Must exist concurrent with the first inoperability; and

b.

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

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

a.

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

b.

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

( continued)

Catawba Units 1 and 2 1.3-2 Amendment Nos. 298/294

Completion Times 1.3 1.3 Completion Times (continued)

DESCRIPTION (continued)

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

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

( continued)

Catawba Units 1 and 2 1.3-3 Amendment Nos. 298/294

1.3 Completion Times (continued)

Completion Times 1.3 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 hours6.944444e-5 days <br />0.00167 hours <br />9.920635e-6 weeks <br />2.283e-6 months <br /> Action and associated AND Completion Time not B.2 Be in MODE 5.

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

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

(continued)

Catawba Units 1 and 2 1.3-4 Amendment Nos. 298/294

Completion Times 1.3 1.3 Completion Times EXAMPLES (continued)

EXAMPLE 1.3-2 ACTIONS CONDITION A.

One pump inoperable.

B.

Required Action and associated Completion Time not met.

REQUIRED ACTION COMPLETION TIME A.1 Restore pump to 7 days OPERABLE status.

8.1 Be in MODE 3.

6 hours6.944444e-5 days <br />0.00167 hours <br />9.920635e-6 weeks <br />2.283e-6 months <br /> AND 8.2 Be in MODE 5.

36 hours4.166667e-4 days <br />0.01 hours <br />5.952381e-5 weeks <br />1.3698e-5 months <br /> When a pump is declared inoperable, Condition A is entered. If the pump is not restored to OPERABLE status within 7 days, Condition B is also entered and the Completion Time clocks for Required Actions 8.1 and 8.2 start. If the inoperable pump is restored to OPERABLE status after Condition B is entered, Condition A and Bare exited, and therefore, the Required Actions of Condition B may be terminated.

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

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

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

While in LCO 3.0.3, if one of the inoperable pumps is restored to OPERABLE status and the Completion Time for Condition A has expired,

( continued)

Catawba Units 1 and 2 1.3-5 Amendment Nos. 298/294

Completion Times 1.3 1.3 Completion Times EXAMPLES EXAMPLE 1.3-2 ( continued)

LCO 3.0.3 may be exited and operation continued in accordance with Condition B. The Completion Time for Condition B is tracked from the time the Condition A Completion Time expired.

On restoring one of the pumps to OPERABLE status, the Condition A Completion Time is not reset, but continues from the time the first pump was declared inoperable. This Completion Time may be extended if the pump restored to OPERABLE status was the first inoperable pump. A 24 hour2.777778e-4 days <br />0.00667 hours <br />3.968254e-5 weeks <br />9.132e-6 months <br /> extension to the stated 7 days is allowed, provided this does not result in the second pump being inoperable for > 7 days.

( continued)

Catawba Units 1 and 2 1.3-6 Amendment Nos. 298/294

1.3 Completion Times EXAMPLES

( continued)

EXAMPLE 1.3-3 ACTIONS CONDITION A.

One Function X train inoperable.

B.

One Function Y train inoperable.

C.

One Function X train inoperable.

AND One Function Y train inoperable.

Catawba Units 1 and 2 REQUIRED ACTION A.1 Restore Function X train to OPERABLE status.

8.1 Restore Function Y train to OPERABLE status.

C. 1 Restore Function X train to OPERABLE status.

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

Completion Times 1.3 COMPLETION TIME 7 days AND 10 days from discovery of failure to meet the LCO 72 hours8.333333e-4 days <br />0.02 hours <br />1.190476e-4 weeks <br />2.7396e-5 months <br /> AND 10 days from discovery of failure to meet the LCO 72 hours8.333333e-4 days <br />0.02 hours <br />1.190476e-4 weeks <br />2.7396e-5 months <br /> 72 hours

( continued) 1.3-7 Amendment Nos. 298/294

Completion Times 1.3 1.3 Completion Times EXAMPLES EXAMPLE 1.3-3 (continued)

When one Function X train and one Function Y train are inoperable, Condition A and Condition B are concurrently applicable. The Completion Times for Condition A and Condition B are tracked separately for each train starting from the time each train was declared inoperable and the Condition was entered. A separate Completion Time is established for Condition C and tracked from the time the second train was declared inoperable (i.e., the time the situation described in Condition C was discovered).

If Required Action C.2 is completed within the specified Completion Time, Conditions B and C are exited. If the Completion Time for Required Action A.1 has not expired, operation may continue in accordance with Condition A. The remaining Completion Time in Condition A is measured from the time the affected train was declared inoperable (i.e., initial entry into Condition A).

The Completion Times of Conditions A and B are modified by a logical connector with a separate 10 day Completion Time measured from the time it was discovered the LCO was not met. In this example, without the separate Completion Time, it would be possible to alternate between Conditions A, B, and C in such a manner that operation could continue indefinitely without ever restoring systems to meet the LCO. The separate Completion Time modified by the phrase "from discovery of failure to meet the LCO" is designed to prevent indefinite continued operation while not meeting the LCO. This Completion Time allows for an exception to the normal "time zero" for beginning the Completion Time "clock". In this instance, the Completion Time "time zero" is specified as commencing at the time the LCO was initially not met, instead of at the time the associated Condition was entered.

(continued)

Catawba Units 1 and 2 1.3-8 Amendment Nos. 298/294

Completion Times 1.3 1.3 Completion Times EXAMPLES

( continued)

EXAMPLE 1.3-4 ACTIONS CONDITION A.

One or more valves inoperable.

8.

Required Action and associated Completion Time not met.

REQUIRED ACTION COMPLETION TIME A.1 Restore valve(s) to 4 hours4.62963e-5 days <br />0.00111 hours <br />6.613757e-6 weeks <br />1.522e-6 months <br /> OPERABLE status.

8.1 Be in MODE 3.

6 hours6.944444e-5 days <br />0.00167 hours <br />9.920635e-6 weeks <br />2.283e-6 months <br /> AND 8.2 Be in MODE 4.

12 hours1.388889e-4 days <br />0.00333 hours <br />1.984127e-5 weeks <br />4.566e-6 months <br /> A single Completion Time is used for any number of valves inoperable at the same time. The Completion Time associated with Condition A is based on the initial entry into Condition A and is not tracked on a per valve basis. Declaring subsequent valves inoperable, while Condition A is still in effect, does not trigger the tracking of separate Completion Times.

Once one of the valves has been restored to OPERABLE status, the Condition A Completion Time is not reset, but continues from the time the first valve was declared inoperable. The Completion Time may be extended if the valve restored to OPERABLE status was the first inoperable valve. The Condition A Completion Time may be extended for up to 4 hours4.62963e-5 days <br />0.00111 hours <br />6.613757e-6 weeks <br />1.522e-6 months <br /> provided this does not result in any subsequent valve being inoperable for > 4 hours4.62963e-5 days <br />0.00111 hours <br />6.613757e-6 weeks <br />1.522e-6 months <br />.

If the Completion Time of 4 hours4.62963e-5 days <br />0.00111 hours <br />6.613757e-6 weeks <br />1.522e-6 months <br /> (including the extension) expires while one or more valves are still inoperable, Condition B is entered.

(continued)

Catawba Units 1 and 2 1.3-9 Amendment Nos. 298/294

Completion Times 1.3 1.3 Completion Times EXAMPLES (continued)

EXAMPLE 1.3-5 ACTIONS


NOTE--------------------------------------------

Separate Condition entry is allowed for each inoperable valve.

CONDITION REQUIRED ACTION COMPLETION TIME A.

One or A.1 Restore valve to 4 hours4.62963e-5 days <br />0.00111 hours <br />6.613757e-6 weeks <br />1.522e-6 months <br /> more valves OPERABLE status.

inoperable.

B.

Required 8.1 Be in MODE 3.

6 hours6.944444e-5 days <br />0.00167 hours <br />9.920635e-6 weeks <br />2.283e-6 months <br /> Action and associated AND Completion Time not B.2 Be in MODE 4.

12 hours1.388889e-4 days <br />0.00333 hours <br />1.984127e-5 weeks <br />4.566e-6 months <br /> met.

The Note above the ACTIONS Table is a method of modifying how the Completion Time is tracked. If this method of modifying how the Completion Time is tracked was applicable only to a specific Condition, the Note would appear in that Condition rather than at the top of the ACTIONS Table.

The Note allows Condition A to be entered separately for each inoperable valve, and Completion Times tracked on a per valve basis. When a valve is declared inoperable, Condition A is entered and its Completion Time starts. If subsequent valves are declared inoperable, Condition A is entered for each valve and separate Completion Times start and are tracked for each valve.

(continued)

Catawba Units 1 and 2 1.3-10 Amendment Nos. 298/294

Completion Times 1.3 1.3 Completion Times EXAMPLES EXAMPLE 1.3-5 (continued)

If the Completion Time associated with a valve in Condition A expires, Condition B is entered for that valve. If the Completion Times associated with subsequent valves in Condition A expire, Condition B is entered separately for each valve and separate Completion Times start and are tracked for each valve. If a valve that caused entry into Condition Bis restored to OPERABLE status, Condition B is exited for that valve.

Since the Note in this example allows multiple Condition entry and tracking of separate Completion Times, Completion Time extensions do not apply.

EXAMPLE 1.3-6 ACTIONS CONDITION A.

One channel inoperable.

B.

Required Action and associated Completion Time not met.

REQUIRED ACTION COMPLETION TIME A.1 Perform SR 3.x.x.x.

Once per 8 hours9.259259e-5 days <br />0.00222 hours <br />1.322751e-5 weeks <br />3.044e-6 months <br /> OR A.2 Reduce THERMAL 8 hours9.259259e-5 days <br />0.00222 hours <br />1.322751e-5 weeks <br />3.044e-6 months <br /> POWER to

~50% RTP.

B.1 Be in MODE 3.

6 hours6.944444e-5 days <br />0.00167 hours <br />9.920635e-6 weeks <br />2.283e-6 months <br /> (continued)

Catawba Units 1 and 2 1.3-11 Amendment Nos. 298/294

Completion Times 1.3 1.3 Completion Times EXAMPLES EXAMPLE 1.3-6 (continued)

Entry into Condition A offers a choice between Required Action A.1 or A.2. Required Action A.1 has a "once per" Completion Time, which qualifies for the 25% extension, per SR 3.0.2, to each performance after the initial performance. The initial 8 hour9.259259e-5 days <br />0.00222 hours <br />1.322751e-5 weeks <br />3.044e-6 months <br /> interval of Required Action A.1 begins when Condition A is entered and the initial performance of Required Action A.1 must be complete within the first 8 hour9.259259e-5 days <br />0.00222 hours <br />1.322751e-5 weeks <br />3.044e-6 months <br /> interval. If Required Action A.1 is followed, and the Required Action is not met within the Completion Time (plus the extension allowed by SR 3.0.2),

Condition B is entered. If Required Action A.2 is followed and the Completion Time of 8 hours9.259259e-5 days <br />0.00222 hours <br />1.322751e-5 weeks <br />3.044e-6 months <br /> is not met, Condition Bis entered.

If after entry into Condition B, Required Action A.1 or A.2 is met, Condition B is exited and operation may then continue in Condition A.

(continued)

Catawba Units 1 and 2 1.3-12 Amendment Nos. 298/294

Completion Times 1.3 1.3 Completion Times EXAMPLES

( continued)

EXAMPLE 1.3-7 ACTIONS CONDITION A.

One subsystem inoperable.

B.

Required Action and associated Completion Time not met.

REQUIRED ACTION COMPLETION TIME A.1 Verify affected 1 hour1.157407e-5 days <br />2.777778e-4 hours <br />1.653439e-6 weeks <br />3.805e-7 months <br /> subsystem isolated.

AND Once per 8 hours9.259259e-5 days <br />0.00222 hours <br />1.322751e-5 weeks <br />3.044e-6 months <br /> thereafter AND A.2 Restore subsystem 72 hours8.333333e-4 days <br />0.02 hours <br />1.190476e-4 weeks <br />2.7396e-5 months <br /> to OPERABLE status.

8.1 Be in MODE 3.

6 hours6.944444e-5 days <br />0.00167 hours <br />9.920635e-6 weeks <br />2.283e-6 months <br /> AND 8.2 Be in MODE 5.

36 hours4.166667e-4 days <br />0.01 hours <br />5.952381e-5 weeks <br />1.3698e-5 months <br /> Required Action A.1 has two Completion Times. The 1 hour1.157407e-5 days <br />2.777778e-4 hours <br />1.653439e-6 weeks <br />3.805e-7 months <br /> Completion Time begins at the time the Condition is entered and each "Once per 8 hours9.259259e-5 days <br />0.00222 hours <br />1.322751e-5 weeks <br />3.044e-6 months <br /> thereafter" interval begins upon performance of Required Action A.1.

If after Condition A is entered, Required Action A.1 is not met within either the initial 1 hour1.157407e-5 days <br />2.777778e-4 hours <br />1.653439e-6 weeks <br />3.805e-7 months <br /> or any subsequent 8 hour9.259259e-5 days <br />0.00222 hours <br />1.322751e-5 weeks <br />3.044e-6 months <br /> interval from the previous performance (plus the extension allowed by SR 3.0.2),

Condition B is entered. The Completion Time clock for Condition A does not stop after Condition B is entered, but continues from the time (continued)

Catawba Units 1 and 2 1.3-13 Amendment Nos. 298/294

Completion Times 1.3 1.3 Completion Times EXAMPLES EXAMPLE 1.3-7 (continued)

Condition A was initially entered. If Required Action A.1 is met after Condition B is entered, Condition B is exited and operation may continue in accordance with Condition A, provided the Completion Time for Required Action A.2 has not expired.

IMMEDIATE When "Immediately" is used as a Completion Time, the COMPLETION TIME Required Action should be pursued without delay and in a controlled manner.

Catawba Units 1 and 2 1.3-14 Amendment Nos. 298/294

LCO Applicability 3.0 3.0 LCO APPLICABILITY (continued)

LCO 3.0.4 LCO 3.0.5 LCO 3.0.6 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; or

b.

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

c.

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

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

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 to demonstrate OPERABILITY.

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.

Catawba Units 1 and 2 3.0-2 (continued)

Amendment Nos. 298/294

SR Applicability 3.0 3.0 SURVEILLANCE REQUIREMENT (SR) APPLICABILITY SR 3.0.1 SR 3.0.2 SR 3.0.3 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.

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.

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

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

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

Catawba Units 1 and 2 3.0-5

( continued)

Amendment Nos. 298/294

UNITED STATES NUCLEAR REGULATORY COMMISSION WASHINGTON, 0.C. 20555-0001 DUKE ENERGY PROGRESS, LLC DOCKET NO. 50-400 SHEARON HARRIS NUCLEAR POWER PLANT, UNIT 1 AMENDMENT TO RENEWED FACILITY OPERATING LICENSE Amendment No. 162 Renewed License No. NPF-63

1.

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

A.

The application for amendment by Duke Energy Progress, LLC (the licensee),

dated July 18, 2017, as supplemented by letter dated October 12, 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 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-63 is hereby amended to read as follows:

(2)

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

3.

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

Attachment:

Changes to the Renewed License and the Technical Specifications FOR THE NUCLEAR REGULATORY COMMISSION u!f!i! !.ff~~

Plant Licensing Branch 11-2 Division of Operating Reactor Licensing Office of Nuclear Reactor Regulation Date of Issuance: Febraury 1, 2018

ATTACHMENT TO LICENSE AMENDMENT NO. 162 SHEARON HARRIS NUCLEAR POWER PLANT, UNIT 1 RENEWED FACILITY OPERATING LICENSE NO. NPF-63 DOCKET NO. 50-400 Replace the following page of the Renewed Facility Operating License with the revised page.

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

Remove Pages NPF-63, Page 4 Insert Pages NPF-63, Page 4 Replace the following pages of the Appendix A Technical Specifications (TS) with the attached revised pages. The revised pages are identified by amendment number and contain marginal lines indicating the areas of change.

Remove Pages 3/4 0-2 Insert Pages 3/4 0-2 C.

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

(1)

(2)

(3)

(4)

(5)

Maximum Power Level Duke Energy Progress, LLC, is authorized to operate the facility at reactor Core power levels not in excess of 2948 megawatts thermal (100 percent rated core power) in accordance with the conditions specified herein.

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

Antitrust Conditions Duke Energy Progress, LLC. shall comply with the antitrust conditions delineated in Appendix C to this license.

Initial Startup Test Program (Section 14)1 Any changes to the Initial Test Program described in Section 14 of the FSAR made in accordance with the provisions of 1 O CFR 50.59 shall be reported in accordance with 50.59(b) within one month of such change.

Steam Generator Tube Rupture (Section 15.6.3)

Prior to startup following the first refueling outage, Carolina Power & Light Company* shall submit for NRC review and receive approval if a steam generator tube rupture analysis, including the assumed operator actions, which demonstrates that the consequences of the design basis steam generator tube rupture event for the Shearon Harris Nuclear Power Plant are less than the acceptance criteria specified in the Standard Review Plan, NUREG-0800, at 15.6.3 Subparts II (1) and (2) for calculated doses from radiological releases. In preparing their analysis Carolina Power &

Light Company* will not assume that operators will complete corrective actions within the first thirty minutes after a steam generator tube rupture.

1 The parenthetical notation following the title of many license conditions denotes the section of the Safety Evaluation Report and/or its supplements wherein the license condition is discussed.

  • On April 29, 2013, the name "Carolina Power & Light Company" (CP&L) was changed to "Duke Energy Progress, Inc." On August 1, 2015, the name "Duke Energy Progress, Inc." was changed to "Duke Energy Progress, LLC."

Renewed License No. NPF-63 Amendment No. 162

APPLICABILITY LIMITING CONDITION FOR OPERATION (Continued)

If the required OPERABLE train or subsystem becomes inoperable while this specification is in use, it must be restored to OPERABLE status within 24 hours2.777778e-4 days <br />0.00667 hours <br />3.968254e-5 weeks <br />9.132e-6 months <br /> or the provisions of this specification cannot be applied to the trains or subsystems supported by the barriers that cannot perform their related support function(s).

At the end of the specified period, the required barriers must be able to perform their related support function(s) or the supported system LCO(s) shall be declared not met.

SURVEILLANCE REQUIREMENTS 4.0.1 Surveillance Requirements shall be met during the OPERATIONAL MODES or other conditions specified for individual Limiting Conditions for Operation, unless otherwise stated in an individual Surveillance Requirement. Failure to meet a Surveillance Requirement, 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 surveillance interval shall be failure to meet the LCO except as provided in SR 4.0.3. Surveillances do not have to be performed on inoperable equipment or variables outside specified limits.

4.0.2 Each Surveillance Requirement shall be performed within the specified surveillance interval with a maximum allowable extension not to exceed 25% of the specified surveillance interval.

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

If the surveillance is not performed within the delay period, the LCO must immediately be declared not met, and the applicable ACTION requirements must be met.

When the surveillance is performed within the delay period and the surveillance criteria are not met, the LCO must immediately be declared not met, and the applicable ACTION requirements must be met.

4.0.4 Entry into an OPERATIONAL MODE or other specified condition shall not be made unless the Surveillance Requirement(s) associated with the Limiting Condition for Operation has been performed within the stated surveillance interval or as otherwise specified. This provision shall not prevent passage through or to OPERATIONAL MODES as required to comply with ACTION requirements.

4.0.5 Deleted SHEARON HARRIS - UNIT 1 3/4 0-2 Amendment No.162

UNITED STATES NUCLEAR REGULATORY COMMISSION WASHINGTON, D.C. 20555-0001 DUKE ENERGY CAROLINAS, LLC DOCKET NO. 50-369 MCGUIRE NUCLEAR STATION, UNIT 1 AMENDMENT TO RENEWED FACILITY OPERATING LICENSE Amendment No. 307 Renewed License No. NPF-9

1.

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

A.

The application for amendment to the McGuire Nuclear Station, Unit 1 (the facility), Renewed Facility Operating License No. NPF-9, filed by the Duke Energy Carolinas, LLC (licensee), dated July 18, 2017, as supplemented by letter dated October 12, 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 as 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 set forth in 10 CFR Chapter I; 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 Specifications as indicated in the attachment to this license amendment, and Paragraph 2.C.(2) of Renewed Facility Operating License No. NPF-9 is hereby amended to read as follows:

(2)

Technical Specifications The Technical Specifications contained in Appendix A, as revised through Amendment No. 307, are hereby incorporated into this renewed operating license. The licensee shall operate the facility in accordance with the Technical Specifications.

3.

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

Attachment:

Changes to License No. NPF-9 and the Technical Specifications FOR THE NUCLEAR REGULATORY COMMISSION

~~t!11~~

Plant Licensing Branch 11-2 Division of Operating Reactor Licensing Office of Nuclear Reactor Regulation Date of Issuance: February 1, 2018

UNITED STATES NUCLEAR REGULATORY COMMISSION WASHINGTON, D.C. 20555-0001 DUKE ENERGY CAROLINAS, LLC DOCKET NO. 50-370 MCGUIRE NUCLEAR STATION, UNIT 2 AMENDMENT TO RENEWED FACILITY OPERATING LICENSE Amendment No. 286 Renewed License No. NPF-17

1.

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

A.

The application for amendment to the McGuire Nuclear Station, Unit 2 (the facility), Renewed Facility Operating License No. NPF-17, filed by the Duke Energy Carolinas, LLC (the licensee), dated July 18, 2017, as supplemented by letter dated October 12, 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 as 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 set forth in 10 CFR Chapter I; 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 Specifications as indicated in the attachment to this license amendment, and Paragraph 2.C.(2) of Renewed Facility Operating License No. NPF-17 is hereby amended to read as follows:

(2)

Technical Specifications The Technical Specifications contained in Appendix A, as revised through Amendment No. 286, are hereby incorporated into this renewed operating license. The licensee shall operate the facility in accordance with the Technical Specifications.

3.

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

Attachment:

Changes to License No. NPF-17 and the Technical Specifications FOR THE NUCLEAR REGULA TORY COMMISSION tt//J~-

Undine Shoop, Chief Plant Licensing Branch 11-2 Division of Operating Reactor Licensing Office of Nuclear Reactor Regulation Date of Issuance: February 1, 2018

ATTACHMENT TO MCGUIRE NUCLEAR STATION, UNITS 1 AND 2 LICENSE AMENDMENT NO. 307 RENEWED FACILITY OPERATING LICENSE NO. NPF-9 DOCKET NO. 50-369 AND LICENSE AMENDMENT NO. 286 RENEWED FACILITY OPERATING LICENSE NO. NPF-17 DOCKET NO. 50-370 Replace the following pages of the Renewed Facility Operating 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 License NPF-9, page 3 NPF-17, page 3 TSs 1.3-1 1.3-2 1.3-3 1.3-4 1.3-5 1.3-6 1.3-7 1.3-8 1.3-9 1.3-10 1.3-11 1.3-12 1.3-13 1.3-14 3.0-2 3.0-5 License NPF-9, page 3 NPF-17, page 3 TSs 1.3-1 1.3-2 1.3-3 1.3-4 1.3-5 1.3-6 1.3-7 1.3-8 1.3-9 1.3-10 1.3-11 1.3-12 1.3-13 1.3-14 3.0-2 3.0-5 (4)

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

Pursuant to the Act and 1 O CFR Parts 30, 40 and 70, to possess, but not separate, such byproducts and special nuclear materials as may be produced by the operation of McGuire Nuclear Station, Units 1 and 2, and; (6)

Pursuant to the Act and 10 CFR Parts 30 and 40, to receive, possess and process for release or transfer such byproduct material as may be produced by the Duke Training and Technology Center.

C.

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

(1)

Maximum Power Level The licensee is authorized to operate the facility at a reactor core full steady state power level of 3469 megawatts thermal (100%).

(2)

Technical Specifications The Technical Specifications contained in Appendix A, as revised through Amendment No. 307, are hereby incorporated into this renewed operating license. The licensee shall operate the facility in accordance with the Technical Specifications.

(3)

Updated Final Safety Analysis Report The Updated Final Safety Analysis Report supplement submitted pursuant to 1 O CFR 54.21 (d), as revised on December 16, 2002, describes certain future activities to be completed before the period of extended operation. Duke shall complete these activities no later than June 12, 2021, and shall notify the NRG in writing when implementation of these activities is complete and can be verified by NRG inspection.

The Updated Final Safety Analysis Report supplement as revised on December 16, 2002, described above, shall be included in the next scheduled update to the Updated Final Safety Analysis Report required by 10 CFR 50.71(e)(4), following issuance of this renewed operating license.

Until that update is complete, Duke may make changes to the programs described in such supplement without prior Commission approval, provided that Duke evaluates each such change pursuant to the criteria set forth in 10 CFR 50.59 and otherwise complies with the requirements in that section.

Renewed License No. NPF-9 Amendment No. 307 (4)

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

Pursuant to the Act and 10 CFR Parts, 30, 40 and 70, to possess, but not separate, such byproducts and special nuclear materials as my be produced by the operation of McGuire Nuclear Station, Units 1 and 2; and, (6)

Pursuant to the Act and 10 CFR Parts 30 and 40, to receive, possess and process for release or transfer such by product material as may be produced by the Duke Training and Technology Center.

C.

This renewed operating license shall be deemed to contain and is subject to the conditions specified in the Commission's regulations set forth in 1 O 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 thereafter in effect; and is subject to the additional conditions specified or incorporated below:

(1)

Maximum Power Level The licensee is authorized to operate the facility at a reactor core full steady state power level of 3469 megawatts thermal (100%).

(2)

Technical Specifications The Technical Specifications contained in Appendix A, as revised through Amendment No. 286 are hereby incorporated into this renewed operating license. The licensee shall operate the facility in accordance with the Technical Specifications.

(3)

Updated Final Safety Analysis Report The Updated Final Safety Analysis Report supplement submitted pursuant to 10 CFR 54.21 (d), as revised on December 16, 2002, describes certain future activities to be completed before the period of extended operation.

Duke shall complete these activities no later than March 3, 2023, and shall notify the NRC in writing when implementation of these activities is complete and can be verified by NRC inspection.

The Updated Final Safety Analysis Report supplement as revised on December 16, 2002, described above, shall be included in the next scheduled update to the Updated Final Safety Analysis Report required by 10 CFR 50.71 (e)(4), following issuance of this renewed operating license.

Until that update is complete, Duke may make changes to the programs described in such supplement without prior Commission approval, provided that Duke evaluates each such change pursuant to the criteria set forth in 10 CFR 50.59, and otherwise complies with the requirements in that section.

Renewed License No. NPF-17 Amendment No. 286

Completion Times 1.3 1.0 USE AND APPLICATION 1.3 Completion Times PURPOSE BACKGROUND DESCRIPTION The purpose of this section is to establish the CGmpletion Time convention and to provide guidance for its use.

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).

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 an inoperable diesel generator, inoperable when the redundant required feature(s) are inoperable. The Completion Time states, "4 hours4.62963e-5 days <br />0.00111 hours <br />6.613757e-6 weeks <br />1.522e-6 months <br /> from discovery of Condition B concurrent with inoperability of redundant required feature(s)." In this case the Completion Time does not begin until the conditions in the Completion Time are satisfied.

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

(continued)

McGuire Units 1 and 2 1.3-1 Amendment Nos. 307 /286

Completion Times 1.3 1.3 Completion Times DESCRIPTION (continued)

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

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

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

a.

Must exist concurrent with the first inoperability; and

b.

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

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

a.

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

b.

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

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

McGuire Units 1 and 2 1.3-2 (continued)

Amendment Nos. 307 /286

Completion Times 1.3 1.3 Completion Times DESCRIPTION (continued)

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

McGuire Units 1 and 2 1.3-3 (continued)

Amendment Nos. 307/286

Completion Times 1.3 1.3 Completion Times (continued)

EXAMPLES The following examples illustrate the use of Completion Times with different types of Conditions and changing Conditions.

EXAMPLE 1.3-1 ACTIONS CONDITION B.

Required Action and associated Completion Time not met.

REQUIRED ACTION 8.1 Be in MODE 3.

AND 8.2 Be in MODE 5.

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

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

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

(continued)

McGuire Units 1 and 2 1.3-4 Amendment Nos. 307/286

Completion Times 1.3 1.3 Completion Times EXAMPLES (continued)

EXAMPLE 1.3-2 ACTIONS CONDITION A.

One pump inoperable.

B.

Required Action and associated Completion Time not met.

REQUIRED ACTION COMPLETION TIME A.1 Restore pump to 7 days OPERABLE status.

8.1 Be in MODE 3.

6 hours6.944444e-5 days <br />0.00167 hours <br />9.920635e-6 weeks <br />2.283e-6 months <br /> AND 8.2 Be in MODE 5.

36 hours4.166667e-4 days <br />0.01 hours <br />5.952381e-5 weeks <br />1.3698e-5 months <br /> When a pump is declared inoperable, Condition A is entered. If the pump is not restored to OPERABLE status within 7 days, Condition B is also entered and the Completion Time clocks for Required Actions B.1 and 8.2 start. If the inoperable pump is restored to OPERABLE status after Condition B is entered, Condition A and B are exited, and therefore, the Required Actions of Condition B may be terminated.

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

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

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

While in LCO 3.0.3, if one of the inoperable pumps is restored to OPERABLE status and the Completion Time for Condition A has expired, (continued)

McGuire Units 1 and 2 1.3-5 Amendment Nos. 307 /286

Completion Times 1.3 1.3 Completion Times EXAMPLES EXAMPLE 1.3-2 (continued)

LCO 3.0.3 may be exited and operation continued in accordance with Condition B. The Completion Time for Condition B is tracked from the time the Condition A Completion Time expired.

On restoring one of the pumps to OPERABLE status, the Condition A Completion Time is not reset, but continues from the time the first pump was declared inoperable. This Completion Time may be extended if the pump restored to OPERABLE status was the first inoperable pump. A 24 hour2.777778e-4 days <br />0.00667 hours <br />3.968254e-5 weeks <br />9.132e-6 months <br /> extension to the stated 7 days is allowed, provided this does not result in the second pump being inoperable for > 7 days.

(continued)

McGuire Units 1 and 2 1.3-6 Amendment Nos. 307 /286

1.3 Completion Times EXAMPLES (continued)

EXAMPLE 1.3-3 ACTIONS CONDITION A.

One Function X train inoperable.

B.

One Function Y train inoperable.

C.

One Function X train inoperable.

AND One Function Y train inoperable.

McGuire Units 1 and 2 REQUIRED ACTION A.1 Restore Function X train to OPERABLE status.

8.1 Restore Function Y train to OPERABLE status.

C.1 Restore Function X train to OPERABLE status.

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

Completion Times 1.3 COMPLETION TIME 7 days AND 10 days from discovery of failure to meet the LCO 72 hours8.333333e-4 days <br />0.02 hours <br />1.190476e-4 weeks <br />2.7396e-5 months <br /> AND 10 days from discovery of failure to meet the LCO 72 hours8.333333e-4 days <br />0.02 hours <br />1.190476e-4 weeks <br />2.7396e-5 months <br /> 72 hours (continued) 1.3-7 Amendment Nos. 307/286

Completion Times 1.3 1.3 Completion Times EXAMPLES EXAMPLE 1.3-3 {continued}

When one Function X train and one Function Y train are inoperable, Condition A and Condition B are concurrently applicable. The Completion Times for Condition A and Condition B are tracked separately for each train starting from the time each train was declared inoperable and the Condition was entered. A separate Completion Time is established for Condition C and tracked from the time the second train was declared inoperable {i.e., the time the situation described in Condition C was discovered).

If Required Action C.2 is completed within the specified Completion Time, Conditions B and C are exited. If the Completion Time for Required Action A.1 has not expired, operation may continue in accordance with Condition A. The remaining Completion Time in Condition A is measured from the time the affected train was declared inoperable (i.e., initial entry into Condition A}.

The Completion Times of Conditions A and B are modified by a logical connector with a separate 10 day Completion Time measured from the time it was discovered the LCO was not met. In this example, without the separate Completion Time, it would be possible to alternate between Conditions A, B, and C in such a manner that operation could continue indefinitely without ever restoring systems to meet the LCO. The separate Completion Time modified by the phrase "from discovery of failure to meet the LCO" is designed to prevent indefinite continued operation while not meeting the LCO. This Completion Time allows for an exception to the normal "time zero" for beginning the Completion Time "clock". In this instance, the Completion Time "time zero" is specified as commencing at the time the LCO was initially not met, instead of at the time the associated Condition was entered.

{continued}

McGuire Units 1 and 2 1.3-8 Amendment Nos. 307 /286

Completion Times 1.3 1.3 Completion Times EXAMPLES (continued)

EXAMPLE 1.3-4 ACTIONS CONDITION A.

One or more valves inoperable.

8.

Required Action and associated Completion Time not met.

REQUIRED ACTION COMPLETION TIME A.1 Restore valve(s) to 4 hours4.62963e-5 days <br />0.00111 hours <br />6.613757e-6 weeks <br />1.522e-6 months <br /> OPERABLE status.

8.1 Be in MODE 3.

6 hours6.944444e-5 days <br />0.00167 hours <br />9.920635e-6 weeks <br />2.283e-6 months <br /> AND 8.2 Be in MODE 4.

12 hours1.388889e-4 days <br />0.00333 hours <br />1.984127e-5 weeks <br />4.566e-6 months <br /> A single Completion Time is used for any number of valves inoperable at the same time. The Completion Time associated with Condition A is based on the initial entry into Condition A and is not tracked on a per valve basis. Declaring subsequent valves inoperable, while Condition A is still in effect, does not trigger the tracking of separate Completion Times.

Once one of the valves has been restored to OPERABLE status, the Condition A Completion Time is not reset, but continues from the time the first valve was declared inoperable. The Completion Time may be extended if the valve restored to OPERABLE status was the first inoperable valve. The Condition A Completion Time may be extended for up to 4 hours4.62963e-5 days <br />0.00111 hours <br />6.613757e-6 weeks <br />1.522e-6 months <br /> provided this does not result in any subsequent valve being inoperable for > 4 hours4.62963e-5 days <br />0.00111 hours <br />6.613757e-6 weeks <br />1.522e-6 months <br />.

If the Completion Time of 4 hours4.62963e-5 days <br />0.00111 hours <br />6.613757e-6 weeks <br />1.522e-6 months <br /> (including the extension) expires while one or more valves are still inoperable, Condition B is entered.

(continued)

McGuire Units 1 and 2 1.3-9 Amendment Nos. 307/286

Completion Times 1.3 1.3 Completion Times EXAMPLES (continued)

EXAMPLE 1.3-5 ACTIONS


~-~----------------------NOTE--------------------------~-------

Separate Condition entry is allowed for each inoperable valve.

CONDITION REQUIRED ACTION COMPLETION TIME A.

One or A.1 Restore valve to 4 hours4.62963e-5 days <br />0.00111 hours <br />6.613757e-6 weeks <br />1.522e-6 months <br /> more valves OPERABLE status.

inoperable.

B.

Required 8.1 Be in MODE 3.

6 hours6.944444e-5 days <br />0.00167 hours <br />9.920635e-6 weeks <br />2.283e-6 months <br /> Action and associated AND Completion Time not 8.2 Be in MODE4.

12 hours1.388889e-4 days <br />0.00333 hours <br />1.984127e-5 weeks <br />4.566e-6 months <br /> met.

The Note above the ACTIONS Table is a method of modifying how the Completion Time is tracked. If this method of modifying how the Completion Time is tracked was applicable only to a specific Condition, the Note would appear in that Condition rather than at the top of the ACTIONS Table.

The Note allows Condition A to be entered separately for each inoperable valve, and Completion Times tracked on a per valve basis. When a valve is declared inoperable, Condition A is entered and its Completion Time starts. If subsequent valves are declared inoperable, Condition A is entered for each valve and separate Completion Times start and are tracked for each valve.

(continued)

McGuire Units 1 and 2 1.3-10 Amendment Nos. 307/286

Completion Times 1.3 1.3 Completion Times EXAMPLES EXAMPLE 1.3-5 (continued)

If the Completion Time associated with a valve in Condition A expires, Condition B is entered for that valve. If the Completion Times associated with subsequent valves in Condition A expire, Condition Bis entered separately for each valve and separate Completion Times start and are tracked for each valve. If a valve that caused entry into Condition B is restored to OPERABLE status, Condition B is exited for that valve.

Since the Note in this example allows multiple Condition entry and tracking of separate Completion Times, Completion Time extensions do not apply.

EXAMPLE 1.3-6 ACTIONS CONDITION A..

One channel inoperable.

B.

Required Action and associated Completion Time not met.

REQUIRED ACTION COMPLETION TIME A.1 Perform SR 3.x.x.x.

Once per 8 hours9.259259e-5 days <br />0.00222 hours <br />1.322751e-5 weeks <br />3.044e-6 months <br /> OR A.2 Reduce THERMAL 8 hours9.259259e-5 days <br />0.00222 hours <br />1.322751e-5 weeks <br />3.044e-6 months <br /> POWER to

~50% RTP.

8.1 Be in MODE 3.

6 hours6.944444e-5 days <br />0.00167 hours <br />9.920635e-6 weeks <br />2.283e-6 months <br /> (continued)

McGuire Units 1 and 2 1.3-11 Amendment Nos. 307/286

Completion Times 1.3 1.3 Completion Times EXAMPLES EXAMPLE 1.3-6 (continued)

Entry into Condition A offers a choice between Required Action A.1 or A.2. Required Action A.1 has a "once per" Completion Time, which qualifies for the 25% extension, per SR 3.0.2, to each performance after the initial performance. The initial 8 hour9.259259e-5 days <br />0.00222 hours <br />1.322751e-5 weeks <br />3.044e-6 months <br /> interval of Required Action A.1 begins when Condition A is entered and the initial performance of Required Action A.1 must be complete within the first 8 hour9.259259e-5 days <br />0.00222 hours <br />1.322751e-5 weeks <br />3.044e-6 months <br /> interval. If Required Action A.1 is followed, and the Required Action is not met within the Completion Time (plus the extension allowed by SR 3.0.2),

Condition Bis entered. If Required Action A.2 is followed and the Completion Time of 8 hours9.259259e-5 days <br />0.00222 hours <br />1.322751e-5 weeks <br />3.044e-6 months <br /> is not met, Condition B is entered.

If after entry into Condition B, Required Action A.1 or A.2 is met, Condition B is exited and operation may then continue in Condition A.

(continued)

McGuire Units 1 and 2 1.3-12 Amendment Nos. 307 /286

Completion Times 1.3 1.3 Completion Times EXAMPLES (continued)

EXAMPLE 1.3-7 ACTIONS CONDITION A.

One subsystem inoperable.

B.

Required Action and associated Completion Time not met.

REQUIRED ACTION COMPLETION TIME A.1 Verify affected 1 hour1.157407e-5 days <br />2.777778e-4 hours <br />1.653439e-6 weeks <br />3.805e-7 months <br /> subsystem isolated.

AND Once per 8 hours9.259259e-5 days <br />0.00222 hours <br />1.322751e-5 weeks <br />3.044e-6 months <br /> thereafter AND A.2 Restore subsystem 72 hours8.333333e-4 days <br />0.02 hours <br />1.190476e-4 weeks <br />2.7396e-5 months <br /> to OPERABLE status.

B.1 Be in MODE 3.

6 hours6.944444e-5 days <br />0.00167 hours <br />9.920635e-6 weeks <br />2.283e-6 months <br /> AND B.2 Be in MODE 5.

36 hours4.166667e-4 days <br />0.01 hours <br />5.952381e-5 weeks <br />1.3698e-5 months <br /> Required Action A.1 has two Completion Times. The 1 hour1.157407e-5 days <br />2.777778e-4 hours <br />1.653439e-6 weeks <br />3.805e-7 months <br /> Completion Time begins at the time the Condition is entered and each "Once per 8 hours9.259259e-5 days <br />0.00222 hours <br />1.322751e-5 weeks <br />3.044e-6 months <br /> thereafter interval begins upon performance of Required Action A.1.

If after Condition A is entered, Required Action A.1 is not met within either the initial 1 hour1.157407e-5 days <br />2.777778e-4 hours <br />1.653439e-6 weeks <br />3.805e-7 months <br /> or any subsequent 8 hour9.259259e-5 days <br />0.00222 hours <br />1.322751e-5 weeks <br />3.044e-6 months <br /> interval from the previous performance (plus the extension allowed by SR 3.0.2), Condition B is entered. The Completion Time clock for Condition A does not stop after Condition B is entered, but continues from the time (continued)

McGuire Units 1 and 2 1.3-13 Amendment Nos. 307 /286

Completion Times 1.3 1.3 Completion Times EXAMPLES EXAMPLE 1.3-7 (continued)

Condition A was initially entered. If Required Action A.1 is met after Condition B is entered, Condition B is exited and operation may continue in accordance with Condition A, provided the Completion Time for Required Action A.2 has not expired.

IMMEDIATE When "Immediately" is used as a Completion Time, the COMPLETION TIME Required Action should be pursued without delay and in a controlled manner.

McGuire Units 1 and 2 1.3-14 Amendment Nos. 307/286

LCO Applicability 3.0 3.0 LCO APPLICABILITY (continued)

LCO 3.0.4 LCO 3.0.5 LCO 3.0.6 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; or

b.

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

c.

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

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

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 to demonstrate OPERABILITY.

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)

McGuire Units 1 and 2 3.0-2 Amendment Nos. 307/286

SR Applicability 3.0 3.0 SURVEILLANCE REQUIREMENT (SR) APPLICABILITY SR 3.0.1 SR 3.0.2 SR 3.0.3 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.

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.

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

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

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

McGuire Units 1 and 2 3.0-5 (continued)

Amendment Nos. 307 /286

UNITED STATES NUCLEAR REGULATORY COMMISSION WASHINGTON, D.C. 20555-0001 DUKE ENERGY CAROLINAS, LLC DOCKET NO. 50-269 OCONEE NUCLEAR STATION, UNIT NO. 1 AMENDMENT TO RENEWED FACILITY OPERATING LICENSE Amendment No. 407 Renewed License No. DPR-38

1.

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

A.

The application for amendment to the Oconee Nuclear Station, Unit 1 (the facility), Renewed Facility Operating License No. DPR-38, filed by the Duke Energy Carolinas, LLC (the licensee), dated July 18, 2017, as supplemented by letter dated October 12, 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 as 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 set forth in 10 CFR Chapter I; 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 Specifications as indicated in the attachment to this license amendment, and Paragraph 3.8 of Renewed Facility Operating License No. DPR-38 is hereby amended to read as follows:

(2)

Technical Specifications The Technical Specifications contained in Appendix A, as revised through Amendment No. 407, are hereby incorporated into the license. The licensee shall operate the facility in accordance with the Technical Specifications.

3.

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

Attachment:

Changes to Renewed Facility Operating License No. DPR-38 and the Technical Specifications FOR THE NUCLEAR REGULATORY COMMISSION f!!:!~c~r Plant Licensing Branch 11-2 Division of Operating Reactor Licensing Office of Nuclear Reactor Regulation Date of Issuance: February 1, 2018

UNITED STATES NUCLEAR REGULATORY COMMISSION WASHINGTON, D.C. 20555-0001 DUKE ENERGY CAROLINAS, LLC DOCKET NO. 50-270 OCONEE NUCLEAR STATION, UNIT NO. 2 AMENDMENT TO RENEWED FACILITY OPERATING LICENSE Amendment No. 409 Renewed License No. DPR-47

1.

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

A.

The application for amendment to the Oconee Nuclear Station, Unit 2 (the facility), Renewed Facility Operating License No. DPR-47, filed by the Duke Energy Carolinas, LLC (the licensee), dated July 18, 2017, as supplemented by letter dated October 12, 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 as 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 set forth in 10 CFR Chapter I; 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 ~mendment 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 Specifications as indicated in the attachment to this license amendment, and Paragraph 3.B of Renewed Facility Operating License No. DPR-47 is hereby amended to read as follows:

(2)

Technical Specifications The Technical Specifications contained in Appendix A, as revised through Amendment No. 409, are hereby incorporated into the license. The licensee shall operate the facility in accordance with the Technical Specifications.

3.

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

Attachment:

Changes to Renewed Facility Operating License No. DPR-47 and the Technical Specifications FOR THE NUCLEAR REGULATORY COMMISSION tt!JJ~O/

Undine Shoop, Chief Plant Licensing Branch 11-2 Division of Operating Reactor Licensing Office of Nuclear Reactor Regulation Date of Issuance: Febraury 1, 2018

UNITED STATES NUCLEAR REGULATORY COMMISSION WASHINGTON, D.C. 20555-0001 DUKE ENERGY CAROLINAS, LLC DOCKET NO. 50-287 OCONEE NUCLEAR STATION, UNIT NO. 3 AMENDMENT TO RENEWED FACILITY OPERATING LICENSE Amendment No. 408 Renewed License No. DPR-55

1.

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

A.

The application for amendment to the Oconee Nuclear Station, Unit 3 (the facility), Renewed Facility Operating License No. DPR-55, filed by the Duke Energy Carolinas, LLC (the licensee), dated July 18, 2017, as supplemented by letter dated October 12, 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 as 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 set forth in 10 CFR Chapter I; 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 Specifications as indicated in the attachment to this license amendment, and Paragraph 3. B of Renewed Facility Operating License No. DPR-55 is hereby amended to read as follows:

(2)

Technical Specifications The Technical Specifications contained in Appendix A, as revised through Amendment No. 408, are hereby incorporated into the license. The licensee shall operate the facility in accordance with the Technical Specifications.

3.

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

Attachment:

Changes to Renewed Facility Operating License No. DPR-55 and the Technical Specifications FOR THE NUCLEAR REGULATORY COMMISSION u1!!1:!.~/

Plant Licensing Branch 11-2 Division of Operating Reactor Licensing Office of Nuclear Reactor Regulation Date of Issuance: February 1, 2018

ATTACHMENT TO OCONEE NUCLEAR STATION, UNIT NO. 1, 2 AND 3 LICENSE AMENDMENT NO. 407 RENEWED FACILITY OPERATING LICENSE NO. DPR-38 DOCKET NO. 50-269 AND LICENSE AMENDMENT NO. 409 RENEWED FACILITY OPERATING LICENSE NO. DPR-47 DOCKET NO. 50-270 AND LICENSE AMENDMENT NO. 408 RENEWED FACILITY OPERATING LICENSE NO. DPR-55 DOCKET NO. 50-287 Replace the following pages of the Renewed Facility Operating Licenses with the attached revised pages. The revised pages are identified by amendment number and contain marginal lines indicating the areas of change.

Remove Pages DPR-38, page 3 DPR-47, page 3 DPR-55, page 3 Insert Pages DPR-38, page 3 DPR-47, page 3 DPR-55, page 3 Replace the following pages of the Appendix A Technical Specifications with the attached revised pages. The revised pages are identified by amendment number and contain marginal lines indicating the areas of change.

Remove Pages 1.3-1 1.3-2 1.3-3 3.0-4 Insert Pages 1.3-1 1.3-2 1.3-3 3.0-4 A.

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

8.

Technical Specifications The Technical Specifications contained in Appendix A, as revised through Amendment No. 407 are hereby incorporated in the license. The licensee shall operate the facility in accordance with the Technical Specifications.

C.

This license is subject to the following antitrust conditions:

Applicant makes the commitments contained herein, recognizing that bulk power supply arrangements between neighboring entities normally tend to serve the public interest. In addition, where there are net benefits to all participants, such arrangements also serve the best interests of each of the participants. Among the benefits of such transactions are increased electric system reliability, a reduction in the cost of electric power, and minimization of the environmental effects of the production and sale of electricity.

Any particular bulk power supply transaction may afford greater benefits to one participant than to another. The benefits realized by a small system may be proportionately greater than those realized by a larger system. The relative benefits to be derived by the parties from a proposed transaction, however, should not be controlling upon a decision with respect to the desirability of participating in the transaction. Accordingly, applicant will enter into proposed bulk power transactions of the types hereinafter described which, on balance, provide net benefits to applicant. There are net benefits in a transaction if applicant recovers the cost of the transaction (as defined in,i1 (d) hereof) and there is no demonstrable net detriment to applicant arising from that transaction.

1.

As used herein:

(a)

"Bulk Power" means electric power and any attendant energy, supplied or made available at transmission or sub-transmission voltage by one electric system to another.

(b)

"Neighboring Entity" means a private or public corporation, a governmental agency or authority, a municipality, a cooperative, or a lawful association of any of the foregoing owning or operating, or proposing to own or operate, facilities for the generation and transmission of electricity which meets each of Renewed License No. DPR-38 Amendment No. 407 A.

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

B.

Technical Specifications The Technical Specifications contained in Appendix A, as revised through Amendment No. 409 are hereby incorporated in the license. The licensee shall operate the facility in accordance with the Technical Specifications.

C.

This license is subject to the following antitrust conditions:

Applicant makes the commitments contained herein, recognizing that bulk power supply arrangements between neighboring entities normally tend to serve the public interest. In addition, where there are net benefits to all participants, such arrangements also serve the best interests of each of the participants. Among the benefits of such transactions are increased electric system reliability, a reduction in the cost of electric power, and minimization of the environmental effects of the production and sale of electricity.

Any particular bulk power supply transaction may afford greater benefits to one participant than to another. The benefits realized by a small system may be proportionately greater than those realized by a larger system. The relative benefits to be derived by the parties from a proposed transaction, however, should not be controlling upon a decision with respect to the desirability of participating in the transaction. Accordingly, applicant will enter into proposed bulk power transactions of the types hereinafter described which, on balance, provide net benefits to applicant. There are net benefits in a transaction if applicant recovers the cost of the transaction (as defined in,i1 (d) hereof) and there is no demonstrable net detriment to applicant arising from that transaction.

2.

As used herein:

(c)

"Bulk Power" means electric power and any attendant energy, supplied or made available at transmission or sub-transmission voltage by one electric system to another.

(d)

"Neighboring Entity" means a private or public corporation, a governmental agency or authority, a municipality, a cooperative, or a lawful association of any of the foregoing owning or operating, or proposing to own or operate, facilities for the generation and transmission of electricity which meets each of Renewed License No. DPR-47 Amendment No. 409 A.

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

B.

Technical Specifications The Technical Specifications contained in Appendix A, as revised through Amendment No. 408 are hereby incorporated in the license. The licensee shall operate the facility in accordance with the Technical Specifications.

C.

This license is subject to the following antitrust conditions:

Applicant makes the commitments contained herein, recognizing that bulk power supply arrangements between neighboring entities normally tend to serve the public interest. In addition, where there are net benefits to all participants, such arrangements also serve the best interests of each of the participants. Among the benefits of such transactions are increased electric system reliability, a reduction in the cost of electric power, and minimization of the environmental effects of the production and sale of electricity.

Any particular bulk power supply transaction may afford greater benefits to one participant than to another. The benefits realized by a small system may be proportionately greater than those realized by a larger system. The relative benefits to be derived by the parties from a proposed transaction, however, should not be controlling upon a decision with respect to the desirability of participating in the transaction. Accordingly, applicant will enter into proposed bulk power transactions of the types hereinafter described which, on balance, provide net benefits to applicant. There are net benefits in a transaction if applicant recovers the cost of the transaction (as defined in,i1 (d) hereof) and there is no demonstrable net detriment to applicant arising from that transaction.

3.

As used herein:

(e)

"Bulk Power" means electric power and any attendant energy, supplied or made available at transmission or sub-transmission voltage by one electric system to another.

(f)

"Neighboring Entity" means a private or public corporation, a governmental agency or authority, a municipality, a cooperative, or a lawful association of any of the foregoing owning or operating, or proposing to own or operate, facilities for the generation and transmission of electricity which meets each of Renewed License No. DPR-55 Amendment No. 408

Completion Times 1.3 1.0 USE AND APPLICATION 1.3 Completion Times PURPOSE BACKGROUND DESCRIPTION The purpose of this section is to establish the Completion Time convention and to provide guidance for its use.

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).

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 C.2.2.1, requires energizing both standby buses from the Lee Combustion Turbine (LCT) via the isolated power path. The Completion Time states, "72 hours8.333333e-4 days <br />0.02 hours <br />1.190476e-4 weeks <br />2.7396e-5 months <br /> AND 1 hour1.157407e-5 days <br />2.777778e-4 hours <br />1.653439e-6 weeks <br />3.805e-7 months <br /> from subsequent discovery of deenergized standby bus." In this case the 1-hour Completion Time does not begin until the conditions In the Completion Time (i.e., discovery of the deenergized standby bus) 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.

OCONEE UNITS 1, 2, & 3 1.3-1 Amendment Nos. 407, 409, & 408

Completion Times 1.3 1.3 Completion Times DESCRIPTION (continued)

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

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

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

a.

Must exist concurrent with the first inoperability; and

b.

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

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

a.

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

b.

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

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

OCONEE UNITS 1, 2, & 3 1.3-2 Amendment Nos. 407, 409, & 408

Completion Times 1.3 1.3 Completion Times DESCRIPTION (continued)

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

The following examples illustrate the use of Completion Times with different types of Conditions and changing Conditions.

EXAMPLE 1.3-1 ACTIONS CONDITION

8. Required Action and associated Completion Time not met.

REQUIRED ACTION COMPLETION TIME 8.1 Be in MODE 3.

6 hours6.944444e-5 days <br />0.00167 hours <br />9.920635e-6 weeks <br />2.283e-6 months <br /> AND 8.2 Be in MODE 5.

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

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

OCONEE UNITS 1, 2, & 3 1.3-3 Amendment Nos. 407,409, & 408 I

SR Applicability 3.0 3.0 SURVEILLANCE REQUIREMENT (SR) APPLICABILITY SR 3.0.1 SR 3.0.2 SR 3.0.3 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.

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.

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

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

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

OCONEE UNITS 1, 2, & 3 3.0-4 Amendment Nos. 407,409, & 408

UNITED STATES NUCLEAR REGULATORY COMMISSION WASHINGTON, D.C. 20555-0001 DUKE ENERGY PROGRESS, LLC DOCKET NO. 50-261 H. 8. ROBINSON STEAM ELECTRIC PLANT, UNIT NO. 2 AMENDMENT TO RENEWED FACILITY OPERATING LICENSE Amendment No. 256 Renewed License No. DPR-23

1.

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

A.

The application for amendment by Duke Energy Progress, LLC (the licensee),

dated July 18, 2017, as supplemented by letter dated October 12, 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;

8.

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 amended by changes to the Technical Specifications, as indicated in the attachment to this license amendment; and paragraph 3.B. of Renewed Facility Operating License No. DPR-23 is hereby amended to read as follows:

B.

Technical Specifications The Technical Specifications contained in Appendix A, as revised through Amendment No. 256, are hereby incorporated in the license.

The licensee shall operate the facility in accordance with the Technical Specifications.

3.

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

Attachment:

FOR THE NUCLEAR REGULATORY COMMISSION u1!£!~or Plant Licensing Branch 11-2 Division of Operating Reactor Licensing Office of Nuclear Reactor Regulation Changes to Operating License No. DPR-23 and the Technical Specifications Date of Issuance: February 1, 2018

ATTACHMENT TO LICENSE AMENDMENT NO. 256 H.B. ROBINSON STEAM ELECTRIC PLANT, UNIT NO. 2 RENEWED FACILITY OPERATING LICENSE NO. DPR-23 DOCKET NO. 50-261 Replace the following page of the Renewed Facility Operating License with the attached revised page. The revised page is identified by amendment number and contains marginal lines indicating the area of change.

Remove Page DPR-23, page 3 Insert Page DPR-23, page 3 Replace the following pages of the Appendix A Technical Specifications with the attached revised pages. The revised pages are identified by amendment number and contain marginal lines indicating the areas of change.

Remove Pages 1.3-1 3.0-2 3.0-4 Insert Pages 1.3-1 1.3-1 a 3.0-2 3.0-4

3 D.

Pursuant to the Act and 1 O 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 and equipment calibration or associated with radioactive apparatus or components; E.

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

3.

This renewed license shall be deemed to contain and is subject to the conditions specified in the following Commission regulations: 10 CFR Part 20, Section 30.34 of 10 CFR Part 30, Section 40.41 of 10 CFR Part 40, Section 50.54 and 50.59 of 1 O CFR Part 50, and Section 70.32 of 10 CFR Part 70; 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:

A.

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

B.

Technical Specifications The Technical Specifications contained in Appendix A, as revised through Amendment No. 256 are hereby incorporated in the license. The licensee shall operate the facility in accordance with the Technical Specifications.

(1)

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

Renewed Facility Operating License No. DPR-23 Amendment No. 256

Completion Times 1.3 1.0 USE AND APPLICATION 1.3 Completion Times PURPOSE BACKGROUND DESCRIPTION HBRSEP Unit No. 2 The purpose of this section is to establish the Completion Time convention and to provide guidance for its use.

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).

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 an inoperable diesel generator, inoperable when the redundant required feature(s) are inoperable. The Completion Time states, "4 hours4.62963e-5 days <br />0.00111 hours <br />6.613757e-6 weeks <br />1.522e-6 months <br /> from discovery of Condition B concurrent with inoperability of redundant required feature(s)." In this case the Completion Time does not begin until the conditions in the Completion Time are satisfied.

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

(continued) 1.3-1 Amendment No. 256

Completion Times 1.3 1.3 Completion Times DESCRIPTION (continued)

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

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

(continued) 1.3-1 a Amendment No. 256

LCO Applicability 3.0 3.0 LCO APPLICABILITY LCO 3.0.4 (continued)

LCO 3.0.5 LCO 3.0.6 HBRSEP Unit No. 2

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, or
b. After performance of a risk assessment addressing inoperable systems and components, consideration of the results, determination of the acceptability of entering the MODE or other specified condition in the Applicability, and establishment of risk management actions, if appropriate (exceptions to this Specification are stated in the individual Specifications); or
c. When an allowance is stated in the individual value, parameter, or other Specification.

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

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.

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 (continued) 3.0-2 Amendment No. 256

LCO Applicability 3.0 3.0 SURVEILLANCE REQUIREMENT (SR) APPLICABILITY SR 3.0.1 SR 3.0.2 SR 3.0.3 HBRSEP Unit No. 2 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.

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.

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

(continued) 3.0-4 Amendment No. 256

UNITED STATES NUCLEAR REGULATORY COMMISSION WASHINGTON, D.C. 20555-0001 SAFETY EVALUATION BY THE OFFICE OF NUCLEAR REACTOR REGULATION RELATED TO AMENDMENT NOS. 298 AND 294 TO RENEWED FACILITY OPERATING LICENSE NOS.NPF-35 AND NPF-52 AMENDMENT NO. 162 TO RENEWED FACILITY OPERATING LICENSE NO. NPF-63 AMENDMENT NOS. 307 AND 286 TO RENEWED FACILITY OPERATING LICENSE NOS. NPF-9 AND NPF-17 AMENDMENT NOS. 407,409, AND 408 TO RENEWED FACILITY OPERATING LICENSE NOS. DPR-38, DPR-47, AND DPR-55 AMENDMENT NO. 256 TO RENEWED FACILITY OPERATING LICENSE NO. DPR-23 DUKE ENERGY CAROLINAS, LLC AND DUKE ENERGY PROGRESS, LLC CATAWBA NUCLEAR STATION, UNITS 1 AND 2 DOCKET NOS. 50-413. 50-414 SHEARON HARRIS NUCLEAR POWER PLANT, UNIT NO. 1 DOCKET NO. 50-400 MCGUIRE NUCLEAR STATION, UNITS 1 AND 2 DOCKET NOS. 50-369, 50-370 OCONEE NUCLEAR STATION, UNIT NOS. 1, 2, AND 3 DOCKET NOS. 50-269, 50-270, 50-287 H. B. ROBINSON STEAM ELECTRIC PLANT, UNIT NO. 2 DOCKET NO. 50-261

1.0 INTRODUCTION

By application dated July 18, 2017, as supplemented by letter dated October 12, 2017, (Agencywide Documents Access and Management System (ADAMS) Accession Nos.

ML17199F771 and ML17285A052, respectively), Duke Energy Carolinas, LLC and Duke Energy Progress, LLC (Duke Energy, the licensee) submitted a license amendment request to the U. S. Nuclear Regulatory Commission (NRG, the Commission) for the Catawba Nuclear Station, Units 1 and 2 (CNS); Shearon Harris Nuclear Power Plant, Unit 1 (HNP); McGuire Nuclear Station, Units 1 and 2 (MNS); Oconee Nuclear Station, Unit Nos. 1, 2, and 3 (ONS);

and H. B. Robinson Steam Electric Plant, Unit No. 2 (RNP) (the facilities). 0 The amendments would revise and clarify the technical specification (TS) usage rules for completion times, limiting conditions for operation (LCOs ), and surveillance requirements (SRs) based on Technical Specification Task Force (TSTF) Traveler TSTF-529, "Clarify Use and Application Rules," Revision 4 (ADAMS Accession No. ML16062A271 ). The licensee proposed variations from the TS changes described in TSTF-529 that will be addressed in the applicable sections of this safety evaluation (SE).

The supplement dated October 12, 2017, provided additional information that clarified the application, did not expand the scope of the application as originally noticed, and did not change the NRG staff's original proposed no significant hazards consideration determination as published in the Federal Register on August 29, 2017 (82 FR 41067).

2.0

2.1 REGULATORY EVALUATION

Description of Subject TS Sections As specified in Title 10 of the Code of Federal Regulations (10 CFR) Section 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).

CNS, MNS, ONS, and RNP, 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.

Regarding HNP, the licensee identified the following variation.

HNP has not converted to the NUREG-1431 improved Standard Technical Specifications (STS). [... ] the HNP TS do not include a section on Completion Times similar to STS TS 1.3. Hence, the STS TS 1.3 changes included in TSTF-529 are not applicable.

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 changes that TSTF-529, Revision 4, makes to STS Section 1.3, LCO 3.0.4, and SR 3.0.3 are independent of each other and licensees may choose to adopt them separately. For each facility, the licensee proposed to make changes to the TSs based on TSTF-529, Revision 4.

Due to plant-specific differences, the licensee did not request the complete set of changes in TSTF-529, Revision 4, for HNP and ONS. The licensee's proposed TS changes are described below.

2.2.1 Proposed Changes to "Time of Discovery" CNS, MNS, ONS, and RNP, 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.

CNS, MNS, ONS, and RNP, 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 CNS, MNS, ONS, and RNP, 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 SE.

2.2.2 Proposed Addition to "Time of Discovery" The licensee proposed to add the following paragraph to the CNS, MNS, and RNP, 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 [diesel generator] set inoperable when its required redundant feature(s) is inoperable. The Completion Time states, "4 hours4.62963e-5 days <br />0.00111 hours <br />6.613757e-6 weeks <br />1.522e-6 months <br /> from discovery of Condition B concurrent with inoperability of redundant required feature(s)." In this case the Completion Time does not begin until the conditions in the Completion Time are satisfied.

The licensee proposed to add a different paragraph to the ONS, TS Section 1.3 under, "Description," using a different example since ONS LCO 3.8.1 does not address diesel generators. The licensee explained the variation as follows:

Consistent with the plant design, ONS LCO 3.8.1 does not address diesel generators.

As described in ONS Bases 3.8.1, the onsite standby power sources are the Keowee Hydro Units (KHU), and the standby buses can also receive power from a combustion turbine generator at the Lee Steam Station through a dedicated 100 kV transmission line. Therefore, the proposed change for ONS TS 1.3 includes an alternate example.

Specifically, Required Action C.2.2.1 of ONS LCO 3.8.1 regarding the Lee Combustion Turbine (LCT) is discussed as an example, in lieu of Required Action B.2.

Accordingly, the licensee proposed to add the following paragraph to the ONS, 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 C.2.2.1, requires energizing both standby buses from the Lee Combustion Turbine (LCT) via the isolated power path. The Completion Time states, "72 hours8.333333e-4 days <br />0.02 hours <br />1.190476e-4 weeks <br />2.7396e-5 months <br /> AND 1 hour1.157407e-5 days <br />2.777778e-4 hours <br />1.653439e-6 weeks <br />3.805e-7 months <br /> from subsequent discovery of deenergized standby bus." In this case the 1-hour Completion Time does not begin until the conditions in the Completion Time (i.e., discovery of the deenergized standby bus) 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" CNS, MNS, ONS, and RNP, 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 include the following sentence at the beginning of the paragraph added to CNS, MNS, ONS, and RNP, TS Section 1.3 (described in Section 2.2.2 of this SE),

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:

and 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.

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 CNS and MNS, 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; or

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.

RNP, 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, or

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.

Regarding ONS and HNP, the licensee identified the following variation.

LCO 3.0.4.a, LCO 3.0.4.b, and LCO 3.0.4.c were introduced into the STS via TSTF-359.

TSTF-359 has not been adopted by ONS or HNP; hence, this portion of the TSTF-529 change is not applicable to ONS or HNP.

The licensee proposed to clarify LCO 3.0.4.b, for CNS, MNS, and RNP, by removing the semicolon after appropriate and placing the statement regarding exceptions in parenthesis.

Note, that RNP has ending commas for LCO 3.0.4.a and LCO 3.0.4.b. Accordingly, the licensee also proposed to clarify LCO 3.0.4.b, for RNP, by replacing the ending comma with a semicolon. The proposed, CNS and MNS, 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; or

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 proposed, RNP, 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, or

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 SR 3.0.3 or its Equivalent CNS, MNS, and ONS, TS SR 3.0.3 currently states the following:

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

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

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

RNP TS SR 3.0.3 is the same as CNS, MNS, and ONS except that there is no comma in the last sentence of the first paragraph. Thus the RNP, TS SR 3.0.3 currently states the following:

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

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

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

Regarding HNP, the licensee identified the following variation.

HNP has not converted to the NUREG-1431 improved Standard Technical Specifications (STS). Therefore, the general format and numbering convention associated with the current TS has been retained. In particular, HNP TS 4.0.3 is the corresponding TS associated with the TSTF-529 changes for STS SR 3.0.3.

HNP, TS SR 4.0.3 currently states the following:

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

If the surveillance is not performed within the delay period, the LCO must immediately be declared not met, and the applicable ACTION requirements must be met.

When the surveillance is performed within the delay period and the surveillance criteria are not met, the LCO must immediately be declared not met, and the applicable ACTION requirements must be met.

The licensee proposed the following changes to CNS, MNS, and ONS, 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 hours2.777778e-4 days <br />0.00667 hours <br />3.968254e-5 weeks <br />9.132e-6 months <br /> or up to the limit of the specified Frequency, whichever is greater. This delay period is permitted to allow performance of the Surveillance. The delay period is only applicable when there is a reasonable expectation the surveillance will be met when performed. A risk evaluation shall be performed for any Surveillance delayed greater than 24 hours2.777778e-4 days <br />0.00667 hours <br />3.968254e-5 weeks <br />9.132e-6 months <br />, and the risk impact shall be managed.

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

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

The licensee proposed the following changes to RNP, 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 hours2.777778e-4 days <br />0.00667 hours <br />3.968254e-5 weeks <br />9.132e-6 months <br /> or up to the limit of the specified Frequency, whichever is greater. This delay period is permitted to allow performance of the Surveillance. The delay period is only applicable when there is a reasonable expectation the surveillance will be met when performed. A risk evaluation shall be performed for any Surveillance delayed greater than 24 hours2.777778e-4 days <br />0.00667 hours <br />3.968254e-5 weeks <br />9.132e-6 months <br /> and the risk impact shall be managed.

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

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

The licensee proposed the following changes to HNP, TS SR 4.0.3 {the additional sentence is underlined):

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

If the surveillance is not performed within the delay period, the LCO must immediately be declared not met, and the applicable ACTION requirements must be met.

When the surveillance is performed within the delay period and the surveillance criteria are not met, the LCO must immediately be declared not met, and the applicable ACTION requirements must be met.

The adequacy of these changes is discussed in Section 3.1.3 of this SE.

2.3 Regulatory Requirements and Guidance Per 10 CFR 50.36(b ), each license authorizing operation of a utilization facility will include TSs.

The TSs will be derived from the analyses and evaluations included in the safety analysis report, and amendments thereto, submitted pursuant to 10 CFR 50.34 (describing the technical information to be included in applications for an operating license). Pursuant to 10 CFR 50.36(c), TSs are required to include items in the following five specific categories related to station operation: (1) safety limits, limiting safety system settings, and limiting control settings; (2) LCOs; (3) SRs; (4) design features; and (5) administrative controls. The Commission may include such additional TSs as the Commission finds appropriate.

The regulations in 10 CFR 50.36(c)(2) establish the requirements for LCOs. LCOs are the lowest functional capability or performance level of equipment required for the safe operation of the facility. When an LCO is not met, the licensee must shut down the reactor or follow any remedial action permitted by the TSs until the LCO can be met.

The regulations in 10 CFR 50.36(c)(3) establish the requirements for SRs. SRs 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 staffs guidance for review of the TSs is in Chapter 16, "Technical Specifications," of NUREG-0800, "Standard Review Plan for the Review of Safety Analysis Reports for Nuclear Power Plants: LWR [Light-Water Reactor] Edition," Revision 3, dated March 2010 (ADAMS Accession No. ML100351425). As described therein, as part of the regulatory standardization effort, the staff has prepared improved STS (NUREG-1430 through NUREG-1434) for each of the LWR nuclear steam supply systems and associated balance-of-plant equipment systems.

The licensee's proposed amendments are based on TSTF-529, Revision 4, which is an NRG-approved change to the current STS. The NRC staff's review includes consideration of whether the proposed changes are consistent with the current STS, as modified by TSTF-529, Revision 4. Special attention is given to TS provisions that depart from the improved STS, 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' TSs against what is required to be in the TSs 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 CNS, MNS, ONS, and RNP TS Section 1.3 (quoted in Section 2.2.1 of this SE). Throughout the CNS, MNS, ONS, and RNP 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 TSs. This provides clarity to the term "discovery," and therefore provides a clear and objective application of the TSs Required Actions and associated Completion Times. The change is editorial since it does not change requirements currently in TSs. 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 CNS, MNS, and RNP, 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 hours4.62963e-5 days <br />0.00111 hours <br />6.613757e-6 weeks <br />1.522e-6 months <br /> from discovery of Condition B concurrent with inoperability of redundant required feature(s)." In this case the Completion Time does not begin until the conditions in the Completion Time are satisfied.

Similarly, the licensee proposed to add the following paragraph to the ONS, 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 C.2.2.1, requires energizing both standby buses from the Lee Combustion Turbine (LCT) via the isolated power path. The Completion Time states, "72 hours8.333333e-4 days <br />0.02 hours <br />1.190476e-4 weeks <br />2.7396e-5 months <br /> AND 1 hour1.157407e-5 days <br />2.777778e-4 hours <br />1.653439e-6 weeks <br />3.805e-7 months <br /> from subsequent discovery of deenergized standby bus." In this case the 1-hour Completion Time does not begin until the conditions in the Completion Time (i.e., discovery of the deenergized standby bus) 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 staffs expectation that a senior licensed operator on the operating shift crew with responsibility for plant operations makes the determination that an LCO is not met and a Condition is entered. The phrase "and an ACTIONS Condition is entered" in the above proposed insertion, is necessary to accommodate circumstances in which LCO 3.0.6 allows an LCO to not be met without entry into the Conditions. In those circumstances, a Completion Time does not begin. In addition, an example is added to the proposed insertion in order to illustrate the concept presented. The NRC staff finds the alternative example for ONS acceptable since it is consistent with the plant design and it provides a comparable alternate 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 CNS, MNS, ONS, and RNP 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, CNS, MNS, and RNP, TS 3.8.1, "AC [alternating current]

Sources - Operating," Required Action 8.2 (ONS uses an alternative example as discussed in Section 3.1.1.2 of the SE), 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 hours4.62963e-5 days <br />0.00111 hours <br />6.613757e-6 weeks <br />1.522e-6 months <br /> from discovery of Condition B concurrent with inoperability of redundant required feature(s)." In this case, the Completion Time does not begin until the conditions in the Completion Time are satisfied.

As discussed in Section 2.2.3 of this SE, the licensee proposed to include the following sentence at the beginning of the paragraph added to CNS, MNS, ONS, and RNP, TS Section 1.3 (described in Section 2.2.2 of this SE), 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:

and 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.

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.1.4 Technical Conclusion Regarding Changes to TS Section 1.3 As discussed above, the amendments for CNS, MNS, ONS, and RNP would revise and clarify the TS usage rules for completion times associated with required actions for conditions where an LCO is not met. The NRC staff concludes that the licensee will continue to meet 10 CFR 50.36(c)(2) with the proposed changes because the TSs for each of these facilities will continue to specify appropriate remedial actions for the licensee to follow until the LCO can be met.

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 CNS, MNS, and RNP, contains three options (i.e., a, b, and c). Paragraphs a and b for CNS and MNS end with"; or" and for RNP ends with", or".

The LCO 3.0.4.b statement: "After performance of a risk assessment... stated in the individual Specifications; [, for RNP] 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 LCO 3.0.4.b, for CNS, MNS, and RNP, by removing the semicolon after "appropriate" and placing the statement regarding exceptions in parenthesis.

The licensee also proposed to clarify the LCO 3.0.4.b, for RNP, by replacing the ending comma with a semicolon. The proposed TS LCO 3.0.4.b statement for CNS, MNS, and RNP 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. Therefore, with the proposed changes to LCO 3.0.4, the requirements in 10 CFR 50.36(c)(2) will continue to be met at CNS, MNS, and RNP.

3.1.3 Proposed Changes to SR 3.0.3 The NRC has typically interpreted TS SR 3.0.3 (or its equivalent), 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 (or its equivalent) 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 (or its equivalent) 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 (or its equivalent) 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 CNS, MNS, and ONS, 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 hours2.777778e-4 days <br />0.00667 hours <br />3.968254e-5 weeks <br />9.132e-6 months <br /> or up to the limit of the specified Frequency, whichever is greater. This delay period is permitted to allow performance of the Surveillance. The delay period is only applicable when there is a reasonable expectation the surveillance will be met when performed. A risk evaluation shall be performed for any Surveillance delayed greater than 24 hours2.777778e-4 days <br />0.00667 hours <br />3.968254e-5 weeks <br />9.132e-6 months <br />, and the risk impact shall be managed.

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

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

The licensee proposed the following changes to RNP, 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 hours2.777778e-4 days <br />0.00667 hours <br />3.968254e-5 weeks <br />9.132e-6 months <br /> or up to the limit of the specified Frequency, whichever is greater. This delay period is permitted to allow performance of the Surveillance. The delay period is only applicable when there is a reasonable expectation the surveillance will be met when performed. A risk evaluation shall be performed for any Surveillance delayed greater than 24 hours2.777778e-4 days <br />0.00667 hours <br />3.968254e-5 weeks <br />9.132e-6 months <br /> and the risk impact shall be managed.

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

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

The licensee proposed the following changes to HNP, TS SR 4.0.3 (the additional sentence is underlined):

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

If the surveillance is not performed within the delay period, the LCO must immediately be declared not met, and the applicable ACTION requirements must be met.

When the surveillance is performed within the delay period and the surveillance criteria are not met, the LCO must immediately be declared not met, and the applicable ACTION requirements must be met.

For each facility, the licensee stated in the revised TS Bases pages included with the application that many factors should be considered when determining if there is a reasonable expectation that the SR will be met when performed. The factors identified include, but are not limited to, the period of time since the SR was last performed, whether the SR (or a portion thereof) has ever been performed, and any other indications, tests, or activities that might support the expectation that the SR will be met when performed. The licensee further states:

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 a Surveillance will be met when performed should increase based on the length of time since the last performance of the Surveillance. If the Surveillance has been performed recently, a review of the Surveillance history and equipment performance may be sufficient to support a reasonable expectation that the Surveillance will be met when performed. For Surveillances 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 OPERABLE. The evaluation should be documented in sufficient detail to allow a knowledgeable individual to understand the basis for the determination.

The NRC staff finds that the delay period allowed by SR 3.0.3 (or its equivalent) offers adequate time to complete SRs that have been missed, including those that have never been 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 be met when performed. The staff finds that the proposed change, which expands the scope of SR 3.0.3 (or its equivalent) to SRs that have never been performed, is acceptable because the licensee must determine that there is a reasonable expectation the SR will be met when performed. Therefore, with the proposed change to SR 3.0.3 (or its equivalent), the staff concludes that 10 CFR 50.36(c)(2) and 10 CFR 50.36(c)(3) will continue to be met at each of the licensee's facilities.

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

4.0 STATE CONSULTATION

In accordance with the Commission's regulations, the North Carolina and South Carolina State officials were notified of the proposed issuance of the amendments on December 7, 2017. The State officials had no comments.

5.0 ENVIRONMENTAL CONSIDERATION

The amendments change requirements with respect to the installation or use of facility components located within the restricted areas as defined in 10 CFR Part 20 and change SRs.

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, which was published in the Federal Register on August 29, 2017 (82 FR 41067), that the amendments involve no significant hazards consideration, and there has been no public comment on such finding.

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: Dennis Galvin Date: February 1, 2018

ML17340A720 OFFICE DORL/LPL2-2/PM DORL/LPL2-2/LA NAME DGalvin BClayton DATE 01/17/18 12/15/17 OFFICE OGC DORL/LPL2-2/BC NAME DRoth*

UShoop (RSchaaf for)

DATE 01/26/18 02/01/18