Text

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
	ML16175A292
Person / Time
Site:	Oconee, Mcguire, Catawba, Harris, Brunswick, Robinson, McGuire ; (DPR-023, DPR-038, DPR-047, DPR-062, DPR-071, NPF-009, NPF-017, NPF-035, NPF-052, NPF-063)
Issue date:	06/23/2016
From:	Elnitsky J; Duke Energy Carolinas
To:	; Document Control Desk, Office of Nuclear Reactor Regulation
References
	RA-16-0007
	Download: ML16175A292 (92)
	v • d • e

(~ DUKE ENERGY.

Serial: RA-16-0007 June 23, 2016 U.S. Nuclear Regulatory Commission A TIN: Document Control Desk Washington, DC 20555-0001 BRUNSWICK STEAM ELECTRIC PLANT, UNIT NOS. 1 AND 2 Jolm Elnitsky 526 South Church Street Charlotte, NC 28202 MaiDng Address:

Mail Code ECOlH I P.O. Box 1006 Charlotte, NC 28201* 1006 704-382*4371 10 CFR 50.90 DOCKET NOS. 50-325 AND 50-324 / RENEWED LICENSE NOS. DPR-71 AND DPR-62 CATAWBA NUCLEAR STATION, UNITS 1 AND 2 DOCKET NOS. 50-413 AND 50-414 I RENEWED LICENSE NOS. NPF-35 AND NPF-52 MCGUIRE NUCLEAR STATION, UNITS 1 AND 2 DOCKET NOS. 50-369 AND 50-370 I RENEWED LICENSE NOS. NPF-9 AND NPF-17 OCONEE NUCLEAR STATION, UNIT NOS. 1, 2 AND 3 DOCKET NOS. 50-269, 50-270 AND 50-287 I RENEWED LICENSE NOS. DPR-38, DPR-47 AND DPR-55 SHEARON HARRIS NUCLEAR POWER PLANT, UNIT NO. 1 DOCKET NO. 50-400 I RENEWED LICENSE NO. NPF-63 H. B. ROBINSON STEAM ELECTRIC PLANT, UNIT NO. 2 DOCKET NO. 50-261 I RENEWED LICENSE NO. DPR-23

SUBJECT:

APPLICATION TO REVISE TECHNICAL SPECIFICATIONS TO ADOPT TSTF-427, REVISION 2, "ALLOWANCE FOR NON TECHNICAL SPECIFICATION BARRIER DEGRADATION ON SUPPORTED SYSTEM OPERABILITY" USING THE CONSOLIDATED LINE ITEM IMPROVEMENT PROCESS

REFERENCE:

1. Federal Register dated October 3, 2006 (71 FR 58444), Notice of Availability of Model Application Concerning Technical Specification Improvement to Modify Requirements Regarding the Addition of LCO 3. 0. 9 on the Unavailability of Barriers Using the Consolidated Line Item Improvement Process Ladies and Gentlemen:

In accordance with the provisions of 10 CFR 50.90, Duke Energy Progress, Inc., and Duke Energy Carolinas, LLC, collectively referred to henceforth as "Duke Energy," is submitting a request for amendments to the Technical Specifications (TS) for Brunswick Steam Electric Plant

U.S. Nuclear Regulatory Commission RA-16-0007 Page2 (BSEP), Unit Nos. 1 and 2; Catawba Nuclear Station (CNS), Units 1 and 2; McGuire Nuclear Station (MNS), Units 1 and 2; Oconee Nuclear Station (ONS), Units 1, 2 and 3; Shearon Harris Nuclear Power Plant (HNP), Unit 1; and H. B. Robinson Steam Electric Plant (RNP), Unit No. 2.

The proposed amendments would modify TS requirements for unavailable barriers by adding Limiting Condition for Operation (LCO) 3.0.9 to the TS for BSEP, ONS, and RNP. The same changes are added as LCO 3.0.10 to the TS for CNS and MNS. For HNP, the proposed amendment would modify TS requirements for unavailable barriers by adding LCO 3.0.6 to the TS. The proposed changes are consistent with TSTF-427, Revision 2, "Allowance for Non Technical Specification Barrier Degradation on Supported System OPERABILITY," subject to stated variations. provides a description of the proposed change, the requested confirmation of applicability, and plant-specific verifications. Attachment 2 provides the existing TS pages marked up to show the proposed change. Attachment 3 provides revised (clean) TS pages. provides existing TS Bases pages marked up based on the proposed change (for information only). Attachment 5 provides a listing of the regulatory commitments.

Duke Energy requests approval of the proposed License Amendment by June 23, 2017, with the amendment being implemented within 120 days.

In accordance with 10 CFR 50.91, a copy of this application, with attachments, is being provided to the designated North Carolina and South Carolina officials.

If you should have any questions regarding this submittal, or require additional information, please contact Art Zaremba, Manager - Nuclear Fleet Licensing, at (980)373-2062.

I declare under penalty of perjury that the foregoing is true and correct. Executed on

'J}1 v e.. z.. r 1 Z-o I ~

Sincerely, Senior Vice President - Nuclear Engineering Nuclear Corporate Office NOE Attachments: 1. Description and Assessment

2. Proposed Technical Specification Changes

3. Retyped Technical Specification Pages

4. Proposed Technical Specification Bases Changes

5. Regulatory Commitments

U.S. Nuclear Regulatory Commission RA-16-0007 Page3 cc (with Attachments):

C. Haney, USNRC Region II-Regional Administrator A. Klein, USNRC - Chief, TS Branch M. P. Catts, USNRC Senior Resident Inspector - BSEP G. A. Hutto, USNRC Senior Resident Inspector - CNS J. Zeiler, USNRC Senior Resident Inspector - MNS J. D. Austin, USNRC Senior Resident Inspector - HNP K. Ellis, USNRC Senior Resident Inspector - RNP E. Crowe, USN RC Senior Resident Inspector - ONS A. L. Hon, NRR Project Manager - BSEP M. C. Barillas, NRR Project Manager - HNP D. Galvin, NRR Project Manager - RNP V. Sreenivas, NRR Project Manager - MNS M. Orenak, NRR Project Manager - CNS J. R. Hall, NRR Project Manager - ONS A. Gantt, Chief, Bureau of Radiological Health (SC)

A. Wilson, Attorney General (SC)

W. L. Cox, Ill, Section Chief, North Carolina Department of Health and Human Services, RP Section (NC)

S. E. Jenkins, Manager, Radioactive and Infectious Waste Management (SC)

Chairman, North Carolina Utilities Commission

U.S. Nuclear Regulatory Commission RA-16-0007 Page4 bee (with attachments):

Chris Nolan Art Zaremba Kate Nolan Leo Martin File: (Corporate)

Electronic Licensing Library (ELL)

Randy Gideon Lee Grzeck Mark Turkal Bill Murray (For BSEP Licensing/Nuclear Records Files)

John Caves Jon Gomes Donald Griffith Tanya Hamilton Bentley Jones Brian McCabe Sean O'Connor Ben Waldrep HNP NSRB Dennis Earp Paula Hamilton (For HNP Licensing/Nuclear Records Files)

Mike Glover Scott Connelly Justin Wild Heidi Walters (For RNP Licensing/Nuclear Records Files)

Kelvin Henderson Cecil Fletcher Sherry Andrews Tonya Lowery (For CNS Licensing/Nuclear Records Files)

Scott Batson Chris Wasik Samuel Adams Michele Shealy (For ONS Licensing/Nuclear Records Files)

Steven Capps Jeff Robertson Brian Richards Kay Crane/Jill Morton (For MNS Licensing/Nuclear Records Files)

North Carolina Municipal Power Agency No. 1 (NCMPA)

Electronic copy preferred: CatawbaContracts@electricities.org Piedmont Municipal Power Agency (PMPA)

Electronic copy preferred: Catawba_RegulatoryDox@pmpa.com North Carolina Electric Membership Corporation (NCEMC)

Electronic copy preferred: Catawba.Manager@ncemcs.com ONS Master File-ON03DM (File OS 801.01)

MNS Master File - MG02DM (file MC 801.01)

CNS Master File-CN04DM (File CN 801.01) to RA-16-0007 Page 1of4 DESCRIPTION AND ASSESSMENT

Subject:

Application to revise Technical Specifications to adopt TSTF-427, Revision 2, "Allowance for Non Technical Specification Barrier Degradation on Supported System OPERABILITY" using the consolidated line item improvement process

1.0 DESCRIPTION

2.0 ASSESSMENT

2.1 Applicability of Published Safety Evaluation 2.2 Optional Changes and Variations

3.0 REGULATORY ANALYSIS

3. 1 No Significant Hazards Consideration Determination 3.2 Verification and Commitments 4.0 ENVIRONMENTAL EVALUATION

5.0 REFERENCES

to RA-16-0007 Page 2of4

1.0 DESCRIPTION

The proposed amendment would modify technical specification (TS) requirements for unavailable barriers by adding a new LCO requirement in Section 3.0, "Limiting Condition for Operation (LCO) Applicability."

The changes are consistent with Nuclear Regulatory Commission (NRC) approved Industry/Technical Specification Task Force (TSTF) Improved Standard Technical Specifications Change Traveler TSTF-427, Revision 2 (Ref. 1 ). The availability of this TS improvement was published in the Federal Register on October 3, 2006 (71 FR 58444) as part of the consolidated line item improvement process (CLllP) (Ref. 2).

2.0 ASSESSMENT

2.1 Applicability of Published Safety Evaluation Duke Energy has reviewed the safety evaluation dated October 3, 2006 (71 FR 58444) as part of the CLllP. This review included a review of the NRC staff's evaluation, as well as the supporting information provided to support TSTF-427. Duke Energy has concluded that the justifications presented in the TSTF proposal and the safety evaluation prepared by the NRC staff are applicable to Brunswick Steam Electric Plant (BSEP), Units Nos. 1 and 2, Catawba Nuclear Station (CNS), Units 1 and 2, McGuire Nuclear Station (MNS), Units 1 and 2, Oconee Nuclear Station (ONS), Units 1, 2 and 3, Shearon Harris Nuclear Power Plant (HNP), Unit No. 1, and H. B. Robinson Steam Electric Plant (RNP), Unit No. 2, and justify this amendment for the incorporation of the changes to the plants' technical specifications.

On November 27, 2012, the NRC published a Federal Register Notice stating that Regulatory Guide (RG) 1.182 has been withdrawn and the subject matter has been incorporated into Revision 3 of RG 1.160, "Monitoring the Effectiveness of Maintenance at Nuclear Power Plants" (77 FR 70846) (Ref. 3). RG 1.160 (Ref. 4) endorses Revision 4A of Nuclear Utility Management and Resources Council (NUMARC) 93-01, "Industry Guideline for Monitoring the Effectiveness of Maintenance at Nuclear Power Plants," dated April 2011 (Ref. 5). TSTF-427 and the proposed Bases, the model application and commitments, the model Safety Evaluation, and the implementation guidance reference RG 1. 182, "Assessing and Managing Risk Before Maintenance Activities at Nuclear Power Plants," which endorses the February 2000 version of NUMARC 93-01, "Industry Guideline for Monitoring the Effectiveness of Maintenance at Nuclear Power Plants." References and commitments to RG 1. 182 in these documents are assumed to refer to RG 1.160 and Revision 4A of NUMARC 93-01 instead of RG 1.182. References to RG 1.182 in the Technical Specification Bases and model application have been revised to refer to RG 1.160.

2.2 Optional Changes and Variations Duke Energy is proposing the following variations or deviations from the TS changes described in either TSTF-427 Revision 2 or the NRC staff's model safety evaluation dated October 3, 2006 (71 FR 58444):

The current TS for CNS and MNS already include a LCO 3.0.9. As a result, the new LCO in TSTF-427 is incorporated as LCO 3.0.10.

to RA-16-0007 Page 3of4 The current TS for HNP do not contain a LCO 3.0.6. As a result, the new LCO in TSTF-427 is incorporated as LCO 3.0.6.

3.0 REGULATORY ANALYSIS

3.1 No Significant Hazards Consideration Determination Duke Energy has reviewed the proposed no significant hazards consideration determination (NSHCD) published in the Federal Register as part of the CLllP. Duke Energy has concluded that the proposed NSHCD presented in the Federal Register notice is applicable to Brunswick Steam Electric Plant (BSEP), Units Nos. 1 and 2, Catawba Nuclear Station (CNS), Units 1 and 2, McGuire Nuclear Station, Units 1 and 2 (MNS), Oconee Nuclear Station (ONS), Units 1, 2 and 3, Shearon Harris Nuclear Power Plant (HNP), Unit No. 1, and H. B. Robinson Steam Electric Plant (RNP), Unit No. 2 and is hereby incorporated by reference to satisfy the requirements of 10 CFR 50.91(a).

3.2 Verification and Commitments As discussed in the notice of availability published in the Federal Register on October 3, 2006 (71 FR 58444) for this TS improvement, plant-specific verifications were performed as follows:

1. Duke Energy commits to the guidance of NUMARC 93-01 Section 11, Revision 4A, which provides guidance and details on the assessment and management of risk during maintenance.

2. Duke Energy will revise procedures to ensure that the risk assessment and management process described in NEI 04-08 is used whenever a barrier is considered unavailable and the requirements of the new LCO (LCO 3.0.9 for BSEP, ONS, and RNP; LCO 3.0.1 O for CNS and MNS; LCO 3.0.6 for HNP) are to be applied, in accordance with an overall Configuration Risk Management Program (CRMP), to ensure that potentially risk significant configurations resulting from maintenance and other operational activities are identified and avoided.

4.0 ENVIRONMENTAL EVALUATION Duke Energy has reviewed the environmental evaluation included in the model safety evaluation dated October 3, 2006 (71 FR 58444) as part of the CLllP. Duke Energy has concluded that the staff's findings presented in that evaluation are applicable to Brunswick Steam Electric Plant (BSEP), Units Nos. 1 and 2, Catawba Nuclear Station (CNS), Units 1 and 2, McGuire Nuclear Station (MNS), Units 1 and 2, Oconee Nuclear Station (ONS), Units 1, 2 and 3, Shearon Harris Nuclear Power Plant (HNP), Unit No. 1, and H. B. Robinson Steam Electric Plant (RNP), Unit No. 2 and the evaluation is hereby incorporated by reference for this application.

to RA-16-0007 Page 4of4

5.0 REFERENCES

1. Technical Specification Task Force Improved Standard Technical Specifications Change Traveler, TSTF-427, "Allowance for Non Technical Specification Barrier Degradation on Supported System OPERABILITY," Revision 2.

2. Federal Register Notice (71 FR 58444), dated October 3, 2006, "Notice of Availability of Model Application Concerning Technical Specification Improvement To Modify Requirements Regarding the Addition of LCO 3. 0. 9 on the Unavailability of Barriers Using the Consolidated Line Item Improvement Process."

3. Federal Register Notice (77 FR 70846), dated November 27, 2012, Notice of Withdrawal of Regulatory Guide 1.182, "Assessing and Managing Risk Before Maintenance Activities at Nuclear Power Plants."

4. Regulatory Guide, 1.160, "Monitoring the Effectiveness of Maintenance at Nuclear Power Plants," U.S. Nuclear Regulatory Commission, Washington, DC (Accession No. ML113610098).

5. NU MARC 93-01, "Industry Guideline for Monitoring the Effectiveness of Maintenance at Nuclear Power Plant," Revision 4A, Nuclear Energy Institute, Washington, DC, April 2011 (Accession No. ML11116A198).

to RA-16-0007 PROPOSED TECHNICAL SPECIFICATION CHANGES to RA-16-0007

\\.

(

LCO Applicability 3.0 3.0 LIMITING CONDITION FOR OPERATION (LCO) APPLICABILITY LCO 3.0.1 LCO 3.0.2 LCO 3.0.3 LCO 3.0.4 Brunswick Unit 1 LCOs shall be met during the MODES or other specified conditions in the Applicability, except as provided in LCO 3.0.2, Cl 3.0.7, end LC0 1

3.0.\\

I

, and LCO 3.0.9 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 LC03.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.

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

a.

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

b.

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

c.

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

Exceptions to this Specification are stated in the individual Specifications.

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

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

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 l 3.0-1 Amendment No. *1 to RA-16-0007 LCO Applicability 3.0 '

3.0 LCO APPLICABILITY (continued)

LCO 3.0.7 LCO 3.0.8 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.

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 0.02 hours 1.190476e-4 weeks 2.7396e-5 months ; or

b.

The snubbers not able to perform their associated support funclion(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 0.00333 hours 1.984127e-5 weeks 4.566e-6 months .

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.

~INSERT - Brunswick LCO 3.0.9 I Brunswick Unit 1 3.0-3 Amendment No. x.44 to RA-16-0007 INSERT - Brunswick LCO 3.0.9 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 functlon(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 0.00667 hours 3.968254e-5 weeks 9.132e-6 months 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.

to RA-16-0007

." \\.

LCO Applicab'lity 3.0 3.0 LIMITING CONDITION FOR OPERATION (LCO) APPLICABILITY LCO 3.0.1 LCO 3.0.2 LCO 3.0.3 LCO 3.0.4 Brunswick Unit 2 LCOs shall be met during the MODES or other specified conditions in the Applicability, except as provided in LCO 3.0.2, LCI 3.0.7, EtAEf LCOl 3 0.8~

, and LCO 3.0.9 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.

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

a.

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

b.

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

c.

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

Exceptions to this Specification are stated in the individual Specifications.

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

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

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; fcon ouedl 3.0-1 Amendment No. 269 I to RA-16-0007 LCO Applicability 3.0 3.0 LCO APPLICABILITY (continued)

LCO 3.0.7 LCO 3.0.8 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.

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 or 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 0.02 hours 1.190476e-4 weeks 2.7396e-5 months ; 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 0.00333 hours 1.984127e-5 weeks 4.566e-6 months .

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.

~INSERT - Brunswick LCO 3.0.9 I Brunswick Unit 2 3.0-3 Amendment No. 269 I to RA-16-0007 INSERT - Brunswick LCO 3.0.9 LCO 3.0.9 When one or more required barriers are unable to perform their related support funclion(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 functlon(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 0.00667 hours 3.968254e-5 weeks 9.132e-6 months 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.

to RA-16-0007 LCO Applicability 3.0 3.0 LIMITING CONDITION FOR OPERATION (LCO) APPLICABILITY LCO 3.0.1 LCO 3.0.2 LCO 3.0.3 LCOs shall be met during the MODES or other specified conditions in the Applicability, except as provided in LCO 3.0.2, 3.0.7, aAEl 3.0.8.

, and 3.0.10 Upon discovery of a failure to meet an L 0, the Required Actions of the associated Conditions shall be met, except as provided in LCO 3.0.5 and LC03.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 Actlon(s) is not required unless otherwise stated.

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

a.

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

b.

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

c.

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

Exceptions to this Specification are stated in the individual Specifications.

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

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

(continued)

Catawba Units 1 and 2 3.0*1 Amendment Nos. ~. '81 to RA-16-0007 LCO Applicability 3.0 3.0 LCO APPLICABILITY (continued)

LCO 3.0.9 LCOs including the associated ACTIONS shall apply to each unit individually unless otherwise indicated as follows:

a.

Whenever the LCO refers to systems or components which are shared by both units, the ACTIONS will apply to both units simultaneously;

b.

Whenever the LCO applies to only one unit, this will be identified in the Applicability section of the Specification; and

c.

Whenever certain portions of a Specification contain operating parameters, setpoints etc., which are different for each unit, this will be identified in parentheses or footnotes. (For example, *... flow rate of 54,000 cfm (Unit 1) or 43,000 cfm (Unit 2)...").

~ INSERT - Catawba LCO 3.0.10 Catawba Units 1 and 2 3.0-4 Amendment Nos. ~. 2M I to RA-16-0007 INSERT - Catawba LCO 3.0.10 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 functlon(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 0.00667 hours 3.968254e-5 weeks 9.132e-6 months 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.

to RA-16-0007 LCO Applicability 3.0 3.0 LIMITING CONDITION FOR OPERATION (LCO) APPLICABILITY LCO 3.0.1 LCO 3.0.2 LCO 3.0.3 LCOs shall be met during the MODES or other specified conditions in the Applicability, except as provided in LCO 3.0.2, 3.0.7, ~

3.0.8.

Upon discovery of a failure to meet an

, t e equ1red Actions of the associated Conditions shall be met, except as provided in LCO 3.0.5 and LC03.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.

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

a.

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

b.

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

c.

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

Exceptions to this Specification are stated in the individual Specifications.

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

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

McGuire Units 1 and 2 3.0-1 Amendment Nos. m., ~

to RA-16-0007 3.0 LCO APPLICABILITY (continued)

LCO 3.0.7 LCO 3.0.8 LCO 3.0.9 Test Exception LCOs 3.1.8 and 3.4.17 allow specified Technical Specification (TS) requirements to be changed to permit performance of special tests and operations. Unless othelWise specified, all other TS requirements remain unchanged. Compliance with Test Exception LCOs is optional. When a Test Exception LCO is desired to be met but is not met, the ACTIONS of the Test Exception LCO shall be met. When a Test 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 Specttications.

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 thi_s 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 0.02 hours 1.190476e-4 weeks 2.7396e-5 months ; 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 0.00333 hours 1.984127e-5 weeks 4.566e-6 months .

e,t 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.

LCOs including the associated ACTIONS shall apply to each unit individually unless otherwise indicated as follows:

a.

Whenever the LCO refers to systems or components which are shared by both units, the ACTIONS will apply to both units simultaneously;

b.

Whenever the LCO applies to only one unit, this will be identified n the Applicability section of the Specification; and

c.

Whenever certain portions of a Specification contain operating parameters. setpoints etc., which are different for each unit, this will be identified in parentheses or footnotes. (for example, *...flow rate of 54,000 cfm (Unit 1) or 43,000 cfm (Unit 2)... ").

~ INSERT - McGuire LCO 3.0.10 (continued)

McGuire Units 1 and 2 3.0-3 Amendment Nos. 238-, Z26 to RA-16-0007 INSERT - McGuire LCO 3.0.10 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 functlon(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 functlon(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 0.00667 hours 3.968254e-5 weeks 9.132e-6 months 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.

to RA-16-0007 LCO Applicability 3.0 3.0 LIMITING CONDITION FOR OPERATION {LCO) APPLICABILITY LCO 3.0.1 LCO 3.0.2 LCO 3.0.3 LC03.0.4 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, eAEf LC0.3.0.81'-I I. and LCO 3.0.9~

Upon discovery of a failure to meet an LCO, the Required Actions of the associated Conditions shall be met, except as provided ln LCO 3.0.5 and LC03.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.

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

a.

MODE 3 within 12 hours1.388889e-4 days 0.00333 hours 1.984127e-5 weeks 4.566e-6 months ;

b.

MODE 4 within 18 hours2.083333e-4 days 0.005 hours 2.97619e-5 weeks 6.849e-6 months ; and

c.

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

Exceptions to this Specification are stated in the Individual Specifications.

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

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

When an LCO is not met, entry into a MODE or other specified condition in the ApplicabUity shall not be made except 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.

This Specification shall not prel(ent chang~

Jn MQDES or othecspecified conditions in the Applicability that are required to comply with ACTIONS or that are part of a shutdown of the unit.

OCONEE UNITS t. 2, & 3 3.0-t Amendment Nos. 368, 358, 357 to RA-16-0007 LCO Appllcablllty 3.0 3.0 LCO APPLICABILITY LC03.0.8 (continued) and managed, and:

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

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

At the end of the specified period the required snubbers must be able to pertorm their associated support function(s), or the affected supported system LCO(s) shall be declared not met INSERT - Oconee LCO 3.0.9 OCONEE UNITS 1, 2, & 3 3.0-3 Amendment Nos. 366, 356, 357 to RA-16-0007 INSERT - Oconee LCO 3.0.9 LCO 3.0.9 When one or more required barriers are unable to perform their related support funclion(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 functlon(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 0.00667 hours 3.968254e-5 weeks 9.132e-6 months 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.

to RA-16-0007

\\.._../.

3/4.0 APPLICABILITY LIMITING CONDITION FOR OPERATION 3.0.l Compliance with the limiting Conditions for Operation contained in the succeeding specifications-is required during the OPERATIONAL HODES or other conditions specified therein; except that upon failure to meet the limiting Conditions for Operation, the ~ssociated ACTION requirements shall be met.

3.0.2 Noncompliance with a specfffcatfon shall exist when the requirements of the Limiting Condition for Operation and associated ACTION requirements are not met within the specified time intervals. If the Limiting Condition for Operation is restored prior to expiration of the specified time intervals, completion of the ACTION requirements is not required unless otherwise noted in the ACTION statement.

3.0.3 When a Lfmftfng Condition for Operation is not met, except as provided in the associated ACTION requirements, within l hour action shall be initiated to place the unit fn a HOOE in which the specification does not apply by placing it, as applicable, in:

a.

At least HOT STANDBY within the next 6 hours6.944444e-5 days 0.00167 hours 9.920635e-6 weeks 2.283e-6 months ,

b.

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

c.

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

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 Lfmftfng Condition for Operation. Exceptions to these requirements are stated in the individual specifications.

This specification is not applicable fn HOOE 5 or 6.

3.0.4 Entry into an OPERATIONAL HOOE or.other specified condition shall not be made when the conditions for the limiting Conditions for Operation are not met and the associated ACTION requires a shutdown if they are not met within a specified time interval. Entry into an OPERATIONAL MODE or specified condition may be made in accordance with ACTION requirements when conformance to them permits continued operation of the facility for an unlimited period of time. This provision shall not prevent passage through or to OPERATIONAL HODES as required to comply with ACTION requirements or that are part of a shutdown of the unit. Exceptions ~o these requirements are stated in the individual specf ffcatfons.

3.0.S Equipment removed from service or declared inoperable to comply with ACTIONS may be returned to service under admtnfstratfve control solely to perform testing required to demonstrate its OPERABJLJTY *or the OPERABILITY of other equipment. This ts an exception to 3.0.l above for the system returned to service under administrative control to perform the testing required to demonstrate OPERABILITY.

INSERT - Harris LCO 3.0.6 SHEARON HARRIS

UNIT I 3/4 O*I Amendment No. 84-

~ -

to RA-16-0007 INSERT - Hauls LCO 3.0,6 3.0.6 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 functlon(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 functlon(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 0.00667 hours 3.968254e-5 weeks 9.132e-6 months 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.

to RA-16-0007 LCO Appllcability 3.0 3.0 LIMITING CONDITION FOR OPERATION {LCO) APPLICABILITY LCO 3.0.1 LCOs shaU be met during the MODES or other specified conditions In the Applicability, except as provided In LCO 3.0.2, 3.0.7, aRd 3.0.8!\\-

11. and LCO 3.0.91-I - -----

LCO 3.0.2 LCO 3.0.3 LCO 3.0.4 HBRSEP Unit No. 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 Tirne(s), completion of the Required Action{s) is not required unless otherwise stated.

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. AcUon shall be Initiated within 1 hour1.157407e-5 days 2.777778e-4 hours 1.653439e-6 weeks 3.805e-7 months to place the unit, as applicable, in:

a.

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

b.

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

c.

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

Exceptions to this Specification are stated in the individual Specifications.

Where corrective measures are completed that permit operation In accordance with the LCO or ACTIONS, completion of the acUons required by LCO 3.0.3 ls not required.

LCO 3.0.3 ls only appl!cable In MODES 1, 2, 3, and 4.

Whan an LCO Is not met, entry into a MODE or other specified condition in the ApplicabUlty shall only be made:

(continued) 3.0-1 Amendment No. N2 to RA-16-0007 LCO Applicablfity 3.0 3.0 LCO APPLICABILITY LC03.0.6 (continued)

LC0 3.0.7 LC03.0.8 HBRSEP Unit No. 2 the loss or safety function exists are required to be entered.

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

Test Exception LCO 3.1.8 allows specified Technical Specification (TS) requirements to be changed lo permit performance of special tests and operations. Unless olhelWlse specified, all other TS requirements remain unchanged. Compliance with Test Exception LCOs Is optional. When a Test Exception LCO is desired to be met but is not met, the ACTIONS of the Test Exception LCO shall be met. When a Test 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.

When one or more required snubbers are unable to perform their associated support functlon(s), any affected supported LCO(s) are not required to be declared not met solely ror this reason If risk Is assessed and managed, and:

a.

the snubbers not able to perform their associated support function(&) 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 with n 72 hours8.333333e-4 days 0.02 hours 1.190476e-4 weeks 2.7396e-5 months ; or

b.

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

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

INSERT - HB Robinson LCO 3.0.9 3.0-3 Amendment No. 2l2 to RA-16-0007 INSERT - HB Robinson LCO 3.0.9 LCO 3.0.9 When one or more required barriers are unable to perform their related support runction(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 functlon(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 0.00667 hours 3.968254e-5 weeks 9.132e-6 months 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.

RETYPED TECHNICAL SPECIFICATION PAGES

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

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

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

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

a.

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

b.

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

c.

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

Exceptions to this Specification are stated in the individual Specifications.

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

LCO 3.0.3 is only applicable in MODES 1, 2, 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 Brunswick Unit 1 3.0-3 Amendment No. 241 3.0 LCO APPLICABILITY (continued)

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 0.02 hours 1.190476e-4 weeks 2.7396e-5 months ; 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 0.00333 hours 1.984127e-5 weeks 4.566e-6 months .

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

LCO Applicability 3.0 Brunswick Unit 1 3.0-4 Amendment No. 241 3.0 LCO APPLICABILITY LCO 3.0.9 train or subsystem supported system provided at least one train or (continued) 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 0.00667 hours 3.968254e-5 weeks 9.132e-6 months 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 Brunswick Unit 1 3.0-5 Amendment No. 224 3.0 SURVEILLANCE REQUIREMENT (SR) APPLICABILITY SR 3.0.1 SRs shall be met during the MODES or other specified conditions in the Applicability for individual LCOs, unless otherwise stated in the SR.

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

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

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

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

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

Exceptions to this Specification are stated in the individual Specifications.

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

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

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

(continued)

SR Applicability 3.0 Brunswick Unit 1 3.0-6 Amendment No. 233 3.0 SR APPLICABILITY (continued)

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.

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

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

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

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

a.

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

b.

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

c.

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

Exceptions to this Specification are stated in the individual Specifications.

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

LCO 3.0.3 is only applicable in MODES 1, 2, 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 Brunswick Unit 2 3.0-3 Amendment No. 269 3.0 LCO APPLICABILITY (continued)

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 0.02 hours 1.190476e-4 weeks 2.7396e-5 months ; 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 0.00333 hours 1.984127e-5 weeks 4.566e-6 months .

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

LCO Applicability 3.0 Brunswick Unit 2 3.0-4 Amendment No. 269 3.0 LCO APPLICABILITY LCO 3.0.9 train or subsystem supported system provided at least one train or (continued) 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 0.00667 hours 3.968254e-5 weeks 9.132e-6 months 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 Brunswick Unit 2 3.0-5 Amendment No. 249 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.