TS-3.0.2: Difference between revisions

From kanterella
Jump to navigation Jump to search
(Regex Bot pdf)
 
(No difference)

Latest revision as of 09:15, 5 December 2017

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.

Bases

LCO 3.0.2 establishes that upon discovery of a failure to meet an LCO, the associated ACTIONS shall be met. The Completion Time of each Required Action for an ACTIONS Condition is applicable from the point in time that an ACTIONS Condition is entered. The Required Actions establish those remedial measures that must be taken within specified Completion Times when the requirements of an LCO are not met. This Specification establishes that:

a. Completion of the Required Actions within the specified Completion Times constitutes compliance with a Specification and
b. Completion of the Required Actions is not required when an LCO is met within the specified Completion Time, unless otherwise specified.

There are two basic types of Required Actions. The first type of Required Action specifies a time limit in which the LCO must be met. This time limit is the Completion Time to restore an inoperable system or component to OPERABLE status or to restore variables to within specified limits. If this type of Required Action is not completed within the specified Completion Time, a shutdown may be required to place the unit in a MODE or condition in which the Specification is not applicable. (Whether stated as a Required Action or not, correction of the entered Condition is an action that may always be considered upon entering ACTIONS.) The second type of Required Action specifies the remedial measures that permit continued operation of the unit that is not further restricted by the Completion Time. In this case, compliance with the Required Actions provides an acceptable level of safety for continued operation.

Completing the Required Actions is not required when an LCO is met or is no longer applicable, unless otherwise stated in the individual Specifications.

The nature of some Required Actions of some Conditions necessitates that, once the Condition is entered, the Required Actions must be completed even though the associated Conditions no longer exist. The individual LCO's ACTIONS specify the Required Actions where this is the case. An example of this is in LCO 3.4.10, "RCS Pressure and Temperature (P/T) Limits." The Completion Times of the Required Actions are also applicable when a system or component is removed from service intentionally. The reasons for intentionally relying on the ACTIONS include, but are not limited to, performance of Surveillances, preventive maintenance, corrective maintenance, or investigation of operational problems.

Entering ACTIONS for these reasons must be done in a manner that does not compromise safety. Intentional entry into ACTIONS should not be made for operational convenience. Additionally, if intentional entry into ACTIONS would result in redundant equipment being inoperable, alternatives should be used instead. Doing so limits the time both subsystems/divisions of a safety function are inoperable and limits the time conditions exist which may result in LCO 3.0.3 being entered.

Individual Specifications may specify a time limit for performing an SR when equipment is removed from service or bypassed for testing. In this case, the Completion Times of the Required Actions are applicable when this time limit expires, if the equipment remains removed from service or bypassed.

When a change in MODE or other specified condition is required to comply with Required Actions, the unit may enter a MODE or other specified condition in which another Specification becomes applicable. In this case, the Completion Times of the associated Required Actions would apply from the point in time that the new Specification becomes applicable, and the ACTIONS Condition(s) are entered. See: ML12104A192 and ML12104A193

 SiteStart dateTitle
05000220/FIN-2011005-01Nine Mile Point31 December 2011 23:59:59Troubleshooting Approach Not Consistent With Technical Specification Bases
05000341/FIN-2014003-01Fermi30 June 2014 23:59:59Incorrect Application of TSSR 3.0.3 to Never-Performed Battery Surveillances
05000424/FIN-2009005-01Vogtle31 December 2009 23:59:59Operation of NSCW System with Tower Return Valves in Open Bypass
05000424/FIN-2014004-06Vogtle30 September 2014 23:59:59Licensee-Identified Violation
05000440/FIN-2010004-02Perry30 September 2010 23:59:59Failure to Comply with Technical Specification LCOs When Reactor Vessel Level Instruments Were Declared Inoperable
05000440/FIN-2010005-06Perry31 December 2010 23:59:59Licensee-Identified Violation
05000443/FIN-2017002-01Seabrook30 June 2017 23:59:59Seabrook Station Use and Application of Technical Specifications.
05000455/FIN-2014005-05Byron31 December 2014 23:59:59Containment Penetration Isolation Valves Rendered Inoperable for Operational Convenience