JAFP-20-0049, Application to Adopt TSTF-427, Revision 2, Allowance for Non Technical Specification Barrier Degradation on Supported System Operability

From kanterella
Revision as of 20:33, 10 December 2024 by StriderTol (talk | contribs) (StriderTol Bot change)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search

Application to Adopt TSTF-427, Revision 2, Allowance for Non Technical Specification Barrier Degradation on Supported System Operability
ML20174A077
Person / Time
Site: Dresden, Peach Bottom, Nine Mile Point, Byron, Braidwood, Limerick, Ginna, Clinton, Quad Cities, FitzPatrick, LaSalle  Constellation icon.png
Issue date: 06/22/2020
From: David Gudger
Exelon Generation Co
To:
Document Control Desk, Office of Nuclear Reactor Regulation
References
JAFP-20-0049, NMP1L3344, RS-20-077
Download: ML20174A077 (32)
v • d • e


Text

200 Exelon Way Kennett Square, PA 19348 www.exeloncorp.com 10 CFR 50.90 RS-20-077 JAFP-20-0049 NMP1L3344 June 22, 2020 U.S. Nuclear Regulatory Commission ATTN: Document Control Desk Washington, DC 20555-0001 Braidwood Station, Units 1 and 2 Renewed Facility Operating License Nos. NPF-72 and NPF-77 NRC Docket Nos. STN 50-456 and STN 50-457 Byron Station, Units 1 and 2 Renewed Facility Operating License Nos. NPF-37 and NPF-66 NRC Docket Nos. STN 50-454 and STN 50-455 Clinton Power Station, Unit 1 Facility Operating License No. NPF-62 NRC Docket No. 50-461 Dresden Nuclear Power Station, Units 2 and 3 Renewed Facility Operating License Nos. DPR-19 and DPR-25 NRC Docket Nos. 50-237 and 50-249 James A. FitzPatrick Nuclear Power Plant Renewed Facility Operating License No. DPR-59 NRC Docket No. 50-333 LaSalle County Station, Units 1 and 2 Renewed Facility Operating License Nos. NPF-11 and NPF-18 NRC Docket Nos. 50-373 and 50-374 Limerick Generating Station, Units 1 and 2 Renewed Facility Operating License Nos. NPF-39 and NPF-85 NRC Docket Nos. 50-352 and 50-353 Nine Mile Point Nuclear Station, Unit 1 Renewed Facility Operating License No. DPR-63 NRC Docket No. 50-220 Peach Bottom Atomic Power Station, Units 2 and 3 Renewed Facility Operating License Nos. DPR-44 and DPR-56 NRC Docket Nos. 50-277 and 50-278

U.S. Nuclear Regulatory Commission Adoption of TSTF-427 June 22, 2020 Page 2 Quad Cities Nuclear Power Station, Units 1 and 2 Renewed Facility Operating License Nos. DPR-29 and DPR-30 NRC Docket Nos. 50-254 and 50-265 R. E. Ginna Nuclear Power Plant Renewed Facility Operating License No. DPR-18 NRC Docket No. 50-244

Subject:

Application to Adopt TSTF-427, Revision 2, "Allowance for Non Technical Specification Barrier Degradation on Supported System OPERABILITY"

Reference:

1. Letter J. Barstow (Exelon Generation Company, LLC) to U.S. Nuclear Regulatory Commission, "Application to Adopt TSTF-427, Revision 2,

'Allowance for Non Technical Specification Barrier Degradation on Supported System OPERABILITY,'" dated June 27, 2019 In the Reference 1 letter, Exelon Generation Company, LLC (EGC) submitted a request for an amendment to the Technical Specifications (TS) for the stations identified above. The proposed amendment would modify TS requirements for unavailable barriers by adding Limiting Condition for Operation (LCO) 3.0.9, or its equivalent. The proposed changes are consistent with NRC approved Technical Specification Task Force (TSTF) Standard Technical Specification Change Traveler, TSTF-427, Revision 2, "Allowance for Non Technical Specification Barrier Degradation on Supported System OPERABILITY," dated May 3, 2006.

Since the submittal of the marked-up pages in the Reference 1 letter, the following changes to the pages have occurred:

1) Braidwood Station, Units 1 and 2, and Byron Station, Units 1 and 2 - LCO numbering has been changed as a result of the insertion of an approved TS.
2) James A. FitzPatrick Nuclear Power Plant - The TS pages have been changed as a result of the insertion of an approved TS.
3) LaSalle County Station, Units 1 and 2 - The TS pages for the are being updated to:
a. Page 3.0-3 is being submitted to show the change from a double line to single line at the bottom of the page.
b. Existing revision bars and amendment numbers have been deleted on all revised pages.
c. Where only the page number is changed, a revision bar has been added.
4) Limerick Generating Station, Units 1 and 2 - The term LCO has been deleted from Limiting Condition for Operation 3.0.1, and the new insert 3.0.9 spells out Limiting Conditions for Operation.

EGC has reviewed the information supporting a finding of no significant hazards consideration, and the environmental consideration, that were previously provided to the NRC in the Reference 1 letter. The supplemental information provided in this response does not affect the bases for concluding that the proposed license amendment does not involve a

U.S. Nuclear Regulatory Commission Adoption of TSTF-427 June 22, 2020 Page 3 significant hazards consideration under the standards set forth in 10 CFR 50.92. In addition, EGC has concluded that the information provided in this supplemental response does not affect the bases for concluding that neither an environmental impact statement nor an environmental assessment needs to be prepared in connection with the proposed amendment.

Should you have any questions concerning this letter, please contact Tom Loomis at (610) 765-5510.

I declare under penalty of perjury that the foregoing is true and correct. Executed on the 22nd day of June 2020.

Respectfully, David T. Gudger Senior Manager - Licensing Exelon Generation Company, LLC Attachments:

1) Revised Technical Specifications Pages for Braidwood Station, Units 1 and 2, and Byron Station, Units 1 and 2
2) Revised Technical Specifications Pages for James A. FitzPatrick Nuclear Power Plant
3) Revised Technical Specifications Pages for LaSalle County Station, Units 1 and 2
4) Revised Technical Specifications Pages for Limerick Generating Station, Units 1 and 2 David T. Gudger

U.S. Nuclear Regulatory Commission Adoption of TSTF-427 June 22, 2020 Page 4 cc:

Regional Administrator - NRC Region I Regional Administrator - NRC Region III NRC Senior Resident Inspector - Braidwood Station NRC Senior Resident Inspector - Byron Station NRC Senior Resident Inspector - Clinton Power Station NRC Senior Resident Inspector - Dresden Nuclear Power Station NRC Senior Resident Inspector - James A. FitzPatrick Nuclear Power Plant NRC Senior Resident Inspector - LaSalle County Station NRC Senior Resident Inspector - Limerick Generating Station NRC Senior Resident Inspector - Nine Mile Point Nuclear Station NRC Senior Resident Inspector - Peach Bottom Atomic Power Station NRC Senior Resident Inspector - Quad Cities Nuclear Power Station NRC Senior Resident Inspector - R. E. Ginna Nuclear Power Plant NRC Project Manager - Braidwood Station NRC Project Manager - Byron Station NRC Project Manager - Clinton Power Station NRC Project Manager - Dresden Nuclear Power Station NRC Project Manager - James A. FitzPatrick Nuclear Power Plant NRC Project Manager - LaSalle County Station NRC Project Manager - Limerick Generating Station NRC Project Manager - Nine Mile Point Nuclear Station NRC Project Manager - Peach Bottom Atomic Power Station NRC Project Manager - Quad Cities Nuclear Power Station NRC Project Manager - R. E. Ginna Nuclear Power Plant Illinois Emergency Management Agency - Division of Nuclear Safety S. Seaman, State of Maryland A. L. Peterson, NYSERDA

Updated Technical Specifications Pages for Braidwood Station, Units 1 and 2, and Byron Station, Units 1 and 2 Pages 3.0.1 3.0.4 3.0.5 3.0.6 3.0.7

LCO Applicability 3.0 BRAIDWOOD UNITS 1 & 2 3.0 1 Amendment 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.9, and LCO 3.0.10.

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

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

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

a.

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

b.

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

c.

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

Exceptions to this Specification are stated in the individual Specifications.

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

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

LCO Applicability 3.0 BRAIDWOOD UNITS 1 & 2 3.0 4 Amendment 3.0 LCO Applicability LCO 3.0.7 Exception LCOs allow specified Technical Specification (TS) requirements to be changed to permit performance of special tests and operations. Unless otherwise specified, all other TS requirements remain unchanged. Compliance with Exception LCOs is optional. When an Exception LCO is desired to be met but is not met, the ACTIONS of the Exception LCO shall be met. When an Exception LCO is not desired to be met, entry into a MODE or other specified condition in the Applicability shall be made in accordance with the other applicable Specifications.

LCO 3.0.8 LCOs, including associated ACTIONs, shall apply to each unit individually, unless otherwise indicated. Whenever the LCO refers to a system or component that is shared by both units, the ACTIONs will apply to both units simultaneously.

LCO 3.0.9 When one or more required snubbers are unable to perform their associated support function(s), any affected supported LCO(s) are not required to be declared not met solely for this reason if risk is assessed and managed, and:

a.

the snubbers not able to perform their associated support function(s) are associated with only one train or subsystem of a multiple train or subsystem supported system or are associated with a single train or subsystem supported system and are able to perform their associated support function within 72 hours8.333333e-4 days <br />0.02 hours <br />1.190476e-4 weeks <br />2.7396e-5 months <br />; or

b.

the snubbers not able to perform their associated support function(s) are associated with more than one train or subsystem of a multiple train or subsystem supported system and are able to perform their associated support function within 12 hours1.388889e-4 days <br />0.00333 hours <br />1.984127e-5 weeks <br />4.566e-6 months <br />.

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

LCO Applicability 3.0 BRAIDWOOD UNITS 1 & 2 3.0 5 Amendment 3.0 LCO Applicability LCO 3.0.10 When one or more required barriers are unable to perform their related support function(s), any supported system LCO(s) are not required to be declared not met solely for this reason for up to 30 days provided that at least one train or subsystem of the supported system is OPERABLE and supported by barriers capable of providing their related support function(s), and risk is assessed and managed. This specification may be concurrently applied to more than one train or subsystem of a multiple train or subsystem supported system provided at least one train or subsystem of the supported system is OPERABLE and the barriers supporting each of these trains or subsystems provide their related support function(s) for different categories of initiating events.

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

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

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

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

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

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

SR 3.0.5 SRs shall apply to each unit individually, unless otherwise indicated.

LCO Applicability 3.0 BYRON UNITS 1 & 2 3.0 1 Amendment 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.9, and LCO 3.0.10.

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

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

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

a.

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

b.

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

c.

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

Exceptions to this Specification are stated in the individual Specifications.

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

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

LCO Applicability 3.0 BYRON UNITS 1 & 2 3.0 4 Amendment 3.0 LCO Applicability LCO 3.0.7 Exception LCOs allow specified Technical Specification (TS) requirements to be changed to permit performance of special tests and operations. Unless otherwise specified, all other TS requirements remain unchanged. Compliance with Exception LCOs is optional. When an Exception LCO is desired to be met but is not met, the ACTIONS of the Exception LCO shall be met. When an Exception LCO is not desired to be met, entry into a MODE or other specified condition in the Applicability shall be made in accordance with the other applicable Specifications.

LCO 3.0.8 LCOs, including associated ACTIONs, shall apply to each unit individually, unless otherwise indicated. Whenever the LCO refers to a system or component that is shared by both units, the ACTIONs will apply to both units simultaneously.

LCO 3.0.9 When one or more required snubbers are unable to perform their associated support function(s), any affected supported LCO(s) are not required to be declared not met solely for this reason if risk is assessed and managed, and:

a. the snubbers not able to perform their associated support function(s) are associated with only one train or subsystem of a multiple train or subsystem supported system or are associated with a single train or subsystem supported system and are able to perform their associated support function within 72 hours8.333333e-4 days <br />0.02 hours <br />1.190476e-4 weeks <br />2.7396e-5 months <br />; or
b. the snubbers not able to perform their associated support function(s) are associated with more than one train or subsystem of a multiple train or subsystem supported system and are able to perform their associated support function within 12 hours1.388889e-4 days <br />0.00333 hours <br />1.984127e-5 weeks <br />4.566e-6 months <br />.

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

LCO Applicability 3.0 BYRON UNITS 1 & 2 3.0 5 Amendment 3.0 LCO Applicability LCO 3.0.10 When one or more required barriers are unable to perform their related support function(s), any supported system LCO(s) are not required to be declared not met solely for this reason for up to 30 days provided that at least one train or subsystem of the supported system is OPERABLE and supported by barriers capable of providing their related support function(s), and risk is assessed and managed. This specification may be concurrently applied to more than one train or subsystem of a multiple train or subsystem supported system provided at least one train or subsystem of the supported system is OPERABLE and the barriers supporting each of these trains or subsystems provide their related support function(s) for different categories of initiating events.

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

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

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

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

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

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

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.

SR 3.0.5 SRs shall apply to each unit individually, unless otherwise indicated.

Revised Technical Specifications Pages for James A. FitzPatrick Nuclear Power Plant Pages 3.0.1 3.0.3 3.0.4 3.0.5 3.0.6

LCO Applicability 3.0 3.0 LIMITING CONDITION FOR OPERATION (LCO) APPLICABILITY JAFNPP 3.0-1 Amendment 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 plant shall be placed in a MODE or other specified condition in which the LCO is not applicable. Action shall be initiated within 1 hour1.157407e-5 days <br />2.777778e-4 hours <br />1.653439e-6 weeks <br />3.805e-7 months <br /> to place the plant, as applicable, in:

a.

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

b.

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

c.

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

Exceptions to this Specification are stated in the individual Specifications.

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

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

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; (continued)

LCO Applicability 3.0 3.0 LCO APPLICABILITY JAFNPP 3.0-3 Amendment LCO 3.0.7 Special Operations LCOs in Section 3.10 allow specified Technical Specifications (TS) requirements to be changed to permit performance of special tests and operations. Unless otherwise specified, all other TS requirements remain unchanged. Compliance with Special Operations LCOs is optional. When a Special Operations LCO is desired to be met but is not met, the ACTIONS of the Special Operations LCO shall be met.

When a Special Operations LCO is not desired to be met, entry into a MODE or other specified condition in the Applicability shall only be made in accordance with the other applicable Specifications.

LCO 3.0.8 When one or more required snubbers are unable to perform their associated support function(s), any affected supported LCOs are not required to be declared not met solely for this reason if risk is assessed and managed, and:

a.

the snubbers not able to perform their associated support function(s) are associated with only one train or subsystem of a multiple train or subsystem supported system or are associated with a single train or subsystem supported system and are able to perform their associated support function within 72 hours8.333333e-4 days <br />0.02 hours <br />1.190476e-4 weeks <br />2.7396e-5 months <br />; or b.

the snubbers not able to perform their associated support function(s) are associated with more than one train or subsystem of a multiple train or subsystem supported system and are able to perform their associated support function within 12 hours1.388889e-4 days <br />0.00333 hours <br />1.984127e-5 weeks <br />4.566e-6 months <br />.

At the end of the specified period, the required snubbers must be able to perform their associated support function(s), or the affected supported system LCOs shall be declared not met.

(continued)

(continued)

LCO Applicability 3.0 3.0 LCO APPLICABILITY JAFNPP 3.0-4 Amendment LCO 3.0.9 When one or more required barriers are unable to perform their related support function(s), any supported system LCO(s) are not required to be declared not met solely for this reason for up to 30 days provided that at least one train or subsystem of the supported system is OPERABLE and supported by barriers capable of providing their related support function(s), and risk is assessed and managed. This specification may be concurrently applied to more than one train or subsystem of a multiple train or subsystem supported system provided at least one train or subsystem of the supported system is OPERABLE and the barriers supporting each of these trains or subsystems provide their related support function(s) for different categories of initiating events.

For the purposes of this specification, the High Pressure Coolant Injection system, the Reactor Core Isolation Cooling system, and the Automatic Depressurization System are considered independent subsystems of a single system.

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

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

(continued)

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

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

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

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

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

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

Exceptions to this Specification are stated in the individual Specifications.

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

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

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

(continued)

SR Applicability 3.0 3.0 SR APPLICABILITY (continued)

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

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

Revised Technical Specifications Pages for LaSalle County Station, Units 1 and 2 Pages 3.0.1 3.0.3 3.0.4 3.0.5 3.0.6

LCO Applicability 3.0 LaSalle 1 and 2 3.0-1 Amendment No.

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

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

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

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

a. MODE 2 within 7 hours8.101852e-5 days <br />0.00194 hours <br />1.157407e-5 weeks <br />2.6635e-6 months <br />;
b. MODE 3 within 13 hours1.50463e-4 days <br />0.00361 hours <br />2.149471e-5 weeks <br />4.9465e-6 months <br />; and
c. MODE 4 within 37 hours4.282407e-4 days <br />0.0103 hours <br />6.117725e-5 weeks <br />1.40785e-5 months <br />.

Exceptions to this Specification are stated in the individual Specifications.

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

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

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; (continued)

LCO Applicability 3.0 LaSalle 1 and 2 3.0-3 Amendment No.

3.0 LCO APPLICABILITY LCO 3.0.7 Special Operations LCOs in Section 3.10 allow specified Technical Specifications (TS) requirements to be changed to permit performance of special tests and operations. Unless otherwise specified, all other TS requirements remain unchanged. Compliance with Special Operations LCOs is optional. When a Special Operations LCO is desired to be met but is not met, the ACTIONS of the Special Operations LCO shall be met. When a Special Operations LCO is not desired to be met, entry into a MODE or other specified condition in the Applicability shall only be made in accordance with the other applicable Specifications.

LCO 3.0.8 When one or more required snubbers are unable to perform their associated support function(s), any affected supported LCO(s) are not required to be declared not met solely for this reason if risk is assessed and managed, and:

a.

the snubbers not able to perform their associated support function(s) are associated with only one train or subsystem of a multiple train or subsystem supported system or are associated with a single train or subsystem supported system and are able to perform their associated support function within 72 hours8.333333e-4 days <br />0.02 hours <br />1.190476e-4 weeks <br />2.7396e-5 months <br />; or

b.

the snubbers not able to perform their associated support function(s) are associated with more than one train or subsystem of a multiple train or subsystem supported system and are able to perform their associated support function within 12 hours1.388889e-4 days <br />0.00333 hours <br />1.984127e-5 weeks <br />4.566e-6 months <br />.

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

LCO 3.0.9 LCOs, including associated ACTIONS, shall apply to each unit individually, unless otherwise indicated. Whenever the LCO refers to a system or component that is shared by both units, the ACTIONS will apply to both units simultaneously.

LCO Applicability 3.0 LaSalle 1 and 2 3.0-4 Amendment No.

3.0 LCO APPLICABILITY LCO 3.0.10 When one or more required barriers are unable to perform their related support function(s), any supported system LCO(s) are not required to be declared not met solely for this reason for up to 30 days provided that at least one train or subsystem of the supported system is OPERABLE and supported by barriers capable of providing their related support function(s), and risk is assessed and managed.

This specification may be concurrently applied to more than one train or subsystem of a multiple train or subsystem supported system provided at least one train or subsystem of the supported system is OPERABLE and the barriers supporting each of these trains or subsystems provide their related support function(s) for different categories of initiating events.

For the purposes of this specification, the High Pressure Core Spray system, the Reactor Core Isolation Cooling system, and the Automatic Depressurization System are considered independent subsystems of a single system.

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

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

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

Failure to perform a Surveillance within the specified Frequency shall be failure to meet the LCO except as provided in SR 3.0.3. Surveillances do not have to be performed on inoperable equipment or variables outside specified limits.

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

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

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

Exceptions to this Specification are stated in the individual Specifications.

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

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

(continued)

SR Applicability 3.0 LaSalle 1 and 2 3.0-6 Amendment No 3.0 SR APPLICABILITY SR 3.0.3 When the Surveillance is performed within the delay period (continued) and the Surveillance is not met, the LCO must immediately be declared not met, and the applicable Condition(s) must be entered.

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

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.

SR 3.0.5 SRs shall apply to each unit individually, unless otherwise indicated.

Revised Technical Specifications Pages for Limerick Generating Station, Units 1 and 2 Pages 3/4 0-1 3/4 0-1b

3/4.0 APPLICABILITY LIMITING CONDITION FOR OPERATION 3.0.1 Compliance with the Limiting Conditions for Operation contained in the succeeding Specifications is required during the OPERATIONAL CONDITIONS or other conditions specified therein, except as provided in Specification 3.0.8. Upon failure to meet the Limiting Conditions for Operation, the associated ACTION requirements shall be met, except as provided in Specifications 3.0.5, 3.0.6, and 3.0.9.

3.0.2 Noncompliance with a Specification shall exist when the requirements of the Limiting Condition for Operation and associated ACTION requirements are not met within the specified time intervals, except as provided in Specifications 3.0.5 and 3.0.6. If the Limiting Condition for Operation is restored prior to expiration of the specified time intervals, completion of the ACTION requirements is not required.

3.0.3 When a Limiting Condition for Operation is not met, except as provided in the associated ACTION requirements, within one hour action shall be initiated to place the unit in an OPERATIONAL CONDITION in which the Specification does not apply by placing it, as applicable, in:

a.

At least STARTUP within the next 6 hours6.944444e-5 days <br />0.00167 hours <br />9.920635e-6 weeks <br />2.283e-6 months <br />,

b.

At least HOT SHUTDOWN within the following 6 hours6.944444e-5 days <br />0.00167 hours <br />9.920635e-6 weeks <br />2.283e-6 months <br />, and

c.

At least COLD SHUTDOWN within the subsequent 24 hours2.777778e-4 days <br />0.00667 hours <br />3.968254e-5 weeks <br />9.132e-6 months <br />.

Where corrective measures are completed that permit operation under the ACTION requirements, the ACTION may be taken in accordance with the specified time limits as measured from the time of failure to meet the Limiting Condition for Operation. Exceptions to these requirements are stated in the individual Specifications.

This Specification is not applicable in OPERATIONAL CONDITION 4 or 5.

3.0.4 When a Limiting Condition for Operation is not met, entry into an OPERATIONAL CONDITION or other specified condition in the Applicability shall only be made:

a.

When the associated ACTION requirements to be entered permit continued operation in the OPERATIONAL CONDITION or other specified condition in the Applicability for an unlimited period of time; or

b.

After performance of a risk assessment addressing inoperable systems and components, consideration of the results, determination of the acceptability of entering the OPERATIONAL CONDITION 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 OPERATIONAL CONDITIONS or other specified conditions in the Applicability that are required to comply with ACTION requirements or that are part of a shutdown of the unit.

LIMERICK - UNIT 1 3/4 0-1 Amendment No. 11, 169, 219, 226,

234,

3/4.0 APPLICABILITY LIMITING CONDITION FOR OPERATION (Continued) 3.0.9 When one or more required barriers are unable to perform their related support function(s), any supported system Limiting Conditions for Operation are not required to be declared not met solely for this reason for up to 30 days provided that at least one train or subsystem of the supported system is OPERABLE and supported by barriers capable of providing their related support function(s), and risk is assessed and managed. This specification may be concurrently applied to more than one train or subsystem of a multiple train or subsystem supported system provided at least one train or subsystem of the supported system is OPERABLE and the barriers supporting each of these trains or subsystems provide their related support function(s) for different categories of initiating events.

For the purposes of this specification, the High Pressure Coolant Injection system, the Reactor Core Isolation Cooling system, and the Automatic Depressurization System are considered independent subsystems of a single system.

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

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

LIMERICK - UNIT 1 3/4 0-1b Amendment No.

3/4.0 APPLICABILITY LIMITING CONDITION FOR OPERATION 3.0.1 Compliance with the Limiting Conditions for Operation contained in the succeeding Specifications is required during the OPERATIONAL CONDITIONS or other conditions specified therein, except as provided in Specification 3.0.8. Upon failure to meet the Limiting Conditions for Operation, the associated ACTION requirements shall be met, except as provided in Specifications 3.0.5, 3.0.6, and 3.0.9.

3.0.2 Noncompliance with a Specification shall exist when the requirements of the Limiting Condition for Operation and associated ACTION requirements are not met within the specified time intervals, except as provided in Specifications 3.0.5 and 3.0.6. If the Limiting Condition for Operation is restored prior to expiration of the specified time intervals, completion of the ACTION requirements is not required.

3.0.3 When a Limiting Condition for Operation is not met, except as provided in the associated ACTION requirements, within one hour action shall be initiated to place the unit in an OPERATIONAL CONDITION in which the Specification does not apply by placing it, as applicable, in:

a.

At least STARTUP within the next 6 hours6.944444e-5 days <br />0.00167 hours <br />9.920635e-6 weeks <br />2.283e-6 months <br />,

b.

At least HOT SHUTDOWN within the following 6 hours6.944444e-5 days <br />0.00167 hours <br />9.920635e-6 weeks <br />2.283e-6 months <br />, and

c.

At least COLD SHUTDOWN within the subsequent 24 hours2.777778e-4 days <br />0.00667 hours <br />3.968254e-5 weeks <br />9.132e-6 months <br />.

Where corrective measures are completed that permit operation under the ACTION requirements, the ACTION may be taken in accordance with the specified time limits as measured from the time of failure to meet the Limiting Condition for Operation. Exceptions to these requirements are stated in the individual Specifications.

This Specification is not applicable in OPERATIONAL CONDITION 4 or 5.

3.0.4 When a Limiting Condition for Operation is not met, entry into an OPERATIONAL CONDITION or other specified condition in the Applicability shall only be made:

a.

When the associated ACTION requirements to be entered permit continued operation in the OPERATIONAL CONDITION or other specified condition in the Applicability for an unlimited period of time; or

b.

After performance of a risk assessment addressing inoperable systems and components, consideration of the results, determination of the acceptability of entering the OPERATIONAL CONDITION 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 OPERATIONAL CONDITIONS or other specified conditions in the Applicability that are required to comply with ACTION requirements or that are part of a shutdown of the unit.

LIMERICK - UNIT 2 3/4 0-1 Amendment No. 132, 181, 189, 197,

3/4.0 APPLICABILITY LIMITING CONDITION FOR OPERATION (Continued) 3.0.9 When one or more required barriers are unable to perform their related support function(s), any supported system Limiting Conditions for Operation are not required to be declared not met solely for this reason for up to 30 days provided that at least one train or subsystem of the supported system is OPERABLE and supported by barriers capable of providing their related support function(s), and risk is assessed and managed. This specification may be concurrently applied to more than one train or subsystem of a multiple train or subsystem supported system provided at least one train or subsystem of the supported system is OPERABLE and the barriers supporting each of these trains or subsystems provide their related support function(s) for different categories of initiating events.

For the purposes of this specification, the High Pressure Coolant Injection system, the Reactor Core Isolation Cooling system, and the Automatic Depressurization System are considered independent subsystems of a single system.

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

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

LIMERICK - UNIT 2 3/4 0-1b Amendment No.

Retrieved from "https://kanterella.com/w/index.php?title=JAFP-20-0049,_Application_to_Adopt_TSTF-427,_Revision_2,_Allowance_for_Non_Technical_Specification_Barrier_Degradation_on_Supported_System_Operability&oldid=4125902"