ML070790397

Tech Spec Pages for Amendments 235 and 231 Regarding Snubbers, TSTF-372, Rev. 4

ML070790397
Person / Time
Site:	Catawba
Issue date:	03/19/2007
From:	NRC/NRR/ADRO/DORL/LPLII-1
To:
Shared Package
ML063100424	List: ML063100443 ML070790397
References
TAC MD1785, TAC MD1786
Download: ML070790397 (8)

Text

(2) Technical Spe*cations The Technical Soecifications contained InAppendix A, as revised through Amendment No 235 which are attached hereto, are hereby Incorporated indo this renewed operating license. Duke Power Company LLC shall operate the facility inaccordance with the Technical Specifications.

(3) Updated Firmnl Safety Analysis Report The Updated Final Safety Analysis Report supplement submitted pursuani to 10 CFR 54.21(d), as revised on December 16, 2002, describes certain future activities to be completed before the period of extended operation. Duke shall complete these activities no later than December 6, 2024, and shall notify the NRC In writing when Implementation of these activities Is complete end can be verified by NRC Inspection.

The Updated Final Safety Analysis Report supplement as revised on December 16, 2002, described above, shal be Included Inthe next scheduled update to the Updated Final Safety Analysis Report required by 10CFR 50.71(eX4), following issuance of this renewed operating license. Until that update is complete, Duke may make changes to the programs described in such supplement without prior Commission approval, provided that Duke evaluates each such change pursuant to the criteria set forth In 10 CFR 50.59 and otherwise complies with the requrements In that section.

(4) Antitrust Conditios Duke Power Company LLC shall comply with the antitrust conditions delineated In Appendix C to this renewed operating license.

(5) Fire Protection Probram (Section 9.5.1, SER, SSER#2,SSER#3,SSER#4, SSER#S)*

Duke Power Company LLC shall Implerment and maintain ineffect d provisions of the approved fire protection program as described Inthe Updated Final Safety Analysis Report, as amended, for the facility and as approved In the SER through Supplement 5, subject to the following provision:

The licensee 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 inthe event of a fire.

• The parenthetical notation following the title of tits renewed operating license condition denotes the section of the Safety Evak.,ton Report ndlor Its supplement wherein tfis renewed license conditI~n Is discussed.

Renewed License No. NPFI35 Amendment No., 235

(2) Technical Soeclfications The Technical Snpdlflcations contained inAppendix A, as revised through Amendment Nc 231 whkih are attached hereto, are herebyincorporated Into this renewed operating license. Duke Power Company LLC shal operate the facility In accordance with the Technical Specifications.

(3) Uodated Final Safety Analysis Re=r The Updated Final Safety Analysis Report supplement suibmfted pursuant to 10 CFR 54.21(d). as revised on December 16, 2002. describes certain future activities to be completed before the period of extended operafto Duke shall complete these activities no later than February 24, 2026, and shall notiry the NRC in writing when Implementation of these actives is comnplete and can be veriFied by NRC Inspection.

The Updated Final Safety Analysis Report supplement as revised on December 16,2002, described above, shall be Included inthe next scheduled update to the Updated Final Safety Analybsi Report required by 10 CFR 60.71 (eX4), following Issuance of this renewed operating license. Until that update Is complete, Duke may make changes to the programs described insuch supplement without prior Commission approval. prov~ded.ftdt Duke evaluates each such change pursuant to the criteria set forth In 10 CFR 50.59 and otherwise complies with the requirements In that setionL (4) Atust Conditioms Duke Power Company LLC shall comply with the antitrust conditions delineated Iin Appendix C to this renewed operating license.

(5) Fire Protection Program (Section 8.5.1, SER, SSER #2, SSER #3, SSER #4, SSER#5)"

Duke Power Company LLC shfit Implement and maintaln In effect all provisions of the approved fire protection program as described Inthe Updated Final Safety Anrlysis Report, as amended, for the facility and as approved in Ihe SER through Supplement 5. sutject to the following provision:

The licensee may make changes to the approved fire protection program without prior approval of Me Conunisslon only Ifthose changes would not adversely affect the ability to achileve and maintain safe shtdlown Inthe event of a fre.

T'he parenthetical notation following the title of this renewed operating license condition denotes the section of the Safety Evaluation Report end/or Its supplements wherein this renewed license conddion Is d'Iscussed.

Renewed License No. NPF-62 Amendment No 231

LCO Applicability 3.0 3.0 LIMITING CONDITION FOR OPERATION (LCO) APPLICABILITY LCO 3.0.1 LCOs shall be met during the MODES or other specified conditions in the Applicability, except as provided in LCO 3.0.2, 3.0.7, and 3.0.8.

LCO 3.0.2 Upon discovery of a failure to meet an LCO, the Required Actions of the associated Conditions shall be met, except as provided in LCO 3.0.5 and LCO 3.0.6.

If the LCO is met or is no longer applicable prior to expiration of the specified Completion Time(s), completion of the Required Action(s) is not required unless otherwise stated.

LCO 3.0.3 When an LCO is not met and the associated ACTIONS are not met, an associated ACTION is not provided, or if directed by the associated ACTIONS, the unit shall be placed in a MODE or other specified condition in which the LCO is not applicable. Action shall be initiated within 1 hour1.157407e-5 days <br />2.777778e-4 hours <br />1.653439e-6 weeks <br />3.805e-7 months <br /> to place the unit, as applicable, in:

a. MODE 3 within 7 hours8.101852e-5 days <br />0.00194 hours <br />1.157407e-5 weeks <br />2.6635e-6 months <br />;

b. MODE 4 within 13 hours1.50463e-4 days <br />0.00361 hours <br />2.149471e-5 weeks <br />4.9465e-6 months <br />; and

c. MODE 5 within 37 hours4.282407e-4 days <br />0.0103 hours <br />6.117725e-5 weeks <br />1.40785e-5 months <br />.

Exceptions to this Specification are stated in the individual Specifications.

Where corrective measures are completed that permit operation in accordance with the LCO or ACTIONS, completion of the actions required by LCO 3.0.3 is not required.

LCO 3.0.3 is only applicable in MODES 1, 2, 3, and 4.

(continued)

Catawba Units 1 and 2 3.0-1 Amendment Nos. 235, 231

LCO Applicability 3.0 3.0 LCO APPLICABILITY (continued)

LCO 3.0.4 When an LCO is not met, entry into a MODE or other specified condition in the Applicability shall only be made:

a. When the associated ACTIONS to be entered permit continued operation in the MODE or other specified condition in the Applicability for an unlimited period of time; or

b. After performance of a risk assessment addressing inoperable systems and components, consideration of the results, determination of the acceptability of entering the MODE or other specified condition in the Applicability, and establishment of risk management actions, if appropriate; exceptions to this Specification are stated in the individual Specifications; or

c. When an allowance is stated in the individual value, parameter, or other Specification.

This Specification shall not prevent changes in MODES or other specified conditions in the Applicability that are required to comply with ACTIONS or that are part of a shutdown of the unit.

LCO 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 LCO 3.0.2 for the system returned to service under administrative control to perform the required testing to demonstrate OPERABILITY.

LCO 3.0.6 When a supported system LCO is not met solely due to a support system LCO not being met, the Conditions and Required Actions associated with this supported system are not required to be entered. Only the support system LCO ACTIONS are required to be entered. This is an exception to LCO 3.0.2 for the supported system. In this event, additional evaluations and limitations may be required in accordance with Specification 5.5.15, "Safety Function Determination Program (SFDP)."

If a loss of safety function is determined to exist by this program, the appropriate Conditions and Required Actions of the LCO in which the loss of safety function exists are required to be entered.

When a support system's Required Action directs a supported system to be declared inoperable or directs entry into Conditions and Required Actions for a supported system, the applicable Conditions and Required Actions shall be entered in accordance with LCO 3.0.2.

(continued)

Catawba Units 1 and 2 3.0-2 Amendment Nos. 235, 231

LCO Applicability 3.0 3.0 LCO APPLICABILITY (continued)

LCO 3.0.7 Test Exception LCOs 3.1.8 and 3.4.17 allow specified Technical Specification (TS) requirements to be changed to permit performance of special tests and operations. Unless otherwise specified, all other TS requirements remain unchanged. Compliance with Test Exception LCOs is optional. When a Test Exception LCO is desired to be met but is not met, the ACTIONS of the Test Exception LCO shall be met. When a Test Exception LCO is not desired to be met, entry into a MODE or other specified condition in the Applicability shall be made in accordance with the other applicable Specifications.

LCO 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.

(continued)

Catawba Units 1 and 2 3.0-3 Amendment Nos. 2 3 5 , 2311

LCO Applicability 3.0 3.0 LCO APPLICABILITY (continued)

LCO 3.0.9 LCOs including the associated ACTIONS shall apply to each unit individually unless otherwise indicated as follows:

I

a. Whenever the LCO refers to systems or components which are shared by both units, the ACTIONS will apply to both units simultaneously;

b. Whenever the LCO applies to only one unit, this will be identified in the Applicability section of the Specification; and

c. Whenever certain portions of a Specification contain operating parameters, setpoints etc., which are different for each unit, this will be identified in parentheses or footnotes. (For example, "...flow rate of 54,000 cfm (Unit 1) or 43,000 cfm (Unit 2)...").

Catawba Units 1 and 2 3.0-4 Amendment Nos. 235, 231 1

SR Applicability 3.0 3.0 SURVEILLANCE REQUIREMENT (SR) APPLICABILITY SR 3.0.1 SRs shall be met during the MODES or other specified conditions in the Applicability for individual LCOs, unless otherwise stated in the SR.

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 LCO. Failure to perform a Surveillance within the specified Frequency shall be failure to meet the LCO except as provided in SR 3.0.3. Surveillances do not have to be performed on inoperable equipment or variables outside specified limits.

SR 3.0.2 The specified Frequency for each SR is met if the Surveillance is performed within 1.25 times the interval specified in the Frequency, as measured from the previous performance or as measured from the time a specified condition of the Frequency is met.

For Frequencies specified as "once," the above interval extension does not apply.

If a Completion Time requires periodic performance on a "once per...

basis, the above Frequency extension applies to each performance after the initial performance.

Exceptions to this Specification are stated in the individual Specifications.

SR 3.0.3 If it is discovered that a Surveillance was not performed within its specified 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 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.

(continued)

Catawba Units 1 and 2 3.0-5 Amendment Nos.235, 231

SR Applicability 3.0 3.0 SR APPLICABILITY (continued)

SR 3.0.4 Entry into a MODE or other specified condition in the'Applicability of an LCO shall only be made when the LCO's Surveillances have been met within their specified Frequency, except as provided by SR 3.0.3. When an LCO is not met due to Surveillances not having been met, entry into a MODE or other specified condition in the Applicability shall only be made in accordance with LCO 3.0.4 This provision shall not prevent entry into MODES or other specified conditions in the Applicability that are required to comply with ACTIONS or that are part of a shutdown of the unit.

SR 3.0.5 Surveillance Requirements shall apply to each unit individually unless otherwise indicated as stated in LCO 3.0.8 for individual Specifications or whenever certain portions of a Specification contain surveillance parameters different for each unit, which will be identified in parentheses or footnotes.

Catawba Units 1 and 2 3.0-6 Amendment Nos. 235, 2311