ML031950320
ML031950320 | |
Person / Time | |
---|---|
Site: | Summer |
Issue date: | 07/11/2003 |
From: | NRC/NRR/DLPM |
To: | |
References | |
TAC MB6522 | |
Download: ML031950320 (5) | |
Text
APPLICABILITY SURVEILLANCE REQUIREMENTS 4.0.1 Surveillance Requirements shall be applicable during the OPERATIONAL MODES or other conditions specified for individual Limiting Conditions for Operation unless otherwise stated in an individual Surveillance Requirement.
4.0.2 Each Surveillance 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 If it is discovered that a Surveillance was not performed within its specified frequency, as defined by Specification 4.0.2, 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 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 hours2.777778e-4 days <br />0.00667 hours <br />3.968254e-5 weeks <br />9.132e-6 months <br /> 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 Action(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 Action(s) must be entered.
4.0.4 Entry into an OPERATIONAL MODE or other specified condition shall not be made unless the Surveillance Requirement(s) associated with the Limiting Condition for Operation have been performed within the stated surveillance interval or as otherwise specified. This provision shall not prevent passage through or to OPERATIONAL MODES 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 Section Xl 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 Commission pursuant to 10 CFR 50, Section 50.55a(g)(6)(i).
- b. Surveillance intervals specified in Section Xl 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 Addenda shall be applicable as follows in these Technical Specifications:
SUMMER - UNIT 1 3/4 0-2 Amendment No63
APPLICABILITY BASES 4.0.1 This specification provides that surveillance activities necessary to insure the Limiting Conditions for Operation are met and will be performed during the OPERATIONAL MODES or other conditions for which the Limiting Conditions for Operation are applicable.
Provisions for additional surveillance activities to be performed without regard to the applicable OPERATIONAL MODES or other conditions are provided in the individual Surveillance Requirements. Surveillance Requirements for Special Test Exceptions need only be performed when the Special Test Exception is being utilized as an exception to an individual specification.
4.0.2 Specification 4.0.2 establishes the limit for which the specified time interval for Surveillance Requirements may be extended. It permits an allowable extension of the normal 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 accommodate 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 performed 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 performed is the verification of conformance with the Surveillance Requirements. This provision is sufficient to ensure that the reliability ensured through surveillance activities is not significantly degraded beyond that obtained from the specified surveillance interval.
4.0.3 Surveillance Requirement (SR) 4.0.3 establishes the flexibility to defer declaring affected equipment inoperable or an affected variable outside their specified limits when a surveillance has not been completed within the specified frequency. A delay period of 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 greater, applies from the point in time that it is discovered that the surveillance has not been performed in accordance with SR 4.0.2 and not at the time that the specified frequency was not met.
This delay period provides adequate time to complete surveillances that have been missed. This delay period permits the completion of a surveillance before complying with required Actions or other remedial measures that might preclude completion of the surveillance.
The basis for this delay period includes consideration of unit conditions, adequate planning, availability of personnel, the time required to perform the surveillance, the safety significance of the delay in completing the required surveillance, and the recognition that the most probable result of any particular surveillance being performed is the verification of conformance with the requirements.
When a surveillance with a frequency based not on time intervals, but upon specified unit conditions, operating situations, or requirements of regulations (e.g., prior to entering MODE 1 after each fuel loading, or in accordance with 10 CFR 50, Appendix J, as modified by approved exemptions, etc.) is discovered to not have been performed when specified, SR 4.0.3 allows for the full delay period up to the specified frequency to perform the surveillance.
However, since there is not a time interval specified, the missed surveillance should be performed at the first reasonable opportunity.
SUMMER - UNIT 1 B 3/4 0-2 Amendment No. 163
APPLICABILITY BASES SR 4.0.3 provides a time limit for, and allowances for the performance of, surveillances that become applicable as a consequence of MODE changes imposed by required Actions.
Failure to comply with specified frequencies for SRs is expected to be an infrequent occurrence. Use of the delay period established by SR 4.0.3 is a flexibility, which is not intended to be used as an operational convenience to extend surveillance intervals.
While up to 24 hours2.777778e-4 days <br />0.00667 hours <br />3.968254e-5 weeks <br />9.132e-6 months <br /> or the limit of the specified frequency is provided to perform the missed surveillance, it is expected that the missed surveillance will be performed at the first reasonable opportunity. The determination of first reasonable opportunity should include consideration of the impact on plant risk (from delaying the surveillance as well as any plant configuration changes required or shutting the plant down to perform the surveillance) and impact on any analysis assumptions, in addition to unit conditions, planning, availability of personnel, and the time required to perform the surveillance. This risk impact should be managed through the program in place to implement 10 CFR 50.65(a)(4) and its implementing guidance, NRC Regulatory Guide 1.182, "Assessing and Managing Risk Before Maintenance Activities at Nuclear Power Plants." This Regulatory Guide addresses consideration of temporary and aggregate risk impacts, determination of risk management action thresholds, and risk management action up to and including plant shutdown. The missed surveillance should be treated as an emergent condition as discussed in the Regulatory Guide. The risk evaluation may use quantitative, qualitative, or blended methods.
The degree of depth and rigor of the evaluation should be commensurate with the importance of the component. Missed surveillances for important components should be analyzed quantitatively. If the results of the risk evaluation determine the risk increase is significant, this evaluation should be used to determine the safest course of action. All missed surveillances will be placed in the Corrective Action Program.
If a surveillance is not completed within the allowed delay period, then the equipment is considered inoperable or the variable is considered outside the specified limits and the Allowed Outage Time (AOT) for the required Action for the applicable LCO conditions begin immediately upon expiration of the delay period. If a surveillance is failed within the delay period, then the equipment is inoperable, or the variable is considered outside the specified limits and the AOT of the required Action for the applicable LCO begin immediately upon the failure of the surveillance.
Completion of the surveillance within the delay period allowed by this specification, or within the AOT of the Action, restores compliance with SR 4.0.1.
4.0.4 This specification establishes the requirement that all applicable surveillances must be met before entry into an OPERATIONAL MODE or other condition of operation specified in the Applicability statement. The purpose of this specification is to ensure that system and component OPERABILITY requirements or parameter limits are met before entry into a MODE or condition for which these systems and components ensure safe operation of the facility. This provision applies to changes in OPERATIONAL MODES or other specified conditions associated with plant shutdown as well as startup.
SUMMER - UNIT 1 B 3/4 0-2a Amendment No. 163
APPLICABILITY BASES Under the provision of this specification, the applicable Surveillance Requirements must be performed within the specified surveillance interval to ensure that the Limiting Conditions for Operation are met during initial plant startup or following a plant outage.
When a shutdown is required to comply with ACTION requirements, the provisions of Specification 4.0.4 do not apply because this would delay placing the facility in a lower MODE of operation.
Under the terms of this specification, for example, during initial plant startup or following extended plant outages, the applicable surveillance activities must be performed within the stated surveillance interval prior to placing or returning the system or equipment into OPERABLE status.
SUMMER - UNIT 1 B 3/4 0-2b Amendment No. 163 S
ADMINISTRATIVE CONTROLS Technical Specifications (TS) Bases Control Program This program provides a means for processing changes to the Bases of these Technical Specifications.
- 1. Changes to the Bases shall be made under appropriate administrative control and reviews.
- 2. Licensees may make changes to Bases without prior NRC approval provided the changes do not require either of the following:
a) A change in the TS incorporated in the license or b) A change to the updated FSAR or bases that requires NRC approval pursuant to 10 CFR 50.59.
- 3. The Bases Control Program shall contain provisions to insure that the Bases are maintained consistent with the FSAR.
- 4. Proposed changes that meet the criteria of Specification 6.8.4.i.2.b above shall be reviewed and approved prior to implementation. Changes to the Bases implemented without prior NRC approval shall be provided to the NRC on a frequency consistent with 10 CFR 50.71(e).
SUMMER - UNIT 1 6-12d Amendment No. i63