ML20094F995
| ML20094F995 | |
| Person / Time | |
|---|---|
| Site: | Perry  |
| Issue date: | 02/11/1992 |
| From: | Office of Nuclear Reactor Regulation |
| To: | |
| Shared Package | |
| ML20094F999 | List: |
| References | |
| NUDOCS 9202280101 | |
| Download: ML20094F995 (5) | |
Text
r-i a
3/4.0 APPtlCAB!t!TY LIMITING CONDITION FOR OPERATION 3.0.1 Compliance with the Limiting Conditions for Operation contained in the succeeding Specific &tions is required during the OPERATIONAL CONDITIONS or other conditions specified therein; except that upon failure to meet the Limiting Conditions for Operation, the associated ACTION requirements shall be me s.
3.0.2 Noncompliance with a $pecification shull 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 requiaements is not required.
3.0.3 When a Limiting Condition for Operation is not met, except as provided in the associated ACTION requirements, within one hour action shall be initiated to place the unit in an OPERATIONAL CONDITION 'i which the Specification does not apply by placing it, as applicable, in:
1.
At least STARTUP within the next 6 hours6.944444e-5 days <br />0.00167 hours <br />9.920635e-6 weeks <br />2.283e-6 months <br />, 2.
At least HOT $HUTDOWN within the following 6 hours6.944444e-5 days <br />0.00167 hours <br />9.920635e-6 weeks <br />2.283e-6 months <br />, and 3.
At least COLD SHUTDOWN within the subsequent 24 hours2.777778e-4 days <br />0.00667 hours <br />3.968254e-5 weeks <br />9.132e-6 months <br />.
Where corrective measures are complet1d that permit operation nder 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 Limiting Condition for Operation.
Exceptions to these requirements are stated in the individual Specifications.
This Specification is not applicable in OPERATIONAL CONDITIONS 4 or 5.
3.0.4 Entry into an UPERATIONAL CONDITION 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 niet within a specified time interval.
Entry into an OPERATIONAL CONDITION or other specified condition may be made in act.ordance with the ACTION require-ments when conformance to them pennits continued operation of the f acility for an unlimited period of time.
This provision shall not prevent passage through or to OPERATIONAL CONDITIONS as required to comply with ACTION requirements.
Exceptions to these requirements are stated in the individual Specifications.
i l
i 9202280101 920211 PDR ADOCK 05000440 p
PDR PERRY - UNIT 1 3/4 0-1 Amendment No. 30
~
e APPLICABILITY SURVEllLANCE_ REQUIREMENTS
==
4.0.1 Surveillance Requirements shall be met during the OPERATIONAL COND11th or other conditions specified for individual Limiting Conditions for Operatico unless otherwise stated in an individual Surveillance Rsquirement.
4.0.2 Each Surveiliance Requirement shall be performed within the specified surveillance interval with a maximum allowable extension not to exceed 25 percent of the specified surveillance interval.
4.0.3 Failure to perform a Surveillance Requirement within the allowed surveil-lance interval, defined by Specification 4.0.2, shall constitute noncompliance with the OPERABILIT) requirements for a Limiting Condition for Operation.
The time limits of the ACfl0N requirements are applicable at the time it is identified that a Surveillance Requirement has not been performed.
The ACTION requirements may b's delayed for up to 24 hours2.777778e-4 days <br />0.00667 hours <br />3.968254e-5 weeks <br />9.132e-6 months <br /> to pennit the completion of the surveillance when the allowable outage time limits of the ACTION rcquirements are less than 24 h)urs.
Surveillance Requirements do not have to be performed on inoperable equi) ment.
4.0.4 Entry into an OPERATIONAL CONDITION or other specif bd applicable condi-tion shall not be made unless the Surveillance Requirement (s) associated with the Limiting Cono tion for Operation have been performed within the applicable surveillance interval or as otterwise specified.
This provision shall not prevent passage through or to OPERATIONAL COND!TIONS as required to comply with ACTION requirements.
4.0.5 Surveillance Requirements for inservice inspection and testing of ASME Code Class 1, 2, and 3 components shall be applicable as follows:
a.
Inservice inspection of ASME Code Class 1, 2, and 3 components and inservice testing of ASME Code Class 1, 2, and 3 pumps and valves shall be performed in accordance with Section XI of the ASME Boiler and Pressure Vessel Code and applicable Addenda as required by 10 CFR 50, Section 50.55a(g), except where specific written relief has been granted by the Comission pursuant to 10 CFR 50, Section 50.55a(g)(6)(i).
b.
Surveillance intervals specified-in Section XI of the ASME Boiler and Pressure Vessel Code and applicable Addenda for the inservice inspection and testing activities required by the ASME Boiler and Pressure Vessel Code and applicable Addends shall be applicable as follows in these Technical Specifications:
ASME Boiler and Pressure Vessel Required frequencies Code and applicable Addenda for perfonning inservice tenninology for inservice inspection and testing inspection-and testing activities activities Weekly At least once per 7 days Monthly At least once per 31 days Quarterly or every 3 months At least once per 92 days Semiannually or every 6 months At least once per 184 days Every 9 months At least once per 276 days Yearly or annually At least once per 366 days f
PERRY - UNIT 1 3/4 04 Amendment No. #, 29
3/4.0 APPLICABILITY BASES (Continued) time to reach COLD SHUTDOWN or other OPERATIONAL CONDITION, is not reduced.
For example, if STARTUP is reached in 2 hours2.314815e-5 days <br />5.555556e-4 hours <br />3.306878e-6 weeks <br />7.61e-7 months <br />, the time allowed to reach HOT SHUTDOWN is the next 11 hours1.273148e-4 days <br />0.00306 hours <br />1.818783e-5 weeks <br />4.1855e-6 months <br /> because the total time to reach HOT T,4U100WN is not reduced from the allowable limit of 13 hours1.50463e-4 days <br />0.00361 hours <br />2.149471e-5 weeks <br />4.9465e-6 months <br />.
Therefore, if remedial measures are completed that would pemit a return to POWER operation, a penalty is not incurred by having to reach a lower CONDITION of operation in less than the total time allowed.
The same principle applies with regard to the allowable outage time limits of the ACTION requirements, if compliance with the ACTION requirements for one specification results in entry into an OPERATIONAL CONDITION or condition of operation for another specification in which the requirements of the Limiting Condition for Operation are not met.
if the new specification becomes applicable in less time than specified, the difference may be added to the allowable Outage time limits of the second specification.
However, the allcwable outage time limits of ACTION requirements for a higher CONDITION of operation may not be used to extend the allowable outage time that is applicable when a Limiting Condition for Operation is not met in a lower CONDITION of operation.
The shutdown requirements of Specification 3.0.3 do not apply in eONDITIONS 4 and 5, because the ACTION requirements of individual specifications define the remedial reasures to be taken.
Specification 3.0.4 establishes limitations on a change in OPERATIONAL COND!TTDhT when a LimftTng Condition for Operation is not met.
It precludes placing the facility in a higher CONDITION of operation when the requirements for a Limiting Condition for Operation are not met and continued noncompliann.
to these conditions would result in a shutdown to comply with the ACTION requi e-ments if a change in CONDITIONS were pemitted. The purpose of this specificat 7n is to ensure that facility operation is not initiated or that higher CONDITIONS of operation are not entered when corrective action is being taken to obtain compliance with a specification by restoring equipment to OPERABLE status or parameters to specified limits.
Compliance with ACTION requirements that permit continued operation of the facility for an unlimited period of time provides an acceptable level of safety for continued operation without regard to the status of the plant before or af ter a change in OPERATIONAL CONDITIONS.
Therefore, in this case, entry into an OPERATIONAL CONDITION or other specified condition may be made in accordance with the provisions of the ACTION requirements. The provisions of this specification should not, however, be interpreted as endJrsing the failure to exercise good practice in restoring systems or components to OPERABLE status before plant startup.
When a shutdown is required to comply with ACTION requirements, the provi-sions of Specification 3.0.4 do not apply because they would delay placing the facility in a lower CONDITION of operation.
Specifications 4.0.1 through 4.0.5 establish the general requirements applicable to $urveillance Requirements. These requirements are based on the PERRY - UNIT 1 B 3/4 0 3 Amendment No. 30 I
1
3]4.0 APPLICABILITY B_ASES (Continued)
Surveillance Requirements stated in tro Code of Federal Regulations, 10 CFR 50.36(c)(3):
" Surveillance requirements are requirements relating to test, calibration, or inspection to ensure that the necessary quality of systems and components is maintained, that facility operation will be within safety limits, and that the limiting conditions of operation will be met."
Specification 4.0.1 establishes the requirement that surveillances must be performed during the OFTRATIONAL CONDITIONS or other conditions for which the requirements of the Limiting Conditiora for Operation apply unless otherwise stated in an individual Surveillance Requirement.
The purpose of this specifica-tion is to ensure that surveillances are performed to verify the operational status of systems ard components and that parameters are within sp?c4fied limits to ensure safe operation of the facility when the plant is in an OPERATIONAL CONDITION or other specified condition for which the individual Limiting Condi-(
tions for Operation are applicable.
Surveillance Requirements do not have to be perfurmed when the facility is in an OPERATIONAL CONDITION for which the require-ments of the associated Limiting Condition for Operation do not apply unless otherwise specified.
The Surveillance Requirements associated with a Special Test Exception are only applicable when the Special Test Exception is used as an allowable exception to the requirements of a specification.
S ecification 4.0.2 establishes the limit for which the specified time f
interval for Surveillance Requirements may be extended.
it pemits an allowable extension of the specified surveillance interval to facilitate surveillance scheduling and consideration of plant operating conditions that may not be suitable for conducting the surveillance; e.g., transient conditions or other ongoing surveillance or maintenance activities.
It also provides flexibility to accomodate the length of a fuel cycle for surveillances that are performed at each refueling outage and are specified with an 18 month surveillance interval.
It is not intended that this provision be used repeatedly as a convenience to extend surveillance intervals beyond that specified for surveillances that are not perfomed during refueling outages.
The limitation of Specification 4.0.2 is based on engineering judgment and the recognition that the most probable result of any particular surveillance being perfomed is the verification of confomance with the Surveillance Requirements.
This provision is sufficient to ensure that the reliability ensured through surveillance actsvities is not significantly degraded beyond that obtained from the specified surveillance interval.
Specification 4.0.3 establishes that the failure to perfom a Surveillance s Requirement within the allowed surveillsnce interval, dt'ined by the provisions of Specification 4.0.2. is a condition that constitutes a failure to meet the OPERABILITY requirements for a Limiting Condition for Ope' ration.
Under the
.)
provisions of this specification, systems and components are assumed to be OPERABLE when Surveillance Requirements have been satisfactorily perfomed within the specified time interval.
However, nothing in this provision is to be construed as implying that systems or components are OPERABLE when they are found or known to be inoperable although still meeting the Surveillance Requirements.
This specification also clarifies that the ACTION requirements are applicable when Surveillance Requirements have not been completed within the allowed surveil-lance interval and that the time limits of the ACTION requirements apply from the PERRY - UNIT 1 B 3/4 0-4 Amendment No. 39, 39