ML24191A315: Difference between revisions

From kanterella
Jump to navigation Jump to search
(StriderTol Bot insert)
 
(No difference)

Latest revision as of 11:48, 20 June 2025

Final Safety Analysis Report Rev. OL-27 and Technical Specification Bases Rev. 25, Chapter 1, Use and Application
ML24191A315
Person / Time
Site: Callaway Ameren icon.png
Issue date: 05/06/2024
From:
Ameren Missouri, Union Electric Co
To:
Office of Nuclear Reactor Regulation
Shared Package
ML24191A265 List: ... further results
References
ULNRC-06877
Download: ML24191A315 (1)


Text

CALLAWAY PLANT 1.0-i CHAPTER TABLE OF CONTENTS CHAPTER 1.0 USE AND APPLICATION Section Page 1.1 Definitions............................................................................................................. 1.1-1 ACTIONS........................................................................................................ 1.1-1 ACTUATION LOGIC TEST............................................................................. 1.1-1 AXIAL FLUX DIFFERENCE (AFD)................................................................. 1.1-1 CHANNEL CALIBRATION.............................................................................. 1.1-1 CHANNEL CHECK.......................................................................................... 1.1-1 CHANNEL OPERATIONAL TEST (COT)....................................................... 1.1-2 CORE ALTERATION...................................................................................... 1.1-2 CORE OPERATING LIMITS REPORT (COLR).............................................. 1.1-2 DOSE EQUIVALENT I-131............................................................................. 1.1-2 DOSE EQUIVALENT XE-133......................................................................... 1.1-3 ENGINEERED SAFETY FEATURE (ESF) RESPONSE TIME....................... 1.1-3 INSERVICE TESTING PROGRAM................................................................. 1.1-3 LEAKAGE........................................................................................................ 1.1-3 MASTER RELAY TEST.................................................................................. 1.1-4 MODE.............................................................................................................. 1.1-4 OPERABLE - OPERABILITY.......................................................................... 1.1-4 PHYSICS TESTS............................................................................................ 1.1-5 PRESSURE AND TEMPERATURE LIMITS REPORT (PTLR)....................... 1.1-5 QUADRANT POWER TILT RATIO (QPTR).................................................... 1.1-5 RATED THERMAL POWER (RTP)................................................................. 1.1-5 REACTOR TRIP SYSTEM (RTS) RESPONSE TIME..................................... 1.1-5 SHUTDOWN MARGIN (SDM)........................................................................ 1.1-6 SLAVE RELAY TEST...................................................................................... 1.1-6 STAGGERED TEST BASIS............................................................................ 1.1-6 THERMAL POWER......................................................................................... 1.1-6 TRIP ACTUATING DEVICE OPERATIONAL TEST (TADOT)........................ 1.1-6 1.2 Logical Connectors............................................................................................... 1.2-1 PURPOSE....................................................................................................... 1.2-1 BACKGROUND............................................................................................... 1.2-1 EXAMPLES..................................................................................................... 1.2-2 1.3 Completion Times................................................................................................. 1.3-1 PURPOSE....................................................................................................... 1.3-1 BACKGROUND............................................................................................... 1.3-1 DESCRIPTION................................................................................................ 1.3-1

CALLAWAY - SP CHAPTER TABLE OF CONTENTS (Continued)

Section Page 1.0-ii EXAMPLES..................................................................................................... 1.3-3 IMMEDIATE COMPLETION TIME................................................................ 1.3-14 1.4 Frequency............................................................................................................. 1.4-1 PURPOSE....................................................................................................... 1.4-1 DESCRIPTION................................................................................................ 1.4-1 EXAMPLES..................................................................................................... 1.4-2

CALLAWAY PLANT 1.0-i LIST OF TABLES Number Title 1.1-1 MODES

CALLAWAY PLANT 1.1-1 Amendment 135 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 Specifications and Bases.

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

ACTUATION LOGIC TEST An ACTUATION LOGIC TEST shall be the application of various simulated or actual input combinations in conjunction with each possible interlock logic state required for OPERABILITY of a logic circuit and the verification of the required logic output. The ACTUATION LOGIC TEST, as a minimum, shall include a continuity check of output devices.

AXIAL FLUX DIFFERENCE (AFD)

AFD shall be the difference in normalized flux signals between the top and bottom halves of an excore neutron detector.

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

Definitions 1.1 1.1 Definitions (continued)

CALLAWAY PLANT 1.1-2 Amendment 233 CHANNEL OPERATIONAL TEST (COT)

A COT 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 COT shall include adjustments, as necessary, of the required alarm, interlock, and trip setpoints required for channel OPERABILITY such that the setpoints are within the necessary range and accuracy. The COT 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.

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

CORE OPERATING LIMITS REPORT (COLR)

The COLR is the unit specific document that provides cycle specific parameter limits for the current reload cycle. These cycle specific parameter limits shall be determined for each reload cycle in accordance with Specification 5.6.5. Plant operation within these limits is addressed in individual Specifications.

DOSE EQUIVALENT I-131 DOSE EQUIVALENT I-131 shall be that concentration of I-131 (microcuries per gram) that alone would produce the same dose when inhaled as the combined activities of iodine isotopes I-131, I-132, I-133, I-134, and I-135 actually present.

The determination of DOSE EQUIVALENT I-131 shall be performed using thyroid dose conversion factors from:

1. Table 2.1 of EPA Federal Guidance Report No. 11, EPA-520/1-88-020, "Limiting Values of Radionuclide Intake and Air Concentration and Dose Conversion Factors for Inhalation, Submersion, and Ingestion," 1988.

(continued)

Definitions 1.1 1.1 Definitions (continued)

CALLAWAY PLANT 1.1-3 Amendment 222 DOSE EQUIVALENT XE-133 DOSE EQUIVALENT XE-133 shall be that concentration of Xe-133 (microcuries per gram) that alone would produce the same acute dose to the whole body as the combined activities of noble gas nuclides Kr-85m, Kr-87, Kr-88, Xe-133m, Xe-133, Xe-135m, Xe-135, and Xe-138 actually present. If a specific noble gas nuclide is not detected, it should be assumed to be present at the minimum detectable activity.

The determination of DOSE EQUIVALENT XE-133 shall be performed using the effective dose conversion factors for air submersion listed in Table III.1 of EPA Federal Guidance Report No. 12, EPA-402-R-93-081, "External Exposure to Radionuclides in Air, Water, and Soil", 1993.

ENGINEERED SAFETY FEATURE (ESF) RESPONSE TIME The ESF RESPONSE TIME shall be that time interval from when the monitored parameter exceeds its ESF actuation setpoint at the channel sensor until the ESF equipment is capable of performing its safety function (i.e., the valves travel to their required positions, pump discharge pressures reach their required values, etc.). Times shall include diesel generator starting and sequence loading delays, where applicable. The response time may be measured by means of any series of sequential, overlapping, or total steps so that the entire response time is measured. In lieu of measurement, response time may be verified for selected components provided that the components and methodology for verification have been previously reviewed and approved by the NRC.

INSERVICE TESTING PROGRAM The INSERVICE TESTING PROGRAM is the licensee program that fulfills the requirements of 10 CFR 50.55a(f).

LEAKAGE LEAKAGE shall be:

a. Identified LEAKAGE
1. LEAKAGE, such as that from pump seals or valve packing (except reactor coolant pump (RCP) seal water leakoff), that is captured and conducted to collection systems or a sump or collecting tank;
2. LEAKAGE into the containment atmosphere from sources that are both specifically located and known either not to interfere with the operation of leakage detection systems or not to be pressure boundary LEAKAGE; or (continued)

Definitions 1.1 1.1 Definitions CALLAWAY PLANT 1.1-4 Amendment 222 LEAKAGE (continued)

3. Reactor Coolant System (RCS) LEAKAGE through a steam generator to the Secondary System (primary to secondary LEAKAGE);
b. Unidentified LEAKAGE All LEAKAGE (except RCP seal water leakoff) that is not identified LEAKAGE;
c. Pressure Boundary LEAKAGE LEAKAGE (except primary to secondary LEAKAGE) through a nonisolable fault in an RCS component body, pipe wall, or vessel wall.

MASTER RELAY TEST A MASTER RELAY TEST shall consist of energizing all master relays in the channel required for channel OPERABILITY and verifying the OPERABILITY of each required master relay. The MASTER RELAY TEST shall include a continuity check of each associated required slave relay. The MASTER RELAY TEST may be performed by means of any series of sequential, overlapping, or total steps.

MODE A MODE shall correspond to any one inclusive combination of core reactivity condition, power level, average reactor coolant temperature, and reactor vessel head closure bolt tensioning specified in Table 1.1-1 with fuel in the reactor vessel.

OPERABLE - OPERABILITY A system, subsystem, train, 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, train, component, or device to perform its specified safety function(s) are also capable of performing their related support function(s).

(continued)

Definitions 1.1 1.1 Definitions (continued)

CALLAWAY PLANT 1.1-5 Amendment 222 PHYSICS TESTS PHYSICS TESTS shall be those tests performed to measure the fundamental nuclear characteristics of the reactor core and related instrumentation. These tests are:

a. Described in Chapter 14 of the FSAR;
b. Authorized under the provisions of 10 CFR 50.59; or
c. Otherwise approved by the Nuclear Regulatory Commission.

PRESSURE AND TEMPERATURE LIMITS REPORT (PTLR)

The PTLR is the unit specific document that provides the reactor vessel pressure and temperature limits, including heatup and REPORT (PTLR) cooldown rates, the power operated relief valve (PORV) lift settings, and the Cold Overpressure Mitigation System (COMS) arming temperature, for the current reactor vessel fluence period. These pressure and temperature limits shall be determined for each fluence period in accordance with Specification 5.6.6.

QUADRANT POWER TILT RATIO (QPTR)

QPTR shall be the ratio of the maximum upper excore detector calibrated output to the average of the upper excore detector calibrated outputs, or the ratio of the maximum lower excore detector calibrated output to the average of the lower excore detector calibrated outputs, whichever is greater.

RATED THERMAL POWER (RTP)

RTP shall be a total reactor core heat transfer rate to the reactor coolant of 3565 MWt.

REACTOR TRIP SYSTEM (RTS) RESPONSE TIME The RTS RESPONSE TIME shall be that time interval from when the monitored parameter exceeds its RTS trip setpoint at the channel sensor until loss of stationary gripper coil voltage. The response time may be measured by means of any series of sequential, overlapping, or total steps so that the entire response time is measured. In lieu of measurement, response time may be verified for selected components provided that the components and methodology for verification have been previously reviewed and approved by the NRC.

(continued)

Definitions 1.1 1.1 Definitions (continued)

CALLAWAY PLANT 1.1-6 Amendment 222 SHUTDOWN MARGIN (SDM)

SDM shall be the instantaneous amount of reactivity by which the reactor is subcritical or would be subcritical from its present condition assuming:

a. All rod cluster control assemblies (RCCAs) are fully inserted except for the single RCCA of highest reactivity worth, which is assumed to be fully withdrawn. With any RCCA not capable of being fully inserted, the reactivity worth of the RCCA must be accounted for in the determination of SDM; and
b. In MODES 1 and 2, the fuel and moderator temperatures are changed to the hot zero power temperatures.

SLAVE RELAY TEST A SLAVE RELAY TEST shall consist of energizing all slave relays in the channel required for channel OPERABILITY and verifying the OPERABILITY of each required slave relay. The SLAVE RELAY TEST shall include a continuity check of associated required testable actuation devices. The SLAVE RELAY TEST may be performed by means of any series of sequential, overlapping, or total steps.

STAGGERED TEST BASIS A STAGGERED TEST BASIS shall consist of the testing of one of the systems, subsystems, channels, or other designated components during the interval specified by the Surveillance Frequency, so that all systems, subsystems, channels, or other designated components are tested during n Surveillance Frequency intervals, where n is the total number of systems, subsystems, channels, or other designated components in the associated function.

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

TRIP ACTUATING DEVICE OPERATIONAL TEST (TADOT)

A TADOT shall consist of operating the trip actuating device and verifying the OPERABILITY of all devices in the channel required for trip actuating device OPERABILITY. The TADOT shall include adjustment, as necessary, of the trip actuating device so that it actuates at the required setpoint within the necessary accuracy. The TADOT may be performed by means of any series of sequential, overlapping, or total channel steps.

CALLAWAY PLANT 1.1-7 Amendment 133 Definitions 1.1 TABLE 1.1-1 (PAGE 1 OF 1)

MODES (a)

Excluding decay heat.

(b)

At least 53 of 54 reactor vessel head closure bolts fully tensioned.

(c)

Two or more reactor vessel head closure bolts less than fully tensioned.

MODE TITLE REACTIVITY CONDITION (keff)

% RATED THERMAL POWER(a)

AVERAGE REACTOR COOLANT TEMPERATURE

(°F) 1 Power Operation 0.99

> 5 NA 2

Startup 0.99 5

NA 3

Hot Standby

< 0.99 NA 350 4

Hot Shutdown(b)

< 0.99 NA 350 > Tavg > 200 5

Cold Shutdown(b)

< 0.99 NA 200 6

Refueling(c)

NA NA NA

CALLAWAY PLANT 1.2-1 Amendment 133 Logical Connectors 1.2 1.0 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 Specifications (TS) to discriminate between, and yet connect, discrete Conditions, Required Actions, Completion Times, Surveillances, and Frequencies. The only logical connectors that appear in TS 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 indentations 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.

(Continued)

Logical Connectors 1.2 1.2 Logical Connectors (continued)

CALLAWAY PLANT 1.2-2 Amendment 133 EXAMPLES The following examples illustrate the use of logical connectors.

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

CONDITION REQUIRED ACTION COMPLETION TIME A.

LCO not met.

A.1 Verify...

AND A.2 Restore...

(continued)

Logical Connectors 1.2 1.2 Logical Connectors CALLAWAY PLANT 1.2-3 Amendment 133 EXAMPLES (continued)

EXAMPLE 1.2-2 ACTIONS 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.

CONDITION REQUIRED ACTION COMPLETION TIME A.

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

CALLAWAY PLANT 1.3-1 Amendment 227 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 Limiting Conditions for Operation (LCOs) specify minimum requirements for ensuring safe operation of the unit. The ACTIONS associated with an LCO state Conditions that typically describe the ways in which the requirements of the LCO 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 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 LCO.

Unless otherwise specified, the Completion Time begins when a senior licensed operator on the operating shift crew with responsibility for plant operations makes the determination that an LCO is not met and an ACTIONS Condition is entered. The "otherwise specified" exceptions are varied, such as a Required Action Note or Surveillance Requirement Note that provides an alternative time to perform specific tasks, such as testing, without starting the Completion Time. While utilizing the Note, should a Condition be applicable for any reason not addressed by the Note, the Completion Time begins. Should the time allowance in the Note be exceeded, the Completion Time begins at that point. The exceptions may also be incorporated into the Completion Time. For example, LCO 3.8.1, "AC Sources - Operating," Required Action B.2, requires declaring required feature(s) supported by an inoperable diesel generator inoperable when the redundant required feature(s) are inoperable. The Completion Time states, "4 hours4.62963e-5 days <br />0.00111 hours <br />6.613757e-6 weeks <br />1.522e-6 months <br /> from discovery of Condition B concurrent with inoperability of redundant required feature(s)." In this case, the Completion Time does not begin until the conditions in the Completion Time are satisfied.

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

(Continued)

Completion Times 1.3 1.3 Completion Times CALLAWAY PLANT 1.3-2 Amendment 227 l DESCRIPTION (continued)

If situations are discovered that require entry into more than one Condition at a time within a single LCO (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 discovery of the situation that required entry into the Condition, unless otherwise specified.

Once a Condition has been entered, subsequent trains, 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, unless otherwise specified.

However, when a subsequent train, subsystem, component, 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 extensions do not apply to those Specifications that have exceptions that allow completely separate re-entry into the Condition (for each train, 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 Specifications.

(continued)

Completion Times 1.3 1.3 Completion Times CALLAWAY PLANT 1.3-3 Amendment 229 DESCRIPTION (continued)

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

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

EXAMPLE 1.3-1 ACTIONS 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 6 hours6.944444e-5 days <br />0.00167 hours <br />9.920635e-6 weeks <br />2.283e-6 months <br /> AND in MODE 5 within 36 hours4.166667e-4 days <br />0.01 hours <br />5.952381e-5 weeks <br />1.3698e-5 months <br />. A total of 6 hours6.944444e-5 days <br />0.00167 hours <br />9.920635e-6 weeks <br />2.283e-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 42 hours4.861111e-4 days <br />0.0117 hours <br />6.944444e-5 weeks <br />1.5981e-5 months <br />) is allowed for reaching MODE 5 from the time that Condition B was entered. If MODE 3 is reached within 3 hours3.472222e-5 days <br />8.333333e-4 hours <br />4.960317e-6 weeks <br />1.1415e-6 months <br />, the time allowed for reaching MODE 5 is the next 33 hours3.819444e-4 days <br />0.00917 hours <br />5.456349e-5 weeks <br />1.25565e-5 months <br /> because the total time allowed for reaching MODE 5 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 5 is the next 36 hours4.166667e-4 days <br />0.01 hours <br />5.952381e-5 weeks <br />1.3698e-5 months <br />.

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

6 hours6.944444e-5 days <br />0.00167 hours <br />9.920635e-6 weeks <br />2.283e-6 months <br /> 36 hours (continued)

Completion Times 1.3 1.3 Completion Times CALLAWAY PLANT 1.3-4 Amendment 133 EXAMPLES (continued)

EXAMPLE 1.3-2 ACTIONS 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. LCO 3.0.3 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 LCO 3.0.3 is entered, but continues to be tracked from the time Condition A was initially entered.

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

While in LCO 3.0.3, if one of the inoperable pumps is restored to OPERABLE status and the Completion Time for Condition A has expired, LCO 3.0.3 may be exited and operation continued in accordance with 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 5.

6 hours6.944444e-5 days <br />0.00167 hours <br />9.920635e-6 weeks <br />2.283e-6 months <br /> 36 hours (continued)

Completion Times 1.3 1.3 Completion Times CALLAWAY PLANT 1.3-5 Amendment 133 EXAMPLES EXAMPLE 1.3-2 (continued)

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)

Completion Times 1.3 1.3 Completion Times CALLAWAY PLANT 1.3-6 Amendment 229 EXAMPLES (continued)

EXAMPLE 1.3-3 ACTIONS CONDITION REQUIRED ACTION COMPLETION TIME A.

One Function X train inoperable.

A.1 Restore Function X train to OPERABLE status.

7 days B.

One Function Y train inoperable.

B.1 Restore Function Y train to OPERABLE status.

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

One Function X train inoperable.

AND One Function Y train inoperable.

C.1 Restore Function X train to OPERABLE status.

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

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

Completion Times 1.3 1.3 Completion Times CALLAWAY PLANT 1.3-7 Amendment 229 EXAMPLES EXAMPLE 1.3-3 (continued)

When one Function X train and one Function Y train are inoperable, Condition A and Condition B are concurrently applicable. The Completion Times for Condition A and Condition B are tracked separately for each train starting from the time each train was declared inoperable and the Condition was entered. A separate Completion Time is established for Condition C and tracked from the time the second train 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.

It is possible to alternate between Conditions A, B, and C in such a manner that operation could continue indefinitely without ever restoring systems to meet the LCO. However, doing so would be inconsistent with the basis of the Completion Times. Therefore, there shall be administrative controls to limit the maximum time allowed for any combination of Conditions that result in a single contiguous occurrence of failing to meet the LCO. These administrative controls shall ensure that the Completion Times for those Conditions are not inappropriately extended.

(continued)

Completion Times 1.3 1.3 Completion Times CALLAWAY PLANT 1.3-8 Amendment 133 EXAMPLES (continued)

EXAMPLE 1.3-4 ACTIONS 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 /> (including the extension) expires while one or more valves are still inoperable, Condition B is entered.

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.

6 hours6.944444e-5 days <br />0.00167 hours <br />9.920635e-6 weeks <br />2.283e-6 months <br /> 12 hours (continued)

Completion Times 1.3 1.3 Completion Times CALLAWAY PLANT 1.3-9 Amendment 133 EXAMPLES (continued)

EXAMPLE 1.3-5 ACTIONS


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

Separate Condition entry is allowed for each inoperable valve.

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.

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.

6 hours6.944444e-5 days <br />0.00167 hours <br />9.920635e-6 weeks <br />2.283e-6 months <br /> 12 hours (continued)

Completion Times 1.3 1.3 Completion Times CALLAWAY PLANT 1.3-10 Amendment 135 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 SR 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 hours B.

Required Action and associated Completion Time not met.

B.1 Be in MODE 3.

6 hours6.944444e-5 days <br />0.00167 hours <br />9.920635e-6 weeks <br />2.283e-6 months <br /> (continued)

Completion Times 1.3 1.3 Completion Times CALLAWAY PLANT 1.3-11 Amendment 133 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 SR 3.0.2, 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 complete 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 SR 3.0.2),

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)

Completion Times 1.3 1.3 Completion Times CALLAWAY PLANT 1.3-12 Amendment 133 EXAMPLES (continued)

EXAMPLE 1.3-7 ACTIONS 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 SR 3.0.2), 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 is met after Condition B is entered, Condition B is exited and operation may continue in accordance with CONDITION REQUIRED ACTION COMPLETION TIME A.

One subsystem inoperable.

A.1 Verify affected subsystem isolated.

AND A.2 Restore subsystem to OPERABLE status.

1 hours1.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 5.

6 hours6.944444e-5 days <br />0.00167 hours <br />9.920635e-6 weeks <br />2.283e-6 months <br /> 36 hours (continued)

Completion Times 1.3 1.3 Completion Times CALLAWAY PLANT 1.3-13 Amendment 229 EXAMPLES EXAMPLE 1.3-7 (continued)

Condition A, provided the Completion Time for Required Action A.2 has not expired.

EXAMPLE 1.3-8 ACTIONS When a subsystem is declared inoperable, Condition A is entered. The 7 day Completion Time may be applied as discussed in Example 1.3-2.

However, the licensee may elect to apply the Risk Informed Completion Time Program which permits calculation of a Risk Informed Completion Time (RICT) that may be used to complete the Required Action beyond the 7 day Completion Time. The RICT cannot exceed 30 days. After the 7 day Completion Time has expired, the subsystem must be restored to OPERABLE status within the RICT or Condition B must also be entered.

CONDITION REQUIRED ACTION COMPLETION TIME A.

One subsystem inoperable.

A.1 Restore subsystem to OPERABLE status.

7 days OR In accordance with the Risk Informed Completion Time Program B.

Required Action and associated Completion Time not met.

B.1 Be in MODE 3.

AND B.2 Be in MODE 5.

6 hours6.944444e-5 days <br />0.00167 hours <br />9.920635e-6 weeks <br />2.283e-6 months <br /> 36 hours (continued)

Completion Times 1.3 1.3 Completion Times CALLAWAY PLANT 1.3-14 Amendment 229 EXAMPLES EXAMPLE 1.3-8 (continued)

The Risk Informed Completion Time Program requires recalculation of the RICT to reflect changing plant conditions. For planned changes, the revised RICT must be determined prior to implementation of the change in configuration. For emergent conditions, the revised RICT must be determined within the time limits of the Required Action Completion Time (i.e., not the RICT) or 12 hours1.388889e-4 days <br />0.00333 hours <br />1.984127e-5 weeks <br />4.566e-6 months <br /> after the plant configuration change, whichever is less.

If the 7 day Completion Time clock of Condition A has expired and subsequent changes in plant condition result in exiting the applicability of the Risk Informed Completion Time Program without restoring the inoperable subsystem to OPERABLE status, Condition B is also entered and the Completion Time clocks for Required Actions B.1 and B.2 start.

If the RICT expires or is recalculated to be less than the elapsed time since the Condition was entered and the inoperable subsystem has not been restored to OPERABLE status, Condition B is also entered and the Completion Time clocks for Required Actions B.1 and B.2 start. If the inoperable subsystems are restored to OPERABLE status after Condition B is entered, Condition A is exited, and therefore, the Required Actions of Condition B may be terminated.

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

CALLAWAY PLANT 1.4-1 Amendment 133 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 Surveillance Requirement (SR) has a specified Frequency in which the Surveillance must be met in order to meet the associated LCO. An understanding of the correct application of the specified Frequency is necessary for compliance with the SR.

The "specified Frequency" is referred to throughout this section and each of the Specifications of Section 3.0, Surveillance Requirement (SR)

Applicability. The "specified Frequency" consists of the requirements of the Frequency column of each SR as well as certain Notes in the Surveillance column that modify performance requirements.

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 LCO is within its Applicability, represent potential SR 3.0.4 conflicts. To avoid these conflicts, the SR (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 SR satisfied, SR 3.0.4 imposes no restriction.

(Continued)

Frequency 1.4 1.4 Frequency (continued)

CALLAWAY PLANT 1.4-2 Amendment 133 EXAMPLES The following examples illustrate the various ways that Frequencies are specified. In these examples, the Applicability of the LCO (LCO not shown) is MODES 1, 2, and 3.

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

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

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

Frequency 1.4 1.4 Frequency CALLAWAY PLANT 1.4-3 Amendment 133 EXAMPLES (continued)

EXAMPLE 1.4-2 SURVEILLANCE REQUIREMENTS 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 />.

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 25% extension allowed by SR 3.0.2. "Thereafter" indicates future performances must be established per SR 3.0.2, 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.

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

Frequency 1.4 1.4 Frequency CALLAWAY PLANT 1.4-4 Amendment 133 EXAMPLES (continued)

EXAMPLE 1.4-3 SURVEILLANCE REQUIREMENTS 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 performed within the "specified Frequency." Therefore, if the Surveillance were not performed within the 7 day (plus the extension allowed by SR 3.0.2) interval, but operation was

< 25% RTP, it would not constitute a failure of the SR or failure to meet the LCO. Also, no violation of SR 3.0.4 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 SR 3.0.3 would apply.

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 day