Letter Sequence Approval |
---|
|
|
MONTHYEARML0404002262004-02-0505 February 2004 Tech Spec Pages for License Amendment 240, Extension of Delay Period as Result of Missed Surveillance Project stage: Approval ML0401500052004-02-0505 February 2004 License Amendment, Extension of Delay Period as Result of Missed Surveillance Project stage: Acceptance Review 2004-02-05
[Table View] |
|
---|
Category:Technical Specification
MONTHYEARML24214A0692024-08-0101 August 2024 Enclosure 18: Technical Basis Document No. 24-01-12-2888 Revision 1, Dose Contribution from Insignificant Radionuclides in the Oyster Creek Site-Specific Suite of Radiological Nuclides, February 14, 2024 RA-19-019, Submittal of Changes to Technical Specifications Bases2019-04-12012 April 2019 Submittal of Changes to Technical Specifications Bases RA-18-018, Submittal of Changes to Technical Specifications Bases2018-04-13013 April 2018 Submittal of Changes to Technical Specifications Bases RA-14-035, Submittal of Changes to Technical Specifications Bases2014-04-10010 April 2014 Submittal of Changes to Technical Specifications Bases RA-13-039, Submittal of Changes to Technical Specifications Bases2013-04-10010 April 2013 Submittal of Changes to Technical Specifications Bases RA-12-046, Submittal of Changes to Technical Specifications Bases2012-04-12012 April 2012 Submittal of Changes to Technical Specifications Bases RA-11-021, Submittal of Changes to Technical Specifications Bases2011-04-15015 April 2011 Submittal of Changes to Technical Specifications Bases RA-10-027, Technical Specification Change Request No. 356, Elimination of Daily Testing of an Operable Emergency Diesel Generator (EDG) When the Other EDG Is Declared Inoperable2010-06-25025 June 2010 Technical Specification Change Request No. 356, Elimination of Daily Testing of an Operable Emergency Diesel Generator (EDG) When the Other EDG Is Declared Inoperable RA-10-037, Submittal of Changes to Technical Specifications Bases2010-04-22022 April 2010 Submittal of Changes to Technical Specifications Bases ML1006200112010-02-25025 February 2010 Oyster Creek, License Amendment Request, Changes to Trunnion Room Secondary Containment Boundary RA-10-009, Oyster Creek, License Amendment Request, Changes to Trunnion Room Secondary Containment Boundary2010-02-25025 February 2010 Oyster Creek, License Amendment Request, Changes to Trunnion Room Secondary Containment Boundary RA-09-065, Application for Technical Specifications Change Regarding Risk-Informed Justification for Relocation of Specific Surveillance Frequency Requirements to Licensee Controlled Program (Adoption of TSTF-425, Rev 3)2009-10-30030 October 2009 Application for Technical Specifications Change Regarding Risk-Informed Justification for Relocation of Specific Surveillance Frequency Requirements to Licensee Controlled Program (Adoption of TSTF-425, Rev 3) RA-09-036, Submittal of Changes to Technical Specifications Bases, Includes Changes Through April 2, 20092009-04-17017 April 2009 Submittal of Changes to Technical Specifications Bases, Includes Changes Through April 2, 2009 RA-08-091, Submittal of Revised Bases Page - Relocation of Pressure and Temperature (P-T) Curves to the Pressure and Temperature Limits Report (PTLR)2008-09-29029 September 2008 Submittal of Revised Bases Page - Relocation of Pressure and Temperature (P-T) Curves to the Pressure and Temperature Limits Report (PTLR) ML0823907072008-08-21021 August 2008 Revised T.S. Pages Oyster Creek Nuclear Generating Station and Peach Bottom Atomic Power Station, Unit 3-Correction to Facility Operating Licenses RA-08-060, Transmittal of Supplemental Response - Amergen Application to Revise Technical Specifications Secondary Containment Operability Requirements During Refueling2008-07-0303 July 2008 Transmittal of Supplemental Response - Amergen Application to Revise Technical Specifications Secondary Containment Operability Requirements During Refueling RA-08-047, Application for Technical Specification Change Regarding Revision of Control Rod Notch Surveillance Test Frequency, Clarification of SRM Insert Control Rod Action and Clarification of a Frequency Example Using the Consolidation Line Item I2008-06-0909 June 2008 Application for Technical Specification Change Regarding Revision of Control Rod Notch Surveillance Test Frequency, Clarification of SRM Insert Control Rod Action and Clarification of a Frequency Example Using the Consolidation Line Item Im ML0810505452008-04-30030 April 2008 Technical Specification Pages for License Amendment No. 265 the Incorporation of TSTF-448, Revision 3, Control Room Habitability. (Tac MD5281) RA-08-041, Submittal of Changes to Technical Specifications Bases2008-04-28028 April 2008 Submittal of Changes to Technical Specifications Bases ML0731804012007-11-0202 November 2007 Technical Specification Change Request No. 338 - Secondary Containment Operability Requirements During Refueling RS-07-044, Amergen Energy Company, LLC, Request for Amendment to Technical Specifications Section for the Inservice Testing Program2007-08-0808 August 2007 Amergen Energy Company, LLC, Request for Amendment to Technical Specifications Section for the Inservice Testing Program ML0712401382007-04-27027 April 2007 Submittal of Changes to Technical Specifications Bases RS-07-020, Exelon/Amergen Application to Revise Technical Specifications Regarding Control Room Envelope Habitability in Accordance with TSTF-448, Revision 3, Using the Consolidated Line Item Improvement Process2007-04-12012 April 2007 Exelon/Amergen Application to Revise Technical Specifications Regarding Control Room Envelope Habitability in Accordance with TSTF-448, Revision 3, Using the Consolidated Line Item Improvement Process ML0627200562006-09-28028 September 2006 Technical Specification Change Request No. 339 - License Amendment Request to Revise Technical Specification Definitions of Channel Calibration, Channel Check and Channel Test ML0615103502006-05-25025 May 2006 Technical Specification Change Request No. 328 - Response to Request for Additional Information Concerning a Revision to Surveillance Requirements for Testing of Main Steam Line Electromatic Relief Valve ML0612902192006-04-24024 April 2006 Submittal of Changes to Technical Specifications Bases ML0534302552005-12-0202 December 2005 License Amendment Request Increase Safety Valve As-Found Setpoint Tolerance from 1% to 3% ML0513704932005-05-10010 May 2005 Oyster Creek Generating Station, Submittal of Changes to Technical Specifications Bases ML0508705402005-03-25025 March 2005 Technical Specification Change Request No. 332 - Upgrade of 69 Kv Offsite Power Transmission Line ML0506002452005-02-25025 February 2005 Technical Specification Pages Re Control Rod Operability Requirements RS-04-125, Exelon/Amergen Request for Amendment to Technical Specifications Administrative Controls to Incorporate Requirement for Control Room Envelope Integrity Program2004-11-29029 November 2004 Exelon/Amergen Request for Amendment to Technical Specifications Administrative Controls to Incorporate Requirement for Control Room Envelope Integrity Program ML0432200942004-11-16016 November 2004 Tech Spec Page for Amendment No. 252, Safety Limit Minimum Critical Power Ratio ML0432201012004-11-0808 November 2004 Unit 1 Amendment to Technical Specification ML0429505442004-10-15015 October 2004 Correction of Amendment No. 245 to Technical Specification Pages Electrical Power Sources ML0409003432004-03-23023 March 2004 Technical Specification Change Request No. 304/320 (Tscr) - Relocation of Independent Onsite Safety Review Group Function to the Quality Assurance Topical Report ML0409003312004-03-19019 March 2004 Technical Specification Change Request No. 322 Regarding Implementation of Option B Scram Time Testing ML0404002262004-02-0505 February 2004 Tech Spec Pages for License Amendment 240, Extension of Delay Period as Result of Missed Surveillance ML0326510472003-09-11011 September 2003 Supplement to License Amendment Request No. 306 for Revision to Technical Specifications Regarding DC Electrical Power Sources Based on TSTF-360 ML0316110292003-06-0202 June 2003 Technical Specification Change Request No. 314 - Startup Transformer and Emergency Diesel Generator Unavailability Periods ML0312006612003-04-21021 April 2003 License Amendment Request No. 306 - DC Electrical Power Sources Based on TSTF-360 ML0234505702002-11-27027 November 2002 Request for Technical Specifications Change to Eliminate Requirements for Post Accident Sampling System Using the Consolidated Line Item Improvement Process ML0215401332002-05-31031 May 2002 TS Pages to Amendment 289 Cycle-Specific Safety Limit Minimum Critical Power Ratio ML0215503542002-05-0707 May 2002 Tech Spec Change Request No. 294, Transmittal of Camera - Ready Tech Spec Pages ML0212900522002-04-26026 April 2002 Technical Specification Change Request No. 308 - General Electric Stability Analysis Methodology ML0208705752002-03-27027 March 2002 Technical Specifications, Amendment 227 - Allowing 24-month Capacity Test for DG Starting Batteries ML0208000102002-03-18018 March 2002 Technical Specification - Amendment, Correction of Pages Issued by Amendment No. 219 (Tac Nos. MA7804 and MB1748) ML0205801792002-02-11011 February 2002 Transmittal of Revised Oyster Creek Technical Specification Page 3 (Revision 224), Lep 1 (Revision 224), Lep 4 (Revision 224), Xxiv (Revision 224), TS Appendix a Pages 6-4 & 6-6 (Revision 224) ML0204300932002-02-0707 February 2002 Amendment 225, Tech Spec Pages ML0203005342002-01-23023 January 2002 Amendment 223, Technical Specification 5.3 Re Auxiliary Equipment ML0204501572002-01-17017 January 2002 Technical Specification Change Request 287, Transmittal of Camera-Ready Technical Specification Pages 2024-08-01
[Table view] Category:Amendment
MONTHYEARML1006200112010-02-25025 February 2010 Oyster Creek, License Amendment Request, Changes to Trunnion Room Secondary Containment Boundary RA-10-009, Oyster Creek, License Amendment Request, Changes to Trunnion Room Secondary Containment Boundary2010-02-25025 February 2010 Oyster Creek, License Amendment Request, Changes to Trunnion Room Secondary Containment Boundary RA-09-065, Application for Technical Specifications Change Regarding Risk-Informed Justification for Relocation of Specific Surveillance Frequency Requirements to Licensee Controlled Program (Adoption of TSTF-425, Rev 3)2009-10-30030 October 2009 Application for Technical Specifications Change Regarding Risk-Informed Justification for Relocation of Specific Surveillance Frequency Requirements to Licensee Controlled Program (Adoption of TSTF-425, Rev 3) ML0823907072008-08-21021 August 2008 Revised T.S. Pages Oyster Creek Nuclear Generating Station and Peach Bottom Atomic Power Station, Unit 3-Correction to Facility Operating Licenses RA-08-060, Transmittal of Supplemental Response - Amergen Application to Revise Technical Specifications Secondary Containment Operability Requirements During Refueling2008-07-0303 July 2008 Transmittal of Supplemental Response - Amergen Application to Revise Technical Specifications Secondary Containment Operability Requirements During Refueling RA-08-047, Application for Technical Specification Change Regarding Revision of Control Rod Notch Surveillance Test Frequency, Clarification of SRM Insert Control Rod Action and Clarification of a Frequency Example Using the Consolidation Line Item I2008-06-0909 June 2008 Application for Technical Specification Change Regarding Revision of Control Rod Notch Surveillance Test Frequency, Clarification of SRM Insert Control Rod Action and Clarification of a Frequency Example Using the Consolidation Line Item Im ML0810505452008-04-30030 April 2008 Technical Specification Pages for License Amendment No. 265 the Incorporation of TSTF-448, Revision 3, Control Room Habitability. (Tac MD5281) ML0627200562006-09-28028 September 2006 Technical Specification Change Request No. 339 - License Amendment Request to Revise Technical Specification Definitions of Channel Calibration, Channel Check and Channel Test ML0534302552005-12-0202 December 2005 License Amendment Request Increase Safety Valve As-Found Setpoint Tolerance from 1% to 3% ML0506002452005-02-25025 February 2005 Technical Specification Pages Re Control Rod Operability Requirements RS-04-125, Exelon/Amergen Request for Amendment to Technical Specifications Administrative Controls to Incorporate Requirement for Control Room Envelope Integrity Program2004-11-29029 November 2004 Exelon/Amergen Request for Amendment to Technical Specifications Administrative Controls to Incorporate Requirement for Control Room Envelope Integrity Program ML0432200942004-11-16016 November 2004 Tech Spec Page for Amendment No. 252, Safety Limit Minimum Critical Power Ratio ML0432201012004-11-0808 November 2004 Unit 1 Amendment to Technical Specification ML0429505442004-10-15015 October 2004 Correction of Amendment No. 245 to Technical Specification Pages Electrical Power Sources ML0409003432004-03-23023 March 2004 Technical Specification Change Request No. 304/320 (Tscr) - Relocation of Independent Onsite Safety Review Group Function to the Quality Assurance Topical Report ML0409003312004-03-19019 March 2004 Technical Specification Change Request No. 322 Regarding Implementation of Option B Scram Time Testing ML0404002262004-02-0505 February 2004 Tech Spec Pages for License Amendment 240, Extension of Delay Period as Result of Missed Surveillance ML0326510472003-09-11011 September 2003 Supplement to License Amendment Request No. 306 for Revision to Technical Specifications Regarding DC Electrical Power Sources Based on TSTF-360 ML0312006612003-04-21021 April 2003 License Amendment Request No. 306 - DC Electrical Power Sources Based on TSTF-360 ML0234505702002-11-27027 November 2002 Request for Technical Specifications Change to Eliminate Requirements for Post Accident Sampling System Using the Consolidated Line Item Improvement Process ML0215401332002-05-31031 May 2002 TS Pages to Amendment 289 Cycle-Specific Safety Limit Minimum Critical Power Ratio ML0208705752002-03-27027 March 2002 Technical Specifications, Amendment 227 - Allowing 24-month Capacity Test for DG Starting Batteries ML0208000102002-03-18018 March 2002 Technical Specification - Amendment, Correction of Pages Issued by Amendment No. 219 (Tac Nos. MA7804 and MB1748) ML0205801792002-02-11011 February 2002 Transmittal of Revised Oyster Creek Technical Specification Page 3 (Revision 224), Lep 1 (Revision 224), Lep 4 (Revision 224), Xxiv (Revision 224), TS Appendix a Pages 6-4 & 6-6 (Revision 224) ML0204300932002-02-0707 February 2002 Amendment 225, Tech Spec Pages ML0203005342002-01-23023 January 2002 Amendment 223, Technical Specification 5.3 Re Auxiliary Equipment ML17037C1771975-12-19019 December 1975 Letter Enclosing a Corrected Attachment to License Amendment No. 11 Change No. 27 to the Technical Specifications Provisional Operating License No. DPR-16 ML17037B7791974-02-0707 February 1974 Letter Regarding Petition for Derating of Certain Boiling Water Reactors and Enclosed Before the Atomic Safety and Licensing Appeal Board in the Matter of Vermont Yankee Nuclear Power Corporation - Vermont Yankee Nuclear ... 2010-02-25
[Table view] |
Text
TABLE OF CONTENTS (cont'd)
Section 5 Design Features Page 5.1 Site 5.1-1 5.2 Containment 5.2-1 5.3 Auxiliary Equipment 5.3-1 Section 6 Administrative Controls 6.1 Responsibility 6-1 6.2 Organization 6-1 6.3 Facility Staff Qualifications 6-2a 6.4 DELETED 6-3 6.5 Review and Audit 6-3 6-6 Reportable Event Action 6-9 6-7 Safety Limit Violation 6-9 6-8 Procedures and Programs 6-10 6-9 Reporting Requirements 6-13 6-10 Record Retention 6-17 6-11 Radiation Protection Program 6-18 6-12 (Deleted) 6-18 6-13 High Radiation Area 6-18 6-14 Environmental Qualification 6-19*
6-15 Integrity of Systems Outside Containment 6-19 6-16 Iodine Monitoring 6-19 6-17 Post Accident Sampling 6-20 6-18 Process Control Plan 6-20 6-19 Offsite Dose Calculation Manual 6-20 6-20 DELETED 6-20 6-21 Technical Specification (TS) Bases Control Program 6-21
- Issued by NRC Order dated 10-24-80 OYSTER CREEK iii Amendment No.: 94, 97,r9, 1-0 115, 131, 166, 136 232, 240
Section 4 Surveillance Requirements 4.0 Surveillance Requirement Applicability 4.0.1 Surveillance requirements shall be met during the modes or other specified conditions in the applicability for individual LCOs, unless otherwise stated in the surveillance requirements. 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 4.0.2. Surveillances do not have to be performed on inoperable equipment or variables outside specified limits.
4.0.2 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.
BASES: Surveillance Requirement 4.0.1 establishes the requirement that surveillance requirements must be met during the modes or other specified conditions in the applicability for which the requirements of the LCO apply, unless otherwise specified in the individual surveillance requirements. This specification is to ensure that surveillances are performed to verify the OPERABILITY of systems and components, and that variables are within specified limits. Failure to meet a surveillance within the specified frequency constitutes a failure to meet an LCO.
Systems and components are assumed to be OPERABLE when the associated surveillance requirements have been met. Nothing in this specification, however, is to be construed as implying that systems or components are OPERABLE when:
- a. The systems or components are known to be inoperable, although still meeting the surveillance requirements; or Oyster Creek 4.0-1 Amendment No. 4-5, 240
- b. The requirements of the surveillance(s) are known to be not met between required surveillance performances.
Surveillances do not have to be performed when the unit is in a mode or other specified condition for which the requirements of the associated LCO are not applicable, unless otherwise specified.
Surveillances, including surveillances invoked by required actions, do not have to be performed on inoperable equipment because the actions define the remedial measures that apply. Surveillances have to be met and performed prior to returning equipment to OPERABLE status.
Upon completion of maintenance, appropriate post maintenance testing is required to declare equipment OPERABLE. This includes ensuring applicable surveillances are not failed. Post maintenance testing may not be possible in the current mode or other specified conditions in the applicability due to the necessary unit parameters not having been established. In these situations, the equipment may be considered OPERABLE provided testing has been satisfactorily completed to the extent possible and the equipment is not otherwise believed tobbe incapable of performing its function. This will allow operation to proceed to a mode or other specified condition where other necessary post maintenance tests can be completed.
Surveillance Requirement 4.0.2 establishes the flexibility to defer declaring affected equipment inoperable or an affected variable outside the specified limits when a surveillance has not been completed within the specified frequency. A delay period of 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, applies from the point in time that it is discovered that the surveillance has not been performed in accordance with surveillance requirement 4.0.2 and not at the time that the specified frequency was not met.
This delay period provides adequate time to complete surveillances that have been missed. This delay period permits the completion of a surveillance before complying with required actions or other remedial measures that might preclude completion of the surveillance.
The basis for this delay period includes consideration of unit conditions, adequate planning, availability of personnel, the time required to perform the surveillance, the safety significance of the delay in completing the required surveillance, and the recognition that the most probable result of any particular surveillance being performed is the verification of conformance with the requirements.
Oyster Creek 4.0-2 Amendment No. 4-I, 240
When a surveillance with a frequency based not on time intervals, but upon specified unit conditions, operating situations, or requirements of regulations (e.g. prior to entering power operation after each fuel loading, or in accordance with 10 CFR 50, Appendix J, as modified by approved exemptions, etc.) is discovered to not have been performed when specified, Surveillance Requirement 4.0.2 allows for the full delay period of up to the specified frequency to perform the surveillance. However, since there is not a time interval specified, the missed surveillance should be performed at the first reasonable opportunity. Surveillance requirement 4.0.2 provides a time limit for, and allowances for the performance of, surveillances that become applicable as a consequence of mode changes imposed by required actions.
Failure to comply with specified surveillance frequencies is expected to be an infrequent occurrence. Use of the delay period established by Surveillance Requirement 4.0.2 is a flexibility which is not intended to be used as an operational convenience to extend surveillance intervals. While up to 24 hours2.777778e-4 days <br />0.00667 hours <br />3.968254e-5 weeks <br />9.132e-6 months <br /> or the limit of the specified frequency is provided to perform the missed surveillance, it is expected that the missed surveillance will be performed at the first reasonable opportunity. The determination of the first reasonable opportunity should include consideration of the impact on plant risk (from delaying the surveillance as well as any plant configuration changes required or shutting the plant down to perform the surveillance) and impact on any analysis assumptions, in addition to unit conditions, planning, availability of personnel, and the time required to perform the surveillance. This risk impact should be managed through the program in place to implement 10 CFR 50.65 (a)(4) and its implementation guidance, NRC Regulatory Guide 1.182, 'Assessing and Managing Risk Before Maintenance Activities at Nuclear Power Plants.' This Regulatory Guide addresses consideration of temporary and aggregate risk impacts, determination of risk management thresholds, and risk management action up to and including plant shutdown. The missed surveillance should be treated as an emergent condition as discussed in the Regulatory Guide. The risk evaluation may use quantitative, qualitative, or blended methods. The degree of depth and rigor of the evaluation should be commensurate with the importance of the component. Missed surveillances for important components should be analyzed quantitatively. If the results of the evaluation determine the risk increase is significant, this evaluation should be used to determine the safest course of action. All missed surveillances will be placed in the licensee's Corrective Action Program.
If a surveillance is not completed within the allowed delay period, then the equipment is considered inoperable or the variable is considered outside the specified limits and the completion times of the required actions for the applicable LCO conditions begin immediately upon expiration of the delay period. If a surveillance is failed within the delay period, then the equipment is inoperable, or the variable is outside the specified limits and the completion times of the required actions for the applicable LCO conditions begin immediately upon the failure of the surveillance.
Completion of the surveillance within the delay period allowed by this specification, or within the completion time of the actions, restores compliance with Surveillance Requirement 4.0.1.
Oyster Creek 4.0-3 Amendment No. 48-5, 240
6.20 MAJOR CHANGES TO RADIOACTIVE WASTE TREATMENT SYSTEMS DELETED 6.21 Technical Specifications (TS) Bases Control Program This program provides a means for processing changes to the Bases of these Technical Specifications.
- a. Changes to the Bases of the TS shall be made under appropriate administrative controls and reviews.
- b. Licensees may make changes to Bases without prior NRC approval provided the changes do not require either of the following:
- 1. A change in the TS incorporated in the license or
- 2. A change to the updated FSAR (UFSAR) or Bases that requires NRC approval pursuant to 10 CFR 50.59.
- c. The Bases Control Program shall contain provisions to ensure that the Bases are maintained consistent with the UFSAR.
- d. Proposed changes that meet the criteria of Specification 6.21.b.1 or 6.21.b.2 above shall be reviewed and approved by the NRC prior to implementation. Changes to the bases implemented without prior NRC approval shall be provided to the NRC on a frequency consistent with 10 CFR 50.71 (e)
OYSTER CREEK 6.21 Amendment No. 108,166 49 4 240