ML032260661

Technical Specifications (TS) Change 410 - Mode Change Limitations Using the Consolidated Line Item Improvement Process (CLIIP)

ML032260661
Person / Time
Site:	Browns Ferry
Issue date:	08/07/2003
From:	Abney T Tennessee Valley Authority
To:	Document Control Desk, Office of Nuclear Reactor Regulation
References
TVA-BFN-TS-410
Download: ML032260661 (49)

Text

R08030807627 Tennessee Valley Authority. Post Office Box 2000. Decatur. Alabama 35609-2000 August 7, 2003 TVA-BFN-TS-4 10 10 CFR 50.90 U.S. Nuclear Regulatory Commission ATTN: Document Control Desk Mail Stop:

OWEN P1-35 Washington, D.C. 20555-0001 Gentlemen:

In the Matter of

)

Docket Nos. 50-259 Tennessee Valley Authority 50-260 50-296 BROWNS FERRY NUCLEAR PLANT (BFN) -

UNITS 1, 2, AND 3 -

TECHNICAL SPECIFICATIONS (TS) CHANGE 410 -

MODE CHANGE LIMITATIONS USING THE CONSOLIDATED LINE ITEM IMPROVEMENT PROCESS (CLIIP)

Pursuant to 10 CFR 50.90, the Tennessee Valley Authority (TVA) is submitting a request for a TS change (TS-410) to licenses DPR-33, DPR-52, and DPR-68 for BEN Units 1, 2, and 3, respectively. The proposed amendment would modify TS requirements for mode change limitations in Limiting Condition for Operation 3.0.4 and Surveillance Requirement 3.0.4 to adopL the provisions of Industry/Technical Specification Task Force (TSTF) change TSTF-359, "Increase Flexibility in Mode Restraints." provides a description of the proposed change including a listing of the affected TS with a brief description of the change, the confirmation of applicability, and the plant-specific verification. Enclosure 2 provides the existing Unit 2 TS pages marked-up to show the proposed changes.

Identical changes are being requested for BEN Units 1 and 3 TS. provides the existing Unit 2 TS Bases pages marked-up to show the proposed changes.

Identical changes to the Units 1 and 3 TS Bases are proposed.

U.S. Nuclear Regulatory Commission Page 2 August 7, 2003 TVA is asking that this TS change be approved by December 1, 2003, and that the implementation of the revised TS be made within 60 days of NRC approval.

The enclosed changes to the TS Bases will be implemented concurrently with the TS change in accordance with the TS Bases Control Program.

TVA has determined that there are no significant hazards considerations associated with the proposed change and that the TS change qualifies for a categorical exclusion from environmental review pursuant to the provisions of 10 CFR 51.22(c) (9).

Additionally, in accordance with 10 CFR 50.91(b) (1), TVA is sending a copy of this letter and attachments to the Alabama State Department of Public Health.

There are no regulatory commitments associated with this submittal.

This letter is being sent in accordance with NRC Regulatory Issue Summary 2001-05, Guidance on Submitting Documents to the NRC by Electronic Information Exchange or on CD-ROM.

If you have any questions about this TS change, please contact me at (256)729-2636.

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

Executed on August 7, 2003.

S'ncerel T.

E. Abie Manager rc--e-n--s i an ndustry Aff irs Enc o~e

1. Descrip Assessment

2. Proposed Technical Specifications Changes (mark-up)

3. Changes to Technical Specifications Bases Pages (mark-up) cc: (Enclosures)

State Health Officer Alabama State Department of Public Health RSA Tower -

Administration Suite 1552 P. O. Box 303017 Montgomery, Alabama 36130-3017

U.S. Nuclear Regulatory Commission Page 3 August 7, 2003 DTL BCM: BAB Enclosures cc (w/o Enclosures):

A. S. Bhatnagar, PAB lE-BFN M. J. Burzynski, BR 4X-C J. E. Maddox, LP 6A-C T. J. Niessen, Jr., PAB lA-BFN D. C. Olcsvary, LP 6A-C J. R. Rupert, LP 6A-C K. W. Singer, LP 6A-C M. D. Skaggs, POB 2C-BFN E. J. Vigluicci, ET 11A-K NSRB Support, LP 51-C EDMS-K (with Enclosures) s:lic/submit/TechSpec/TS-410 Mode Changes Browns Ferry Nuclear Plant (BFN)

Units 1, 2, and 3 Technical Specifications (TS) Change 410 Mode Change Limitations Using the Consolidated Line Item Improvement Process (CLIIP)

Description and Assessment

1.0 DESCRIPTION

The proposed amendment would modify Technical Specifications (TS) requirements for mode change limitations in Limiting Condition for Operation (LCO) 3.0.4 and Surveillance Requirement (SR) 3.0.4.

The changes are consistent with Nuclear Regulatory Commission (NRC) approved Industry/Technical Specification Task Force (TSTF) Standard TS (STS) change TSTF-359 Revision 8, as modified by the notice in the Federal Register published on April 4, 2003.

That Federal Register Notice (FRN) announced the availability of this TS improvement through the CLIIP.

TSTF-359 Revision 8 was subsequently revised to incorporate the modifications discussed in the April 4, 2003, FRN and other minor changes, and was submitted to NRC on April 28, 2003, as TSTF-359 Revision 9.

A description of the proposed TS/TS Bases changes that directly adopt TSTF-359 Revision 9 with no variations is provided directly below. A description of the TS/TS Bases changes where variances are required to adopt TSTF-359 Revision 9, due to differences between BFN TS and STS, is provided in Section 2.2 of this enclosure.

A. LCO 3.0.4 is revised to allow entry into a MODE or other specified condition in the Applicability while relying on the associated ACTIONS, provided that there is a risk assessment performed which lustifies the use of LCO 3.0.4, the ACTIONS to be entered permit continued operation in the MODE or other specified condition in the Applicability for an unlimited period of time, or an NRC approved allowance is provided in the Specification to be entered.

The associated Bases are likewise being modified in accordance with TSTF-359 Revision 9.

The

bracketed provisions in the Revision 9 Bases mark-ups have been removed for consistency with NUREG-1433 Revision 2, Standard Technical Specifications, "General Electric Plants, BWR/4."

B. SR 3.0.4 is revised to reflect the concepts of the change to LCO 3.0.4.

The applicability of LCO 3.0.4 and SR 3.0.4 is expanded to include transition into all MODES or other specified conditions in the Applicability, except when required to comply with ACTIONS or that are part of a shutdown of the unit. The associated Bases are likewise being modified in accordance with TSTF-359 Revision 9. The bracketed provisions in the Revision 9 Bases mark-ups have been removed for consistency with NUREG-1433 Revision 2, Standard Technical Specifications, "General Electric Plants, BWR/4."

C. In LCO 3.5.1, Emergency Core Cooling System -

Operating, an ACTIONS Note is added to indicate that the new LCO 3.0.4.b provision is not applicable to the High Pressure Coolant Injection system.

D. In LCO 3.5.3, Reactor Core Isolation Cooling, an ACTIONS Note is added to indicate that the new LCO 3.0.4.b provision is not applicable.

E. In LCO 3.8.1, Alternating Current -

Operating, an ACTIONS Note is added to indicate that the new LCO 3.0.4.b provision is not applicable to diesel generators (DGs). provides the existing Unit 2 TS pages marked-up to show the proposed change. Identical changes are being requested for BFN Units 1 and 3 TS. provides the existing Unit 2 TS Bases pages marked-up to show the proposed change.

Identical changes to the Units 1 and 3 TS Bases are proposed. LCO 3.0.4 and SR 3.0.4 are identical for all 3 BFN units.

2.0 ASSESSMENT

2.1 Applicability of Published Safety Evaluation The Tennessee Valley Authority (TVA) has reviewed the NRC safety evaluation dated March 28, 2003, as part of the CLIIP.

This review included a review of the NRC staff's evaluation, as well as the supporting information provided to support TSTF-359 Revision 8 and included the consideration of the updates made in TSTF-359 Revision 9.

TVA has concluded that the justifications presented in the TSTF proposal and the safety evaluation prepared by the NRC E1-2

staff are applicable to BFN Units 1, 2, and 3, and justify this amendment for the incorporation of the changes to the BFN TS.

2.2 Optional Changes and Variations TVA is not proposing any variations or deviations from the model TS/TS Bases changes for LCO 3.0.4 and SR 3.0.4 described in the modified TSTF-359 Revision 8 (as updated by Revision 9) and the NRC staff's model safety evaluation dated March 28, 2003.

However, due to minor differences between BFN TS/TS Bases and the model STS in NUREG-1433 Revision 2, Standard Technical Specifications, "General Electric Plants, BWR/4",

in several cases small variances from the TSTF mark-up changes are necessary. These variations are discussed below and do not affect the adoption or application of TSTF-359 Revision 9.

All other TS Sections are modified without variance as described in Section 1.0 above.

There are several minor technical differences among the 3 units for the affected LCO sections (setpoints, surveillance frequency, etc.).

These technical differences do not affect the application of TSTF-359 Revision 9, so the same changes shown in Unit 2 TS/TS Bases mark-ups apply identically to the Units 1 and 3 TS/TS Bases.

A. BFN LCO 3.3.3.1, Post Accident Monitoring (PAM)

Instrumentation, is revised to delete Note 1 from the ACTIONS, which is the LCO 3.0.4 non-applicability Note, in accordance with the TSTF. BFN TS currently have a third Note under the LCO ACTIONS, whereas STS has only two notes. The retention of the third note (renumbered as Note 2) shows in Enclosures 2 and 3 as a deviation from the TSTF-359 Revision 9 mark-ups.

B. In the TSTF mark-ups, STS 3.3.3.2, Remote Shutdown System, Note 1 from the ACTIONS, which is the LCO 3.0.4 non-applicability Note, is deleted. The equivalent BFN TS is titled as TS 3.3.3.2, Backup Control System, and the same change is made.

C. In the TSTF mark-ups, STS 3.3.6.3, Low-Low Set (LLS)

Instrumentation, is modified. BFN TS do not have an equivalent section, so no changes are needed.

D. In the TSTF mark-ups, in STS 3.4.6, Reactor Coolant System (RCS) Leakage Detection Instrumentation, Note 1 from the ACTIONS, which is the LCO 3.0.4 non-applicability Note, is deleted.

In BFN TS, the E1-3

equivalent TS is TS 3.4.5 (same title) and the LCO 3.0.4 non-applicability Note, which is being deleted, is located in REQUIRED ACTION B rather than the ACTIONS.

E.

In the TSTF mark-ups, STS 3.4.7, Reactor Coolant System Specific Activity, a Note permitting the use of the new LCO 3.0.4.c provision is substituted for the existing LCO 3.0.4 non-applicability note in REQUIRED ACTION A.

In BFN TS, the equivalent TS is TS 3.4.6 (same title) and the same change is made.

F. In the TSTF mark-ups, STS 3.4.8, Residual Heat Removal (RHR) System -

Hot Shutdown, Note 1 from the ACTIONS, which is the LCO 3.0.4 non-applicability Note, is deleted. In BFN TS, the equivalent TS is TS 3.4.7 (same title) and the same change is made.

G. In the TSTF mark-ups, STS 3.6.3.1, Primary Containment Hydrogen Recombiners, is modified. BFN TS do not have an equivalent section, so no changes are needed.

H.

In the TSTF mark-ups, STS 3.6.3.2, Drywell Cooling System Fans, is modified. BFN TS do not have an equivalent section, so no changes are needed.

I.

In the TSTF mark-ups, STS 3.6.3.4, Containment Atmospheric Dilution (CAD) System, the Note in REQUIRED ACTION A.l, which is the LCO 3.0.4 non-applicability Note, is deleted. In BFN TS, the equivalent TS is TS 3.6.3.1 (same title) and the same change is being made.

J. In the TSTF mark-ups, the LCO 3.0.4 non-applicability Note is being deleted from Required Action A for STS 3.7.3, Diesel Generator (DG) [lB] Standby Service Water (SSW) System. BFN TS do not have the direct equivalent of STS 3.7.3. A similar function (DG cooling) is provided by the Emergency Equipment Cooling Water (EECW)

System, which is addressed in BFN TS 3.7.2, EECW System and Ultimate Heat Sink. TS 3.7.2, however, does not have an LCO 3.0.4 non-applicability provision, so no changes are needed for consistency with TSTF-359.

3.0 REGULATORY ANALYSIS

3.1 No Significant Hazards Consideration Determination TVA has reviewed the proposed no significant hazards consideration determination (NSHCD) published in the Federal Register as part of the CLIIP.

TVA has concluded that the proposed NSHCD presented in the Federal Register notice is E1-4

applicable to Browns Ferry Nuclear Plant 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 April 4, 2003, for this TS improvement, plant-specific verifications were performed as follows:

TVA has established TS Bases for LCO 3.0.4 and SR 3.0.4, which state that use of the TS mode change limitation flexibility established by LCO 3.0.4 and SR 3.0.4 is not to be interpreted as endorsing the failure to exercise the good practice of restoring systems or components to operable status before entering an associated mode or other specified condition in the TS Applicability.

The modification also includes changes to the Bases for LCO 3.0.4 and SR 3.0.4 that provide details on how to implement the new requirements. The Bases changes provide guidance for changing Modes or other specified conditions in the Applicability when an LCO is not met. The Bases changes describe in detail how: LCO 3.0.4.a allows entry into a MODE or other specified condition in the Applicability with the LCO not met 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; LCO 3.0.4.b allows entry into a MODE or other specified condition in the Applicability with the LCO not met after performance of a risk assessment addressing inoperable systems and components, consideration of the results, determination of the acceptability of entering the MODE or other specified condition in the Applicability, and establishment of risk management actions, if appropriate; and LCO 3.0.4.c allows entry into a MODE or other specified condition in the Applicability with the LCO not met based on a Note in the Specification, which is typically applied to Specifications which describe values and parameters (e.g., Reactor Coolant System Activity), though it may be applied to other Specifications based on NRC plant-specific approval. The Bases also state that any 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 Risks Before Maintenance Activities at Nuclear Power Plants," and that the results of the risk assessment shall be considered in determining the acceptability of entering the MODE or other specified condition in the Applicability, and any corresponding risk management actions. Upon entry into a E1-5

MODE or other specified condition in the Applicability with the LCO not met, LCO 3.0.1 and LCO 3.0.2 require entry into the applicable Conditions and Required Actions until the Condition is resolved, until the LCO is met, or until the unit is not within the Applicability of the TS. The Bases also state that SR 3.0.4 does not restrict changing MODES or other specified conditions of the Applicability when a Surveillance has not been performed within the specified Frequency, provided the requirement to declare the LCO not met has been delayed in accordance with SR 3.0.3.

The revised TS Bases will be implemented concurrently with the TS change in accordance with the TS Bases Control Program as described in TS 5.5.10.

4.0 ENVIRONMENTAL EVALUATION TVA has reviewed the environmental evaluation included in the model safety evaluation dated March 28, 2003, as part of the CLIIP.

TVA has concluded that the staff's findings presented in that evaluation are applicable to BFN and the evaluation is hereby incorporated by reference for this application.

E1-6 Browns Ferry Nuclear Plant (BFN)

Units 1, 2, and 3 Technical Specifications (TS) Change 410 Mode Change Limitations Using the Consolidated Line Item Improvement Process (CLIIP)

Proposed Technical Specifications Changes (mark-up)

LCO Applicability

.3.0 3.0 LCO APPLICABILITY (continued)

LCO 3.0.4 When an LCO not met, entry into a MODE or other specifi condition i e Applicability shall not be made except when the ass ated ACTIONS to b entered permit con~fted oper on in the MODE or r specified condi in the i~Je~T

(\\

icability for an unli d period of time.

is Specifica n allnot prevent cha esin MODES or er specified conditions in the Applicability that are uired to cor~ y with ACTIONS or that are a part of a shuown of the unit.

-~iaexptuons to this Specification are stated in the individual Specifications.

LCO.4is only apjble for entry oaMODE other sp cified condition.46 the Applicabi in MODES

, 2, and 3.

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

LCO 3.0.6 When a supported system LCO is not met solely due to a support system LCO not being met, the Conditions and Required Actions associated with this supported system are not required to be entered. Only the support system LCO ACTIONS are required to be entered. This is an exception to LCO 3.0.2 for the supported system. In this event, an evaluation shall be performed in accordance with Specification 5.5.11, "Safety Function Determination Program (SFDP)." If a loss of safety function is (continued)

INSERT I (LCO 3.0.4)

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

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

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

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

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

SR Applicability 3.0 3.0 SR APPLICABILITY SR 3.0.3 If the Surveillance is not performed within the delay period, the (continued)

LCO must immediately be declared not met, and the applicable Condition(s) must be entered.

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

SR 3.0.4 Entry into a MODE or other specified condition in the Applicability of an LC all not be ma unless the LCO's Surveillances have bee et within their ified Frequency.

provision sha t

p vent entry into DES or other speci conditions e

C e c ' 7 Applicability th re required to com with ACTION or that are part of a shutdown of the unit.

SR 3.0.4j only appli le for entry int a MODE orpther specifie condits in the App~t'ability in MOD 1,_2, anda8 BEN-UNIT 2 3.0-5 Amendment No. 253

INSERT 2 (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.

PAM Instrumentation 3.3.3.1 3.3 INSTRUMENTATION 3.3.3.1 Post Accident Monitoring (PAM) Instrumentation LCO 3.3.3.1 The PAM instrumentation for each Function in Table 3.3.3.1 -1 shall be OPERABLE.

APPLICABILITY:

MODES I and 2.

ACTIONS NOTES (1 /t.CO 3/4 is yn'applicr KeT>

(o) 0 Separate Condition entry is allowed for each Function.

For Function 6, Separate Condition entry is allowed for each penetration flow path.

CONDITION REQUIRED ACTION COMPLETION TIME A. One or more Functions A. I Restore required channel 30 days with one required channel to OPERABLE status.

inoperable.

B. Required Action and B.1 Initiate action in Immediately associated Completion accordance with Time of Condition A not Specification 5.6.6.

met.

(continued)

BFN-UNIT 2 3.3-24 Amendment No. 253

Backup Control System 3.3.3.2 3.3 INSTRUMENTATION 3.3.3.2 Backup Control System LCO 3.3.3.2 The Backup Control System Functions shall be OPERABLE.

APPLICABILITY:

MODES I and 2.

ACTIONS NOT

• LC 3.0.4 is npt applica)te Separate Condition entry is allowed for each Function.

CONDITION REQUIRED ACTION COMPLETION TIME A. One or more required A. I Restore required Function 30 days Functions inoperable, to OPERABLE status.

B. Required Action and B.I Be in MODE 3.

12 hours1.388889e-4 days <br />0.00333 hours <br />1.984127e-5 weeks <br />4.566e-6 months <br /> associated Completion Time not met.

BFN-UNIT 2 3.3-28 Amendment No. 253

RCS Leakage Detection Instrumentation 3.4.5 ACTIONS (continued)

CONDITION REQUIRED ACTION COMPLETION TIME B. Required primary NOTE containment atmospheric LCO.4)(njapplicaW6.

monitoring system inoperable.

B.1 Analyze grab samples of Once per primary containment 12 hours1.388889e-4 days <br />0.00333 hours <br />1.984127e-5 weeks <br />4.566e-6 months <br /> atmosphere.

AND B.2 Restore required primary 30 days containment atmospheric monitoring system to OPERABLE status.

C. Required Action and C.1 Be in MODE 3.

12 hours1.388889e-4 days <br />0.00333 hours <br />1.984127e-5 weeks <br />4.566e-6 months <br /> associated Completion Time of Condition A or B AND not met.

C.2 Be in MODE 4.

36 hours4.166667e-4 days <br />0.01 hours <br />5.952381e-5 weeks <br />1.3698e-5 months <br /> D. All required leakage D.1 Enter LCO 3.0.3.

Immediately detection systems inoperable.

BFN-UNIT 2 3.4-13 Amendment No. 253

RCS Specific Activity 3.4.6 3.4 REACTOR COOLANT SYSTEM (RCS) 3.4.6 RCS Specific Activity LCO 3.4.6 The specific activity of the reactor coolant shall be limited to DOSE EQUIVALENT 1-131 specific activity *3.2 jpCi/gm.

APPLICABILITY:

MODE 1, MODES 2 and 3 with any main steam line not isolated.

ACTIONS CONDITION REQUIRED ACTION COMPLETION TIME A. Reactor coolant specific NOTE

' Se 7

activity > 3.2 piCi/gm and LCO3 is nota icable

• 5 26.0 pLCi/gm DOSE EQUIVALENT 1-131.

A. 1 Determine DOSE Once per 4 hours4.62963e-5 days <br />0.00111 hours <br />6.613757e-6 weeks <br />1.522e-6 months <br /> EQUIVALENT 1-131.

AND A.2 Restore DOSE 48 hours5.555556e-4 days <br />0.0133 hours <br />7.936508e-5 weeks <br />1.8264e-5 months <br /> EQUIVALENT 1-131 to within limits.

(continued)

BFN-UNIT 2 3.4-15 Amendment No. 253

INSERT 7 (RCS SPECIFIC ACTIVITY)

LCO 3.O.4.c is applicable.

RHR Shutdown Cooling System - Hot Shutdown 3.4.7 3.4 REACTOR COOLANT SYSTEM (RCS) 3.4.7 Residual Heat Removal (RHR) Shutdown Cooling System - Hot Shutdown LCO 3.4.7 Two RHR shutdown cooling subsystems shall be OPERABLE, and, with no recirculation pump in operation, at least one RHR shutdown cooling subsystem shall be in operation.

NOTES

1. Both required RHR shutdown cooling subsystems and recirculation pumps may not be in operation for up to 2 hours2.314815e-5 days <br />5.555556e-4 hours <br />3.306878e-6 weeks <br />7.61e-7 months <br /> per 8 hour9.259259e-5 days <br />0.00222 hours <br />1.322751e-5 weeks <br />3.044e-6 months <br /> period.

2. One required RHR shutdown cooling subsystem may be inoperable for up to 2 hours2.314815e-5 days <br />5.555556e-4 hours <br />3.306878e-6 weeks <br />7.61e-7 months <br /> for performance of Surveillances.

APPLICABILITY:

MODE 3, with reactor steam dome pressure less than the RHR low pressure permissive pressure.

ACTIONS NOTEJ 7~CO?.O.4As not applicable eparate Condition entry is allowed for each RHR shutdown cooling subsystem.

CONDITION REQUIRED ACTION COMPLETION TIME A. One or two required RHR A. 1 Initiate action to restore Immediately shutdown cooling required RHR shutdown subsystems inoperable, cooling subsystem(s) to OPERABLE status.

AN D continued)

BEN-UNIT 2 3.4-18 Amendment No. 253

ECCS-Operating 3.5.1 3.5 EMERGENCY CORE COOLING SYSTEMS (ECCS) AND REACTOR CORE ISOLATION COOLING (RCIC) SYSTEM 3.5.1 ECCS - Operating LCO 3.5.1 Each ECCS injection/spray subsystem and the Automatic

-'iepressurization System (ADS) function of six safety/relief valves shall be OPERABLE.

APPLICABILITY:

MODE 1, MODES 2 and 3, except high pressure coolant injection (HPCI) and ADS valves are not required to be OPERABLE with reactor steam dome pressure

• 150 psig.

ACTIONS_

CONDITION REQUIRED ACTION COMPLETION TIME A. One low pressure ECCS A.1 Restore low pressure 7 days injection/spray subsystem ECCS injection/spray inoperable, subsystem(s) to OPERABLE status.

OR One low pressure coolant injection (LPCI) pump in both LPCI subsystems inoperable.

B. Required Action and B.1 Be in MODE 3.

12 hours1.388889e-4 days <br />0.00333 hours <br />1.984127e-5 weeks <br />4.566e-6 months <br /> associated Completion Time of Condition A not AND met.

met.

~~B.2 Be in MODE 4.

36 hours4.166667e-4 days <br />0.01 hours <br />5.952381e-5 weeks <br />1.3698e-5 months <br /> (continued)

BFN-UNIT 2 3.5-1 Amendment No. ~ 269 March 12, 2001

BWR4 INSERT I (LCO 3.5.1, ECCS - OPERATING)

-- ~NOTE---------------------------------

LCO 3.Q.4.b is not applicable to HPCI.

RCIC System 3.5.3 3.5 EMERGENCY CORE COOLING SYSTEMS (ECCS) AND REACTOR CORE ISOLATION COOLING (RCIC) SYSTEM 3.5.3 RCIC System LCO0 3.5.3 The RCIC System shall be OPERABLE.

APPLICABILITY:

MODE 1, MODES 2 and 3 with reactor steam dome pressure > 150 psig.

ACTIONS CONDITION REQUIRED ACTION COMPLETION TIME A. RCIC System inoperable.

A.1 Verify by administrative Immediately means High Pressure Coolant Injection System is OPERABLE.

AND A.2 Restore RCIC System to 14 days OPERABLE status.

B. Required Action and B. 1 Be in MODE 3.

12 hours1.388889e-4 days <br />0.00333 hours <br />1.984127e-5 weeks <br />4.566e-6 months <br /> associated Completion Time not met.

AND B.2 Reduce reactor steam 36 hours4.166667e-4 days <br />0.01 hours <br />5.952381e-5 weeks <br />1.3698e-5 months <br /> dome pressure to

• 150 psig.

BFN-UNIT 2

3. 5-1 2 Amendment No. 253

BWR4 INSERT 2 (LCO 3.5.3, RCIC SYSTEM)

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

LCO 3.Q.4.b is not applicable to RCIC.

CAD System 3.6.3.1 3.6 CONTAINMENT SYSTEMS 3.6.3.1 Containment Atmosphere Dilution (CAD) System LCO 3.6.3.1 Two CAD subsystems shall be OPERABLE.

APPLICABILITY:

MODES I and 2.

ACTIONS CONDITION REQUIRED ACTION COMPLETION TIME A. One CAD subsystem A. 1 NOTE-inoperable.

LC

.4 0

Restore CAD subsystem 30 days to OPERABLE status.

B. Two CAD subsystems B.1 Verify by administrative 1 hour1.157407e-5 days <br />2.777778e-4 hours <br />1.653439e-6 weeks <br />3.805e-7 months <br /> inoperable, means that the hydrogen control function is AND maintained.

Once per 12 hours1.388889e-4 days <br />0.00333 hours <br />1.984127e-5 weeks <br />4.566e-6 months <br /> thereafter AND B.2 Restore one CAD 7 days subsystem to OPERABLE status.

C. RequiredrAction and C.1 Be in MODE3.

12 hours1.388889e-4 days <br />0.00333 hours <br />1.984127e-5 weeks <br />4.566e-6 months <br /> associated Completion Time not met.

BFN-UNIT 2 3.6-40 Amendment No. 2.5~ 265 May 24, 2000

AC Sources - Operating 3.8.1 3.8 ELECTRICAL POWER SYSTEMS 3.8.1 AC Sources - Operating LCO 3.8.1 The following AC electrical power sources shall be OPERABLE:

a. Two qualified circuits between the offsite transmission network and the onsite Class I E AC Electrical Power Distribution System;

b. Unit I and 2 diesel generators (DGs) with two divisions of 480 V load shed logic and common accident signal logic OPERABLE; and

c. Unit 3 DG(s) capable of supplying the Unit 3 4.16 kV shutdown board(s) required by LCO 3.8.7, "Distribution Systems -

Operating.o APPLICABILITY:

MODES 1, 2, and 3.

'4

\\

l A 3 ACTIONS CONDITION REQUIRED ACTION COMPLETION TIME A. One required offsite A. 1 Verify power availability 1 hour1.157407e-5 days <br />2.777778e-4 hours <br />1.653439e-6 weeks <br />3.805e-7 months <br /> circuit inoperable, from the remaining OPERABLE offsite AND transmission network.

Once per 8 hours9.259259e-5 days <br />0.00222 hours <br />1.322751e-5 weeks <br />3.044e-6 months <br /> thereafter AND (continued BFN-UNIT 2 3.8-1 Amendment No. 253

BWR4 INSERT 3 (LCO 3.8.1, AC SOURCES - OPERATING)

LCO 3.O.4.b is not applicable to DGs.

Browns Ferry Nuclear Plant (BFN)

Units 1, 2, and 3 Technical Specifications (TS) Change 410 Mode Change Limitations Using the Consolidated Line Item Improvement Process (CLIIP)

Changes to Technical Specifications Bases Pages (mark-up)

LCO Applicability B 3.0 BASES LCO 3.0.3 Therefore, this LCO can be applicable in any or all MODES. If the (continued)

LCO and the Required Actions of LCO 3.7.6 are not met white in MODE 1, 2, or 3, there is no safety benefit to be gained by placing the unit in a shutdown condition. The Required Action of LCO 3.7.6 of "Suspend movement of irradiated fuel assemblies in the spent fuel storage pool" is the appropriate Required Action to complete in lieu of the actions of LCO 3.0.3. These exceptions are addressed in the individual Specifications.

LCO 3.0.4 LCO 3.0.4 establishes limitations on changes in MODES or other specified co ditions in the A licability when n LCO is not met. It preclude lacing the uniti a different MO or other specified conditi stated in that plicability (e.g pplicability d red to b e epfred) whren thI Ilowing exist:

J Unitconditiok esuch that r uirementso e LCO would I

not be met i the Applicability desired to be entered; and C M ti n u e d-n o n W M p I 9 n-'Ene nt, i f the Applicability were entered, would result in the unit being x

required to exit the Applicability desired to be entered to comply t with the R uired Actions.

Complia e with Required ions that permit con 6 e operation of the nit for an unlimite riod of time in a M E or other sp ed condition pro es an acceptablele lof safety for tinued operation.

is is without regar o the status of unit efore or after the ODE change. Ther ore, in such cad s, entry into a MODE or er specified condi n in the Appli lity may be made in a rdance with the pr isions of the Re uired Actions. T provisions of this Specification sho l 6 not be interpreted as endorsing the fairure to exercise the good practice of restoring systems or compone'nts to OPERABLE status before unit startup.

(continued)

BFN-UNIT 2 B 3.0-6 Revision 0

INSERT 3 (LCO 3.0.4 BASES)

LCO 3.0.4 establishes limitations on changes in MODES or other specified conditions in the Applicability when an LCO is not met. It allows placing the unit in a MODE or other specified condition stated in that Applicability (e.g., the Applicability desired to be entered) when unit conditions are such that the requirements of the LCO would not be met, in accordance with LCO 3.0.4.a, LCO 3.0.4.b, or LCO 3.0.4.c.

LCO 3.0.4.a allows entry into a MODE or other specified condition in the Applicability with the LCO not met 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.

Compliance with Required Actions that permit continued operation of the unit for an unlimited period of time in a MODE or other specified condition provides an acceptable level of safety for continued operation. This is without regard to the status of the unit before or after the MODE change. Therefore, in such cases, entry into a MODE or other specified condition in the Applicability may be made in accordance with the provisions of the Required Actions.

LCO 3.0.4.b allows entry into a MODE or other specified condition in the Applicability with the LCO not met after performance of a risk assessment addressing inoperable systems and components, consideration of the results, determination of the acceptability of entering the MODE or other specified condition in the Applicability, and establishment of risk management actions, if appropriate.

The risk assessment may use quantitative, qualitative, or blended approaches, and the risk assessment will be conducted using the plant program, procedures, and criteria in place to implement 10 CFR 50.65(a)(4), which requires that risk impacts of maintenance activities to be assessed and managed. The risk assessment, for the purposes of LCO 3.0.4 (b), must take into account all inoperable Technical Specification equipment regardless of whether the equipment is included in the normal 10 CFR 50.65(a)(4) risk assessment scope. The risk assessments will be conducted using the procedures and guidance endorsed by Regulatory Guide 1.182, "Assessing and Managing Risk Before Maintenance Activities at Nuclear Power Plants." Regulatory Guide 1.182 endorses the guidance in Section 11 of NUMARC 93-01, "Industry Guideline for Monitoring the Effectiveness of Maintenance at Nuclear Power Plants." These documents address general guidance for conduct of the risk assessment, quantitative and qualitative guidelines for establishing risk management actions, and example risk management actions. These include actions to plan and conduct other activities in a manner that controls overall risk, increased risk awareness by shift and management personnel, actions to reduce the duration of the condition, actions to minimize the magnitude of risk increases (establishment of backup success paths or compensatory measures), and determination that the proposed MODE change is acceptable.

Consideration should also be given to the probability of completing restoration such that the requirements of the LCO would be met prior to the expiration of ACTIONS Completion Times that would require exiting the Applicability.

LCO 3.0.4.b may be used with single, or multiple systems and components unavailable.

NUMARC 93-01 provides guidance relative to consideration of simultaneous unavailability of multiple systems and components.

The results of the risk assessment shall be considered in determining the acceptability of entering the MODE or other specified condition in the Applicability, and any corresponding risk management actions. The LCO 3.0.4.b risk assessments do not have to be documented.

The Technical Specifications allow continued operation with equipment unavailable in MODE I for the duration of the Completion Time. Since this is allowable, and since in general the risk impact in that particular MODE bounds the risk of transitioning into and through the applicable MODES or other specified conditions in the Applicability of the LCO, the use of the LCO 3.0.4.b

Insert 3 (LCO 3.0.4 Bases) (Cant.)

allowance should be generally acceptable, as long as the risk is assessed and managed as stated above. However, there is a small subset of systems and components that have been determined to be more important to risk and use of the LCO 3.0.4.b allowance is prohibited. The LCOs governing these system and components contain Notes prohibiting the use of LCO 3.0.4.b by stating that LCO 3.0.4.b is not applicable.

LCO 3.0.4.c allows entry into a MODE or other specified condition in the Applicability with the LCO not met based on a Note in the Specification which states LCO 3.0.4.c is applicable. These specific allowances permit entry into MODES or other specified conditions in the Applicability when the associated ACTIONS to be entered do not provide for continued operation for an unlimited period of time and a risk assessment has not been performed. This allowance may apply to all the ACTIONS or to a specific Required Action of a Specification. The risk assessments performed to justify the use of LCO 3.0.4.b usually only consider systems and components. For this reason, LCO 3.O.4.c is typically applied to Specifications which describe values and parameters (e.g., Reactor Coolant System Specific Activity), and may be applied to other Specifications based on NRC plant-specific approval.

The provisions of this Specification should not be interpreted as endorsing the failure to exercise the good practice of restoring systems or components to OPERABLE status before entering an associated MODE or other specified condition in the Applicability.

The provisions of LCO 3.0.4 shall not prevent changes in MODES or other specified conditions in the Applicability that are required to comply with ACTIONS. In addition, the provisions of LCO 3.0.4 shall not prevent changes in MODES or other specified conditions in the Applicability that result from any unit shutdown. In this context, a unit shutdown is defined as a change in MODE or other specified condition in the Applicability associated with transitioning from MODE 1 to MODE 2, MODE 2 to MODE 3, and MODE 3 to MODE 4.

Upon entry into a MODE or other specified condition in the Applicability with the LCO not met, LCO 3.0.1 and LCO 3.0.2 require entry into the applicable Conditions and Required Actions until the Condition is resolved, until the LCO is met, or until the unit is not within the Applicability of the Technical Specification.

Surveillances do not have to be performed on the associated inoperable equipment (or on variables outside the specified limits), as permitted by SR 3.0.1. Therefore, utilizing LCO 3.0.4 is not a violation of SR 3.0.1 or SR 3.0.4 for any Surveillances that have not been performed on inoperable equipment. However, SRs must be met to ensure OPERABILITY prior to declaring the associated equipment OPERABLE (or variable within limits) and restoring compliance with the affected LCO.

LCO Applicability B 3.0 BASES LCO 3.0.4 The provisions of LCO.0.4 shall not prevent changes in MODES (continued) or other specified ditions in the Applicability that are required to comply with AC NS. In addition, t e provisions of LCO 3.0.4 shall not pre nt changes in MOD or other specified conditions in the Ap cability that result f any unit shutdown.

E tions to LCO 3.0.

re stated in the individual Specifications.

V-T e exceptions allo ntry into MODES or other s ecified conditions in the A plicability when the associa ACTIONS to be entered do no rovide for continued operati for an unlimited period of time Exceptions may apply to he ACTIONS or to a specific quired Action of a Specifica n.

LCO 3.0.4 is only applicable wh entering MODE 3 from DE 4,

'MODE 2 from MODE 3 or 4, o ODE I from MODE 2.

"Furthermore, LCO 3.0.4 is plicable when enterin ny other specified condition in th plcability only while erating in MODE 1, 2, or 3. Th equirements of LCO 34 do not apply in MODES 4 and 5, o n other specified con ons of the Applicability (unless in MODE

, 2, or 3) because th

,CTIONS of individual specifications s iciently define the r edial measures to be

'taken. [In some cases (e.g.,..) the ACTIONS provide aQote that states 'While this LCO is not mj, entry into a MODE o ther Ispecified condition in the Applicability is not permitt unless required to comply with ACTIONS." This Note is a requirement jxplicitly precluding entry into a MODE or other specified condition /

the Appicability.]

(continued)

BFN.-UNIT 2 B 3.0-7 Revision 0

LCO Applicability B 3.0 BASES LCO 3.0.4 Surveillances do not have to be performed on the associated (continued) inoperable uipment (or on variables outside the specified limits),

aspe edbySR3.0.1. T reforechanging MODES or other spe 'ted conditions whil an ACTIONS Co ition, either in pliance with LCO 0.4 or where an e ption to LCO 3.0.4 is stated, is not a vi ion of SR 3.0.1 or 3.0.4 for those Surveillances at do not have to b erformed due to associated* operable equipmen. However, SRs st be met to ensure OPERABILITY prior to eclaring the as ciated equipment OPERABLE (or variable within limits) and re oring compliance with the affected LCO.

LCO 3.0.5 LCO 3.0.5 establishes the allowance for restoring equipment to service under administrative controls when it has been removed from service or declared inoperable to comply with ACTIONS. The sole purpose of this Specification is to provide an exception to LCO 3.0.2 (e.g., to not comply with the applicable Required Action(s)) to allow the performance of required testing to demonstrate:

a. The OPERABILITY of the equipment being returned to service; or

b. The OPERABILITY of other equipment.

The administrative controls ensure the time the equipment is returned to service in conflict with the requirements of the ACTIONS is limited to the time absolutely necessary to perform the required testing to demonstrate OPERABILITY. This Specification does not provide time to perform any other preventive or corrective maintenance.

(continued)

BFN-UNIT 2 B 3.0-8 Revision 0

SR Applicability B 3.0 BASES (continued)

SR 3.0.4 3.0.4 establishes the re uirement that all applicable SRs must be met before entry into ODE or other specified condition in the Applicability.

This Specificatjp ensures that system apdomponent OPERABILIP(

requirements and var able limits are met before entry into ODES or other specifi gconditions in the Applicability for wh[eCtthese systems and ponents ensure safe operation of the it.

sysem he provisions of this pa$ification should not be in feeted as endorsing the fail to exercise the good practi f restoring systems or components to OPERABLE status ore entering an associated M9DE or other specified condin in the Applicability.

However,1n certain circumstances fai g to meet an SR will not result in. SR 3.0.4 restricting a MO change or other specified condition change. When a sysje, subsystem, division,

/

component, device, or variab

'is inoperable or outside its specified limits, the associat'ed SR(s) are not required t performed, per SR 3.0.1 /which states that Surveilla s do not have to be performedAJn inoperable equipment.

en equipment is inoperable, SR 3.0.4 does not apply to the a ciated SR(s) since the requirement for the SR(s) to be pe rmed is removed.

Therefore, failing to perform the Surveilla e(s) within the speIted Frequency does not result in an SR 3 0 restriction to cha ng MDES or other specified conditions4 h plcblt.

However, since the LCO is not metih this instance, LCO 3.0.4 will govern any restrictions that may (or may not) apply to'MODE or

\\ other specified condition changes.

(continued)

BFN-UNIT 2 B 3.0-17 Revision 0

INSERT 4 (SR 3.0.4 BASES)

SR 3.0.4 establishes the requirement that all applicable SRs must be met before entry into a MODE or other specified condition in the Applicability.

This Specification ensures that system and component OPERABILITY requirements and variable limits are met before entry into MODES or other specified conditions in the Applicability for which these systems and components ensure safe operation of the unit. The provisions of this Specification should not be interpreted as endorsing the failure to exercise the good practice of restoring systems or components to OPERABLE status before entering an associated MODE or other specified condition in the Applicability.

A provision is included to allow entry into a MODE or other specified condition in the Applicability when an LCO is not met due to Surveillance not being met in accordance with LCO 3.0.4.

However, in certain circumstances, failing to meet an SR will not result in SR 3.0.4 restricting a MODE change or other specified condition change. When a system, subsystem, division, component, device, or variable is inoperable or outside its specified limits, the associated SR(s) are not required to be performed, per SR 3.0.1, which states that surveillances do not have to be performed on inoperable equipment. When equipment is inoperable, SR 3.0.4 does not apply to the associated SR(s) since the requirement for the SR(s) to be performed is removed.

Therefore, failing to perform the Surveillance(s) within the specified Frequency does not result in an SR 3.0.4 restriction to changing MODES or other specified conditions of the Applicability.

However, since the LCO is not met in this instance, LCO 3.0.4 will govern any restrictions that may (or may not) apply to MODE or other specified condition changes. SR 3.0.4 does not restrict changing MODES or other specified conditions of the Applicability when a Surveillance has not been performed within the specified Frequency, provided the requirement to declare the LCO not met has been delayed in accordance with SR 3.0.3.

The provisions of SR 3.0.4 shall not prevent entry into MODES or other specified conditions in the Applicability that are required to comply with ACTIONS. In addition, the provisions of SR 3.0.4 shall not prevent changes in MODES or other specified conditions in the Applicability that result from any unit shutdown. In this context, a unit shutdown is defined as a change in MODE or other specified condition in the Applicability associated with transitioning from MODE 1 to MODE 2, MODE 2 to MODE 3, and MODE 3 to MODE 4.

The precise requirements for performance of SRs are specified such that exceptions to SR 3.0.4 are not necessary. The specific time frames and conditions necessary for meeting the SRs are specified in the Frequency, in the Surveillance, or both. This allows performance of Surveillances when the prerequisite condition(s) specified in a Surveillance procedure require entry into the MODE or other specified condition in the Applicability of the associated LCO prior to the performance or completion of a Surveillance. A Surveillance that could not be performed until after entering the LCO's Applicability, would have its Frequency specified such that it is not "due" until the specific conditions needed are met. Alternately, the Surveillance may be stated in the form of a Note, as not required (to be met or performed) until a particular event, condition, or time has been reached. Further discussion of the specific formats of SRs' annotation is found in Section 1.4, Frequency.

SR Applicability B 3.0 BASES SR 3.0.4 The provisions of SR 3.0.4 shall not prevent changes in MODES or (continued) other specified conditions in the Applicability that are required to comply with ACTIONS. In addition, the provisions of SR 3.0.4 shall not prevent changes in MP ES or other specified conditions in the Applicability that resu tVfrom any unit shutdown.

I The precise req irements for performance o s are specified such that e ptions to SR 3.0.4 are no cessary. The specific time fr and conditions necess or meeting the SRs are specified in the Frequency, in thy urveillance, or both. This a cSd's performance of Surveji dhces when the prerequisite zondition(s) specified in *Surveillance procedure re uire entry into the MODE or other s iified condition in the Appl, ility of the associated LCO pef to the performance or co letion of a Surveillance. i~.Surveillance that could not performed until after entering the LCO Applicability would ha its Frequency specified such that it-fs not "due" until the specj c conditions needed are met. Altemately, the Surveillance, ay be stated in the form of a Note.as not required (to be mei< performed) until a particular event, condition, or time ha* been reached. Further discussion of the specific formats of SR. annotation is found in Section 1.4, Frequency.

/

SR 3.0.4 is only applicable when entering MODE 3 f MODE 4, MODE 2 from MODE 3 or 4, or MODE I from MO 2.

Furthermore, SR 3.0.4 is applicable when ent ng any other specified condition in the Applicability only ile operating in MODE 1, 2, or 3. The requirements of SF(

.4 do not apply in MODES 4 and 5, or in other specifiedOconditions of the Applicability I (unless in MODE 1, 2, or 3) because the ACTIONS of individual Specifications sufficiently define the remedial measures to be taken.

BFN-UNIT 2 B 3.0-18 Revision 0

PAM Instrumentation B 3.3.3.1 BASES (continued)

APPLICABILITY The PAM instrumentation LCO is applicable in MODES I and 2.

These variables are related to the diagnosis and preplanned actions required to mitigate DBAs. The applicable DBAs are assumed to occur in V'.)DES I and 2. In MODES 3, 4, and 5, plant conditions are sL: lh that the likelihood of an event that would require PAM instlrumentation is extremely low; therefore, PAM instrumentation is not required to be OPERABLE in these MODES.

ACTIONS Note I has been added to the ACTIONS to exclude the MODE change restrictq of LCO 3.0.4. T is exception allows entry into the ap ble MODE whil elying on the ACTIOSS even though eACTIONS may entually require pi utdown.

Thi xception is acce le due to the pas function of the truments, the op tos ability to dia se an accident using /

\\ alternative instruents and methods, d the low probability of an event requiring these instruments.

Note S~-

have been provided to modify the ACTIONS re ae~d to PAM instrumentation channels. Section 1.3, Completion Times, specifies that once a Condition has been entered, subsequent divisions, 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. Section 1.3 also specifies that Required Actions of the Condition continue to apply for each additional failure, with Completion Times based on initial entry into the Condition. However, the Required Actions for inoperable PAM instrumentation channels provide appropriate compensatory-..4-measures for separate Functions. As such, Note hias been provided to allow separate Condition entry for each inoperable PAM Function. Note tZhas been provided for Function 6 to allow separate Condition ientry for each penetration flow path.

BFN-UNIT 2 B 3.3-92 Revision 0

Backup Control System B 3.3.3.2 BASES (continued)

ACTIONS A Note is included that excludes the MODE change restriction of LCO 3.4. This excepti allows entry i to an applicabi MO hile relying on ACTIONS e though the A ONS may eve ally require ant shutdown.

is xrception is acc able due to low probabilit f an event quiring this stem.

Noteas been provided to modify the ACTIONS related to K~J/ ~Backup Control System Functions. Section 1.3, Completion Times, specifies that once a Condition has been entered, subsequent divisions, 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.

Section 1.3 also specifies that Required Actions of the Condition continue to apply for each additional failure, with Completion Times based on initial entry into the Condition.

However, the Required Actions for inoperable Backup Control System Functions provide appropriate compensatory measures for separate Functions. As such, a Note has been provided that allows separate Condition entry for each inoperable Backup Control System Function.

A. 1 Condition A addresses the situation where one or more required Functions of the Backup Control System is inoperable.

This includes any instrument parameter Function listed in Table B 3.3.3.2-1, as well as the control and transfer switches.

The Required Action is to restore the Function to OPERABLE status within 30 days. The Completion Time is based on operating experience and the low probability of an event that would require evacuation of the control room.

(continued)

BFN-UNlT 2 B 3.3-102 Revision 4 April 09, 1999

RCS Leakage Detection Instrumentation B 3.4.5 BASES ACTIONS 8.1 and B.2 (continued)

The 12 hour1.388889e-4 days <br />0.00333 hours <br />1.984127e-5 weeks <br />4.566e-6 months <br /> interval provides periodic information that is adequate to detect LEAKAGE. The 30 day Completion Time for restoration recognizes that at least one other form of leakage detection is available.

(The Requir d Actions are modified by a Note that states that the provsibns of LCO 3-O.4 are not applicable. As a result, a 10 change is rowed when bo e gaseous and pficulate pr4.y containme #mospheric9 nitoring channels\\

noperable. 3i allowance* provided because other instrumentation is`'available to m itor RCS leakage.

C.1 and C.2 If any Required Action and associated Completion Time of Condition A or B cannot be met, the plant must be brought to a MODE in which the LCO does not apply. To achieve this status, the plant must be brought to at least MODE 3 within 12 hours1.388889e-4 days <br />0.00333 hours <br />1.984127e-5 weeks <br />4.566e-6 months <br /> and MODE 4 within 36 hours4.166667e-4 days <br />0.01 hours <br />5.952381e-5 weeks <br />1.3698e-5 months <br />. The allowed Completion Times are reasonable, based on operating experience, to perform the actions in an orderly manner and without challenging plant systems.

D.1 With all required monitors inoperable, no required automatic means of monitoring LEAKAGE are available, and immediate plant shutdown in accordance with LCO 3.0.3 is required.

(continued)

BFN-UNIT 2 B 3.4-34 Revision 0

RCS Specific Activity B 3.4.6 BASES (continued)

APPLICABILITY In MODE 1, and MODES 2 and 3 with any main steam line not isolated, limits on the primary coolant radioactivity are applicable since there is an escape path for release of radioactive material from the primary coolant to the environment in the event of an MSLB outside of primary containment.

In MODES 2 and 3 with the main steam lines isolated, such limits do not apply since an escape path does not exist. In MODES 4 and 5, no limits are required since the reactor is not pressurized and the potential for leakage is reduced.

ACTIONS A. 1 and A.2 When the reactor coolant specific activity exceeds the LCO DOSE EQUIVALENT 1-131 limit, but is *26.0 j.Ci/gm, samples must be analyzed for DOSE EQUIVALENT 1-131 at least once every 4 hours4.62963e-5 days <br />0.00111 hours <br />6.613757e-6 weeks <br />1.522e-6 months <br />. In addition, the specific activity must be restored to the LCO limit within 48 hours5.555556e-4 days <br />0.0133 hours <br />7.936508e-5 weeks <br />1.8264e-5 months <br />. The Completion Time of once every 4 hours4.62963e-5 days <br />0.00111 hours <br />6.613757e-6 weeks <br />1.522e-6 months <br /> is based on the time needed to take and analyze a sample. The 48 hour5.555556e-4 days <br />0.0133 hours <br />7.936508e-5 weeks <br />1.8264e-5 months <br /> Completion Time to restore the activity level provides a reasonable time for temporary coolant activity increases (iodine spikes) to be cleaned up with the normal processing systems.

A Note to Required Actions f Condition A excludes the MODE W.

j40 S

cha ere cion of LC

.0.4. This ception allo >sentry Ip~i;Sar t e p~licable M

() whrile ing on th CTIONS even ough eAC IONS may e ntuall re ire lant shutdown. Thi s acceptable due to the significant conrs~erva~s~rnmnporporate-d into the specific activity limit, the low probability of an event which is limiting due to exceeding this limit, and the ability to restore transient specific activity A

v (e

excursions while the plant remains at, or proceeds to power operation.

(continued)

BFN-UNIT 2 B 3.4-39 Revision 0

INSERT 8 (RCS SPECIFIC ACTIVITY BASES)

A Note permits the use of the provisions of LCO 3.O.4.c. This allowance permits entry into the applicable MODE(S) while relying on the ACTIONS.

RHR Shutdown Cooling System - Hot Shutdown B 3.4.7 BASES APPLICABILITY The requirements for decay heat removal in MODES 4 and 5 (continued) are discussed in LCO 3.4.8, "Residual Heat Removal (RHR)

Shutdown Cooling System - Cold Shutdown"; LCO 3.9.7, "Residual Heat Removal (RHR) - High Water Level"; and LCO 3.9.8, "Residual Heat Removal (RHR) - Low Water Level."

ACTIONS

-AN6t-th the ACTIONS excludes the MODE change restrictionu\\

of LCO 3.0.4. T exception al s entry into the applicable MODE(S) w relying on t ACTIONS ev ough the ACTION ay eventual require plant utdown. This excep n is accepta due to the undancy of the OP BLE sub tems, the lo ressure at whi he plant is erating, the w probabilit f an event oc ing during operation i is conditio and the availabi ity of alternate methods of decay heat removal capability.

A seeed Note has been provided to modify the ACTIONS related to RHR shutdown cooling subsystems. Section 1.3, Completion Times, specifies once a Condition has been entered, subsequent divisions, 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. Section 1.3, also specifies Required Actions of the Condition continue to apply for each additional failure, with Completion Times based on initial entry into the Condition.

However, the Required Actions for inoperable shutdown cooling subsystems provide appropriate compensatory measures for separate inoperable shutdown cooling subsystems. As such, a Note has been provided that allows separate Condition entry for each inoperable RHR shutdown cooling subsystem.

(continued)

BFN-UNIT 2 B 3.4-45 Revision 3 March 19, 1 999

ECOS - Operating B 3.5.1 BASES LCO LPCI subsystems may be considered OPERABLE during (continued) alignment and operation for decay heat removal when below the actual RHR low pressure permissive pressure in MODE 3, if capable of being manually realigned (remote or local) to the LPCI mode and not otherwise inoperable. At these low pressures and decay heat levels, a reduced complement of ECCS subsystems should provide the required core cooling, thereby allowing operation of RHR shutdown cooling when necessary.

APPLICABILITY All ECCS subsystems are required to be OPERABLE during MODES 1, 2, and 3, when there is considerable energy in the reactor core and core cooling would be required to prevent fuel damage in the event of a break in the primary system piping. In MODES 2 and 3, when reactor steam dome pressure is

• 150 psig, ADS and HPCI are not required to be OPERABLE because the low pressure ECOS subsystems can provide sufficient flow below this pressure. ECCS requirements for MODES 4 and 5 are specified in LCO 3.5.2, "ECOS -

Shutdown.."

ACTIONS A.1 If any one low pressure ECCS injection/spray subsystem is inoperable, or if one LPCI pump in both LPCI subsystems is inoperable, the inoperable subsystem(s) must be restored to OPERABLE status within 7 days. In this condition, the 4

0remaining OPERABLE subsystems provide adequate core cooling during a LOCA. However, overall ECCS reliability is reduced, because a single failure in one of the remaining OPERABLE subsystems, concurrent with a LOCA, may result in the ECCS not being able to perform its intended safety function.

BEN-UNIT 2 B 3.5-8 Amendment No. 269 March 12, 2001

BWR4 INSERT lB (LCO 3.5.1, ECCS - OPERATING)

A Note prohibits the application of LCO 3.Q.4.b to an inoperable HPCI subsystem. There is an increased risk associated with entering a MODE or other specified condition in the Applicability with an inoperable HPCI subsystem and the provisions of LCO 3.O.4.b, which allow entry into a MODE or other specified condition in the Applicability with the LCO not met after performance of a risk assessment addressing inoperable systems and components, should not be applied in this circumstance.

RCIC System B 3.5.3 BASES (continued)

LCO The OPERABILITY of the RCIC System provides adequate core cooling such that actuation of any of the low pressure ECCS subsystems is not required in the event of RPV isolation accompanied by a loss of feedwater flow. The RCIC System has sufficient capacity for maintaining RPV inventory during an isolation event.

APPLICABILITY The RCIC System is required to be OPERABLE during MODE 1, and MODES 2 and 3 with reactor steam dome pressure > 150 psig, since RCIC is the primary non-ECCS water source for core cooling when the reactor is isolated and pressurized. In MODES 2 and 3 with reactor steam dome pressure

• 150 psig, and in MODES 4 and 5, ROIC is not required to be OPERABLE since the low pressure ECCS injection/spray subsystems can provide sufficient flow to the RPV.

ACTIONS A.1 and A.2 If the RCIC System is inoperable during MODE 1, or MODE 2 or 3 with reactor steam dome pressure > 150 psig, and the HPCI System is immediately verified to be OPERABLE, the RCIC System must be restored to OPERABLE status within 14 days. In this Condition, loss of the RCIC System will not affect the overall plant capability to provide makeup inventory at high reactor pressure since the HPCI System is the only high pressure system assumed to function during a loss of coolant accident (LOCA). OPERABILITY of HPCI is therefore immediately verified when the RCIC System is inoperable. This may be performed as an administrative check, by examining logs or other information, to determine if HPCI is out of service for maintenance or other reasons. It does not mean it is (continued)

BFN-.UNlT 2 B 3.5-32 Revision 0

BWR4 INSERT 2B (LCO 3.5.3, RCIC SYSTEM)

A Note prohibits the application of LCO 3.O.4.b to an inoperable RCIC system. There is an increased risk associated with entering a MODE or other specified condition in the Applicability with an inoperable RCIC system and the provisions of LCO 3.O.4.b, which allow entry into a MODE or other specified condition in the Applicability with the LCO not met after performance of a risk assessment addressing inoperable systems and components, should not be applied in this circumstance.

CAD System B 3.6.3.1 BASES (continued)

ACTIONS A. 1 If one CAD subsystem is inoperable, it must be restored to OPERABLE status within 30 days. In this Condition, the remaining OPERABLE CAD subsystem is adequate to perform the oxygen control function. However, the overall reliability is reduced because a single failure in the OPERABLE subsystem could result in reduced oxygen control capability. The 30 day Completion Time is based on the low probability of the occurrence of a LOCA that would generate hydrogen and oxygen in amounts capable of exceeding the flammability limit, the amount of time available after the event for operator action to prevent exceeding this limit, and the availability of the OPERABLE CAD subsystem and other hydrogen mitigating systems.

/ 'Re uuied Action A.1 has been modified by a Note that indicates 1 that the prn'visions of LCO 3.0.4 are not applicable. As a result, a MO change is allowed when one CAD subsystem is ino rable. This allo fce is provided because of the low bability of the ourrce of a LOC Kat would generate hydrogen ando gen in amounts ble of exceeding e

flammability it, the low proba of the failure of OPERAB subsystem, the ount of time avai e after a postula.ted LOCA for ope oraction to prey exceeding the flammability limit, and.th'e presence of an4i erted containment atmosphere during normal operations.

B.1 and B.2 With two CAD subsystems inoperable, the ability to control the hydrogen control function via alternate capabilities must be verified by administrative means within 1 hour1.157407e-5 days <br />2.777778e-4 hours <br />1.653439e-6 weeks <br />3.805e-7 months <br />. The alternate hydrogen control capabilities are provided by the Primary Containment Inerting System. The 1 hour1.157407e-5 days <br />2.777778e-4 hours <br />1.653439e-6 weeks <br />3.805e-7 months <br /> Completion Time (continued)

BFN-UNIT 2 B 3.6.93 Amendment No. 265 May 24,2000

AC Sources - Operating B 3.8.1 BASES (continued)

ACTIONS A.1 To ensure a highly reliable power source remains with one required offsite circuit inoperable, it is necessary to verify the availability of the remaining required offsite circuit on a more vi Li frequent basis. This action ensures proper circuit continuity for NB~

i~Lf the offsite AC electrical power supply to the onsite distribution

\\,,,p~

/

network and availability of offsite AC electrical power. If a second required circuit is not available, the second offsite circuit is inoperable, and Condition E, for two offsite circuits inoperable, is entered.

A.2 Required Action A.2, which only applies if one or both 4.16 kV shutdown boards in a division cannot be powered from a qualified offsite source, is intended to provide assurance that an event with a coincident single failure of a DG does not result in a complete loss of safety function of critical systems. These features are designed with redundant safety related divisions (i.e., single division systems are not included). Redundant required features failures consist of inoperable features associated with a division redundant to the division that has no offsite power. For example, if no qualified offsite power source was available to 4.16 kV shutdown board A and RHR pump D was inoperable for maintenance, then RHR pump A would have to be declared inoperable.

(continued)

BFN-UNIT 2 B 3.8-11 Revision 0

BWR4 INSERT 3B (LCO 3.8.1, AC SOURCES - OPERATING)

A Note prohibits the application of LCO 3.O.4.b to an inoperable DG. There is an increased risk associated with entering a MODE or other specified condition in the Applicability with an inoperable DG and the provisions of LCO 3.O.4.b, which allow entry into a MODE or other specified condition in the Applicability with the LCO not met after performance of a risk assessment addressing inoperable systems and components, should not be applied in this circumstance.