|
---|
Category:Technical Specification
MONTHYEARRA-23-0121, License Amendment Request to Adopt TSTF-258-A, Revision 4, Regarding Changes to Technical Specification Section 5.7, High Radiation Area2023-10-0505 October 2023 License Amendment Request to Adopt TSTF-258-A, Revision 4, Regarding Changes to Technical Specification Section 5.7, High Radiation Area ML23145A1602023-05-25025 May 2023 Submittal of Updated Final Safety Analysis Report (Revision No. 30), Independent Spent Fuel Storage Installation Safety Analysis Report (Revision No. 28), Technical Specifications Bases Revisions, Quality RA-22-0091, Application to Revise Technical Specifications to Adopt TSTF-554, Revision 1, Revise Reactor Coolant Leakage Requirements2023-02-16016 February 2023 Application to Revise Technical Specifications to Adopt TSTF-554, Revision 1, Revise Reactor Coolant Leakage Requirements RA-22-0118, License Amendment Request to Revise Restrictive Technical Specification Surveillance Requirement Frequencies2023-02-0101 February 2023 License Amendment Request to Revise Restrictive Technical Specification Surveillance Requirement Frequencies RA-22-0153, License Amendment Request to Add Feedwater Isolation on Steam Generator Level High-High to Technical Specification 3.3.2 and Update the List of Analytical Methods Used in the Determination of Core.2022-09-21021 September 2022 License Amendment Request to Add Feedwater Isolation on Steam Generator Level High-High to Technical Specification 3.3.2 and Update the List of Analytical Methods Used in the Determination of Core. RA-21-0183, Remove 4.160 Kilovolt Bus 2 from Surveillance Requirement 3.8.1.16 (Automatic Transfer Capability from Unit Auxiliary Transformer to Startup Transformer)2022-04-28028 April 2022 Remove 4.160 Kilovolt Bus 2 from Surveillance Requirement 3.8.1.16 (Automatic Transfer Capability from Unit Auxiliary Transformer to Startup Transformer) RA-20-0107, Duke Energy Progress, LLC, and Duke Energy Carolinas, LLC, Application to Revise Technical Specifications to Adopt TSTF-541, Add Exceptions to Surveillance Requirements for Valves and Dampers Locked in the Actuated Position2022-01-18018 January 2022 Duke Energy Progress, LLC, and Duke Energy Carolinas, LLC, Application to Revise Technical Specifications to Adopt TSTF-541, Add Exceptions to Surveillance Requirements for Valves and Dampers Locked in the Actuated Position RA-22-0017, Supplement to Application to Revise Technical Specifications to Adopt TSTF-577, Revised Frequencies for Steam Generator Tube Inspections2022-01-0606 January 2022 Supplement to Application to Revise Technical Specifications to Adopt TSTF-577, Revised Frequencies for Steam Generator Tube Inspections RA-21-0057, Independent Spent Fuel Storage Installation, Submittal of Updated Final Safety Analysis Report (Revision No. 29), Independent Spent Fuel Storage Installation Safety Analysis Report (Revision No. 27), Technical .2021-05-27027 May 2021 Independent Spent Fuel Storage Installation, Submittal of Updated Final Safety Analysis Report (Revision No. 29), Independent Spent Fuel Storage Installation Safety Analysis Report (Revision No. 27), Technical . RA-19-0183, License Amendment Request to Add New Feedwater Bypass Valves to Technical Specification 3.7.32019-07-29029 July 2019 License Amendment Request to Add New Feedwater Bypass Valves to Technical Specification 3.7.3 RA-19-0006, License Amendment Application to Relocate Technical Specification Unit/Facility Staff Qualification ANSI N18.1-1971, ANSI/ANS-3.1-1978 and ANSI/ANS-3.1-1981 Requirements to the Duke Energy Corporation Quality Assurance Program Description2019-07-0808 July 2019 License Amendment Application to Relocate Technical Specification Unit/Facility Staff Qualification ANSI N18.1-1971, ANSI/ANS-3.1-1978 and ANSI/ANS-3.1-1981 Requirements to the Duke Energy Corporation Quality Assurance Program Description RNP-RA/18-0044, Supplement to License Amendment Request Proposing to Add a Qualified Offsite Circuit to Technical Specification 3.8.1, AC Sources - Operating and the Use of Load Tap Changers in the Automatic Mode of Operation on the Startup Transform2018-07-11011 July 2018 Supplement to License Amendment Request Proposing to Add a Qualified Offsite Circuit to Technical Specification 3.8.1, AC Sources - Operating and the Use of Load Tap Changers in the Automatic Mode of Operation on the Startup Transformers RA-18-0001, Duke Energy Progress, LLC and Duke Energy Carolinas, LLC - License Amendment Application to Remove Heaters from Ventilation System Technical Specifications2018-05-10010 May 2018 Duke Energy Progress, LLC and Duke Energy Carolinas, LLC - License Amendment Application to Remove Heaters from Ventilation System Technical Specifications ML18130A8072018-05-10010 May 2018 Duke Energy Progress, LLC and Duke Energy Carolinas, LLC - Submittal of License Amendment Application to Remove Heaters from Ventilation System Technical Specifications RA-18-000, Duke Energy Progress, LLC and Duke Energy Carolinas, LLC - Submittal of License Amendment Application to Remove Heaters from Ventilation System Technical Specifications2018-05-10010 May 2018 Duke Energy Progress, LLC and Duke Energy Carolinas, LLC - Submittal of License Amendment Application to Remove Heaters from Ventilation System Technical Specifications RA-17-0005, Application to Revise Technical Specifications to Adopt TSTF-545, Revision 3, TS Inservice Testing Program Removal & Clarify SR Usage Rule Application to Section 5.5 Testing2017-11-0707 November 2017 Application to Revise Technical Specifications to Adopt TSTF-545, Revision 3, TS Inservice Testing Program Removal & Clarify SR Usage Rule Application to Section 5.5 Testing RA-17-0022, Technical Specification Changes to Support Self-Performance of Core Reload Design and Safety Analyses2017-10-19019 October 2017 Technical Specification Changes to Support Self-Performance of Core Reload Design and Safety Analyses RA-17-0045, Supplement: Application to Revise Technical Specifications to Adopt TSTF-529, Clarify Use and Application Rules.2017-10-12012 October 2017 Supplement: Application to Revise Technical Specifications to Adopt TSTF-529, Clarify Use and Application Rules. RNP-RA/17-0041, Transmittal of Technical Specifications Bases Revisions2017-05-23023 May 2017 Transmittal of Technical Specifications Bases Revisions RNP-RA/17-0034, Modification of Request for Technical Specification Change to Change Technical Specification Surveillance Requirement Frequencies to Support 24-Month Fuel Cycles (MF9544)2017-05-0202 May 2017 Modification of Request for Technical Specification Change to Change Technical Specification Surveillance Requirement Frequencies to Support 24-Month Fuel Cycles (MF9544) RA-16-0019, Duke Energy Progress - Application to Revise Technical Specifications to Adopt TSTF-522, Revision 0, Revise Ventilation System Surveillance Requirements to Operate for 10 Hours Per Month Using the Consolidated Line Item Improvement Proces2016-09-27027 September 2016 Duke Energy Progress - Application to Revise Technical Specifications to Adopt TSTF-522, Revision 0, Revise Ventilation System Surveillance Requirements to Operate for 10 Hours Per Month Using the Consolidated Line Item Improvement Process RA-16-0007, Duke Energy Carolinas, LLC, Application to Revise TS to Adopt TSTF-427, Revision 2, Allowance for Non Technical Specification Barrier Degradation on Supported System Operability Using the Consolidated Line Item Improvement Process2016-06-23023 June 2016 Duke Energy Carolinas, LLC, Application to Revise TS to Adopt TSTF-427, Revision 2, Allowance for Non Technical Specification Barrier Degradation on Supported System Operability Using the Consolidated Line Item Improvement Process ML16116A0332016-04-24024 April 2016 Application for Technical Specification Change to Adopt Technical Specifications Task Force (TSTF)-339, Relocate TS Parameters to the COLR Consistent with WCAP-14483, Revision 2 RA-16-0005, Supplement to Application to Revise Technical Specifications for Methodology Report DPC-NE-2005-P, Revision 52016-02-0101 February 2016 Supplement to Application to Revise Technical Specifications for Methodology Report DPC-NE-2005-P, Revision 5 RNP-RA/15-0083, Submits Request for Technical Specification Change to Reactor Coolant System Pressure and Temperature Limits2015-11-0202 November 2015 Submits Request for Technical Specification Change to Reactor Coolant System Pressure and Temperature Limits RNP-RA/15-0086, Transmittal of Technical Specifications Bases Revisions2015-10-0808 October 2015 Transmittal of Technical Specifications Bases Revisions RNP-RA/15-0077, Submittal of Technical Specifications Section 5.6.6, Post Accident Monitoring Instrumentation Report, 14-Day Report for the Inoperability of Pressurizer Power Operated Relief Valves Position Indication2015-09-0101 September 2015 Submittal of Technical Specifications Section 5.6.6, Post Accident Monitoring Instrumentation Report, 14-Day Report for the Inoperability of Pressurizer Power Operated Relief Valves Position Indication ML14188B0152014-06-20020 June 2014 Request for Technical Specifications (TS) Change Regarding Correction to TS 5.5.9.b.2, Steam Generator (SG) Program Accident-Induced Leakage Performance Criterion RNP-RA/14-0042, Transmittal of Technical Specifications Bases Revisions2014-04-29029 April 2014 Transmittal of Technical Specifications Bases Revisions RNP-RA/13-0077, License Amendment Request for Technical Specification(Ts) Change to Use NRC-Approved TSTF-491, Revision 2, Removal of Main Steam and Main Feedwater Valve Isolation Times from Technical Specifications2013-09-30030 September 2013 License Amendment Request for Technical Specification(Ts) Change to Use NRC-Approved TSTF-491, Revision 2, Removal of Main Steam and Main Feedwater Valve Isolation Times from Technical Specifications RNP-RA/13-0038, Replacement of Technical Specification Pages to Correct Typographical Errors in Request for TS Changes Regarding TS 3.1.4 Rod Group Alignment Limits and TS 3.1.7 Rod Position Indication2013-04-24024 April 2013 Replacement of Technical Specification Pages to Correct Typographical Errors in Request for TS Changes Regarding TS 3.1.4 Rod Group Alignment Limits and TS 3.1.7 Rod Position Indication RNP-RA/12-0066, Transmittal of Technical Specifications Bases Revisions2012-09-17017 September 2012 Transmittal of Technical Specifications Bases Revisions RNP-RA/12-0033, Application for Technical Specification Change to Add LCO 3.0.8 on the Inoperability of Snubbers Using the Consolidated Line Item Improvement Process2012-08-0606 August 2012 Application for Technical Specification Change to Add LCO 3.0.8 on the Inoperability of Snubbers Using the Consolidated Line Item Improvement Process RNP-RA/11-0095, Request for Technical Specifications Change Regarding Missed Surveillance Using the Consolidated Line Item Improvement Process2012-02-10010 February 2012 Request for Technical Specifications Change Regarding Missed Surveillance Using the Consolidated Line Item Improvement Process RNP-RA/11-0002, Transmittal of Technical Specifications Bases Revisions2011-01-12012 January 2011 Transmittal of Technical Specifications Bases Revisions RNP-RA/10-0001, Request for Technical Specification Changes to Section 3.3.2, Engineered Safety Feature, Actuation System (ESFAS) Instrumentation, and Section 3.3.6, Containment Ventilation Isolation Instrumentation2010-03-0505 March 2010 Request for Technical Specification Changes to Section 3.3.2, Engineered Safety Feature, Actuation System (ESFAS) Instrumentation, and Section 3.3.6, Containment Ventilation Isolation Instrumentation ML0828301372008-10-0606 October 2008 License Amendment Request to Eliminate Work Hour Controls to Support Compliance with Revised 10 CFR 26 RNP-RA/08-0006, Request for Technical Specifications Changes Related to Control Room Habitability - Supplement2008-04-0101 April 2008 Request for Technical Specifications Changes Related to Control Room Habitability - Supplement RNP-RA/08-0016, Supplement to the Request for Administrative Changes to the Technical Specifications2008-02-0404 February 2008 Supplement to the Request for Administrative Changes to the Technical Specifications RNP-RA/07-0126, Request for Technical Specifications Change to Section 3.6.8 Isolation Valve Seal Water System2007-11-29029 November 2007 Request for Technical Specifications Change to Section 3.6.8 Isolation Valve Seal Water System RNP-RA/07-0073, Request for Administrative Changes to the Operating License and Technical Specifications2007-11-19019 November 2007 Request for Administrative Changes to the Operating License and Technical Specifications RNP-RA/07-0124, Request for Technical Specifications Change to Section 3.1.7 Rod Position Indication2007-11-15015 November 2007 Request for Technical Specifications Change to Section 3.1.7 Rod Position Indication RNP-RA/07-0108, Transmittal of Technical Specifications Bases Revisions2007-10-30030 October 2007 Transmittal of Technical Specifications Bases Revisions RNP-RA/07-0056, Request for Technical Specifications Changes Related to Control Room Habitability2007-07-17017 July 2007 Request for Technical Specifications Changes Related to Control Room Habitability RNP-RA/06-0095, Request for Technical Specifications Change to Section 3.3.3, Post Accident Monitoring2007-02-0202 February 2007 Request for Technical Specifications Change to Section 3.3.3, Post Accident Monitoring ML0702404832007-01-19019 January 2007 H. B. Robinson, Unit 2 - Resubmission of Request for Technical Specifications Change Regarding Steam Generator Alternate Repair Criteria ML0634104702006-11-29029 November 2006 Technical Specification Pages Re Core Operating Limit Report References, ML0628900812006-10-12012 October 2006 Submittal of H. B. Robinson, Unit 2 - Request for Technical Specifications Change Regarding Steam Generator Alternate Repair Criteria RNP-RA/06-0033, Transmittal of Technical Specifications Bases Revisions2006-04-0606 April 2006 Transmittal of Technical Specifications Bases Revisions RNP-RA/05-0107, Request for Technical Specifications Change to Section 3.8.1 for the Diesel Generator Automatic Trips Bypass2005-11-30030 November 2005 Request for Technical Specifications Change to Section 3.8.1 for the Diesel Generator Automatic Trips Bypass 2023-05-25
[Table view] Category:Amendment
MONTHYEARRA-22-0091, Application to Revise Technical Specifications to Adopt TSTF-554, Revision 1, Revise Reactor Coolant Leakage Requirements2023-02-16016 February 2023 Application to Revise Technical Specifications to Adopt TSTF-554, Revision 1, Revise Reactor Coolant Leakage Requirements RA-22-0153, License Amendment Request to Add Feedwater Isolation on Steam Generator Level High-High to Technical Specification 3.3.2 and Update the List of Analytical Methods Used in the Determination of Core.2022-09-21021 September 2022 License Amendment Request to Add Feedwater Isolation on Steam Generator Level High-High to Technical Specification 3.3.2 and Update the List of Analytical Methods Used in the Determination of Core. RA-21-0183, Remove 4.160 Kilovolt Bus 2 from Surveillance Requirement 3.8.1.16 (Automatic Transfer Capability from Unit Auxiliary Transformer to Startup Transformer)2022-04-28028 April 2022 Remove 4.160 Kilovolt Bus 2 from Surveillance Requirement 3.8.1.16 (Automatic Transfer Capability from Unit Auxiliary Transformer to Startup Transformer) RA-19-0183, License Amendment Request to Add New Feedwater Bypass Valves to Technical Specification 3.7.32019-07-29029 July 2019 License Amendment Request to Add New Feedwater Bypass Valves to Technical Specification 3.7.3 RA-19-0006, License Amendment Application to Relocate Technical Specification Unit/Facility Staff Qualification ANSI N18.1-1971, ANSI/ANS-3.1-1978 and ANSI/ANS-3.1-1981 Requirements to the Duke Energy Corporation Quality Assurance Program Description2019-07-0808 July 2019 License Amendment Application to Relocate Technical Specification Unit/Facility Staff Qualification ANSI N18.1-1971, ANSI/ANS-3.1-1978 and ANSI/ANS-3.1-1981 Requirements to the Duke Energy Corporation Quality Assurance Program Description RNP-RA/18-0044, Supplement to License Amendment Request Proposing to Add a Qualified Offsite Circuit to Technical Specification 3.8.1, AC Sources - Operating and the Use of Load Tap Changers in the Automatic Mode of Operation on the Startup Transform2018-07-11011 July 2018 Supplement to License Amendment Request Proposing to Add a Qualified Offsite Circuit to Technical Specification 3.8.1, AC Sources - Operating and the Use of Load Tap Changers in the Automatic Mode of Operation on the Startup Transformers RA-18-0001, Duke Energy Progress, LLC and Duke Energy Carolinas, LLC - License Amendment Application to Remove Heaters from Ventilation System Technical Specifications2018-05-10010 May 2018 Duke Energy Progress, LLC and Duke Energy Carolinas, LLC - License Amendment Application to Remove Heaters from Ventilation System Technical Specifications ML18130A8072018-05-10010 May 2018 Duke Energy Progress, LLC and Duke Energy Carolinas, LLC - Submittal of License Amendment Application to Remove Heaters from Ventilation System Technical Specifications RA-18-000, Duke Energy Progress, LLC and Duke Energy Carolinas, LLC - Submittal of License Amendment Application to Remove Heaters from Ventilation System Technical Specifications2018-05-10010 May 2018 Duke Energy Progress, LLC and Duke Energy Carolinas, LLC - Submittal of License Amendment Application to Remove Heaters from Ventilation System Technical Specifications RA-17-0005, Application to Revise Technical Specifications to Adopt TSTF-545, Revision 3, TS Inservice Testing Program Removal & Clarify SR Usage Rule Application to Section 5.5 Testing2017-11-0707 November 2017 Application to Revise Technical Specifications to Adopt TSTF-545, Revision 3, TS Inservice Testing Program Removal & Clarify SR Usage Rule Application to Section 5.5 Testing RA-17-0022, Technical Specification Changes to Support Self-Performance of Core Reload Design and Safety Analyses2017-10-19019 October 2017 Technical Specification Changes to Support Self-Performance of Core Reload Design and Safety Analyses RNP-RA/17-0034, Modification of Request for Technical Specification Change to Change Technical Specification Surveillance Requirement Frequencies to Support 24-Month Fuel Cycles (MF9544)2017-05-0202 May 2017 Modification of Request for Technical Specification Change to Change Technical Specification Surveillance Requirement Frequencies to Support 24-Month Fuel Cycles (MF9544) RNP-RA/15-0083, Submits Request for Technical Specification Change to Reactor Coolant System Pressure and Temperature Limits2015-11-0202 November 2015 Submits Request for Technical Specification Change to Reactor Coolant System Pressure and Temperature Limits RNP-RA/13-0077, License Amendment Request for Technical Specification(Ts) Change to Use NRC-Approved TSTF-491, Revision 2, Removal of Main Steam and Main Feedwater Valve Isolation Times from Technical Specifications2013-09-30030 September 2013 License Amendment Request for Technical Specification(Ts) Change to Use NRC-Approved TSTF-491, Revision 2, Removal of Main Steam and Main Feedwater Valve Isolation Times from Technical Specifications RNP-RA/12-0033, Application for Technical Specification Change to Add LCO 3.0.8 on the Inoperability of Snubbers Using the Consolidated Line Item Improvement Process2012-08-0606 August 2012 Application for Technical Specification Change to Add LCO 3.0.8 on the Inoperability of Snubbers Using the Consolidated Line Item Improvement Process ML0828301372008-10-0606 October 2008 License Amendment Request to Eliminate Work Hour Controls to Support Compliance with Revised 10 CFR 26 RNP-RA/08-0006, Request for Technical Specifications Changes Related to Control Room Habitability - Supplement2008-04-0101 April 2008 Request for Technical Specifications Changes Related to Control Room Habitability - Supplement RNP-RA/08-0016, Supplement to the Request for Administrative Changes to the Technical Specifications2008-02-0404 February 2008 Supplement to the Request for Administrative Changes to the Technical Specifications RNP-RA/07-0126, Request for Technical Specifications Change to Section 3.6.8 Isolation Valve Seal Water System2007-11-29029 November 2007 Request for Technical Specifications Change to Section 3.6.8 Isolation Valve Seal Water System RNP-RA/07-0073, Request for Administrative Changes to the Operating License and Technical Specifications2007-11-19019 November 2007 Request for Administrative Changes to the Operating License and Technical Specifications RNP-RA/07-0124, Request for Technical Specifications Change to Section 3.1.7 Rod Position Indication2007-11-15015 November 2007 Request for Technical Specifications Change to Section 3.1.7 Rod Position Indication RNP-RA/07-0056, Request for Technical Specifications Changes Related to Control Room Habitability2007-07-17017 July 2007 Request for Technical Specifications Changes Related to Control Room Habitability RNP-RA/06-0095, Request for Technical Specifications Change to Section 3.3.3, Post Accident Monitoring2007-02-0202 February 2007 Request for Technical Specifications Change to Section 3.3.3, Post Accident Monitoring ML0634104702006-11-29029 November 2006 Technical Specification Pages Re Core Operating Limit Report References, ML0628900812006-10-12012 October 2006 Submittal of H. B. Robinson, Unit 2 - Request for Technical Specifications Change Regarding Steam Generator Alternate Repair Criteria RNP-RA/05-0107, Request for Technical Specifications Change to Section 3.8.1 for the Diesel Generator Automatic Trips Bypass2005-11-30030 November 2005 Request for Technical Specifications Change to Section 3.8.1 for the Diesel Generator Automatic Trips Bypass ML0522003672005-08-0202 August 2005 Technical Specification Pages Re Bases Control Program (Tac No. MC3636) ML0511102212005-04-19019 April 2005 Enclosure, Amendment No. 204 on TS Revisions to Eliminate Monthly Operating and Annual Occupational Radiation Exposure Report Requirements (Tac No. MC5129) RNP-RA/05-0005, Request for Technical Specifications Change to Section 3.8.4, DC Sources - Operating2005-02-14014 February 2005 Request for Technical Specifications Change to Section 3.8.4, DC Sources - Operating ML0405707022004-02-18018 February 2004 Informational Copy of Operating License & Appendices. Technical Specification Pages 3.3-20 Through 3.3-28 for Amendment 176 ML0405706622004-02-18018 February 2004 Informational Copy of Operating License & Appendices. Technical Specification Pages 1.3-1 Through 1.3-13 for Amendment 176 ML0405706652004-02-18018 February 2004 Informational Copy of Operating License & Appendices. Technical Specification Pages 1.1-1 Through 1.2-3 for Amendment 176 ML0405706702004-02-18018 February 2004 Informational Copy of Operating License & Appendices. Technical Specification Pages 1.4-1 Through 1.4-4 for Amendment 176 ML0405706752004-02-18018 February 2004 Informational Copy of Operating License & Appendices. Operating License Effective Pages Through Technical Specifications Effictive Pages ML0405706832004-02-18018 February 2004 Informational Copy of Operating License & Appendices. Technical Specification Table of Contents for Amendment 176 ML0405706872004-02-18018 February 2004 Informational Copy of Operating License & Appendices. Technical Specification Pages 2.0-1 Through 2.0-2 for Amendment 176 ML0405706912004-02-18018 February 2004 Informational Copy of Operating License & Appendices. Technical Specification Pages 3.0.1 Through 3.0.5 for Amendment 176 ML0405706942004-02-18018 February 2004 Informational Copy of Operating License & Appendices. Technical Specification Pages 3.1-1 Through 3.1-21 for Amendment 176 ML0405706962004-02-18018 February 2004 Informational Copy of Operating License & Appendices. Technical Specification Pages 3.2-1 Through 3.2-14 for Amendment 176 ML0405706992004-02-18018 February 2004 Informational Copy of Operating License & Appendices. Technical Specification Pages 3.3-1 Through 3.3-19 for Amendment 176 ML0407804992004-02-18018 February 2004 Informational Copy of Operating License & Appendices. Technical Specification Pages 3.6-1 Through 3.6-21 for Amendment 176 ML0407805072004-02-18018 February 2004 Informational Copy of Operating License & Appendices. Technical Specification Pages 5.0-1 Through 5.0-34 for Amendment 176 ML0407805052004-02-18018 February 2004 Informational Copy of Operating License & Appendices. Technical Specification Pages 4.0-1 for Amendment 176 Through 4.0-3 for Amendment 198 ML0407805042004-02-18018 February 2004 Informational Copy of Operating License & Appendices. Technical Specification Pages 3.9-1 Through 3.0-12 for Amendment 176 ML0407805022004-02-18018 February 2004 Informational Copy of Operating License & Appendices. Technical Specification Pages 3.8-1 for Amendment 176 Through 3.8-36 for Amendment 190 ML0407805002004-02-18018 February 2004 Informational Copy of Operating License & Appendices. Technical Specification Pages 3.7-1 Through 3.7-33 for Amendment 176 ML0405707052004-02-18018 February 2004 Informational Copy of Operating License & Appendices. Techncial Specification Pages 3.3-29 Through 3.3-32 for Amendment 176 ML0407804962004-02-18018 February 2004 Informational Copy of Operating License & Appendices. Technical Specification Pages 3.5-1 Through 3.5-11 for Amendment 176 ML0407804942004-02-18018 February 2004 Informational Copy of Operating License & Appendices. Technical Specification Pages 3.4-1 Through 3.4-28 for Amendment 176 ML0407804912004-02-18018 February 2004 Informational Copy of Operating License & Appendices. Technical Specification Pages 3.4-29 Through 3.4-51 for Amendment 176 2023-02-16
[Table view] |
Text
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 MODEor specified condition stated in the Applicability of the LCO. Required Actions must be completed prior to the expiration of the specified Completion Time. An ACTIONS Condition remains in effect and the Required Actions apply until the Condition no longer exists or the unit is not within the LCO Applicability.
If situations are discovered that require entry into more than one Condition at a time within a single LCO (multiple Conditions), the Required Actions for each Condition must be performed within the associated Completion Time. When in multiple Conditions, separate Completion Times are tracked for each Condition starting from the time of discovery of the situation that required entry into the Condition.
Once a Condition has been entered, subsequent trains, subsystems, components, or variables expressed in the Condition, discovered to be inoperable or not within limits, will not result in separate entry into the Condition, unless specifically stated. The Required Actions of the Condition continue to apply to each additional failure, with Completion Times based on initial entry into the Condition.
(continued)
HBRSEP Unit No. 2 1.3-l Amendment No. 176
Completion Times 1.3 1.3 Completion Times DESCRIPTION However, when a subsequent train, subsystem, component, or (continued) 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;
- 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 hour2.777778e-4 days <br />0.00667 hours <br />3.968254e-5 weeks <br />9.132e-6 months <br />s: or
- b. The stated Completion Time as measured from discovery of the subsequent inoperability.
The above Completion Time extensions do not apply to those Specifications that have exceptions that allow completely separate re-entry into the Condition (for each train, subsystem, component, or variable expressed in the Condition) and separate tracking of Completion Times based on this re-entry. These exceptions are stated in individual Specifications.
The above Completion Time extension does not apply to a Completion Time with a modified "time zero." This modified "time zero" may be expressed as a repetitive time (i.e., "once per 8 hours9.259259e-5 days <br />0.00222 hours <br />1.322751e-5 weeks <br />3.044e-6 months <br />," where the Completion Time is referenced from a previous completion of the Required Action versus the time of Condition entry) or as a time modified by the phrase "from discovery . . ." Example 1.3-3 illustrates one use of this type of Completion Time. The 10 day Completion Time specified for Conditions A and B in Example 1.3-3 may not be extended.
(continued)
HBRSEP Unit No. 2 1.3-2 Amendment No. 176
Completion Times 1.3 1.3 Completion Times (continued)
EXAMPLES The following examples illustrate the use of Completion Times with different types of Conditions and changing Conditions.
EXAMPLE 1.3-l ACTIONS CONDITION REQUIRED ACTION COMPLETIONTIME I I B. Required B.l Be in MODE3. 6 hours6.944444e-5 days <br />0.00167 hours <br />9.920635e-6 weeks <br />2.283e-6 months <br /> Action and associated AND Completion Time not B.2 Be in MODE5. 36 hours4.166667e-4 days <br />0.01 hours <br />5.952381e-5 weeks <br />1.3698e-5 months <br /> met.
Condition B has two Required Actions. Each Required Action has its own separate Completion Time. Each Completion Time is referenced to the time that Condition B is entered.
The Required Actions of Condition B are to be in MODE3 within 6 hours6.944444e-5 days <br />0.00167 hours <br />9.920635e-6 weeks <br />2.283e-6 months <br /> AND in MODE5 within 36 hours4.166667e-4 days <br />0.01 hours <br />5.952381e-5 weeks <br />1.3698e-5 months <br />. A total of 6 hours6.944444e-5 days <br />0.00167 hours <br />9.920635e-6 weeks <br />2.283e-6 months <br /> is allowed for reaching MODE3 and a total of 36 hours4.166667e-4 days <br />0.01 hours <br />5.952381e-5 weeks <br />1.3698e-5 months <br /> (not 42 hours4.861111e-4 days <br />0.0117 hours <br />6.944444e-5 weeks <br />1.5981e-5 months <br />) is allowed for reaching MODE 5 from the time that Condition B was entered. If MODE3 is reached within 3 hours3.472222e-5 days <br />8.333333e-4 hours <br />4.960317e-6 weeks <br />1.1415e-6 months <br />, the time allowed for reaching MODE 5 is the next 33 hours3.819444e-4 days <br />0.00917 hours <br />5.456349e-5 weeks <br />1.25565e-5 months <br /> because the total time allowed for reaching MODE5 is 36 hours4.166667e-4 days <br />0.01 hours <br />5.952381e-5 weeks <br />1.3698e-5 months <br />.
If Condition B is entered while in MODE3, the time allowed for reaching MODE5 is the next 36 hours4.166667e-4 days <br />0.01 hours <br />5.952381e-5 weeks <br />1.3698e-5 months <br />.
(continued)
HBRSEP Unit No. 2 1.3-3 Amendment No. 176
Completion Times 1.3 1.3 Completion Times EXAMPLES EXAMPLE 1.3-2 (continued)
ACTIONS CONDITION REQUIRED ACTION COMPLETIONTIME I
A. One pump A.1 Restore pump to 7 days inoperable. OPERABLE status.
B. Required B.l Be in MODE3. 6 hours6.944444e-5 days <br />0.00167 hours <br />9.920635e-6 weeks <br />2.283e-6 months <br /> Action and associated AND Completion Time not 8.2 Be in MODE5. 36 hours4.166667e-4 days <br />0.01 hours <br />5.952381e-5 weeks <br />1.3698e-5 months <br /> met.
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.l 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 (continued)
HBRSEP Unit No. 2 1.3-4 Amendment No. 176
Completion Times 1.3 1.3 Completion Times EXAMPLES EXAMPLE 1.3-2 (continued)
Condition A has expired, LCO 3.0.3 may be exited and operation continued in accordance with Condition B. The Completion Time for Condition B is tracked from the time the Condition A Completion Time expired.
On restoring one of the pumps to OPERABLE status, the Condition A Completion Time is not reset, but continues from the time the first pump was declared inoperable. This Completion Time may be extended if the pump restored to OPERABLE status was the first inoperable pump. A 24 hour2.777778e-4 days <br />0.00667 hours <br />3.968254e-5 weeks <br />9.132e-6 months <br /> extension to the stated 7 days is allowed, provided this does not result in the second pump being inoperable for
> 7 days.
(continued)
HBRSEP Unit No. 2 1.3-5 Amendment No. 176
Completion Times 1.3 1.3 Completion Times EXAMPLES EXAMPLE 1.3-3 (continued)
ACTIONS CONDITION REQUIRED ACTION COMPLETIONTIME A. One A.1 Restore 7 days Function X Function X train train to OPERABLE AND inoperable. status.
10 days from discovery of failure to meet the LCO B. One B.l Restore 72 hours8.333333e-4 days <br />0.02 hours <br />1.190476e-4 weeks <br />2.7396e-5 months <br /> Function Y Function Y train train to OPERABLE AND inoperable. status.
10 days from discovery of failure to meet the LCO C. One C.l Restore 72 hours8.333333e-4 days <br />0.02 hours <br />1.190476e-4 weeks <br />2.7396e-5 months <br /> Function X Function X train train to OPERABLE inoperable. status.
AND OR One C.2 Restore 72 hours8.333333e-4 days <br />0.02 hours <br />1.190476e-4 weeks <br />2.7396e-5 months <br /> Function Y Function Y train train to OPERABLE inoperable. status.
(continued)
HBRSEP Unit No. 2 1.3-6 Amendment No. 176
Completion Times 1.3 1.3 Completion Times EXAMPLES EXAMPLE 1.3-3 (continued)
When one Function X train and one Function Y train are inoperable, Condition A and Condition B are concurrently applicable. The Completion Times for Condition A and Condition B are tracked separately for each train starting from the time each train was declared inoperable and the Condition was entered. A separate Completion Time is established for Condition C and tracked from the time the second train was declared inoperable (i.e., the time the situation described in Condition C was discovered).
If Required Action C.2 is completed within the specified Completion Time, Conditions B and C are exited. If the Completion Time for Required Action A.1 has not expired, operation may continue in accordance with Condition A. The remaining Completion Time in Condition A is measured from the time the affected train was declared inoperable (i.e.,
initial entry into Condition A).
The Completion Times of Conditions A and B are modified by a logical connector with a separate 10 day Completion Time measured from the time it was discovered the LCO was not met. In this example, without the separate Completion Time, it would be possible to alternate between Conditions A, B, and C in such a manner that operation could continue indefinitely without ever restoring systems to meet the LCO.
The separate Completion Time modified by the phrase "from discovery of failure to meet the LCO" is designed to prevent indefinite continued operation while not meeting the LCO.
This Completion Time allows for an exception to the normal "time zero" for beginning the Completion Time "clock". In this instance, the Completion Time "time zero" is specified as commencing at the time the LCO was initially not met, instead of at the time the associated Condition was entered.
(continued)
HBRSEP Unit No. 2 1.3-7 Amendment No. 176
Completion Times 1.3 1.3 Completion Times EXAMPLES EXAMPLE 1.3-4 (continued)
ACTIONS CONDITION REQUIRED ACTION COMPLETIONTIME A. One or more A.1 Restore valve(s) 4 hours4.62963e-5 days <br />0.00111 hours <br />6.613757e-6 weeks <br />1.522e-6 months <br /> valves to OPERABLE inoperable. status.
B. Required B.l Be in MODE3. 6 hours6.944444e-5 days <br />0.00167 hours <br />9.920635e-6 weeks <br />2.283e-6 months <br /> Action and associated AND Completion Time not B.2 Be in MODE4. 12 hours1.388889e-4 days <br />0.00333 hours <br />1.984127e-5 weeks <br />4.566e-6 months <br /> met.
A single Completion Time is used for any number of valves inoperable at the same time. The Completion Time associated with Condition A is based on the initial entry into Condition A and is not tracked on a per valve basis.
Declaring subsequent valves inoperable, while Condition A is still in effect, does not trigger the tracking of separate Completion Times.
Once one of the valves has been restored to OPERABLE status, the Condition A Completion Time is not reset, but continues from the time the first valve was declared inoperable. The Completion Time may be extended if the valve restored to OPERABLE status was the first inoperable valve. The Condition A Completion Time may be extended for up to 4 hours4.62963e-5 days <br />0.00111 hours <br />6.613757e-6 weeks <br />1.522e-6 months <br /> provided this does not result in any subsequent valve being inoperable for > 4 hours4.62963e-5 days <br />0.00111 hours <br />6.613757e-6 weeks <br />1.522e-6 months <br />.
If the Completion Time of 4 hours4.62963e-5 days <br />0.00111 hours <br />6.613757e-6 weeks <br />1.522e-6 months <br /> (including the extension) expires while one or more valves are still inoperable, Condition B is entered.
(continued)
HBRSEP Unit No. 2 1.3-8 Amendment No. 176
Completion Times 1.3 1.3 Completion Times EXAMPLES EXAMPLE 1.3-5 (continued)
ACTIONS
____-1_--__---1-_-_--------- NOTE----------------------------
Separate Condition entry is allowed for each inoperable valve.
CONDITION REQUIRED ACTION COMPLETIONTIME A. One or more A.1 Restore valve to 4 hours4.62963e-5 days <br />0.00111 hours <br />6.613757e-6 weeks <br />1.522e-6 months <br /> valves OPERABLE status.
inoperable.
B. Required B.l Be in MODE3. 6 hours6.944444e-5 days <br />0.00167 hours <br />9.920635e-6 weeks <br />2.283e-6 months <br /> Action and associated Completion Time not B.2 Be in MODE4. 12 hours1.388889e-4 days <br />0.00333 hours <br />1.984127e-5 weeks <br />4.566e-6 months <br /> met.
The Note above the ACTIONS Table is a method of modifying how the Completion Time is tracked. If this method of modifying how the Completion Time is tracked was applicable only to a specific Condition, the Note would appear in that Condition rather than at the top of the ACTIONS Table.
The Note allows Condition A to be entered separately for each inoperable valve, and Completion Times tracked on a per valve basis. When a valve is declared inoperable, Condition A is entered and its Completion Time starts. If subsequent valves are declared inoperable, Condition A is entered for each valve and separate Completion Times start and are tracked for each valve.
(continued)
HBRSEP Unit No. 2 1.3-9 Amendment No. 176
Completion Times 1.3 1.3 Completion Times EXAMPLES EXAMPLE 1.3-5 (continued)
If the Completion Time associated with a valve in Condition A expires, Condition B is entered for that valve.
If the Completion Times associated with subsequent valves in Condition A expire, Condition B is entered separately for each valve and separate Completion Times start and are tracked for each valve. If a valve that caused entry into Condition 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 COMPLETIONTIME A. One channe 1 A.1 Perform Once per inoperable SR 3.x.x.x. 8 hours9.259259e-5 days <br />0.00222 hours <br />1.322751e-5 weeks <br />3.044e-6 months <br /> OR A.2 Reduce THERMAL 8 hours9.259259e-5 days <br />0.00222 hours <br />1.322751e-5 weeks <br />3.044e-6 months <br /> POWERto
< 50% RTP.
B. Required B.l Be in MODE3. 6 hours6.944444e-5 days <br />0.00167 hours <br />9.920635e-6 weeks <br />2.283e-6 months <br /> Action and associated Completion Time not met.
(continued)
HBRSEP Unit No. 2 1.3-10 Amendment No. 176
Completion Times 1.3 1.3 Completion Times EXAMPLES EXAMPLE 1.3-6 (continued)
Entry into Condition A offers a choice between Required Action A.1 or A.2. Required Action A.1 has a "once per" Completion Time, which qualifies for the 25% extension, per SR 3.0.2, to each performance after the initial performance.
The initial 8 hour9.259259e-5 days <br />0.00222 hours <br />1.322751e-5 weeks <br />3.044e-6 months <br /> interval of Required Action A.1 begins when Condition A is entered and the initial performance of Required Action A.1 must be complete within the first 8 hour9.259259e-5 days <br />0.00222 hours <br />1.322751e-5 weeks <br />3.044e-6 months <br /> interval. If Required Action A.1 is followed, and the Required Action is not met within the Completion Time (plus the extension allowed by SR 3.0.21, Condition B is entered.
If Required Action A.2 is followed and the Completion Time of 8 hours9.259259e-5 days <br />0.00222 hours <br />1.322751e-5 weeks <br />3.044e-6 months <br /> is not met, Condition B is entered.
If after entry into Condition B, Required Action A.1 or A.2 is met, Condition B is exited and operation may then continue in Condition A.
(continued)
HBRSEP Unit No. 2 1.341 Amendment No. 176
Completion Times 1.3 1.3 Completion Times EXAMPLES EXAMPLE 1.3-7 (continued)
ACTIONS CONDITION REQUIRED ACTION COMPLETIONTIME A. One A.1 Verify affected 1 hour1.157407e-5 days <br />2.777778e-4 hours <br />1.653439e-6 weeks <br />3.805e-7 months <br /> subsystem subsystem inoperable. isolated. AND Once per 8 hours9.259259e-5 days <br />0.00222 hours <br />1.322751e-5 weeks <br />3.044e-6 months <br /> thereafter AND A.2 Restore subsystem 72 hours8.333333e-4 days <br />0.02 hours <br />1.190476e-4 weeks <br />2.7396e-5 months <br /> to OPERABLE status.
B. Required B.1 Be in MODE3. 6 hours6.944444e-5 days <br />0.00167 hours <br />9.920635e-6 weeks <br />2.283e-6 months <br /> Action and associated AND Completion Time not B.2 Be in MODE5. 36 hours4.166667e-4 days <br />0.01 hours <br />5.952381e-5 weeks <br />1.3698e-5 months <br /> met.
Required Action A.1 has two Completion Times. The 1 hour1.157407e-5 days <br />2.777778e-4 hours <br />1.653439e-6 weeks <br />3.805e-7 months <br /> Completion Time begins at the time the Condition is entered and each "Once per 8 hours9.259259e-5 days <br />0.00222 hours <br />1.322751e-5 weeks <br />3.044e-6 months <br /> thereafter" interval begins upon performance of Required Action A.l.
If after Condition A is entered, Required Action A.1 is not met within either the initial 1 hour1.157407e-5 days <br />2.777778e-4 hours <br />1.653439e-6 weeks <br />3.805e-7 months <br /> or any subsequent 8 hour9.259259e-5 days <br />0.00222 hours <br />1.322751e-5 weeks <br />3.044e-6 months <br /> interval from the previous performance (plus the extension allowed by SR 3.0.21, Condition B is entered. The Completion Time clock for Condition A does not stop after Condition B is entered, but continues from the time (continued)
HBRSEP Unit No. 2 1.342 Amendment No. 176
Completion Times 1.3 1.3 Completion Times EXAMPLES EXAMPLE 1.3-7 (continued)
Condition A was initially entered. If Required Action A.1 is met after Condition B is entered, Condition B is exited and operation may continue in accordance with Condition A, provided the Completion Time for Required Action A.2 has not expired.
IMMEDIATE When Immediately is used as a Completion Time, the COMPLETIONTIME Required Action should be pursued without delay and in a controlled manner.
HBRSEP Unit No. 2 1.3-13 Amendment No. 176