ML023230430

Tech Spec Pages for Millstone, Unit 3, Limiting Condition for Operation

ML023230430
Person / Time
Site:	Millstone
Issue date:	11/15/2002
From:	Office of Nuclear Reactor Regulation
To:
References
Download: ML023230430 (7)

Text

3/4 LIMITING CONDITIONS FOR OPERATION AND SURVEILLANCE REQUIREMENTS 3/4.0 APPLICABILITY LIMITING CONDITION FOR OPERATION 3.0.1 Compliance with the Limiting Conditions for Operation contained in the succeeding specifications is required during the OPERATIONAL MODES or other conditions specified therein; except that upon failure to meet the Limiting Conditions for Operation, the associated ACTION requirements shall be met, except as provided in Specification 3.0.5.

3.0.2 Noncompliance with a specification shall exist when the requirements of the Limiting Condition for Operation and associated ACTION requirements are not met within the specified time intervals, except as provided in Specification 3.0.5. If the Limiting Condition for Operation is restored prior to expiration of the specified time intervals, completion of the ACTION requirements is not required.

3.0.3 When a Limiting Condition for Operation is not met, except as provided in the associated ACTION requirements!, within 1 hour1.157407e-5 days <br />2.777778e-4 hours <br />1.653439e-6 weeks <br />3.805e-7 months <br /> action shall be initiated to place the unit in a MODE in which the specification does not apply by placing it, as applicable, in:

a. At least HOT STANDBY within the next 6 hours6.944444e-5 days <br />0.00167 hours <br />9.920635e-6 weeks <br />2.283e-6 months <br />,

b. At least HOT SHUTDOWN within the following 6 hours6.944444e-5 days <br />0.00167 hours <br />9.920635e-6 weeks <br />2.283e-6 months <br />, and

c. 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 completed that permit operation under 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 MODE 5 or 6.

3.0.4 Entry into an OPERATIONAL MODE or other specified condition shall not be made when the conditions for the Limiting Condition for Operation are not met and the associated ACTION requires a shutdown if they are not met within a specified time interval. Entry into an OPERATIONAL MODE or specified condition may be made in accordance with ACTION requirements when conformance to them permit continued operation of the facility for an unlimited period of time. This provision shall not prevent passage through or to OPERATIONAL MODES as required to comply with ACTION requirements. Exceptions to these requirements are stated in the individual specifications.

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 Specifications 3.0.1 and 3.0.2 for the system returned to service under administrative controls to perform the testing required to demonstrate OPERABILITY.

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 MILLSTONE - UNIT 3 3/4 0-1 Amendment No. 99, 97, 777, 213 0912

3Z4 LIMITING CONDITIONS FOR OPERATION AND SURVEILLANCE REQUIREMENTS 3/4.0 APPLICABILITY LIMITING CONDITION FOR OPERATION 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 time interval with a maximum allowable extension not to exceed 25% of the 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 Condition(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 Condition(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 requi rements.

d.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 Part 50, Section 50.55a;

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 Addenda shall be applicable as follows in these Technical Specifications:

0ILLSTONE 0912

- UNIT 3 3/4 0-2 Amendment No. ý9, 97, 179, 179, 213

APPLICABILITY LIMITING CONDITION FOR OPERATION (Continued)

ASME Boiler and Pressure Vessel Required frequencies for Code and applicable Addenda performing inservice terminology for inservice inspection and testing insDection and testina 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 Biennially or every 2 years At least once per 731 days

c. The provisions of Specification 4.0.2 are applicable to the above required frequencies for pe'rforming inservice inspection and testing activities;

d. Performance of the above inservice inspection and testing activities shall be in addition to other specified Surveillance Requirements; and

e. Nothing in the ASME Boiler and Pressure Vessel Code shall be construed to supersede the requirements of any Technical Specification.

MILLSTONE - UNIT 3 3/4 0-3 Amendment No. M P, 77, 77, 0912 J77, 213

3/4.0 APPLICABILITY S""BASES "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 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 will allow operation to proceed to a MODE or other specified condition where other necessary post maintenance tests can be completed.

MILLSTONE 0913

- UNIT 3 B 3/4 0-4 Amendment No. 97, 71,213

3/4.0 APPLICABILITY BASES Some examples of this process are:

a. Auxiliary feedwater (AFW) pump turbine maintenance during refueling that requires testing at steam pressure > 800 psi. 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.

b. High pressure safety injection (HPSI) maintenance during shutdown that requires system functional tests at a specified pressure. Provided other appropriate testing is satisfactorily completed, startup can proceed with HPSI considered OPERABLE. This allows operation to reach the specified pressure to complete the necessary post maintenance testing.

Specification 4.0.2 This specification 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 racilitate 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 typically 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 outage. The limitation of 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.

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 surveillance interval 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.

MILLSTONE - UNIT 3 B 3/4 0-5 Amendment No. ý7, 777, o013 gp, 213

3/4.0 APPLICABILITY

• JBASES 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 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 specified surveillance intervals for the 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 licensee's 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 entry into the ACTION requirements for the applicable Limiting Condition for Operation begins 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 Conditions for Operation begins 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 applicable ACTIONS, restores compliance with Specification 4.0.1.

MILLSTONE - UNIT 3 B 3/4 0-5a Amendment No. 213 0913

3/4.0 APPLICABILITY RASES Soecification 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 operatiop.

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 XI of the ASME Boiler and Pressure Vessel Code and Addenda as required by IOCFR50.55a. These requirements apply except when relief has been provided in writing by the Commission.

This specification includes a clarification of the frequencies for performing the inservice inspection and testing activities required by Section XI of the ASME Boiler and Pressure Vessel Code and 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 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 Boiler and Pressure Vessel Code provision which allows pumps and valves to be tested up to one week after return to normal operation. The Technical Specification definition of OPERABLE does not allow a grace period before a component, that is not capable of performing its specified function, is declared inoperable and takes precedence over the ASME Boiler and Pressure Vessel Code provision which allows a valve to be incapable of performing its specified function for up to 24 hours2.777778e-4 days <br />0.00667 hours <br />3.968254e-5 weeks <br />9.132e-6 months <br /> before being declared inoperable.

MILLSTONE - UNIT 3 B 3/4 0-6 Amendment No. P7,213 0913