3.0 LCO APPLICABILITY Flashcards
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 and LCO 3.0.7.
SR 3.0.1 Surveillance requirements shall be met during the MODES or other specified conditions in the Applicability of 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 a 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 performed on inoperable equipment or variables outside specified limits.
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 3.0.6
If the LCO is met, or is no longer applicable prior to expiration of the specified Completion Times(s), completion of the Required Action(s) is not required, unless otherwise stated.
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.
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 hour to place the unit, as applicable in:
a. MODE 3 within 7 hours; and
b. MODE 4 within 13 hours; and
c. MODE 5 within 37 hours.
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 hours 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 hours 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.
3.0.4 When an LCO is not met, entry into a MODE or other specified condition in the Applicability 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 prevent changes in MODES or other specified conditions in the Applicability that are required to comply with ACTIONS or are part of a shutdown of the unit.
Exceptions to this Specification are stated in the individual Specifications.
LCO 3.0.4 is only applicable for entry into a MODE or other specified condition in the Applicability in Modes 1, 2, 3, and 4.
SR 3.0.4 Entry into a MODE or other specified condition in the Applicability of a LCO shall not be made unless the LCO’s Surveillances have been met within their specified Frequency. 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.
SR 3.0.4 is only applicable for entry into a MODE or other specified condition in the Applicability in MODES 1, 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 test requried to demonstrate OPERABILITY.
N/A
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 the 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 IAW Specification 5.5.7, “Safety Function Determination Program.” 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 applicable Conditions and Required Actions shall be entered IAW LCO 3.0.2
N/A
3.0.7 Test Exception LCOs 3.1.8 and 3.1.10 allow specified Tech Spec 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 MODE or other specified condition in the Applicability shall be made IAW the other applicable Specifications.