ML030910272

Tech Spec Amendment No. 145 for Hope Creek

ML030910272
Person / Time
Site:	Hope Creek
Issue date:	03/31/2003
From:	NRC/NRR/DLPM
To:
References
Download: ML030910272 (6)

Text

APPLICABILITY SURVEILLANCE REQUIREMENTS 4.0.1 Surveillance Requirements shall be met during the OPERATIONAL CONDITIONS or other specified conditions in the Applicability for individual Limiting Conditions for Operation, unless otherwise stated in the 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 frequency shall be a 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 its 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, 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 hours1 days <br />0.143 weeks <br />0.0329 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 hours1 days <br />0.143 weeks <br />0.0329 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 Actions 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 Actions must be entered.

4.0.4 Entry into an OPERATIONAL CONDITION or other specified applicable condition shall not be made unless the Surveillance Requirement(s) associated with the Limiting Condition for Operation have been performed within the applicable surveillance interval or as otherwise specified. This provision shall not prevent passage through or to OPERATIONAL CONDITIONS as required to comply with ACTION requirements.

4.0.5 Surveillance Requirements for inservice inspection and testing of ASME Code Class 1, 2, & 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 Sections 50.55a(f) and 50.55a(g), except where specific written relief has been granted by the Commission pursuant to 10 CFR 50, Section 50.55a(f)(6)(i) or 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 HOPE CREEK 3 /4 0-2 Amendment No. 145

ADMINISTRATIVE CONTROLS 6.13 PROCESS CONTROL PROGRAM (PCP)

Changes to the PCP:

a. Shall be documented and records of reviews performed shall be retained as required by Specification 6.10.3.n. This documentation shall contain:

(1) Sufficient information to support the change together with the appropriate analyses or evaluations justifying the changes(s) and (2) A determination that the change will maintain the overall conformance of the solidified waste product to existing requirements of Federal, State, or other applicable regulations.

b. Shall become effective after review and acceptance by the SORC and the approval of the Plant General Manager.

6.14 OFFSITE DOSE CALCULATION MANUAL (ODCM)

Changes to the ODCM:

a. Shall be documented and records of reviews performed shall be retained as required by Specification 6.10.3.n. This documentation shall contain:

1) Sufficient information to support the change together with the appropriate analyses or evaluations justifying the changes(s) and

2) A determination that the change will maintain the level of radioactive effluent control required by 10 CFR 20.106, 40 CFR Part 190, 10 CFR 50.36a, and Appendix I to 10 CFR Part 50 and not adversely impact the accuracy or reliability of effluent, dose, or setpoint calculations.

b. Shall become effective after review and acceptance by the SORC and the approval of the Plant General Manager.

c. Shall be submitted to the Commission in the form of a complete, legible copy of the entire ODCM as a part of or concurrent with the Annual Radioactive Effluent Release Report for the period of the report in which any change to the ODCM was made. Each change shall be identified by markings in the margin of the affected pages, clearly indicating the area of the page that was changed, and shall indicate the date (e.g., month/year) the change was implemented.

HOPE CREEK 6-25 Amendment No- 145

ADMINISTRATIVE CONTROLS 6.15 TECHNICAL SPECIFICATION (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. PSEG may make changes to the 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 or Bases that requires NRC approval pursuant to 10 CFR 50.59.

c. Proposed changes to the Bases that require either condition of Specification 6.15.b above shall be reviewed and approved by the NRC prior to implementation.

d. 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).

e. The Bases Control Program shall contain provisions to ensure that the Bases are maintained consistent with the UFSAR.

REFERENCES

1. CENPD-300-P-A, "reference Safety Report for Boiling Water Reactors Reload Fuel," (latest approved revision)

2. NEDE-24011-P-A (latest approved revision), "General Electric Standard Application for Reactor Fuel (GESTAR-II)"

HOPE CREEK 6-26 Amendment No. 145

3/4.0 APPLICABILITY BASES (Con't)

Specifications 4.0.1 through 4.0.5 establish the general requirements applicable to Surveillance Requirements. These requirements are based on the Surveillance Requirements stated in the 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 Surveillance Requirements must be met during the OPERATIONAL CONDITIONS or other specified conditions in the Applicability for which the requirements of the Limiting Conditions for Operation apply unless otherwise specified in an individual Surveillance Requirement. This specification is to ensure that surveillances are performed to verify the OPERABILITY of systems and components and that variables are within specified limits. Failure to meet a Surveillance within the specified Frequency, in accordance with Specification 4.0.2, constitutes a failure to meet an LCO.

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.

Surveillances do not have to be performed when the facility is in an OPERATIONAL CONDITION or other specified condition 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. In this case, the unplanned event may be credited as fulfilling the performance of the Surveillance Requirement. This allowance includes those Surveillances whose performance is normally precluded in a given OPERATIONAL CONDITION or other specified condition.

Surveillances, including Surveillances invoked by ACTIONS, 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 OPERATIONAL CONDITION 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 HOPE CREEK B 3/4 0-4 Amendment No.-145

3/4.0 APPLICABILITY BASES (Con't) the equipment is not otherwise believed to be incapable of performing its function. This will allow operation to proceed to an OPERATIONAL CONDITION or other specified condition where other necessary post maintenance tests can be completed.

Some examples of this process are:

a. Control Rod Drive maintenance during refueling that requires scram testing at > 950 psig. However, if other appropriate testing is satisfactorily completed and the scram time testing of TS 4.1.3.2 is satisfied, the control rod can be considered OPERABLE. This allows startup to proceed to reach 950 psig to perform other necessary testing.

b. High Pressure Coolant Injection (HPCI) maintenance during shutdown that requires system functional tests at a specified pressure. Provided other appropriate testing is satisfactorily completed, startup can proceed with HPCI considered OPERABLE. This allows operation to reach the specified pressure to complete the necessary post maintenance 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 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 frequency. A delay period of up to 24 hours1 days <br />0.143 weeks <br />0.0329 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 TS 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.

HOPE CREEK B 3/4 0-4a Amendment No. 145

3/4 .0 APPLICABILITY BASES (Con't)

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 10CFR50 Appendix J, as modified by approved exemptions, etc.)

is discovered not to have been performed when specified, SR 4.0.3 allows the full delay period of 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.

SR 4.0.3 also 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 Surveillances 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 hours1 days <br />0.143 weeks <br />0.0329 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 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 CFR50.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 Completion Times of the Required Actions for the applicable LCO 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 the Completions Times of the Required Actions for the applicable LCO begins immediately upon the failure of the Surveillance.

Completion of the Surveillance within the delay period allowed by this Specification, or within the Completion Time of the Actions, restores compliance with SR 4.0.1.

Specification 4.0.4 establishes the requirement that all applicable surveillances must be met before entry into an OPERATIONAL CONDITION or other HOPE CREEK B 3/4 0-5 Amendment No. 145