Text

Application to Revise Technical Specifications to Adopt TSTF-529 11 Clarify Use and Application Rules, 11 Revision 4
	ML19032A256
Person / Time
Site:	Palisades, Indian Point, Grand Gulf, Arkansas Nuclear, River Bend, Waterford
Issue date:	01/31/2019
From:	Halter M; Entergy Nuclear Operations, Entergy Operations
To:	; Document Control Desk, Office of Nuclear Reactor Regulation
References
	CNRO-2019-00003, TSTF-529, Rev 4
	Download: ML19032A256 (201)
	v • d • e

Entergy Operations, Inc. and Entergy Nuclear Operations, Inc.

-===* Enterµv 1340 Echelon Parkway Jackson, MS 39213 bJ@ Tel 601-368-5573 Mandy K. Halter Director, Nuclear Licensing 10 CFR 50.90 CNR0-2019-00003 January 31, 2019 ATTN: Document Control Desk U.S. Nuclear Regulatory Commission Washington, DC 20555-0001 11

Subject:

Application to Revise Technical Specifications to Adopt TSTF-529 Clarify Use 11 and Application Rules, Revision 4 Arkansas Nuclear One, Units 1 and 2 N RC Docket Nos. 50-313 and 50-368 Renewed Facility Operating License Nos. DPR-51 and NPF-6 Grand Gulf Nuclear Station, Unit 1 NRG Docket No. 50-416 Renewed Facility Operating License No. NPF-29 Indian Point Nuclear Generating Units 2 and 3 NRG Docket Nos. 50-247 and 50-286 Renewed Facility Operating License Nos. DPR-26 and DPR-64 Palisades Nuclear Plant NRG Docket No. 50-255 Renewed Facility Operating License No. DPR-20 River Bend Station, Unit 1 N RC Docket No. 50-458 Renewed Facility Operating License No. NPF-47 Waterford Steam Electric Station, Unit 3 NRG Docket No. 50-382 Renewed Facility Operating License No. NPF-38 In accordance with Title 1O of the Code of Federal Regulations (CFR) Part 50, Section 50.90, 11 Application for amendment of license, construction permit, or early site permit, Entergy 11 Operations, Inc. and Entergy Nuclear Operations, Inc. (collectively referred to as Entergy) are submitting a request for an amendment to Renewed Facility Operating License, Appendix A, Technical Specifications (TS) for Arkansas Nuclear One, Units 1 and 2; Grand Gulf Nuclear 11 11

CNR0-2019-00003 Page 2 of 4 Station, Unit 1; Indian Point Nuclear Generating Units 2 and 3; Palisades Nuclear Plant; River Bend Station, Unit 1; and Waterford Steam Electric Station, Unit 3.

The proposed changes revise TS Section 1.3, "Completion Times," and TS Section 3.0, "LCO Applicability" to clarify the use and application of the TS usage rules. These proposed changes are consistent with NRG-approved Technical Specifications Task Force (TSTF) Traveler TSTF-529, "Clarify Use and Application Rules," Revision 4.

The Enclosure to this letter provides a description and assessment of the proposed changes.

Attachments 1.a through 1.f provide the existing TS pages marked-up to show the proposed changes. Attachments 2.a through 2.f provide revised (clean) TS pages. Attachments 3.a through 3.f provide, for information only, marked up versions of existing TS Bases pages to show the proposed changes.

This letter contains no new regulatory commitments.

Entergy requests approval of the proposed license amendment by February 1, 2020. The proposed changes would be implemented within 90 days of issuance of the amendment.

Should you have any questions or require additional information, please contact Stephenie Pyle at (601) 368-5516.

In accordance with 10 CFR 50.91, "Notice for public comment; State consultation," paragraph (b), a copy of this application, with attachments, is being provided to the designated State Officials.

I declare under penalty of perjury, the foregoing is true and correct. Executed on 31st day of January 2019.

Respectfully, 4

Jna~J{l?d~t_

Mandy K. Halter MKH/jls

CNR0-2019-00003 Page 3 of 4

Enclosure:

Description and Assessment of the Proposed Changes Attachments:

1.a. Markup of Technical Specification (TS) Pages - Arkansas Nuclear One, Units 1 and 2 1.b. Markup of Technical Specification (TS) Pages - Grand Gulf Nuclear Station, Unit 1 1.c. Markup of Technical Specification (TS) Pages - Indian Point Nuclear Generating Units 2 and 3 1.d. Markup of Technical Specification (TS) Pages - Palisades Nuclear Plant 1.e. Markup of Technical Specification (TS) Pages - River Bend Station, Unit 1 1.f. Markup of Technical Specification (TS) Pages - Waterford Steam Electric Station, Unit 3 2.a. Clean Technical Specification (TS) Pages -Arkansas Nuclear One, Units 1 and 2 2.b. Clean Technical Specification (TS) Pages - Grand Gulf Nuclear Station, Unit 1 2.c. Clean Technical Specification (TS)* Pages - Indian Point Nuclear Generating Units 2 and 3 2.d. Clean Technical Specification (TS) Pages - Palisades Nuclear Plant 2.e. Clean Technical Specification (TS) Pages - River Bend Station, Unit 1 2.f. Clean Technical Specification (TS) Pages - Waterford Steam Electric Station, Unit 3 3.a. Markup of Technical Specification (TS) Bases Pages - For Information Only-Arkansas Nuclear One, Units 1 and 2 3.b. Markup of Technical Specification (TS) Bases Pages - For Information Only-Grand Gulf Nuclear Station, Unit 1 3.c. Markup of Technical Specification (TS) Bases Pages - For Information Only-Indian Point Nuclear Generating Units 2 and 3 3.d. Markup of Technical Specification (TS) Bases Pages - For Information Only-Palisades Nuclear Plant 3.e. Markup of Technical Specification (TS) Bases Pages - For Information Only-River Bend Station, Unit 1 3.f. Markup of Technical Specification (TS) Bases Pages - For Information Only-Waterford Steam Electric Station, Unit 3

CNR0-2019-00003 Page 4 of 4 cc: NRC Region I - Regional Administrator NRC Region Ill - Regional Administrator NRC Region IV - Regional Administrator NRC Senior Resident Inspector - Arkansas Nuclear One, Units 1 and 2 NRC Senior Resident Inspector - Grand Gulf Nuclear Station, Unit 1 NRC Senior Resident Inspector - Indian Point Nuclear Generating Units 2 and 3 NRC Senior Resident Inspector - Palisades Nuclear Plant NRC Senior Resident Inspector - River Bend Station, Unit 1 NRC Senior Resident Inspector - Waterford Steam Electric Station, Unit 3 NRC Project Manager - Entergy Fleet Arkansas Department of Health, Radiation Control Section State Health Officer, Mississippi Department of Health President and CEO, NYSERDA New York State Public Service Commission Michigan Department of Environmental Quality Louisiana of Department of Environmental Quality

bee w/o attachments:

L. Coyle J. Ventosa Site Vice President - Arkansas Nuclear One, Units 1 and 2 Site Vice President - Grand Gulf Nuclear Station, Unit 1 Site Vice President - Indian Point Nuclear Generating Units 2 and 3 Site Vice President - Palisades Nuclear Plant Site Vice President - River Bend Station, Unit 1 Site Vice President -Waterford Steam Electric Station, Unit 3 K. Jury R. Gaston M. Halter J. Giddens S. Pyle bee w/ attachments:

NRC Project Manager - Arkansas Nuclear One, Units 1 and 2 NRC Project Manager - Grand Gulf Nuclear Station, Unit 1 NRC Project Manager - Indian Point Nuclear Generating Units 2 and 3 NRC Project Manager- Palisades Nuclear Plant NRC Project Manager - River Bend Station, Unit 1 NRC Project Manager - Waterford Steam Electric Station, Unit 3 Regulatory Assurance Manager -Arkansas Nuclear One, Units 1 and 2 Regulatory Assurance Manager - Grand Gulf Nuclear Station, Unit 1 Regulatory Assurance Manager - Indian Point Nuclear Generating Units 2 and 3 Regulatory Assurance Manager - Palisades Nuclear Plant Regulatory Assurance Manager - River Bend Station, Unit 1 Regulatory Assurance Manager - Waterford Steam Electric Station, Unit 3 George Vickery - Corporate Operations David Bice - ANO Licensing Ryan Sexton - Grand Gulf Licensing Mahvash Mirzai - IPEC Licensing Jim Miksa - Palisades Licensing Bridget Johns - River Bend Licensing Maria Zamber - Waterford Licensing John Schrage - Corporate Regulatory Assurance

ENCLOSURE CNR0-2019-00003 Description and Assessment of the Proposed Changes Application to Revise Technical Specifications to Adopt 11 TSTF-529 "Clarify Use and Application Rules, Revision 4 Arkansas Nuclear One, Units 1 and 2 Grand Gulf Nuclear Station, Unit 1 Indian Point Nuclear Generating Units 2 and 3 Palisades Nuclear Plant River Bend Station, Unit 1 Waterford Steam Electric Station, Unit 3 (6 Pages) 1.0 Description 2.0 Assessment 2.1 Applicability of Published Safety Evaluation 2.2 Variations 3.0 Regulatory Analysis 3.1 No Significant Hazards Determination 4.0 Environmental Consideration 5.0 References

CNR0-2019-00003 Enclosure Page 1 of 6 1.0 Description In accordance with Title 10 of the Code of Federal Regulations (CFR) Part 50, Section 50.90, "Application for amendment of license, construction permit, or early site permit," Entergy Operations, Inc. and Entergy Nuclear Operations, Inc.

(collectively referred to as Entergy) are submitting a request for an amendment to the Renewed Facility Operating License (RFOL), Appendix A, 'Technical Specifications" (TS) for Arkansas Nuclear One, Units 1 and 2 (AN0-1 and AN0-2, collectively referred to as ANO); Grand Gulf Nuclear Station, Unit 1 (GGNS); Indian Point (IP)

Nuclear Generating Units 2 and 3 (IP2 and IP3, collectively referred to as IPEC);

Palisades Nuclear Plant (PNP); River Bend Station, Unit 1 (RBS); and Waterford Steam Electric Station, Unit 3.

The proposed changes revise TS Section 1.3, "Completion Times, and TS Section 11 3.0, "LCO Applicability" to clarify the use and application of the TS usage rules, as described below. These proposed changes are consistent with NRG-approved Technical Specifications Task Force (TSTF) Traveler TSTF-529, "Clarify Use and 11 Application Rules, Revision 4:

TS Section 1.3, is revised to clarify "discovery" and to discuss exceptions to starting the Completion Time at condition entry.

Limiting Condition for Operation (LCO) 3.0.4.b is revised to clarify that LCO 3.0.4.a, LCO 3.0.4.b, and LCO 3.0.4.c are independent options.

Surveillance Requirement (SR) 3.0.3 (or equivalent) is revised to allow application of SR 3.0.3 when an SR has not been previously performed and to clarify the application of SR 3.0.3.

2.0 Assesment 2.1 Applicability of Published Safety Evaluation Entergy has reviewed the Nuclear Regulatory Commission (NRG) Safety Evaluation (SE) for TSTF-529, Revision 4 (ADAMS Accession No. ML16060A440), which was transmitted to the TSTF in a letter dated April 21, 2016 (ADAMS Accession No. ML16060A455). This included a review of the NRG SE, as well as the information provided in TSTF-529. Entergy has concluded that the justifications presented in TSTF-529 proposal and the NRG SE are applicable to ANO, GGNS, IPEC, PNP, RBS, and Waterford and justify this amendment for the incorporation of the changes to each plant's TS.

CNR0-2019-00003 Enclosure Page 2 of 6 2.2 Variations Entergy is proposing the following variations from the TS or TS Bases changes described in TSTF-529. These variations do not affect the applicability of TSTF-529 or the NRC SE to the proposed license amendment.

2.2.1 AN0-1 None 2.2.2 AN0-2

i. AN0-2 TS Section 1.0, "Definitions" does not currently include a definition for "Completion Time." As a result, the proposed changes to the AN0-2 TS do not include the TSTF-529 revision to TS 1.3, "Completion Time." This variation is administrative, and consistent with the current AN0-2 TS, as well as the underlying basis for the current AN0-2 TS (i.e., NUREG-0212, "Standard Technical Specifications for Combustion Engineering Pressurized Water Reactors"). In addition, as discussed in TSTF-529, omission of one or more changes is an acceptable variation from the traveler.

ii. The current AN0-2 TS format, numbering, and terminology is consistent with the NUREG-0212 Standard Technical Specifications (STS). The NUREG-0212 STS numbering for survejllance requirements differs from the numbering in NUREG-1432, "Standard Technical Specifications Combustion Engineering Plants," (i.e., the Improved STS which were used to develop TSTF-529). As a result, the TSTF-529 revision to SR 3.0.3 has been incorporated into proposed changes to AN0-2 TS 4.0.3. This variation is administrative, consistent with the current AN0-2 TS, as well as the underlying NUREG-0212 basis for the current AN0-2 TS, and does not affect the applicability of TSTF-529 to th,e AN0-2 TS.

iii. Similarly, the TSTF-529 revision to TS Bases LCO 3.0.5 and TS Bases SR 3.0.3 have been incorporated into proposed changes to AN0-2 TS Bases LCO 3.0.6 and AN0-2 TS Bases SR 4.0.3, respectively. These variations are administrative, consistent with the current AN0-2 TS, as well as the underlying NUREG-0212 basis for the current AN0-2 TS, and do not affect the applicability of TSTF-529 to the AN0-2 TS.

iv. AN0-2 TS SR 4.0.3 refers to "specified surveillance interval," which is consistent with NUREG-0212, but represents a variation from the NUREG-1432 SR 3.0.3 terminology, which refers to "specified Frequency." This variation is administrative, consistent with the current AN0-2 TS, as well as the underlying NUREG-0212 basis for the current AN0-2 TS, and does not affect the applicability of TSTF-529 to the AN0-2 TS.

CNR0-2019-00003 Enclosure Page 3 of 6 2.2.3 GGNS None 2.2.4 IPEC None 2.2.5 PNP

i. The proposed change to PNP TS 1.3 differs from TSTF-529 TS 1.3 by using 11 11 the current PNP term plant instead of "unit" in the BACKGROUND section (one occurrence) and the DESCRIPTION section (two occurrences). This terminology reflects the licensed name for PNP, which does not specify a unit number. This variation is administrative and consistent with the current PNP TS, and does not affect the applicability of TSTF-529 to the PNP TS.

ii. The format of the proposed change to PNP TS Bases LCO 3.0.5 differs slightly from the TSTF-529 TS Bases LCO 3.0.5 in that the two numbered examples of demonstrating OPERABILITY of other equipment (i.e., on PNP TS Bases page 3.0-8) are on separate lines, as opposed to within the body of the paragraph.

This variation is administrative, consistent with the current PNP TS Bases format, and does not affect the applicability of TSTF-529 to the PNP TS.

2.2.6 RBS

i. The proposed change to RBS TS Bases SR 3.0.3 deletes a site-specific statement that limits the use of a delay period for performance of missed SRs to those surveillances where the initial surveillances have been successfully performed. This deletion is consistent with the TSTF-529 revision to Bases SR 3.0.3 which adds additional requirements for surveillances that have not been performed for a long period of time or that have never been performed.

2.2.7 Waterford

i. Waterford TS Section 1.0, "Definitions" does not currently include a definition for "Completion Time." As a result, the, the proposed changes to the Waterford TS do not include the TSTF-529 revision to TS 1.3, "Completion Time." This variation is administrative, and consistent with the current Waterford TS, as well as the underlying NUREG-0212 basis for the current Waterford TS. In addition, as discussed in TSTF-529, omission of one or more changes is an acceptable variation from the traveler.

ii. The current Waterford TS format, numbering, and terminology is consistent with NUREG-0212. The NUREG-0212 STS numbering for surveillance requirements differs from the numbering in NUREG-1432. As such, the TSTF-529 revision to SR 3.0.3 has been incorporated into proposed changes to Waterford TS 4.0.3. This variation is administrative, consistent with the current Waterford TS, as well as the underlying NUREG-0212 basis for the current Waterford TS, and does not affect the applicability of TSTF-529 to the Waterford TS.

CNR0-2019-00003 Enclosure Page 4 of 6 iii. Similarly, the TSTF-529 revision to TS Bases SR 3.0.3 has been incorporated into proposed changes to Waterford TS Bases SR 4.0.3. This variation is administrative, consistent with the current Waterford TS, as well as the underlying NUREG-0212 basis for the current Waterford TS, and does not affect the applicability of TSTF-529 to the Waterford TS.

iv. Waterford TS SR 4.0.3 refers to "specified surveillance interval," which is consistent with NUREG-0212, but represents a variation from the NUREG-1432 SR 3.0.3 terminology, which refers to "specified Frequency." This variation is administrative, consistent with the current Waterford TS, as well as the underlying NUREG-0212 basis for the current Waterford TS, and does not affect the applicability of TSTF-529 to the Waterford TS.

v. The current Waterford TS 3.0.4 is based on the equivalent TS in NUREG-0212, which is different from TS 3.0.4 in NUREG-1432, Revision 3. Therefore, the proposed Waterford TS changes do not include the TSTF-529 revision to LCO 3.0.4 and Bases LCO 3.0.4. This variation is administrative, and consistent with the current Waterford TS, as well as the underlying NUREG-0212 basis for the current Waterford TS. In addition, as discussed TSTF-529, omission of one or more changes is an acceptable variation from the traveler.

3.0 Regulatory Analysis 3.1 No Significant Hazards Determination Entergy Operations, Inc. and Entergy Nuclear Operations, Inc. (collectively referred to as Entergy) request adoption of NRG-approved Technical Specifications Task Force (TSTF) Traveler TSTF-529, "Clarify Use and Application Rules, 11 Revision 4 into the Technical Specifications (TS) of Arkansas Nuclear One, Units 1 and 2; Grand Gulf Nuclear Station, Unit 1; Indian Point Nuclear Generating Units 2 and 3; Palisades Nuclear Plant; River Bend Station, Unit 1; and Waterford Steam Electric Station, Unit 3.

11 The proposed changes revise Section 1.3, "Completion Times, and Section 3.0, "LCO Applicability" and "SR Applicability" of the TS to clarify the use and application of the TS usage rules and revise the application of Surveillance Requirement (SR) 3.0.3 (or equivalent). Section 1.3 is modified to clarify the concept of "discovery" that a Limiting Condition for Operation (LCO) is not met and to describe existing exceptions to the start of Completion Times in the TS.

An editorial change is made to LCO 3.0.4.b to clarify that LCO 3.0.4.a, LCO 3.0.4.b, and LCO 3.0.4.c are independent options. SR 3.0.3 (or equivalent) is revised to allow application of SR 3.0.3 when an SR has not been previously performed. These proposed changes are consistent with TSTF-529.

Entergy has evaluated whether or not a significant hazards consideration is involved with the proposed amendment by focusing on the three standards set forth in 10 CFR 50.92, "Issuance of amendment, 11 as discussed below:

CNR0-2019-00003 Enclosure Page 5 of 6

1. Does the proposed change involve a significant increase in the probability or consequences of an accident previously evaluated?

Response: No.

The proposed changes to Section 1.3 and LCO 3.0.4 have no effect on the requirement for systems to be Operable and have no effect on the application of TS actions. The proposed change to SR 3.0.3 (or equivalent) states that the allowance may only be used when there is a reasonable expectation the surveillance will be met when performed.

Since the proposed changes do not significantly affect system Operability, the proposed changes will have no significant effect on the initiating events for accidents previously evaluated and will have no significant effect on the ability of the systems to mitigate accidents previously evaluated.

Therefore, it is concluded that these changes do not involve a significant increase in the probability or consequences of an accident previously evaluated.

2. Does the proposed change create the possibility of a new or different kind of accident from any accident previously evaluated?

Response: No.

The proposed changes to the TS usage rules do not affect the design or function of any plant systems. The proposed changes do not change the Operability requirements for plant systems or the actions taken when plant systems are not operable.

Therefore, it is concluded that the changes do not create the possibility of a new or different kind of accident from any accident previously evaluated.

3. Does the proposed change involve a significant reduction in a margin of safety?

Response: No.

The proposed changes clarify the application of Section 1.3 and LCO 3.0.4 and do not result in changes in plant operation. SR 3.0.3 (or equivalent) is revised to allow application of SR 3.0.3 when an SR has not been previously performed if there is reasonable expectation that the SR will be met when performed. This expands the use of SR 3.0.3 while ensuring the affected system is capable of performing its safety function. As a result, plant safety is either improved or unaffected.

Therefore, it is concluded that the changes do not involve a significant reduction in a margin of safety.

CNR0-2019-00003 Enclosure Page 6 of 6 Based on the above, Entergy concludes that the proposed amendments do not present a significant hazards consideration under the standards set forth in 10 CFR 50.92(c), and, accordingly, a finding of "no significant hazards consideration" is justified.

4.0 Environmental Consideration The proposed amendments would change a requirement with respect to installation or use of a facility component located within the restricted area, as defined in Title 10 of the Code of Federal Regulations (CFR) Part 20 (1 O CFR 20), or would change an inspection or surveillance requirement. However, the proposed changes do not involve (i) a significant hazards consideration, (ii) a significant change in the types or significant increase in the amounts of any effluents that may be released offsite, or (iii) a significant increase in individual or cumulative occupational radiation exposure.

Accordingly, the proposed change meets the eligibility criterion for categorical exclusion set forth in 10 CFR 51.22(c)(9). Therefore, pursuant to 10 CFR 51.22(b),

no environmental impact statement or environmental assessment need be prepared in connection with the proposed change.

5.0 References 11 5.1 TSTF-529, Revision 4, "Clarify Use and Application Rules, dated April 25, 2016.

5.2 Final Safety Evaluation of Technical Specifications Task Force Traveler TSTF-529, Revision 4, "Clarify Use and Application Rules" using the Consolidated Line Item Improvement Process (TAC Nos. MF1406 and MF1407) ADAMS Accession Nos. ML16060A455 (Letter/Public);

ML16060A440 (Final SE/Public); ML16060A441 (Package/Public).

ATTACHMENT 1.a CN R0-2019-00003 Markup of Technical Specification (TS) Pages Arkansas Nuclear One, Unit 1 NRC Docket No. 50-313 Renewed Facility Operating License No. DPR-51 Unit 1 TS Pages 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*

3.0-1 3.0-4

Unit 1 TS Pages 1.3-3 through 1.3-10 are included due to repagination only.

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

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

DESCRIPTION The Completion Time is the amount of time allowed for completing a Required Action. It is referenced to the 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.

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 0.00111 hours 6.613757e-6 weeks 1.522e-6 months 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.

AN0-1 1.3-1 Amendment No. ~ .

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 Yme e-f-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 0.00667 hours 3.968254e-5 weeks 9.132e-6 months ; 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.

AN0-1 1.3-2 Amendment No. ~ .

Completion Times 1.3 1.3 Completion Times (continued)

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 0.00222 hours 1.322751e-5 weeks 3.044e-6 months ," 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.

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 8.1 Be in MODE 3. 6 hours6.944444e-5 days 0.00167 hours 9.920635e-6 weeks 2.283e-6 months Action and associated AND Completion Time not met. 8.2 Be in MODE 5. 36 hours4.166667e-4 days 0.01 hours 5.952381e-5 weeks 1.3698e-5 months 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 0.00167 hours 9.920635e-6 weeks 2.283e-6 months AND in MODE 5 within 36 hours4.166667e-4 days 0.01 hours 5.952381e-5 weeks 1.3698e-5 months . A total of 6 hours6.944444e-5 days 0.00167 hours 9.920635e-6 weeks 2.283e-6 months is allowed for reaching MODE 3 and a total of 36 hours4.166667e-4 days 0.01 hours 5.952381e-5 weeks 1.3698e-5 months (not 42 hours4.861111e-4 days 0.0117 hours 6.944444e-5 weeks 1.5981e-5 months ) 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 8.333333e-4 hours 4.960317e-6 weeks 1.1415e-6 months , the time allowed for reaching MODE 5 is the next 33 hours3.819444e-4 days 0.00917 hours 5.456349e-5 weeks 1.25565e-5 months because the total time allowed for reaching MODE 5 is 36 hours4.166667e-4 days 0.01 hours 5.952381e-5 weeks 1.3698e-5 months .

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

AN0-1 1.3-3 Amendment No. ~ ,

Completion Times 1.3 1.3 Completion Times EXAMPLES (continued)

EXAMPLE 1 .3-2 ACTIONS CONDITION REQUIRED ACTION COMPLETION TIME A. One pump A.1 Restore pump to 7 days inoperable. OPERABLE status.

B. Required 8.1 Be in MODE 3. 6 hours6.944444e-5 days 0.00167 hours 9.920635e-6 weeks 2.283e-6 months Action and associated AND Completion Time not met. B.2 Be in MODE 5. 36 hours4.166667e-4 days 0.01 hours 5.952381e-5 weeks 1.3698e-5 months When a pump is declared inoperable, Condition A is entered. If the pump is not restored to OPERABLE status within 7 days, Condition B is also entered and the Completion Time clocks for Required Actions B.1 and B.2 start. If the inoperable pump is restored to OPERABLE status after Condition B is entered, 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, 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.

AN0-1 1.3-4 Amendment No. ~ .

Completion Times 1.3 1.3 Completion Times EXAMPLES (continued)

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 0.00667 hours 3.968254e-5 weeks 9.132e-6 months extension to the stated 7 days is allowed, provided this does not result in the second pump being inoperable for> 7 days.

EXAMPLE 1.3-3 ACTIONS CONDITION REQUIRED ACTION COMPLETION TIME A. One A.1 Restore Function X 7 days Function X train to train OPERABLE AND inoperable. status.

10 days from discovery of failure to meet the LCO B. One 8.1 Restore Function Y 72 hours8.333333e-4 days 0.02 hours 1.190476e-4 weeks 2.7396e-5 months Function Y train to train OPERABLE AND inoperable. status.

10 days from discovery of failure to meet the LCO C. One C.1 Restore Function X 72 hours8.333333e-4 days 0.02 hours 1.190476e-4 weeks 2.7396e-5 months Function X train to train OPERABLE inoperable. status.

AND OR One C.2 Restore Function Y 72 hours8.333333e-4 days 0.02 hours 1.190476e-4 weeks 2.7396e-5 months Function Y train to OPERABLE train status.

inoperable.

AN0-1 1.3-5 Amendment No. ~ .

Completion Times 1.3 1.3 Completion Times EXAMPLES (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.

AN0-1 1.3-6 Amendment No. ~ .

Completion Times 1.3 1.3 Completion Times EXAMPLES (continued)

EXAMPLE 1.3-4 ACTIONS CONDITION REQUIRED ACTION COMPLETION TIME A. One or more A.1 Restore valve(s) to 4 hours4.62963e-5 days 0.00111 hours 6.613757e-6 weeks 1.522e-6 months valves OPERABLE inoperable. status.

B. Required 8.1 Be in MODE 3. 6 hours6.944444e-5 days 0.00167 hours 9.920635e-6 weeks 2.283e-6 months Action and associated AND Completion Time not met. 8.2 Be in MODE 4. 12 hours1.388889e-4 days 0.00333 hours 1.984127e-5 weeks 4.566e-6 months 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 0.00111 hours 6.613757e-6 weeks 1.522e-6 months provided this does not result in any subsequent valve being inoperable for> 4 hours4.62963e-5 days 0.00111 hours 6.613757e-6 weeks 1.522e-6 months .

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

AN0-1 1.3-7 Amendment No. ~ .

Completion Times 1.3 1.3 Completion Times EXAMPLES (continued)

EXAMPLE 1.3-5 ACTIONS

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

Se pa rate Condition entry is allowed for each inoperable valve.

CONDITION REQUIRED ACTION COMPLETION TIME A. One or more A.1 Restore valve to 4 hours4.62963e-5 days 0.00111 hours 6.613757e-6 weeks 1.522e-6 months valves OPERABLE inoperable. status.

B. Required 8.1 Be in MODE 3. 6 hours6.944444e-5 days 0.00167 hours 9.920635e-6 weeks 2.283e-6 months Action and associated AND Completion Time not met. 8.2 Be in MODE 4. 12 hours1.388889e-4 days 0.00333 hours 1.984127e-5 weeks 4.566e-6 months 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.

AN0-1 1.3-8 Amendment No. ~ .

Completion Times 1.3 1.3 Completion Times EXAMPLES (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 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 REQUIRED ACTION COMPLETION TIME A. One channel A.1 Perform Once per 8 hours9.259259e-5 days 0.00222 hours 1.322751e-5 weeks 3.044e-6 months inoperable. SR 3.x.x.x.

OR A.2 Reduce THERMAL 8 hours9.259259e-5 days 0.00222 hours 1.322751e-5 weeks 3.044e-6 months POWER to

~ 50% RTP.

B. Required B.1 Be in MODE 3. 6 hours6.944444e-5 days 0.00167 hours 9.920635e-6 weeks 2.283e-6 months Action and associated Completion Time not met.

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 0.00222 hours 1.322751e-5 weeks 3.044e-6 months 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 0.00222 hours 1.322751e-5 weeks 3.044e-6 months 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 0.00222 hours 1.322751e-5 weeks 3.044e-6 months 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.

AN0-1 1.3-9 Amendment No. ~ .

Completion Times 1.3 1.3 Completion Times EXAMPLES (continued)

ACTIONS CONDITION REQUIRED ACTION COMPLETION TIME A. One A.1 Verify affected 1 hour1.157407e-5 days 2.777778e-4 hours 1.653439e-6 weeks 3.805e-7 months subsystem subsystem isolated.

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

B. Required B.1 Be in MODE 3. 6 hours6.944444e-5 days 0.00167 hours 9.920635e-6 weeks 2.283e-6 months Action and associated AND Completion Time not met. B.2 Be in MODE 5. 36 hours4.166667e-4 days 0.01 hours 5.952381e-5 weeks 1.3698e-5 months Required Action A.1 has two Completion Times. The 1 hour1.157407e-5 days 2.777778e-4 hours 1.653439e-6 weeks 3.805e-7 months Completion Time begins at the time the Condition is entered and each "Once per 8 hours9.259259e-5 days 0.00222 hours 1.322751e-5 weeks 3.044e-6 months 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 2.777778e-4 hours 1.653439e-6 weeks 3.805e-7 months or any subsequent 8 hour9.259259e-5 days 0.00222 hours 1.322751e-5 weeks 3.044e-6 months 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 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 Required COMPLETION TIME Action should be pursued without delay and in a controlled manner.

AN0-1 1.3-10 Amendment No. ~,248,

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

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

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

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

a. MODE 3 within 7 hours8.101852e-5 days 0.00194 hours 1.157407e-5 weeks 2.6635e-6 months ;

b. MODE 4 within 13 hours1.50463e-4 days 0.00361 hours 2.149471e-5 weeks 4.9465e-6 months ; and

c. MODE 5 within 37 hours4.282407e-4 days 0.0103 hours 6.117725e-5 weeks 1.40785e-5 months .

Exceptions to this Specification are stated in the individual Specifications.

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

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

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

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

b. After performance of a risk assessment addressing inoperable systems and components, consideration of the results, determination of the acceptability of entering the MODE or other specified condition in the Applicability, and establishment of risk management actions, if appropriate-;- .(exceptions to this Specification are stated in the individual Specifications1:i- or AN0-1 3.0-1 Amendment No. ~.~.~.2-59.

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

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

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

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

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

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

Exceptions to this Specification are stated in the individual Specifications.

SR 3.0.3 If it is discovered that a Surveillance was not performed within its specified Frequency, then compliance with the requirement to declare the LCO not met may be delayed, from the time of discovery, up to 24 hours2.777778e-4 days 0.00667 hours 3.968254e-5 weeks 9.132e-6 months 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 0.00667 hours 3.968254e-5 weeks 9.132e-6 months 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.

AN0-1 3.0-4 Amendment No.~.~.~.~.

ATTACHMENT 1.a (continued)

CNR0-2019-00003 Markup of Technical Specification (TS) Pages Arkansas Nuclear One, Unit 2 NRC Docket No. 50-368 Renewed Facility Operating License No. NPF-6 Unit 2 TS Pages 3/4 0-1 3/4 0-2

3/4 LIMITING CONDITIONS FOR OPERATION AND SURVEILLANCE REQUIREMENTS 3/4.0 APPLICABILITY LIMITING CONDITION FOR OPERATION 3.0.1 Limiting Conditions for Operation (LCO) and ACTION requirements shall be applicable during the OPERATIONAL MODES or other conditions specified for each specification, except as provided in LCO 3.0.2, LCO 3.0.8, and LCO 3.0.9.

3.0.2 Adherence to the requirements of the Limiting Condition for Operation and/or associated ACTION within the specified time interval shall constitute compliance with the specification, except as provided in Specification 3.0.6. In the event the Limiting Condition for Operation is restored prior to expiration of the specified time interval, completion of the ACTION statement is not required.

3.0.3 In the event a Limiting Condition for Operation and/or associated ACTION requirements cannot be satisfied because of circumstances in excess of those addressed in the specification within 1 hour1.157407e-5 days 2.777778e-4 hours 1.653439e-6 weeks 3.805e-7 months , action shall be initiated to place the unit in a mode in which the specification does not apply by placing it, as applicable, in at least HOT STANDBY within 6 hours6.944444e-5 days 0.00167 hours 9.920635e-6 weeks 2.283e-6 months , in at least HOT SHUTDOWN within the next 6 hours6.944444e-5 days 0.00167 hours 9.920635e-6 weeks 2.283e-6 months , and in at least COLD SHUTDOWN within the following 24 hours2.777778e-4 days 0.00667 hours 3.968254e-5 weeks 9.132e-6 months unless corrective measures are completed that permit operation under the permissible ACTION statements for the specified time interval as measured from initial discovery or until the reactor is placed in a MODE in which the specification is not applicable. Exceptions to these requirements shall be stated in the individual specification.

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

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

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

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

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

ARKANSAS - UNIT 2 3/4 0-1 Amendment No. 4-9,4M,2-07,2-84,

~.~.

APPLICABILITY SURVEILLANCE REQUIREMENTS 4.0.1 Surveillance Requirements shall be met during the MODES or other specified conditions in the Applicability for individual LCOs, unless otherwise stated in the Surveillance.

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 interval shall be failure to meet the LCO except as provided in 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 percent of the specified surveillance interval.

4.0.3 If it is discovered that a Surveillance was not performed within its specified 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 0.00667 hours 3.968254e-5 weeks 9.132e-6 months or up to the limit of the specified 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 0.00667 hours 3.968254e-5 weeks 9.132e-6 months 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(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 ACTION(s) must be entered.

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

This provision shall not prevent entry into MODES or other specified conditions in the Applicability that are required to comply with ACTIONs or that are part of a shutdown of the unit.

ARKANSAS - UNIT 2 3/4 0-2 Amendment No. 42,4-03,434,~,249.

~.

ATTACHMENT 1.b CNR0-2019-00003 Markup of Technical Specification (TS) Pages Grand Gulf Nuclear Station, Unit 1 NRC Docket No. 50-416 Renewed Facility Operating License No. NPF-29 Unit 1 TS Pages 1.0-11 3.0-2 3.0-4

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

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

DESCRIPTION The Completion Time is the amount of time allowed for completing a Required Action. It is referenced to the -t4ffle.

--e+-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 expiration of the specified Completion T' . An ACTIONS Condition remains in effect and the Re

ed Actions apply until the Condition no longer

s 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 ef discovery of the situation that required entry into the Condition.

Once a Condition has been entered, subsequent div' ions, subsystems, components, or variables expressed i the Condition, discovered to be inoperable or not w* hin limits, will not result in separate entry into the Con ition unless specifically stated. The Required Actions of the Condition continue to apply to each additional failur, with Completion Times based on initial entry in the Conditio .

, unless otherwise specified (continued l.

GRAND GULF 1.0-11 Amendment No. -He-

Insert 1 (TS 1.3, Completion Times, page 1.0-11)

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 0.00111 hours 6.613757e-6 weeks 1.522e-6 months 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.

LCO Applicability 3.0 3.0 LCO APPLICABILITY LCO 3.0.4 b. After perfo mance of a risk assessment addressing (continued) inoperable s stems and c mponents, consideration of the results, det rmination o the acceptability of entering the MODE or other specified condition in the Applicability, and establishment of risk management actions, if ap ropriat~exceptions to this Specification re stated in the individual Specifications or

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

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

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

LCO 3.0.6 When a supported system LCO is not met solely due to a support system LCO not being met, the Conditions and Required Actions associated with this supported system are not required to be entered. Only the support system LCO ACTIONS are required to be entered. This is an exception to LCO 3.0.2 for the supported system. In this event, an evaluation shall be performed in accordance with Specification 5.5.10, "Safety Function Determination Program CSFDP)." 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)

GRAND GULF 3.0-2 Amendment No. -+/--4-& * ..J:.7.§-

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

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

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

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

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

Exceptions to this Specification are stated in the individual Specifications.

SR 3.0.3 If it is discovered that a Surveillance was not performed within its specified Frequency, then compliance with the requirement to declare the LCO not met may be delayed, from the time of discovery, up to 24 hours2.777778e-4 days 0.00667 hours 3.968254e-5 weeks 9.132e-6 months or up to the limit of

-r 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 surveill e delayed greater than 24 hours2.777778e-4 days 0.00667 hours 3.968254e-5 weeks 9.132e-6 months and the risk sha 11 be managed.

The delay period is only applicable when there is a If the Surveillance is not performed within the delay reasonable expectation the period, the LCO must immediately be declared not met, and surveillance will be met the applicable Condition(s) must be entered.

when performed.

continued GRAND GULF 3.0-4 Amendment No.~ 3:-5-r--

ATTACHMENT 1.c CNR0-2019-00003 Markup of Technical Specification (TS) Pages Indian Point Nuclear Generating Unit 2 NRC Docket No. 50-247 Renewed Facility Operating License No. DPR-26 Unit 2 TS Pages 1.3-1 3.0-2 3.0-4

Comp1etion Times 1.3 u 1.0 USE AND APPLICATION 1.3 Completion Times PURPOSE The purpose of this section is to establish the Completion TI me convention and lo provide guidance for its use.

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

DESCRIPTION The Completion Time is the amount of time aUowed 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 L . equired Actions must be completed prior to the expiration of the spe * ,ed Completion Time. An ACTIONS Condition remains in effect and th equired Actions apply unlit the Condition no longer exists or the unit is ot within the LCO Applicability.

If situations are discovered that require entry into more than one Condition at a time within a single LCO (mu1tiple Conditions), the Required Actions for Insert Ne each Condition must be performed within the associated Completion Tame.

When in multiple Conditions, separate Completion Times are tracked for each Condition starting from the time or discovery of the situation that required entry Jnto the Conditi

One ition has been entered, subsequent trains, subsystems,

, unless otherwise components. or variabl~s expressed in the Condition, discovered to 'be specified inoperable or not within limits, wi11 not result in separate entry into the

---OGRCru* ion, unless specifically stated. The Required Actions of the Condition continue to each additiona1 fai1ure, with Completion Times based on initial entry into the Con * * .

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

a. Must exist concurrent with the first inoperabitity and INDIAN POINT 2 1.3 .. 1 Amendment No. %5&

Insert 1 (TS 1.3, Completion Times, page 1.3-1)

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 0.00111 hours 6.613757e-6 weeks 1.522e-6 months 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.

LCO Applicability 3.0

b. After perfor ance of a risk assessment addressing inoperable systems and components, consideration of the results, determination of the accep ability of entering the MODE or other specified condition in the Appti bility, and establishment of risk management actions, if appropriat~exceptions to this Specification are stated in the individual Specification7'or .

c. When an allo~~s stated In the individual value, parameter, or other Specification. l\"l LG This Specification shall not prevent changes in MODES or other specified conditions in the Applicability that are required to comply with ACTIONS or that are part of a shutdown of the unit.

LCO 3.0.5 Equipment removed from service or decfared inoperable to comply with

. ACTIONS may be returned to service llnder 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.

u LCO 3.0.6 When a supported system LCO is not met solely due to a support system LCO not being met, the Conditions and Required Actions associated with this supported system are not required to be entered. Only the support system LCO ACTIONS are required to be entered. This is an exception to LCO 3.0.2 for the supported system. In this event, an evaluation shall be performed in accordance with Technical Specification 5.5.13, **safety Function Determination Program {SFDP)." If a loss of safety function is determined .to exist by this program, the appropriate ConditiOr)S 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.

\_) INDJAN POINT 2 3.0*2 Amendment No.~

SR Applicability 3.0 u

. .3.0 SURVEILLANCE REQUIREMENT (SR) APPLICABILITY SR 3.0.1 SRs shall be met during the MODES or other specified conditions Jn the Applicability for individuat LCOs, unless otherwise stated in the SR. Fatlure to meet a Surveillance, whether such failure is experienced during the performance of the Surveillance or between performances of the Surveillance, shall be failure to meet the LCO. Failure to perform a Surveillance within the specified Frequency shall be failure to meet the LCO except as provided In SR 3.0.3. Surveillances do not have to be performed on inoperable equipment or variables outside specified limits.

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

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

apply.

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

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

Exceptions to this Specification are stated in the individual Specifications.

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

If the Surveillance ls no\ performed within the de1a ~ period, the LCO must immedjately be declared not met, and the appUcat: e 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 delay period is only applicable when there is a reasonable expectation the

-, surveillance will be met when performed.

\._) JNDIAN POINT 2 3.0-4 Amendment No. 2a&

ATTACHMENT 1.c (continued)

CNR0-2019-00003 Markup of Technical Specification (TS) Pages Indian Point Nuclear Generating Unit 3 NRG Docket No. 50-286 Renewed Facility Operating License No. DPR-64 Unit 3 TS Pages 1.3-1 1.3-2 3.0-2 3.0-4

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

BACKGROUND Limiting Conditions for Operation (LCOs) specify minimum requirements for ensuring safe operation of the unit. The ACTIONS associated With an LCO state Conditions that typically describe the ways in which the requirements of the LCO can fail to be met.

Specified with each stated Condition are Required Action(s) and Completion Time(s).

DESCRIPTION The Completion Time is the amount of time allowed for completing a Required Action. It is referenced to the 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 HOOE or specified condition stated in the Applicability of the LCO quired Actions must be completed prior to the expiration of he spe

ied Completion Time.

An ACTIONS Condition remains in e ect and the Re

ed Actions apply until the Condition no lo er exists or the unit* ot within the LCO Applicability. ......,n-s_e_rt_N_e_VJ_

Paragraph 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 b~ 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.

comp ents. or variables expressed in the Condition. discovered to

be noperable or not within limits. will not result in separate e ry into the Condition. unless specifically stated. The Required ctions of the Condition continue to apply to each

, unless otherVJise specified u (continued)

INDIAN POINT 3 1.3*1 lwendrnent ~

Insert 1 (TS 1.3, Completion Times, page 1.3-1)

Unless otherwise specified, the Completion Time begins when a senior licensed operator on the operating shift crew with responsibility for plant operations makes the determination that an LCO is not met and an ACTIONS Condition is entered. The "otherwise specified" exceptions are varied, such as a Required Action Note or Surveillance Requirement Note that provides an alternative time to perform specific tasks, such as testing, without starting the Completion Time.

While utilizing the Note, should a Condition be applicable for any reason not addressed by the Note, the Completion Time begins. Should the time allowance in the Note be exceeded, the Completion Time begins at that point. The exceptions may also be incorporated into the Completion Time. For example, LCO 3.8.1, "AC Sources - Operating," Required Action B.2, requires declaring required feature(s) supported by an inoperable diesel generator, inoperable when the redundant required feature(s) are inoperable. The Completion Time states, "4 hours4.62963e-5 days 0.00111 hours 6.613757e-6 weeks 1.522e-6 months 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.

, unless otherwise specified Completion Times 1.3 1.3 Com letion Times V DESCRIPTION additional failur. with Completion Times based on initial entry (continued) into the Conditio However. when a subsegueat 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. Hust exist concurrent with the .fir.s:t inoperability: and

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

The tot~l 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 hour2.777778e-4 days 0.00667 hours 3.968254e-5 weeks 9.132e-6 months s: or

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

The above Completion Time extensions do not apply to those Specifications that have exceptions that allow completely separate re-entry into the Condition (for each train, subsystem. component.

or variable expressed in the Condition) and separate tracking of Completion Times based on this re-entry. These exceptions are stated in individual Specifications.

The above Completion Time extension.does not apply to a Completion Time with a modified "time zero." This modified "time zero" may be expressed as a repetitive time Ci.e ** "once per 8 hours9.259259e-5 days 0.00222 hours 1.322751e-5 weeks 3.044e-6 months .* where the Completion Time is referenced from a previ~us 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 Bin Example 1.3*3 may not be extended.

V (continued)

INDIAN POINT 3 Amencinent -f65-

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

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

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

c. When an allowa ce is stated in the individual value, parameter, or o her Specification.

This Specification hall not prevent c anges in MODES or other specified con itions in the Appl cability that are required to comply ith ACTIONS or tha are part of a shutdown of the uni LCO 3.0.5 Equipment removed from service or declared inoperable to comply with ACTIONS may be returned to service under administrative control solely to perform testing required to demonstrate its OPERABILITY or the OPERABILITY of other equipment. This is an exception to LCO 3.0.2 for the system returned to service under administrative control to perform the testing required to demonstrate OPERABILITY.

(continued) u INDIAN POINT 3 3.0 - 2 Amendment~

SR Applicability 3.0 3.0 SURVEILLANCE REQUIREMENT (SR) APPLICABILITY SR 3.0.1 SRs shall be met during the MODES or other specified conditions in the Applicability for individual LCOs, unless otherwise stated in the SR. Failure to meet a Surveillance, whether such failure is experienced during the perfonnance of the Surveillance or between perfonnances of the Surveillance, shall be failure to meet the LCO.

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

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

SR 3.0.2 The specified Frequency for each SR is met if the Surveillance is perfonned within 1.25 times the interval specified in the Frequency, as measured from the previous perfonnance 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 *** 11 basis, the above Frequency extension applies to each perfonnance after the initial performance.

Exceptions to this Specification are stated in the individual Specifications.

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

the risk impact shall be managed.

If the Surveillance is not perfo ed within the delay period, the LCO must imnediately be declared ot met, and the applicable Condition(s) must be entered.

When the Surveillance is perfonned within the delay period and the Surveillance is not met, the LCO m st imnediately be declared not met, and the applicable Condition(s must be entered.

The delay period is only

- - - - - - - - - - - - - - - - - - - - i a p p l i c a b l e when there is a reasonable expectation the (continued) u INDIAN POINT 3 3.0 - 4 surveillance will be met when performed.

Amendment z:t-r

ATTACHMENT 1.d CNR0-2019-00003 Markup of Technical Specification (TS) Pages Palisades Nuclear Plant NRC Docket No. 50-255 Renewed Facility Operating License No. DPR-20 TS Pages 1.3-1 3.0-2 3.0-5

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

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

DESCRIPTION The Completion Time is the amount of time allowed for completing a Required Action. It is referenced to the 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 plant is in a MODE or specified condition stated in the Applicability of the

.------1--~*. 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 plant 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, otherwise c-n;:::.,.. ..1-,on 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, Palisades Nuclear Plant 1.3-1 Amendment No. 189

LCO Applicability 3.0 3.0 LCO APPLICABILITY LCO 3.0.4 (continued)

b. After performance of a risk assessment addressing inoperable systems and components, consideration of the results, determination of the acceptability of entering the MODE or other specified condition in the Applicability, and establishment of risk management actions, if appropriate7 (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 plant.

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

LCO 3.0.6 When a supported system LCO is not met solely due to a support system LCO not being met, the Conditions and Required Actions associated with this supported system are not required to be entered. Only the support system LCO ACTIONS are required to be entered. This is an exception to LCO 3.0.2 for the supported system. In this event, an evaluation shall be performed in accordance with Specification 5.5.13, "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.

Palisades Nuclear Plant 3.0-2 Amendment No. 8-9, 219

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

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

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

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

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

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

Exceptions to this Specification are stated in the individual Specifications.

SR 3.0.3 If it is discovered that a Surveillance was not performed within its specified Frequency, then compliance with the requirement to declare the LCO not met may be delayed, from the time of discovery, up to 24 hours2.777778e-4 days 0.00667 hours 3.968254e-5 weeks 9.132e-6 months or up to the limit of the specified Frequency, whichever is greater. This delay period is permitted to allow performance of the Surveillance. The is when is a l"O~>C-1"\n"ll'h!a exr)ec:tat1on rua, 11 1 0

will be met A risk evaluation shall be performed for any Surveillance delayed greater than 24 hours2.777778e-4 days 0.00667 hours 3.968254e-5 weeks 9.132e-6 months 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.

Palisades Nuclear Plant 3.0-5 Amendment No. 489, 210

Insert 1 (TS 1.3, Completion Times, page 1.3-1)

(Note: The below paragraph will be added as a new separate paragraph between "LCO."

And "Required." This will result in splitting the existing paragraph into two separate paragraphs with the insert also a separate paragraph between them.)

Unless otherwise specified, the Completion Time begins when a senior licensed operator on the operating shift crew with responsibility for plant operations makes the determination that an LCO is not met and an ACTIONS Condition is entered. The "otherwise specified" exceptions are varied, such as a Required Action Note or Surveillance Requirement Note that provides an alternative time to perform specific tasks, such as testing, without starting the Completion Time.

While utilizing the Note, should a Condition be applicable for any reason not addressed by the Note, the Completion Time begins. Should the time allowance in the Note be exceeded, the Completion Time begins at that point. The exceptions may also be incorporated into the Completion Time. For example, LCO 3.8.1, "AC Sources - Operating," Required Action B.2, requires declaring required feature(s) supported by an inoperable diesel generator, inoperable when the redundant required feature(s) are inoperable. The Completion Time states, "4 hours4.62963e-5 days 0.00111 hours 6.613757e-6 weeks 1.522e-6 months 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.

ATIACHMENT 1.e CNR0-2019-00003 Markup of Technical Specification (TS) Pages River Bend Station, Unit 1 NRC Docket No. 50-458 Renewed Facility Operating License No. NPF-47 Unit 1 TS Pages 1.0-11 3.0-2 3.0-4

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

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

DESCRIPTION The Completion Time is the amount of time allowed for completing a Required Action. It is referenced to the tim~ of discovery of a situation (e.g., inoperable equipment or variable not within limits) that requires Insert 1 entering an ACTIONS Condition unless otherwise specified, providing the unit is in a MODE or specified condition stated in the Applicability of the LC . Required Actions must be completed prior to the expiration of the specified Completion Time. An ACTIONS Condition remains in effect and the Required Actions apply until the Condition no longer exists or the unit is not within the LCO Applicability.

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

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

(continued)

, unless otherwise specified RIVER BEND 1.0-11 Amendment No.

Insert 1 (TS 1.3, Completion Times, page 1.0-11)

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 0.00111 hours 6.613757e-6 weeks 1.522e-6 months 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.

LCO Applicablity 3.0 3.0 LCO APPLICABILITY LCO 3.0.4 b. After performance of a risk assessme addressing inoperable (continued) systems and components, considerati n of the results, determination of the acceptability of e tering the MODE or other specified condition in the Applicabilit and establishment of risk management actions, if appropriato/exceptions to this Specification are stated in the individual Specification~r

c. When an allowance is stated in the individual value, pa other Specification.

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

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

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

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

(continued)

RIVER BEND 3.0-2 Amendment No. 84, ~

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

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

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

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

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

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

Exceptions to this Specification are stated in the individual Specifications.

t SR 3.0.3 If it is discovered that a Surveillance was not performed within its specified Frequency, then compliance with the requirement to declare the LCO not met may be delayed, from the time of discovery, up to 24 hours2.777778e-4 days 0.00667 hours 3.968254e-5 weeks 9.132e-6 months 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 great than 24 hours2.777778e-4 days 0.00667 hours 3.968254e-5 weeks 9.132e-6 months and the risk shall be managed.

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

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

The delay period is only (continued) applicable when there is a reasonable expectation the surveillance will be met when performed.

RIVER BEND 3.0-4 Amendment No. 84, ~

ATIACHMENT 1.f CNR0-2019-00003 Markup of Technical Specification (TS) Pages Waterford Steam Electric Station, Unit 3 NRC Docket No. 50-382 Renewed Facility Operating License No. NPF-38 Unit 3 TS Pages 3/4 0-2

~EPLICABILIJY

§URVEILLANCE REQUIREMENTS 4.0.1 Surveillance Requirements shall be met during the MODES or other specified conditions in the Applicability for individual LCOs, unless otherwise stated in the Surveillance. 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 interval shall be failure to meet the LCO except as provided in 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 twenty-five percent of the specified surveillance interval.

4.0.3 If it is discovered that a Surveillance was not performed within its. specified 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 0.00667 hours 3.968254e-5 weeks 9.132e-6 months 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 hou and the risk impact shall be managed.

If the Survelllance Is not performed within the delay period, the LCO must I mediately be declared not met, and the applicable ACTION(s) must be entered.

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

4.0.4 C::ntry into an Ol"ERATIONAL MODE or otherspecifiedcond' 10n sh;all not be made unless the Surveillance Requirement(s) associated with the Limiti Condition for Operation have been performed within the stated surveillance interval or as therwise specified. This provision shall not prevent passage through or to operational m des as required to comply with ACTION requirements.

The delay period is only applicable when there is a reasonable expectation the surveillance will be met when performed.

WATERFORD UNIT 3 3/4 0-2 AMENDMENT N O . ~ ~

MAR 2 1 2003

ATTACHMENT 2.a CNR0-2019-00003 Clean Technical Specification (TS) Pages Arkansas Nuclear One, Unit 1 NRC Docket No. 50-313 Renewed Facility Operating License No. DPR-51 Unit 1 TS Pages 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*

3.0-1 3.0-4

Unit 1 TS Pages 1.3-3 through 1.3-1 Oare included due to repagination only.

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

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

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

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

AN0-1 1.3-1 Amendment No. 2-+a,

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 0.00667 hours 3.968254e-5 weeks 9.132e-6 months ; 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.

AN0-1 1.3-2 Amendment No. ~ .

Completion Times 1.3 1.3 Completion Times (continued)

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 0.00222 hours 1.322751e-5 weeks 3.044e-6 months ," 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.

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

8. Required 8.1 Be in MODE 3. 6 hours6.944444e-5 days 0.00167 hours 9.920635e-6 weeks 2.283e-6 months Action and associated AND Completion Time not met. 8.2 Be in MODE 5. 36 hours4.166667e-4 days 0.01 hours 5.952381e-5 weeks 1.3698e-5 months 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 Bis entered.

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

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

AN0-1 1.3-3 Amendment No. ~ .

Completion Times 1.3 1.3 Completion Times EXAMPLES (continued)

EXAMPLE 1. 3-2 ACTIONS CONDITION REQUIRED ACTION COMPLETION TIME A. One pump A.1 Restore pump to 7 days inoperable. OPERABLE status.

8. Required 8.1 Be in MODE 3. 6 hours6.944444e-5 days 0.00167 hours 9.920635e-6 weeks 2.283e-6 months Action and associated AND Completion Time not met. 8.2 Be in MODE 5. 36 hours4.166667e-4 days 0.01 hours 5.952381e-5 weeks 1.3698e-5 months 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 B are exited, and therefore, the Required Actions of Condition B may be terminated.

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

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

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

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

AN0-1 1.3-4 Amendment No. ~ .

Completion Times 1.3 1.3 Completion Times EXAMPLES (continued)

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 0.00667 hours 3.968254e-5 weeks 9.132e-6 months extension to the stated 7 days is allowed, provided this does not result in the second pump being inoperable for> 7 days.

EXAMPLE 1.3-3 ACTIONS CONDITION REQUIRED ACTION COMPLETION TIME A. One A.1 Restore Function X 7 days Function X train to train OPERABLE AND inoperable. status.

10 days from discovery of failure to meet the LCO B. One B.1 Restore Function Y 72 hours8.333333e-4 days 0.02 hours 1.190476e-4 weeks 2.7396e-5 months Function Y train to train OPERABLE AND inoperable. status.

10 days from discovery of failure to meet the LCO C. One C.1 Restore Function X 72 hours8.333333e-4 days 0.02 hours 1.190476e-4 weeks 2.7396e-5 months Function X train to train OPERABLE inoperable. status.

AND OR One C.2 Restore Function Y 72 hours8.333333e-4 days 0.02 hours 1.190476e-4 weeks 2.7396e-5 months Function Y train to OPERABLE train status.

inoperable.

AN0-1 1.3-5 Amendment No. ~ ,

Completion Times 1.3 1.3 Completion Times EXAMPLES (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.

AN0-1 1.3-6 Amendment No. ~ ,

Completion Times 1.3 1.3 Completion Times EXAMPLES (continued)

EXAMPLE 1.3-4 ACTIONS CONDITION REQUIRED ACTION COMPLETION TIME A. One or more A.1 Restore valve(s) to 4 hours4.62963e-5 days 0.00111 hours 6.613757e-6 weeks 1.522e-6 months valves OPERABLE inoperable. status.

B. Required B.1 Be in MODE 3. 6 hours6.944444e-5 days 0.00167 hours 9.920635e-6 weeks 2.283e-6 months Action and associated AND Completion Time not met. B.2 Be in MODE 4. 12 hours1.388889e-4 days 0.00333 hours 1.984127e-5 weeks 4.566e-6 months 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 0.00111 hours 6.613757e-6 weeks 1.522e-6 months provided this does not result in any subsequent valve being inoperable for > 4 hours4.62963e-5 days 0.00111 hours 6.613757e-6 weeks 1.522e-6 months .

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

AN0-1 1.3-7 Amendment No. ~ .

Completion Times 1.3 1.3 Completion Times EXAMPLES (continued)

EXAMPLE 1.3-5 ACTIONS

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

S e para te Condition entry is allowed for each inoperable valve.

CONDITION REQUIRED ACTION COMPLETION TIME A. One or more A.1 Restore valve to 4 hours4.62963e-5 days 0.00111 hours 6.613757e-6 weeks 1.522e-6 months valves OPERABLE inoperable. status.

B. Required B.1 Be in MODE 3. 6 hours6.944444e-5 days 0.00167 hours 9.920635e-6 weeks 2.283e-6 months Action and associated AND Completion Time not met. B.2 Be in MODE 4. 12 hours1.388889e-4 days 0.00333 hours 1.984127e-5 weeks 4.566e-6 months 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.

AN0-1 1.3-8 Amendment No. ~ .

Completion Times 1.3 1.3 Completion Times EXAMPLES (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 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 REQUIRED ACTION COMPLETION TIME A. One channel A.1 Perform Once per 8 hours9.259259e-5 days 0.00222 hours 1.322751e-5 weeks 3.044e-6 months inoperable. SR 3.x.x.x.

OR A.2 Reduce THERMAL 8 hours9.259259e-5 days 0.00222 hours 1.322751e-5 weeks 3.044e-6 months POWER to

~ 50% RTP.

B. Required 8.1 Be in MODE 3. 6 hours6.944444e-5 days 0.00167 hours 9.920635e-6 weeks 2.283e-6 months Action and associated Completion Time not met.

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 0.00222 hours 1.322751e-5 weeks 3.044e-6 months 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 0.00222 hours 1.322751e-5 weeks 3.044e-6 months 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 0.00222 hours 1.322751e-5 weeks 3.044e-6 months 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.

AN0-1 1.3-9 Amendment No. ~ .

Completion Times 1.3 1.3 Completion Times EXAMPLES (continued)

ACTIONS CONDITION REQUIRED ACTION COMPLETION TIME A. One A.1 Verify affected 1 hour1.157407e-5 days 2.777778e-4 hours 1.653439e-6 weeks 3.805e-7 months subsystem subsystem isolated.

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

B. Required 8.1 Be in MODE 3. 6 hours6.944444e-5 days 0.00167 hours 9.920635e-6 weeks 2.283e-6 months Action and associated AND Completion Time not met. 8.2 Be in MODE 5. 36 hours4.166667e-4 days 0.01 hours 5.952381e-5 weeks 1.3698e-5 months Required Action A.1 has two Completion Times. The 1 hour1.157407e-5 days 2.777778e-4 hours 1.653439e-6 weeks 3.805e-7 months Completion Time begins at the time the Condition is entered and each "Once per 8 hours9.259259e-5 days 0.00222 hours 1.322751e-5 weeks 3.044e-6 months thereafter" inteNal 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 2.777778e-4 hours 1.653439e-6 weeks 3.805e-7 months or any subsequent 8 hour9.259259e-5 days 0.00222 hours 1.322751e-5 weeks 3.044e-6 months inteNal 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 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 Required COMPLETION TIME Action should be pursued without delay and in a controlled manner.

AN0-1 1.3-10 Amendment No. ~ . ~ .