ML031360582
| ML031360582 | |
| Person / Time | |
|---|---|
| Site: | Seabrook  |
| Issue date: | 05/15/2003 |
| From: | NRC/NRR/DLPM |
| To: | |
| References | |
| TAC MB4749 | |
| Download: ML031360582 (7) | |
Text
APPLICABILITY SURVEILLANCE REQUIREMENTS 4.0.1 Surveillance Requirements shall be met during the OPERATIONAL MODES or other conditions specified for individual Limiting Conditions for Operation unless otherwise stated in an individual Surveillance Requirement. 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 Limiting Condition for Operation. Failure to perform a Surveillance within the specified surveillance interval shall be failure to meet the Limiting Condition for Operation except as provided in Specification 4.0.3. Surveillances do not have to be performed on inoperable equipment or variables outside specified limits.
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 surveillance interval, then compliance with the requirement to declare the Limiting Condition for Operation 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 surveillance interval, 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 Limiting Condition for Operation 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 Limiting Condition for Operation 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 has 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 shall be performed in accordance with Section Xi of the ASME Boiler and Pressure Vessel Code and applicable Addenda as required by 10 CFR Part 50, Section 50.55a(g), except where specific written relief has been granted by the Commission pursuant to 10 CFR Part 50, Section 50.55a(g)(6)(i).
Inservice testing of ASME Code Class 1, 2, and 3 components shall be performed in accordance with the Code for Operation and Maintenance of Nuclear Power Plants (ASME OM Code) and applicable Addenda as required by 10 CFR Part 50, Section 50.55a(f), except where specific written relief has been granted by the Commission pursuant to 10 CFR Part 50, Section 50.55a(f)(6)(i).
SEABROOK - UNIT 3/4 0-2 Amendment No. 69, 87
3/4.0 APPLICABILITY BASES Specification 4.0.1 establishes the requirement that surveillances must be met during the OPERATIONAL MODES or other conditions for which the requirements of the Limiting Conditions for Operation apply unless otherwise stated in an individual Surveillance Requirement. The purpose of this specification is to ensure that surveillances are performed to verify the OPERABILITY of systems and components and that parameters are within specified limits to ensure safe operation of the facility when the plant is in a MODE or other specified condition for which the associated Limiting Conditions for Operation are applicable. Failure to meet a Surveillance within the specified surveillance interval, in accordance with Specification 4.0.2, constitutes a failure to meet a Limiting Condition for Operation.
Systems and components are assumed to be OPERABLE when the associated Surveillance Requirements have been met. Nothing in this Specification, however, is to be construed as implying that systems or components are OPERABLE when either:
- a. The systems or components are known to be inoperable, although still meeting the Surveillance Requirements or
- b. The requirements of the Surveillance(s) are known to be not met between required Surveillance performances.
Surveillance requirements do not have to be performed when the facility is in an OPERATIONAL MODE or other specified conditions for which the requirements 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.
Unplanned events may satisfy the requirements (including applicable acceptance criteria) for a given Surveillance Requirement. In this case, the unplanned event may be credited as fulfilling the performance of the Surveillance Requirement. This allowance includes those Surveillance Requirement(s) whose performance is normally precluded in a given MODE or other specified condition.
Surveillance Requirements, including Surveillances invoked by ACTION requirements, do not have to be performed on inoperable equipment because the ACTIONS define the remedial measures that apply. Surveillances have to be met and performed in accordance with Specification 4.0.2, prior to returning equipment to OPERABLE status.
Upon completion of maintenance, appropriate post maintenance testing is required to declare equipment OPERABLE. This includes ensuring applicable Surveillances are not failed and their most recent performance is in accordance with Specification 4.0.2.
Post maintenance testing may not be possible in the current MODE or other specified conditions in the Applicability due to the necessary unit parameters not having been established. In these situations, the equipment may be considered OPERABLE provided testing has been satisfactorily completed to the extent possible and the equipment is not otherwise believed to be incapable of performing its function. This SEABROOK - UNIT 1 B 3/4 0-4 Amendment No. 7
3/4.0 APPLICABILITY BASES will allow operation to proceed to a MODE or other specified condition where other necessary post maintenance tests can be completed. An example of this process:
Emergency feedwater (EFW) pump turbine maintenance during refueling that requires testing at steam pressure > 500 psig. However, if other appropriate testing is satisfactorily completed, the AFW System can be considered OPERABLE. This allows startup and other necessary testing to proceed until the plant reaches the steam pressure required to perform the testing.
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 judgement 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.
Specification 4.0.3 establishes the flexibility to defer declaring affected equipment inoperable or an affected variable outside the specified limits when a Surveillance has not been completed within the specified surveillance interval. 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 surveillance interval, whichever is greater, applies from the point in time that it is discovered that the Surveillance has not been performed in accordance with Specification 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 ACTION requirements 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 surveillance interval based not on time intervals, but upon specified unit conditions, operating situations, or requirements of regulations (e.g., prior to entering MODE I 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 SEABROOK - UNIT 1 B 3/4 0-5 Amendment No. 87
3/4.0 APPLICABILITY BASES when specified, Specification 4.0.3 allows for the full delay period of up to the specified surveillance interval to perform the Surveillance. However, since there is not a time interval specified, the missed Surveillance should be performed at the first reasonable opportunity.
Specification 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 ACTION requirements.
Failure to comply with the specified surveillance intervals for Surveillance Requirements is expected to be an infrequent occurrence. Use of the delay period established by Specification 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 surveillance interval 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 the 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 implementation 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 entry into the ACTION requirements for the applicable Limiting Condition for Operation 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 outside the specified limits and entry into the ACTION requirements for the applicable Limiting Condition for Operation conditions begin immediately upon the failure of the Surveillance.
Completion of the Surveillance within the delay period allowed by this Specification, or within the Allowed Outage time of the ACTIONS, restores compliance with Specification 4.0.1.
SEABROOK - UNIT 1 B 3/4 0-6 Amendment No. 6§, 7
3/4.0 APPLICABILITY BASES Specification 4.0.4 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.
Under the provisions 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.
Specification 4.0.5 establishes the requirement that 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 a periodically updated version of Section Xl of the ASME Boiler and Pressure Vessel Code and the ASME OM Code including applicable Addenda as required by 10 CFR 50.55a. These requirements apply except when relief has been provided inwriting by the Commission.
This specification includes a clarification of the frequencies for performing the inservice inspection and testing activities required by Section Xl of the ASME Boiler and Pressure Vessel Code and the ASME OM Code including applicable Addenda. This clarification is provided to ensure consistency in surveillance intervals throughout the Technical Specifications and to remove any ambiguities relative to the frequencies for performing the required inservice inspection and testing activities.
Under the terms of this specification, the more restrictive requirements of the Technical Specifications take precedence over the ASME Boiler and Pressure Vessel Code and the ASME OM Code including applicable Addenda. The requirements of Specification 4.0.4 to perform surveillance activities before entry into an OPERATIONAL MODE or other specified condition takes precedence over the ASME OM Code provision which allows pumps that can only be tested during plant operation to be tested within 1 week following plant startup.
SEABROOK - UNIT I B 3/4 0-7 Amendment No. 1.17
ADMINISTRATIVE CONTROLS PROCEDURES AND PROGRAMS 6.7.6 (Continued)
- j. Technical Sp ecification (TS) Bases Control Program This program provides a means for processing changes to the Bases of these Technical Specifications.
- a. Changes to the Bases of the TS shall be made under appropriate administrative controls and reviews.
- b. Licensees may make changes to Bases without prior NRC approval provided the changes do not require either of the following:
- 1. A change in the TS incorporated in the license or
- 2. A change to the updated FSAR (UFSAR) or Bases that requires NRC approval pursuant to 10 CFR 50.59.
- c. The Bases Control Program shall contain provisions to ensure that the Bases are maintained consistent with the UFSAR.
- d. Proposed changes that meet the criteria of Specification 6.7.6j.b above shall be reviewed and approved by the NRC 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).
6.8 REPORTING REQUIREMENTS ROUTINE REPORTS 6.8.1 In addition to the applicable reporting requirements of Title 10, Code of Federal Regulations, the following reports shall be submifted to the Regional Administrator of the Regional Office of the NRC unless otherwise noted.
STARTUP REPORT 6.8.1.1 A summary report of station startup and power escalation testing shall be submitted following: (1) receipt of an Operating License, (2) amendment to the license involving a planned increase in power level, (3) installation of fuel that has a different design or has been manufactured by a different fuel supplier, and (4) modifications that may have significantly altered the nuclear, thermal, or hydraulic performance of the station.
SEABROOK - UNIT 1 6-1 4D Amendment No. 34- 6 97
May 15, 2003 M.Warner A copy of the related Safety Evaluation is also enclosed. Notice of Issuance will be included in the Commission's biweekly Federal ReQister notice.
Sincerely,
/RA/
Victor Nerses, Sr. Project Manager, Section 2 Project Directorate I Division of Licensing Project Management Office of Nuclear Reactor Regulation Docket No. 50-443
Enclosures:
- 1. Amendment No. 87 to NPF-86
- 2. Safety Evaluation cc w/encls: See next page DISTRIBUTION:
PUBLIC VNerses GHill(2)
PDI-2 Rdg. CRaynor RDennig SRichards OGC DJaffe JClifford ACRS BMcDermott, RGN-I ADAMS Accession Numbers: ML022000461, TS(s): ML , Package: ML
- See Drevious concurrence.
OFFICE PDI-2/PM PDI- / OGC* RORP/SC* PDIV-1/PM* PDI-2/SC NAME Wrsl CRayhor RWeisman RDennig DJaffe J
.DATE ViO53 l 105 I I 3/3/03 1/21/03 1/21/03 ;i a3 J OFFICIAL RECORD COPY