ML072610197

From kanterella
Jump to navigation Jump to search

Technical Specifications, Adoption of Technical Specification Task Force (TSTF) Change TSTF-372, the Addition of Limiting Condition for Operation (LCO) 3.0.8 on the Inoperability of Snubbers
ML072610197
Person / Time
Site: Pilgrim
Issue date: 09/18/2007
From:
Plant Licensing Branch III-2
To:
kim J, NRR/ADRO/DORL, 415-4125
References
TAC MD3579
Download: ML072610197 (3)


Text

B. Technical Specifications The Technical Specifications contained in Appendix A, as revised through Amendment No.229 are hereby incorporated in the license. The licensee shall operate the facility in accordance with the Technical Specifications.

C. Records ENO shall keep facility operating records in accordance with the requirements of the Technical Specifications.

D. Equalizer Valve Restriction - DELETED E. Recirculation Loop Inoperable - DELETED F. Fire Protection ENO shall implement and maintain in effect all provisions of the approved fire protection program as described in the Final Safety Analysis Report for the facility and as approved in the SER dated December 21, 1978 as supplemented subject to the following provision:

ENO may make changes to the approved fire protection program without prior approval of the Commission only ifthose changes would not adversely affect the ability to achieve and maintain safe shutdown in the event of a fire.

G. Physical Protection The licensee shall fully implement and maintain in effect all provisions of the Commission-approved physical security, training and qualification, and safeguards contingency plans including amendments made pursuant to provisions of the Miscellaneous Amendments and Search Requirements revisions to 10 CFR73.55 (51 FR27817 and 27822) and to the authority of 10 CFR 50.90 and 10 CFR 50.54(p). The combined set of plans, which contain Safeguards Information protected under 10 CFR 73.21, is entitled: "Pilgrim Nuclear Power Station Physical Security, Training and Qualification, and Safeguards Contingency Plan, Revision 0" submitted by letter dated October 13, 2004, as supplemented by letter dated May 15, 2006.

Anencdnent 229

3.0 LIMITING CONDITION FOR OPERATION (LCO) APPLICABILITY 3.0.1 Not Used 3.0.2 Not Used 3.0.3 Not Used 3.0.4 Not Used 3.0.5 Not Used 3.0.6 Not Used 3.0.7 Special Operations LCOs in Section 3.14 allow specified Technical Specifications requirements to be changed to permit performance of special tests and operations. Unless otherwise specified, all other Technical Specification requirements remain unchanged. Compliance with Special Operations LCOs is optional. When a Special Operations LCO is desired to be met but is not met, the ACTIONS of the Special Operations LCO shall be met. When a Special Operations LCO is not desired to be met, entry into a Mode or other specified condition in the Applicability shall only be made in accordance with the other applicable Specifications.

3.0.8 When one or more required snubbers are unable to perform their associated support function(s), any affected supported LCO(s) are not required to be declared not met solely for this reason if risk is assessed and managed, and:

a. the snubbers not able to perform their associated support function(s) are associated with only one train or subsystem of a multiple train or subsystem supported system or are associated with a single train or subsystem supported system and are able to perform their associated support function within 72 hours8.333333e-4 days <br />0.02 hours <br />1.190476e-4 weeks <br />2.7396e-5 months <br />; or
b. the snubbers not able to perform their associated support function(s) are associated with more than one train or subsystem of a multiple train or subsystem supported system and are able to perform their associated support function within 12 hours1.388889e-4 days <br />0.00333 hours <br />1.984127e-5 weeks <br />4.566e-6 months <br />.

At the end of the specified period the required snubbers must be able to perform their associated support function(s), or the affected supported system LCO(s) shall be declared not met.

Amendment 249- 2-4-, 22-9 3/4.0-1

I . a 4.0 SURVEILLANCE REQUIREMENT (SR) APPLICABILITY 4.0.1 Not Used 4.0.2 Not Used 4.0.3 If it is discovered that a Surveillance was not performed within its specified Surveillance Frequency, 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 Surveillance 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 Condition(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 Condition(s) must be entered.

Amendment 2W2-4-l , 229 3/4.0-2 .1