ML050750064

From kanterella
Jump to navigation Jump to search

Tech Spec Pages for Amendments 212 and 204, Respectively, Increased Flexibility in Mode Restraints
ML050750064
Person / Time
Site: Dresden  Constellation icon.png
Issue date: 03/10/2005
From:
NRC/NRR/DLPM/LPD3
To:
Rossbach L, 415-2863, NRR/DLPM
Shared Package
ML050750445 List:
References
TAC MC3025, TAC MC3026
Download: ML050750064 (11)
v • d • e


Text

Frequency 1.4 1.4 Frequency DESCRIPTION a. The Surveillance is not required to be performed; and (continued)

b. The Surveillance is not required to be met or, even if required to be met, is not known to be failed.

EXAMPLES The following examples illustrate the various ways that Frequencies are specified. In these examples, the Applicability of the LCO (LCO not shown) is MODES 1, 2, and 3. The examples do not reflect the potential application of LCO 3.0.4.b.

EXAMPLE 1.4-1 SURVEILLANCE REQUIREMENTS SURVEILLANCE FREQUENCY Perform CHANNEL CHECK. 12 hours1.388889e-4 days <br />0.00333 hours <br />1.984127e-5 weeks <br />4.566e-6 months <br /> Example 1.4-1 contains the type of SR most often encountered in the Technical Specifications (TS). The Frequency specifies an interval (12 hours1.388889e-4 days <br />0.00333 hours <br />1.984127e-5 weeks <br />4.566e-6 months <br />) during which the associated Surveillance must be performed at least one time.

Performance of the Surveillance initiates the subsequent interval. Although the Frequency is stated as 12 hours1.388889e-4 days <br />0.00333 hours <br />1.984127e-5 weeks <br />4.566e-6 months <br />, an extension of the time interval to 1.25 times the interval specified in the Frequency is allowed by SR 3.0.2 for operational flexibility. The measurement of this interval continues at all times, even when the SR is not required to be met per SR 3.0.1 (such as when the equipment is inoperable, a variable is outside specified limits, or the unit is outside the Applicability of the LCO). If the interval specified by SR 3.0.2 is exceeded while the unit is in a MODE or other specified condition in the Applicability of the LCO, and the performance of the Surveillance is not otherwise modified (refer to Examples 1.4-3 and 1.4-4), then SR 3.0.3 becomes applicable.

If the interval as specified by SR 3.0.2 is exceeded while the unit is not in a MODE or other specified condition in the Applicability of the LCO for which performance of the SR (continued)

Dresden 2 and 3 1.4-2 Amendment No. 212/204

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

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 13 hours1.50463e-4 days <br />0.00361 hours <br />2.149471e-5 weeks <br />4.9465e-6 months <br />; and
b. MODE 4 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, and 3.

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;
b. After performance of a risk assessment addressing inoperable systems and components, consideration of (continued)

Dresden 2 and 3 3.0-1 Amendment No. 2 1 2/ 2 0 4

LCO Applicability 3.0 3.0 LCO APPLICABILITY LCO 3.0.4 the results, determination of the acceptability of (continued) 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 testing required 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, an evaluation shall be performed in accordance with Specification 5.5.11, "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)

Dresden 2 and 3 3.0-2 Amendment No. L2/204

LCO Applicability 3.0 3.0 LCO APPLICABILITY LCO 3.0.7 Special Operations LCOs in Section 3.10 allow specified Technical Specifications (TS) requirements to be changed to permit performance of special tests and operations. Unless otherwise specified, all other TS requirements remain unchanged. Compliance with Special Operations LCOs is optional. When a Special Operations LCO is desired to be met but 1s 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.

LCO 3.0.8 LCOs, including associated ACTIONS, shall apply to each unit individually, unless otherwise indicated. Whenever the LCO refers to a system or component that is shared by both units, the ACTIONS will apply to both units simultaneously.

.Dresden 2 and 3 3.0 -3 Amendment No. 212/204

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 I 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 SRs shall apply to each unit individually, unless otherwise indicated.

Dresden 2 and 3 3.0- 5 Amendment No. /

212/204

PAM Instrumentation 3.3.3.1 3.3 INSTRUMENTATION 3.3.3.1 Post Accident Monitoring (PAM) Instrumentation LCO 3.3.3.1 The PAM instrumentation for each Function in Table 3.3.3.1-1 shall be OPERABLE.

APPLICABILITY: MODES 1 and 2.

ACTIONS

NOTE------------------------------------

Separate Condition entry is allowed for each Function. I CONDITION REQUIRED ACTION COMPLETION TIME A. One or more Functions A.1 Restore required 30 days with one required channel to OPERABLE channel inoperable. status.

B. Required Action and B.1 Initiate action in Immediately associated Completion accordance with Time of Condition A Specification 5.6.6.

not met.

C. One or more Functions C.1 Restore one required 7 days with two required channel to OPERABLE channels inoperable. status.

(continued)

Dresden 2 and 3 3.3.3. 1-1 Amendment NO-21/204

RCS Specific Activity 3.4.6 3.4 REACTOR COOLANT SYSTEM (RCS) 3.4.6 RCS Specific Activity LCO 3.4.6 The specific activity of the reactor coolant shall be limited to DOSE EQUIVALENT 1-131 specific activity

< 0.2 jCi/gm.

APPLICABILITY: MODE 1, MODES 2 and 3 with any main steam line not isolated.

ACTIONS CONDITION REQUIRED ACTION COMPLETION TIME A. Reactor coolant -------------- NOTE-----------

specific activity LCO 3.0.4.c is applicable. I

> 0.2 pCi/gm and .

s 4.0 pCi/gm DOSE EQUIVALENT 1-131. A.1 Determine DOSE Once per 4 hours4.62963e-5 days <br />0.00111 hours <br />6.613757e-6 weeks <br />1.522e-6 months <br /> EQUIVALENT 1-131.

A.2 Restore DOSE 48 hours5.555556e-4 days <br />0.0133 hours <br />7.936508e-5 weeks <br />1.8264e-5 months <br /> EQUIVALENT I-131 to within limits.

B. Required Action and B.1 Determine DOSE Once per 4 hours4.62963e-5 days <br />0.00111 hours <br />6.613757e-6 weeks <br />1.522e-6 months <br /> associated Completion EQUIVALENT 1-131.

Time of Condition A not met. AND DR B.2.1 Isolate all main 12 hours1.388889e-4 days <br />0.00333 hours <br />1.984127e-5 weeks <br />4.566e-6 months <br /> steam lines.

Reactor Coolant specific activity OR

> 4.0 pCi/gm DOSE EQUIVALENT I-131.

(continued)

Dresden 2 and 3 3.4.6-1 Amendment No. /

212/204

SDC System-Hot Shutdown 3.4.7 3.4 REACTOR COOLANT SYSTEM (RCS) 3.4.7 Shutdown Cooling (SOC) System-Hot Shutdown LCO 3.4.7 Two SDC subsystems shall be OPERABLE, and, with no recirculation pump in operation, at least one SDC subsystem shall be in operation.

NOTES-----------.

1. Both required SDC subsystems and recirculation pumps may be not in operation for up to 2 hours2.314815e-5 days <br />5.555556e-4 hours <br />3.306878e-6 weeks <br />7.61e-7 months <br /> per 8 hour9.259259e-5 days <br />0.00222 hours <br />1.322751e-5 weeks <br />3.044e-6 months <br /> period.
2. One required SDC subsystem may be inoperable for up to 2 hours2.314815e-5 days <br />5.555556e-4 hours <br />3.306878e-6 weeks <br />7.61e-7 months <br /> for the performance of Surveillances.

APPLICABILITY: MODE 3, with reactor vessel coolant temperature less than the SDC cut-in permissive temperature.

ACTIONS

NOTE-------------------------------------

Separate Condition entry is allowed for each SDC subsystem. I CONDITION REQUIRED ACTION COMPLETION TIME A. One or two required A.1 Initiate action to Immediately SDC subsystems restore required SOC inoperable. subsystemts) to OPERABLE status.

AND (continued)

Dresden 2 and 3 3.4.7-1 Amendment No.2,/2/204

ECCS-Operating 3.5.1 3.5 EMERGENCY CORE COOLING SYSTEMS (ECCS) AND ISOLATION CONDENSER (IC) SYSTEM 3.5.1 ECCS-Operating LCO 3.5.1 Each ECCS injection/spray subsystem and the Automatic Depressurization System (ADS) function of five relief valves shall be OPERABLE.

APPLICABILITY: MODE 1, MODES 2 and 3, except high pressure coolant injection (HPCI) and ADS valves are not required to be OPERABLE with reactor steam dome pressure s 150 psig.

ACTIONS

e to H-.

LNOTEt--------------- - ---------------

LCO 3.0.4.b is not applicable to HPCI.

CONDITION REQUIRED ACTION COMPLETION TIME A. One Low Pressure A.1 Restore LPCI pump to 30 days Coolant Injection OPERABLE status.

(LPCI) pump inoperable.

B. One LPCI subsystem B.1 Restore low pressure 7 days inoperable for reasons ECCS injection/spray other than Condition A. subsystem to OPERABLE status.

OR One Core Spray subsystem inoperable.

C. One LPCI pump in each C.1 Restore one LPCI pump 7 days subsystem inoperable. to OPERABLE status.

D. Two LPCI subsystems D.1 Restore one LPCI 72 hours8.333333e-4 days <br />0.02 hours <br />1.190476e-4 weeks <br />2.7396e-5 months <br /> inoperable for reasons subsystem to OPERABLE other than Condition C. status.

(continued)

Dresden 2 and 3 3.5. 1-1 Amendment No. /

212/204

IC System 3.5.3 3.5 EMERGENCY CORE COOLING SYSTEMS (ECCS) AND ISOLATION CONDENSER (IC) SYSTEM 3.5.3 IC System LCO 3.5.3 The IC System shall be OPERABLE.

APPLICABILITY: MODE 1, MODES 2 and 3 with reactor steam dome pressure > 150-psig.

ACTIONS

NOTE---------------------------------------

LCO 3.0.4.b is not applicable to IC.

CONDITION REQUIRED ACTION COMPLETION TIME A. IC System inoperable. A.1 Verify by Immediately administrative means High Pressure Coolant Injection System is OPERABLE.

AND A.2 Restore IC System to 14 days OPERABLE status.

B. Required Action and B.1 Be in MODE 3. 12 hours1.388889e-4 days <br />0.00333 hours <br />1.984127e-5 weeks <br />4.566e-6 months <br /> associated Completion Time not met. AU B.2 Reduce reactor steam 36 hours4.166667e-4 days <br />0.01 hours <br />5.952381e-5 weeks <br />1.3698e-5 months <br /> dome pressure to s 150 psig.

Dresden 2 and 3 3.5.3-1 Amendment No212/204

AC Sources-Operating 3.8.1 ACTIONS

-- -- -- --- - -- -- - --- -- -- -- -- -- -- -- -- - -- NOTE -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -

LCO 3.0.4.b is not applicable to the unit and common DGs, but is applicable to the opposite unit DG. I CONDITION REQUIRED ACTION I COMPLETION TIME A. One required offsite A.1 Perform SR 3.8.1.1 1 hour1.157407e-5 days <br />2.777778e-4 hours <br />1.653439e-6 weeks <br />3.805e-7 months <br /> circuit inoperable. for OPERABLE required offsite circuit. AND Once per 8 hours9.259259e-5 days <br />0.00222 hours <br />1.322751e-5 weeks <br />3.044e-6 months <br /> thereafter A.2 Declare required 24 hours2.777778e-4 days <br />0.00667 hours <br />3.968254e-5 weeks <br />9.132e-6 months <br /> from feature(s) with no discovery of no offsite power offsite power to available inoperable one division when the redundant concurrent with required feature(s) inoperability of are inoperable. redundant required feature(s)

AND~

A.3 Restore required 7 days offsite circuit to OPERABLE status. AND 14 days from discovery of failure to meet LCO 3.8.1.a or b (continued)

Dresden 2 and 3 3.8.1-2 Amendment No. /

212/204

Retrieved from "https://kanterella.com/w/index.php?title=ML050750064&oldid=2595099"