RS-11-159, Quad Cities, Units 1 and 2 - Technical Requirements Manual

From kanterella
Jump to navigation Jump to search
Quad Cities, Units 1 and 2 - Technical Requirements Manual
ML11305A134
Person / Time
Site: Quad Cities  Constellation icon.png
Issue date: 10/19/2011
From:
Exelon Generation Co, Exelon Nuclear
To:
Office of Nuclear Reactor Regulation
References
RS-11-159
Download: ML11305A134 (354)


Text

Quad Cities Nuclear Power Station Technical Requirements Manual (TRM) October 2011

Quad Cities Nuclear Power Station, Unit 1 and 2 Renewed Facility Operating License Nos. DPR-29 (Unit 1) and DPR-30 (Unit 2) NRC Docket Nos. STN 50-254 (Unit 1) and 50-265 (Unit 2)

Quad Cities 1 and 2 1.1-1 Revision 0 TRM Definitions 1.1 1.0 USE AND APPLICATION

1.1 Definitions


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

The defined terms of this section appear in capitalized type and are applicable throughout these Technical Requirements Manual and Bases.


Term Definition

ACTIONS ACTIONS shall be that part of a Requirement that prescribes Required Actions to be taken under designated Conditions within specified Completion Times.

CHANNEL CALIBRATION A CHANNEL CALIBRATION shall be the adjustment, as necessary, of the channel output such that it responds within the necessary range and accuracy to known values of the parameter that the channel monitors. The CHANNEL CALIBRATION shall encompass all devices in the channel required for channel OPERABILITY and the CHANNEL FUNCTIONAL TEST. Calibration of instrument channels with resistance temperature detector (RTD) or thermocouple sensors may consist of an inplace qualitative assessment of sensor behavior and normal calibration of the remaining adjustable devices in the channel. The CHANNEL CALIBRATION may be performed by means of any series of sequential, overlapping, or total channel steps.

CHANNEL CHECK A CHANNEL CHECK shall be the qualitative assessment, by observation, of channel behavior during operation. This determination shall include, where possible, comparison of the channel indication and status to other indications or status derived from independent instrument channels measuring the

same parameter. (continued)

TRM Definitions 1.1 Quad Cities 1 and 2 1.1-2 Revision 0 1.1 Definitions (continued)

CHANNEL FUNCTIONAL TEST A CHANNEL FUNCTIONAL TEST shall be the injection of a simulated or actual signal into the channel as close to the sensor as practicable to verify OPERABILITY of all devices in the channel required for channel OPERABILITY. The CHANNEL FUNCTIONAL TEST may be performed by means of any series of sequential, overlapping, or total channel

steps.

CORE ALTERATION CORE ALTERATION shall be the movement of any fuel, sources, or reactivity control components, within the reactor vessel with the vessel head removed and fuel in the vessel.

The following exceptions are not considered to be CORE ALTERATIONS:

a. Movement of source range monitors, local power range monitors, intermediate range m onitors, traversing incore probes, or special movable detectors (including undervessel replacement); and
b. Control rod movement, provided there are no fuel assemblies in the associated core cell.

Suspension of CORE ALTERATIONS shall not preclude completion of movement of a component to a safe position.

CORE OPERATING LIMITS The COLR is the unit specific document that REPORT (COLR) provides cycle specific parameter limits for the current reload cycle. These cycle specific limits shall be determined for each reload cycle in accordance with Technical Specification 5.6.5. Plant operation within these limits is addressed in individual requirements.

LOGIC SYSTEM FUNCTIONAL A LOGIC SYSTEM FUNCTIONAL TEST shall be a test of TEST all logic components required for OPERABILITY of a logic circuit, from as close to the sensor as practicable up to, but not including, the actuated device, to verify OPERABILITY.

The LOGIC SYSTEM

(continued)

Quad Cities 1 and 2 1.1-3 Revision QC-TRM-02-007 1.1 Definitions (continued)

LOGIC SYSTEM FUNCTIONAL FUNCTIONAL TEST may be performed by means of any TEST series of sequential overlapping, or total system (continued) steps so that the entire logic system is tested.

MODE A MODE shall correspond to any one inclusive combination of MODE switch position, average reactor coolant temperature, and reactor vessel head closure bolt tensioning specified in Technical Specifications Table 1.1-1 with fuel in

the reactor vessel.

OFFSITE DOSE CALCULATION The ODCM shall contain the methodology and MANUAL (ODCM) parameters used in the calculation of offsite doses resulting from radioactive gaseous and liquid effluents, in the calculation of gaseous and liquid effluent monitoring Alarm/Trip Setpoints, and in the conduct of the Environmental Radiological Monitoring Program. The ODCM shall also contain (1) the Radioactive Effluent Controls and Radiological Environmental Monitoring Programs and (2) descriptions of the information that should be included in the Annual Radiological Environmental Operating and Radioactive

Effluent Release Reports.

OPERABLE - OPERABILITY A system, subsystem, division, component, or device shall be OPERABLE or have OPERABILITY when it is capable of performing its specified safety function(s) and when all necessary attendant instrumentation, controls, normal or emergency electrical power, cooling and seal water, lubrication, and other auxiliary equipment that are required for the system, subsystem, division, component, or device to perform its specified safety function(s) are also capable of performing their related support function(s).

RATED THERMAL POWER RTP shall be a total reactor core heat transfer rate to (RTP) the reactor coolant of 2957 MWt.

THERMAL POWER THERMAL POWER shall be the total reactor core heat transfer rate to the reactor coolant.

Quad Cities 1 and 2 1.2-1 Revision 0 TRM Logical Connectors 1.2 USE AND APPLICATION

1.2 Logical Connectors PURPOSE The purpose of this section is to explain the meaning of logical connectors.

Logical connectors are used in Technical Requirements Manual (TRM) to discriminate between, and yet connect, discrete Conditions, Required Actions, Completion Times, Surveillances, and Frequencies. The only logical connectors that appear in TRM are AND and OR. The physical arrangement of these connectors constitutes logical conventions with specific meanings.

BACKGROUND Several levels of logic may be used to state Required Actions. These levels are identified by the placement (or nesting) of the logical connectors and by the number assigned to each Required Action. The first level of logic is identified by the first digit of the number assigned to a Required Action and the placement of the logical connector in the first level of nesting (i.e., left justified with the number of the Required Action). The successive levels of logic are identified by additional digits of the Required Action number and by successive indentions of the logical connectors.

When logical connectors are used to state a Condition, Completion Time, Surveillance, or Frequency, only the first level of logic is used, and the logical connector is left justified with the statement of the Condition, Completion Time, Surveillance, or Frequency.

EXAMPLES The following examples illustrate the use of logical connectors.

(continued)

TRM Logical Connectors 1.2 Quad Cities 1 and 2 1.2-2 Revision 0 1.2 Logical Connectors EXAMPLES EXAMPLE 1.2-1 (continued)

ACTIONS CONDITION REQUIRED ACTION COMPLETION TIME A. TLCO not met.

A.1 Verify . . .

AND A.2 Restore . . .

In this example, the logical connector AND is used to indicate that, when in Condition A, both Required Actions A.1 and A.2 must be completed.

(continued)

TRM Logical Connectors 1.2 Quad Cities 1 and 2 1.2-3 Revision 0 1.2 Logical Connectors

EXAMPLES EXAMPLE 1.2-2 (continued)

ACTIONS CONDITION REQUIRED ACTION COMPLETION TIME

A. TLCO not met.

A.1 Trip . . .

OR A.2.1 Verify . . .

AND A.2.2.1 Reduce . . .

OR A.2.2.2 Perform . . .

OR A.3 Align . . .

This example represents a more complicated use of logical connectors.

Required Actions A.1, A.2, and A.3 are alternative choices, only one of which must be performed as indicated by the use of the logical connector OR and the left justified placement. Any one of these three Actions may be chosen. If A.2 is chosen, then both A.2.1 and A.2.2 must be performed as indicated by the logical connector AND. Required Action A.2.2 is met by performing A.2.2.1 or A.2.2.2. The indented position of the logical connector OR indicates that A.2.2.1 and A.2.2.2 are alternative choices, only one of which must be performed.

Quad Cities 1 and 2 1.3-1 Revision 0 TRM Completion Times 1.3 1.0 USE AND APPLICATION

1.3 Completion Times PURPOSE The purpose of this section is to establish the Completion Time convention and to provide guidance for its use.

BACKGROUND Technical Requirements Manual Limiting Conditions for Operation (TLCOs) specify minimum requirements for ensuring safe operation of the unit. The ACTIONS associated with a TLCO state Conditions that typically describe the ways in which the requirements of the TLCO can fail to be met. Specified with each stated Condition are Required Action(s) and Completion Time(s).

DESCRIPTION The Completion Time is the amount of time allowed for completing a Required Action. It is referenced to the time of discovery of a situation (e.g., inoperable equipment or variable not within limits) that requires entering an ACTIONS Condition unless otherwise specified, providing the unit is in a MODE or specified condition stated in the Applicability of the TLCO. Required Actions must be completed prior to the expiration of the specified Completion Time. An ACTIONS Condition remains in effect and the Required Actions apply until the Condition no longer exists or the unit is not within the TLCO Applicability.

If situations are discovered that require entry into more than one Condition at a time within a single TLCO (multiple Conditions), the Required Actions for each Condition must be performed within the associated Completion Time. When in multiple Conditions, separate Completion Times are tracked for each Condition starting from the time of discovery of the situation that required entry into the Condition.

Once a Condition has been entered, subsequent divisions, subsystems, components, or variables expressed in the Condition, discovered to be inoperable or not within limits, will not result in separate entry into the Condition unless specifically stated. The Required Actions of the Condition continue to apply to each additional failure, with Completion Times based on initial entry into the Condition.

(continued)

TRM Completion Times 1.3 Quad Cities 1 and 2 1.3-2 Revision 0 1.3 Completion Times

DESCRIPTION However, when a subsequent division, subsystem, component, (continued) or variable expressed in the Condition is discovered to be inoperable or not within limits, the Completion Time(s) may be extended. To apply this Completion Time extension, two criteria must first be met. The subsequent inoperability:

a. Must exist concurrent with the first inoperability; and
b. Must remain inoperable or not within limits after the first inoperability is resolved.

The total Completion Time allowed for completing a Required Action to address the subsequent inoperability shall be limited to the more restrictive of either:

a. The stated Completion Time, as measured from the initial entry into the Condition, plus an additional 24 hours2.777778e-4 days <br />0.00667 hours <br />3.968254e-5 weeks <br />9.132e-6 months <br />; or
b. The stated Completion Time as measured from discovery of the subsequent inoperability.

The above Completion Time extension does not apply to those TLCOs that have exceptions that allow completely separate re-entry into the Condition (for each division, subsystem, component, or variable expressed in the Condition) and separate tracking of Completion Times based on this re-entry. These exceptions are stated in individual TLCOs.

The above Completion Time extension does not apply to a Completion Time with a modified "time zero." This modified "time zero" may be expressed as a repetitive time (i.e., "once per 8 hours9.259259e-5 days <br />0.00222 hours <br />1.322751e-5 weeks <br />3.044e-6 months <br />," where the Completion Time is referenced from a previous completion of the Required Action versus the time of Condition entry) or as a time modified by the phrase "from discovery . . ." Example 1.3-3 illustrates one use of this type of Completion Time. The 10 day Completion Time specified for Conditions A and B in Example 1.3-3 may not be extended.

EXAMPLES The following examples illustrate the use of Completion Times with different types of Conditions and changing Conditions.

(continued)

TRM Completion Times 1.3 Quad Cities 1 and 2 1.3-3 Revision 0 1.3 Completion Times

EXAMPLES EXAMPLE 1.3-1 (continued)

ACTIONS CONDITION REQUIRED ACTION COMPLETION TIME

B. Required Action and associated

Completion Time not met.

B.1 Be in MODE 3.

AND B.2 Be in MODE 4.

12 hours1.388889e-4 days <br />0.00333 hours <br />1.984127e-5 weeks <br />4.566e-6 months <br />

36 hours4.166667e-4 days <br />0.01 hours <br />5.952381e-5 weeks <br />1.3698e-5 months <br /> Condition B has two Required Actions. Each Required Action has its own separate Completion Time. Each Completion Time is referenced to the time that Condition B is entered.

The Required Actions of Condition B are to be in MODE 3 within 12 hours1.388889e-4 days <br />0.00333 hours <br />1.984127e-5 weeks <br />4.566e-6 months <br /> AND in MODE 4 within 36 hours4.166667e-4 days <br />0.01 hours <br />5.952381e-5 weeks <br />1.3698e-5 months <br />. A total of 12 hours1.388889e-4 days <br />0.00333 hours <br />1.984127e-5 weeks <br />4.566e-6 months <br /> is allowed for reaching MODE 3 and a total of 36 hours4.166667e-4 days <br />0.01 hours <br />5.952381e-5 weeks <br />1.3698e-5 months <br /> (not 48 hours5.555556e-4 days <br />0.0133 hours <br />7.936508e-5 weeks <br />1.8264e-5 months <br />) is allowed for reaching MODE 4 from the time that Condition B was entered. If MODE 3 is reached within 6 hours6.944444e-5 days <br />0.00167 hours <br />9.920635e-6 weeks <br />2.283e-6 months <br />, the time allowed for reaching MODE 4 is the next 30 hours3.472222e-4 days <br />0.00833 hours <br />4.960317e-5 weeks <br />1.1415e-5 months <br /> because the total time allowed for reaching MODE 4 is 36 hours4.166667e-4 days <br />0.01 hours <br />5.952381e-5 weeks <br />1.3698e-5 months <br />.

If Condition B is entered while in MODE 3, the time allowed for reaching MODE 4 is the next 36 hours4.166667e-4 days <br />0.01 hours <br />5.952381e-5 weeks <br />1.3698e-5 months <br />.

(continued)

TRM Completion Times 1.3 Quad Cities 1 and 2 1.3-4 Revision 0 1.3 Completion Times

EXAMPLES EXAMPLE 1.3-2 (continued)

ACTIONS CONDITION REQUIRED ACTION COMPLETION TIME

A. One pump inoperable.

A.1 Restore pump to OPERABLE status.

7 days B. Required Action and associated Completion Time not met.

B.1 Be in MODE 3.

AND B.2 Be in MODE 4.

12 hours1.388889e-4 days <br />0.00333 hours <br />1.984127e-5 weeks <br />4.566e-6 months <br />

36 hours4.166667e-4 days <br />0.01 hours <br />5.952381e-5 weeks <br />1.3698e-5 months <br /> When a pump is declared inoperable, Condition A is entered. If the pump is not restored to OPERABLE status within 7 days, Condition B is also entered and the Completion Time clocks for Required Actions B.1 and B.2 start. If the inoperable pump is restored to OPERABLE status after Condition B is entered, Condition A and B are exited, and therefore, the Required Actions of Condition B may be terminated.

When a second pump is declared inoperable while the first pump is still inoperable, Condition A is not re-entered for the second pump.

TLCO 3.0.c is entered, since the ACTIONS do not include a Condition for more than one inoperable pump. The Completion Time clock for Condition A does not stop after TLCO 3.0.c is entered, but continues to be tracked from the time Condition A was initially entered.

While in TLCO 3.0.c, if one of the inoperable pumps is restored to OPERABLE status and the Completion Time for Condition A has not expired, TLCO 3.0.c may be exited and operation continued in accordance with Condition A.

(continued)

TRM Completion Times 1.3 Quad Cities 1 and 2 1.3-5 Revision 0 1.3 Completion Times

EXAMPLES EXAMPLE 1.3-2 (continued)

While in TLCO 3.0.c, if one of the inoperable pumps is restored to OPERABLE status and the Completion Time for Condition A has expired, TLCO 3.0.c may be exited and operation continued in accordance with Condition B. The Completion Time for Condition B is tracked from the

time the Condition A Completion Time expired.

On restoring one of the pumps to OPERABLE status, the Condition A Completion Time is not reset, but continues from the time the first pump was declared inoperable. This Completion Time may be extended if the pump restored to OPERABLE status was the first inoperable pump. A 24 hour2.777778e-4 days <br />0.00667 hours <br />3.968254e-5 weeks <br />9.132e-6 months <br /> extension to the stated 7 days is allowed, provided this does not result in the second pump being inoperable for > 7 days.

(continued)

TRM Completion Times 1.3 Quad Cities 1 and 2 1.3-6 Revision 0 1.3 Completion Times

EXAMPLES EXAMPLE 1.3-3 (continued)

ACTIONS CONDITION REQUIRED ACTION COMPLETION TIME

A. One Function X

subsystem

inoperable.

A.1 Restore Function X subsystem to OPERABLE status.

7 days

AND 10 days from discovery of failure to

meet the TLCO B. One Function Y subsystem

inoperable.

B.1 Restore Function Y subsystem to OPERABLE status.

72 hours8.333333e-4 days <br />0.02 hours <br />1.190476e-4 weeks <br />2.7396e-5 months <br /> AND 10 days from

discovery of failure to meet the TLCO C. One Function X subsystem inoperable.

AND One Function Y

subsystem

inoperable.

C.1 Restore Function X subsystem to OPERABLE status.

OR C.2 Restore Function Y subsystem to OPERABLE status.

72 hours8.333333e-4 days <br />0.02 hours <br />1.190476e-4 weeks <br />2.7396e-5 months <br />

72 hours8.333333e-4 days <br />0.02 hours <br />1.190476e-4 weeks <br />2.7396e-5 months <br /> (continued)

TRM Completion Times 1.3 Quad Cities 1 and 2 1.3-7 Revision 0 1.3 Completion Times

EXAMPLES EXAMPLE 1.3-3 (continued)

When one Function X subsystem and one Function Y subsystem are inoperable, Condition A and Condition B are concurrently applicable. The Completion Times for Condition A and Condition B are tracked separately for each subsystem, starting from the time each subsystem was declared inoperable and the Condition was entered. A separate Completion Time is established for Condition C and tracked from the time the second subsystem was declared inoperable (i.e., the time the situation described in Condition C was discovered).

If Required Action C.2 is completed within the specified Completion Time, Conditions B and C are exited. If the Completion Time for Required Action A.1 has not expired, operation may continue in accordance with Condition A. The remaining Completion Time in Condition A is measured from the time the affected subsystem was declared inoperable (i.e., initial entry into Condition A).

The Completion Times of Conditions A and B are modified by a logical connector, with a separate 10 day Completion Time measured from the time it was discovered the TLCO was not met. In this example, without the separate Completion Time, it would be possible to alternate between Conditions A, B, and C in such a manner that operation could continue indefinitely without ever restoring sy stems to meet the TLCO. The separate Completion Time modified by the phrase "from discovery of failure to meet the TLCO" is designed to prevent indefinite continued

operation while not meeting the TLCO. This Completion Time allows for an exception to the normal "time zero" for beginning the Completion Time "clock". In this instance, the Completion Time "time zero" is specified as commencing at the time the TLCO was initially not met, instead of at the time the associated Condition was entered.

(continued)

TRM Completion Times 1.3 Quad Cities 1 and 2 1.3-8 Revision 0 1.3 Completion Times

EXAMPLES EXAMPLE 1.3-4 (continued)

ACTIONS CONDITION REQUIRED ACTION COMPLETION TIME

A. One or more valves inoperable.

A.1 Restore valve(s) to OPERABLE status.

4 hours4.62963e-5 days <br />0.00111 hours <br />6.613757e-6 weeks <br />1.522e-6 months <br /> B. Required Action and associated

Completion Time not met.

B.1 Be in MODE 3.

AND B.2 Be in MODE 4.

12 hours1.388889e-4 days <br />0.00333 hours <br />1.984127e-5 weeks <br />4.566e-6 months <br />

36 hours4.166667e-4 days <br />0.01 hours <br />5.952381e-5 weeks <br />1.3698e-5 months <br /> A single Completion Time is used for any number of valves inoperable at the same time. The Completion Time associated with Condition A is based on the initial entry into Condition A and is not tracked on a per

valve basis. Declaring subsequent valves inoperable, while Condition A is still in effect, does not trigger the tracking of separate Completion

Times. Once one of the valves has been restored to OPERABLE status, the Condition A Completion Time is not reset, but continues from the time the first valve was declared inoperable. The Completion Time may be extended if the valve restored to OPERABLE status was the first inoperable valve. The Condition A Completion Time may be extended for up to 4 hours4.62963e-5 days <br />0.00111 hours <br />6.613757e-6 weeks <br />1.522e-6 months <br /> provided this does not result in any subsequent valve being inoperable for > 4 hours4.62963e-5 days <br />0.00111 hours <br />6.613757e-6 weeks <br />1.522e-6 months <br />.

If the Completion Time of 4 hours4.62963e-5 days <br />0.00111 hours <br />6.613757e-6 weeks <br />1.522e-6 months <br /> (plu s the extension) expires while one or more valves are still inoperable, Condition B is entered.

(continued)

TRM Completion Times 1.3 Quad Cities 1 and 2 1.3-9 Revision 0 1.3 Completion Times

EXAMPLES EXAMPLE 1.3-5 (continued)

ACTIONS ----------------------------------------------NOTE----------------------------------------

Separate Condition entry is allowed for each inoperable valve.


CONDITION REQUIRED ACTION COMPLETION TIME

A. One or more valves inoperable.

A.1 Restore valve to OPERABLE status.

4 hours4.62963e-5 days <br />0.00111 hours <br />6.613757e-6 weeks <br />1.522e-6 months <br /> B. Required Action and associated

Completion Time not met.

B.1 Be in MODE 3.

AND B.2 Be in MODE 4.

12 hours1.388889e-4 days <br />0.00333 hours <br />1.984127e-5 weeks <br />4.566e-6 months <br />

36 hours4.166667e-4 days <br />0.01 hours <br />5.952381e-5 weeks <br />1.3698e-5 months <br /> The Note above the ACTIONS Table is a method of modifying how the Completion Time is tracked. If this method of modifying how the Completion Time is tracked was applicable only to a specific Condition, the Note would appear in that Condition rather than at the top of the ACTIONS Table.

The Note allows Condition A to be entered separately for each inoperable valve, and Completion Times tracked on a per valve basis. When a valve is declared inoperable, Condition A is entered and its Completion Time starts. If subsequent valves are declared inoperable, Condition A is entered for each valve and separate Completion Times start and are tracked for each valve.

(continued)

TRM Completion Times 1.3 Quad Cities 1 and 2 1.3-10 Revision 0 1.3 Completion Times EXAMPLES EXAMPLE 1.3-5 (continued)

If the Completion Time associated with a valve in Condition A expires, Condition B is entered for that valve. If the Completion Times associated with subsequent valves in Condition A expire, Condition B is entered separately for each valve and separate Completion Times start and are tracked for each valve. If a valve that caused entry into Condition B is restored to OPERABLE status, Condition B is exited for that valve.

Since the Note in this example allows multiple Condition entry and tracking of separate Completion Times, Completion Time extensions do

not apply.

EXAMPLE 1.3-6 ACTIONS CONDITION REQUIRED ACTION COMPLETION TIME

A. One channel inoperable.

A.1 Perform TSR 3.x.x.x.

OR A.2 Reduce THERMAL POWER to

< 50% RTP.

Once per 8 hours9.259259e-5 days <br />0.00222 hours <br />1.322751e-5 weeks <br />3.044e-6 months <br />

8 hours9.259259e-5 days <br />0.00222 hours <br />1.322751e-5 weeks <br />3.044e-6 months <br /> B. Required Action and associated

Completion Time not met.

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 /> (continued)

TRM Completion Times 1.3 Quad Cities 1 and 2 1.3-11 Revision 0 1.3 Completion Times

EXAMPLES EXAMPLE 1.3-6 (continued)

Entry into Condition A offers a choice between Required Action A.1 or A.2. Required Action A.1 has a "once per" Completion Time, which qualifies for the 25% extension, per TSR 3.0.b, to each performance after the initial performance. The initial 8 hour9.259259e-5 days <br />0.00222 hours <br />1.322751e-5 weeks <br />3.044e-6 months <br /> interval of Required Action A.1 begins when Condition A is entered and the initial performance of Required Action A.1 must be completed within the first 8 hour9.259259e-5 days <br />0.00222 hours <br />1.322751e-5 weeks <br />3.044e-6 months <br /> interval. If Required Action A.1 is followed and the Required Action is not met within the Completion Time (plus the extension allowed by TSR 3.0.b),

Condition B is entered. If Required Action A.2 is followed and the Completion Time of 8 hours9.259259e-5 days <br />0.00222 hours <br />1.322751e-5 weeks <br />3.044e-6 months <br /> is not met, Condition B is entered.

If after entry into Condition B, Required Action A.1 or A.2 is met, Condition B is exited and operation may then continue in Condition A.

(continued)

TRM Completion Times 1.3 Quad Cities 1 and 2 1.3-12 Revision 0 1.3 Completion Times

EXAMPLES EXAMPLE 1.3-7 (continued)

ACTIONS CONDITION REQUIRED ACTION COMPLETION TIME

A. One subsystem

inoperable.

A.1 Verify affected subsystem

isolated.

AND A.2 Restore subsystem to OPERABLE status.

1 hour1.157407e-5 days <br />2.777778e-4 hours <br />1.653439e-6 weeks <br />3.805e-7 months <br />

AND Once per 8 hours9.259259e-5 days <br />0.00222 hours <br />1.322751e-5 weeks <br />3.044e-6 months <br /> thereafter

72 hours8.333333e-4 days <br />0.02 hours <br />1.190476e-4 weeks <br />2.7396e-5 months <br /> B. Required Action and associated Completion Time not met.

B.1 Be in MODE 3.

AND B.2 Be in MODE 4.

12 hours1.388889e-4 days <br />0.00333 hours <br />1.984127e-5 weeks <br />4.566e-6 months <br />

36 hours4.166667e-4 days <br />0.01 hours <br />5.952381e-5 weeks <br />1.3698e-5 months <br /> Required Action A.1 has two Completion Times. The 1 hour1.157407e-5 days <br />2.777778e-4 hours <br />1.653439e-6 weeks <br />3.805e-7 months <br /> Completion Time begins at the time the Condition is entered and each "Once per 8 hours9.259259e-5 days <br />0.00222 hours <br />1.322751e-5 weeks <br />3.044e-6 months <br /> thereafter" interval begins upon performance of Required Action A.1.

If after Condition A is entered, Required Action A.1 is not met within either the initial 1 hour1.157407e-5 days <br />2.777778e-4 hours <br />1.653439e-6 weeks <br />3.805e-7 months <br /> or any subsequent 8 hour9.259259e-5 days <br />0.00222 hours <br />1.322751e-5 weeks <br />3.044e-6 months <br /> interval from the previous performance (plus the extension allowed by TSR 3.0.b), Condition B is entered. The Completion Time clock for Condition A does not stop after Condition B is entered, but continues from the time Condition A was initially entered. If Required Action A.1

(continued)

TRM Completion Times 1.3 Quad Cities 1 and 2 1.3-13 Revision 0 1.3 Completion Times

EXAMPLES EXAMPLE 1.3-7 (continued) is met after Condition B is entered, Condition B is exited and operation may continue in accordance with Condition A, provided the Completion Time for Required Action A.2 has not expired.

IMMEDIATE When "Immediately" is used as a Completion Time, the COMPLETION TIME Required Action should be pursued without delay and in a controlled manner.

Quad Cities 1 and 2 1.4-1 Revision 0 TRM Frequency 1.4 1.0 USE AND APPLICATION

1.4 Frequency

PURPOSE The purpose of this section is to define the proper use and application of Frequency requirements.

DESCRIPTION Each Technical Requirements Manual Surveillance Requirement (TSR) has a specified Frequency in which the Surveillance must be met in order to meet the associated Technical Requirements Manual Limiting Condition for Operation (TLCO). An understanding of the correct application of the specified Frequency is necessary for compliance with the TSR. The "specified Frequency" is referred to throughout this section and each of the Specifications of Section 3.0, Technical Requirements Manual Surveillance Requirement (TSR) Applicability. The "specified Frequency" consists of the requirements of the Frequency column of each TSR, as well as certain Notes in the Surveillance column that modify performance requirements.

Sometimes special situations dictate when the requirements of a Surveillance are to be met. They are "otherwise stated" conditions allowed by TSR 3.0.a. They may be stated as clarifying Notes in the Surveillance, as part of the Surveillance, or both. Example 1.4-4 discusses these special situations.

Situations where a Surveillance could be required (i.e., its Frequency could expire), but where it is not possible or not desired that it be performed until sometime after the associated TLCO is within its Applicability, represent potential TSR 3.0.d conflicts. To avoid these conflicts, the TSR (i.e., the Surveillance or the Frequency) is stated such that it is only "required" when it can be and should be performed. With an TSR satisfied, TSR 3.0.d imposes no restriction.

The use of "met" or "performed" in these instances conveys specified

meanings. A Surveillance is "met" only when the acceptance criteria are satisfied. Known failure of the requirements of a Surveillance, even without a Surveillance specifically being "performed," constitutes a Surveillance not "met." "Performance" refers only to the requirement to

(continued)

TRM Frequency 1.4 Quad Cities 1 and 2 1.4-2 Revision 0 1.4 Frequency

DESCRIPTION specifically determine the ability to meet the acceptance (continued) criteria. TSR 3.0.d restrictions would not apply if both the following conditions are satisfied:

a. The Surveillance is not required to be performed; and
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 TLCO (TLCO not

shown) is MODES 1, 2, and 3.

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 TSR most often encountered in the Technical Requirements Manual (TRM). 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 TSR 3.0.b for operational flexibility. The measurement of this interval continues at all times, even when the TSR is not required to be met per TSR 3.0.a (such as when the equipment is inoperable, a variable is outside specified limits, or the unit is outside the Applicability of the TLCO). If the interval specified by TSR 3.0.b is exceeded while the unit is in a MODE or other specified condition in the

(continued)

TRM Frequency 1.4 Quad Cities 1 and 2 1.4-3 Revision 0 1.4 Frequency

EXAMPLES EXAMPLE 1.4-1 (continued)

Applicability of the TLCO, and the performance of the Surveillance is not otherwise modified (refer to Examples 1.4-3 and 1.4-4), then TSR 3.0.c becomes applicable.

If the interval as specified by TSR 3.0.b is exceeded while the unit is not in a MODE or other specified condition in the Applicability of the TLCO for which performance of the TSR is required, the Surveillance must be performed within the Frequency requirements of TSR 3.0.b prior to entry into the MODE or other specified condition. Failure to do so would result in a violation of TSR 3.0.d.

EXAMPLE 1.4-2 SURVEILLANCE REQUIREMENTS SURVEILLANCE FREQUENCY Verify flow is within limits.

Once within 12 hours1.388889e-4 days <br />0.00333 hours <br />1.984127e-5 weeks <br />4.566e-6 months <br /> after

> 25% RTP AND 24 hours2.777778e-4 days <br />0.00667 hours <br />3.968254e-5 weeks <br />9.132e-6 months <br /> thereafter Example 1.4-2 has two Frequencies. The first is a one time performance Frequency, and the second is of the type shown in Example 1.4-1. The logical connector "AND" indicates that both Frequency requirements must be met. Each time reactor power is increased from a power level

< 25% RTP to >

25% RTP, the Surveillance must be performed within 12 hours1.388889e-4 days <br />0.00333 hours <br />1.984127e-5 weeks <br />4.566e-6 months <br />.

(continued)

TRM Frequency 1.4 Quad Cities 1 and 2 1.4-4 Revision 0 1.4 Frequency

EXAMPLES EXAMPLE 1.4-2 (continued)

The use of "once" indicates a single performance will satisfy the specified Frequency (assuming no other Frequencies are connected by "AND

"). This type of Frequency does not qualify for the extension allowed by TSR 3.0.b.

"Thereafter" indicates future performances must be established per TSR 3.0.b, but only after a specified condition is first met (i.e., the "once" performance in this example). If reactor power decreases to < 25% RTP, the measurement of both intervals stops. New intervals start upon reactor power reaching 25% RTP.

EXAMPLE 1.4-3 SURVEILLANCE REQUIREMENTS SURVEILLANCE FREQUENCY ---------------------------NOTE-----------------------------

Not required to be performed until 12 hours1.388889e-4 days <br />0.00333 hours <br />1.984127e-5 weeks <br />4.566e-6 months <br /> after

> 25% RTP. ----------------------------------------------------------------

Perform channel adjustment.

7 days The interval continues whether or not the unit operation is < 25% RTP between performances.

As the Note modifies the required performance of the Surveillance, it is construed to be part of the "specified Frequency." Should the 7 day interval be exceeded while operation is < 25% RTP, this Note allows 12 hours1.388889e-4 days <br />0.00333 hours <br />1.984127e-5 weeks <br />4.566e-6 months <br /> after power reaches > 25% RTP to perform the Surveillance. The Surveillance is still considered to be within the "specified Frequency."

Therefore, if the Surveillance were not performed within the 7 day interval (plus the extension

(continued)

TRM Frequency 1.4 Quad Cities 1 and 2 1.4-5 Revision 0 1.4 Frequency

EXAMPLES EXAMPLE 1.4-3 (continued) allowed by TSR 3.0.b), but operation was < 25% RTP, it would not constitute a failure of the TSR or failure to meet the TLCO. Also, no violation of TSR 3.0.d occurs when changing MODES, even with the 7 day Frequency not met, provided operation does not exceed 12 hours1.388889e-4 days <br />0.00333 hours <br />1.984127e-5 weeks <br />4.566e-6 months <br />

with power >

25% RTP.

Once the unit reaches 25% RTP, 12 hours1.388889e-4 days <br />0.00333 hours <br />1.984127e-5 weeks <br />4.566e-6 months <br /> would be allowed for completing the Surveillance. If the Surveillance were not performed within this 12 hour1.388889e-4 days <br />0.00333 hours <br />1.984127e-5 weeks <br />4.566e-6 months <br /> interval, there would then be a failure to perform a Surveillance within the specified Frequency, and the provisions of

TSR 3.0.c would apply.

EXAMPLE 1.4-4 SURVEILLANCE REQUIREMENTS SURVEILLANCE FREQUENCY


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

Only required to be met in MODE 1.


Verify leakage rates are within limits.

24 hours2.777778e-4 days <br />0.00667 hours <br />3.968254e-5 weeks <br />9.132e-6 months <br /> Example 1.4-4 specifies that the requirements of this Surveillance do not have to be met until the unit is in MODE 1. The interval measurement for the Frequency of this Surveillance continues at all times, as described in Example 1.4-1. However, the Note constitutes an "otherwise stated" exception to the Applicability of this Surveillance. Therefore, if the Surveillance were not performed within the 24 hour2.777778e-4 days <br />0.00667 hours <br />3.968254e-5 weeks <br />9.132e-6 months <br /> interval (plus the extension allowed by TSR 3.0.b), but the unit was not in MODE 1, there would be no failure of the TSR nor failure to meet the TLCO. Therefore, no violation of TSR 3.0.d occurs when changing MODES, even with the 24 hour2.777778e-4 days <br />0.00667 hours <br />3.968254e-5 weeks <br />9.132e-6 months <br /> Frequency exceeded, provided the MODE change was not made into MODE 1. Prior to entering MODE 1 (assuming again that the 24 hour2.777778e-4 days <br />0.00667 hours <br />3.968254e-5 weeks <br />9.132e-6 months <br /> Frequency were not met), TSR 3.0.d would require satisfying the TSR.

Quad Cities 1 and 2 1.5-1 Revision 0 TRM TLCO and TSR Implementation 1.5 1.0 USE AND APPLICATION

1.5 TLCO and TSR Implementation

The Technical Requirements Manual (TRM) provides those limitations upon plant operations which are part of the licensing basis for the station but do not meet the criteria for continued inclusion in the Technical Specifications.

It also provides information which supplements the Technical Specifications. Nothing in the TRM shall supersede any Technical Specification requirement.

TLCOs and TSRs are implemented the same as Technical Specifications (see TRM 3.0). However, TLCOs and TSRs are treated as plant procedures and are not part of the Technical Specifications. Therefore the following exceptions apply:

a. Violations of the Action or Surveillance requirements in a TLCO are not reportable as conditions prohibited by, or deviations from, the Technical Specifications per 10 CFR 50.72 or 10 CFR 50.73, unless specifically required by the TRM.
b. Power reduction or plant shutdowns required to comply with the Actions of a TLCO or as a result of the application of TLCO 3.0.c are not reportable per 10 CFR 50.72 or 10 CFR 50.73.
c. Violations of TLCO or TSR requirements, except as provided for in TLCO 3.0 of this manual, shall be treated the same as plant procedure violations.

Quad Cities 1 and 2 1.6-1 Revision 0 TRM Technical Requirements Manual Revisions 1.6 1.0 USE AND APPLICATION

1.6 Technical Requirements Manual Revisions

Changes to this manual shall be made under the following provisions:

a. Changes to the TRM shall be made under appropriate administrative controls and reviews. b. Licensees may make changes to TRM without prior NRC approval provided the change does not require NRC approval pursuant to 10 CFR 50.59.
c. The TRM revision process shall contain provisions to ensure that the TRM is maintained consistent with the UFSAR.
d. Proposed changes that require NRC approval prior to shall be reviewed and approved by the NRC prior to implementation. Changes to the TRM implemented without prior NRC approval shall be provided to the NRC on a frequency consistent with 10 CFR 50.71(e) as modified by approved exemptions.

Quad Cities 1 and 2 2.1.a-1 Revision QC-TRM-09-002 TRM Miscellaneous Test Requirements 2.1.a 2.1.a MISCELLANEOUS TEST REQUIREMENTS


NOTE------------------------------------------------------------------- Failure to meet the surveillance requirement require immediate actions to determine OPERABILITY of the associated equipment.


APPLICABILITY: As defined in the TSR.

SURVEILLANCE REQUIREMENTS SURVEILLANCE FREQUENCY TSR 2.1.a.1 -----------------------------NOTE---------------------------

Only applicable in MODES 1 and 2.


Verify reactor recirculation control system programmed maximum speed limit setting and adjustable speed drive programmed maximum speed limit setting are within the limits specified by the COLR.

24 months (continued)

TRM Miscellaneous Test Requirements 2.1.a Quad Cities 1 and 2 2.1.a-2 Revision 0 SURVEILLANCE REQUIREMENTS (continued)

SURVEILLANCE FREQUENCY TSR 2.1.a.2 ---------------------------NOTE-------------------------------

TSR 2.1.a.2 provides the scram time limits for <800 psig steam dome pressure to satisfy Technical Specification SR 3.1.4.3 and is only applicable in MODES 1 and 2. ------------------------------------------------------------------

Verify each affected control rod scram time is within limits of Technical Specification Table 3.1.4-1 with any reactor pressure. The control rod scram time acceptance criteria shall be <

2.04 seconds from fully withdrawn position to 90% insertion at 0 psig reactor steam dome pressure.

Prior to declaring

control rod OPERABLE after work on the control rod or CRD System that could affect scram time

TSR 2.1.a.3 -----------------------------NOTE-------------------------------

Only applicable when associated diesel generator is required to be OPERABLE. --------------------------------------------------------------------

Drain each diesel generator fuel oil storage tank, remove the accumulated sediment, and clean the

tank.

10 years

TRM TLCO Applicability 3.0 Quad Cities 1 and 2 3.0-1 Revision QDC-TRM-05-003 3.0 TECHNICAL REQUIREMENTS MANUAL LIMITING CONDITION FOR OPERATION (TLCO) APPLICABILITY

TLCO 3.0.a TLCOs shall be met during the MODES or other specified conditions in the Applicability, except as provided in TLCO 3.0.b. TLCO 3.0.b Upon discovery of a failure to meet a TLCO, the Required Actions of the associated Conditions shall be met, except as provided in TLCO 3.0.e.

If the TLCO 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. TLCO 3.0.c When a TLCO is not met and the associated ACTIONS are not met, an associated ACTION is not provided, or if directed by the associated ACTIONS, 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:

a. Implement appropriate compensatory actions as needed;
b. Verify that the plant is not in an unanalyzed condition(s) or that a required safety function is not compromised by the inoperabilities;

and c. Within 12 hours1.388889e-4 days <br />0.00333 hours <br />1.984127e-5 weeks <br />4.566e-6 months <br />, obtain Station Duty Officer approval of the compensatory actions and the plan for exiting TLCO 3.0.c.

Exceptions to this TLCO are stated in the individual TLCOs.

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

TLCO 3.0.c is only applicable in MODES 1, 2, and 3. TLCO 3.0.d When an TLCO is not met, entry into a MODE or other specified condition in the Applicability shall only be made:

1. 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;

(continued)

TRM TLCO Applicability 3.0 Quad Cities 1 and 2 3.0-2 Revision QDC-TRM-05-003 3.0 TLCO APPLICABILITY (continued)

TLCO 3.0.d 2. 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 TLCO are stated in the individual TLCOs, or

3. When an allowance is stated in the individual value, parameter, or other TLCO.

This TLCO 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.

TLCO 3.0.e 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 TLCO 3.0.b for the system returned to service under administrative control to perform the testing required to demonstrate OPERABILITY.

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

(continued)

TRM TSR Applicability 3.0 Quad Cities 1 and 2 3.0-3 Revision QC-TRM-05-002 3.0 TECHNICAL REQUIREMENTS MANUAL SURVEILLANCE REQUIREMENT (TSR)

APPLICABILITY

TSR 3.0.a TSRs shall be met during the MODES or other specified conditions in the Applicability for individual TLCOs, unless otherwise stated in the TSR.

Failure to meet a TSR, whether such failure is experienced during the performance of the TSR or between performances of the TSR, shall be failure to meet the TLCO. Failure to perform a TSR within the specified Frequency shall be failure to meet the TLCO except as provided in TSR 3.0.c. TSRs do not have to be performed on inoperable equipment or variables outside specified limits.

TSR 3.0.b The specified Frequency for each TSR is met if the TSR 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 TSR are stated in the individual TSRs.

TSR 3.0.c If it is discovered that a TSR was not performed within its specified Frequency, then compliance with the requirement to declare the TLCO 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 TSR. 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 TSR is not performed within the delay period, the TLCO must immediately be declared not met, and the applicable Condition(s) must be entered.

When the TSR is performed within the delay period and the TSR is not met, the TLCO must immediately be declared not met, and the applicable Condition(s) must be entered. (continued)

TRM TSR Applicability 3.0 Quad Cities 1 and 2 3.0-4 Revision QC-TRM-05-003 3.0 TSR APPLICABILITY (continued)

TSR 3.0.d Entry into a MODE or other specified condition in the Applicability of an TLCO shall only be made when the TLCO's TSRs have been met within their specified Frequency, except as provided by TSR 3.0.c. When an TLCO is not met due to TSRs not having been met, entry into a MODE or other specified condition in the Applicability shall only be made in accordance with TLCO 3.0.d.

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.

TSR 3.0.e TSRs shall apply to each unit individually, unless otherwise indicated.

This Section Intentionally Blank

Technical Requirements Manual Section 3.1 Not Used TRM Control Rod Block Instrumentation 3.3.a Quad Cities 1 and 2 3.3.a-1 Revision 0 3.3 INSTRUMENTATION

3.3.a Control Rod Block Instrumentation

TLCO 3.3.a The control rod block instrumentation for each Function in Table T3.3.a-1 shall be OPERABLE.

APPLICABILITY: According to Table T3.3.a-1.

ACTIONS


NOTE------------------------------------------------------------ Separate Condition entry is allowed for each channel.


CONDITION REQUIRED ACTION COMPLETION TIME

A. For Functions 1.a, 1.b, 1.c, 1.d, 2.a, 2.b, 2.c, 3.a, 3.b, 3.c, and 3.d, one required channel inoperable.

A.1 Restore inoperable channel to OPERABLE status.

7 days B. For Functions 4.a and 4.b, one or more required channels inoperable.

B.1 Place inoperable channels in trip.

12 hours1.388889e-4 days <br />0.00333 hours <br />1.984127e-5 weeks <br />4.566e-6 months <br /> (continued)

TRM Control Rod Block Instrumentation 3.3.a Quad Cities 1 and 2 3.3.a-2 Revision 0 ACTIONS CONDITION REQUIRED ACTION COMPLETION TIME C. For Functions 1.a, 1.b, 1.c, 1.d, 2.a, 2.b, 2.c, 3.a, 3.b, 3.c, and 3.d, two or more required channels

inoperable.

OR Required Action and associated Completion

Time of Condition A not met. C.1 Place inoperable channels in trip.

1 hour1.157407e-5 days <br />2.777778e-4 hours <br />1.653439e-6 weeks <br />3.805e-7 months <br />

TRM Control Rod Block Instrumentation 3.3.a Quad Cities 1 and 2 3.3.a-3 Revision 0 SURVEILLANCE REQUIREMENTS


NOTES--------------------------------------------------------------- 1. Refer to Table T3.3.a-1 to determine which TSRs apply to each Control Rod Block Function.

2. When a channel is placed in an inoperable status solely for performance of required Surveillances, entry into associated Conditions and Required Actions may be delayed for up to 6 hours6.944444e-5 days <br />0.00167 hours <br />9.920635e-6 weeks <br />2.283e-6 months <br /> provided the associated Function maintains Control Rod Block capability. ----------------------------------------------------------------------------------------------------------------------------

SURVEILLANCE FREQUENCY TSR 3.3.a.1 -------------------------------NOTE-------------------------------

Not required to be performed when entering MODE 2 from MODE 1 until 12 hours1.388889e-4 days <br />0.00333 hours <br />1.984127e-5 weeks <br />4.566e-6 months <br /> after entering MODE 2. ----------------------------------------------------------------------

Perform CHANNEL FUNCTIONAL TEST.

7 days TSR 3.3.a.2 -----------------------------NOTE--------------------------------

For Function 1.d, not required to be performed when entering MODE 2 from MODE 1 until 12 hours1.388889e-4 days <br />0.00333 hours <br />1.984127e-5 weeks <br />4.566e-6 months <br /> after entering MODE 2 ----------------------------------------------------------------------

Perform CHANNEL FUNCTIONAL TEST.

92 days TSR 3.3.a.3 --------------------------------NOTES-----------------------------

1. For Function 1.d, not required to be performed when entering MODE 2 from MODE 1 until 12 hours1.388889e-4 days <br />0.00333 hours <br />1.984127e-5 weeks <br />4.566e-6 months <br /> after entering MODE 2.
2. Neutron detectors are excluded.
3. For Function 1.a, not required for the flow portion of the channels. -----------------------------------------------------------------------

Perform CHANNEL CALIBRATION.

184 days (continued)

TRM Control Rod Block Instrumentation 3.3.a Quad Cities 1 and 2 3.3.a-4 Revision 0 SURVEILLANCE REQUIREMENTS SURVEILLANCE FREQUENCY TSR 3.3.a.4 -----------------------------NOTE----------------------------- 1. Not required to be performed when entering MODE 2 from MODE 1 until 12 hours1.388889e-4 days <br />0.00333 hours <br />1.984127e-5 weeks <br />4.566e-6 months <br /> after entering MODE 2.

2. Neutron detectors are excluded. ------------------------------------------------------------------

Perform CHANNEL CALIBRATION.

18 months TSR 3.3.a.5 Perform CHANNEL FUNCTIONAL TEST.

24 months TSR 3.3.a.6 -----------------------------NOTE-----------------------------

1. Not required to be performed when entering MODE 2 from MODE 1 until 12 hours1.388889e-4 days <br />0.00333 hours <br />1.984127e-5 weeks <br />4.566e-6 months <br /> after

entering MODE 2.

2. Neutron detectors are excluded. ------------------------------------------------------------------

Perform CHANNEL CALIBRATION.

24 months TRM Control Rod Block Instrumentation 3.3.a Quad Cities 1 and 2 3.3.a-5 Revision QC-TRM-01-004 & QC-TRM-02-005 Table T3.3.a-1 (page 1 of 2) Control Rod Block Instrumentation FUNCTION APPLICABLE MODES OR OTHER SPECIFIED CONDITIONS REQUIRED CHANNELS PER FUNCTION SURVEILLANCE REQUIREMENTS ALLOWABLE VALUE

1. Average Power Range Monitors
a. Flow Biased Neutron Flux-High 1 4 TSR 3.3.a.2 TSR 3.3.a.3

< 0.56W + 55.4%(a)RTP and 109.9% RTP b. Inoperative 1, 2, 5 (e) 4 TSR 3.3.a.2 N.A.

c. Downscale 1 4 TSR 3.3.a.2 TSR 3.3.a.3

> 3.5 % RTP d. Neutron Flux-High, Setdown 2,5 (e) 4 TSR 3.3.a.2 TSR 3.3.a.3

< 14.1 % RTP 2. Source Range Monitors

a. Detector not full in 2 (b)(d) 3 TSR 3.3.a.1 TSR 3.3.a.6 N.A. 5 (d)(h) 2 TSR 3.3.a.1 TSR 3.3.a.6 N.A. b. Upscale 2 (c) 3 TSR 3.3.a.1 TSR 3.3.a.4

< 2.8 x 10 5 cps 5 (h) 2 TSR 3.3.a.1 TSR 3.3.a.4

<2.8 x 10 5 cps c. Inoperative

2 (c) 3 TSR 3.3.a.1 N.A.

5 (h) 2 TSR 3.3.a.1 N.A.

(continued)

(a) Allowable Value is 0.56W + 51.2% RTP and 109.9% RTP when reset for single loop operation per Technical Specification 3.4.1, "Recirculation Loops Operating." (b) With the Intermediate Range Monitor (IRM) channels are on range 2 or below.

(c) With IRM channels on range 7 or below.

(d) With detector count rate less than or equal to the Allowable Value (Detector Not Full In AV 163 cps).

(e) Required to be OPERABLE only during SHUTDOWN MARGIN demonstrations performed per Specification 3.10.7.

TRM Control Rod Block Instrumentation 3.3.a Quad Cities 1 and 2 3.3.a-6 Revision QC-TRM-02-005 Table T3.3.a-1 (page 2 of 2) Control Rod Block Instrumentation FUNCTION APPLICABLE MODES OR OTHER SPECIFIED CONDITIONS REQUIRED CHANNELS PER FUNCTION SURVEILLANCE REQUIREMENTS ALLOWABLE VALUE 3. Intermediate Range Monitors

a. Detector not full in 2, 5 (h) 6 TSR 3.3.a.1 TSR 3.3.a.6 N.A. b. Upscale 2, 5 (h) 6 TSR 3.3.a.1 TSR 3.3.a.6

< 112/125 of full scale c. Inoperative

2, 5 (h) 6 TSR 3.3.a.1 N.A. d. Downscale (f) 2, 5 (h) 6 TSR 3.3.a.1 TSR 3.3.a.6

> 5/125 of full scale 4. Scram Discharge Volume

a. Water Level-High 1, 2, 5 (g) 1 per bank TSR 3.3.a.2 <

25.5 gal b. Scram Discharge Volume Switch in Bypass

5 (g) 1 TSR 3.3.a.5 N.A.

(f) With IRM channels on range 2 or higher.

(g) With two or more control rods withdrawn. Not applicable to control rods removed per Technical Specification 3.10.4, "Single Control Rod Drive Removed-Refueling", or 3.10.5, "Multiple Control Rod Withdrawal-Refueling."

(h) With any control rod withdrawn from a core cell containing one or more fuel assemblies.

TRM PAM Instrumentation 3.3.b Quad Cities 1 and 2 3.3.b-1 Revision QC-TRM-05-008 3.3 INSTRUMENTATION

3.3.b Post Accident Monitoring (PAM) Instrumentation

TLCO 3.3.b The PAM instrumentation for each Function in Table T3.3.b-1 shall be OPERABLE.

APPLICABILITY: MODES 1 and 2.

ACTIONS


NOTE---------------------------------------------------------- Separate Condition entry is allowed for each Function. -----------------------------------------------------------------------------------------------------------------------------

CONDITION REQUIRED ACTION COMPLETION TIME

A. One or more Functions with one required channel

inoperable.

A.1 Restore required channel to OPERABLE status.

30 days B. One or more Functions with two required channels inoperable.

B.1 Restore one required channel to OPERABLE

status.

7 days --------------- NOTE --------------- Functions 1, 2, 3, and 4 only. ----------------------------------------

C. Required Action and associated Completion

Time of Condition A or B

not met.

C.1 Initiate alternate method of monitoring the appropriate

parameters.

AND C.2 Prepare a corrective action program report.

Immediately

Immediately

TRM PAM Instrumentation 3.3.b Quad Cities 1 and 2 3.3.b-2 Revision QC-TRM-05-008 ACTIONS --------------- NOTE --------------- Functions 5 and 6 only. ----------------------------------------

D. Required Action and associated Completion Time of Condition A or B not met. D.1 Prepare a corrective action program report.

AND D.2 Initiate alternate method of monitoring the appropriate parameters.

OR D.3 Enter TLCO 3.0.c Immediately Immediately

TRM PAM Instrumentation 3.3.b Quad Cities 1 and 2 3.3.b-3 Revision QC-TRM-05-008 SURVEILLANCE REQUIREMENTS


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

1. These TSRs apply to each Function in Table T3.3.b-1, except where identified in the TSR.
2. When a channel is placed in an inoperable status solely for performance of required Surveillances, entry into associated Conditions and Required Actions may be delayed for up to 6 hours6.944444e-5 days <br />0.00167 hours <br />9.920635e-6 weeks <br />2.283e-6 months <br /> provided the other required channel in the associated Function is OPERABLE. ------------------------------------------------------------------------------------------------------------------------------

SURVEILLANCE FREQUENCY TSR 3.3.b.1 Perform CHANNEL CHECK.

31 days TSR 3.3.b.2 ----------------------------NOTE--------------------------- Functions 5 and 6 only. ----------------------------------------------------------------

Perform CHANNEL CALIBRATION.

92 days TSR 3.3.b.3 ----------------------------NOTE--------------------------- 1. Function 3 only.

2. Neutron detectors are excluded.

Perform CHANNEL CALIBRATION.

18 months TSR 3.3.b.4 ----------------------------NOTE--------------------------- Functions 1, 2, and 4 only. ----------------------------------------------------------------

Perform CHANNEL CALIBRATION.

24 months

TRM PAM Instrumentation 3.3.b Quad Cities 1 and 2 3.3.b-4 Revision QC-TRM-05-008 Table T3.3.b-1 (page 1 of 1) Post Accident Monitoring Instrumentation FUNCTION REQUIRED CHANNELS

1. Drywell Air Temperature 2
2. Safety/Relief Valve Position Indicators-Acoustic and Temperature 2/valve (1 each)
3. Source Range Neutron Monitors 2 4. Torus Air Temperature 2 5. Drywell H 2 Concentration Analyzer and Monitor 2 6. Drywell O 2 Concentration Analyzer and Monitor 2

TRM Explosive Gas Monitoring Instrumentation 3.3.c Quad Cities 1 and 2 3.3.c-1 Revision 0 3.3 INSTRUMENTATION

3.3.c Explosive Gas Monitoring Instrumentation

TLCO 3.3.c The explosive gas monitoring instrumentation channels in Table T3.3.c-1 shall be OPERABLE with their Alarm/Trip Setpoints set to ensure that the limits of the Explosive Gas and St orage Tank Radioactivity Monitoring Program are not exceeded.

APPLICABILITY: During operation of the Offgas Holdup System.

ACTIONS


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

Separate Condition entry is allowed for each channel.


CONDITION REQUIRED ACTION COMPLETION TIME A. Required channel inoperable.

A.1.1 Take grab samples.

OR Once per 4 hours4.62963e-5 days <br />0.00111 hours <br />6.613757e-6 weeks <br />1.522e-6 months <br />

(continued)

TRM Explosive Gas Monitoring Instrumentation 3.3.c Quad Cities 1 and 2 3.3.c-2 Revision 0 ACTIONS CONDITION REQUIRED ACTION COMPLETION TIME A. (continued)

A.1.2 ---------NOTE--------

Only applicable if recombiner(s) temperature remains constant and THERMAL POWER has not

changed.


Take grab samples.

AND A.2 Analyze grab samples.

AND A.3.1 Restore channel to OPERABLE status.

OR A.3.2 Prepare a corrective action program report.

Once per 8 hours9.259259e-5 days <br />0.00222 hours <br />1.322751e-5 weeks <br />3.044e-6 months <br />

Within 4 hours4.62963e-5 days <br />0.00111 hours <br />6.613757e-6 weeks <br />1.522e-6 months <br /> following each grab

sample

30 days

30 days

TRM Explosive Gas Monitoring Instrumentation 3.3.c Quad Cities 1 and 2 3.3.c-3 Revision QC-TRM-01-006 SURVEILLANCE REQUIREMENTS SURVEILLANCE FREQUENCY TSR 3.3.c.1 Perform CHANNEL CHECK.

24 hours2.777778e-4 days <br />0.00667 hours <br />3.968254e-5 weeks <br />9.132e-6 months <br /> TSR 3.3.c.2 Perform CHANNEL FUNCTIONAL TEST.

31 days TSR 3.3.c.3 Perform CHANNEL CALIBRATION.

180 days

TRM Explosive Gas Monitoring Instrumentation 3.3.c Quad Cities 1 and 2 3.3.c-4 Revision 0 Table T3.3.c-1 (page 1 of 1)

Explosive Gas Monitoring Instrumentation INSTRUMENT REQUIRED CHANNELS Main Condenser Offgas Treatment System Explosive Gas Monitoring System-Hydrogen Monitor 1

TRM Suppression Chamber and Drywell Spray Actuation Instrumentation 3.3.d Quad Cities 1 and 2 3.3.d-1 Revision 0 3.3 INSTRUMENTATION

3.3.d Suppression Chamber and Drywell Spray Actuation Instrumentation

TLCO 3.3.d The suppression chamber and drywell spray actuation instrumentation shown in Table 3.3.d-1 shall be OPERABLE.

APPLICABILITY: MODES 1, 2, and 3.

ACTIONS


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

Separate Condition entry is allowed for each channel.


CONDITION REQUIRED ACTION COMPLETION TIME A. One or more channels inoperable in one trip system.

A.1 Place one inoperable channel in trip such that it will not prevent containment spray.

24 hours2.777778e-4 days <br />0.00667 hours <br />3.968254e-5 weeks <br />9.132e-6 months <br /> B. One or more channels inoperable in both trip systems.

OR Required Action and Associated Completion Time of Condition A not

met.

B.1 Declare Suppression Chamber and Drywell Spray

Actuation mode of the Residual Heat Removal

system inoperable.

Immediately

TRM Suppression Chamber and Drywell Spray Actuation Instrumentation 3.3.d Quad Cities 1 and 2 3.3.d-2 Revision 0 SURVEILLANCE REQUIREMENTS


NOTES----------------------------------------------------------

1. Refer to Table T3.3.d-1 to determine which TSRs apply to each Function.
2. When a channel is placed in an inoperable status solely for performance of required Surveillances, entry into associated Conditions and Required Actions may be delayed for up to 6 hours6.944444e-5 days <br />0.00167 hours <br />9.920635e-6 weeks <br />2.283e-6 months <br /> provided the associated Function maintains suppression chamber and

drywell spray actuation capability. ------------------------------------------------------------------------------------------------------------------------------

SURVEILLANCE FREQUENCY TSR 3.3.d.1 Perform CHANNEL CHECK.

24 hours2.777778e-4 days <br />0.00667 hours <br />3.968254e-5 weeks <br />9.132e-6 months <br /> TSR 3.3.d.2 Perform CHANNEL FUNCTIONAL TEST.

92 days TSR 3.3.d.3 Calibrate the trip units.

92 days TSR 3.3.d.4 Perform CHANNEL CALIBRATION.

92 days TSR 3.3.d.5 Perform CHANNEL CALIBRATION.

24 months

TSR 3.3.d.6 Perform LOGIC SYSTEM FUNCTIONAL TEST.

24 months

TRM Suppression Chamber and Drywell Spray Actuation Instrumentation 3.3.d Quad Cities 1 and 2 3.3.d-3 Revision 0 Table T3.3.d-1 (page 1 of 1) Suppression Chamber and Drywell Spray Actuation Instrumentation FUNCTION REQUIRED NUMBER OF CHANNELS PER TRIP SYSTEM SURVEILLANCE REQUIREMENTS ALLOWABLE VALUE 1. Drywell Pressure-High (permissive) 2 TSR 3.3.d.2 TSR 3.3.d.4 TSR 3.3.d.6

> 0.56 psig and < 1.44 psig

2. Reactor Vessel Water Level-Low (permissive) 1 TSR 3.3.d.1 TSR 3.3.d.2 TSR 3.3.d.3 TSR 3.3.d.5 TSR 3.3.d.6

> -175.7 inches TRM Toxic Gas Monitoring System 3.3.e Quad Cities 1 and 2 3.3.e-1 Revision QC-TRM-03-001 3.3 INSTRUMENTATION

3.3.e Toxic Gas Monitoring System

TLCO 3.3.e The Toxic Gas Monitoring System shall be OPERABLE.

APPLICABILITY: MODES 1, 2, 3, 4, and 5.

ACTIONS CONDITION REQUIRED ACTION COMPLETION TIME

A. Toxic Gas Monitoring System inoperable.

B. One Toxic Gas Monitor channel inoperable.

C. Required Action and associated Completion Time of Condition A or B not met.

A.1 Initiate and maintain Control Room Emergency Ventilation System in the isolation mode of operation.

B.1 Restore channel to OPERABLE status.

C.1 Prepare a corrective action program report (Condition Report).

1 hour1.157407e-5 days <br />2.777778e-4 hours <br />1.653439e-6 weeks <br />3.805e-7 months <br /> 30 days Immediately

SURVEILLANCE REQUIREMENTS SURVEILLANCE FREQUENCY TSR 3.3.e.1 Perform CHANNEL CHECK.

12 hours1.388889e-4 days <br />0.00333 hours <br />1.984127e-5 weeks <br />4.566e-6 months <br /> TSR 3.3.e.2 Perform CHANNEL FUNCTIONAL TEST.

92 days TSR 3.3.e.3 Perform CHANNEL CALIBRATION. The Allowable Value shall be < 50 ppm concentration of ammonia.

12 months TRM RWCU Area Temperature Monitoring 3.3.f Quad Cities 1 and 2 3.3.f-1 Revision 0 3.3 INSTRUMENTATION

3.3.f Reactor Water Cleanup (RWCU) Area Temperature Monitoring

TLCO 3.3.f Temperature monitors listed in Table T3.3f-1 shall be OPERABLE.

APPLICABILITY: MODES 1, 2, and 3 with the RWCU system unisolated.

ACTIONS ------------------------------------------------------------NOTE----------------------------------------------------------

Separate Condition entry is allowed for each temperature monitor.


CONDITION REQUIRED ACTION COMPLETION TIME A. With one temperature monitor inoperable.

A.1 Restore inoperable temperature monitor to OPERABLE status.

AND 30 days

(continued)

TRM RWCU Area Temperature Monitoring 3.3.f Quad Cities 1 and 2 3.3.f-2 Revision 0 ACTIONS CONDITION REQUIRED ACTION COMPLETION TIME A. (continued)

A.2.1 ---------NOTE--------- For RWCU heat exchanger and Phase

Separator Rooms only. ----------------------

Observe area temperature.

AND A.2.2 ---------NOTE---------

For D Heater Bay area only. ----------------------

Monitor Non-Regenerative Heat Exchanger Discharge

temperature and RWCU

Discharge Pressure.

1 hour1.157407e-5 days <br />2.777778e-4 hours <br />1.653439e-6 weeks <br />3.805e-7 months <br /> AND twice per shift

thereafter

1 hour1.157407e-5 days <br />2.777778e-4 hours <br />1.653439e-6 weeks <br />3.805e-7 months <br /> AND twice per shift

thereafter

B. With less than the minimum requirement in any area.

OR One or more Main Steam Tunnel Temperature Isolation Bypass switches at panel 901-4 in bypass.

OR Required Action and Associated Completion Time of Condition A not

met.

B.1 Isolate the RWCU system.

1 hour1.157407e-5 days <br />2.777778e-4 hours <br />1.653439e-6 weeks <br />3.805e-7 months <br /> TRM RWCU Area Temperature Monitoring 3.3.f Quad Cities 1 and 2 3.3.f-3 Revision 0 SURVEILLANCE REQUIREMENTS


NOTE------------------------------------------------------------ TSRs apply to each monitor in Table T3.3.f-1.


SURVEILLANCE FREQUENCY TSR 3.3.f.1 --------------------------NOTE--------------------------------

Not required for Main Steam Tunnel Temperature switches. ------------------------------------------------------------------

Perform a resistance check of the temperature monitor.

24 months TSR 3.3.f.2 Perform a functional test of the temperature monitor.

24 months TSR 3.3.f.3 Perform a logic test of the temperature monitor.

24 months TSR 3.3.f.4 Perform a calibration of the temperature monitor.

24 months TRM RWCU Area Temperature Monitoring 3.3.f Quad Cities 1 and 2 3.3.f-4 Revision 0 Table T3.3.f-1 (page 1 of 1) RWCU Temperature Monitoring PARAMETER INSTRUMENT AFFECTED LOGIC MINIMUM REQUIREMENT RWCU Heat Exchanger Room Temperature 1(2)-1291-60K 1(2)-1291-60L RWCU Isolation Panel 2201(2)-77B 1 1(2)-1291-60N 1(2)-1291-60P RWCU Isolation Panel 2201(2)-77A 1 Phase Separator Area 1(2)-1291-60J 1(2)-1291-60M RWCU System Panels 2201-(2)-77A and 2201(2)-77B 2 D Heater Bay 1(2)-1291-60R 1(2)-1291-60S RWCU System Panel

2201-(2)-77B 1 1(2)-1291-60T 1(2)-1291-60U RWCU System Panel

2201-(2)-77A 1 MST Temperature Isolation Bypass (a) NA RWCU Inboard and Outboard Isolation Valves NA (a) Either bypass switch at panel 901(2)-4 in bypass.

TRM Structural Integrity 3.4.a Quad Cities 1 and 2 3.4.a-1 Revision QC-TRM-08-005 3.4 REACTOR COOLANT SYSTEM (RCS)

[TRM Section 3.4.a was deleted under TRM change QC-TRM-08-005.]

TRM RCS Chemistry 3.4.b Quad Cities 1 and 2 3.4.b-1 Revision QC-TRM-01-005 3.4 REACTOR COOLANT SYSTEM

3.4.b Reactor Coolant System (RCS) Chemistry

TLCO 3.4.b The chemistry of the RCS shall be maintained within the limits specified in Table T3.4.b-1.

APPLICABILITY: MODES 1, 2, and 3.

ACTIONS CONDITION REQUIRED ACTION COMPLETION TIME

A. RCS chemistry not within limits in MODE 1.

A.1 Determine chlorides.

AND

A.2 Perform TSR 3.4.b.4.

AND

A.3 Restore RCS chemistry to within limits.

Once per 8 hours9.259259e-5 days <br />0.00222 hours <br />1.322751e-5 weeks <br />3.044e-6 months <br /> when conductivity is not within limit

Once per 24 hours2.777778e-4 days <br />0.00667 hours <br />3.968254e-5 weeks <br />9.132e-6 months <br /> when conductivity is not within limit

72 hours8.333333e-4 days <br />0.02 hours <br />1.190476e-4 weeks <br />2.7396e-5 months <br /> AND 336 hours0.00389 days <br />0.0933 hours <br />5.555556e-4 weeks <br />1.27848e-4 months <br /> cumulative in the past 365 days

B. Required Action and associated Completion Time of Condition A not met.

B.1 Be in MODE 2.

8 hours9.259259e-5 days <br />0.00222 hours <br />1.322751e-5 weeks <br />3.044e-6 months <br /> (continued)

TRM RCS Chemistry 3.4.b Quad Cities 1 and 2 3.4.b-2 Revision QC-TRM-01-005 ACTIONS CONDITION REQUIRED ACTION COMPLETION TIME C. Conductivity

> 10 µmho/cm at 25 o C in MODE 1.

OR Chloride concentration

> 0.5 ppm in MODE 1.

C.1 Be in MODE 2.

12 hours1.388889e-4 days <br />0.00333 hours <br />1.984127e-5 weeks <br />4.566e-6 months <br /> D. -------------NOTE------------- Not applicable during Noble Metal Chemical Applications (injection and cleanup periods). -----------------------------------

RCS chemistry not within required limits in MODE 2

or 3. D.1 Determine chlorides.

AND D.2 Perform TSR 3.4.b.4.

AND D.3 Restore RCS chemistry to within limits.

Once per 8 hours9.259259e-5 days <br />0.00222 hours <br />1.322751e-5 weeks <br />3.044e-6 months <br /> when conductivity is not within limit

Once per 24 hours2.777778e-4 days <br />0.00667 hours <br />3.968254e-5 weeks <br />9.132e-6 months <br />

when conductivity is not within limit

48 hours5.555556e-4 days <br />0.0133 hours <br />7.936508e-5 weeks <br />1.8264e-5 months <br /> E. Required Action and associated Completion

Time of Condition D not

met.

E.1 Be in MODE 3.

AND E.2 Be in MODE 4.

12 hours1.388889e-4 days <br />0.00333 hours <br />1.984127e-5 weeks <br />4.566e-6 months <br />

36 hours4.166667e-4 days <br />0.01 hours <br />5.952381e-5 weeks <br />1.3698e-5 months <br /> F. RCS chemistry not within required limits in MODE 3

during Noble Metal

Chemical Application (injection and cleanup).

F.1 Initiate action to be in MODE 4.

Immediately

TRM RCS Chemistry 3.4.b Quad Cities 1 and 2 3.4.b-3 Revision QC-TRM-01-005 SURVEILLANCE REQUIREMENTS SURVEILLANCE FREQUENCY TSR 3.4.b.1 --------------------------------NOTE------------------------------

Only applicable when the continuous recording conductivity monitor is inoperable. -----------------------------------------------------------------------

Obtain an in-line conductivity measurement of the reactor coolant.

4 hours4.62963e-5 days <br />0.00111 hours <br />6.613757e-6 weeks <br />1.522e-6 months <br /> TSR 3.4.b.2 Analyze a sample of the reactor coolant for chlorides and conductivity.

72 hours8.333333e-4 days <br />0.02 hours <br />1.190476e-4 weeks <br />2.7396e-5 months <br /> TSR 3.4.b.3 -----------------------------NOTE-------------------------------

Only applicable during Noble Metal application (injection and cleanup). ---------------------------------------------------------------------

Analyze a sample of the reactor coolant for pH.

72 hours8.333333e-4 days <br />0.02 hours <br />1.190476e-4 weeks <br />2.7396e-5 months <br /> TSR 3.4.b.4 Perform a CHANNEL CHECK of the continuous conductivity monitor with an in-line flow cell.

7 days TRM RCS Chemistry 3.4.b Quad Cities 1 and 2 3.4.b-4 Revision QC-TRM-01-005 Table T3.4.b-1 (page 1 of 1) Reactor Coolant System Chemistry Limits MODE CHLORIDES (ppm) CONDUCTIVITY

(µmhos/cm at 25 o C) 1 < 0.2 < 1.0 2, 3 (a) < 0.1 < 2.0 3 (b) < 0.1 < 10.0 (a) Except during Noble Metal Chemical Applications.

(b) During Noble Metal Chemical Applications.

TRM RHR Drywell Spray 3.6.a Quad Cities 1 and 2 3.6.a-1 Revision 0 3.6 CONTAINMENT SYSTEMS

3.6.a Residual Heat Removal (RHR) Drywell Spray

TLCO 3.6.a Two RHR drywell spray subsystems shall be OPERABLE.

APPLICABILITY: MODES 1, 2, and 3.

ACTIONS CONDITION REQUIRED ACTION COMPLETION TIME

A. One RHR drywell spray subsystem inoperable.

A.1 Restore RHR drywell spray subsystem to OPERABLE status. 7 days B. Two RHR drywell spray subsystems inoperable.

B.1 Restore one RHR drywell spray subsystem to OPERABLE status.

8 hours9.259259e-5 days <br />0.00222 hours <br />1.322751e-5 weeks <br />3.044e-6 months <br /> C. Required Action and associated Completion Time not met.

C.1 Enter TLCO 3.0.c.

Immediately

TRM RHR Drywell Spray 3.6.a Quad Cities 1 and 2 3.6.a-2 Revision 0 SURVEILLANCE REQUIREMENTS SURVEILLANCE FREQUENCY TSR 3.6.a.1 Verify each RHR drywell spray subsystem manual and power operated valve in the flow path that is not locked, sealed, or otherwise secured in position, is in the correct position or can be aligned to the correct position.

31 days TSR 3.6.a.2 Verify each RHR drywell spray nozzle is unobstructed by performance of an air or smoke flow test of the RHR drywell spray nozzles.

10 years TRM RHRSW System-Shutdown 3.7.a Quad Cities 1 and 2 3.7.a-1 Revision QC-TRM-07-003 3.7 PLANT SYSTEMS

3.7.a Residual Heat Removal Service Water (RHRSW) System-Shutdown

TLCO 3.7.a For each required OPERABLE RHR system, a RHRSW subsystem shall be OPERABLE.

APPLICABILITY: MODES 4 and 5, During movement of recently irradiated fuel assemblies in secondary containment, During operations with a potential for draining the reactor vessel.

ACTIONS CONDITION REQUIRED ACTION COMPLETION TIME

A. One or more required RHRSW subsystems

inoperable.

A.1 Declare supported safety-related equipment

inoperable.

Immediately

SURVEILLANCE REQUIREMENTS SURVEILLANCE FREQUENCY TSR 3.7.a.1 Verify each RHRSW manual, power operated, and automatic valve in the flow path, that is not locked, sealed, or otherwise secured in position, is in the correct position or can be aligned to the correct position.

31 days TRM DGCW-Shutdown 3.7.b Quad Cities 1 and 2 3.7.b-1 Revision 0 3.7 PLANT SYSTEMS

3.7.b Diesel Generator Cooling Water (DGCW) System-Shutdown

TLCO 3.7.b The DGCW System shall be OPERABLE with:

1. One OPERABLE DGCW pump per required subsystem, and
2. An OPERABLE flow path capable of taking suction from the Ultimate Heat Sink and transferring water to the associated diesel generator.
3. An operable DGCW pump capable of transferring cooling water to the Emergency Core Cooling System (ECCS) room emergency

coolers.

APPLICABILITY: MODES 4 and 5 when the associated diesel generator or ECCS is required to be OPERABLE.

ACTIONS


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

Separate Condition entry is allowed for each DGCW subsystem.


CONDITION REQUIRED ACTION COMPLETION TIME

A. One required DGCW subsystem inoperable and not capable of supporting its associated

DG.

A.1 Declare associated diesel generator inoperable.

Immediately (continued)

TRM DGCW-Shutdown 3.7.b Quad Cities 1 and 2 3.7.b-2 Revision 0 ACTIONS CONDITION REQUIRED ACTION COMPLETION TIME B. Required DGCW subsystem inoperable and not capable of supporting the ECCS room emergency

coolers.

B.1 Align a DGCW subsystem to the ECCS room

emergency coolers.

OR B.2 Declare the supported ECCS components inoperable.

1 hour1.157407e-5 days <br />2.777778e-4 hours <br />1.653439e-6 weeks <br />3.805e-7 months <br />

1 hour1.157407e-5 days <br />2.777778e-4 hours <br />1.653439e-6 weeks <br />3.805e-7 months <br /> SURVEILLANCE REQUIREMENTS SURVEILLANCE FREQUENCY TSR 3.7.b.1 Verify each required DGCW subsystem valve in the flow path, that is not locked, sealed, or otherwise secured in position, is in the correct position or can be aligned to the correct position.

31 days TSR 3.7.b.2 Verify each required DGCW pump starts automatically on an actual or simulated initiation signal.

24 months

TRM UHS-Shutdown 3.7.c Quad Cities 1 and 2 3.7.c-1 Revision 0 3.7 PLANT SYSTEMS

3.7.c Ultimate Heat Sink (UHS)-Shutdown

TLCO 3.7.c The UHS shall be OPERABLE.

APPLICABILITY: MODES 4 and 5, During movement of irradiated fuel assemblies in secondary containment, During CORE ALTERATIONS, During operations with the potential for draining the reactor vessel.

ACTIONS CONDITION REQUIRED ACTION COMPLETION TIME A. UHS inoperable in MODE 4 and 5.

A.1 Declare the required Residual Heat Removal Service Water subsystems and Diesel Generator Cooling Water subsystems inoperable.

Immediately B. UHS inoperable during movement of irradiated fuel assemblies in

secondary containment, during CORE

ALTERATIONS or during operations with the potential for draining the

reactor vessel.

B.1 Declare the required Diesel Generator Cooling Water subsystems inoperable.

Immediately

TRM UHS-Shutdown 3.7.c Quad Cities 1 and 2 3.7.c-2 Revision 0 SURVEILLANCE REQUIREMENTS SURVEILLANCE FREQUENCY TSR 3.7.c.1 Verify average water temperature is <

95 o F.

24 hours2.777778e-4 days <br />0.00667 hours <br />3.968254e-5 weeks <br />9.132e-6 months <br /> TSR 3.7.c.2 Verify water level is > 568 ft mean sea level.

24 hours2.777778e-4 days <br />0.00667 hours <br />3.968254e-5 weeks <br />9.132e-6 months <br /> TRM Liquid Holdup Tanks 3.7.d Quad Cities 1 and 2 3.7.d-1 Revision 0 3.7 PLANT SYSTEMS

3.7.d Liquid Holdup Tanks

TLCO 3.7.d The quantity of radioactive material contained in any outside tanks shall be less than or equal to the limits calculated in the OFFSITE DOSE CALCULATION MANUAL.

APPLICABILITY: At all times.

ACTIONS ----------------------------------------------------------------NOTE-------------------------------------------------------

Separate Conditions entry is allowed for each tank.


CONDITION REQUIRED ACTION COMPLETION TIME

A. Quantity of radioactive material in one or more of the outside tanks not

within limits.

A.1 Suspend all additions of radioactive material to the

affected tank(s).

AND A.2 Reduce affected tank contents to within limits.

Immediately

48 hours5.555556e-4 days <br />0.0133 hours <br />7.936508e-5 weeks <br />1.8264e-5 months <br />

TRM Liquid Holdup Tanks 3.7.d Quad Cities 1 and 2 3.7.d-2 Revision 0 SURVEILLANCE REQUIREMENTS SURVEILLANCE FREQUENCY TSR 3.7.d.1 ------------------------------NOTE------------------------------- Not required to be performed for 7 days if when tank(s) is empty at the start of addition. ---------------------------------------------------------------------

Determine the quantity of radioactive material of each outside tank is within limits by analyzing a representative sample of the tank's contents.

7 days when radioactive materials are being added to the

tank(s)

AND Once within 7

days after each

completion of

radioactive material to the tank TRM Explosive Gas Mixture 3.7.e Quad Cities 1 and 2 3.7.e-1 Revision 0 3.7 PLANT SYSTEMS

3.7.e Explosive Gas Mixture

TLCO 3.7.e The concentration of hydrogen in the Offgas Holdup System shall be <

4% by volume.

APPLICABILITY: During Offgas Holdup System operation.

ACTIONS CONDITION REQUIRED ACTION COMPLETION TIME A. Hydrogen concentration in the Offgas Holdup System > 4% by

volume.

A.1 Restore concentration to within limit.

48 hours5.555556e-4 days <br />0.0133 hours <br />7.936508e-5 weeks <br />1.8264e-5 months <br />

SURVEILLANCE REQUIREMENTS SURVEILLANCE FREQUENCY TSR 3.7.e.1 Verify hydrogen concentration in the Offgas Holdup System is < 4% by volume.

24 hours2.777778e-4 days <br />0.00667 hours <br />3.968254e-5 weeks <br />9.132e-6 months <br />

TRM Flood Protection 3.7.f Quad Cities 1 and 2 3.7.f-1 Revision 0 3.7 PLANT SYSTEMS

3.7.f Flood Protection

TLCO 3.7.f Flood protection shall be available for all required safe shutdown systems, components, and structures.

APPLICABILITY: At all times.

ACTIONS CONDITION REQUIRED ACTION COMPLETION TIME

A. Water level > 586 ft mean sea level USGS datum.

A.1 Initiate applicable flood protection measures.

Immediately

B. Water level > 594 ft mean sea level USGS datum.

OR Water level predicted to be > 594 ft mean sea

level USGS datum in <

72 hours8.333333e-4 days <br />0.02 hours <br />1.190476e-4 weeks <br />2.7396e-5 months <br />.

B.1 Be in MODE 3.

AND B.2 Be in MODE 4.

12 hours1.388889e-4 days <br />0.00333 hours <br />1.984127e-5 weeks <br />4.566e-6 months <br />

36 hours4.166667e-4 days <br />0.01 hours <br />5.952381e-5 weeks <br />1.3698e-5 months <br />

TRM Flood Protection 3.7.f Quad Cities 1 and 2 3.7.f-2 Revision 0 SURVEILLANCE REQUIREMENTS SURVEILLANCE FREQUENCY TSR 3.7.f.1 -----------------------------NOTE--------------------------------

Not required to be performed if water level is < 585.5 ft mean sea level USGS datum. ---------------------------------------------------------------------

Determine water level at the plant intake bay.

2 hours2.314815e-5 days <br />5.555556e-4 hours <br />3.306878e-6 weeks <br />7.61e-7 months <br /> TSR 3.7.f.2 Determine water level at the plant intake bay.

24 hours2.777778e-4 days <br />0.00667 hours <br />3.968254e-5 weeks <br />9.132e-6 months <br /> TRM Sealed Source Contamination 3.7.g Quad Cities 1 and 2 3.7.g-1 Revision 0 3.7 PLANT SYSTEMS

3.7.g Sealed Source Contamination

TLCO 3.7.g Each sealed source containing radioactive material either in excess of 100 µCi of beta and/or gamma emitting material or 5 µCi of alpha emitting material shall be free of 0.005 µCi of removable contamination.

APPLICABILITY: At all times.

ACTIONS


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

Separate Condition entry is allowed for each source.


CONDITION REQUIRED ACTION COMPLETION TIME

A. -------------NOTE-------------

Required Actions A.2 and A.3 shall be completed

whenever Condition A is

entered. ----------------------------------

One or more sealed sources with removable contamination not within limits. A.1 Withdraw the sealed source from use.

AND A.2.1 Initiate action to decontaminate and repair the sealed source.

OR Immediately

Immediately

(continued)

TRM Sealed Source Contamination 3.7.g Quad Cities 1 and 2 3.7.g-2 Revision 0 ACTIONS CONDITION REQUIRED ACTION COMPLETION TIME A. (continued)

A.2.2 Initiate action to dispose of the sealed source in accordance with NRC Regulations.

AND A.3 Initiate a corrective action program report.

Immediately

Immediately

TRM Sealed Source Contamination 3.7.g Quad Cities 1 and 2 3.7.g-3 Revision 0 SURVEILLANCE REQUIREMENTS


NOTES-------------------------------------------------------

1. Each sealed source shall be tested for leakage and/or contamination by the licensee, or other persons specifically authorized by the Commission or Agreement State.
2. The test method shall have a detection sensitivity of at least 0.005 µCi per test sample.
3. Startup sources and fission detectors previously subjected to core flux are exempted from the TSRs.
4. Sealed sources which are continuously enclosed within a shielded mechanism (i.e., sealed sources within radiation monitoring or boron measuring devices) are considered to be stored and need not be tested unless they are removed from the shielded mechanism. -------------------------------------------------------------------------------------------------------------------------

SURVEILLANCE FREQUENCY TSR 3.7.g.1 -----------------------------NOTE----------------------------

Only required to be performed on sources in use.


Perform leakage testing for all sealed sources containing radioactive materials with a half-life > 30 days (excluding Hydrogen 3) and in any form other

than gas.

184 days TSR 3.7.g.2 --------------------------NOTES----------------------------------

1. Only required to be performed on stored sources not in use.
2. Only required to be performed if not tested within the previous 6 months. ----------------------------------------------------------------------

Perform leakage testing for each sealed source and fission detector.

Prior to use or transfer to another licensee (continued)

TRM Sealed Source Contamination 3.7.g Quad Cities 1 and 2 3.7.g-4 Revision 0 SURVEILLANCE REQUIREMENTS SURVEILLANCE FREQUENCY TSR 3.7.g.3 --------------------------------NOTE-------------------------------

Only required to be performed on stored sources not in use. -----------------------------------------------------------------------

Perform leakage testing on sealed sources and fission detectors transferred without a certificate indicating the last test date.

Prior to use

TSR 3.7.g.4 ------------------------------NOTE---------------------------------

Only required to be performed on sealed startup sources and fission detectors not previously subjected to core flux. -----------------------------------------------------------------------

Perform leakage testing for each sealed startup source and fission detector.

Once within 31

days prior to being subjected to core flux or installed in the core or following repair or

maintenance to

sources TRM Snubbers 3.7.h Quad Cities 1 and 2 3.7.h-1 Revision QC-TRM-06-003 3.7 PLANT SYSTEMS

3.7.h Snubbers

TLCO 3.7.h All required snubbers shall be OPERABLE.


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

Not applicable to snubbers installed on nonsafety related systems unless their failure, or failure of the associated system(s), would adversely affect any safety related system. ----------------------------------------------------------------------------------------------

APPLICABILITY: MODES 1, 2, 3, and MODES 4, and 5 for snubbers located on systems required OPERABLE in those MODES.

ACTIONS ----------------------------------------------------------NOTE-----------------------------------------------------

Separate Condition entry is allowed for each snubber.


CONDITION REQUIRED ACTION COMPLETION TIME A. -------------NOTE------------- Required Action A.2 shall be completed whenever this Condition is entered due to a functional failure of the snubber(s). ----------------------------------

One or more required snubber(s) inoperable.

A.1 Replace or restore the snubber to OPERABLE status.

AND A.2 Perform an engineering evaluation on the attached

component to determine if

the component is acceptable for continued operation.

72 hours8.333333e-4 days <br />0.02 hours <br />1.190476e-4 weeks <br />2.7396e-5 months <br />

72 hours8.333333e-4 days <br />0.02 hours <br />1.190476e-4 weeks <br />2.7396e-5 months <br /> (continued)

TRM Snubbers 3.7.h Quad Cities 1 and 2 3.7.h-2 Revision QC-TRM-04-004 ACTIONS CONDITION REQUIRED ACTION COMPLETION TIME B. Required Actions and associated Completion Time not met.

B.1 Declare the attached system inoperable.

Immediately

SURVEILLANCE REQUIREMENTS


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

The provisions of TSR 3.0.b are applicable for all inspection intervals up to and including

48 months.


SURVEILLANCE FREQUENCY TSR 3.7.h.1 Examination and testing of safety related snubbers shall be performed in accordance with the 10CFR50.55a approved edition of the ASME OMa Code, Subsection

ISTD as denoted in the current revision of the Inservice Inspection Program Plan.

In accordance with the Augmented

Inservice

Inspection Program TRM Communications 3.9.a Quad Cities 1 and 2 3.9.a-1 Revision 0 3.9 REFUELING OPERATIONS

3.9.a Communications

TLCO 3.9.a Direct communications shall be maintained between the control room and refueling platform personnel.

APPLICABILITY: During CORE ALTERATIONS, except movement of control rods with their normal drive system.

ACTIONS CONDITION REQUIRED ACTION COMPLETION TIME

A. Direct communications not maintained.

A.1 Suspend CORE ALTERATIONS.

Immediately

SURVEILLANCE REQUIREMENTS SURVEILLANCE FREQUENCY TSR 3.9.a.1 Demonstrate direct communications between the control room and refueling platform personnel.

Once within 1 hour1.157407e-5 days <br />2.777778e-4 hours <br />1.653439e-6 weeks <br />3.805e-7 months <br /> prior to the start of CORE ALTERATIONS

AND Once per 12 hours1.388889e-4 days <br />0.00333 hours <br />1.984127e-5 weeks <br />4.566e-6 months <br />

thereafter

TRM Appendix A Primary Containment Isolation Devices Table A-2 Primary Containment Isolation Devices (Unit 2) (Page 1 of 14)

Quad Cities Unit 1 and 2 A2-1 Revision QC-TRM-09-005 Containment Penetration Number Valve Part Number Line Isolated

Valve Type Location Ref.

to Containment

Normal Status Max. Operating Time (sec)

Comments X-007A 0203-1A Main steam line AO Valve Inside Open 3T5 X-007A 0203-2A Main steam line AO Valve Outside Open 3T5 X-007A 0220-10A Main steam line - pressure test inboard stop Manual Outside Closed NA tap between 0203-1A & 2A X-007B 0203-1B Main steam line AO Valve Inside Open 3T5 X-007B 0203-2B Main steam line AO Valve Outside Open 3T5 X-007B 0220-10B Main steam line - pressure test inboard stop Manual Outside Closed NA tap between 0203-1B & 2B X-007C 0203-1C Main steam line AO Valve Inside Open 3T5 X-007C 0203-2C Main steam line AO Valve Outside Open 3T5 X-007C 0220-10C Main steam line - pressure test inboard stop Manual Outside Closed NA tap between 0203-1C & 2C X-007D 0203-1D Main steam line AO Valve Inside Open 3T5 X-007D 0203-2D Main steam line AO Valve Outside Open 3T5 X-007D 0220-10D Main steam line - pressure test inboard stop Manual Outside Closed NA tap between 0203-1D & 2D X-008 0220-1 Main steam line drain MO Valve Inside Closed 35 X-008 0220-2 Main steam line drain MO Valve Outside Closed 35 X-008 0220-5 Main steam line drain - pressure test inbd stop Manual Outside Closed NA tap between 0220-1 & 2 X-009A 0220-62A From reactor feedwater Check Outside Open NA X-009A 0220-58A From reactor feedwater Check Inside Open NA X-009A 0220-86A From Rx FW - local pressure test inboard stop Manual Outside Closed NA tap between 0220-58A & 62A X-009A 3299-130 From Rx FW - LLRT inboard valve Manual Inside Closed NA tap between 0220-58A & 62A X-009A 220-115A From Rx FW - inboard drain valve Manual Inside Closed NA tap between 0220-58A & Rx X-009A 3299-128 From Rx FW - inboard vent valve Manual Inside Closed NA tap between 0220-58A & Rx X-009B 0220-62B From reactor feedwater Check Outside Open NA X-009B 0220-58B From reactor feedwater Check Inside Open NA X-009B 0220-86B From Rx FW - local pressure test inboard stop Manual Outside Closed NA tap between 0220-58B & 62B X-009B 3299-124 From Rx FW - LLRT inboard valve Manual Inside Closed NA tap between 0220-58B & 62B X-009B 0220-115B From Rx FW - inboard drain valve Manual Inside Closed NA tap between 0220-58B & Rx X-009B 3299-122 From Rx FW - inboard vent valve Manual Inside Closed NA tap between 0220-58B & Rx TRM Appendix A Primary Containment Isolation Devices Table A-2 Primary Containment Isolation Devices (Unit 2) (Page 2 of 14)

Quad Cities Unit 1 and 2 A2-2 Revision QC-TRM-09-005 Containment Penetration Number Valve Part Number Line Isolated

Valve Type Location Ref.

to Containment

Normal Status Max. Operating Time (sec)

Comments X-010 1301-16 RCIC turbine steam supply MO Valve Inside Open 25 X-010 1301-17 RCIC turbine steam supply MO Valve Outside Open 25 X-010 1301-18A RCIC turbine steam supply - pressure test inboard stopManual Outside Closed NA tap between 1301-16 & 17 X-011 2301-4 HPCI turbine steam MO Valve Inside Open 50 X-011 2301-5 HPCI turbine steam MO Valve Outside Open 63 X-011 2301-16 HPCI turbine steam - pressure test inbd stop Manual Outside Closed NA tap between X-11 & 2301-5 X-012 1001-47 RHR reactor shutdown cooling supply MO Valve Outside Closed 40 X-012 1001-50 RHR reactor shutdown cooling supply MO Valve Inside Closed 40 X-012 1099-178 shutdown cooling supply-inboard vent Manual Inside Closed NA tap between 1001-50 & 47 X-012 1001-48 shutdown cooling supply - press test inbd stop Manual Outside Closed NA tap between 1001-50 & 47 X-012 1001-156A shutdown cooling supply - inboard vent Manual Outside Closed NA tap between 1001-50 & 47 X-012 1001-156D shutdown cooling supply - inboard vent Manual Outside Closed NA tap between 1001-50 & 47 X-013A 1001-29A RHR reactor LPCI / shutdown cooling injection MO Valve Outside Closed NA X-013A 1001-28A RHR reactor LPCI / shutdown cooling injection MO Valve Outside Open NA X-013A 1001-68A RHR reactor LPCI / shutdown cooling injection AO Check Inside Closed NA X-013A 1001-30A

'A' LPCI loop - pressure test inboard stop Manual Outside Closed NA tap between 1001-29A & 68A X-013B 1001-29B RHR reactor LPCI / shutdown cooling injection MO Valve Outside Closed NA X-013B 1001-28B RHR reactor LPCI / shutdown cooling injection MO Valve Outside Open NA X-013B 1001-68B RHR reactor LPCI / shutdown cooling injection AO Check Inside Closed NA X-013B 1001-31B 'B' LPCI / SDC loop - press test inboard stop Manual Outside Closed NA tap between 1001-29B & 68B X-014 1201-2 Reactor water cleanup supply MO Valve Inside Open 30 X-014 1201-5 Reactor water cleanup supply MO Valve Outside Open 38 X-014 RV-1299-87 Reactor water cleanup supply Relief Inside Closed NA X-014 1201-121 RWCU supply - pressure test inboard stop Manual Outside Closed NA tap between 1201-2 & 5 X-016A 1402-24A Core spray to reactor MO Valve Outside Open NA X-016A 1402-25A Core spray to reacto r MO Valve Outside Closed NA X-016A 1402-9A Core spray to reactor Check Inside Closed NA X-016A 1402-5A Core Spray to Rx - pump dsch press test inbd stop Manual Outside Closed NA tap between 1402-24A & 25A TRM Appendix A Primary Containment Isolation Devices Table A-2 Primary Containment Isolation Devices (Unit 2) (Page 3 of 14)

Quad Cities Unit 1 and 2 A2-3 Revision QC-TRM-09-005 Containment Penetration Number Valve Part Number Line Isolated

Valve Type Location Ref.

to Containment

Normal Status Max. Operating Time (sec)

Comments X-016A 1499-51 Core Spray to Rx-inboard vent Manual Outside Closed NA tap between 1402-24A & 25A X-016A 1402-33A Core Spray to Rx - pump dsch press test inbd stop Manual Outside Closed NA tap between 1402-25A & 9A X-016B 1402-24B Core spray to reactor MO Valve Outside Open NA X-016B 1402-25B Core spray to reacto r MO Valve Outside Closed NA X-016B 1402-9B Core spray to reactor Check Inside Closed NA X-016B 1402-5B Core Spray to Rx - pump dsch press test inbd stop Manual Outside Closed NA tap between 1402-24B & 25B X-016B 1402-33B Core Spray to Rx - pump dsch press test inbd stop Manual Outside Closed NA tap between 1402-25B & 9B X-018 2001-3 Drywell floor drain disc harge AO Valve Outside Closed 20 X-018 2001-4 Drywell floor drain disc harge AO Valve Outside Closed 20 X-018 2099-394 DW floor drain discharge - press test inbd stop Manual Outside Closed NA tap between 2001-3 & 4 X-019 2001-15 Drywell equipment drain disc harge AO Valve Outside Closed 20 X-019 2001-16 Drywell equipment drain disc harge AO Valve Outside Closed 20 X-019 2099-500 DW equip drain discharge - press test inbd stop Manual Outside Closed NA tap between 2001-15 & 16 X-020 4399-45 Clean demineralizer water in Manual Outside Closed NA X-020 4399-46 Clean demineralizer water in Check Outside Closed NA X-020 4399-347 Clean demin water in - pressure test inbd stop Manual Outside Closed NA tap between 4399-46 & X-20 X-020 4399-349 Clean demin water in - pressure test inbd stop Manual Outside Closed NA tap between 4399-45 & 46 X-021 4699-47 Service air to drywe ll Check Outside Closed NA X-021 4699-46 Service air to drywe ll Manual Outside Closed NA X-021 4699-314 Service air to drywell - press test inbd stop Manual Outside Closed NA tap between 4699-46 & 47 X-022 4799-155 Instrument air to drywell Check Inside Open NA X-022 4799-156 Instrument air to drywell Check Outside Open NA X-022 4799-157 Instrument air to drywell Manual Outside Open NA X-022 4799-518 Inst. air to drywell - local drop shutoff valve Manual Outside Closed NA tap between 4799-155 & 156 X-023 3799-31 Rx building closed cooling water supply Check Inside Open NA X-023 3702 Rx building closed cooling water supply MO Valve Outside Open NA X-023 3799-136 RBCCW supply - press test inbd stop Manual Outside Closed NA tap between 3799-31 & 3702 X-024 3703 Rx building closed cooling water return MO Valve Outside Open NA

TRM Appendix A Primary Containment Isolation Devices Table A-2 Primary Containment Isolation Devices (Unit 2) (Page 4 of 14)

Quad Cities Unit 1 and 2 A2-4 Revision QC-TRM-09-005 Containment Penetration Number Valve Part Number Line Isolated

Valve Type Location Ref.

to Containment

Normal Status Max. Operating Time (sec)

Comments X-024 3706 Rx building closed cooling water return MO Valve Inside Open NA X-024 3799-138 RBCCW return - press test inbd stop Manual Outside Closed NA tap between 3703 & 3706 X-025 1601-23 Drywell main exhaust AO Valve Outside Closed 10 X-025 1601-62 Drywell main exhaust valve bypass (vent relief) AO Valve Outside Closed 15 X-025 1601-24 Main primary containment vent to Rx building exh AO Valve Outside Closed 10 X-025 1601-63 Primary Containment exhaust to SBGT system AO Valve Outside Closed 10 X-025 1601-72 Drywell main exh. / Main primary containment vent to Rx bldg exh - press test inbd stop Manual Outside Closed NA tap between 1601-23 & 24 X-025 2599-64 ACAD to SBGT - DW PT 1641-12 test tap stop Manual Outside Closed NA tap between X-25 & 2599-4A/B X-026 1601-55 Drywell nitrogen purge inle t AO Valve Outside Open 10 X-026 1601-21 Drywell purge inlet AO Valve Outside Closed 10 X-026 1601-22 Drywell purge inlet AO Valve Outside Closed 10 X-026 1601-74 Drywell purge inlet - press test inbd st op Manual Outside Closed NA tap between 1601-21 & 22 X-026 RV-8799-214 Nitrogen makeup Relief Outside Closed NA X-026 1601-57 Nitrogen makeup MO Valve Outside Open 15 X-026 1601-59 Nitrogen makeup to Drywell AO Valve Outside Open 15 X-026 8803 Oxygen analyzer return AO Valve Outside Open 10 X-026 8804 Oxygen analyzer return AO Valve Outside Open 10 X-026 1601-77 Oxygen analyzer return - DW air sample system pressure test stop Manual Outside Closed NA tap between X-26 & 8804 / 1601-21X-027C PT 2-1624 test tap Drywell pressure NA Outside Cap Installed NA X-027C PT 2-1625 test tap Drywell pressure NA Outside Cap Installed NA X-027C DPT 2-1641-51 high side test tap Drywell to Suppression Chamber differential pressure NA Outside Cap Installed NA low side sensing line from X-205 X-030C 0220-451A 0220-452A

'A' RR Pump 1 st stage seal pressure instrumentation/vent line Check 2/Outside Open N/A The check valve is held open by CRD flow X-030E 0220-176A 'A' RR Pmp DPT 0261-5A & DPIS 0261-35A,C,E,G low inboard vent Manual Outside Closed NA tap between X-30E & 0220-13A TRM Appendix A Primary Containment Isolation Devices Table A-2 Primary Containment Isolation Devices (Unit 2) (Page 5 of 14)

Quad Cities Unit 1 and 2 A2-5 Revision QC-TRM-09-005 Containment Penetration Number Valve Part Number Line Isolated

Valve Type Location Ref.

to Containment

Normal Status Max. Operating Time (sec)

Comments X-030F 0220-174A 'A' RR Pmp DPT 0261-5A & DPIS 0261-35A,C,E,G high inboard vent Manual Outside Closed NA tap between X-30F & 0220-14A X-031C 0220-451B 0220-452B

'B' RR Pump 1 st stage seal pressure instrumentation/vent line Check 2/Outside Open N/A The check valve is held open by CRD flow X-031E 0220-176B 'B' RR Pmp DPT 0261-5B & DPIS 0261-35B,D,F,H low inboard vent Manual Outside Closed NA tap between X-31E & 0220-13B X-031F 0220-174B 'B' RR Pmp DPT 0261-5B & DPIS 0261-35B,D,F,H high inboard vent Manual Outside Closed NA tap between X-31F & 0220-14B X-032 4720 Drywell pneumatic suction X-32D AO Valve Outside Open 10 X-032 4721 Drywell pneumatic suction X-32D AO Valve Outside Open 10 X-033 2499-1A CAM/drywell (position E)

SO Valve Outside Closed NA X-033 2499-2A CAM/drywell (position E)

SO Valve Outside Closed NA X-033 2499-7A CAM/drywell (pos. E) - press test inbd stop Manual Outside Closed NA tap between 2499-1A & 2A X-033 2499-22A CAM return (position D) Check Outside Closed NA X-033 2499-25A CAM return (pos. D) - smpl outlet press test inbd stop Manual Outside Closed NA tap between X-033 & 2499-22A X-035A 0743 Traversing in-core probe purge Check Outside Closed NA X-035B 0737-1C Traversing in-core pr obe SO Valve Outside Closed NA X-035B 0737-2C Traversing in-core probe Shear Outside Open NA X-035C 0737-1B Traversing in-core pr obe SO Valve Outside Closed NA X-035C 0737-2B Traversing in-core probe Shear Outside Open NA X-035D 0737-1D Traversing in-core pr obe SO Valve Outside Closed NA X-035D 0737-2D Traversing in-core probe Shear Outside Open NA X-035E 0737-1F Traversing in-core pr obe SO Valve Outside Closed NA X-035E 0737-2F Traversing in-core probe Shear Outside Open NA X-035F 0737-1E Traversing in-core pr obe SO Valve Outside Closed NA X-035F 0737-2E Traversing in-core probe Shear Outside Open NA X-037 2499-22B CAM return (pos. C)

Check Outside Closed NA X-037 2499-25B CAM return (pos. C) - smpl outlet pressure test inboard stop Manual Outside Closed NA tap between X-037 & 2499-22B TRM Appendix A Primary Containment Isolation Devices Table A-2 Primary Containment Isolation Devices (Unit 2) (Page 6 of 14)

Quad Cities Unit 1 and 2 A2-6 Revision QC-TRM-09-005 Containment Penetration Number Valve Part Number Line Isolated

Valve Type Location Ref.

to Containment

Normal Status Max. Operating Time (sec)

Comments X-039A 1001-26A RHR - containment spray MO Valve Outside Closed NA X-039A 1001-23A RHR - containment spray MO Valve Outside Closed NA X-039A 1001-197 RHR containment spray - pressure test stop Manual Outside Closed NA tap between 1001-26A & 23A X-039A 1099-166 RHR - containment spray Manual Outside Closed NA tap between 1001-26A & 23A X-039A 1001-26A bonnet test tap RHR - containment spray NA Outside Cap Installed NA bonnet test tap cap for 1001-26A X-039A 1001-25A 'A' Containment Spray - loop inboard drain Manual Outside Closed NA tap between 1001-23A & 26A X-039B 1001-26B RHR - containment spray MO Valve Outside Closed NA X-039B 1001-23B RHR - containment spray MO Valve Outside Closed NA X-039B 1001-26B bonnet test tap RHR - containment spray NA Outside Cap Installed NA bonnet test tap cap for 1001-26B X-039B 1001-25B 'B' Containment Spray - loop inboard drain Manual Outside Closed NA tap between 1001-23B & 26B X-039B 1001-196 'B' Containment Spray - loop pressure test Manual Outside Closed NA tap between 1001-23B & 26B X-039B Blind Flange RHR DW spray blind flange NA Outside Installed NA between 1001-23B & 26B X-041 0220-44 Reactor water sample AO Valve Inside Open 5 X-041 0220-45 Reactor water sample AO Valve Outside Open 5 X-041 0220-43 Reactor water sample - press test inbd stop Manual Outside Closed NA tap between 0220-44 & 45 X-043 8800-02B Particulate sample lines (line B) Manual Outside Closed NA X-043 8800-03B Particulate sample lines (line B) Manual Outside Closed NA X-043 8800-02C Particulate sample lines (line C) Manual Outside Closed NA X-043 8800-03C Particulate sample lines (line C) Manual Outside Closed NA X-043 8800-02D Particulate sample lines (line D) Manual Outside Closed NA X-043 8800-03D Particulate sample lines (line D) Manual Outside Closed NA X-043 8800-02E Particulate sample lines (line E) Manual Outside Closed NA X-043 8800-03E Particulate sample lines (line E) Manual Outside Closed NA X-043 8800-02F Particulate sample lines (line F) Manual Outside Closed NA X-043 8800-03F Particulate sample lines (line F) Manual Outside Closed NA X-043 8800-02G Particulate sample lines (line G) Manual Outside Closed NA X-043 8800-03G Particulate sample lines (line G) Manual Outside Closed NA

TRM Appendix A Primary Containment Isolation Devices Table A-2 Primary Containment Isolation Devices (Unit 2) (Page 7 of 14)

Quad Cities Unit 1 and 2 A2-7 Revision QC-TRM-09-005 Containment Penetration Number Valve Part Number Line Isolated

Valve Type Location Ref.

to Containment

Normal Status Max. Operating Time (sec)

Comments X-043 8800-02H Particulate sample lines (line H) Manual Outside Closed NA X-043 8800-03H Particulate sample lines (line H) Manual Outside Closed NA X-043 8800-02I Particulate sample lines (line I) Manual Outside Closed NA X-043 8800-03I Particulate sample lines (line I) Manual Outside Closed NA X-043 8800-02J Particulate sample lines (line J) Manual Outside Closed NA X-043 8800-03J Particulate sample lines (line J) Manual Outside Closed NA X-043 8800-02K Particulate sample lines (line K) Manual Outside Closed NA X-043 8800-03K Particulate sample lines (line K) Manual Outside Closed NA X-043 8800-02L Particulate sample lines (line L) Manual Outside Closed NA X-043 8800-03L Particulate sample lines (line L) Manual Outside Closed NA X-043 8800-02M Particulate sample lines (line M) Manual Outside Closed NA X-043 8800-03M Particulate sample lines (line M) Manual Outside Closed NA X-043 8800-02N Particulate sample lines (line N) Manual Outside Closed NA X-043 8800-03N Particulate sample lines (line N) Manual Outside Closed NA X-043 8800-02O Particulate sample lines (line O) Manual Outside Closed NA X-043 8800-03O Particulate sample lines (line O) Manual Outside Closed NA X-043 8800-02P Particulate sample lines (line P) Manual Outside Closed NA X-043 8800-03P Particulate sample lines (line P) Manual Outside Closed NA X-043 8800-02Q Particulate sample lines (line Q) Manual Outside Closed NA X-043 8800-03Q Particulate sample lines (line Q) Manual Outside Closed NA X-043 8800-02R Particulate sample lines (line R) Manual Outside Closed NA X-043 8800-03R Particulate sample lines (line R) Manual Outside Closed NA X-043 8800-02S Particulate sample lines (line S) Manual Outside Closed NA X-043 8800-03S Particulate sample lines (line S) Manual Outside Closed NA X-043 8800-02T Particulate sample lines (line T) Manual Outside Closed NA X-043 8800-03T Particulate sample lines (line T) Manual Outside Closed NA X-043 8800-02U Particulate sample lines (line U) Manual Outside Closed NA X-043 8800-03U Particulate sample lines (line U) Manual Outside Closed NA

TRM Appendix A Primary Containment Isolation Devices Table A-2 Primary Containment Isolation Devices (Unit 2) (Page 8 of 14)

Quad Cities Unit 1 and 2 A2-8 Revision QC-TRM-09-005 Containment Penetration Number Valve Part Number Line Isolated

Valve Type Location Ref.

to Containment

Normal Status Max. Operating Time (sec)

Comments X-043 8800-02V Particulate sample lines (line V) Manual Outside Closed NA X-043 8800-03V Particulate sample lines (line V) Manual Outside Closed NA X-043 8801A Drywell oxygen analyzer sample (line A) AO Valve Outside Open 10 X-043 8802A Drywell oxygen analyzer sample (line A) AO Valve Outside Open 10 X-043 8801B Drywell oxygen analyzer sample (line B) AO Valve Outside Open 10 X-043 8802B Drywell oxygen analyzer sample (line B) AO Valve Outside Open 10 X-043 8801C Drywell oxygen analyzer sample (line C) AO Valve Outside Open 10 X-043 8802C Drywell oxygen analyzer sample (line C) AO Valve Outside Open 10 X-044 4799-176 HVAC instrument penetration Manual Outside Closed NA capped line X-044 4799-479A HVAC instrument penetration (line A) Manual Outside Closed NA capped line X-044 4799-479B HVAC instrument penetration (line B) Manual Outside Closed NA capped line X-044 4799-479C HVAC instrument penetration (line C) Manual Outside Closed NA capped line X-044 4799-479D HVAC instrument penetration (line D) Manual Outside Closed NA capped line X-044 4799-479E HVAC instrument penetration (line E) Manual Outside Closed NA capped line X-044 4799-479F HVAC instrument penetration (line F) Manual Outside Closed NA capped line X-044 4799-479G HVAC instrument penetration (li ne G) Manual Outside Closed NA capped line X-044 4799-479H HVAC instrument penetration (line H) Manual Outside Closed NA capped line X-044 4799-479J HVAC instrument penetration (li ne J) Manual Outside Closed NA capped line X-044 4799-479K HVAC instrument penetration (line K) Manual Outside Closed NA capped line X-044 4799-479L HVAC instrument penetration (li ne L) Manual Outside Closed NA capped line X-044 4799-479M HVAC instrument penetration (line M) Manual Outside Closed NA capped line X-044 4799-479N HVAC instrument penetration (line N) Manual Outside Closed NA capped line X-044 4799-479P HVAC instrument penetration (line P) Manual Outside Closed NA capped line X-044 4799-479Q HVAC instrument penetration (li ne Q) Manual Outside Closed NA capped line X-044 4799-479R HVAC instrument penetration (line R) Manual Outside Closed NA capped line X-044 4799-479S HVAC instrument penetration (line S) Manual Outside Closed NA capped line X-044 4799-479T HVAC instrument penetration (line T) Manual Outside Closed NA capped line X-044 4799-479U HVAC instrument penetration (line U) Manual Outside Closed NA capped line TRM Appendix A Primary Containment Isolation Devices Table A-2 Primary Containment Isolation Devices (Unit 2) (Page 9 of 14)

Quad Cities Unit 1 and 2 A2-9 Revision QC-TRM-09-005 Containment Penetration Number Valve Part Number Line Isolated

Valve Type Location Ref.

to Containment

Normal Status Max. Operating Time (sec)

Comments X-044 4799-479V HVAC instrument penetration (line V) Manual Outside Closed NA capped line X-044 4799-479W HVAC instrument penetration (li ne W) Manual Outside Closed NA capped line X-044 4799-479X HVAC instrument penetration (line X) Manual Outside Closed NA capped line X-044 4799-479Y HVAC instrument penetration (line Y) Manual Outside Closed NA capped line X-044 4799-479Z HVAC instrument penetration (line Z) Manual Outside Closed NA capped line X-047 1101-16 Standby liquid control Check Outside Closed NA X-047 1101-15 Standby liquid control Check Inside Closed NA X-047 1101-34 SBLC - injection line pressure tap inboard stop Manual Outside Closed NA tap between 1101-15 & 16 X-100D 2499-1B CAM/drywell (position F) SO Valve Outside Closed NA X-100D 2499-2B CAM/drywell (position F) SO Valve Outside Closed NA X-100D 2499-7B CAM/drywell (pos. F) - press test inbd stop Manual Outside Closed NA tap between 2499-1B & 2B X-100D 4799-353 SRM/IRM purge Check Outside Closed NA X-100D 4799-354 SRM/IRM purge Check Outside Closed NA X-100D 4799-480A Instrumentation Lines (li ne A) Manual Outside Closed NA capped line X-100D 4799-480B Instrumentation Lines (li ne B) Manual Outside Closed NA capped line X-100D 4799-480C Instrumentation Lines (li ne C) Manual Outside Closed NA capped line X-104E 4799-477A Instrumentation Lines (li ne A) Manual Outside Closed NA capped line X-104E 4799-477B Instrumentation Lines (li ne B) Manual Outside Closed NA capped line X-104E 4799-477C Instrumentation Lines (li ne C) Manual Outside Closed NA capped line X-104E 4799-477D Instrumentation Lines (li ne D) Manual Outside Closed NA capped line X-104E 4799-477E Instrumentation Lines (li ne E) Manual Outside Closed NA capped line X-104E 4799-477F Instrumentation Lines (li ne F) Manual Outside Closed NA capped line X-104E 4799-477G Instrumentation Lines (li ne G) Manual Outside Closed NA capped line X-108 0263-944A RVLIS Backfill (line 2-2334A) Check Outside Open NA X-108 0263-945A RVLIS Backfill (line 2-2334A) Check Outside Open NA X-108 0263-947A RVLIS Backfill (line 2-2335A) Check Outside Open NA X-108 0263-948A RVLIS Backfill (line 2-2335A) Check Outside Open NA X-108 0263-960A RVLIS Backfill - test valve Manual Outside Closed NA tap between 0263-944A & X-108 TRM Appendix A Primary Containment Isolation Devices Table A-2 Primary Containment Isolation Devices (Unit 2) (Page 10 of 14)

Quad Cities Unit 1 and 2 A2-10 Revision QC-TRM-09-005 Containment Penetration Number Valve Part Number Line Isolated

Valve Type Location Ref.

to Containment

Normal Status Max. Operating Time (sec)

Comments X-108 0263-958A RVLIS Backfill - vent valve Manual Outside Closed NA tap between 0263-944A & X-108 X-108 0263-955A RVLIS Backfill - test valve Manual Outside Closed NA tap between 0263-947A & X-108 X-108 0263-953A RVLIS Backfill - vent valve Manual Outside Closed NA tap between 0263-947A & X-108 X-109 0263-944B RVLIS Backfill (line 2-2334B) Check Outside Open NA X-109 0263-945B RVLIS Backfill (line 2-2334B) Check Outside Open NA X-109 0263-947B RVLIS Backfill (line 2-2335B) Check Outside Open NA X-109 0263-948B RVLIS Backfill (line 2-2335B) Check Outside Open NA X-109 0263-960B RVLIS Backfill - test valve Manual Outside Closed NA tap between 0263-944B & X-109 X-109 0263-958B RVLIS Backfill - vent valve Manual Outside Closed NA tap between 0263-944B & X-109 X-109 0263-955B RVLIS Backfill - test valve Manual Outside Closed NA tap between 0263-947B & X-109 X-109 0263-953B RVLIS Backfill - vent valve Manual Outside Closed NA tap between 0263-947B & X-109 X-203A 1601-60 Suppression chamber main exhaust AO Valve Outside Closed 10 X-203A 1601-61 Suppression chamber main exhaust valve bypass AO Valve Outside Closed 15 X-203A 1601-24 Main primary containment vent to Rx building exh AO Valve Outside Closed 10 X-203A 1601-63 Primary Containment exhaust to SBGT system AO Valve Outside Closed 10 X-203A 1601-72 Suppression chamber main exhaust / Main primary containment vent to Rx bldg exh - pressure test inboard stop Manual Outside Closed NA tap between 1601-60/61 & 24 X-205 1601-20A Vacuum breaker secondary containment to suppression chamber AO Valve Outside Closed NA X-205 1601-31A Vacuum breaker secondary containment to suppression chamber Check Outside Closed NA X-205 1601-73A Vac. breaker secondary containment to suppression chamber - pressure test inbd stop Manual Outside Closed NA tap between 1601-20A & 31A X-205 1601-20B Vacuum breaker secondary containment to suppression chamber AO Valve Outside Closed NA X-205 1601-31B Vacuum breaker secondary containment to suppression chamber Check Outside Closed NA X-205 1601-73B Vac. breaker secondary containment to suppression chamber - pressure test inbd stop Manual Outside Closed NA tap between 1601-20B & 31B TRM Appendix A Primary Containment Isolation Devices Table A-2 Primary Containment Isolation Devices (Unit 2) (Page 11 of 14)

Quad Cities Unit 1 and 2 A2-11 Revision QC-TRM-09-005 Containment Penetration Number Valve Part Number Line Isolated

Valve Type Location Ref.

to Containment

Normal Status Max. Operating Time (sec)

Comments X-205 1601-56 Suppression chamber purge in let AO Valve Outside Open 10 X-205 1601-58 Nitrogen makeup to suppression chamber AO Valve Outside Closed 15 X-205 1601-91B Suppression chamber LT 1641-5B low side vent Manual Outside Closed NA X-205 DPT 2-1641-51 lo w side test tap Drywell to Suppression Chamber differential pressure NA Outside Cap Installed NA hi side sensing line from X-027C X-205 DPT 2-1622A test tap Suppression Chamber to Reactor Building differential pressure NA Outside Cap Installed NA X-205 DPT 2-1622B test tap Suppression Chamber to Reactor Building differential pressure NA Outside Cap Installed NA X-205 PT 2-1623 test tap Suppression Chamber pressure NA Outside Cap Installed NA X-206A 1601-100 Suppression chamber LG 1602-10 upper shutoff Manual Outside Closed NA X-206A 1699-17 Suppression chamber LT 2-1626 upper shutoff Manual Outside Closed NA X-206A 1699-42 Suppression Chamber level indicator drain pot drain valve Manual Outside Closed NA X-206A PT 2-1602-8 test tap Suppression Chamber pressure NA Outside Cap Installed NA X-206A LT 2-1602-9 low side test tap Suppression Chamber level NA Outside Cap Installed NA X-206B 1699-16 Suppression chamber level instrumentation drain Manual Outside Closed NA X-206B 1601-101 Suppression chamber LG 1602-10 lower shutoff Manual Outside Closed NA X-206B 1699-15 Suppression chamber LT 2-1626 lower shutoff Manual Outside Closed NA X-206B 1699-19 Suppression chamber water reservoir fill tap Manual Outside Closed NA X-206B LT 2-1602-9 high side test tap Suppression Chamber level NA Outside Cap Installed NA X-206C 2399-35 Suppression chamber LS 2351A & B high side drain Manual Outside Closed NA X-206C 2399-38A Suppression chamber LS 2351A drain Manual Outside Closed NA X-206C 2399-38B Suppression chamber LS 2351B drain Manual Outside Closed NA X-210A 1402-4A Core spray test to suppre ssion pool MO Valve Outside Closed NA X-210A 1402-4B Core spray test to suppre ssion pool MO Valve Outside Closed NA

TRM Appendix A Primary Containment Isolation Devices Table A-2 Primary Containment Isolation Devices (Unit 2) (Page 12 of 14)

Quad Cities Unit 1 and 2 A2-12 Revision QC-TRM-09-005 Containment Penetration Number Valve Part Number Line Isolated

Valve Type Location Ref.

to Containment

Normal Status Max. Operating Time (sec)

Comments X-210A 1001-36A RHR test line to suppression pool MO Valve Outside Closed NA X-210A 2301-14 HPCI min flow bypass MO Valve Outside Closed NA X-210A 1301-47 RCIC min flow bypa ss Check Outside Closed NA X-210A 1402-38A Core spray min bypa ss MO Valve Outside Closed NA X-210A 1402-38B Core spray min bypa ss MO Valve Outside Closed NA X-210A 1001-18A RHR min flow bypass MO Valve Outside Open NA X-210B 1001-36B RHR test line to suppression pool MO Valve Outside Closed NA X-210B 1001-18B RHR min flow bypass MO Valve Outside Open NA X-211A 1001-34A RHR - suppression pool test re turn MO Valve Outside Closed NA X-211A 1001-37A RHR to suppression spray header MO Valve Outside Closed NA X-211B 1001-34B RHR-suppression pool test re turn MO Valve Outside Closed NA X-211B 1001-37B RHR to suppression spray header MO Valve Outside Closed NA X-212 1301-41 RCIC turbine exhaust Check Outside Closed NA X-212 1301-64 RCIC turbine exhaust Stop Check Outside Open NA X-212 1399-105 RCIC turbine exhaust - press test inbd stop Manual Outside Closed NA tap on 1301-64 X-212 1399-58A RCIC turbine exhaust - press test inbd stop Manual Outside Closed NA tap between 1301-41 & 64 X-213A 1601-80B Supp Chamber drain - inboard drain valve Manual Outside Closed NA X-213A 1601-81B Supp Chamber drain - press test inbd stop Manual Outside Closed NA off torus drain line X-213A 1601-89A Supp Chamber drain - LT 1641-5A hi side inbd drain Manual Outside Closed NA off 1641-5A hi side sensing line X-213B 1601-83 Supp Chamber drain - press test inbd stop Manual Outside Closed NA X-213B 1601-89B Supp Chamber drain - LT 1641-5B hi side inbd drain Manual Outside Closed NA off 1641-5B hi side sensing line X-213B 1699-5 Supp Chamber drain - PT 1641-14 drain Manual Outside Closed NA X-216 4799-159 Instrument air to suppression chamber Check Outside Open NA X-216 4799-158 Instrument air to suppression chamber Check Inside Open NA X-216 4799-527 IA to suppression chamber - press test inbd stop Manual Outside Closed NA tap between 4799-158 & 159 X-217 8801D Torus oxygen analyzer samp le AO Valve Outside Open 10 X-217 8802D Torus oxygen analyzer samp le AO Valve Outside Open 10 X-220 2301-45 HPCI turbine exhaust Check Outside Closed NA

TRM Appendix A Primary Containment Isolation Devices Table A-2 Primary Containment Isolation Devices (Unit 2) (Page 13 of 14)

Quad Cities Unit 1 and 2 A2-13 Revision QC-TRM-09-005 Containment Penetration Number Valve Part Number Line Isolated

Valve Type Location Ref.

to Containment

Normal Status Max. Operating Time (sec)

Comments X-220 2301-74 HPCI turbine exhaust Stop Check Outside Open NA X-220 2399-74 HPCI exhaust vac. breaker - press test inbd stop Manual Outside Closed NA tap between 2301-74 & X-220 X-220 2301-74A HPCI turbine exhaust - press test inbd stop Manual Outside Closed NA tap on 2301-74 X-220 2301-41A HPCI turbine exhaust - press test inbd stop Manual Outside Closed NA tap on 2301-74 & 45 X-221 2301-34 HPCI turbine exhaust drain Check Outside Closed NA X-221 2301-71 HPCI turbine exhaust drai n Stop Check Outside Open NA X-221 2301-41B HPCI turbine exh. drain - press test inbd stop Manual Outside Closed NA tap between 2301-34 & 71 X-221 2399-55 HPCI turbine exh. drain - press test inbd stop Manual Outside Closed NA tap between 2301-71 & X-221 X-222 1301-55 RCIC vacuum pump discharge to suppression chamberStop Check Outside Open NA X-222 1301-40 RCIC vacuum pump discharge to suppression chamberCheck Outside Closed NA X-222 1301-58B RCIC vacuum pump di scharge to suppression chamber - pressure test inboard stop Manual Outside Closed NA tap between 1301-55 & 40 X-222 1399-106 RCIC vacuum pump discharge to suppression chamber - pressure test inboard stop Manual Outside Closed NA tap between 1301-55 & X-222 X-223A 1001-7A RHR pump suction from suppression chamber MO Valve Outside Open NA X-223A 1001-7B RHR pump suction from suppression chamber MO Valve Outside Open NA X-223A 1001-159A 'A' RHR Loop - torus suction inboard vent Manual Outside Closed NA tap between 1001-7A & 7B X-223A RV-1001-125A capped line

'A' RHR Loop - pump 'A' suction RV discharge line NA Outside Cap Installed NA between 1001-7A & torus X-223A RV-1001-125B capped line

'A' RHR Loop - pump 'B' suction RV discharge line NA Outside Cap Installed NA between 1001-7B & torus X-223B 1001-7C RHR pump suction from suppression chamber MO Valve Outside Open NA X-223B 1001-7D RHR pump suction from suppression chamber MO Valve Outside Open NA X-223B 1001-159B 'B' RHR Loop - torus suction inboard vent Manual Outside Closed NA tap between 1001-7C & 7D X-223B RV-1001-125C capped line

'B' RHR Loop - pump 'C' suction RV discharge line NA Outside Cap Installed NA between 1001-7C & torus X-223B RV-1001-125D capped line

'A' RHR Loop - pump 'D' suction RV discharge line NA Outside Cap Installed NA between 1001-7D & torus X-224A 1402-3A Core spray pump suction from suppression chamber MO Valve Outside Open NA X-224A 1402-21A Core spray pump suction header vent valve Manual Outside Closed NA tap between 1402-3A & torus TRM Appendix A Primary Containment Isolation Devices Table A-2 Primary Containment Isolation Devices (Unit 2) (Page 14 of 14)

Quad Cities Unit 1 and 2 A2-14 Revision QC-TRM-09-005 Containment Penetration Number Valve Part Number Line Isolated

Valve Type Location Ref.

to Containment

Normal Status Max. Operating Time (sec)

Comments X-224B 1402-3B Core spray pump suction from suppression chamber MO Valve Outside Open NA X-224B 1402-21B Core spray pump suction header vent valve Manual Outside Closed NA tap between 1402-3B & torus X-225 2301-36 HPCI pump suction from suppression chamber MO Valve Outside Closed NA X-225 2301-37 HPCI pmp suct from Supp chamber - press test stop Manual Outside Closed NA X-225 2399-107 HPCI pump suct from Supp chamber - vent valve Manual Outside Closed NA tap between 2301-36 and torus X-226 1301-25 RCIC pump suction from suppression chamber MO Valve Outside Closed NA X-226 1301-28 RCIC pump suction from suppression chamber -

pressure test inboard stop Manual Outside Closed NA tap between 1301-25 & 27 X-227A 2499-3A CAM/suppression chamber SO Valve Outside Closed NA X-227A 2499-4A CAM/suppression chamber SO Valve Outside Closed NA X-227A 2499-9A CAM/supp chamber - press test inbd stop Manual Outside Closed NA tap between 2499-3A & 4A X-227A 1601-91A Suppression chamber LT 1641-5A low side vent Manual Outside Closed NA X-227B 2499-3B CAM/suppression chamber SO Valve Outside Closed NA X-227B 2499-4B CAM/suppression chamber SO Valve Outside Closed NA X-227B 2499-9B CAM/supp chamber - press test inbd stop Manual Outside Closed NA tap between 2499-3B & 4B X-227B 1601-91B Suppression chamber LT 1641-5B low side vent Manual Outside Closed NA X-229 2399-40 HPCI exhaust vacuum break er MO Valve Outside Open 50 X-229 2399-41 HPCI exhaust vacuum break er MO Valve Outside Open 50 X-229 2399-68 HPCI exhaust vac. breaker - press test inbd stop Manual Outside Closed NA tap between 2399-40 and X-229 X-229 2399-70 HPCI exhaust vac. breaker - press test inbd stop Manual Outside Closed NA tap between 2399-40 & 64 X-229 2399-71 HPCI exhaust vac. breaker - press test inbd stop Manual Outside Closed NA tap between 2399-65 & 67 X-229 2399-72 HPCI exhaust vac. breaker - press test inbd stop Manual Outside Closed NA tap between 2399-64 & 66 X-229 2399-73 HPCI exhaust vac. breaker - press test inbd stop Manual Outside Closed NA tap between 2399-66 & 41

-- 1001-20 RHR discharge to radwaste MO Valve Outside Closed 25

-- 1001-21 RHR discharge to radwaste MO Valve Outside Closed 25

TRM Appendix C SFDP Quad Cities 1 & 2 C-1 Revision 0 TABLE OF CONTENTS

A. PURPOSE

............................................................................................................................2 B. REFERENCES

....................................................................................................................2 C. DEFINITIONS

.....................................................................................................................2 D. LIMITATIONS

....................................................................................................................3

E. PROCEDURE

......................................................................................................................4 E.1 LCO 3.0.6 REQUIREMENTS.......................................................................................4 E.2 T.S. 5.5.11, Safety Function Determination Program (SFDP) Requirements.............6 E.3 Program Implementation................................................................................................8

FIGURE 1 LOSF Evaluation Flow Chart.......................................................................................11

ATTACHMENTS 1 Loss Of Safety Function Evaluation............................................................................13 2 Supported System (s) Completion Time Extensions..................................................19 3 SFDP Tracking Worksheet...........................................................................................26

TABLE 1 Cross Train Check Guidance........................................................................................30

TRM Appendix C SFDP Quad Cities 1 & 2 C-2 Revision 0 A. PURPOSE A.1 Objective

The purpose of the SFDP is to enus re that when Technical Specification LCO 3.0.6 is used to preclude performing the Conditions and Actions for inoperable SUPPORTED SYSTEMS:

  • A Loss of Safety Function does not go undetected,
  • The plant will be placed in a safe condition if a Loss of Safety Function is determined to exist, and
  • A supported SYSTEM(S) Completion Time will not be inappropriately extended.

B. REFERENCES

B.1 Technical Specification (TS) 3.0.6.

B.2 TS 5.5.11, "Safety Function Determination Program (SFDP)"

C. DEFINITIONS

C.1 SAFETY FUNCTION

-

An accident mitigation feature required by NRC regulation, plant design or Technical Specifications normally composed of two trains of SUPPORT and SUPPORTED equipment.

C.2 LOSS OF SAFETY FUNCTION (LOSF)

-

A LOSF exists when, assuming no concurrent single failure and assuming no concurrent loss of offsite power or loss of onsite diesel generator(s), a safety function assumed in the accident analysis cannot be performed. (SEE ATTACHMENT 1.0)

C.3 SUPPORT SYSTEM - A SYSTEM(S) that is needed by another TS LCO required SYSTEM(S) to perform a safety function.

TRM Appendix C SFDP Quad Cities 1 & 2 C-3 Revision 0 C.4 SUPPORTED SYSTEM

- A SYSTEM, required by the TS, which requires a SUPPORT SYSTEM to ensure its safety function can be performed. Process parameters or operating limits do not comprise SUPPORTED SYSTEM(S) for the purposes of implementing TS LCO 3.0.6.

C.5 MAXIMUM OUT OF SERVICE TIME -

A SUPPORTED SYSTEM(S) made inoperable by the SUPPORT SYSTEM(S) inoperability shall be re stored to OPERABLE status within the Maximum Out Of Service Time (MOST). The MOST is the Completion Time specified in the Tec hnical Specifications for restoring the first inoperable SUPPORT SYSTEM(S) to OPERABLE status plus the time specified in the TS for restor ing the SUPPORTED SYSTEM(S) to OPERABLE status. (SEE ATTACHMENT 2 - Completion Time

Extensions )

The inoperability of the SUPPORTED SYSTEM(S) must only be directly attributed to its associated SUPPORT SYSTEM(S) bei ng inoperable and the SUPPORT SYSTEM(S) Required Actions not specifically requiring

entry into the SUPPORTED SYST EM(S) Conditions and Required Actions.

D. LIMITATIONS

D.1 Reporting Requirements will be done in accordance with the Reportability Manual.

D.2 Changes to this Program shall be performed in accordance with the TRM Change Control Program.

D.3 The Shift Manager is responsible for implementing the Safety Function Determination Program.

TRM Appendix C SFDP Quad Cities 1 & 2 C-4 Revision 0

E. PROCEDURE

E.1 LCO 3.0.6 REQUIREMENTS

E.1.1 TS LCO 3.0.2 states that upon discovery of a failure to meet an TS LCO, the Required Actions of the associated Conditions shall be met, except as provided in TS LCO 3.0.5 and TS LCO 3.0.6.

E.1.2 TS LCO 3.0.6 provides an exception to TS LCO 3.0.2 for SUPPORT SYSTEM(S) by not requiring the Conditions and Required Actions for the SUPPORTED SYSTEM(S) to be performed when the failure to meet an TS LCO is solely due to a SUPPORT SYSTEM(S) LCO not being met. In this situation, although the SUPPORTED SYSTEM(S) is determined to be inoperable as defined in the Technical Specifications, LCO 3.0.6 requires only the ACTIONS of the SUPPORT SYSTEM(S) to be performed. The Conditions and Required Actions for the SUPPORTED SYSTEM(S) are not required to be performed (i.e., cascading to the SUPPORTED SYSTEM(S)) per TS LCO 3.0.6.

E.1.3 There are two types of SUPPORT SYSTEM(S) that must be considered when implementing TS LCO 3.0.6:

  • SUPPORT SYSTEM(S) specifica lly addressed in Technical Specifications, and
  • SUPPORT SYSTEM(S) that are not specifically addressed in Technical Specifications NOTE It may be necessary to perform OPERABILITY Determinations in accordance with Procedure RS-AA-105 in order to determine SUPPORTED SYSTEMS made Inoperable by Inoperable SUPPORT SYSTEMS.

If required SUPPORT SYSTEM(S) is addressed in the Technical Specifications, then only the SU PPORT SYSTEM(S) Conditions and Actions must be entered per TS LCO 3.0.6 (i.e., "cascading" to the SUPPORTED SYSTEM(S) is not required).

TRM Appendix C SFDP Quad Cities 1 & 2 C-5 Revision 0 If required SUPPORT SYSTEM(S) is NOT addressed in the Technical Specifications, then impact of the SUPPORT SYSTEM(S) inoperability must be evaluated with respect to any SUPPORTED SYSTEM(S) that is addressed in Technical Specifications.

E.1.4 A single component inoperability may result in multiple inoperabilities within a single train and affect multiple TS LCOs. TS LCO 3.0.6 limits the amount of "cascading" Actions that are required when an inoperable SYSTEM(S) renders a SUPPORTED SYSTEM(S) inoperable.

E.1.5 Any SUPPORT SYSTEM(S) inoperability must be evaluated with respect to the existing plant conditions to ensure that a Loss of Safety Function (LOSF) does not exist.

Example: The loss of Residual Heat Removal Service Water (RHRSW) Pump to one RHRSW heat exchanger. If the heat exchanger bypass valve was found stuck open in the opposite subsystem, a LOSF will exist

following a loss-of-coolant-accident and this plant configuration must be evaluated.

E.1.6 When exception of TS LCO 3.0.6 is u tilized, evaluations are required in accordance with TS 5.5.11, "Safety Function Determination Program (SFDP)".

E.1.7 If LOSF is determined to exist by this Program, the appropriate Conditions and Required Actions of the TS LCO in which the LOSF exists are required to be entered.

E.1.8 When SUPPORT SYSTEM(S) Required Action directs a SUPPORTED SYSTEM(S) to be declared inoperable or directs entry into Conditions and Required Actions for a SUPPORTED SYSTEM(S), the applicable Conditions and Required Actions shall be entered in accordance with TS LCO 3.0.2.

E.1.9 It should be noted that for cas es in which the inoperable SUPPORT SYSTEM(S) is addressed in Technical Specifications, "cascading" Conditions and Required Actions may still be performed in lieu of entry

into TS LCO 3.0.6.

TRM Appendix C SFDP Quad Cities 1 & 2 C-6 Revision 0 E.2 T.S. 5.5.11, SAFETY FUNCTION DETERMINATION PROGRAM (SFDP) REQUIREMENTS NOTE If failure of a TS required SUPPORT SYSTEM(S) results in the inoperability of a SYSTEM(S) outside of the TS, and that SYSTEM(S) is subsequently relied upon by a SUPPORTED SYSTEM(S) to remain OPERABLE, then TS LCO 3.0.6 could apply and only the SUPPORT SYSTEM(S) Required Actions would be entered.

E.2.1 When TS LCO 3.0.6 is used as an exception to TS LCO 3.0.2, an evaluation is required to ensure a LOSF is detected and appropriate actions are taken.

E.2.2 Therefore, the SFDP requires:

E.2.2.1 Cross train checks to ensure a LOSF does not go undetected;

  • Since "cascading" the Conditions and Required Actions of a Specification are not required when applying TS LCO 3.0.6, a possibility exists that unr elated concurrent failures of more than one SYSTEM(S) could result in the complete loss of both trains of a SUPPORTED SYSTEM(S). Therefore, upon a failure to meet two or more LCOs during the same time period, an evaluation shall be conducted to determine if a LOSF exists. Generally, this is done by confirming that the remaining required redundant SYSTEM(S) are OPERABLE. ( Per ATTACHMENT 1 and TABLE 1) If a LOSF does exist, the SFDP directs that the appropriate actions be taken.

E.2.2.2 Placing the plant in a safe condition if a LOSF is detected;

  • If LOSF is determined to exist by this Program, the appropriate Conditions and Required Actions of the LCO in which the LOSF exists are required to be entered per step E.3.4.

TRM Appendix C SFDP Quad Cities 1 & 2 C-7 Revision 0 E.2.2.3 Controls on extending completion times on inoperable supported SYSTEM(S);

  • MOST is determined per Attachment 2.

E.2.2.4 Appropriate limitations and remedial or compensatory actions to be taken as a result of the support SYSTEM(S) inoperability.

TRM Appendix C SFDP Quad Cities 1 & 2 C-8 Revision 0 E.3 PROGRAM IMPLEMENTATION Performing steps E.3.1 thru E.3.7 and / or use of the Flowchart (Figure 1) will implement the requirements of the SFDP.

E.3.1 Does the degraded SYSTEM(S) render a TS required SYSTEM(S) inoperable?

E.3.1.1 If NO, then no further evaluation is necessary.

E.3.1.2 If YES, then evaluate this inoperabilities impact on any current SFDs and document on worksheet.

E.3.2 Is the inoperable SYSTEM(S) also a SUPPORT SYSTEM(S)?

E.3.2.1 If NO, then perform Conditions and Require d Actions for the inoperable SYSTEM(S).

E.3.2.2 If YES, then evaluate all Conditions and Required Actions of any SUPPORTED SYSTEM(S) that are rendered inoperable as a result of this TS SUPPORT SYSTEM Inoperability.

E.3.3 Does the Inoperable SUPPORT SYSTEM(S) Specification Conditions and Required Actions direct either the Immediate Declaration of Inoperability of SUPPORTED SYSTEM(S) or performance of any SUPPORTED SYSTEM(S) Required Action(s)?

E.3.3.1 If YES, then enter the TS Condition for the SUPPORTED SYSTEM(S) as directed and perform the Required Actions.

E.3.3.2 If NO, then: EITHER

  • PERFORM both the SUPPORT and the SUPPORTED SYSTEM(S) Required Actions.

TRM Appendix C SFDP Quad Cities 1 & 2 C-9 Revision 0 OR

  • PERFORM SUPPORT SYSTEM(S) Required Actions, And
  • PERFORM a LOSF Evaluation for ALL inoperable SUPPORT and SUPPORTED SYSTEM(S) , per ATTACHMENT 1 and Table 1.

E.3.4 If LOSF is determined to exist, then perform the appropriate Conditions and Required Actions as determined from using the following guidance.

E.3.4.1 SINGLE SUPPORT SYSTEM INOPERABILITY-

When LOSF is solely due to a single T.S. SUPPORT SYSTEM ( e.g., loss of a pump suction source due to low tank level ) the appropriate LCO is the LCO for the SUPPORT SYSTEM. The Actions for the SUPPORT

SYSTEM LCO adequately address the inoperabilities of that system without reliance upon the Actions of the SUPPORTED SYSTEM.

E.3.4.2 MULTIPLE SUPPORT SYSTEM INOPERABILITY-

When LOSF is due to multiple T.S. SUPPORT SYSTEM inoperabilities, the appropriate LCO is the LCO for the SUPPORTED SYSTEMS.

(e.g. loss of minimum flow switch on Division 1 and the 'B' RHR Pump is inoperable. LOSF associated with ECCS may exist following a loss-of-coolant-accident and this plant configuration must be evaluated.)

E.3.5 If NO LOSF exists or LOSF is solely due to a single T.S. support system, then for all SUPPORTED SYSTEM(S) which are rendered inoperable:

E.3.5.1 Invoke TS LCO 3.0.6 to defer entry into the Conditions and Required Actions associated with the inoperable SUPPORTED SYSTEM(S) by the following:

E.3.5.1.1 Calculate the MOST for the inoperable SUPPORTED SYSTEM(S) using ATTACHMENT 2.

TRM Appendix C SFDP Quad Cities 1 & 2 C-10 Revision 0 E.3.5.1.2 Complete the SFDP Worksheet per Attachment 3.0.

  • When filling out the SFD Worksheet it is only necessary to enter names of those SUPPORTED SYSTEMS that are made Inoperable by the Inoperable SUPPORT SYSTEM. It is not necessary to identify either OPERABLE SUPPORTED SYSTEMS or SUPPORTED SYSTEMS that are not in the MODE OF

APPLICABILITY.

EXAMPLE: Assume the "C" LPCI Pump minimum flow switch is INOPERABLE which results in TS LCO 3.3.5.1 not being met while the Unit is in MODE 1. A review indicates that TS LCO 3.3.5.1 equipment supports systems governed by TS 3.5.1, TS 3.5.2, TS 3.8.1, and TS 3.8.2. Although TS 3.8.1 and TS 3.8.2 are supported by TS 3.3.5.1 ( the emergency DGs are started by a Injection Spray Logic signal) , it would not be necessary to list these supported LCOs because they are not made INOPERABLE by the INOPERABLE minimum flow switch. It is also not necessary to list TS 3.5.2 because this LCO is not applicable in MODE 1. TS LCO 3.5.1 is the only SUPPORTED SYSTEM made INOPERABLE by the minimum flow switch.

E.3.6 If SUPPORTED SYSTEM(S) is NOT restored to OPERABLE status (by restoring the SUPP ORT SYSTEM(S) and all associated SUPPORTED SYSTEM(S) to Operable status) within the MOST, the associated

Condition for the INOPERABLE SUPPORTED SYSTEM(S) Completion Time not being met shall be entere d and the Required Actions shall be performed.

E.3.7 The SFD may be closed when the INOPERABLE SUPPORT SYSTEM and SUPPORTED SYSTEM(S) on the SFDP TRACKING SHEET are restored to Operable Status. Enter the time/date when the SUPPORT SYSTEM as well as all SUPPORTED SYSTEM(S) are restored to Operable status, and sign the SFD Worksheet.

TRM Appendix C SFDP Quad Cities 1 & 2 C-11 Revision 0 Figure 1 LOSF Evaluation Flow Chart Is the InoperableSystem a SupportSystem?N oPerform Applicable Conditionsand Required Actions for theIdentified Inoperability YesDoes the InoperableSupport System Conditionsand Required Actions directeither: (1) ImmediateDeclaration of Inoperabilityof Supported System(s) or(2) Performance of anySupported System RequiredActions?Yes No(Step E.3.1)(Step E.3.2)(Step E.3.3)Does the degradedSYSTEM(S) rendera TS RequiredSystem Inoperable?No further evaluationis necessaryEvaluate this inoperabilities impact on any current SFDs and document on worksheet(s). Yes NoEvaluate InoperableSupported System(s)Conditions and RequiredActionsGo to Next Pa g ePerform Applicable Conditionsand Required Actions for theSupported System InoperabilityYesYes TRM Appendix C SFDP Quad Cities 1 & 2 C-12 Revision 0 Figure 1 (Continued)

LOSF Evaluation Flow Chart (1) Perform Support SystemConditions and RequiredActionsAND(2) Perform LOSF Evaluation(per ATTACHMENT 1 andTABLE 1)Yes NoLOSFExists?1.For Single Support SystemInoperability, Enter LCO,Conditions and Required Actions of the Support System(s)in which the LOSF exists.2.For Multiple Support SystemInoperability, Enter LCO, Condiitons and RequiredActions of the Supported System(s) in which the LOSFexists.1. Calculate SUPPORTEDSYSTEM(S) MOST (Per ATTACHMENT 2)

2. Complete the SFDP Worksheet (per Attachment 3.0

)YES NoEITHERPerform both Support& Supported SystemRequired Actions(Step E.3.3)(Step E.3.4)(Step E.3.6)(Step E.3.5)Supported SystemOPERABILITYrestored withinallowed completiontime?(Step E.3.7)From previous p a g eSFD may be closed when the Support System andSupported Systems are restored to o perable status.Enter associated Conditions andRequired Actions for theSupported System CompletionTime not being met No TRM Appendix C SFDP Quad Cities 1 & 2 C-13 Revision 0 ATTACHMENT 1 LOSS OF SAFETY FUNCTION EVALUATION A. Guidance for Safety Function Evaluation TS 5.5.11 states that a LOSF exists when, assuming no concurrent single failure, and assuming no concurrent loss of offsite power or loss of onsite diesel generator(s), a safety function assumed in the accident analysis cannot be performed. For the purpose of this program, a "graduated" approach may be taken for determining the "safety function" of the SUPPORTED SYSTEM(S). This approach, detailed below, is graduated from most to least conservative. Even if the least conservative method is used, the requirements of TS 5.5.11 will be met. In determining whether a LOSF has occurred, at least one of these methods must be used. Method 1: Redundant SUBSYSTEM(S)/Division/Train a. For this method, the safety function is assumed to be the SYSTEM(S) function as described in the TS BASES. Confirm the OPERABILITY of the corresponding redundant SUPPORTED SYSTEM(S). b. If one or more of the redundant SYSTEM(S) are found to be INOPERABLE, a LOSF may exist. The appropriate ACTIONS for a LOSF may be taken or alternatively, one of the following methods below may be used.

A redundant train evaluation used to identify a LOSF can be seen in the following three examples.

TRM Appendix C SFDP ATTACHMENT 1 (Continued) LOSS OF SAFETY FUNCTION EVALUATION Quad Cities 1 & 2 C-14 Revision 0 SUPPORT/SUPPORTED SYSTEM(S) DIAGRAM EXAMPLE 1 A LOSF may exist when a SUPPORT SYSTEM is INOPERABLE, and:

A required SYSTEM redundant to the SYSTEM(S) supported by the INOPERABLE SUPPORT SYSTEM is also INOPERABLE.

If SYSTEM 2 of Train A is INOPER ABLE, and SYSTEM 5 of Train B is INOPERABLE, a LOSF may exist in SUPPORTED SYSTEM(S) 5, 10, 11.

EXAMPLES TRAIN A TRAIN B System 8 System 8 System 4 System 4 System 9 System 9 System 2 System 2 System 10 System 10 System 5 System 5 System 11 System 11 System 1 System 1 System 12 System 12 System 6 System 6 System 13 System 13 System 3 System 3 System 14 System 14 System 7 System 7 System 15 System 15 Note: Chart reads from left to right, i.e., SYSTEM 1 is a SUPPORT SYSTEM for SYSTEM(S) 2 through 15.

TRM Appendix C SFDP ATTACHMENT 1 (Continued) LOSS OF SAFETY FUNCTION EVALUATION Quad Cities 1 & 2 C-15 Revision 0 SUPPORT/SUPPORTED SYSTEM(S) DIAGRAM EXAMPLE 2 A LOSF may exist when a SUPPORT SYSTEM is INOPERABLE, and:

A required SYSTEM redundant to the SYSTEM(S) in turn supported by the INOPERABLE SUPPORTED SYSTEM(S) is also INOPERABLE.

If SYSTEM 2 of Train A is INOPERABLE, and SYSTEM 11 of Train B is INOPERABLE, a LOSF may exist in SYSTEM 11 which is in turn supported by SYSTEM 5.

EXAMPLES TRAIN A TRAIN B System 8 System 8 System 4 System 4 System 9 System 9 System 2 System 2 System 10 System 10 System 5 System 5 System 11 System 11 System 1 System 1 System 12 System 12 System 6 System 6 System 13 System 13 System 3 System 3 System 14 System 14 System 7 System 7 System 15 System 15 Note: Chart reads from left to right, i.e., SYSTEM 1 is a SUPPORT SYSTEM for SYSTEM(S) 2 through 15.

TRM Appendix C SFDP ATTACHMENT 1 (Continued) LOSS OF SAFETY FUNCTION EVALUATION Quad Cities 1 & 2 C-16 Revision 0 SUPPORT/SUPPORTED SYSTEM(S) DIAGRAM EXAMPLE 3

A LOSF may exist when a SUPPORT SYSTEM is INOPERABLE, and:

A required SYSTEM redundant to the SU PPORT SYSTEM(S) for the SUPPORTED SYSTEM(S) (a) and (b) above is also INOPERABLE.

If SYSTEM 2 of Train A is INOPER ABLE, and SYSTEM 1 of Train B is INOPERABLE, a LOSF may exist in SYSTEM(S) 2, 4, 5, 8, 9, 10 and 11.

EXAMPLES TRAIN A TRAIN B System 8 System 8 System 4 System 4 System 9 System 9 System 2 System 2 System 10 System 10 System 5 System 5 System 11 System 11 System 1 System 1 System 12 System 12 System 6 System 6 System 13 System 13 System 3 System 3 System 14 System 14 System 7 System 7 System 15 System 15 Note: Chart reads from left to right, i.e., SYSTEM 1 is a SUPPORT SYSTEM for SYSTEM(S) 2 through 15.

TRM Appendix C SFDP ATTACHMENT 1 (Continued) LOSS OF SAFETY FUNCTION EVALUATION Quad Cities 1 & 2 C-17 Revision 0 Method 2: TS LCO Function Method 2: TS LCO Function

a. In certain cases, multiple SYSTEM(S) with diverse individual functions are specified under one TS LCO statement; i.e., in one Technical Specification. For these cases, the safety function may be considered to be broader than the individual SYSTEM(S) function - the safety function is the Technical Specification LCO function, not the SYSTEM(S) function (as described in Method 1 above).
b. An example of this is TS 3.5.1, "ECCS-Operating," in which four different SYSTEM(S) are included. In this case, the function as stated in the Bases, "-to cool the core during a LOCA," may be the safety function to be considered in the SFDP.
c. If a loss of TS LCO function is determined to exist, the appropriate Conditions and Required Actions for a LOSF may be taken or alternatively, the following method below may be used.

Method 3: Safety Analysis

In this approach, the function of the SYSTEM(S) described in the UFSAR accident analyses is considered to be the safety function. If the SYSTEM(S) in question is not credited in the accident analyses, or if the accident function it performs is intact, then no LOSF exists. However, if the SYSTEM(S) function is credited and is lost (i.e., the accident function it performs cannot be met), then the appropriate ACTIONS for a LOSF must be taken.

TRM Appendix C SFDP ATTACHMENT 1 (Continued) LOSS OF SAFETY FUNCTION EVALUATION Quad Cities 1 & 2 C-18 Revision 0 B. Loss of Safety Function (LOSF) Evaluation

Is there any INOPERABLE or degraded SUPPORT SYSTEM(S) or SUPPORTED SYSTEM(S) equipment on the opposite/redundant train that, when coupled with this INOPERABLE equipment, might result in a complete loss of a Tech Spec required safety function.

1. NO - No LOSF exists. No further evaluation is necessary.
2. YES - A LOSF may exist. Evaluate which of the following conditions apply:
a. The SYSTEM(S) is part of an TS LCO with multiple SUBSYSTEM(S) and the TS LCO specified function is intact. No LOSF exists.
b. The SYSTEM(S) will still perform its required safety function as defined in the UFSAR. No LOSF exists.
c. A LOSF exists. Perform the Required Actions in which the LOSF exists for the specific Condition(s) that apply.

C. SUPPORTED SYSTEM LOSF

When a LOSF is determined to exist, and the SFDP requires entry into the appropriate Conditions and Required Actions of the LCO in which the LOSF exists, consideration must be given to the specific type of function affected.

1. SINGLE SUPPORT SYSTEM INOPERABILITY-

When a LOSF is solely due to a single T.S. SUPPORT SYSTEM ( e.g., loss of a pump suction source due to low tank level ) the appropriate LCO is the LCO for the SUPPORT SYSTEM. The Actions for the SUPPORT SYSTEM LCO

adequately address the in operabilities of that syst em without reliance upon the Actions of the SUPPORTED SYSTEM.

2. MULTIPLE SUPPORT SYSTEM INOPERABILITY-

When a LOSF is due to multiple T.S. SUPPORT SYSTEM inoperabilities, the appropriate LCO is the LCO for the SUPPORTED SYSTEMS.

TRM Appendix C SFDP Quad Cities 1 & 2 C-19 Revision 0 ATTACHMENT 2 SUPPORTED SYSTEM (S) CO MPLETION TIME EXTENSIONS BACKROUND The T.S. require declaring SUPPORTED SYSTEM(S) INOPERABLE if a SUPPORT SYSTEM(S) inoperability renders the SUPPORTED SYSTEM(S) incapable of performing its required function. However, the Conditions and Required Actions of the SUPPORTED SYSTEM(S) do not have to be entered (i.e., the Conditions and Required Actions are not entered) except as directed by the SUPPORT SYSTEM(S) Required Actions.

Consequently, it is possible to have SU PPORTED SYSTEM(S) I NOPERABLE for longer periods of time than their respective Completion Time would allow on their own. Per Technical Specifications 5.5.11, the SFDP must include measures to ensure that the SUPPORTED SYSTEM('S) Completion Times are not inappropriately extended.

The following two methods are provided for ensuring Completion Times are not inappropriately extended. METHOD 1 applies to SUPPORTED SYSTEM inoperabilities associated with a single SUPPORT SYSTEM inoperability. METHOD 2 is applicable to those SUPPORTED SYSTEM inoperabilities due to multiple SUPPORT SYSTEM inoperabilities.

METHOD 1 Single SUPPORT SYSTEM(S) INOPERABLE affecting SUPPORTED SYSTEM(S)

1. With a single SUPPORT SYSTEM(S) INOPERABLE, the affected SUPPORTED SYSTEM(S) Conditions and Required Actions are not required to be entered unless directed by

the SUPPORT SYSTEM(S) Required Actions.

2. The method to accomplish this will be in the form of a calculated Maximum Out Of Service Time (MOST). The MOST will ensure that a time limit is placed on the INOPERABLE SUPPORTED SYSTEM(S) such that when an additional SUPPORT SYSTEM(S) becomes INOPERABLE no extension of time is added to the original MOST. MOST is only used when implementing the SFDP.
3. The MOST is calculated in the following manner:

Support LCO Required Action Completion Time + Supported LCO Required Action = MOST Completion Time Support Train A, LCO AAA (72hrs) +

Supported Train A, LCO BBB (72 hrs)=144 hrs

+ Supported Train A, LCO UUU (72 hrs)=144 hrs

+ Supported Train A, LCO ZZZ(72 hrs)=240 hrs

+ Supported Train A, LCO RRR (168 hrs) = 240 hrs

TRM Appendix C SFDP ATTACHMENT 2 (Continued)

SUPPORTED SYSTEM (S) COMPLETION TIME EXTENSIONS Quad Cities 1 & 2 C-20 Revision 0 EXAMPLE 1 Single SUPPORT SYSTEM(S) inoperable affecting SUPPORTED SYSTEM(S)

While in Mode 1, the A and B RHRSW SUBSYSTEM Pumps are declared inoperable at 0800 on 8/13/01. TS LCO 3.7.1 Conditions and Required Actions are entered. A LOSF is performed and all B train components are verified to be operable. Therefore, the TS LCO 3.0.6 and the SFDP can be implemented. All SUPPORTED SYSTEM(S) have been identified and the calculated MOST are as follows:

SUPPORT / SUPPORTED SYSTEM(S)

LCO CONDITION COMPLETION TIME MOST RHRSW Pump (A & B) Support 3.7.1 A.1 30 days RHRSW SUBSYSTEM Support 3.7.1 C.1 7 days RHR Suppression Pool Cooling Supported 3.6.2.4 A.1 7 days 14 days RHR Suppression Pool Spray Supported 3.6.2.4 A.1 7 days 14 days 3.7.1 Condition A applies to both inoperable pumps. One RHRSW pump must be operable at 0800 on 8/20/01 (7 days) at which time the RH R Suppression Pool Cooling and Spray are operable. The RHR Suppression Pool Cooling and Spray must be operable at 0800 on 8/27/01 (MOST). The second RHRSW pump must be operable at 0800 on 9/12/01 (30 days).

TRM Appendix C SFDP ATTACHMENT 2 (Continued)

SUPPORTED SYSTEM (S) COMPLETION TIME EXTENSIONS Quad Cities 1 & 2 C-21 Revision 0 EXAMPLE 2 With the A and B RHRSW pumps still inoperable, the A and B RHR pumps are determined to be inoperable at 0800 on 8/19/01. TS LCO 3.6.2.3, 3.6.2.4 Conditions and Required Actions are evaluated. It has been determined that both Condition 3.6.2.3.A and 3.6.2.4.A are now applicable.

SUPPORT / SUPPORTED SYSTEM(S)

LCO CONDITION COMPLETION TIME MOST RHRSW Pump (A & B) Support 3.7.1 A.1 30 days RHRSW SUBSYSTEM Support 3.7.1 C.1 7 days ECCS - Operating (LPCI A & B) Support 3.5.1.A.1 30 days ECCS - Operating Support 3.5.1.B.1 7 days RHR Suppression Pool Cooling Support 3.6.2.3 A.1 7 days RHR Suppression Pool Cooling Supported 3.6.2.3 A.1 7 days 14 days RHR Suppression Pool Spray Support 3.6.2.4 A.1 7 days RHR Suppression Pool Spray Supported 3.6.2.4 A.1 7 days 14 days One RHRSW pump must be operable at 0800 on 8/20/01 (7 days). The A and B RHR pumps must be operable at 0800 on 8/26/01 (7 days). The RHR Suppression Pool Cooling and Spray must still be operable at 0800 on 8/27/01 (MOST). The second RHRSW pump must still be operable at 0800 on 9/12/01 (30 days).

TRM Appendix C SFDP ATTACHMENT 2 (Continued)

SUPPORTED SYSTEM (S) COMPLETION TIME EXTENSIONS Quad Cities 1 & 2 C-22 Revision 0 EXAMPLE 3 The A RHRSW pump is declared operable at 1000 on 8/19/01 while the A and B RHR pumps remain inoperable. TS LCO 3.7.1 Conditions and Required Actions are evaluated. It has been determined that Condition 3.7.1.C for the RHRSW system is no longer applicable.

SUPPORT / SUPPORTED SYSTEM(S)

LCO CONDITION COMPLETION TIME MOST RHRSW Pump A Support 3.7.1 A.1 30 days ECCS - Operating (LPCI A & B) Support 3.5.1.A.1 30 days ECCS - Operating Support 3.5.1.B.1 7 days RHR Suppression Pool Cooling Support 3.6.2.3 A.1 7 days RHR Suppression Pool Spray Support 3.6.2.4 A.1 7 days RHR Suppression Pool Cooling Supported 3.6.2.3 A.1 7 days 14 days RHR Suppression Pool Spray Supported 3.6.2.4 A.1 7 days 14 days The RHR A and B pumps must be operable at 0800 on 8/26/01 (7 days) which supports the restoration of both RHR Suppr ession Pool Cooling / Spray and ECCS LCOs. The RHR Suppression Pool Cooling and Spray mu st be operable at 0800 on 8/27/01 (Original MOST). The second RHRSW pump must be ope rable at 0800 on 9/12/01 (30 days).

TRM Appendix C SFDP ATTACHMENT 2 (Continued)

SUPPORTED SYSTEM (S) COMPLETION TIME EXTENSIONS Quad Cities 1 & 2 C-23 Revision 0 EXAMPLE 4 With the A and B RHR and B RHRSW pumps still inoperable, the A RHRSW pump is again determined to be inoperable at 0800 on 8/25/01. TS LCO 3.7.1.C Conditions and Required Actions are entered.

SUPPORT / SUPPORTED SYSTEM(S)

LCO CONDITION COMPLETION TIME MOST RHRSW Pump (A & B) Support 3.7.1 A.1 30 days RHRSW SUBSYSTEM Support 3.7.1 C.1 7 days ECCS - Operating (LPCI A & B) Support 3.5.1.A.1 30 days ECCS - Operating Support 3.5.1.B.1 7 days RHR Suppression Pool Cooling Support 3.6.2.3 A.1 7 days RHR Suppression Pool Spray Support 3.6.2.4 A.1 7 days RHR Suppression Pool Cooling Supported 3.6.2.3 A.1 7 days 14 days RHR Suppression Pool Spray Supported 3.6.2.4 A.1 7 days 14 days The A and B RHR pumps must be operable at 0800 on 8/26/01. The RHR Suppression Pool Cooling and Sprays must be operable at 0800 on 8/27/01 (Original MOST).

Therefore, at least one of the RHRSW pumps must be operable 0800 on 8/27/01 in order for the RHR Suppression Pool Cooling and Spray to be operable.

If the B RHRSW pump is made operable, then the A RHRSW pump must be operable at 0800 on 9/13/01 (30 days + 24 hour2.777778e-4 days <br />0.00667 hours <br />3.968254e-5 weeks <br />9.132e-6 months <br /> exte nsion allowed by TS 1.3)

TRM Appendix C SFDP ATTACHMENT 2 (Continued)

SUPPORTED SYSTEM (S) COMPLETION TIME EXTENSIONS Quad Cities 1 & 2 C-24 Revision 0 EXAMPLE 5 A Division 1 Core Spray Pump Discharge Flow - Low (BYPASS) instrument has become inoperable. TS LCO 3.3.5.1 Conditions and Required Actions are entered. A LOSF is performed and all Division 2 components are verified to be operable. Therefore, the TS LCO 3.0.6 and the SFDP can be implemented. All SUPPORTED SYSTEM(S) have been identified and the calculated MO ST are as follows:

SUPPORT / SUPPORTED SYSTEM(S)

LCO CONDITION COMPLETION TIME MOST Core Spray Pump Discharge Flow Support 3.3.5.1 E.2 7 Days ECCS SYSTEM (CS) Supported 3.5.1 B.1 7 Days 14 Days In this example, the channel must be restored to operable status within 7 Days per Required Action 3.3.5.1.E.2, or the Supported CS pumps mu st be declared inoperable per 3.3.5.1.H..1.

TRM Appendix C SFDP ATTACHMENT 2 (Continued)

SUPPORTED SYSTEM (S) COMPLETION TIME EXTENSIONS Quad Cities 1 & 2 C-25 Revision 0 METHOD 2 Multiple SUPPORT SYSTEM(S) become INOPERABLE affecting the same SUPPORTED SYSTEM(S)

There may be some cases where two SUPPORT SYSTEMS for a common SUPPORTED SYSTEM become INOPERABLE simultaneously. In this case, the following method should be used to calculate the MOST.

a. The first SUPPORT / SUPPORTED MOST plus an additional 24 hours2.777778e-4 days <br />0.00667 hours <br />3.968254e-5 weeks <br />9.132e-6 months <br />; or
b. The subsequent SUPPORT / SUPPORTED MOST as measured from discovery of the first SUPPORT inoperability.

EXAMPLE 1- Multiple SUPPORT SYSTEM(S)

Two SUPPORT SYSTEM(S) become INOPERABLE at different times.

1. SYSTEMS B and C SU PPORT SYSTEM A.

SYSTEM B (SUPPORT SYSTEM) becomes INOPERABLE at T = 0 days.

  • SYSTEM A (SUPPORTED SYSTEM) Completion Time - 3 days
  • SYSTEM B (SUPPORT SYSTEM) Completion Time - 3 days
  • SYSTEM C (SUPPORT SYSTEM) Completion Time - 7 days
2. SYSTEM B (SUPPORT SYSTEM) with a Completion Time of 3 days, renders SYSTEM A (SUPPORTED SYSTEM) INOPER ABLE. Method 1 is applied, which allows an overall MOST of 6 days for the SYSTEM A (SUPPORTED SYSTEM).
3. At T = 1 day, SYSTEM C (SUPPORT SYSTEM) becomes INOPERABLE and has a Completion Time of 7 days. SYSTEM C (SUPPORT SYSTEM) also supports SYSTEM A (SUPPORTED SYSTEM). SYSTEM B (SUPPORT SYSTEM) continues to remain INOPERABLE through its Completion Time T = 3 days.
4. Once SYSTEM C (SUPPORT SYSTEM) becomes INOPERABLE concurrent with SYSTEM B, Method 2 is applied at T=1, the Most is as follows:

Method 2a: Original MOST ( SY STEM A +B) + 24 hours2.777778e-4 days <br />0.00667 hours <br />3.968254e-5 weeks <br />9.132e-6 months <br /> = 7days, OR Method 2b: New MOST ( SYSTEM A + C ) = 10 days measured from T = 0.

TRM Appendix C SFDP Quad Cities 1 & 2 C-26 Revision 0 ATTACHMENT 3 SFDP TRACKING WORKSHEET INSTRUCTIONS The Safety Function Determination (SFD) Worksheet is used to document the supported systems of an I NOPERABLE SUPPORT SYSTEM, tr ack their Maximum Out Of Service Time (MOST), and document whether or not a lo ss of safety function exists. It is also the mechanism for documenting the reevaluation of safety function determinations that are necessary when subsequent LCO's are entered.

1. Enter the noun name of the INOPERABLE SUPPORT SYSTEM / component.
2. SUPPORT SYSTEM Tech Sp ec Condition / Required Action.
3. Date and time of entry into LCO Conditions and Required Actions for the SUPPORT SYSTEM.
4. Completion time allowed for the Required Ac tion of the SUPPORT SYSTEM Tech Spec.
5. Enter the noun name of each Tech Spec system supported by the INOPERABLE SUPPORT SYSTEM.
6. For each supported system, list the Tech Spec Condition / Required Action.
7. Record the allowed completion time for the supported system Required Action.
8. Perform a cross train check (ATTACHMENT 1/ Method 1 and TABLE 1) to verify operability of the INOPERABLE supported system's redundant equipment, as well as the support features for the redundant equipment. Bl ock 8 is filled in with yes or no.

TRM Appendix C SFDP ATTACHMENT 3 (Continued)

SFDP TRACKING WORKSHEET Quad Cities 1 & 2 C-27 Revision 0

9. Based on the results of the cross train check performed in step 8 of the worksheet, determine whether or not the safety func tion of the supported system has been lost. If the cross train check, ATTACHME NT 1/ Method 1 has failed or can not be performed, Methods 2 or 3 may be used to assess the status of the safety function in question. If the safety function has been lost, then enter the appro priate Conditions and Required Actions for that system or component using the following guidance: 1. SINGLE SU PPORT SYSTEM INOPERABILITY- When a LOSF is solely due to a single T.S. SUPPORT SYSTEM ( e.g., loss of a pump suction source due to low tank level ) the appropriate LCO is the LCO for the SUPPORT SYSTEM. The Actions for the SUPPORT SYSTEM LCO adequately address the inoperabilities of that system without reliance upon the Actions of the SUPPORTED SYSTEM. 2.

MULTIPLE SUPPORT SYSTEM INOPERABILITY- When a LOSF is due to multiple T.S. SUPPORT SYSTEM inoperabilities, the appropriate LCO is the LCO for the SUPPORTED SYSTEMS.

10. If the safety function has not been lost or LOSF is solely due to a single T.S. support system, calculate the Maximum Out of Service Time for the supported system. If ATTACHMENT 2 Method 1 is used, this will be the sum of block 4 and block 7. If Method 2 is used, see ATTACHMENT 2.
11. Expiration time: Time determined in either Method 1 or 2 ATTACHMENT 2 measured from the time in step 3 (Date/Time Entered) in HR: MIN on the MM/DD/YR.
12. The comment block can be used to record any notes or other references.
13. Preparer sign and date.
14. Sign and date for Verification of the SFD, indicating that you c oncur with the listed results.
15. As subsequent inoperabilities occur, all existing SFD's must be reviewed to determ ine their validity. Record the new LCO C ondition and Required Actions and initial and da te indicating either yes, the SFD is still valid, or no the SFD is no longer valid. If the SFD is no longer valid based on the new LCO Conditions and Required Actions, a new SFD must be performed. Attach the new SFD to the now invalid SFD.
16. The SFD may be closed out when the INOPERABLE SUPPORT SYSTEM and SUPPORT ED SYSTEM(S) listed on the SFDP Tracking Sheet are returned to OPERABLE STATUS. Enter the Time and Date when the SUPPORT SYSTEM and SUPPORTED SYSTEM(S) are returned to OPERABLE STATUS and sign the Worksheet.

TRM Appendix C SFDP ATTACHMENT 3 (Continued)

SFDP TRACKING WORKSHEET Quad Cities 1 & 2 C-28 Revision 0 SUPPORT SYSTEM INOPERABLE

1. System Name / Component 2. Tech Spec Condition / Required Action
3. Date / Time Entered
4. Completion Time SUPPORTED SYSTEMS / COMPONENTS 5. Supported System Name 6. T.S. Condition / Required Action 7. Completion Time 8. Redundant Inoperability? 9. Loss of Safety Function? 10. M.O.S.T. 11. Expiration Time 12. Comments 13. Prepared by:
14. Verified by:

sign and date sign and date

15. REVIEW FOR SUBSEQUENT INOPERABILITIES (See Attached Worksheet)
16. SFD CLOSE OUT: The Support Systems and Supported System(s) listed above have been returned to OPERABLE status

Time / Date / Signature TRM Appendix C SFDP ATTACHMENT 3 (Continued)

SFDP TRACKING WORKSHEET Quad Cities 1 & 2 C-29 Revision 0 SFDP REVIEW FOR SUBSEQUENT INOPERABILITIES NEW LCO CONDITION #

SFDPs VALID (Y / N) VERIFIED BY (INITIAL / DATE)

TRM Appendix C SFDP Quad Cities 1 & 2 C-30 Revision 0 TABLE 1 CROSS TRAIN CHECK GUIDANCE Guidelines for Performing Cross Train Checks The following matrix is meant to list possible SUPPORT to SUPPORTED LCO relationships for the purpose of implementing the cross train checks as required by LCO 3.0.6. and 5.5.11.

This matrix does NOT:

  • Cover all possible combinations or permutations of SUPPORT / SUPPORTED LCO relationships.
  • Cover SUPPORT / SUPPORTED relationships for items outside of Tech Spec (i.e., room coolers or snubbers).
  • Cover SUPPORT / SUPPORTED relationships for LCOs that are NOT applicable in a given mode
  • Cover Technical Requirement Manual LCOs or features.
  • Include Support Features and Supported Systems if the Required Actions for the INOPERABLE Support Feature direct the entry into the TS ACTIONS for the Supported System. The purpose behind this matrix is to provide guidance when assessing a LOSF on based on SUPPORTED system LCOs, due to inoperability of a SUPPORT SYSTEM LCO.

The following minimum items should be considered when evaluating the redundant train:

  • Panel Walkdown
  • DEL Review
  • Schedule Review
  • Current Outage Reports
  • Physical walkdown as needed by the US
  • Operability Evaluations Each situation should be assessed on its own merit, to determine LCO impact.

TRM Appendix C SFDP Quad Cities 1 & 2 C-31 Revision 0 TABLE 1 (Continued)

CROSS TRAIN CHECK GUIDANCE Support Feature TS

Number

Support Feature Supported

System TS

Number

Supported System 3.3.5.1 Emergency Core Cooling System (ECCS) Instrumentation 3.5.1 3.5.2

3.8.1

3.8.2 ECCS - Operating

ECCS - Shutdown

AC Sources - Operating

AC Sources - Shutdown 3.3.5.2 Reactor Core Isolation Cooling (RCIC) System Instrumentation3.5.3 RCIC System 3.3.6.1 Primary Containment Isolation Instrumentation 3.1.7

3.4.7

3.4.8

3.6.1.3

3.9.8

3.9.9 Standby Liquid Control (SLC) System

Residual Heat Removal (RHR)

Shutdown Cooling System - Hot

Shutdown

Residual Heat Removal (RHR)

Shutdown Cooling System - Cold

Shutdown

Primary Containment Isolation Valves (PCIVs) Residual Heat Removal (RHR)

Residual Heat Removal (RHR) - High

Water Level

Residual Heat Removal (RHR) - Low

Water Level 3.3.6.2 Secondary Containment Isolation Instrumentation 3.6.4.2

3.6.4.3 Secondary Containment Isolation Valves (SCIVs)

Standby Gas Treatment (SGT) System 3.3.6.3 Relief Valve Instrumentation 3.4.3

3.6.1.6 Safety and Relief Valves

Low Set Relief Valves

TRM Appendix C SFDP Quad Cities 1 & 2 C-32 Revision 0 Support Feature TS

Number

Support Feature Supported

System TS

Number

Supported System 3.3.7.1 Control Room Emergency Ventilation (CREV) System Instrumentation 3.7.4 Control Room Emergency Ventilation (CREV) System 3.3.8.1 Loss of Power (LOP) System Instrumentation 3.3.5.1

3.8.1

3.8.2 Emergency Core Cooling System (ECCS) Instrumentation

AC Sources - Operating

AC Sources - Shutdown 3.6.1.7 Reactor Building-to-Suppression Chamber Vacuum

Breakers 3.6.1.1 Primary Containment 3.6.1.8 Suppression Chamber-to-Drywell Vacuum Breakers Secondary Containment Isolation Valves (SCIVs) 3.6.1.1 Primary Containment 3.6.4.2 Secondary Containment Isolation Valves (SCIVs) 3.6.4.1 Secondary Containment 3.6.4.3 Standby Gas Treatment (SGT) System 3.6.4.1 Secondary Containment

TRM Appendix C SFDP Quad Cities 1 & 2 C-33 Revision 0 TABLE 1 (Continued)

CROSS TRAIN CHECK GUIDANCE Support Feature TS

Number

Support Feature Supported

System TS

Number

Supported System 3.7.1 Residual Heat Removal Service Water (RHRSW) System 3.4.7

3.4.8

3.6.2.3

3.6.2.4

3.7.5

3.9.8

3.9.9 Residual Heat Removal (RHR)

Shutdown Cooling System - Hot

Shutdown

Residual Heat Removal (RHR)

Shutdown Cooling System - Cold

Shutdown

Residual Heat Removal (RHR)

Suppression Pool Cooling

Residual Heat Removal (RHR)

Suppression Pool Spray

Control Room Emergency Ventilation Air Conditioning (AC) System

Residual Heat Removal (RHR) - High

Water Level

Residual Heat Removal (RHR) - Low

Water Level 3.7.2 Diesel Generator Cooling Water (DGCW) System 3.5.1

3.5.2

3.8.1

3.8.2 ECCS - Operating

ECCS - Shutdown

AC Sources - Operating

AC Sources - Shutdown 3.7.3 Ultimate Heat Sink (UHS) 3.7.1

3.7.2 Residual Heat Removal Service Water (RHRSW) System

Diesel Generator Cooling Water (DGCW) System 3.8.1 AC Sources - Operating 3.8.7 Distribution System - Shutdown (AC Portion Only) 3.8.2 AC Sources - Shutdown 3.8.8 Distribution System - Shutdown (AC Portion Only) 3.8.4 DC Sources - Operating 3.8.7 Distribution System - Shutdown (DC Portion Only) 3.8.5 DC Sources - Shutdown 3.8.8 Distribution System - Shutdown (DC Portion Only)

TRM Appendix C SFDP TABLE 1 (Continued)

CROSS TRAIN CHECK GUIDANCE Quad Cities 1 & 2 C-34 Revision 0 Support Feature TS

Number Support Feature Supported System TS

Number Supported System 3.8.7 (AC Only)

Distribution System -

Operating (AC portion Only) 3.1.7

3.3.3.1

3.3.5.1

3.3.5.2

3.3.6.1

3.3.6.2

3.3.7.1

3.4.4

3.4.5

3.4.7

3.5.1

3.5.3 Standby Liquid Control (SLC)

System

Post Accident Monitoring (PAM)

Instrumentation

Emergency Core Cooling System (ECCS) Instrumentation

Isolation Condenser (IC) System Instrumentation (17 & 20 valves)

Primary Containment Isolation Instrumentation

Secondary Containment Isolation Instrumentation

Control Room Emergency Ventilation (CREV) System Instrumentation

RCS Operational Leakage

RCS Leakage Detection Instrumentation

Residual Heat Removal (RHR)

Shutdown Cooling System - Hot

Shutdown

Emergency Core Cooling System (ECCS) - Operating

RCIC System

TRM Appendix C SFDP TABLE 1 (Continued)

CROSS TRAIN CHECK GUIDANCE Quad Cities 1 & 2 C-35 Revision 0 Support Feature TS

Number Support Feature Supported System TS

Number Supported System 3.8.7 (continued)

(AC Only)

Distribution System -

Operating (AC portion Only) 3.6.1.3

3.6.2.3

3.6.2.4

3.6.4.2

3.6.4.3

3.7.1

3.7.2

3.7.4

3.7.5

3.7.9

3.8.1

3.8.3

3.8.4 Primary Containment Isolation

Valves (PCIVs)

Residual Heat Removal (RHR)

Suppression Pool Cooling

Residual Heat Removal (RHR)

Suppression Pool Spray

Secondary Containment Isolation Valves (SCIVs)

Standby Gas Treatment (SGT)

System

Residual Heat Removal Service Water (RHRSW) System

Diesel Generator Cooling Water (DGCW) System

Control Room Emergency Ventilation (CREV) System

Control Room Emergency Ventilation Air Conditioning (AC) System

Safe Shutdown Makeup Pump (SSMP) System

AC Sources - Operating

Diesel Fuel Oil and Starting Air

DC Sources - Operating

TRM Appendix C SFDP TABLE 1 (Continued)

CROSS TRAIN CHECK GUIDANCE Quad Cities 1 & 2 C-36 Revision 0 Support Feature TS

Number Support Feature Supported System TS

Number Supported System 3.8.7 (DC Only) Distribution Systems -

Operating (DC Only) 3.3.3.1

3.3.4.1

3.3.5.1

3.3.5.2

3.3.6.1

3.3.8.1

3.3.8.2

3.4.3

3.4.7

3.5.1 Post Accident Monitoring (Pam) Instrumentation

Anticipated Transient Without SCRAM Recirculation Pump

Trip (ATWS-RPT)

Instrumentation

Emergency Core Cooling System (ECCS) Instrumentation

Reactor Core Isolation Cooling (RCIC) System Instrumentation

Primary Containment Isolation Instrumentation

Loss of Power (LOP) System Instrumentation

Reactor Protection System (RPS) Electric Power Monitoring

Safety and Relief Valves

Residual Heat Removal (RHR)

Shutdown Cooling System -

Hot Shutdown

Emergency Core Cooling System (ECCS) - Operating

TRM Appendix C SFDP TABLE 1 (Continued)

CROSS TRAIN CHECK GUIDANCE Quad Cities 1 & 2 C-37 Revision 0 Support Feature TS

Number Support Feature Supported System TS

Number Supported System 3.8.7 (continued)

(DC Only) Distribution Systems -

Operating (DC Portion Only) 3.5.3

3.6.1.3

3.6.2.3

3.6.2.4

3.7.1

3.7.2

3.8.1 RCIC System

Primary Containment Isolation

Valves (PCIVs)

Residual Heat Removal (RHR)

Suppression Pool Cooling

Residual Heat Removal (RHR)

Suppression Pool Spray

Residual Heat Removal Service

Diesel Generator Cooling Water (DGCW) System

AC Sources - Operating

TRM Appendix C SFDP TABLE 1 (Continued)

CROSS TRAIN CHECK GUIDANCE Quad Cities 1 & 2 C-38 Revision 0 Support Feature TS

Number Support Feature Supported System TS

Number Supported System 3.8.8 (AC Only) Distribution Systems -

Shutdown (AC Portion Only) 3.3.5.1

3.3.6.1

3.3.6.2

3.3.7.1

3.4.8

3.5.2

3.6.1.3 3.6.4.2 Emergency Core Cooling System (ECCS) Instrumentation

Primary Containment Isolation Instrumentation

Secondary Containment Isolation Instrumentation

Control Room Air Filtration (CREV) System Instrumentation

Residual Heat Removal (RHR)

Shutdown Cooling System Cold

Shutdown

Emergency Core Cooling System (ECCS) - Shutdown

Primary Containment Isolation Valves (PCIVs)

Secondary Containment Isolation Valves (SCIVs)

TRM Appendix C SFDP TABLE 1 (Continued)

CROSS TRAIN CHECK GUIDANCE Quad Cities 1 & 2 C-39 Revision 0 Support Feature TS

Number Support Feature Supported System TS

Number Supported System 3.8.8 (continued)

(AC Only) Distribution Systems -

Shutdown (AC Portion Only) 3.6.4.3

3.7.1

3.7.2

3.7.4

3.7.5

3.8.2

3.8.3

3.8.5

3.9.8 3.9.9 Standby Gas Treatment (SGT) System

Residual Heat Removal Service Water (RHRSW) System

Diesel Generator Cooling Water (DGCW) System

Control Room Emergency Ventilation (CREV) System

Control Room Emergency Ventilation Air Conditioning (AC) System

AC Sources - Shutdown

Diesel Fuel Oil and Starting Air

DC Sources - Shutdown

Residual Heat Removal (RHR) - High Water Level

Residual Heat Removal (RHR) - Low

Water Level

TRM Appendix C SFDP TABLE 1 (Continued)

CROSS TRAIN CHECK GUIDANCE Quad Cities 1 & 2 C-40 Revision 0 Support Feature TS

Number Support Feature Supported System TS

Number Supported System 3.8.8 (DC Only) Distribution Systems -

Shutdown (DC Portion Only) 3.3.5.1

3.3.6.1

3.3.8.1

3.3.8.2

3.4.8

3.5.2

3.6.1.3 3.8.2

3.9.8

3.9.9 Emergency Core Cooling System (ECCS) Instrumentation

Primary Containment Isolation Instrumentation

Loss of Power (LOP) System Instrumentation

Reactor Protective System (RPS) Electric Power

Monitoring

Residual Heat Removal (RHR)

Shutdown Cooling System -

Cold Shutdown

ECCS - Shutdown

Primary Containment Isolation

Valves (PCIVs)

AC Sources - Shutdown

Residual Heat Removal (RHR)-

High Water Level

Residual Heat Removal (RHR)-

Low Water Level

TRM TS Bases Control Program Appendix D Quad Cities Units 1 & 2 1 of 15 Revision QC-TRM-05-001 Technical Requirements Manual TECHNICAL SPECIFICATIONS BASES CONTROL PROGRAM TABLE OF CONTENTS SECTION TITLE 1.1 PURPOSE

1.2 REFERENCES

1.3 DEFINITIONS AND/OR ACRONYMS

1.4 PROGRAM DESCRIPTION 1.5 PROGRAM IMPLEMENTATION 1.6 ACCEPTANCE CRITERIA 1.7 LCOARS/COMPENSATORY MEASURES

1.8 REPORTING REQUIREMENTS 1.9 CHANGE CONTROL TRM TS Bases Control Program Appendix D Quad Cities Units 1 & 2 2 of 15 Revision QC-TRM-05-001 Technical Requirements Manual

1.1 PURPOSE

The purpose of this Program is to provide guidance for identifying, processing, and implementing changes to the Technical Specifications (TS) Bases. This Program implements and satisfies the requirements of TS 5.5.10, "Technical Specifications (TS)

Bases Control Program."

This Program is applicable to the preparation, review, implementation, and distribution of changes to the TS Bases. This Program also provides guidance for preparing TS Bases Change Packages for distribution.

1.2 REFERENCES

1. TS 5.5.10, "Technical Specifications (TS) Bases Control Program"
2. 10 CFR 50.4, "Written Communications" 3. 10 CFR 50.59, "Changes, Tests and Experiments"
4. 10 CFR 50.71, "Maintenance of Records, Making of Reports" 5. 10 CFR 50.90, "Application for Amendment of License or Construction Permit" 1.3 DEFINITIONS AND/OR ACRONYMS
1. 10 CFR 50.59 REVIEW - A written regulatory evaluation which provides the basis for the determination that a change does, or does not, require NRC approval pursuant to 10 CFR 50.59.

The scope of the evaluation should be commensurate with the potential safety significance of the change, but must address the relevant safety concerns included in the Safety Analysis Report and other owner controlled documents. The depth of the evaluation must be sufficient to determine whether or not NRC approval is required prior to implementation. Depending upon the significance of the

change, the evaluation may be brief; however, a simple statement of conclusion is not sufficient.

TRM TS Bases Control Program Appendix D Quad Cities Units 1 & 2 3 of 15 Revision QC-TRM-05-001 Technical Requirements Manual 2. EDITORIAL CHANGE - Editorial changes include correction of punctuation, insignificant word or title changes, style or format changes, typographical errors, or correction of

reference errors that do not change the intent, outcome, results, functions, processes, responsibilities, or performance requirements of the item being changed. Changes in numerical values shall not be considered as editorial changes. Editorial changes do not constitute a change to the TRM and therefore do not require further 10 CFR 50.59 Reviews. If the full scope of this proposed change is encompassed by one or more of the below, then the change is considered editorial.

- Rewording or format changes that do not result in changing actions to be accomplished. - Deletion of cycle-specific information that is no longer applicable. - Addition of clarifying information, such as: - Spelling, grammar, or punctuation changes - Changes to references - Name or title references 1.4 PROGRAM DESCRIPTION

1. A Licensee may make changes to the TS Bases without prior NRC approval provided the changes do not require either of the following:
a. A change in the TS as currently incorporated in the license; or
b. A change to the Updated Final Safety Analysis Report (UFSAR) or TS Bases that requires NRC approval pursuant to 10 CFR 50.59.
2. Changes that meet the above criteria (i.e., 1.4.1.a or 1.4.1.b) shall be submitted to the NRC pursuant to

10 CFR 50.90 and reviewed and approved by the NRC prior to implementation.

3. The TS Bases shall be maintained consistent with the UFSAR.

TRM TS Bases Control Program Appendix D Quad Cities Units 1 & 2 4 of 15 Revision QC-TRM-05-001 Technical Requirements Manual 4. If a change to the TS Bases is not consistent with the UFSAR, then the cognizant Engineer shall prepare and submit a UFSAR Change Package when the TS Bases Change Request is

submitted to Regulatory Assurance (RA) for processing.

5. Changes to the TS Bases that do not require prior NRC approval shall be provided to the NRC on a frequency

consistent with 10 CFR 50.71(e), as modified by approved

exemptions.

6. Any change to a Station's TS Bases shall be transmitted, via Attachment D, "Technical Specifications Bases Change

Applicability Review Form," to the Regulatory Assurance Managers (RAMs) at each of the other Stations. The RAM will review the TS Bases change for applicability at their

respective Station and document their review on Attachment D.

7. TS Bases changes associated with a TS Amendment shall be implemented consistent with the implementation requirements

of the TS Amendment.

8. Cantera Licensing (CL) is responsible for the control and distribution of the TS Bases. In order to prevent

distribution errors (i.e., omissions or duplications), CL shall maintain the master TS Bases distribution list.

1.5 PROGRAM IMPLEMENTATION

1. TS Bases Change Requestor identifies the need for a revision to the TS Bases and notifies the RA Licensing Engineer (i.e., hereafter referred to as RA LE). A TS Bases change can be initiated through any Stations' RA. TS Bases Change

Requestor notifies their counterparts on the need for a change.

2. RA LE notifies their counterparts of identified need for revision to the TS Bases.
3. RA LE obtains concurrence from CL on the need for a change.

TRM TS Bases Control Program Appendix D Quad Cities Units 1 & 2 5 of 15 Revision QC-TRM-05-001 Technical Requirements Manual 4. CL Engineer (i.e., hereafter referred to as CLE) assigns a TS Bases Change Request Number (CR #) and records on Attachment B, "Technical Specifications Bases Change Request Log." The

CR # should be a sequential number beginning with the last two digits of the year (e.g., 00-00#).

5. RA LE drafts TS Bases changes considering format, rules of usage, and technical adequacy, and notifies RAMs at each of the other Stations by transmitting Attachment D, "Technical Specifications Bases Change Applicability Review Form."
6. CLE reviews the agreed upon TS Bases wording changes for consistency with format, rules of usage, and technical

adequacy and provides final concurrence.

7. After concurrence of the TS Bases wording changes is obtained, CLE makes an electronic version available in a working directory for use in the preparation of the 10 CFR 50.59 REVIEW and Station Qualified Review (SQR) process. The CLE shall ensure that the master electronic TS Bases files are revised per step 15 below upon receiving SQR approval. The Revision number in the footer should be a sequential number (i.e., 1, 2, etc.).
      • NOTE If the TS Bases changes are applicable to more than one Station, the following steps should be performed concurrently for each Station.
8. TS Bases Change Requestor provides a 10 CFR 50.59 REVIEW for the TS Bases changes in accordance with appropriate plant procedures. An exception to this requirement applies when the changes are being requested in order to reflect an approved NRC Safety Evaluation (SE) associated with a site specific Operating License or TS change. The NRC SE is sufficient to support the changes provided it has been determined that the changes are consistent with and entirely bounded by the NRC SE. A 10 CFR 50.59 REVIEW shall be performed for TS Bases changes that reflect generic industry approval by an NRC SE to determine site specific applicability. A 10 CFR 50.59 REVIEW is not required for an EDITORIAL CHANGE.

TRM TS Bases Control Program Appendix D Quad Cities Units 1 & 2 6 of 15 Revision QC-TRM-05-001 Technical Requirements Manual 9. TS Bases Change Requestor completes Attachment A, "Technical Specifications Bases Change Request Form," as follows:

a. Identifies the affected sections, and includes a copy of the proposed TS Bases changes;
b. Briefly summarizes the changes including the LCO, Action, or Surveillance Requirement to which the changes apply;
c. Briefly summarizes the reason for the changes and attaches all supporting documentation;
d. Identifies any schedule requirements and proposed implementation date that apply (i.e., describe any time limitations that might apply which would require expedited processing). If the changes are outage related, then checks "yes" and lists the applicable outage identifier;
e. Identifies any known implementation requirements such as procedure changes, UFSAR changes, Passport changes, Reportability Manual revisions, pre-

implementation training requirements, etc.;

f. If a 10 CFR 50.59 REVIEW was prepared to support the TS Bases changes, the Requestor then checks the appropriate box, lists the associated 10 CFR 50.59 REVIEW Number, and attaches the original;
g. If the changes to the TS Bases are the result of an approved NRC SE associated with a site specific Operating License or TS change and the scope of the changes determined to be consistent with and entirely bounded by the NRC SE, then the Requestor checks the appropriate box and attaches a copy;
h. If the changes to the TS Bases are EDITORIAL CHANGES, the the Requestor checks the appropriate box and no 10

CFR 50.59 REVIEW is required;

i. Signs and dates as Requestor and identifies the originating department;

TRM TS Bases Control Program Appendix D Quad Cities Units 1 & 2 7 of 15 Revision QC-TRM-05-001 Technical Requirements Manual j. Obtains approval to proceed from Department Supervisor (or designee); and

k. Returns Attachment A to the RA LE.
10. RA LE reviews the TS Bases Change Request Form, including supporting documentation, and documents the review by signing Attachment A. The review verifies that the

following information or documentation is included:

a. Completed 10 CFR 50.59 REVIEW. If the changes are related to an approved NRC SE associated with a site specific Operating License or TS change and determined to be entirely bounded by the NRC SE, then

only a copy of the SE is required to be attached and

no 10 CFR 50.59 REVIEW is required. A 10 CFR 50.59 REVIEW is not required for an EDITORIAL CHANGE;

b. Identification of known documents requiring revisions; and c. Completed UFSAR Change Request with supporting documentation, in accordance with appropriate plant procedures, if applicable.
11. If the TS Bases change is not an EDITORIAL CHANGE, the RA LE/TS Bases Change Requestor obtains SQR approval of the TS Bases changes by performing the following:
a. RA LE prepares the TS Bases Change SQR package. The SQR package shall include Attachment A (including completed 10 CFR 50.59 REVIEW or NRC SE) and the revised TS Bases pages. Attachment A is provided for the purpose of reviewing and finalizing the

implementation requirements and ensuring the necessary actions have been initiated. RA LE shall assign Action Tracking (AT) items, as necessary, to track implementation requirements;

b. TS Bases Change Requestor submits the TS Bases Change SQR package to the SQR Committee members for a preliminary review. The SQR composition shall include RA and Operating Departments in all cases; and TRM TS Bases Control Program Appendix D Quad Cities Units 1 & 2 8 of 15 Revision QC-TRM-05-001 Technical Requirements Manual c. TS Bases Change Requestor resolves preliminary review comments and finalizes the TS Bases Change SQR package.
12. The RAM shall determine the need for Plant Operations Review Committee (PORC) approval. The need for PORC approval shall

be documented on Attachment A.

13. RA LE/TS Bases Change Requestor obtains PORC approval, if necessary.
14. RA LE notifies CLE of approval of the TS Bases changes by forwarding a copy of the approved SQR/PORC Change package to CLE. 15. After approval of the TS Bases changes by SQR/PORC, CLE ensures that the controlled master electronic files are

updated.

16. CL/RA completes Attachment C, "Technical Specifications Bases Change Instruction Form," as follows:
a. CLE indicates the effective date of the TS Bases changes consistent with the SQR/PORC approval or TS amendment required implementation date. If the TS Bases change is a result of a TS Amendment, the update shall be implemented coincident with implementation

requirements of the TS Amendment. Otherwise, the update must be implemented by the date indicated on Attachment C;

b. CLE lists each page to be removed and inserted, including the Affected Page List; and
c. RA LE provides the updated master file directory for updating Electronic Document Management System (EDMS), if applicable.
17. CLE creates a TS Bases Change Package. The TS Bases Change Package shall consist of:
a. TS Bases Change Instruction Form (Attachment C);
b. Revised Affected Page List; and TRM TS Bases Control Program Appendix D Quad Cities Units 1 & 2 9 of 15 Revision QC-TRM-05-001 Technical Requirements Manual c. Revised TS Bases pages.

One CLE shall assemble and approve the TS Bases Change Package for distribution and a second CLE shall perform a peer check to verify completeness of the TS Bases Change

Package. 18. After the RA LE notifies the CLE that SQR/PORC approval of the TS Bases changes has been obtained and that all AT items assigned to track implementation requirements have been completed, CLE forwards the TS Bases Change Package to the RA LE as notification of the need to update the onsite TS

Bases controlled copies and EDMS, if applicable. CLE also forwards the TS Bases Change Package to CL Records Management as notification of the need to update the offsite (CL) TS Bases controlled copies and to transmit updates to the offsite (non-CL) TS Bases controlled copies.

19. RA LE forwards the TS Bases Change Package to Station Records Management as notification of the need to update the onsite TS Bases controlled copies and EDMS, if applicable.
20. Upon completion of updating the onsite TS Bases controlled copies and EDMS (if applicable), Station Records Management Supervisor signs and dates Attachment C and returns Attachment C to the appropriate CLE.
21. Upon completion of updating the offsite (CL) TS Bases controlled copies and transmitting updates to the offsite (non-CL) TS Bases controlled copies, CL Records Management signs and dates Attachment C and returns Attachment C to the appropriate CLE.
22. CLE updates the TS Bases Change Request Log (Attachment B) with the following information:
a. 10 CFR 50.59 REVIEW Number;
b. SQR Number, if applicable;
c. SQR Approval Date; and
d. TS Bases change implementation date.

TRM TS Bases Control Program Appendix D Quad Cities Units 1 & 2 10 of 15 Revision QC-TRM-05-001 Technical Requirements Manual 23. RA LE ensures that the documentation required to be maintained as a quality record is provided to Station Records Management for the purpose of record retention.

1.6 ACCEPTANCE CRITERIA Not applicable.

1.7 LCOARS/COMPENSATORY MEASURES An Issue Report may need to be generated to provide proper tracking and resolution of noted problems associated with the

implementation of this Program.

The RAM will be responsible for ensuring that Program failures have been resolved.

1.8 REPORTING REQUIREMENTS

  • NOTE TS Bases changes requiring prior NRC approval shall be submitted in accordance with Reference 5.

TS Bases changes not requiring prior NRC approval, as described in Section 1.4 of this Program, shall be submitted to the NRC in accordance with 10 CFR 50.71(e).

1.9 CHANGE CONTROL

Changes to this Program, other than EDITORIAL CHANGES, shall include a 10 CFR 50.59 REVIEW and a SQR. The SQR composition shall include RA Department in all cases. For a change to this Program, PORC approval from all Stations is required. The concurrence shall

be that the other Stations are implementing the same changes or that the changes have been reviewed and determined not to be applicable to the other Stations.

TRM TS Bases Control Program Appendix D Quad Cities Units 1 & 2 11 of 15 Revision QC-TRM-05-001 Technical Requirements Manual ATTACHMENT A TECHNICAL SPECIFICATIONS BASES CHANGE REQUEST FORM

1. Change Request #: _____________ Affected Bases Section(s): ________________________
2. Description of changes: __________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

3. Reason for changes (attach all supporting documentation): _____________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

4. Schedule Requirements: Outage Related (check one) No Yes, Outage # ___________ Other (explain) ____________________________________________________________________
5. Implementation Requirements (attach additional pages, as necessary):

Identify the impact of the changes on the following: Affected N/A UFSAR ______________________________________________________________

TS _________________________________________________________________

Technical Requirements Manual ______________________________________

NRC Safety Evaluation ______________________________________________

Fire Protection Report _____________________________________________

NRC Commitments ____________________________________________________

Vendor Documentation _______________________________________________

Special Permits/Licenses ___________________________________________

Procedures _________________________________________________________

Environmental Qualification ________________________________________

Design Basis Documentation _________________________________________

Engineering Calculations ___________________________________________

Drawings/Prints ____________________________________________________

PRA Information ____________________________________________________

Programs ___________________________________________________________

Reportability Manual _______________________________________________

QA Topical Report __________________________________________________

Passport ___________________________________________________________

Pre-Implementation Training Required _______________________________

Maintenance Rule ___________________________________________________

Offsite Dose Calculation Manual ____________________________________

Other ______________________________________________________________

6. Check one:

10 CFR 50.59 REVIEW Attached, 10 CFR 50.59 REVIEW #:_________________________

NRC SE Attached, Changes consistent with and entirely bounded by NRC SE EDITORIAL CHANGE, No 10 CFR 50.59 REVIEW required

7. Requestor: ______________________/______________________/________________________ (Signature) (Date) (Department)
8. Requesting Supervisor Approval: _______________________/________________________ (Signature) (Date)
9. PORC Approval Required: Yes No
10. Licensing Engineer Review: _______________________/________________________

(Signature) (Date)

TRM TS Bases Control Program Appendix D Quad Cities Units 1 & 2 12 of 15 Revision QC-TRM-005-001 Technical Requirements Manual ATTACHMENT B TECHNICAL SPECIFICATIONS BASES CHANGE REQUEST LOG CR # Brief Description of Changes Affected Section(s) 10 CFR 50.59 REVIEW # SQR # SQR Approval Date Date Implemented TRM TS Bases Control Program Appendix D Quad Cities Units 1 & 2 13 of 15 Revision QC-TRM-05-001 Technical Requirements Manual ATTACHMENT C TECHNICAL SPECIFICATIONS BASES CHANGE INSTRUCTION FORM FOR ONSITE/OFFSITE DISTRIBUTION AND FOR UPDATING EDMS

Braidwood/Byron/Dresden/LaSalle/QC (circle one) TS Bases Revision # ______

NOTE: This change is effective as of _____________________________ and shall be implemented by __________ . (SQR/PORC or Amendment Implementation Date) (Date)

Approved for distribution: ___________________________________/_____________ (CLE Signature) (Date)

Verified: ___________________________________/_____________ (CLE Signature) (Date)

REMOVE Section REMOVE Page INSERT Section INSERT Page UPDATE EDMS Section UPDATE EDMS Page Affected

Page List All Affected Page List All N/A N/A

TRM TS Bases Control Program Appendix D Quad Cities Units 1 & 2 14 of 15 Revision QC-TRM-05-001 Technical Requirements Manual ATTACHMENT C TECHNICAL SPECIFICATIONS BASES CHANGE INSTRUCTION FORM FOR ONSITE/OFFSITE DISTRIBUTION AND FOR UPDATING EDMS Braidwood/Byron/Dresden/LaSalle/QC (circle one) TS Bases Revision # ______

___________________________________________________________________________________________

Station Records Management:

Onsite Distribution Completed: ______________________________/___________________

(Station Records Mgmt. Supr.) (Date)

EDMS Update Completed: ______________________________/___________________ (Station Records Mgmt. Supr.) (Date)

    • Return this sheet to: Cantera Licensing Braidwood/Byron/Dresden/LaSalle/QC (circle one) CL CANTERA

___________________________________________________________________________________________

CL Records Management:

Offsite (CL) Distribution Completed: ___________________________/____________________ (CL Records Mgmt.) (Date)

Offsite (non-CL) Distribution Transmitted:

___________________________/____________________ (CL Records Mgmt.) (Date)

    • Return this sheet to Braidwood/Byron/Dresden/LaSalle/QC (circle one) CL

___________________________________________________________________________________________

Offsite (non-CL) Controlled Copy Holders:

Offsite (non-CL) Distribution Completed: ___________________________/____________________ (Signature) (Date)

    • Return this sheet to: EXELON GENERATION COMPANY, LLC LICENSING AND REGULATORY AFFAIRS DEPARTMENT 4300 WINFIELD ROAD WARRENVILLE, IL 60555

TRM TS Bases Control Program Appendix D Quad Cities Units 1 & 2 15 of 15 Revision QC-TRM-05-001 Technical Requirements Manual ATTACHMENT D TECHNICAL SPECIFICATIONS BASES CHANGE APPLICABILITY REVIEW FORM Any change to a Station's Technical Specifications (TS) Bases shall be transmitted to the

Regulatory Assurance Managers (RAMs) at each of the other Stations. The RAM will review the TS Bases change for applicability at their respective Station. Review of applicability shall be documented on this Attachment and forwarded to the Regulatory Assurance Licensing

Engineer(s) at the Station(s) making the change.

Braidwood/Byron/Dresden/LaSalle/QC (circle one)

TS Bases Section(s)/Title(s): _____________________________________________________________

Description of the change: _________________________________________________________________

_____________________________________________________________________________________________

_____________________________________________________________________________________________

_____________________________________________________________________________________________

Braidwood RAM Review: ________________________/_______________ (Signature) (Date)

Change Applicable: Yes No Byron RAM Review: ________________________/_______________ (Signature) (Date)

Change Applicable: Yes No Dresden RAM Review: ________________________/_______________

(Signature) (Date)

Change Applicable: Yes No LaSalle RAM Review: ________________________/_______________ (Signature) (Date)

Change Applicable: Yes No QC RAM Review: ________________________/_______________ (Signature) (Date)

Change Applicable: Yes No

    • Return this sheet to: Regulatory Assurance Braidwood/Byron/Dresden/LaSalle/QC (circle one) Station

TRM TRM Control Program Appendix G Quad Cities Units 1 & 2 1 of 15 Revision QC-TRM-05-001 Technical Requirements Manual TECHNICAL REQUIREMENTS MANUAL CONTROL PROGRAM TABLE OF CONTENTS

SECTION TITLE 1.1 PURPOSE

1.2 REFERENCES

1.3 DEFINITIONS AND/OR ACRONYMS

1.4 PROGRAM DESCRIPTION 1.5 PROGRAM IMPLEMENTATION 1.6 ACCEPTANCE CRITERIA 1.7 LCOARS/COMPENSATORY MEASURES

1.8 REPORTING REQUIREMENTS 1.9 CHANGE CONTROL

TRM TRM Control Program Appendix G Quad Cities Units 1 & 2 2 of 15 Revision QC-TRM-05-001 Technical Requirements Manual

1.1 PURPOSE

The purpose of this Program is to provide guidance for

identifying, processing, and implementing changes to the Technical Requirements Manual (TRM). This Program implements and satisfies the requirements of TRM Section 1.6, "Technical Requirements Manual Revisions."

This Program is applicable to the preparation, review, implementation, and distribution of changes to the TRM. This Program also provides guidance for preparing TRM Change Packages for distribution.

1.2 REFERENCES

1. TRM Section 1.6, "Technical Requirements Manual Revisions" 2. 10 CFR 50.4, "Written Communications" 3. 10 CFR 50.59, "Changes, Tests and Experiments"
4. 10 CFR 50.71, "Maintenance of Records, Making of Reports" 5. 10 CFR 50.90, "Application for Amendment of License or Construction Permit" 1.3 DEFINITIONS AND/OR ACRONYMS 10 CFR 50.59 REVIEW - A written regulatory evaluation which provides the basis for the determination that a change does, or does not, require NRC approval pursuant to 10 CFR 50.59. The scope of the evaluation should be commensurate with the potential

safety significance of the change, but must address the relevant safety concerns included in the Safety Analysis Report and other owner controlled documents. The depth of the evaluation must be sufficient to determine whether or not NRC approval is required prior to implementation. Depending upon the significance of the change, the evaluation may be brief; however, a simple statement of conclusion is not sufficient.

TRM TRM Control Program Appendix G Quad Cities Units 1 & 2 3 of 15 Revision QC-TRM-05-001 Technical Requirements Manual EDITORIAL CHANGE - Editorial changes include correction of

punctuation, insignificant word or title changes, style or format changes, typographical errors, or correction of reference errors

that do not change the intent, outcome, results, functions, processes, responsibilities, or performance requirements of the item being changed. Changes in numerical values shall not be considered as editorial changes. Editorial changes do not

constitute a change to the TRM and therefore do not require

further 10 CFR 50.59 Reviews. If the full scope of this proposed change is encompassed by one or more of the below, then the change is considered editorial.

- Rewording or format changes that do not result in changing actions to be accomplished. - Deletion of cycle-specific information that is no longer applicable. - Addition of clarifying information, such as: - Spelling, grammar, or punctuation changes - Changes to references - Name or title references

1.4 PROGRAM DESCRIPTION

1. A Licensee may make changes to the TRM without prior NRC approval provided the changes do not require NRC approval

pursuant to 10 CFR 50.59.

2. Changes that require NRC approval pursuant to 10 CFR 50.59 shall be submitted to the NRC pursuant to 10 CFR 50.90 and

reviewed and approved by the NRC prior to implementation.

3. The TRM is part of the Updated Final Safety Analysis Report (UFSAR) by reference and shall be maintained consistent with the remainder of the UFSAR.
4. If a change to the TRM is not consistent with the remainder of the UFSAR, then the cognizant Engineer shall prepare and

submit a UFSAR Change Package when the TRM Change Request is submitted to Regulatory Assurance (RA) for processing.

5. Changes to the TRM that do not require prior NRC approval shall be provided to the NRC on a frequency consistent with

10 CFR 50.71(e), as modified by approved exemptions.

TRM TRM Control Program Appendix G Quad Cities Units 1 & 2 4 of 15 Revision QC-TRM-05-001 Technical Requirements Manual 6. Any change to a Station's TRM shall be transmitted, via Attachment D, "Technical Requirements Manual Change Applicability Review Form," to the Regulatory Assurance

Managers (RAMs) at each of the other Stations. The RAM will review the TRM change for applicability at their respective Station and document their review on Attachment D.

7. TRM changes associated with a Technical Specifications (TS)

Amendment shall be implemented consistent with the implementation requirements of the TS Amendment.

8. RA is responsible for the control and distribution of the TRM. In order to prevent distribution errors (i.e.,

omissions or duplications), RA shall maintain the master TRM distribution list.

1.5 PROGRAM IMPLEMENTATION

1. TRM Change Requestor identifies the need for a revision to the TRM and notifies the RA Licensing Engineer (i.e.,

hereafter referred to as RA LE). A TRM change can be

initiated through any Stations' RA. TRM Change Requestor notifies their counterparts on the need for a change.

2. RA LE notifies their counterparts of identified need for revision to the TRM.
3. RA LE assigns a TRM Change Request Number (CR #) and records on Attachment B, "Technical Requirements Manual Change

Request Log." The CR # should be a sequential number beginning with the last two digits of the year (e.g., 00-00#). 4. RA LE drafts TRM changes considering format, rules of usage, and technical adequacy, and notifies RAMs at each of the

other Stations by transmitting Attachment D, "Technical Requirements Manual Change Applicability Review Form."

TRM TRM Control Program Appendix G Quad Cities Units 1 & 2 5 of 15 Revision QC-TRM-05-001 Technical Requirements Manual

5. RA LE makes an electronic version of the proposed TRM changes available in a working directory for use in the preparation of the 10 CFR 50.59 REVIEW and Station Qualified Review (SQR) process. The RA LE shall ensure that the master electronic TRM files are revised per step 12 below upon

receiving SQR approval. The Revision number in the footer should be a sequential number (i.e., 1, 2, etc.).

          • NOTE If the TRM changes are applicable to more than one Station, the following steps should be performed concurrently for each Station.
6. TRM Change Requestor provides a 10 CFR 50.59 REVIEW for the TRM changes in accordance with appropriate plant procedures.

An exception to this requirement applies when the changes are being requested in order to reflect an approved NRC Safety Evaluation (SE) associated with a site specific Operating License or TS change. The NRC SE is sufficient to support the changes provided it has been determined that the

changes are consistent with and entirely bounded by the NRC SE. A 10 CFR 50.59 REVIEW shall be performed for TRM changes that reflect generic industry approval by an NRC SE to determine site specific applicability. A 10 CFR 50.59 REVIEW is not required for an EDITORIAL CHANGE.

7. TRM Change Requestor completes Attachment A, "Technical Requirements Manual Change Request Form," as follows:
a. Identifies the affected sections, and includes a copy of the proposed TRM changes;
b. Briefly summarizes the changes including the TLCO, Action, Surveillance Requirement, or Bases (if

applicable) to which the changes apply;

c. Briefly summarizes the reason for the changes and attaches all supporting documentation;
d. Identifies any schedule requirements and proposed implementation date that apply (i.e., describe any

time limitations that might apply which would require expedited processing). If the changes are outage

related, then checks "yes" and lists the applicable outage identifier;

TRM TRM Control Program Appendix G Quad Cities Units 1 & 2 6 of 15 Revision QC-TRM-05-001 Technical Requirements Manual e. Identifies any known implementation requirements such as procedure changes, UFSAR changes, Passport changes, Reportability Manual revisions, pre-implementation training requirements, etc.;

f. If a 10 CFR 50.59 REVIEW was prepared to support the TRM changes, the Requestor then checks the appropriate

box, lists the associated 10 CFR 50.59 REVIEW Number, and attaches the original;

g. If the changes to the TRM are the result of an approved NRC SE associated with a site specific Operating License or TS change and the scope of the changes determined to be consistent with and entirely

bounded by the NRC SE, then the Requestor checks the

appropriate box and attaches a copy;

h. If the changes to the TRM are EDITORIAL CHANGES, then the Requestor checks the appropriate box and no 10 CFR

50.59 REVIEW is required;

i. Signs and dates as Requestor and identifies the originating department;
j. Obtains approval to proceed from Department Supervisor (or designee); and
k. Returns Attachment A to the RA LE.
8. RA LE reviews the TRM Change Request Form, including supporting documentation, and documents the review by

signing Attachment A. The review verifies that the following information or documentation is included:

a. Completed 10 CFR 50.59 REVIEW. If the changes are related to an approved NRC SE associated with a site specific Operating License or TS change and determined to be entirely bounded by the NRC SE, then only a copy of the SE is required to be attached and no 10 CFR 50.59 REVIEW is required. A 10 CFR 50.59 REVIEW is not required for an EDITORIAL CHANGE;
b. Identification of known documents requiring revisions; and TRM TRM Control Program Appendix G Quad Cities Units 1 & 2 7 of 15 Revision QC-TRM-05-001 Technical Requirements Manual c. Completed UFSAR Change Request with supporting documentation, in accordance with appropriate plant procedures, if applicable.
9. If the TRM change is not an EDITORIAL CHANGE, the RA LE/TRM Change Requestor obtains SQR approval of the TRM change by performing the following:
a. RA LE prepares the TRM Change SQR package. The SQR package shall include Attachment A (including

completed 10 CFR 50.59 REVIEW or NRC SE) and the revised TRM pages. Attachment A is provided for the purpose of reviewing and finalizing the implementation requirements and ensuring the necessary actions have been initiated. RA LE shall assign Action Tracking (AT) items, as necessary, to track implementation requirements;

b. TRM Change Requestor submits the TRM Change SQR package to the SQR Committee members for a preliminary review. The SQR composition shall include RA and Operating Departments in all cases; and
c. TRM Change Requestor resolves preliminary review comments and finalizes the TRM Change SQR package.
10. The RAM shall determine the need for Plant Operations Review Committee (PORC) approval. The need for PORC approval shall

be documented on Attachment A.

11. RA LE/TRM Change Requestor obtains PORC approval, if necessary.
12. After approval of the TRM changes by SQR/PORC, RA LE ensures that the controlled master electronic files are updated.
13. RA LE completes Attachment C, "Technical Requirements Manual Change Instruction Form," as follows:

TRM TRM Control Program Appendix G Quad Cities Units 1 & 2 8 of 15 Revision QC-TRM-05-001 Technical Requirements Manual a. Indicates the effective date of the TRM changes consistent with the SQR/PORC approval or TS amendment required implementation date. If the TRM change is a result of a TS Amendment, the update shall be implemented consistent with the implementation requirements of the TS Amendment. Otherwise, the update must be implemented by the date indicated on Attachment C;

b. Lists each page to be removed and inserted, including the Affected Page List; and
c. Provides the updated master file directory for updating Electronic Document Management System (EDMS), if applicable.
14. RA LE creates a TRM Change Package. The TRM Change Package shall consist of:
1. TRM Change Instruction Form (Attachment C);
2. Revised Affected Page List; and
3. Revised TRM pages.

One RA LE shall assemble and approve the TRM Change Package for distribution and a second RA LE shall perform a peer

check to verify completeness of the TRM Change Package.

15. After verifying that SQR/PORC approval of the TRM changes has been obtained and that all AT items assigned to track

implementation requirements have been completed, RA LE forwards the TRM Change Package to Station Records Management as notification of the need to update the onsite TRM controlled copies and EDMS, if applicable.

16. RA LE also forwards the TRM Change Package to Cantera Licensing (CL) Records Management as notification of the need to update the offsite (CL) TRM controlled copies and to transmit updates to the offsite (non-CL) TRM controlled copies.

TRM TRM Control Program Appendix G Quad Cities Units 1 & 2 9 of 15 Revision QC-TRM-05-001 Technical Requirements Manual 17. Upon completion of updating the onsite TRM controlled copies and EDMS (if applicable), Station Records Management Supervisor signs and dates Attachment C and returns Attachment C to the RA LE.

18. Upon completion of updating the offsite (CL) TRM controlled copies and transmitting updates to the offsite (non-CL) TRM controlled copies, CL Records Management signs and dates Attachment C and returns Attachment C to the RA LE.
19. RA LE updates the TRM Change Request Log (Attachment B) with the following information:
a. 10 CFR 50.59 REVIEW Number;
b. SQR Number, if applicable;
c. SQR Approval Date; and
d. TRM change implementation date.
20. RA LE ensures that the documentation required to be maintained as a quality record is provided to Station Records Management for the purpose of record retention.

1.6 ACCEPTANCE CRITERIA Not applicable.

1.7 LCOARS/COMPENSATORY MEASURES An Issue Report may need to be generated to provide proper tracking and resolution of noted problems associated with the implementation of this Program.

The RAM will be responsible for ensuring that Program failures have been resolved.

TRM TRM Control Program Appendix G Quad Cities Units 1 & 2 10 of 15 Revision QC-TRM-05-001 Technical Requirements Manual 1.8 REPORTING REQUIREMENTS

          • NOTE TRM changes requiring prior NRC approval shall be submitted in accordance with Reference 5.

TRM changes not requiring prior NRC approval, as described in Section 1.4 of this Program, shall be submitted to the NRC in accordance with 10 CFR 50.71(e).

1.9 CHANGE CONTROL Changes to this Program, other than EDITORIAL CHANGES, shall include a 10 CFR 50.59 REVIEW and a SQR. The SQR composition shall include RA Department in all cases. For a change to this Program, PORC approval from all Stations is required. The concurrence shall be that the other Stations are implementing the same changes or

that the changes have been reviewed and determined not to be applicable to the other Stations.

TRM TRM Control Program Appendix G Quad Cities Units 1 & 2 11 of 15 Revision QC-TRM-05-001 Technical Requirements Manual ATTACHMENT A TECHNICAL REQUIREMENTS MANUAL CHANGE REQUEST FORM

1. Change Request #: _____________ Affected TRM Section(s): _________________________
2. Description of changes: _________________________________________________________

____________________________________________________________________________________

____________________________________________________________________________________

3. Reason for changes (attach all supporting documentation): ____________________

____________________________________________________________________________________

____________________________________________________________________________________

____________________________________________________________________________________

4. Schedule Requirements: Outage Related (check one) No Yes, Outage # ___________ Other (explain) ___________________________________________________________________
5. Implementation Requirements (attach additional pages, as necessary):

Identify the impact of the changes on the following: Affected N/A UFSAR ______________________________________________________________

TS _________________________________________________________________

TS Bases ___________________________________________________________

NRC Safety Evaluation _____________________________________________

Fire Protection Report _____________________________________________

NRC Commitments ____________________________________________________

Vendor Documentation _______________________________________________

Special Permits/Licenses ___________________________________________

Procedures _________________________________________________________

Environmental Qualification ________________________________________

Design Basis Documentation _________________________________________

Engineering Calculations ___________________________________________

Drawings/Prints ____________________________________________________

PRA Information ____________________________________________________

Programs ___________________________________________________________

Reportability Manual _______________________________________________

QA Topical Report __________________________________________________

Passport ___________________________________________________________

Pre-Implementation Training Required _______________________________

Maintenance Rule ___________________________________________________

Offsite Dose Calculation Manual ____________________________________

Other ______________________________________________________________

6. Check one:

10 CFR 50.59 REVIEW Attached, 10 CFR 50.59 REVIEW #:_________________________

NRC SE Attached, Changes consistent with and entirely bounded by NRC SE EDITORIAL CHANGE, No 10 CFR 50.59 REVIEW required

7. Requestor: ______________________/______________________/________________________ (Signature) (Date) (Department)
8. Requesting Supervisor Approval: _______________________/________________________ (Signature) (Date)
9. PORC Approval Required: Yes No
10. Licensing Engineer Review: _______________________/________________________

(Signature) (Date)

TRM TRM Control Program Appendix G Quad Cities Units 1 & 2 12 of 15 Revision QC-TRM-05-001 Technical Requirements Manual ATTACHMENT B TECHNICAL REQUIREMENTS MANUAL CHANGE REQUEST LOG CR # Brief Description of Changes Affected Section(s) 10 CFR 50.59 REVIEW # SQR # SQR Approval Date Implemented Date TRM TRM Control Program Appendix G Quad Cities Units 1 & 2 13 of 15 Revision QC-TRM-05-001 Technical Requirements Manual ATTACHMENT C TECHNICAL REQUIREMENTS MANUAL CHANGE INSTRUCTION FORM FOR ONSITE/OFFSITE DISTRIBUTION AND FOR UPDATING EDMS

Braidwood/Byron/Dresden/LaSalle/QC (circle one) TRM Revision # ______

NOTE: This change is effective as of _____________________________ and shall be implemented by __________ . (SQR/PORC or Amendment Implementation Date) (Date)

Approved for distribution: ___________________________________/_____________ (RA LE Signature) (Date)

Verified: ___________________________________/_____________ (RA LE Signature) (Date)

REMOVE Section REMOVE Page INSERT Section INSERT Page UPDATE EDMS Section UPDATE EDMS Page Affected

Page List All Affected Page List All N/A N/A

TRM TRM Control Program Appendix G Quad Cities Units 1 & 2 14 of 15 Revision QC-TRM-05-001 Technical Requirements Manual ATTACHMENT C TECHNICAL REQUIREMENTS MANUAL CHANGE INSTRUCTION FORM FOR ONSITE/OFFSITE DISTRIBUTION AND FOR UPDATING EDMS

Braidwood/Byron/Dresden/LaSalle/QC (circle one) TRM Revision # ______

___________________________________________________________________________________________

Station Records Management:

Onsite Distribution Completed: ______________________________/___________________

(Station Records Mgmt. Supr.) (Date)

EDMS Update Completed: ______________________________/___________________ (Station Records Mgmt. Supr.) (Date)

    • Return this sheet to: Regulatory Assurance Braidwood/Byron/Dresden/LaSalle/QC (circle one) Station

___________________________________________________________________________________________

CL Records Management:

Offsite (CL) Distribution Completed: ___________________________/____________________ (CL Records Mgmt.) (Date)

Offsite (non-CL) Distribution Transmitted: ___________________________/____________________ (CL Records Mgmt.) (Date)

    • Return this sheet to: Regulatory Assurance Braidwood/Byron/Dresden/LaSalle/QC (circle one) Station

___________________________________________________________________________________________

Offsite (non-CL) Controlled Copy Holders:

Offsite (non-CL) Distribution Completed: ___________________________/____________________ (Signature) (Date)

    • Return this sheet to: EXELON GENERATION COMPANY, LLC LICENSING AND REGULATORY AFFAIRS DEPARTMENT 4300 WINFIELD ROAD WARRENVILLE, IL 60555

TRM TRM Control Program Appendix G Quad Cities Units 1 & 2 15 of 15 Revision QC-TRM-05-001 Technical Requirements Manual ATTACHMENT D TECHNICAL REQUIREMENTS MANUAL CHANGE APPLICABILITY REVIEW FORM Any change to a Station's Technical Requirements Manual (TRM) shall be transmitted to the

Regulatory Assurance Managers (RAMs) at each of the other Stations. The RAM will review the TRM change for applicability at their respective Station. Review of applicability shall be documented on this Attachment and forwarded to the Regulatory Assurance Licensing Engineer(s)

at the Station(s) making the change.

Braidwood/Byron/Dresden/LaSalle/QC (circle one)

TRM Section(s)/Title(s): __________________________________________________________________

Description of the change: _________________________________________________________________

_____________________________________________________________________________________________

_____________________________________________________________________________________________

_____________________________________________________________________________________________

Braidwood RAM Review: ________________________/_______________ (Signature) (Date)

Change Applicable: Yes No Byron RAM Review: ________________________/_______________ (Signature) (Date)

Change Applicable: Yes No Dresden RAM Review: ________________________/_______________

(Signature) (Date)

Change Applicable: Yes No LaSalle RAM Review: ________________________/_______________ (Signature) (Date)

Change Applicable: Yes No QC RAM Review: ________________________/_______________ (Signature) (Date)

Change Applicable: Yes No

    • Return this sheet to: Regulatory Assurance Braidwood/Byron/Dresden/LaSalle/QC (circle one) Station

TRM Appendix H Response Times Quad Cities 1 and 2 H-1 Revision QC-TRM-05-004 Table H-1 (page 1 of 1) Response Times FUNCTION RESPONSE TIME 1 Turbine Bypass Valve Bypass Valves: (analysis assumes one Bypass Valve out of service) Delay to first opening (msec after TSV full closure) 50 msec 5% of entire bank* (msec after TSV full closure) 100 msec 80% of entire bank*

(msec after TSV full closure) 240 msec 100% of entire bank*

(msec after TSV full closure) 450 msec

  • entire bank defined as 8 valves open.

2 Reactor Protection System Response Time

< 50 msec (a) (a) Neutron detectors are exempt from response time testing. As measured from the opening of the sensor contact up to and including the opening of the trip actuator.

TRM TLCO Applicability B 3.0 Quad Cities 1 and 2 B 3.0-1 Revision 0

B 3.0 TECHNICAL REQUIREMENTS MANUAL LIMITING CONDITION FOR OPERATION (TLCO) APPLICABILITY

BASES TLCOs TLCO 3.0.a through TLCO 3.0.f establish the general requirements applicable to all TLCOs in Sections 2.1 and 3.1 through 3.9 and apply at all times, unless otherwise stated.

TLCO 3.0.a

TLCO 3.0.a establishes the Applicability statement within each individual TLCO as the requirement for when the TLCO is required to be met (i.e.,

when the unit is in the MODES or other specified conditions of the Applicability statement of each Requirement).

TLCO 3.0.b

TLCO 3.0.b establishes that upon discovery of a failure to meet a TLCO, the associated ACTIONS shall be met. The Completion Time of each Required Action for an ACTIONS Condition is applicable from the point in time that an ACTIONS Condition is entered. The Required Actions establish those remedial measures that must be taken within specified Completion Times when the requirements of a TLCO are not met. This Requirement establishes that:

a. Completion of the Required Actions within the specified Completion Times constitutes compliance with a TLCO; and
b. Completion of the Required Actions is not required when a TLCO is met within the specified Completion Time, unless otherwise specified.

There are two basic types of Required Actions. The first type of Required Action specifies a time limit in which the TLCO must be met. This time limit is the Completion Time to restore an inoperable system or component to OPERABLE status or to restore variables to within specified limits. If this type of Required Action is not completed within the specified Completion Time, a shutdown may be required to place the unit in a MODE or condition in which the TLCO is not applicable. (Whether stated as a Required Action or not, correction of the entered Condition is an action that may always be considered upon entering ACTIONS.) The second type of

(continued)

TRM TLCO Applicability B 3.0 Quad Cities 1 and 2 B 3.0-2 Revision 0 BASES (continued)

TLCO 3.0.b (continued)

Required Action specifies the remedial measures that permit continued operation of the unit that is not further restricted by the Completion Time. In this case, compliance with the Required Actions provides an acceptable level of safety for continued operation.

Completing the Required Actions is not required when a TLCO is met or is no longer applicable, unless otherwise stated in the individual TLCOs.

The nature of some Required Actions of some Conditions necessitates that, once the Condition is entered, the Required Actions must be completed even though the associated Condition no longer exists. The individual TLCO's ACTIONS specify the Required Actions where this is the case. An example of this is in TLCO 3.7.i, "Snubbers."

The Completion Times of the Required Actions are also applicable when a system or component is removed from service intentionally. The reasons for intentionally relying on the ACTIONS include, but are not limited to, performance of Surveillances, preventive maintenance, corrective maintenance, or investigation of operational problems. Entering ACTIONS for these reasons must be done in a manner that does not compromise safety. Intentional entry into ACTIONS should not be made for operational convenience. Additionally, if intentional entry into ACTIONS would result in redundant equipment being inoperable, alternatives should be used instead. Doing so limits the time both subsystems/divisions of a safety function are inoperable and limits the time conditions exist which may result in TLCO 3.0.c being entered. Individual TLCOs may specify a time limit for performing a TSR when equipment is removed from service or bypassed for testing. In this case, the Completion Times of the Required Actions are applicable when this time limit expires, if the equipment remains removed from service or bypassed.

When a change in MODE or other specified condition is required to comply with Required Actions, the unit may enter a MODE or other specified condition in which another TLCO becomes applicable. In this case, the Completion Times of the associated Required Actions would apply from the point in time that the new TLCO becomes applicable and the ACTIONS Condition(s) are entered.

(continued)

TRM TLCO Applicability B 3.0 Quad Cities 1 and 2 B 3.0-3 Revision 0

BASES (continued)

TLCO 3.0.c

TLCO 3.0.c establishes the actions that must be implemented when a TLCO is not met and:

a. An associated Required Action and Completion Time is not met and no other Condition applies; or
b. The condition of the unit is not specifically addressed by the associated ACTIONS. This means that no combination of Conditions stated in the ACTIONS can be made that exactly corresponds to the actual condition of the unit. Sometimes, possible combinations of Conditions are such that entering TLCO 3.0.c is warranted; in such cases, the ACTIONS specifically state a Condition corresponding to such combinations and also that TLCO 3.0.c be entered immediately.

Upon entering TLCO 3.0.c, 1 hour1.157407e-5 days <br />2.777778e-4 hours <br />1.653439e-6 weeks <br />3.805e-7 months <br /> is allowed to implement appropriate compensatory actions and verify the plant is not in an unanalyzed condition or that a required safety function is not compromised. Within 12 hours1.388889e-4 days <br />0.00333 hours <br />1.984127e-5 weeks <br />4.566e-6 months <br />, Shift Operations Superintendent or designee approval of the compensatory actions and the plan for exiting TLCO 3.0.c must be obtained. The use and interpretation of specified times to complete the actions of TLCO 3.0.c are consistent with the discussion of Section 1.3, Completion Times.

The actions required in accordance with TLCO 3.0.c may be terminated and TLCO 3.0.c exited if any of the following occurs:

a. The TLCO is now met.
b. A Condition exists for which the Required Actions have now been performed.
c. ACTIONS exist that do not have expired Completion Times. These Completion Times are applicable from the point in time that the Condition is initially entered and not from the time TLCO 3.0.c is

exited. (continued)

TRM TLCO Applicability B 3.0 Quad Cities 1 and 2 B 3.0-4 Revision QC-TRM-05-003

BASES (continued)

TLCO 3.0.c (continued)

In MODES 1, 2, and 3, TLCO 3.0.c provides actions for Conditions not covered in other Requirements. The requirements of TLCO 3.0.c do not apply in MODES 4 and 5 because the unit is already in the most restrictive Condition. The requirements of TLCO 3.0.c do not apply in other specified conditions of the Applicability (unless in MODE 1, 2, or 3) because the ACTIONS of individual TLCOs sufficiently define the remedial measures to be taken.

TLCO 3.0.d

TLCO 3.0.d establishes limitations on changes in MODES or other specified conditions in the Applicability when an TLCO is not met. It allows placing the unit in a MODE or other specified condition stated in that Applicability (e.g., the Applicability desired to be entered) when unit conditions are such that the requirements of the TLCO would not be met, in accordance with TLCO 3.0.d.1, TLCO 3.0.d.2, or TLCO 3.0.d.3.

TLCO 3.0.d.1 allows entry into a MODE or other specified condition in the Applicability with the TLCO not met 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. Compliance with Required Actions that permit continued operation of the unit for an unlimited period of time in a MODE or other specified condition provides an acceptable level of safety for continued operation. This is without regard to the status of the unit before or after the MODE change. Therefore, in such cases, entry into a MODE or other specified condition in the Applicability may be made in accordance with the provisions of the Required Actions.

TLCO 3.0.d.2 allows entry into a MODE or other specified condition in the Applicability with the TLCO not met 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.

The risk assessment may use quantitative, qualitative, or blended approaches, and the risk assessment will be conducted using the plant program, procedures, and criteria in place to implement 10 CFR 50.65(a)(4), which requires that risk impacts of maintenance activities be assessed and managed. The risk assessment, for the purposes of TLCO 3.0.d.2, must take into account all inoperable TRM equipment regardless of whether the equipment is included in the normal 10 CFR 50.65(a)(4) risk assessment scope.

(continued)

TRM TLCO Applicability B 3.0 Quad Cities 1 and 2 B 3.0-5 Revision QC-TRM-05-003 BASES (continued)

TLCO 3.0.d (continued)

The risk assessments will be conducted using the procedures and guidance endorsed by Regulatory Guide 1.182, "Assessing and Managing Risk Before Maintenance Activities at Nuclear Power Plants." Regulatory Guide 1 .182 endorses the guidance in Section 11 of NUMARC 93-01, "Industry Guideline for Monitoring the Effectiveness of Maintenance at Nuclear Power Plants ." These documents address general guidance for conduct of the risk assessment, quantitative and qualitative guidelines for establishing risk management actions, and example risk management actions. These include actions to plan and conduct other activities in a manner that controls overall risk, increased risk awareness by shift and management personnel, actions to reduce the duration of the condition, actions to minimize the magnitude of risk increases (establishment of backup success paths or compensatory measures), and determination that the proposed MODE change is acceptable. Consideration should also be given to the probability of completing restoration such that the requirements of the TLCO would be met prior to the expiration of ACTIONS Completion Times that would require exiting the Applicability.

TLCO 3.0.d.2 may be used with single, or multiple systems and components unavailable. NUMARC 93-01 provides guidance relative to consideration of simultaneous unavailability of multiple systems and components.

The results of the risk assessment shall be considered in determining the acceptability of entering the MODE or other specified condition in the Applicability, and any corresponding risk management actions. The TLCO 3.0.d.2 risk assessments do not have to be documented.

The TRM allows continued operation with equipment unavailable in MODE 1 for the duration of the Completion Time. Since this is allowable, and since in general the risk impact in that particular MODE bounds the risk of transitioning into and through the applicable MODES or other specified conditions in the Applicability of the TLCO, the use of the TLCO 3.0.d.2 allowance should be generally acceptable, as long as the risk is assessed and managed as stated above.

The provisions of this TLCO should not be interpreted as endorsing the failure to exercise the good practice of restoring systems or components to OPERABLE status before entering an associated MODE or other specified condition in the Applicability.

The provisions of TLCO 3.0.d shall not prevent changes in MODES or other specified conditions in the Applicability that are required to comply with ACTIONS. In addition, the provisions of TLCO 3.0.d shall not prevent changes in MODES or other specified conditions in the Applicability that result from any unit shutdown. In this context, a unit shutdown is (continued)

TRM TLCO Applicability B 3.0 Quad Cities 1 and 2 B 3.0-6 Revision QC-TRM-05-003 BASES (continued)

TLCO 3.0.d (continued)

defined as a change in MODE or other specified condition in the Applicability associated with transitioning from MODE 1 to MODE 2, MODE 2 to MODE 3, and MODE 3 to MODE 4.

Upon entry into a MODE or other specified condition in the Applicability with the TLCO not met, TLCO 3.0.a and TLCO 3.0.b require entry into the applicable Conditions and Required Actions until the Condition is resolved, until the TLCO is met, or until the unit is not within the Applicability of the TLCO. TSRs do not have to be performed on the associated inoperable equipment (or on variables outside the specified limits), as permitted by TSR 3.0.a. Therefore, utilizing TLCO 3.0.d is not a violation of TSR 3.0.a or TSR 3.0.d for any TSRs that have not been performed on inoperable equipment. However, TSRs must be met to ensure OPERABILITY prior to declaring the associated equipment OPERABLE (or variable within limits) and restoring compliance with the affected TLCO.

TLCO 3.0.e establishes the allowance for restoring equipment to service under administrative controls when it has been removed from service or declared inoperable to comply with ACTIONS. The sole purpose of this Requirement is to provide an exception to TLCO 3.0.b (e.g., to not comply with the applicable Required Action(s)) to allow the performance of required testing to demonstrate:

a. The OPERABILITY of the equipment being returned to service; or

TLCO 3.0.e

b. The OPERABILITY of other equipment.

The administrative controls ensure the time the equipment is returned to service in conflict with the requirements of the ACTIONS is limited to the time absolutely necessary to perform the required testing to demonstrate OPERABILITY. This Requirement does not provide time to perform any

other preventive or corrective maintenance.

An example of demonstrating the OPERABILITY of other equipment is taking an inoperable channel or trip system out of the tripped condition to prevent the trip function from occurring during the performance of required testing on another channel in the other trip system. A similar example of demonstrating the OPERABILITY of other equipment is taking an inoperable channel or trip system out of the tripped condition to permit the logic to function and indicate the appropriate response during the performance of required testing on another channel in the same trip system.

TRM TLCO Applicability B 3.0 Quad Cities 1 and 2 B 3.0-7 Revision QC-TRM-05-003 BASES (continued)

TLCO 3.0.f

TLCO 3.0.f establishes the applicability of each TLCO to both Unit 1 and Unit 2 operation. Whenever a requir ement applies to only one unit, or is different for each unit, this will be identified in the appropriate section of the TLCO (e.g., Applicability, TSR, etc.) with parenthetical reference, Notes, or other appropriate presentation within the body of the requirement.

TRM TSR Applicability B 3.0 Quad Cities 1 and 2 B 3.0-8 QC-TRM-05-003

B 3.0 TECHNICAL REQUIREMENTS MANUAL SURVEILLANCE REQUIREMENT (TSR) APPLICABILITY

BASES TSRs TSR 3.0.a through TSR 3.0.e establish the general requirements applicable to all Requirements in Sections 2.1 and 3.1 through 3.9 and apply at all times, unless otherwise stated.

TSR 3.0.a

TSR 3.0.a establishes the requirement that TSRs must be met during the MODES or other specified conditions in the Applicability for which the requirements of the TLCO apply, unless otherwise specified in the individual TSRs. This TLCO is to ensure that TSRs are performed to verify

the OPERABILITY of systems and components, and that variables are within specified limits. Failure to meet a TSR within the specified Frequency, in accordance with TSR 3.0.b, constitutes a failure to meet a

TLCO. Systems and components are assumed to be OPERABLE when the associated TSRs have been met. Nothing in this TSR, however, is to be construed as implying that systems or components are OPERABLE when:

a. The systems or components are known to be inoperable, although still meeting the TSRs; or
b. The requirements of the TSR(s) are known to be not met between required TSR performances.

TSR do not have to be performed when the unit is in a MODE or other specified condition for which the requirements of the associated TLCO are not applicable, unless otherwise specified.

Unplanned events may satisfy the requirements (including applicable acceptance criteria) for a given TSR. In this case, the unplanned event may be credited as fulfilling the performance of the TSR.

(continued)

TRM TSR Applicability B 3.0 Quad Cities 1 and 2 B 3.0-9 QC-TRM-05-003

BASES (continued)

TSR 3.0.a (continued)

TSRs, including TSRs invoked by Required Actions, do not have to be performed on inoperable equipment because the ACTIONS define the remedial measures that apply. TSRs have to be met and performed in accordance with TSR 3.0.b, 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 TSRs are not failed and their most recent performance is in accordance with TSR 3.0.b. 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.

TSR 3.0.b

TSR 3.0.b establishes the requirements for meeting the specified Frequency for TSRs and any Required Action with a Completion Time that requires the periodic performance of the Required Action on a "once per..."

interval.

TSR 3.0.b permits a 25% extension of the interval specified in the Frequency. This extension facilitates TSR scheduling and considers plant operating conditions that may not be suitable for conducting the TSR (e.g.,

transient conditions or other ongoing TSR or maintenance activities).

The 25% extension does not significantly degrade the reliability that results from performing the TSR at its specified Frequency. This is based on the recognition that the most probable result of any particular TSR being performed is the verification of conformance with the TSRs.

As stated in TSR 3.0.b, the 25% extension also does not apply to the initial portion of a periodic Completion Time that requires performance on a "once per..." basis. The 25% extension applies to each performance after the initial performance. The initial performance of the Required

(continued)

TRM TSR Applicability B 3.0 Quad Cities 1 and 2 B 3.0-10 Revision QC-TRM-05-003

BASES (continued)

TSR 3.0.b (continued)

Action, whether it is a particular TSR or some other remedial action, is considered a single action with a single Completion Time. One reason for not allowing the 25% extension to this Completion Time is that such an action usually verifies that no loss of function has occurred by checking the status of redundant or diverse components or accomplishes the function of the inoperable equipment in an alternative manner.

The provisions of TSR 3.0.b are not intended to be used repeatedly merely as an operational convenience to extend TSR intervals (other than those consistent with refueling intervals) or periodic Completion Time intervals beyond those specified.

TSR 3.0.c

TSR 3.0.c establishes the flexibility to defer declaring affected equipment inoperable or an affected variable outside the specified limits when a TSR has not been completed within the specified Frequency. 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 Frequency, whichever is greater, applies from the point in time it is discovered that the TSR has not been performed in accordance with TSR 3.0.b, and not at the time that the specified Frequency was not met. This delay period provides adequate time to complete TSRs that have been missed. This delay period permits the completion of a TSR before complying with Required Actions or other remedial measures that might preclude completion of the TSR.

The basis for this delay period includes consideration of unit conditions, adequate planning, availability of personnel, the time required to perform the TSR, the safety significance of the delay in completing the required TSR, and the recognition that the most probable result of any particular TSR being performed is the verification of conformance with the requirements.

When a TSR with a Frequency based not on time intervals, but upon specified unit conditions, operating situations, or requirements of regulations (e.g., prior to start of movement of fuel assemblies or control rods, or in accordance with the Diesel Fuel Oil Testing Program, etc.) is discovered to not have been performed when specified, TSR 3.0.c allows for (continued)

TRM TSR Applicability B 3.0 Quad Cities 1 and 2 B 3.0-11 Revision QC-TRM-05-003

BASES (continued)

TSR 3.0.c (continued) the full delay period of up to the specified Frequency to perform the TSR. However, since there is not a time interval specified, the missed TSR should be performed at the first reasonable opportunity.

TSR 3.0.c provides a time limit for, and allowances for the performance of, TSRs that become applicable as a consequence of MODE changes imposed by Required Actions.

Failure to comply with specified Frequencies for TSRs is expected to be an infrequent occurrence. Use of the delay period established by TSR 3.0.c is a flexibility which is not intended to be used as an operational convenience to extend TSR 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 Frequency is provided to perform the missed TSR, it is expected that the missed TSR 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 TSR as well as any plant configuration changes required or shutting the plant down to perform the TSR) and impact on any analysis assumptions, in addition to unit conditions, planning, availability of personnel, and the time required to perform the TSR. 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 TSR 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 TSRs 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 TSRs will be placed in the station's Corrective Action Program.

(continued)

TRM TSR Applicability B 3.0 Quad Cities 1 and 2 B 3.0-12 Revision QC-TRM-05-003

BASES (continued)

TSR 3.0.c (continued)

If a TSR is not completed within the allowed delay period, then the equipment is considered inoperable or the variable then is considered outside the specified limits and the Completion Times of the Required Actions for the applicable TLCO Conditions begin immediately upon expiration of the delay period. If a TSR is failed within the delay period, then the equipment is inoperable, or the variable is outside the specified limits and the Completion Times of the Required Actions for the applicable TLCO Conditions begin immediately upon the failure of the TSR.

Completion of the TSR within the delay period allowed by this TSR, or within the Completion Time of the ACTIONS, restores compliance with TSR 3.0.a.

TSR 3.0.d TSR 3.0.d establishes the requirement that all applicable TSRs must be met before entry into a MODE or other specified condition in the Applicability.

This TSR ensures that system and component OPERABILITY requirements and variable limits are met before entry into MODES or other specified conditions in the Applicability for which these systems and components ensure safe operation of the unit. The provisions of this TSR should not be interpreted as endorsing the failure to exercise the good practice of restoring systems or components to OPERABLE status before entering an associated MODE or other specified condition in the Applicability. A provision is included to allow entry into a MODE or other specified condition in the Applicability when an TLCO is not met due to a TSR not being met in accordance with TLCO 3.0.d. However, in certain circumstances, failing to meet an TSR will not result in TSR 3.0.d restricting a MODE change or other specified condition change. When a system, subsystem, division, component, device, or variable is inoperable or outside its specified limits, the associated TSR(s) are not required to be performed, per TSR 3.0.a, which states that TSRs do not have to be performed on inoperable equipment. When equipment is inoperable, TSR 3.0.d does not apply to the associated TSR(s) since the requirement for the TSR(s) to be performed is removed. Therefore, failing to perform the TSR(s) within the specified Frequency does not result in an TSR 3.0.d restriction to changing MODES or other specified conditions of the Applicability.

(continued)

TRM TSR Applicability B 3.0 Quad Cities 1 and 2 B 3.0-13 Revision QC-TRM-05-003

BASES (continued)

TSR 3.0.d (continued)

However, since the TLCO is not met in this instance, TLCO 3.0.d will govern any restrictions that may (or may not) apply to MODE or other specified condition changes. TSR 3.0.d does not restrict changing MODES or other specified conditions of the Applicability when a TSR has not been performed within the specified Frequency, provided the requirement to declare the TLCO not met has been delayed in accordance with TSR 3.0.c.

The provisions of TSR 3.0.d shall not prevent entry into MODES or other specified conditions in the Applicability that are required to comply with ACTIONS. In addition, the provisions of TSR 3.0.d shall not prevent changes in MODES or other specified conditions in the Applicability that result from any unit shutdown. In this context, a unit shutdown is defined as a change in MODE or other specified condition in the Applicability associated with transitioning from MODE 1 to MODE 2, MODE 2 to MODE 3, and MODE 3 to MODE 4. The precise requirements for performance of TSRs are specified such that exceptions to TSR 3.0.d are not necessary. The specific time frames and conditions necessary for meeting the TSRs are specified in the Frequency, in the TSR, or both. This allows performance of TSRs when the prerequisite condition(s) specified in a surveillance procedure require entry into the MODE or other specified condition in the Applicability of the associated TLCO prior to the performance or completion of a TSR. A TSR that could not be performed until after entering the TLCO's Applicability, would have its Frequency specified such that it is not "due" until the specific conditions needed are met. Alternately, the TSR may be stated in the form of a Note, as not required (to be met or performed) until a particular event, condition, or time has been reached. Further discussion of the specific formats of TSRs' annotation is found in TRM Section 1.4, Frequency.

TSR 3.0.e

TSR 3.0.e establishes the applicability of each TSR to both Unit 1 and Unit 2 operation. Whenever a requirement applies to only one unit, or is different for each unit, this will be identified with parenthetical reference, Notes, or other appropriate presentation within the TSR.

This Section Intentionally Blank

Technical Requirements Manual Section B 3.1 Not Used

Quad Cities 1 and 2 B 3.3.b-1 Revision QC-TRM-05-008 TRM PAM Instrumentation B 3.3.b B 3.3 INSTRUMENTATION

B 3.3.b Post Accident Monitoring (PAM) Instrumentation

BASES

Instrumentation is provided to monitor sufficient accident conditions to adequately assess important variables and provide the operators with the necessary information to complete the appropriate mitigation actions. OPERABILITY of the instrumentation listed provides adequate monitoring of the containment following a loss-of-coolant accident. Information from this instrumentation will provide the operator with a detailed knowledge of the conditions resulting from the accident; based on this information, the operator can make logical decisions regarding post accident recovery. Allowable outage times are based on diverse instrumentation availability for guiding the operator should an accident occur, and on the low probability of an instrument being out-of-service concurrent with an accident.

In Reference 1 Exelon submitted a License Amendment Request (LAR) removing the Drywell H 2/O 2 Post Accident Monitoring (PAM) instruments from the Technical Specifications. The NRC approved this request in Reference 2. The LAR contained a regulatory commitment (AT 346390-04) to maintain the capability of the drywell H 2 and O 2 concentration analyzers. The surveillance requirements provided in TRM section 3.3.b for Functions 5 and 6 are required to satisfy this regulatory commitment.

REFERENCES:

1. Letter from K. R. Jury (Exelon) to U. S. NRC, "Request for Amendment to Technical Specifications to Eliminate Requirements for Hydrogen Recombiners and Hydrogen/Oxygen Monitors Using the Consolidated Line Item Improvement Process,"

dated September 15, 2004. 2. Letter from G. F. Dick (USNRC) to C. M. Crane, "Quad Cities Nuclear Power Station, Units 1 and 2 - Issuance of Amendments," dated June 14, 2005.

Quad Cities 1 and 2 B 3.3.c-1 Revision 0 TRM Explosive Gas Monitoring Instrumentation B 3.3.c B 3.3 INSTRUMENTATION

B 3.3.c Explosive Gas Monitoring Instrumentation

BASES

This instrumentation provides for monitoring the concentrations of potentially explosive gas mixtures in the Offgas Holdup System.

Quad Cities 1 and 2 B 3.3.d-1 Revision 0 TRM Suppression Chamber and Drywell Spray Actuation Instrumentation B 3.3.d

B 3.3 INSTRUMENTATION

B 3.3.d Suppression Chamber and Drywell Spray Actuation Instrumentation

BASES Instrumentation is provided to monitor the parameters which are necessary to permit initiation of the suppression chamber and drywell spray mode of the low pressure coolant injection/containment cooling system to condense steam in the containment atmosphere. The spray mode does not significantly affect the rise of drywell pressure following a loss of coolant accident, but does result in quicker depressurization following completion of the blowdown.

Quad Cities 1 and 2 B 3.3.e-1 Revision QC-TRM-03-001 TRM Toxic Gas Monitoring System B 3.3.e B 3.3 INSTRUMENTATION

B 3.3.e Toxic Gas Monitoring System

BASES

Toxic gas monitoring instrumentation is provided in or near the Control Room Emergency Ventilation System intakes to allow prompt detection and the necessary protective actions to be initiated. Isolation from high toxic chemical concentration has been added to the station design as a result of the "Control Room Habitability Study" submitted to the NRC in December 1981 in response to NUREG-0737 Item III D.3.4. As explained in Section 3 of this study, ammonia, chlorine, and sulfur dioxide detection capability has been provided. In a report generated by Sargent and Lundy in April 1991, justification was provided to delete the chlorine and sulfur dioxide detectors from the plant. The setpoints chosen for the control room ventilation isolation are based on early detection in the outside air supply at the odor threshold, so that the toxic chemical will not achieve toxicity limit concentrations in the Control Room. To maximize system reliability, a limit of 30 days is provided for operation with a single sensor channel inoperable.

Quad Cities 1 and 2 B 3.3.f-1 Revision 0 TRM RWCU Area Temperature Monitoring B 3.3.f B 3.3 INSTRUMENTATION

B 3.3.f Reactor Water Cleanup (RWCU) Area Temperature Monitoring

BASES ComEd engineering has recently evaluated the effects of a RWCU system break outside of the containment with a break small enough such that the feedwater system can maintain reactor water level above +8 inches. This analysis was necessary since Monticello reported that below 87 % power, more mass would be discharged to their secondary containment than in the main steam line break outside the containment; previously thought to be the most limiting break. Results of the evaluation show that more mass would be discharged to the secondary containment boundary during the postulated break and the reactor building blowout panels will blow, however, the equipment needed for safe shutdown can perform their function and dose to the public will remain below 10 CFR 100 limits. Crucial to mitigating this scenario is that prompt action is taken when the RWCU Area Temperature annunciators are in the alarm state. This TRM section provides greater control of the RWCU Temperature Area Monitors so that a high level of operability is maintained to support the prompt action required by the operators.

A modification has been installed which results in a RWCU System Isolation when high area temperature is detected. This system monitors 5 areas around the RWCU System Piping and also receives input from the Main St eam Tunnel area temperature monitors.

Quad Cities 1 and 2 B 3.4.a-1 Revision QC-TRM-08-005 TRM Structural Integrity B 3.4.a B 3.4 REACTOR COOLANT SYSTEM

[TRM Section B 3.4.a was deleted under TRM change QC-TRM-08-005.]

Quad Cities 1 and 2 B 3.4.b-1 Revision QC-TRM-01-005 TRM RCS Chemistry B 3.4.b B 3.4 REACTOR COOLANT SYSTEM

B 3.4.b Reactor Coolant System (RCS) Chemistry

BASES

The water chemistry limits of the reactor coolant system are established to prevent damage to the reactor materials in contact with the coolant. Chloride limits are specified to prevent stress corrosion cracking of the stainless steel. The effect of chloride is not as great when the oxygen concentration in the coolant is low, thus the higher limit on chlorides is permitted during MODE 1.

Conductivity measurements are required on a continuous basis since changes in this parameter are an indication of abnormal conditions. Without significant damage to stress corrosion cracking of rector materials in contact with reactor coolant, during a Noble Metal Chemical Application (NMCA), the higher conductivity limits are permitted for a maximum of 48 hours5.555556e-4 days <br />0.0133 hours <br />7.936508e-5 weeks <br />1.8264e-5 months <br /> for the injection of noble metal chemicals in MODE 3 and for a maximum of 24 hours2.777778e-4 days <br />0.00667 hours <br />3.968254e-5 weeks <br />9.132e-6 months <br /> after the end of the injection with the plant being in MODE 4 as rapidly as the cooldown rate limits permit after the end of the injection.

When the conductivity is within limits, chlorides and other impurities affecting conductivity must also be within their acceptable limits. With the conductivity meter inoperable, additional samples must be analyzed to ensure that the chlorides are not exceeding the limits.

The surveillance requirements provide adequate assurance that concentrations in excess of the limits will be detected in sufficient time to take corrective action.

Quad Cities 1 and 2 B 3.6.a-1 Revision 0 TRM RHR Drywell Spray B 3.6.a B 3.6 CONTAINMENT SYSTEMS

B 3.6.a Residual Heat Removal (RHR) Drywell Spray

BASES

Each of the two RHR drywell spray subsystems contain one OPERABLE RHR pump and an OPERABLE flow path capable of recirculating water from the RHR suppression pool through a heat exchanger and the RHR drywell spray nozzles.

Periodic operation of the RHR drywell sprays ma y be used following a Design Basis Accident to assist the natural convection and diffusion mixing of hydrogen and oxygen when other ECCS requirements are met and oxygen concentration exceeds 4%. Since the spray system is a function of the LPCI/containment cooling system, the loops will not be aligned for the spray function during normal operation, but all components required to operate for proper alignment must be OPERABLE.

Quad Cities 1 and 2 B 3.7.a-1 Revision QC-TRM-06-002 TRM RHRSW System-Shutdown B 3.7.a B 3.7 PLANT SYSTEMS

B 3.7.a Residual Heat Removal Service Water (RHRSW) System-Shutdown

BASES

The RHRSW system consists of two RHRSW s ubsystems with 2 RHRSW pumps, a heat exchanger and a flow path capable of taking suction from the Ultimate Heat Sink. An operable RHRSW subsystem shall consist of one OPERABLE RHRSW pump for each required OPERABLE RHR pump and an OPERABLE flow path capable of taking suction from the Ultimate Heat Sink and transferring water through one RHR heat exchanger.

In MODES 4 and 5, the OPERABILITY requirements of the RHRSW System are determined by the systems it supports. Thus, the LCOs of the RHR Shutdown Cooling System (LCO 3.4.8, "Residual Heat Removal (RHR) Shutdown Cooling System-Cold Shutdown," LCO 3.9.8, "Residual Heat Removal (RHR)-High Water Level," and LCO 3.9.9, "Residual Heat Removal (RHR)-Low Water Level"), which require portions of the RHRSW System to be OPERABLE, will govern RHRSW System operation in MODES 4 and 5.

The Train B CREV refrigeration condensing unit, norm ally served by the Service Water System, can be provided with cooling water from either the Unit 1 or 2 Residual Heat Removal Service

Water (RHRSW) System.

The RHRSW System, with the Ultimate Heat Sink, provides sufficient cooling capacity for continued operation of the Residual Heat Removal System and of other safety-related equipment (e.g., RHRSW vault coolers, the Control Room Emergency Ventilation System refrigeration units), during normal and accident conditions. The redundant cooling capacity of the system, assuming a single failure, is consistent with the assumptions used in the safety analysis to keep the accident conditions within acceptable limits. OPERABILITY of this system is also dependent upon special measures for protection from flooding in the condenser pit area.

Movement of a Spent Fuel Cask containing Spent Nuclear Fuel in a sealed Multi-Purpose Canister (MPC) and using a single failure-proof crane is not considered to be "movement of irradiated fuel assemblies in secondary containment." For more information, see references UFSAR, Section 9.1.4.3.2 and NRC Safety Evaluation Report associated with the Holtec International HI-STORM 100 Storage System (Docket Number 72-1014, Certificate Number 1014, Amendment 2).

Quad Cities 1 and 2 B 3.7.b-1 Revision 0 TRM DGCW-Shutdown B 3.7.b B 3.7 PLANT SYSTEMS

B 3.7.b Diesel Generator Cooling Water (DGCW) System-Shutdown

BASES

The Diesel Generator Cooling Water System, with the Ultimate Heat Sink, provides sufficient cooling capacity for continued operation of the diesel generators during normal and accident conditions. The cooling capacity of the system is consistent with the assumptions used in the safety analysis to keep the accident conditions within acceptable limits. OPERABILITY of this system is also dependent upon special measures for protection from flooding in the condenser pit area.

The diesel generator cooling water subsystem also provides cooling water to the Emergency Core Cooling System (ECCS) room emergency coolers. During normal lineup, the diesel generator cooling water subsystems are aligned such that the Unit 1 and Unit 2 subsystems provide cooling to the Unit 1 and Unit 2 ECCS emergency room coolers (respectively). Should one of the Unit diesel generator cooling water subsystems become inoperable, the common diesel generator (i.e., 1/2 diesel generator) cooling water subsystem can be aligned to either Unit's ECCS room emergency coolers. To meet the requirements of the TLCO, the DGCW pump must be capable of being aligned to supply cooling to the ECCS room emergency

coolers.

Quad Cities 1 and 2 B 3.7.c-1 Revision QC-TRM-06-002 TRM UHS-Shutdown B 3.7.c B 3.7 PLANT SYSTEMS

B 3.7.c Ultimate Heat Sink (UHS)-Shutdown

BASES The Mississippi River provides an Ultimate Heat Sink with sufficient cooling capacity to either provide normal cooldown of the units, or to mitigate the effects of accident conditions within acceptable limits for one unit while conducting a normal cooldown on the other unit.

Movement of a Spent Fuel Cask containing Spent Nuclear Fuel in a sealed Multi-Purpose Canister (MPC) and using a single failure-proof crane is not considered to be "movement of irradiated fuel assemblies in secondary containment."

For more information, see references UFSAR, Section 9.1.4.3.2 and NRC Safety Evaluation Report associated with the Holtec International HI-STORM 100 Storage System (Docket Number 72-1014, Certificate Number 1014, Amendment 2).

Quad Cities 1 and 2 B 3.7.d-1 Revision 0 TRM Liquid Holdup Tanks B 3.7.d B 3.7 PLANT SYSTEMS

B 3.7.d Liquid Holdup Tanks

BASES Restricting the quantity of radioactive material contained in the specified tanks provides assurance that in the event of an uncontrolled release of the tanks' contents, the resulting concentrations would be less than the limits of 10 CFR Part 20, Appendix B, Table 2, Column 2, in an unrestricted area. Recirculation of the tank contents for the purpose of reducing the radioactive content is not considered to be an addition of radioactive material to the tank.

Quad Cities 1 and 2 B 3.7.e-1 Revision 0 TRM Explosive Gas Mixture B 3.7.e B 3.7 PLANT SYSTEMS

B 3.7.e Explosive Gas Mixture

BASES

The specification is provided to ensure that the concentration of potentially explosive gas mixtures contained in the waste gas holdup system is maintained below the flammability limits of hydrogen and oxygen. Maintaining the concentration of hydrogen and oxygen below their flammability limits provides assurance that the releases of radioactive materials will be controlled in conformance with the requirement s of General Design Criterion 60 of Appendix A

to 10 CFR Part 50.

Quad Cities 1 and 2 B 3.7.f-1 Revision 0 TRM Explosive Gas Mixture B 3.7.f B 3.7 PLANT SYSTEMS

B 3.7.f Flood Protection

BASES

Flood protection measures are provided to protect the systems and equipment necessary for safe shutdown during high water conditions. The equipment necessary to implement the appropriate measures, as detailed in plant procedures, is required to be available, but not necessarily onsite, to implement the procedures in a timely manner. The selected water levels are based on providing timely protection from the design basis flood of the river.

Quad Cities 1 and 2 B 3.7.g-1 Revision 0 TRM Sealed Source Contamination B 3.7.g B 3.7 PLANT SYSTEMS

B 3.7.g Sealed Source Contamination

BASES The limitations on removable contamination for sources requiring leak testing, including alpha emitters, is based on 10 CFR 70.39(c) limits for plutonium. This limitation will ensure that leakage from byproduct, source, and special nuclear material sources will not exceed allowable intake values. Sealed sources, including startup sources and fission detectors, are classified into three groups according to their use, with surveillance requirements commensurate with the probability of damage to a source in that group. Those sources which are frequently handled are required to be tested more often than those which are not. Sealed sources which are continuously enclosed within a shielded mechanism, i.e., sealed sources within radiation

monitoring or boron measuring devices, are considered to be stored and need not be tested unless they are removed from the shielded mechanism.

TRM Snubbers B 3.7.h Quad Cities 1 and 2 B 3.7.h-1 Revision QC-TRM-04-004

B 3.7 PLANT SYSTEMS

B 3.7.h Snubbers

BASES

Snubbers are provided to ensure that the structural integrity of the reactor coolant system and all other safety-related systems is maintained during and following a seismic event or other events that initiate dynamic loads. To maintain a constant level of snubber protection to the systems, periodic visual inspection, functional testing and the service life monitoring of snubbers is performed in accordance with the 10CFR50.55a approved edition of the ASME OMa Code, Subsection ISTD as denoted in the current revision of the Inservice Inspection Plan.

Quad Cities 1 and 2 B 3.9.a-1 Revision 0 TRM Communications B 3.9.a B 3.9 REFUELING OPERATIONS

B 3.9.a Communications

BASES

The requirement for communications capability ensures that refueling station personnel can be promptly informed of significant or potential changes in the facility status or core reactivity during CORE ALTERATIONS.