ML040570691

Informational Copy of Operating License & Appendices. Technical Specification Pages 3.0.1 Through 3.0.5 for Amendment 176

ML040570691
Person / Time
Site:	Robinson
Issue date:	02/18/2004
From:	Progress Energy Carolinas
To:	Office of Nuclear Reactor Regulation
References
Download: ML040570691 (5)

Text

LCO Applicability 3.0 LIMITING CONDITION FOR OPERATION (LCO) APPLICABILITY LCO 3.0.1 LCOs shall be met during the MODESor other specified conditions in the Applicability, except as provided in LCO 3.0.2 and 3.0.7.

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

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

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

a. MODE3 within 7 hour8.101852e-5 days <br />0.00194 hours <br />1.157407e-5 weeks <br />2.6635e-6 months <br />s:

b. MODE4 within 13 hour1.50463e-4 days <br />0.00361 hours <br />2.149471e-5 weeks <br />4.9465e-6 months <br />s: and C. MODE5 within 37 hours4.282407e-4 days <br />0.0103 hours <br />6.117725e-5 weeks <br />1.40785e-5 months <br />.

Exceptions to this Specification are stated in the individual Specifications.

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

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

LCO 3.0.4 When an LCO is not met, entry into a MODEor other specified condition in the Applicability shall not be made except when the associated ACTIONS to be entered permit continued operation in the MODEor other specified condition in the Applicability for an unlimited period of time. This (continued)

HBRSEP Unit No. 2 3.0-l Amendment No. 176

LCO Applicability 3.0 LCO APPLICABILITY LCO 3.0.4 Specification shall not prevent changes in MODESor other (continued) specified conditions in the Applicability that are required to comply with ACTIONS or that are part of a shutdown of the unit.

Exceptions to this Specification are stated in the individual Specifications. These exceptions allow entry into MODESor other specified conditions in the Applicability when the associated ACTIONS to be entered allow unit operation in the MODEor other specified condition in the Applicability only for a limited period of time.

LCO 3.0.4 is only applicable for entry into a MODEor other specified condition in the Applicability in MODES1, 2, 3, and 4.

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, additional evaluations and limitations may be required in accordance with Specification 5.5.15, "Safety Function Determination Program (SFDP)." If a loss of safety function is determined to exist by this program, the appropriate Conditions and Required Actions of the LCO in which the loss of 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 (continued)

HBRSEP Unit No. 2 3.0-2 Amendment No. 176

LCO Applicability 3.0 LCO APPLICABILITY LCO 3.0.6 applicable Conditions and Required Actions shall be entered (continued) in accordance with LCO 3.0.2.

LCO 3.0.7 Test Exception LCO 3.1.8 allows specified Technical Specification (TS) requirements to be changed to permit performance of special tests and operations. Unless otherwise specified, all other TS requirements remain unchanged. Compliance with 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 MODEor other specified condition in the Applicability shall be made in accordance with the other applicable Specifications.

HBRSEP Unit No. 2 3.0-3 Amendment No. 176

SR Applicability 3.0 SURVEILLANCE REQUIREMENT(SR) APPLICABILITY SR 3.0.1 SRs shall be met during the MODESor other specified conditions in the Applicability for individual LCOs, unless otherwise stated in the SR. Failure to meet a Surveillance, whether such failure is experienced during the performance of the Surveillance or between performances of the Surveillance, shall be failure to meet the LCO. Failure to perform a Surveillance within the specified Frequency shall be failure to meet the LCO except as provided in SR 3.0.3.

Surveillances do not have to be performed on inoperable equipment or variables outside specified limits.

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

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

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

Exceptions to this Specification are stated in the individual Specifications.

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

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

HBRSEP Unit No. 2 3.0-4 Amendment No. 176

SR Applicability; 3.0 SR APPLICABILITY SR 3.0.3 declared not met, and the applicable Condition(s) must be (continued) entered.

SR 3.0.4 Entry into a MODEor other specified condition in the Applicability of an LCO shall not be made unless the LCO's Surveillances have been met within their specified Frequency. This provision shall not prevent entry into MODESor other specified conditions in the Applicability that are required to comply with ACTIONS or that are part of a shutdown of the unit.

SR 3.0.4 is only applicable for entry into a MODEor other specified condition in the Applicability in MODES1, 2, 3, and 4.

HBRSEP Unit No. 2 3.0-5 Amendment No. 176